RAID-1 and bad sectors?

[Rod Speed]

(e-mail address removed) wrote

Could you elaborate?

You can get what appear to be bad sectors at a superficial
look due to a bad cable or bad controller outside the drive.

Seems like you and Chuck F. have made contradictory statements.

What he said was

There's no conflict with what I said. I never said that the drive
will always be able to ensure that no data is lost, most obviously
when it doesnt check that the write was successful, or when the
write worked and it cant be read successfully after that.

But all those "ecc errors" indicate my
drive is defective in some way, no?

Yes. I just meant that it aint about assumptions, clearly the
drive has a problem and the SMART data would confirm that.

 

[void]

I can try the knoppix cd you suggested. So I just boot up with it, and from
the console type "smartctl -a /dev/???" Will my hard drive already be mounted
as /dev/hdX? Or do I have to mount it myself (not sure how to do that)...
Also how do I save the output so that I can boot back into Windows and paste
it into a post for you? Thanks...

 

[Rod Speed]

(e-mail address removed) wrote

I can try the knoppix cd you suggested. So I just boot up
with it, and from the console type "smartctl -a /dev/???"

Yes, basically.

Will my hard drive already be mounted as /dev/hdX?

Yes, and you can see what it gets mounted as when knoppix has booted.

Or do I have to mount it myself (not sure how to do that)...

No need.

Also how do I save the output so that I can boot
back into Windows and paste it into a post for you?

Use the traditional approach, append > filename.log to the command, so
smartctl -a /dev/??? > filename.log

Rather than trying to specify where to put that, just do it like that
and then search using one of the searchers that knoppix has and
then cut and paste using one of the guis to where you want it.
I normally just paste it across the network to the system I am
using the usenet client on.

 

[void]

Here's the output (btw, that knoppix cd is pretty cool)... looks like there
are some errors. Would this indicate that there's definitely something wrong
with the disk, as opposed to a possible cable or controller problem that you
mentioned?



smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model: SAMSUNG SP1213N
Firmware Version: TL100-24
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0
Local Time is: Tue Jan 3 03:34:02 2006 EST
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: (4320) seconds.
Offline data collection
capabilities: (0x1b) 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.
No 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 72) 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 0x000b 100 100 051 Pre-fail Always
- 0
3 Spin_Up_Time 0x0007 065 065 000 Pre-fail Always
- 6016
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always
- 4
5 Reallocated_Sector_Ct 0x0033 253 253 010 Pre-fail Always
- 0
7 Seek_Error_Rate 0x000b 253 253 051 Pre-fail Always
- 0
8 Seek_Time_Performance 0x0024 253 253 000 Old_age Offline
- 0
9 Power_On_Half_Minutes 0x0032 100 100 000 Old_age Always
- 1011h+58m
10 Spin_Retry_Count 0x0013 253 253 049 Pre-fail Always
- 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always
- 3
194 Temperature_Celsius 0x0022 157 148 000 Old_age Always
- 27
195 Hardware_ECC_Recovered 0x000a 100 100 000 Old_age Always
- 7356760
196 Reallocated_Event_Count 0x0012 100 100 000 Old_age Always
- 1
197 Current_Pending_Sector 0x0033 253 253 010 Pre-fail Always
- 0
198 Offline_Uncorrectable 0x0031 100 100 010 Pre-fail Offline
- 1
199 UDMA_CRC_Error_Count 0x000b 100 100 051 Pre-fail Always
- 0
200 Multi_Zone_Error_Rate 0x000b 100 100 051 Pre-fail Always
- 0
201 Soft_Read_Error_Rate 0x000b 253 253 051 Pre-fail Always
- 0

SMART Error Log Version: 1
ATA Error Count: 69 (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 69 occurred at disk power-on lifetime: 940 hours (39 days + 4 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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:51.875 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:51.875 SET FEATURES [Set transfer mode]
c6 00 10 01 00 00 a0 00 41d+20:21:51.875 SET MULTIPLE MODE
00 03 01 01 00 00 a0 00 41d+20:21:51.813 NOP [Reserved subcommand]

Error 68 occurred at disk power-on lifetime: 940 hours (39 days + 4 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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:46.250 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:46.250 SET FEATURES [Set transfer mode]
c6 00 10 01 00 00 a0 00 41d+20:21:46.250 SET MULTIPLE MODE
00 03 01 01 00 00 a0 00 41d+20:21:46.250 NOP [Reserved subcommand]

Error 67 occurred at disk power-on lifetime: 940 hours (39 days + 4 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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:40.688 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:40.688 SET FEATURES [Set transfer mode]
c6 00 10 01 00 00 a0 00 41d+20:21:40.688 SET MULTIPLE MODE
00 03 01 01 00 00 a0 00 41d+20:21:40.625 NOP [Reserved subcommand]

Error 66 occurred at disk power-on lifetime: 940 hours (39 days + 4 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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:35.063 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:35.063 SET FEATURES [Set transfer mode]
c6 00 10 01 00 00 a0 00 41d+20:21:35.063 SET MULTIPLE MODE
00 03 01 01 00 00 a0 00 41d+20:21:35.000 NOP [Reserved subcommand]
ef 03 0c 01 10 00 a0 00 41d+20:21:34.938 SET FEATURES [Set transfer mode]

Error 65 occurred at disk power-on lifetime: 940 hours (39 days + 4 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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:29.313 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:29.313 SET FEATURES [Set transfer mode]
c6 00 10 01 00 00 a0 00 41d+20:21:29.313 SET MULTIPLE MODE
00 03 01 01 00 00 a0 00 41d+20:21:29.313 NOP [Reserved subcommand]

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


Device does not support Selective Self Tests/Logging

 

[Rod Speed]

Here's the output (btw, that knoppix cd is pretty cool)...

Yeah, its pretty decent in this situation.

looks like there are some errors.

Yes, but nothing to worry about. Comments added in the output.

Would this indicate that there's definitely
something wrong with the disk,

No, the disk looks fine.

as opposed to a possible cable or
controller problem that you mentioned?

Doesnt look like a cable problem either, that should
show up in the UDMA_CRC_Error_Count and its perfect.

smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model: SAMSUNG SP1213N
Firmware Version: TL100-24
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0
Local Time is: Tue Jan 3 03:34:02 2006 EST
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: (4320) seconds.
Offline data collection
capabilities: (0x1b) 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.
No 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 72) 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 0x000b 100 100 051 Pre-fail
Always - 0
3 Spin_Up_Time 0x0007 065 065 000 Pre-fail
Always - 6016
4 Start_Stop_Count 0x0032 100 100 000 Old_age
Always - 4
5 Reallocated_Sector_Ct 0x0033 253 253 010 Pre-fail
Always - 0
7 Seek_Error_Rate 0x000b 253 253 051 Pre-fail
Always - 0
8 Seek_Time_Performance 0x0024 253 253 000 Old_age
Offline - 0
9 Power_On_Half_Minutes 0x0032 100 100 000 Old_age
Always - 1011h+58m
10 Spin_Retry_Count 0x0013 253 253 049 Pre-fail
Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age
Always - 3
194 Temperature_Celsius 0x0022 157 148 000 Old_age
Always - 27
195 Hardware_ECC_Recovered 0x000a 100 100 000 Old_age
Always - 7356760

Thats normal with samsungs, just information, no indication of a problem.

196 Reallocated_Event_Count 0x0012 100 100 000 Old_age
Always - 1

That is saying that that has been just one reallocated sector.

Thats fine, nothing to worry about.

197 Current_Pending_Sector 0x0033 253 253 010 Pre-fail
Always - 0
198 Offline_Uncorrectable 0x0031 100 100 010 Pre-fail
Offline - 1

Thats the same single bad sector.

199 UDMA_CRC_Error_Count 0x000b 100 100 051 Pre-fail
Always - 0
200 Multi_Zone_Error_Rate 0x000b 100 100 051 Pre-fail
Always - 0
201 Soft_Read_Error_Rate 0x000b 253 253 051 Pre-fail
Always - 0

SMART Error Log Version: 1
ATA Error Count: 69 (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 69 occurred at disk power-on lifetime: 940 hours (39 days + 4
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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:51.875 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:51.875 SET FEATURES [Set
transfer mode] c6 00 10 01 00 00 a0 00 41d+20:21:51.875 SET
MULTIPLE MODE 00 03 01 01 00 00 a0 00 41d+20:21:51.813 NOP
[Reserved subcommand]

Error 68 occurred at disk power-on lifetime: 940 hours (39 days + 4
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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:46.250 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:46.250 SET FEATURES [Set
transfer mode] c6 00 10 01 00 00 a0 00 41d+20:21:46.250 SET
MULTIPLE MODE 00 03 01 01 00 00 a0 00 41d+20:21:46.250 NOP
[Reserved subcommand]

Error 67 occurred at disk power-on lifetime: 940 hours (39 days + 4
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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:40.688 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:40.688 SET FEATURES [Set
transfer mode] c6 00 10 01 00 00 a0 00 41d+20:21:40.688 SET
MULTIPLE MODE 00 03 01 01 00 00 a0 00 41d+20:21:40.625 NOP
[Reserved subcommand]

Error 66 occurred at disk power-on lifetime: 940 hours (39 days + 4
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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:35.063 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:35.063 SET FEATURES [Set
transfer mode] c6 00 10 01 00 00 a0 00 41d+20:21:35.063 SET
MULTIPLE MODE 00 03 01 01 00 00 a0 00 41d+20:21:35.000 NOP
[Reserved subcommand] ef 03 0c 01 10 00 a0 00 41d+20:21:34.938 SET
FEATURES [Set transfer mode]

Error 65 occurred at disk power-on lifetime: 940 hours (39 days + 4
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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:29.313 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:29.313 SET FEATURES [Set
transfer mode] c6 00 10 01 00 00 a0 00 41d+20:21:29.313 SET
MULTIPLE MODE 00 03 01 01 00 00 a0 00 41d+20:21:29.313 NOP
[Reserved subcommand]

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

Those are the same single bad sector.

 

[void]

So you're saying there's only 1 bad sector on the disk? Would this be one of
those they discovered at the factory, or one that developed after they shipped
it? Also, why did HUTIL report a ton of errors for various sectors? And I'm
not sure why you say the disk is fine... BootItNG already couldn't do
something because of the bad sector, and couldn't more bad sectors develop?

Thanks for your help.

Here's the output (btw, that knoppix cd is pretty cool)...

Yeah, its pretty decent in this situation.

looks like there are some errors.

Yes, but nothing to worry about. Comments added in the output.

Would this indicate that there's definitely
something wrong with the disk,

No, the disk looks fine.

as opposed to a possible cable or
controller problem that you mentioned?

Doesnt look like a cable problem either, that should
show up in the UDMA_CRC_Error_Count and its perfect.

smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model: SAMSUNG SP1213N
Firmware Version: TL100-24
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0
Local Time is: Tue Jan 3 03:34:02 2006 EST
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: (4320) seconds.
Offline data collection
capabilities: (0x1b) 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.
No 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 72) 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 0x000b 100 100 051 Pre-fail
Always - 0
3 Spin_Up_Time 0x0007 065 065 000 Pre-fail
Always - 6016
4 Start_Stop_Count 0x0032 100 100 000 Old_age
Always - 4
5 Reallocated_Sector_Ct 0x0033 253 253 010 Pre-fail
Always - 0
7 Seek_Error_Rate 0x000b 253 253 051 Pre-fail
Always - 0
8 Seek_Time_Performance 0x0024 253 253 000 Old_age
Offline - 0
9 Power_On_Half_Minutes 0x0032 100 100 000 Old_age
Always - 1011h+58m
10 Spin_Retry_Count 0x0013 253 253 049 Pre-fail
Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age
Always - 3
194 Temperature_Celsius 0x0022 157 148 000 Old_age
Always - 27
195 Hardware_ECC_Recovered 0x000a 100 100 000 Old_age
Always - 7356760

Thats normal with samsungs, just information, no indication of a problem.

196 Reallocated_Event_Count 0x0012 100 100 000 Old_age
Always - 1

That is saying that that has been just one reallocated sector.

Thats fine, nothing to worry about.

197 Current_Pending_Sector 0x0033 253 253 010 Pre-fail
Always - 0
198 Offline_Uncorrectable 0x0031 100 100 010 Pre-fail
Offline - 1

Thats the same single bad sector.

199 UDMA_CRC_Error_Count 0x000b 100 100 051 Pre-fail
Always - 0
200 Multi_Zone_Error_Rate 0x000b 100 100 051 Pre-fail
Always - 0
201 Soft_Read_Error_Rate 0x000b 253 253 051 Pre-fail
Always - 0

SMART Error Log Version: 1
ATA Error Count: 69 (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 69 occurred at disk power-on lifetime: 940 hours (39 days + 4
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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:51.875 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:51.875 SET FEATURES [Set
transfer mode] c6 00 10 01 00 00 a0 00 41d+20:21:51.875 SET
MULTIPLE MODE 00 03 01 01 00 00 a0 00 41d+20:21:51.813 NOP
[Reserved subcommand]

Error 68 occurred at disk power-on lifetime: 940 hours (39 days + 4
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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:46.250 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:46.250 SET FEATURES [Set
transfer mode] c6 00 10 01 00 00 a0 00 41d+20:21:46.250 SET
MULTIPLE MODE 00 03 01 01 00 00 a0 00 41d+20:21:46.250 NOP
[Reserved subcommand]

Error 67 occurred at disk power-on lifetime: 940 hours (39 days + 4
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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:40.688 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:40.688 SET FEATURES [Set
transfer mode] c6 00 10 01 00 00 a0 00 41d+20:21:40.688 SET
MULTIPLE MODE 00 03 01 01 00 00 a0 00 41d+20:21:40.625 NOP
[Reserved subcommand]

Error 66 occurred at disk power-on lifetime: 940 hours (39 days + 4
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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:35.063 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:35.063 SET FEATURES [Set
transfer mode] c6 00 10 01 00 00 a0 00 41d+20:21:35.063 SET
MULTIPLE MODE 00 03 01 01 00 00 a0 00 41d+20:21:35.000 NOP
[Reserved subcommand] ef 03 0c 01 10 00 a0 00 41d+20:21:34.938 SET
FEATURES [Set transfer mode]

Error 65 occurred at disk power-on lifetime: 940 hours (39 days + 4
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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:29.313 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:29.313 SET FEATURES [Set
transfer mode] c6 00 10 01 00 00 a0 00 41d+20:21:29.313 SET
MULTIPLE MODE 00 03 01 01 00 00 a0 00 41d+20:21:29.313 NOP
[Reserved subcommand]

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

Those are the same single bad sector.

Device does not support Selective Self Tests/Logging

 

[Rod Speed]

(e-mail address removed) wrote

So you're saying there's only 1 bad sector on the disk?

Even that isnt completely clear, those normally show up as
reallocated sectors. Yours shows up as a reallocation event.

Doesnt explain the different result you got with HUTIL either.

I'd ask Samsung what they make of both reports.

Would this be one of those they discovered at the factory,
Nope.

or one that developed after they shipped it?
Yes.

Also, why did HUTIL report a ton of errors for various sectors?

It doesnt actually, it just reports a series right at the end of the
drive. Looks rather like its having a brain fart or something.

And I'm not sure why you say the disk is fine...

Basically because the SMART report looks fine.

BootItNG already couldn't do something because of the bad sector,

Its not at all clear if that had anything to do with it at all.
Could just be some quirk of BootItNG

and couldn't more bad sectors develop?

Yes, but its clearly not reporting the number that HUTIL whined about.
Looks rather more like HUTIL had a brain fart and was attempting to
access past what the drive actually has or something.

I'd see what Samsung says about both reports.

I'd also see what Hitachi's DFT says about the drive, basically to check HUTIL.

Thanks for your help.

Please post what Samsung's response is.

(e-mail address removed) wrote

Here's the output (btw, that knoppix cd is pretty cool)...

Yeah, its pretty decent in this situation.

looks like there are some errors.

Yes, but nothing to worry about. Comments added in the output.

Would this indicate that there's definitely
something wrong with the disk,

No, the disk looks fine.

as opposed to a possible cable or
controller problem that you mentioned?

Doesnt look like a cable problem either, that should
show up in the UDMA_CRC_Error_Count and its perfect.

smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model: SAMSUNG SP1213N
Firmware Version: TL100-24
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0
Local Time is: Tue Jan 3 03:34:02 2006 EST
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: (4320) seconds.
Offline data collection
capabilities: (0x1b) 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.
No 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 72) 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 0x000b 100 100 051 Pre-fail
Always - 0
3 Spin_Up_Time 0x0007 065 065 000 Pre-fail
Always - 6016
4 Start_Stop_Count 0x0032 100 100 000 Old_age
Always - 4
5 Reallocated_Sector_Ct 0x0033 253 253 010 Pre-fail
Always - 0
7 Seek_Error_Rate 0x000b 253 253 051 Pre-fail
Always - 0
8 Seek_Time_Performance 0x0024 253 253 000 Old_age
Offline - 0
9 Power_On_Half_Minutes 0x0032 100 100 000 Old_age
Always - 1011h+58m
10 Spin_Retry_Count 0x0013 253 253 049 Pre-fail
Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age
Always - 3
194 Temperature_Celsius 0x0022 157 148 000 Old_age
Always - 27
195 Hardware_ECC_Recovered 0x000a 100 100 000 Old_age
Always - 7356760

Thats normal with samsungs, just information, no indication of a
problem.

196 Reallocated_Event_Count 0x0012 100 100 000 Old_age
Always - 1

That is saying that that has been just one reallocated sector.

Thats fine, nothing to worry about.

197 Current_Pending_Sector 0x0033 253 253 010 Pre-fail
Always - 0
198 Offline_Uncorrectable 0x0031 100 100 010 Pre-fail
Offline - 1

Thats the same single bad sector.

199 UDMA_CRC_Error_Count 0x000b 100 100 051 Pre-fail
Always - 0
200 Multi_Zone_Error_Rate 0x000b 100 100 051 Pre-fail
Always - 0
201 Soft_Read_Error_Rate 0x000b 253 253 051 Pre-fail
Always - 0

SMART Error Log Version: 1
ATA Error Count: 69 (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 69 occurred at disk power-on lifetime: 940 hours (39 days + 4
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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:51.875 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:51.875 SET FEATURES [Set
transfer mode] c6 00 10 01 00 00 a0 00 41d+20:21:51.875 SET
MULTIPLE MODE 00 03 01 01 00 00 a0 00 41d+20:21:51.813 NOP
[Reserved subcommand]

Error 68 occurred at disk power-on lifetime: 940 hours (39 days + 4
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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:46.250 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:46.250 SET FEATURES [Set
transfer mode] c6 00 10 01 00 00 a0 00 41d+20:21:46.250 SET
MULTIPLE MODE 00 03 01 01 00 00 a0 00 41d+20:21:46.250 NOP
[Reserved subcommand]

Error 67 occurred at disk power-on lifetime: 940 hours (39 days + 4
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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:40.688 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:40.688 SET FEATURES [Set
transfer mode] c6 00 10 01 00 00 a0 00 41d+20:21:40.688 SET
MULTIPLE MODE 00 03 01 01 00 00 a0 00 41d+20:21:40.625 NOP
[Reserved subcommand]

Error 66 occurred at disk power-on lifetime: 940 hours (39 days + 4
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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:35.063 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:35.063 SET FEATURES [Set
transfer mode] c6 00 10 01 00 00 a0 00 41d+20:21:35.063 SET
MULTIPLE MODE 00 03 01 01 00 00 a0 00 41d+20:21:35.000 NOP
[Reserved subcommand] ef 03 0c 01 10 00 a0 00 41d+20:21:34.938
SET FEATURES [Set transfer mode]

Error 65 occurred at disk power-on lifetime: 940 hours (39 days + 4
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 7e 8d ea 4a e7 Error: UNC at LBA = 0x074aea8d = 122350221

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 03 7e 8d ea 4a e7 00 41d+20:21:29.313 READ MULTIPLE
ef 03 0c 01 10 00 a0 00 41d+20:21:29.313 SET FEATURES [Set
transfer mode] c6 00 10 01 00 00 a0 00 41d+20:21:29.313 SET
MULTIPLE MODE 00 03 01 01 00 00 a0 00 41d+20:21:29.313 NOP
[Reserved subcommand]

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

Those are the same single bad sector.

Device does not support Selective Self Tests/Logging

 

[void]

Rod,

I will email Samsung, and I will also try to run the DFT in the next few days.

Also, can you tell me if reading or writing to a bad sector will always show
up in the SMART data? So if I don't see any mention of errors in the SMART
data, then I'll know that no data has been read or written to a bad sector?

 

[Arno Wagner]

Rod,

I will email Samsung, and I will also try to run the DFT in the next
few days.

Also, can you tell me if reading or writing to a bad sector will
always show up in the SMART data? So if I don't see any mention of
errors in the SMART data, then I'll know that no data has been read
or written to a bad sector?

It will not. I had one disk (specifically Maxtor) decrease
the SMART defect count to zero after it had defects. Now, it
may have re-tested these sectors, but in my view defects are
defects and should not goo away.

What might work is the error log. The disk keeps the last 4
(or so) errors with description.

Best just run a long SMART self-test and see whether it
completes without error.

Arno

 

[J. Clarke]

It will not. I had one disk (specifically Maxtor) decrease
the SMART defect count to zero after it had defects. Now, it
may have re-tested these sectors, but in my view defects are
defects and should not goo away.

Which "defect count"? That's not one of the standard SMART fields. You
should be looking 0x0033, which is usually the reallocated sectors count.
Also, SMART counters are not always intuitive--some of them start at a high
value and count down. Could be that if it's showing zero it means that all
the available sectors have been remapped.

Also, some drives reset the counters after the first 8 hours or so of
operation.

You also need to obtain the manufacturer's docs--the SMART fields are not
completely standardized.

There's a great deal of useful information at
<http://smartmontools.sourceforge.net/>--follow the "useful references"
link and you'll find actual SMART reports on failing drives, some of them
Maxtor.

 

[Rod Speed]

(e-mail address removed) wrote

I will email Samsung, and I will also try to run the DFT in the next few days.

Also, can you tell me if reading or writing to a bad
sector will always show up in the SMART data?

Well, the bad sector should be visible in the SMART data, either
as a reallocated sector if its been reallocated, or as a pending if
it hasnt yet been reallocated for various reasons or uncorrectable.

The attempt to read or write that sector should
show up in the log that you can see with smartctl.

So if I don't see any mention of errors in the SMART data, then
I'll know that no data has been read or written to a bad sector?

Thats complicated by what has happened with the offline tests.
Those will show the bad sectors that have been discovered by
the offline tests and will end up in the SMART data.

 

[Arno Wagner]

Arno Wagner wrote:

Which "defect count"? That's not one of the standard SMART fields. You
should be looking 0x0033, which is usually the reallocated sectors count.

That is what I meant.

Also, SMART counters are not always intuitive--some of them start at a high
value and count down. Could be that if it's showing zero it means that all
the available sectors have been remapped.

No, I am sure about this one. I have > 20 more of these disks and '0'
is the value they have when they are new. This one increased the
reallocated sector cound and then decreased it again.

Also, some drives reset the counters after the first 8 hours or so of
operation.

This was after some months.

You also need to obtain the manufacturer's docs--the SMART fields are not
completely standardized.

Well, yes. There could be something in that.

There's a great deal of useful information at
<http://smartmontools.sourceforge.net/>--follow the "useful references"
link and you'll find actual SMART reports on failing drives, some of them
Maxtor.

I have seen failing ones myself. And I use the smartmontools for
all smart monitoring. The thing I take exception with is that
Maxtor allows the counter to revert to "perfect" when there clearly
was some problem before.

Arno

 

[void]

Thats complicated by what has happened with the offline tests.
Those will show the bad sectors that have been discovered by
the offline tests and will end up in the SMART data.

Yeah, since the offline test will read the entire disk, then if there are any
bad sectors, they'll definitely show up in the SMART data after running a
test.

The only time a bad sector won't show up in the SMART data is if data has
never been read from or written to it.

I hope I got that right.

 

[Rod Speed]

(e-mail address removed) wrote

Yeah, since the offline test will read the entire disk,
then if there are any bad sectors, they'll definitely
show up in the SMART data after running a test.

With a decent SMART implementation, anyway.

Arno claims to have seen a Maxtor drive reset the bad sector count.

I havent seen that myself, but then I dont use Maxtor drives much.

The only time a bad sector won't show up in the SMART
data is if data has never been read from or written to it.

I hope I got that right.

That's correct.

 

[void]

I emailed Samsung the output from HUTIL and smartctl, and here is their
unhelpful response:


Dear Sir/Madam:

If this drive was purchased separately from your computer system, within the
last three years, it is under warranty. If your drive was preinstalled in a
branded computer, such as a Dell or HP, please contact that company, as they
assume all responsibility for service and support. Otherwise, please use the
attached form to request an RMA from our factory service center. As an
alternative to fax, you can also submit the form by email to
(e-mail address removed). This will set up warranty replacement of the drive
with refurbished stock that carries the remainder of your original warranty.
You may also wish to visit our factory service center web site at
http://www.fesvc.com and sign up for a username and password. Once this is
done, you can make any needed RMA requests online.

 

[Rod Speed]

(e-mail address removed) wrote

I emailed Samsung the output from HUTIL and
smartctl, and here is their unhelpful response:

That's not unhelpful, they are saying the drive is
dying and that it will be replaced under warranty.

 

[void]

(e-mail address removed) wrote


That's not unhelpful, they are saying the drive is
dying and that it will be replaced under warranty.

But I seriously doubt that they took the time to analyze the output from the
two programs. Like you told me to do, I asked them why HUTIL reported
multiple bad sectors, while smartctl only reported one bad sector. They
didn't answer that question.

 

[Rod Speed]

(e-mail address removed) wrote

But I seriously doubt that they took the time
to analyze the output from the two programs.

Likely they just use the HUTIL report and recognised a known problem.

Like you told me to do, I asked them why HUTIL reported
multiple bad sectors, while smartctl only reported one
bad sector. They didn't answer that question.

Sure, but they likely decided it was too hard to explain.

 

[Folkert Rienstra]

Thanks for the informative post, Arno.

Just his usual ranting. Never bothers to check what he rambles out.

 

[Folkert Rienstra]

Hi,

I ran HUTIL on my Samsung SP2014N a couple of weeks ago, and when it
found what it said was a bad sector, I think that the warning msg said
that it would write all zeroes to that sector if I answer 'yes'. I was
right in the middle of a bunch of things, so I don't remember exactly,
but I know that I decided NOT to tell it 'yes'.

Yeah, it obviously is a bad thing to correct a bad sector. Good choice.