[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Slow disk reads - exception Emask 0x0 SAct 0x6b0000 SErr 0x0 action 0x0



On 24.12.2021 22:44, Heladu wrote:
Hello,
First of all, thanks for the reply.

El vie, 24-12-2021 a las 03:30 +0500, Alexander V. Makartsev escribió:
 You can review SMART attributes which keep track of device's health and
metrics.
This utility is part of "smartmontools" package.
Run this one-liner to see values of relevant attributes:
    $ sudo smartctl -A /dev/sda | grep -E '5 Realloc|183 Runtime|197
Current|199 UDMA'

Here is what they should like on perfectly fine hard drive:
    $ sudo smartctl -A /dev/sda | grep -E '5 Realloc|183 Runtime|197
Current|199 UDMA'
      5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail 
Always       -       0
    183 Runtime_Bad_Block       0x0032   100   100   000    Old_age  
Always       -       0
    197 Current_Pending_Sector  0x0012   100   100   000    Old_age  
Always       -       0
    199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age  
Always       -       0

Raw values are displayed on the right and they all zeroes. Post the output
you got with next reply.
You should backup or "ddrescue" your data from this drive and RMA\replace it
or better switch to SSD disk.

Well, I installed the package in question and ran the very same command you
said. However, the Runtime_Bad_Block attribute doesn't appear. Here's the
output:
$ sudo smartctl -A /dev/sda | grep -E '5 Realloc|183 Runtime|197 Current|199
UDMA'
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-
fail  Always       -       0
197
Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -  
     1
199
UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -  
     0

If I understood correctly what I read, this means there's one sector waiting
for remapping, right? 
That is correct. Drive's firmware should take care of it automatically or during short or extended self-tests.
I suggest to backup your data before performing any self-tests on the drive.
They are non-destructive by nature, but you never know what could happen and what was the initial cause for 'bad blocks' to appear.

And why doesn't the Runtime_Bad_Block attribute appear?

SMART attributes and functionality could be different, depending on manufacturer or\and model of the device.
My example was from HDD made by Seagate. Maybe it was a mistake on my part, suggesting a one-liner with 'grep', causing a confusion.


-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀ 

Reply to: