I want to know if I have badblocks on my sdb5 HDD.
Steven Vollom
stevenvollom at sbcglobal.net
Sun Nov 23 10:26:33 UTC 2008
Frederic Schaer wrote:
> Steven Vollom a écrit :
>
>> Frederic Schaer wrote:
>>
>>
>>> Hi,
>>>
>>> I'm coming after the battle, but if smart reports there are bad blocks
>>> (using the previous given smartctl -a /dev/sdXX command), given the
>>> price of hard drives and given the price of your own data integrity
>>> (your data has no price, does it ?), I would directly go buy a new disk...
>>>
>>>
>>>
>>>
>>>> NO! Bad blocks are BAD. You map them out because they can NEVER be trusted.
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>> Dear Derek,
>>
>> I feel like a friend with all at the 'List' now, so I will embarrass
>> myself a bit. I am a retired fine-artist that never made a lot of
>> money. (It is obvious that 'fine' doesn't mean the quality of my work,
>> for I have not earned much from the task; it just means that art is what
>> I do for a living.) Consequently, when I had to retire and live on my
>> Social Security, (I could never save for old age.) it was an amount that
>> most people pay in tips each month. So I am just too poor to solve a
>> problem by purchasing something, unless I am absolutely sure the
>> something is really broken. Knowing that, is not an easy thing, when
>> you are as inhibited intellectually as I am. But even if the 'List' got
>> frustrated enough to boot me off, I will not stop trying to learn this
>> stuff. I will still be struggling to learn this system, when I am
>> looking up at the roots of grass, with a 'Here Lies' marker at my head.
>> I will not give up. I am not a quitter.
>>
>>
>>
> Hi,
>
> I'm sorry, I did not really mean that the easiest thing to do was buy a
> new disk : what I meant was that if badblock or smart starts telling you
> there are several bad blocks (lots of ?), you should really think about
> buying a new disk because yours is failing, and you will soon loose data :'(
> I've not seen a drive loosing sectors (blocks) without dying shortly
> after that
>
> I haven't seen the results of previous commands you were asked to run,
> so could you please try this :
>
> sudo apt-get install smartmontools
> sudo smartctl -a /dev/sdb
>
> Hopefully this will give you lots of output. If it does, please post the
> lines that look like this :
>
> 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail
> Always - 0
> ...
> 197 Current_Pending_Sector 0x0012 100 100 000 Old_age
> Always - 0
> 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age
> Offline - 0
>
> And be aware that if the last number (0 for me) is not 0 , your drive
> already knows about bad blocks and tried to or reallocated some already.
> If that number is high (more than ... I don't know : 100 ?), you're
> really going to be in trouble.
>
> If the above command (smartctl) doesn't give you any output... errhhh...
> you might try badblocks on the drive.
> Be warned however : keep backups of your data (just in case...) !!
>
> sudo badblocks -n /dev/sdb
>
> This is going to be veeeeerrryyyyyy slow though.
>
> Regards
>
>
This kind of report overwhelms me at my level of understanding. Could
you take a look and give an opinion on the health of the drive? Please
point out serious concerns?
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE
3 Spin_Up_Time 0x0027 193 189 063 Pre-fail
Always - 15420
4 Start_Stop_Count 0x0032 252 252 000 Old_age
Always - 2112
5 Reallocated_Sector_Ct 0x0033 253 253 063 Pre-fail
Always - 1
6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail
Offline - 0
7 Seek_Error_Rate 0x000a 253 252 000 Old_age
Always - 0
8 Seek_Time_Performance 0x0027 252 244 187 Pre-fail
Always - 36594
9 Power_On_Minutes 0x0032 179 179 000 Old_age
Always - 804h+02m
10 Spin_Retry_Count 0x002b 253 246 157 Pre-fail
Always - 0
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail
Always - 0
12 Power_Cycle_Count 0x0032 248 248 000 Old_age
Always - 2249
192 Power-Off_Retract_Count 0x0032 253 253 000 Old_age
Always - 0
193 Load_Cycle_Count 0x0032 253 253 000 Old_age
Always - 0
194 Temperature_Celsius 0x0032 253 253 000 Old_age
Always - 31
195 Hardware_ECC_Recovered 0x000a 253 252 000 Old_age
Always - 4355
196 Reallocated_Event_Count 0x0008 253 253 000 Old_age
Offline - 0
197 Current_Pending_Sector 0x0008 253 253 000 Old_age
Offline - 0
198 Offline_Uncorrectable 0x0008 253 253 000 Old_age
Offline - 0
199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age
Offline - 0
200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age
Always - 0
201 Soft_Read_Error_Rate 0x000a 253 248 000 Old_age
Always - 64
202 TA_Increase_Count 0x000a 253 252 000 Old_age
Always - 0
203 Run_Out_Cancel 0x000b 253 252 180 Pre-fail
Always - 1
204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age
Always - 0
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age
Always - 0
207 Spin_High_Current 0x002a 253 246 000 Old_age
Always - 0
208 Spin_Buzz 0x002a 253 252 000 Old_age
Always - 0
209 Offline_Seek_Performnce 0x0024 201 199 000 Old_age
Offline - 0
99 Unknown_Attribute 0x0004 253 253 000 Old_age
Offline - 0
100 Unknown_Attribute 0x0004 253 253 000 Old_age
Offline - 0
101 Unknown_Attribute 0x0004 253 253 000 Old_age
Offline - 0
SMART Error Log Version: 1
Warning: ATA error count 11 inconsistent with error log pointer 5
ATA Error Count: 11 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 11 occurred at disk power-on lifetime: 13012 hours (542 days + 4
hours)
When the command that caused the error occurred, the device was in an
unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 00 00 00 f0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 ff 01 00 00 00 f0 08 00:07:26.176 READ DMA
ef 03 46 b3 60 1f f0 08 00:07:26.176 SET FEATURES [Set transfer
mode]
c6 ff 10 b3 60 1f f0 08 00:07:26.176 SET MULTIPLE MODE
10 ff 50 b3 60 1f f0 08 00:07:26.160 RECALIBRATE [OBS-4]
91 ff 3f 00 00 00 ff 08 00:07:26.160 INITIALIZE DEVICE
PARAMETERS [OBS-6]
Error 10 occurred at disk power-on lifetime: 13012 hours (542 days + 4
hours)
When the command that caused the error occurred, the device was in an
unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 00 00 00 f0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 ff 01 00 00 00 f0 08 00:06:12.992 READ DMA
ef 03 46 fc e2 5d f0 08 00:06:12.992 SET FEATURES [Set transfer
mode]
c6 ff 10 fc e2 5d f0 08 00:06:12.992 SET MULTIPLE MODE
10 ff 50 fc e2 5d f0 08 00:06:12.976 RECALIBRATE [OBS-4]
91 ff 3f 00 00 00 ff 08 00:06:12.976 INITIALIZE DEVICE
PARAMETERS [OBS-6]
Error 9 occurred at disk power-on lifetime: 13012 hours (542 days + 4 hours)
When the command that caused the error occurred, the device was in an
unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 00 00 00 f0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 ff 01 00 00 00 f0 08 00:06:05.344 READ DMA
ef 03 46 05 26 db f0 08 00:06:05.344 SET FEATURES [Set transfer
mode]
c6 ff 10 05 26 db f0 08 00:06:05.344 SET MULTIPLE MODE
10 ff 50 05 26 db f0 08 00:06:05.328 RECALIBRATE [OBS-4]
91 ff 3f 00 00 00 ff 08 00:06:05.328 INITIALIZE DEVICE
PARAMETERS [OBS-6]
Error 8 occurred at disk power-on lifetime: 13012 hours (542 days + 4 hours)
When the command that caused the error occurred, the device was in an
unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 00 00 00 f0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 ff 01 00 00 00 f0 08 00:05:57.696 READ DMA
ef 03 46 0f e3 1e f0 08 00:05:57.696 SET FEATURES [Set transfer
mode]
c6 ff 10 0f e3 1e f0 08 00:05:57.696 SET MULTIPLE MODE
10 ff 50 0f e3 1e f0 08 00:05:57.680 RECALIBRATE [OBS-4]
91 ff 3f 00 00 00 ff 08 00:05:57.680 INITIALIZE DEVICE
PARAMETERS [OBS-6]
Error 7 occurred at disk power-on lifetime: 13012 hours (542 days + 4 hours)
When the command that caused the error occurred, the device was in an
unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 00 00 00 f0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 ff 01 00 00 00 f0 08 00:05:50.048 READ DMA
c6 03 10 3f fe 3f b0 08 00:05:47.872 SET MULTIPLE MODE
ef 03 46 3f fe 3f b0 08 00:05:47.872 SET FEATURES [Set transfer
mode]
40 00 01 3f fe 3f bf 08 00:05:47.872 READ VERIFY SECTOR(S)
10 00 3f 3f 00 00 bf 08 00:05:47.856 RECALIBRATE [OBS-4]
steven at Studio25:~$
More information about the kubuntu-users
mailing list