Unoffical empeg BBS

Quick Links: Empeg FAQ | RioCar.Org | Hijack | BigDisk Builder | jEmplode | emphatic
Repairs: Repairs

Topic Options
#298948 - 04/06/2007 14:41 smartctl output, dying drive ?
andy
carpal tunnel

Registered: 10/06/1999
Posts: 5916
Loc: Wivenhoe, Essex, UK
I assume this smartctl output means I should be placing a order for a new drive ?

vault:~# smartctl -a /dev/hda
smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model: ST3160023A
Serial Number: 5JS3B4JW
Firmware Version: 8.01
Device is: In smartctl database [for details use: -P show]
ATA Version is: 6
ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2
Local Time is: Mon Jun 4 17:29:04 2007 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 430) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 111) minutes.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 053 047 006 Pre-fail Always - 118256219
3 Spin_Up_Time 0x0003 097 096 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 0
5 Reallocated_Sector_Ct 0x0033 088 088 036 Pre-fail Always - 510
7 Seek_Error_Rate 0x000f 090 060 030 Pre-fail Always - 981870008
9 Power_On_Hours 0x0032 081 081 000 Old_age Always - 17352
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 132
194 Temperature_Celsius 0x0022 039 056 000 Old_age Always - 39
195 Hardware_ECC_Recovered 0x001a 053 047 000 Old_age Always - 118256219
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0
202 TA_Increase_Count 0x0032 092 245 000 Old_age Always - 8

SMART Error Log Version: 1
ATA Error Count: 17 (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 17 occurred at disk power-on lifetime: 17314 hours (721 days + 10 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 25 33 ff e7 Error: UNC at LBA = 0x07ff3325 = 134165285

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 1e 33 ff e7 00 02:47:18.842 READ SECTOR(S)
20 00 08 1e 33 cf e6 00 02:47:18.830 READ SECTOR(S)
20 00 08 fe 55 cf e6 00 02:47:18.824 READ SECTOR(S)
20 00 08 16 33 cf e6 00 02:47:18.820 READ SECTOR(S)
20 00 08 26 33 33 e6 00 02:47:18.814 READ SECTOR(S)

Error 16 occurred at disk power-on lifetime: 17247 hours (718 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 02 24 33 87 e9 Error: UNC at LBA = 0x09873324 = 159855396

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 1e 33 87 e9 00 08:11:42.927 READ SECTOR(S)
20 00 08 2e 33 ef e6 00 08:11:42.918 READ SECTOR(S)
20 00 08 46 5b ef e6 00 08:11:42.908 READ SECTOR(S)
20 00 08 16 5b 3f e3 00 08:11:42.890 READ SECTOR(S)
20 00 08 c6 5a 5b ef 00 08:11:42.874 READ SECTOR(S)

Error 15 occurred at disk power-on lifetime: 17243 hours (718 days + 11 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 06 00 7b 11 e0 Error: UNC at LBA = 0x00117b00 = 1145600

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 fe 7a 11 e0 00 03:22:44.513 READ SECTOR(S)
20 00 08 de 7a 11 e0 00 03:22:44.504 READ SECTOR(S)
20 00 08 be a5 10 e0 00 03:22:44.485 READ SECTOR(S)
20 00 08 06 fc 12 e0 00 03:22:44.423 READ SECTOR(S)
20 00 08 e6 fb 12 e0 00 03:22:44.071 READ SECTOR(S)

Error 14 occurred at disk power-on lifetime: 17242 hours (718 days + 10 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 06 98 67 11 e0 Error: UNC at LBA = 0x00116798 = 1140632

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 96 67 11 e0 00 02:24:40.495 READ SECTOR(S)
20 00 08 5e 7a c8 e4 00 02:24:40.493 READ SECTOR(S)
20 00 f8 66 79 c8 e4 00 02:24:40.482 READ SECTOR(S)
20 00 10 8e 4a 11 e0 00 02:24:40.480 READ SECTOR(S)
20 00 08 56 51 10 e0 00 02:24:40.470 READ SECTOR(S)

Error 13 occurred at disk power-on lifetime: 17173 hours (715 days + 13 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
10 51 2f 10 b9 02 e0 Error: IDNF at LBA = 0x0002b910 = 178448

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 40 ff b8 02 e0 00 06:17:50.472 READ SECTOR(S)
20 00 40 bf b8 02 e0 00 06:17:50.468 READ SECTOR(S)
20 00 40 7f b8 02 e0 00 06:17:50.464 READ SECTOR(S)
20 00 40 3f b8 02 e0 00 06:17:50.460 READ SECTOR(S)
20 00 40 ff b7 02 e0 00 06:17:50.453 READ SECTOR(S)

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 90% 17347 1145606
# 2 Short offline Completed without error 00% 17323 -
# 3 Extended offline Completed: read failure 90% 17300 1145606
# 4 Short offline Completed: read failure 90% 17299 1145606
# 5 Short offline Completed without error 00% 17276 -
# 6 Extended offline Completed: read failure 90% 17263 1145606
# 7 Short offline Completed: read failure 70% 17252 1014987
# 8 Short offline Completed without error 00% 17228 -
# 9 Short offline Completed: read failure 90% 17205 178495
#10 Short offline Completed without error 00% 17181 -
#11 Short offline Completed without error 00% 17158 -
#12 Extended offline Completed without error 00% 17136 -
#13 Short offline Completed without error 00% 17134 -
#14 Short offline Completed without error 00% 17110 -
#15 Short offline Completed without error 00% 17087 -
#16 Short offline Completed without error 00% 17063 -
#17 Short offline Completed without error 00% 17040 -
#18 Short offline Completed without error 00% 17016 -
#19 Short offline Completed without error 00% 16992 -
#20 Extended offline Completed without error 00% 16971 -
#21 Short offline Completed without error 00% 16968 -

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
_________________________
Remind me to change my signature to something more interesting someday

Top
#298949 - 04/06/2007 15:09 Re: smartctl output, dying drive ? [Re: andy]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 14493
Loc: Canada
Quote:
I assume this smartctl output means I should be placing a order for a new drive ?


That's certainly what I would do.

Cheers

Top
#298950 - 04/06/2007 15:19 Re: smartctl output, dying drive ? [Re: mlord]
andy
carpal tunnel

Registered: 10/06/1999
Posts: 5916
Loc: Wivenhoe, Essex, UK
Thanks Mark, order placed. I wish Seagate in the UK had an advanced replacement scheme, then the 5 year warranty might actually be useful. Still at least I'll have a spare for next time

The mini-itx machine that this drive is in seems to like eating drives, I think this is the third to die in the last five years.
_________________________
Remind me to change my signature to something more interesting someday

Top
#298951 - 04/06/2007 15:23 Re: smartctl output, dying drive ? [Re: mlord]
peter
carpal tunnel

Registered: 13/07/2000
Posts: 4180
Loc: Cambridge, England
New drives are in fact pretty cheap these days. I just got a pair of 120Gb drives for £41 each from Dabs. With a touch of sadness, because it means the end is now sort-of in sight for the car-player: drives above 128Gb don't work with the stock kernel, and even Hijack doesn't help with drives above 160Gb as they're all Serial ATA only. So the time will come when I'll have more FLAC than I can ever fit in a car-player...

Peter

Top
#298952 - 04/06/2007 15:44 Re: smartctl output, dying drive ? [Re: peter]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 14493
Loc: Canada
Yeah, my local has Fujitsu 120GB notebook PATA drives for CDN$89/each.

But I'm just waiting for 32GB CF cards to drop into the sub-$300 range now..


Edited by mlord (04/06/2007 15:44)

Top
#298953 - 04/06/2007 15:54 Re: smartctl output, dying drive ? [Re: peter]
wfaulk
carpal tunnel

Registered: 25/12/2000
Posts: 16706
Loc: Raleigh, NC US
No reason you can't cram a SATA-PATA adapter in there.
_________________________
Bitt Faulk

Top
#298954 - 04/06/2007 16:25 Re: smartctl output, dying drive ? [Re: wfaulk]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 14493
Loc: Canada
Quote:
No reason you can't cram a SATA-PATA adapter in there.


Space.

I suppose one could fit the cable adapter plus the SATA/PATA converter
into one of the two drive bays, but then one could just use two PATA drives
instead for the same (or better, at the moment) capacity.

cheers


Edited by mlord (04/06/2007 16:25)

Top
#298955 - 04/06/2007 17:16 Re: smartctl output, dying drive ? [Re: mlord]
wfaulk
carpal tunnel

Registered: 25/12/2000
Posts: 16706
Loc: Raleigh, NC US
One would assume that, at some point, 2.5" SATA drives will have more than twice the capacity of PATA drives.
_________________________
Bitt Faulk

Top
#298956 - 04/06/2007 17:30 Re: smartctl output, dying drive ? [Re: andy]
LittleBlueThing
addict

Registered: 11/01/2002
Posts: 612
Loc: Reading, UK
Quote:
Thanks Mark, order placed. I wish Seagate in the UK had an advanced replacement scheme, then the 5 year warranty might actually be useful. Still at least I'll have a spare for next time

Maxtor used to IIRC. (Before Seagate bought them)

I spent about 45 minutes harranguing their tech support people, escalating it etc etc a few weeks back (slow work day) asking how I was supposed to get data onto my new drive if I'd sent the old one back? Was I supposed to copy it onto paper? I bought Maxtor because of the advance replacement; yada yada.

On the other hand Samsung are fabulous - I think you need to send them a cheque and they send back a drive by return. When the RMA drive gets to them they send back the cheque.

I buy Samsung where I can now
_________________________
LittleBlueThing Running twin 30's

Top
#298957 - 05/07/2007 14:04 Re: smartctl output, dying drive ? [Re: LittleBlueThing]
Schido
enthusiast

Registered: 29/03/2005
Posts: 364
Loc: Probably lost somewhere in Wal...
So, i guess my time to replace the drive has come too

(I get i/o errors and irq timeouts on the screen.)

Any limit on the drivesize on a mk1? (Will the big disk builder have enough memory?)



Code:

./smartctl -a /dev/hda
smartctl version 5.33 [arm-empeg-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model: FUJITSU MHT2040AT
Serial Number: NN58T4215RUE
Firmware Version: 0022
User Capacity: 40,007,761,920 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 6
ATA Standard is: ATA/ATAPI-6 T13 1410D revision 3a
Local Time is: Tue Jan 13 03:29:44 1970 /usr/local/armtools
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 293) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 40) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.

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
1 Raw_Read_Error_Rate 0x100f 100 100 046 Pre-fail Always - 113545
2 Throughput_Performance 0x0005 100 100 030 Pre-fail Offline - 14680064
3 Spin_Up_Time 0x0003 100 100 025 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 4707
5 Reallocated_Sector_Ct 0x0033 100 100 024 Pre-fail Always - 8564165181446
7 Seek_Error_Rate 0x070f 100 100 047 Pre-fail Always - 1406
8 Seek_Time_Performance 0x0005 100 100 019 Pre-fail Offline - 0
9 Power_On_Seconds 0x0032 099 099 000 Old_age Always - 755h+50m+56s
10 Spin_Retry_Count 0x0013 100 100 020 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 2042
192 Power-Off_Retract_Count 0x0032 094 094 000 Old_age Always - 1672
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 6032
194 Temperature_Celsius 0x0022 100 095 000 Old_age Always - 34 (Lifetime Min/Max 61/65535)
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 11692
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 286785542
197 Current_Pending_Sector 0x0012 099 099 000 Old_age Always - 2
198 Offline_Uncorrectable 0x0010 099 099 000 Old_age Offline - 3
199 UDMA_CRC_Error_Count 0x003e 200 196 000 Old_age Always - 117
200 Multi_Zone_Error_Rate 0x000f 100 100 060 Pre-fail Always - 11122
203 Run_Out_Cancel 0x0002 100 100 000 Old_age Always - 433776361662

SMART Error Log Version: 1
Warning: ATA error count 0 inconsistent with error log pointer 3

ATA Error Count: 0
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 0 occurred at disk power-on lifetime: 37892 hours (1578 days + 20 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
-- -- -- -- -- -- --
02 11 e0 59 00 00 03 Error:

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
00 02 e0 c4 fa 6e 00 73 00:00:16.384 NOP [Reserved subcommand]
00 02 e0 c4 ca 5b 00 73 00:00:00.000 NOP [Reserved subcommand]
00 02 e0 c4 af 5b 00 73 00:00:00.000 NOP [Reserved subcommand]
00 02 e0 c4 93 5b 00 73 00:00:00.000 NOP [Reserved subcommand]
00 02 e0 c4 75 5b 00 73 00:00:00.000 NOP [Reserved subcommand]

Error -1 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
When the command that caused the error occurred, the device was in standby mode.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
a0 00 73 02 e0 59 00

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
5b a0 73 02 e0 c4 ca 04 17d+19:46:04.928 [RESERVED]
5b 9c 73 02 e0 c4 af 04 17d+19:16:35.456 [RESERVED]
5b 98 73 02 e0 c4 93 04 17d+18:46:00.448 [RESERVED]
5b 94 73 02 e0 c4 75 04 17d+18:13:14.368 [RESERVED]
5b 90 73 02 e0 c4 58 04 17d+17:41:33.824 [RESERVED]

Error -2 occurred at disk power-on lifetime: 755 hours (31 days + 11 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 59 02 a2 73 02 e0 Error: UNC at LBA = 0x000273a2 = 160674

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c4 00 02 a2 73 02 e0 00 38d+05:30:39.624 READ MULTIPLE
c4 00 04 a0 73 02 e0 00 38d+05:30:34.598 READ MULTIPLE
c4 00 04 9c 73 02 e0 00 38d+05:30:34.570 READ MULTIPLE
c4 00 04 98 73 02 e0 00 38d+05:30:34.543 READ MULTIPLE
c4 00 04 94 73 02 e0 00 38d+05:30:34.515 READ MULTIPLE

Error -3 occurred at disk power-on lifetime: 0 hours (0 days + 0 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
-- -- -- -- -- -- --
00 00 03 11 00 00 00

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a0 4e 00 00 00 40 04 e6 31d+01:43:37.331 PACKET
a0 4e 00 00 00 00 04 ca 31d+01:43:37.331 PACKET
9c 4e 00 00 00 00 04 af 30d+07:05:08.467 [RESERVED]
98 4e 00 00 00 00 04 93 29d+12:26:39.603 CHECK POWER MODE [RET-4]
94 4e 00 00 00 00 04 74 28d+17:48:10.739 STANDBY IMMEDIATE [RET-4]

Error -4 occurred at disk power-on lifetime: 627 hours (26 days + 3 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
-- -- -- -- -- -- --
59 00 00 00 03 11 00 at LBA = 0x00110300 = 1114880

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
40 c4 04 9a 00 00 00 e0 12d+10:16:23.298 READ VERIFY SECTOR(S)
00 c4 87 85 00 00 00 e0 00:00:41.474 NOP [Reserved subcommand]
00 c4 69 85 00 00 00 e0 00:00:40.964 NOP [Reserved subcommand]
00 c4 4c 85 00 00 00 e0 00:00:39.940 NOP [Reserved subcommand]
00 c4 30 85 00 00 00 e0 00:00:38.916 NOP [Reserved subcommand]

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

_________________________
Empeg Mk1 #00177, 2.00 final, hijack 4.76

Top
#298958 - 11/07/2007 05:46 Re: smartctl output, dying drive ? [Re: andy]
andy
carpal tunnel

Registered: 10/06/1999
Posts: 5916
Loc: Wivenhoe, Essex, UK
After I finally got round to it, dd_rescue did a great job of recovering seemingly every sector from that failing drive. It did take a couple of days to work its way through all 160GB though (it wasn't an empeg drive by the way, it was the drive in my off-site backup server).
_________________________
Remind me to change my signature to something more interesting someday

Top