Bad Clusters vs. Bad Sectors


A

Ant

Hello!

Am I understanding correctly that these terms are basically the same? If
so, then why did my client's updated Windows 2000 SP4's chkdsk (/r /f
parameters and rebooted to run it) on a HDD (NTFS) in an old Dell
Optiplex system say there was a bad cluster and was able to move a file
to a better place, but I rerun chkdsk in Windows 2000 and ran a chkdsk
(no parameters) and it found 0 KB of bad sector?

Thank you in advance. :)
--
"This is the ant. Treat it with respect. For it may very well be the
next dominant lifeform of our planet." --Empire of the Ants movie
/\___/\
/ /\ /\ \ Phil/Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Nuke ANT from e-mail address: (e-mail address removed)
( ) or (e-mail address removed)
Ant is currently not listening to any songs on his home computer.
 
Ad

Advertisements

B

BillW50

In Ant typed on Sun, 04 Oct 2009 15:15:43 -0700:
Hello!

Am I understanding correctly that these terms are basically the same?
If so, then why did my client's updated Windows 2000 SP4's chkdsk (/r
/f parameters and rebooted to run it) on a HDD (NTFS) in an old Dell
Optiplex system say there was a bad cluster and was able to move a
file to a better place, but I rerun chkdsk in Windows 2000 and ran a
chkdsk (no parameters) and it found 0 KB of bad sector?

Thank you in advance. :)

Once a bad sector/cluster is found and marked as bad, it is no longer
part of the useable part of the drive. And IDE drives internally hides
them from outside sources, like Windows for example. Older MFM drives
didn't have this ability. And brand new hard drives always have had bad
sectors.

And manufactures got tired of people returning hard drives because they
have some bad sectors on them. So under IDE, they now had the ability to
hide them from the outside. Although they can only hide so many. Once
this limit is hit, they will start to show up. Which is rare, unless
something is wrong with the drive.
 
L

loke

InAnt typed on Sun, 04 Oct 2009 15:15:43 -0700:




Once a bad sector/cluster is found and marked as bad, it is no longer
part of the useable part of the drive. And IDE drives internally hides
them from outside sources, like Windows for example. Older MFM drives
didn't have this ability. And brand new hard drives always have had bad
sectors.

And manufactures got tired of people returning hard drives because they
have some bad sectors on them. So under IDE, they now had the ability to
hide them from the outside. Although they can only hide so many. Once
this limit is hit, they will start to show up. Which is rare, unless
something is wrong with the drive.

But if you use SMART, a drive status system built in the modern
drives, you will know the bad sector problems, regardless, which
should give you a good info about the health of the drive as well.
Smartmontools on Linux does this very well.
Loke
 
B

BillW50

In
loke typed on Thu, 8 Oct 2009 09:24:26 -0700 (PDT):
But if you use SMART, a drive status system built in the modern
drives, you will know the bad sector problems, regardless, which
should give you a good info about the health of the drive as well.
Smartmontools on Linux does this very well.
Loke

I use Hard Drive Sentinel which lists all of the SMART info. Nothing
about bad sectors though. Yet all hard drives have them when they are
manufactured. And the SMART info for all of my drives (about 15 of them)
all shows 100%. I also believe it was Google (who has tons of hard
drives) only found that SMART is only reliable for detecting pending
faults only about 60% of the time.
 
Ad

Advertisements

A

Ant

I use Hard Drive Sentinel which lists all of the SMART info. Nothing
about bad sectors though. Yet all hard drives have them when they are
manufactured. And the SMART info for all of my drives (about 15 of them)
all shows 100%. I also believe it was Google (who has tons of hard
drives) only found that SMART is only reliable for detecting pending
faults only about 60% of the time.

Whoops, I forgot about this thread. In
http://groups.google.com/group/comp...d373e/36430ad427d7a4a8?q=ant%40zimage.comANT&
.... I was told that bad clusters were not same as bad sectors. I didn't
see any bad sectors from chkdsk, smartctl, and SpinRite v6.0.

Here are SMART results after I did two chkdsks and a smartctl full test
request:

smartctl version 5.38 [i686-mingw32-2000-sp4] Copyright (C) 2002-8 Bruce
Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family: Maxtor DiamondMax Plus 8 family
Device Model: Maxtor 6E040L0
Serial Number: E155KPHE
Firmware Version: NAR61590
User Capacity: 41,110,142,976 bytes
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: Sun Oct 04 16:43:43 2009 PDT
SMART support is: Available - device has SMART capability.
Enabled status cached by OS, trying SMART RETURN
STATUS cmd.
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: ( 116) The previous self-test completed
having
the read element of the test
failed.
Total time to complete Offline
data collection: (1021) 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.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 17) 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
3 Spin_Up_Time 0x0027 227 221 063 Pre-fail
Always - 5662
4 Start_Stop_Count 0x0032 253 253 000 Old_age
Always - 1252
5 Reallocated_Sector_Ct 0x0033 252 252 063 Pre-fail
Always - 9
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 246 240 187 Pre-fail
Always - 41311
9 Power_On_Minutes 0x0032 242 242 000 Old_age
Always - 865h+43m
10 Spin_Retry_Count 0x002b 253 252 157 Pre-fail
Always - 0
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail
Always - 0
12 Power_Cycle_Count 0x0032 250 250 000 Old_age
Always - 1251
192 Power-Off_Retract_Count 0x0032 252 252 000 Old_age Always
- 1248
193 Load_Cycle_Count 0x0032 253 253 000 Old_age Always
- 2746
194 Temperature_Celsius 0x0032 253 253 000 Old_age Always
- 26
195 Hardware_ECC_Recovered 0x000a 253 252 000 Old_age Always
- 8300
196 Reallocated_Event_Count 0x0008 251 251 000 Old_age
Offline - 2
197 Current_Pending_Sector 0x0008 253 253 000 Old_age
Offline - 2
198 Offline_Uncorrectable 0x0008 251 251 000 Old_age
Offline - 2
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 252 000 Old_age Always
- 8
202 TA_Increase_Count 0x000a 253 251 000 Old_age Always
- 0
203 Run_Out_Cancel 0x000b 253 252 180 Pre-fail Always
- 29
204 Shock_Count_Write_Opern 0x000a 253 251 000 Old_age Always
- 0
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age Always
- 0
207 Spin_High_Current 0x002a 253 252 000 Old_age Always
- 0
208 Spin_Buzz 0x002a 253 252 000 Old_age Always
- 0
209 Offline_Seek_Performnce 0x0024 188 187 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 19 inconsistent with error log pointer 5

ATA Error Count: 19 (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 19 occurred at disk power-on lifetime: 3881 hours (161 days + 17
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
-- -- -- -- -- -- --
40 51 01 83 a2 68 e2 Error: UNC 1 sectors at LBA = 0x0268a283 =
40411779

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 00 01 83 a2 68 e2 00 02:14:10.592 READ DMA
c8 00 01 82 a2 68 e2 00 02:14:10.592 READ DMA
c8 00 01 81 a2 68 e2 00 02:14:10.592 READ DMA
c8 00 01 80 a2 68 e2 00 02:14:10.592 READ DMA
c8 00 01 7f a2 68 e2 00 02:14:10.592 READ DMA

Error 18 occurred at disk power-on lifetime: 3881 hours (161 days + 17
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
-- -- -- -- -- -- --
40 51 06 67 a2 68 e2 Error: UNC 6 sectors at LBA = 0x0268a267 =
40411751

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 00 22 67 a2 68 e2 00 02:14:09.264 READ DMA
c8 00 1e 13 ee 30 e1 00 02:14:09.248 READ DMA
c8 00 1f f1 15 30 e1 00 02:14:09.248 READ DMA
c8 00 1e 2f a8 27 e1 00 02:14:09.232 READ DMA
c8 00 1f da e7 23 e1 00 02:14:09.232 READ DMA

Error 17 occurred at disk power-on lifetime: 3871 hours (161 days + 7 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
-- -- -- -- -- -- --
40 51 06 67 a2 68 e2 Error: UNC 6 sectors at LBA = 0x0268a267 =
40411751

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 00 22 67 a2 68 e2 00 04:55:32.656 READ DMA
c8 00 80 81 02 ab e1 00 04:55:32.656 READ DMA
c8 00 08 09 02 ab e1 00 04:55:32.640 READ DMA
c8 00 1e 13 ee 30 e1 00 04:55:32.640 READ DMA
c8 00 08 c5 a3 11 e1 00 04:55:32.624 READ DMA

Error 16 occurred at disk power-on lifetime: 1858 hours (77 days + 10 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
-- -- -- -- -- -- --
40 51 62 db a5 68 e2 Error: UNC 98 sectors at LBA = 0x0268a5db =
40412635

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 00 67 db a5 68 e2 00 00:49:20.528 READ DMA
c8 00 08 89 ae 65 e0 00 00:49:20.512 READ DMA
c8 00 0f 42 ae 65 e0 00 00:49:20.512 READ DMA
c8 00 02 d6 d4 75 e0 00 00:49:20.512 READ DMA
c8 00 03 f5 78 69 e2 00 00:49:20.512 READ DMA

Error 15 occurred at disk power-on lifetime: 1455 hours (60 days + 15 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
-- -- -- -- -- -- --
40 51 05 a8 fb 13 e0 Error: UNC 5 sectors at LBA = 0x0013fba8 = 1309608

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 00 08 a8 fb 13 e0 00 01:04:55.104 READ DMA
ca 00 08 3c f4 64 e2 00 01:04:55.104 WRITE DMA
c8 00 80 d0 fb 13 e0 00 01:04:55.104 READ DMA
c8 00 08 a8 fb 13 e0 00 01:04:53.968 READ DMA
ca 00 80 03 de 72 e2 00 01:04:53.968 WRITE DMA

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: read failure 40% 3882
49793
# 2 Extended offline Interrupted (host reset) 70% 3881
-
# 3 Short offline Completed without error 00% 0
-

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.
--
"Left right left right we're army ants. We swarm we fight. We have no
home. We roam. We race. You're lucky if we miss your place." --Douglas
Florian (The Army Ants Poem)
/\___/\
/ /\ /\ \ Phil/Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Nuke ANT from e-mail address: (e-mail address removed)
( ) or (e-mail address removed)
Ant is currently not listening to any songs on his home computer.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top