Hard Drive Screeches 4 times on Windows 2000


O

Olumide

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?

Thanks,

- Olumide
 
Ad

Advertisements

R

Rod Speed

Olumide said:
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.

Almost certainly the hard drive is recalibrating when it cant read some sectors properly.
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,

Because it cant read the directory structures properly due to the bad sectors.
although the disk management utility (Administrative Tools :: Computer
Management) reported all drives healthy. Also, the machine seems slower.

Because its retrying on marginal bad sectors.
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,

Replace the hard drive.
preferably without having to reformat my E drive -- that'll be my last resort.

Its normally only a short term fix with bad sectors.
What could be wrong with this partition?

Bad sectors. Post the Everest SMART report, or the smartctl report from linux.
Has anyone had this problem?

Yep, heaps have.
 
O

Olumide

Rod said:
Bad sectors. Post the Everest SMART report, or the smartctl report from linux.

Thanks Rod. Here's the output of: smartctl -a /dev/hdb1.
(What do you make of all this?)

------------------------------------------------------------------------------------------------------------------

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

=== START OF INFORMATION SECTION ===
Device Model: IBM-DTLA-307015
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
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
-
 
J

JAD

Olumide said:
linux.

Thanks Rod. Here's the output of: smartctl -a /dev/hdb1.
(What do you make of all this?)

try this for a longer test
smartctl -t long /dev/hda

Is this an IDE drive?/ try changing channels and/or ribbons


-------------------------------------------------------------------------- ----------------------------------------

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

=== START OF INFORMATION SECTION ===
Device Model: IBM-DTLA-307015
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
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
-
 
O

OSbandito

I know Dell has had problems with bad bearings in some of its IBM-made
laptop HD's. The bad bearings cause both noise and erratic behavior.
Also, the larger Deskstar drives have had major issues. The line was
purchased by Hitachi from IBM. I'd probably pickup one of the small
portable HD's like the one make by Western Digital, connected via USB2
and run the sys off that for awhile to see how things go before deciding
what to do about the main drive.
 
V

VideoReDo Sucks

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?

Thanks,

- Olumide

Complete and irrevocable failure of that drive is imminent.
Turn the computer off and leave it off until you have a replacement drive.
Use the replacement drive manufacturers "clone" program to clone the failing
drive.
With any degree of luck you might be ale to save your Windows installation
and data.
 
Ad

Advertisements

A

Arno Wagner

In comp.sys.ibm.pc.hardware.storage Olumide said:
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).

You are not save if the data is on the same disk only.
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?

I think nothing is wrong with the pattition. But there seems to be
something very wrong with the disk. It may be dying. My advice
would be to update your backup immediately and stop using that
disk.

Arno
 
O

Olumide

JAD said:
try this for a longer test
smartctl -t long /dev/hda

What? ... Even if its /dev/hdb1 that's supposedly malfunctioning?
Is this an IDE drive?/ try changing channels and/or ribbons

Erm ... I suppose it is, at least I'm sure its not SCSI. Channels,
ribbons? ... I've never done that before, oh well there's always a
first time. *Wonders to himself* ... Just how do I go about doing that?
 
O

Olumide

OSbandito said:
.... I'd probably pickup one of the small
portable HD's like the one make by Western Digital, connected via USB2
and run the sys off that for awhile to see how things go before deciding
what to do about the main drive.

Good advise, thanks ;-)
 
J

JAD

Olumide said:
What? ... Even if its /dev/hdb1 that's supposedly malfunctioning?

of course drop the correct hd/position name where it
belongs....................

Erm ... I suppose it is, at least I'm sure its not SCSI. Channels,
ribbons? ... I've never done that before, oh well there's always a
first time. *Wonders to himself* ... Just how do I go about doing that?


find a techi friend...your in trouble here. It involves opening the case and
moving/checking the ribbon cables that connect the hard drives to the main
board. assuming its IDE.
 
O

Olumide

Thanks guys (and girls :) ), keep the advise coming. I'll try to get a
portable drive as soon as I can.
 
Ad

Advertisements

J

John Doe

The obsessed troll JAD as usual acting like a technical sloth,
even when the information is right in front of his nose.


Path: newssvr12.news.prodigy.com!newsdbm05.news.prodigy.com!newsdst01.news.prodigy.net!prodigy.com!newscon04.news.prodigy.net!prodigy.net!newshub.sdsu.edu!hwmnpeer01.lga!news.highwinds-media.com!hw-filter.lga!newsfe04.lga.POSTED!53ab2750!not-for-mail
From: "JAD" <JOHN DOE PORN_ ADDY_ HARVESTER.com>
Newsgroups: microsoft.public.win2000.hardware,comp.sys.ibm.pc.hardware.storage,alt.comp.hardware.pc-homebuilt,comp.sys.ibm.pc.hardware.systems
References: <1163651669.243098.255980 f16g2000cwb.googlegroups.com> <4s28htFtk7f4U1 mid.individual.net> <1163657318.543405.37600 i42g2000cwa.googlegroups.com>
Subject: Re: Hard Drive Screeches 4 times on Windows 2000
Lines: 234
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Message-ID: <yKT6h.335$895.300 newsfe04.lga>
X-Trace: noffecneefnkbhgfkannfilpcpbbolnmaaiklanikhajadjblnijfcjfbjnkioleldkkkpefgplocfkpcllbgmnhjmclmeaakenjmjidaleobfiajejgakbegefbihepenfnojecgjgcfcij
NNTP-Posting-Date: Wed, 15 Nov 2006 23:41:34 MST
Date: Wed, 15 Nov 2006 22:41:32 -0800
Xref: prodigy.net microsoft.public.win2000.hardware:94264 comp.sys.ibm.pc.hardware.storage:378023 alt.comp.hardware.pc-homebuilt:478949 comp.sys.ibm.pc.hardware.systems:108144


Here's the output of: smartctl -a /dev/hdb1

try this for a longer test
smartctl -t long /dev/hda
 
R

Rod Speed

JAD said:
of course drop the correct hd/position name where it
belongs....................




find a techi friend...your in trouble here. It involves opening the
case and moving/checking the ribbon cables that connect the hard
drives to the main board. assuming its IDE.

The real problem is that its an IBM 75GXPs what got the name DeathStar for a reason.
 
R

Rod Speed

Olumide said:
Rod Speed wrote
Thanks Rod. Here's the output of: smartctl -a /dev/hdb1.
(What do you make of all this?)

That that is one very sick drive. I'd bin it if it was mine, its
one of the notorious DeathStars thats in its death throws.

The Everest report is a lot more readable, can you do one easily ?
http://www.majorgeeks.com/download.php?det=4181

More interleaved below.
------------------------------------------------------------------------------------------------------------------

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

=== START OF INFORMATION SECTION ===
Device Model: IBM-DTLA-307015

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
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
-
 
Ad

Advertisements

R

RussellS

Olumide said:
Thanks guys (and girls :) ), keep the advise coming. I'll try to get a
portable drive as soon as I can.

---------------------------------------------------------------
If you value any remaining salvagable data on either partition, turn your
computer off and leave it off until a replacement hard drive is installed.
The bearing could be bad, a platter may be damaged and/or the spindle could
be bad, scraping any data away from your drive platters every time the disk
is powered. Once a new drive is installed, you can partition/format/install
OS and drivers, than hook up your bad drive as a slave or on a separate
cable and attempt to pull any remaing data from it onto the replacement
drive, then power off your system and trash the bad drive. You could try
cloning the bad drive and restorng the clone to the replacement drive
instead of a clean install, but likely will not be successful.

Russell
http://tastycomputers.com
 
Ad

Advertisements


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