Hard Drive Screeches 4 times on Windows 2000

F

Folkert Rienstra

That that is one very sick drive.
Click to expand...

Ignore the mindless doom sayers.
It actually only has 2 uncorrectable read error bad sectors.
Run Drive Fitness Test and the drive will likely be fine.
If by chance they are in the partition structures and DFT refuses
to fix it then kill that partition or change the type to something DFT
doesn't understand.
Then it will happily fix any remaining bad sectors still and you can
set it back to original again.
Even removing the bad partition and setting it up again may well
fix it already.

I'd bin it if it was mine, its one of the notorious DeathStars
thats in its death throws.
Click to expand...

Not with only 2 bad sectors it isn't.
Checking power supply, cabling and fans is all that may be needed.
The Everest report is a lot more readable, can you do one easily ?
http://www.majorgeeks.com/download.php?det=4181
Click to expand...
More interleaved below.
Click to expand...

Mindless drivel you mean. Didn't even bother to check the report.

Report's original formatting restored.
=== START OF INFORMATION SECTION ===
Device Model: IBM-DTLA-307015
Click to expand...

Urk, thats one of the infamous IBM 75GXP drives that generated a
full class action suit because the failure rate was so utterly obscene.

They werent called DeathStars for nothing.
Serial Number: YF0YFT06663
Firmware Version: TX2OA50C
Device is: In smartctl database [for details use: -P show]
ATA Version is: 5
ATA Standard is: ATA/ATAPI-5 T13 1321D revision 1
Local Time is: Thu Nov 16 06:04:20 2006 GMT

==> WARNING: IBM Deskstar 40GV and 75GXP drives may need upgraded SMART firmware.
Please see http://www.geocities.com/dtla_update/

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:
Off-line data collection status: (0x00) Offline data collection activity was never started.
Auto Off-line Data Collection: Disabled.
Self-test execution status: ( 118) The previous self-test completed having the read element of the test failed.
Total time to complete off-line data collection: (1231) seconds.
Offline data collection capabilities: (0x1b) SMART execute Offline immediate.
Automatic timer 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: ( 2) minutes.
Extended self-test routine recommended polling time: ( 10) 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 060 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0007 215 215 024 Pre-fail Always - 69 (Average 70)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 3160
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 3
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 020 Pre-fail Offline - 0
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 3825
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 3155
192 Power-Off_Retract_Count 0x0032 098 098 050 Old_age Always - 3160
193 Load_Cycle_Count 0x0012 098 098 050 Old_age Always - 3160
194 Temperature_Celsius 0x0002 103 103 000 Old_age Always - 53
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 3
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 2
Click to expand...
Click to expand...

A lousy 2 bad sectors that may not even be physically bad.
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0

SMART Error Log Version: 1
ATA Error Count: 330 (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]
Timestamp = decimal seconds since the previous disk power-on.
Note: timestamp "wraps" after 2^32 msec = 49.710 days.

Error 330 occurred at disk power-on lifetime: 3823 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 01 4f d6 e6 f0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Timestamp Command/Feature_Name
-- -- -- -- -- -- -- -- --------- --------------------
c8 00 01 4f d6 e6 f0 00 8886.600 READ DMA
c8 00 07 50 d6 e6 f0 00 8886.600 READ DMA
c8 00 08 4f d6 e6 f0 00 8881.300 READ DMA
c8 00 08 47 d6 e6 f0 00 8881.300 READ DMA
c8 00 08 3f d6 e6 f0 00 8881.300 READ DMA

Error 329 occurred at disk power-on lifetime: 3823 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 08 4f d6 e6 f0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Timestamp Command/Feature_Name
-- -- -- -- -- -- -- -- --------- --------------------
c8 00 08 4f d6 e6 f0 00 8881.300 READ DMA
c8 00 08 47 d6 e6 f0 00 8881.300 READ DMA
c8 00 08 3f d6 e6 f0 00 8881.300 READ DMA
c8 00 08 37 d6 e6 f0 00 8881.300 READ DMA
c8 00 08 2f d6 e6 f0 00 8881.300 READ DMA

Error 328 occurred at disk power-on lifetime: 3823 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 08 4f d6 e6 f0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Timestamp Command/Feature_Name
-- -- -- -- -- -- -- -- --------- --------------------
20 00 08 4f d6 e6 f0 00 8312.400 READ SECTOR(S)
20 00 08 47 d6 e6 f0 00 8312.400 READ SECTOR(S)
20 00 08 3f d6 e6 f0 00 8312.400 READ SECTOR(S)
20 00 08 37 d6 e6 f0 00 8312.400 READ SECTOR(S)
20 00 08 2f d6 e6 f0 00 8312.400 READ SECTOR(S)

Error 327 occurred at disk power-on lifetime: 3823 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 08 4f d6 e6 f0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Timestamp Command/Feature_Name
-- -- -- -- -- -- -- -- --------- --------------------
20 00 08 4f d6 e6 f0 00 8304.100 READ SECTOR(S)
20 00 08 47 d6 e6 f0 00 8304.100 READ SECTOR(S)
20 00 08 3f d6 e6 f0 00 8304.100 READ SECTOR(S)
20 00 08 37 d6 e6 f0 00 8304.100 READ SECTOR(S)
20 00 08 2f d6 e6 f0 00 8304.100 READ SECTOR(S)

Error 326 occurred at disk power-on lifetime: 3823 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 08 4f d6 e6 f0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Timestamp Command/Feature_Name
-- -- -- -- -- -- -- -- --------- --------------------
20 00 08 4f d6 e6 f0 00 8295.700 READ SECTOR(S)
20 00 08 47 d6 e6 f0 00 8295.700 READ SECTOR(S)
20 00 08 3f d6 e6 f0 00 8295.700 READ SECTOR(S)
20 00 08 37 d6 e6 f0 00 8295.700 READ SECTOR(S)
20 00 08 2f d6 e6 f0 00 8295.700 READ SECTOR(S)

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended off-line Completed: read failure 60% 3825 0x00e50608
# 2 Extended off-line Completed: read failure 60% 3825 0x00e50608
# 3 Short off-line Completed without error 00% 3825 -
# 4 Short off-line Completed without error 00% 3825 -
# 5 Short off-line Completed without error 00% 3825 -
Click to expand...
Click to expand...
 
O

Olumide

Okay lads, I'm shopping for a portable drive to back up my data to.
Someone suggests that I try a Lacie or a Formac? Which is more
reliable? Are there any perticular models I should avoid? ...
Recomendations would also be welcome.

Thanks
 
O

Olumide

Olumide said:
Okay lads, I'm shopping for a portable drive to back up my data to.
Someone suggests that I try a Lacie or a Formac? Which is more
reliable? Are there any perticular models I should avoid? ...
Recomendations would also be welcome.
Click to expand...

I just hope those drives work on/with Linux ...
 
R

Rod Speed

Folkert Rienstra said:
Ignore the mindless doom sayers.
It actually only has 2 uncorrectable read error bad sectors.
Run Drive Fitness Test and the drive will likely be fine.
Click to expand...

Not for long with a 75GXP, ****wit child.
If by chance they are in the partition structures and DFT refuses
to fix it then kill that partition or change the type to something DFT
doesn't understand.
Then it will happily fix any remaining bad sectors still and you can
set it back to original again.
Even removing the bad partition and setting it up again may well
fix it already.
Click to expand...
Not with only 2 bad sectors it isn't.
Checking power supply, cabling and fans is all that may be needed.
Click to expand...

Not a ****ing clue, as always.
Mindless drivel you mean. Didn't even bother to check the report.
Click to expand...

Guess which pathetic little pig ignorant prat has
just got egg all over its pathetic little face, as always.
Report's original formatting restored.
Click to expand...

You dont know that he can ever read it in that format.
=== START OF INFORMATION SECTION ===
Device Model: IBM-DTLA-307015
Click to expand...

Urk, thats one of the infamous IBM 75GXP drives that generated a
full class action suit because the failure rate was so utterly
obscene.

They werent called DeathStars for nothing.
Serial Number: YF0YFT06663
Firmware Version: TX2OA50C
Device is: In smartctl database [for details use: -P show]
ATA Version is: 5
ATA Standard is: ATA/ATAPI-5 T13 1321D revision 1
Local Time is: Thu Nov 16 06:04:20 2006 GMT

==> WARNING: IBM Deskstar 40GV and 75GXP drives may need upgraded
SMART firmware.
Please see http://www.geocities.com/dtla_update/

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:
Off-line data collection status: (0x00) Offline data collection
activity was never started.
Auto Off-line Data Collection: Disabled.
Self-test execution status: ( 118) The previous self-test
completed having the read element of the test failed. Total time to
complete off-line data collection: (1231) seconds.
Offline data collection capabilities: (0x1b) SMART execute Offline
immediate.
Automatic timer 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: ( 2) minutes.
Extended self-test routine recommended polling time: ( 10) 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 060 Pre-fail Always - 0 2
Throughput_Performance 0x0005 100 100 050 Pre-fail
Offline - 0 3 Spin_Up_Time 0x0007 215
215 024 Pre-fail Always - 69 (Average 70) 4
Start_Stop_Count 0x0012 100 100 000 Old_age Always
- 3160 5 Reallocated_Sector_Ct 0x0033 100 100 005
Pre-fail Always - 3 7 Seek_Error_Rate 0x000b
100 100 067 Pre-fail Always - 0 8
Seek_Time_Performance 0x0005 100 100 020 Pre-fail
Offline - 0 9 Power_On_Hours 0x0012 100 100
000 Old_age Always - 3825 10 Spin_Retry_Count
0x0013 100 100 060 Pre-fail Always - 0 12
Power_Cycle_Count 0x0032 100 100 000 Old_age Always
- 3155 192 Power-Off_Retract_Count 0x0032 098 098 050
Old_age Always - 3160 193 Load_Cycle_Count
0x0012 098 098 050 Old_age Always - 3160 194
Temperature_Celsius 0x0002 103 103 000 Old_age Always
- 53 196 Reallocated_Event_Count 0x0032 100 100 000
Old_age Always - 3
197 Current_Pending_Sector 0x0022 100 100 000 Old_age
Always - 2
Click to expand...
Click to expand...
Click to expand...
A lousy 2 bad sectors that may not even be physically bad.
Click to expand...

Pity about the reallocated sectors, ****wit child.
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age
Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200
200 000 Old_age Always - 0

SMART Error Log Version: 1
ATA Error Count: 330 (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]
Timestamp = decimal seconds since the previous disk power-on.
Note: timestamp "wraps" after 2^32 msec = 49.710 days.

Error 330 occurred at disk power-on lifetime: 3823 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 01 4f d6 e6 f0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Timestamp Command/Feature_Name
-- -- -- -- -- -- -- -- --------- --------------------
c8 00 01 4f d6 e6 f0 00 8886.600 READ DMA
c8 00 07 50 d6 e6 f0 00 8886.600 READ DMA
c8 00 08 4f d6 e6 f0 00 8881.300 READ DMA
c8 00 08 47 d6 e6 f0 00 8881.300 READ DMA
c8 00 08 3f d6 e6 f0 00 8881.300 READ DMA

Error 329 occurred at disk power-on lifetime: 3823 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 08 4f d6 e6 f0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Timestamp Command/Feature_Name
-- -- -- -- -- -- -- -- --------- --------------------
c8 00 08 4f d6 e6 f0 00 8881.300 READ DMA
c8 00 08 47 d6 e6 f0 00 8881.300 READ DMA
c8 00 08 3f d6 e6 f0 00 8881.300 READ DMA
c8 00 08 37 d6 e6 f0 00 8881.300 READ DMA
c8 00 08 2f d6 e6 f0 00 8881.300 READ DMA

Error 328 occurred at disk power-on lifetime: 3823 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 08 4f d6 e6 f0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Timestamp Command/Feature_Name
-- -- -- -- -- -- -- -- --------- --------------------
20 00 08 4f d6 e6 f0 00 8312.400 READ SECTOR(S)
20 00 08 47 d6 e6 f0 00 8312.400 READ SECTOR(S)
20 00 08 3f d6 e6 f0 00 8312.400 READ SECTOR(S)
20 00 08 37 d6 e6 f0 00 8312.400 READ SECTOR(S)
20 00 08 2f d6 e6 f0 00 8312.400 READ SECTOR(S)

Error 327 occurred at disk power-on lifetime: 3823 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 08 4f d6 e6 f0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Timestamp Command/Feature_Name
-- -- -- -- -- -- -- -- --------- --------------------
20 00 08 4f d6 e6 f0 00 8304.100 READ SECTOR(S)
20 00 08 47 d6 e6 f0 00 8304.100 READ SECTOR(S)
20 00 08 3f d6 e6 f0 00 8304.100 READ SECTOR(S)
20 00 08 37 d6 e6 f0 00 8304.100 READ SECTOR(S)
20 00 08 2f d6 e6 f0 00 8304.100 READ SECTOR(S)

Error 326 occurred at disk power-on lifetime: 3823 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 08 4f d6 e6 f0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Timestamp Command/Feature_Name
-- -- -- -- -- -- -- -- --------- --------------------
20 00 08 4f d6 e6 f0 00 8295.700 READ SECTOR(S)
20 00 08 47 d6 e6 f0 00 8295.700 READ SECTOR(S)
20 00 08 3f d6 e6 f0 00 8295.700 READ SECTOR(S)
20 00 08 37 d6 e6 f0 00 8295.700 READ SECTOR(S)
20 00 08 2f d6 e6 f0 00 8295.700 READ SECTOR(S)

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error # 1 Extended off-line
Completed: read failure 60% 3825 0x00e50608 # 2
Extended off-line Completed: read failure 60% 3825
0x00e50608 # 3 Short off-line Completed without error
00% 3825 - # 4 Short off-line Completed without
error 00% 3825 - # 5 Short off-line Completed
without error 00% 3825 -
Click to expand...
Click to expand...
Click to expand...
 
R

Rod Speed

Olumide said:
Okay lads, I'm shopping for a portable drive to back up my data to.
Someone suggests that I try a Lacie or a Formac? Which is more
reliable? Are there any perticular models I should avoid? ...
Click to expand...

The maxtors and any that dont move significant volumes of air over the drive.
Recomendations would also be welcome.
Click to expand...

I prefer to buy a decent box and put a normal drive in it, so you
get the full 3-5 year warranty on the drive, not the pathetic 1 year
warranty you get with all assembled portable drives.
 
P

paulmd

Olumide said:
Hello -

I think my one of my two NTFS partitions may be going crazy. The
trouble started a few hours ago, when I switched on my PC, and to my
amazement, as Windows 2000 washalfway booting, a my machine (one of the
hard drives I suspect) began to make a series of screech sounds (4 in
number), then pause for 1 or 2 seconds then screech again for 4 times
etc -- very annoying. But the worst part is that after taking an
eternity to boot up, screeches abounding still, explorer reported that
my E drive (NTFS partition) was unformatted, although the disk
management utility (Administrative Tools :: Computer Management)
reported all drives healthy. Also, the machine seems slower. I've tried
going into safe mode, with the hope of scaning the disks for errors but
the defragmenter doesn't even list the E drive so there's no way to
scan it.

Here's the lone bit of good news, fortunately, I can mount the dodgy
partition on Linux (after thats after just one set of screeches :-D ),
and I've copied important files to the Linux partition (phew).

Now I'd like to fix this problem, preferably without having to reformat
my E drive -- that'll be my last resort. What could be wrong with this
partition? Has anyone had this problem?
Click to expand...

Good you don't have to reformat the partition.

Bad You DO have to replace the drive.
 
P

paulmd

Folkert said:
Ignore the mindless doom sayers.
It actually only has 2 uncorrectable read error bad sectors.
Click to expand...

SHIT! Every attribute is either pre_fail or old_age! What are you
smoking?

Replace the drive while there's time to clone it and save the data.
 

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

Similar Threads

PC not recognising new external hard drive 14
Defrag on hard drives with mutiple file systems 2
ReiserFS Linux Native Partition to NTFS/FAT32 Conversion 1
Linux Windows dual boot not restoring properly 8
USB Hard Drive Issue 2
WindowsXP on E: Drive / Windows 7 on C: Drive. I want Linux toreplace Win7? 1
Drive errors for Sata 6.0 drive with Sata 3.0 hard disk controller 5
Putting a WD2500JB IDE on my XP PC 16

Top