[gentoo-user] Does this drive need a funeral?

[gentoo-user] Does this drive need a funeral?

[Dale]

Hi,

For the first time in my life, I think I have a drive failing on me.  
Here is the info:

root@smoker / # smartctl -a /dev/sdc
smartctl 5.40 2010-10-16 r3189 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar family
Device Model:     WDC WD800BB-00DKA0
Serial Number:    WD-WCAHL2497094
Firmware Version: 77.07W77
User Capacity:    80,026,361,856 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   6
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Tue Nov  1 13:52:49 2011 CDT
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: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
See vendor-specific Attribute list for failed Attributes.

General SMART Values:
Offline data collection status:  (0x85) Offline data collection activity
                                         was aborted by an interrupting 
command from host.
                                         Auto Offline Data Collection: 
Enabled.
Self-test execution status:      (  73) The previous self-test completed 
having
                                         a test element that failed and 
the test
                                         element that failed is not known.
Total time to complete Offline
data collection:                 (2478) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                         Auto Offline data collection 
on/off support.
                                         Suspend Offline collection upon new
                                         command.
                                         Offline surface scan supported.
                                         Self-test supported.
                                         Conveyance Self-test supported.
                                         Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                         power-saving mode.
                                         Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                         No General Purpose Logging support.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        (  38) minutes.
Conveyance self-test routine
recommended polling time:        (   5) 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   018   001   051    Pre-fail  
Always   FAILING_NOW 1904
   3 Spin_Up_Time            0x0007   087   084   021    Pre-fail  
Always       -       2166
   4 Start_Stop_Count        0x0032   099   099   040    Old_age   
Always       -       1288
   5 Reallocated_Sector_Ct   0x0033   199   199   140    Pre-fail  
Always       -       1
   7 Seek_Error_Rate         0x000b   200   200   051    Pre-fail  
Always       -       0
   9 Power_On_Hours          0x0032   023   023   000    Old_age   
Always       -       56466
  10 Spin_Retry_Count        0x0013   100   100   051    Pre-fail  
Always       -       0
  11 Calibration_Retry_Count 0x0013   100   100   051    Pre-fail  
Always       -       0
  12 Power_Cycle_Count       0x0032   099   099   000    Old_age   
Always       -       1039
194 Temperature_Celsius     0x0022   110   253   000    Old_age   
Always       -       33
196 Reallocated_Event_Count 0x0032   199   199   000    Old_age   
Always       -       1
197 Current_Pending_Sector  0x0012   199   199   000    Old_age   
Always       -       17
198 Offline_Uncorrectable   0x0012   200   200   000    Old_age   
Always       -       10
199 UDMA_CRC_Error_Count    0x000a   200   253   000    Old_age   
Always       -       1155
200 Multi_Zone_Error_Rate   0x0009   195   085   051    Pre-fail  
Offline      -       191

SMART Error Log Version: 1
ATA Error Count: 4449 (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 4449 occurred at disk power-on lifetime: 759 hours (31 days + 15 
hours)
   When the command that caused the error occurred, the device was doing 
SMART Offline or Self-test.

   After command completion occurred, registers were:
   ER ST SC SN CL CH DH
   -- -- -- -- -- -- --
   40 51 08 a7 73 a8 f4

   Commands leading to the command that caused the error were:
   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
   -- -- -- -- -- -- -- --  ----------------  --------------------
   01 00 c8 00 00 08 00 00      01:47:13.550  [RESERVED]
   00 00 00 00 00 00 00 00      01:47:13.550  NOP [Abort queued commands]
   01 00 ef 00 00 45 00 00      01:47:13.550  [RESERVED]
   00 00 00 00 00 00 00 00      01:47:13.550  NOP [Abort queued commands]
   01 00 c8 00 00 08 00 00      01:47:13.550  [RESERVED]

Error 4448 occurred at disk power-on lifetime: 759 hours (31 days + 15 
hours)
   When the command that caused the error occurred, the device was doing 
SMART Offline or Self-test.

   After command completion occurred, registers were:
   ER ST SC SN CL CH DH
   -- -- -- -- -- -- --
   40 51 08 a7 73 a8 f4

   Commands leading to the command that caused the error were:
   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
   -- -- -- -- -- -- -- --  ----------------  --------------------
   01 00 c8 00 00 08 00 00      01:47:11.550  [RESERVED]
   00 00 00 00 00 00 00 00      01:47:11.550  NOP [Abort queued commands]
   01 00 ef 00 00 45 00 00      01:47:11.550  [RESERVED]
   01 00 27 00 00 00 00 00      01:47:11.550  [RESERVED]
   04 00 a8 00 00 a7 73 00      01:47:11.550  [RESERVED]

Error 4447 occurred at disk power-on lifetime: 759 hours (31 days + 15 
hours)
   When the command that caused the error occurred, the device was doing 
SMART Offline or Self-test.

   After command completion occurred, registers were:
   ER ST SC SN CL CH DH
   -- -- -- -- -- -- --
   40 51 08 a7 73 a8 f4

   Commands leading to the command that caused the error were:
   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
   -- -- -- -- -- -- -- --  ----------------  --------------------
   01 00 c8 00 00 08 00 00      01:47:09.500  [RESERVED]
   00 00 00 00 00 00 00 00      01:47:09.500  NOP [Abort queued commands]
   01 00 ef 00 00 45 00 00      01:47:09.500  [RESERVED]
   00 00 00 00 00 00 00 00      01:47:09.500  NOP [Abort queued commands]
   01 00 c8 00 00 08 00 00      01:47:09.500  [RESERVED]

Error 4446 occurred at disk power-on lifetime: 759 hours (31 days + 15 
hours)
   When the command that caused the error occurred, the device was doing 
SMART Offline or Self-test.

   After command completion occurred, registers were:
   ER ST SC SN CL CH DH
   -- -- -- -- -- -- --
   40 51 08 a7 73 a8 f4

   Commands leading to the command that caused the error were:
   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
   -- -- -- -- -- -- -- --  ----------------  --------------------
   01 00 c8 00 00 08 00 00      01:47:07.550  [RESERVED]
   01 00 ec 00 00 00 00 00      01:47:07.550  [RESERVED]
   00 00 00 00 00 00 00 00      01:47:07.550  NOP [Abort queued commands]
   01 00 ec 00 00 00 00 00      01:47:07.550  [RESERVED]
   00 00 00 00 00 00 00 00      01:47:07.550  NOP [Abort queued commands]

Error 4445 occurred at disk power-on lifetime: 759 hours (31 days + 15 
hours)
   When the command that caused the error occurred, the device was doing 
SMART Offline or Self-test.

   After command completion occurred, registers were:
   ER ST SC SN CL CH DH
   -- -- -- -- -- -- --
   40 51 08 a7 73 a8 f4

   Commands leading to the command that caused the error were:
   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
   -- -- -- -- -- -- -- --  ----------------  --------------------
   01 00 c8 00 00 08 00 00      01:47:05.600  [RESERVED]
   00 00 00 00 00 00 00 00      01:47:05.600  NOP [Abort queued commands]
   01 00 ef 00 00 45 00 00      01:47:05.600  [RESERVED]
   00 00 00 00 00 00 00 00      01:47:05.600  NOP [Abort queued commands]
   01 00 c8 00 00 08 00 00      01:47:05.600  [RESERVED]

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  
LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: unknown failure    90%       
760         4294705476
# 2  Extended offline    Completed: unknown failure    90%       
759         4294705476
# 3  Extended offline    Completed: unknown failure    90%       
759         4294705476
# 4  Extended offline    Completed without error       00%      
1038         -
# 5  Short offline       Completed without error       00%      
1037         -
# 6  Extended offline    Completed without error       00%      
1075         -
# 7  Extended offline    Completed without error       00%       
305         -
# 8  Extended offline    Completed without error       00%       
660         -
# 9  Extended offline    Completed without error       00%       
213         -
#10  Extended offline    Completed without error       00%       
687         -
#11  Extended offline    Completed without error       00%       
686         -
#12  Extended offline    Completed without error       00%       
629         -

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.

root@smoker / #

What you folks think?  Can I fix it somehow?  I got a good shovel handy 
just in case.

Dale

:-)  :-)

Re: [gentoo-user] Does this drive need a funeral?

[Mark Knecht]

On Tue, Nov 1, 2011 at 11:58 AM, Dale <rdalek1967@gmail.com> wrote:
> Hi,
>
> For the first time in my life, I think I have a drive failing on me.  Here
> is the info:
>
<SNIP>
>
> What you folks think?  Can I fix it somehow?  I got a good shovel handy just
> in case.
>
> Dale

Start doing backups before you write even 1 more email! ;;-)

- Mark

Re: [gentoo-user] Does this drive need a funeral?

[Dale]

Mark Knecht wrote:
> On Tue, Nov 1, 2011 at 11:58 AM, Dale<rdalek1967@gmail.com>  wrote:
>> Hi,
>>
>> For the first time in my life, I think I have a drive failing on me.  Here
>> is the info:
>>
> <SNIP>
>> What you folks think?  Can I fix it somehow?  I got a good shovel handy just
>> in case.
>>
>> Dale
> Start doing backups before you write even 1 more email! ;;-)
>
> - Mark
>
>


Well, it was in my brothers winders rig.  Winders couldn't do anything 
but puke on the keyboard so I brought it down here and put it in my old 
Linux rig.  I mounted it ro and got the data off it FIRST THING.  There 
was a boatload of pictures from their camera.  Anyway, the data seems to 
be safe tho a few may have gotten messed up.  I got to test that in a bit.

Is this terminal or can something be done to correct this?  I did run 
the dd command before I ran the selftest.  I don't think it matters but 
thought it wouldn't hurt either.  If it is terminal, I'll get my 
screwdriver out and see what these drives look like on the inside.  The 
last one I looked into was a old 14" thing many years ago.  Platters 
were about the size of 33 rpm records. lol  Dang I'm old.  O_O

Dale

:-)  :-)

Re: [gentoo-user] Does this drive need a funeral?

[Michael Mol]

On Tue, Nov 1, 2011 at 3:47 PM, Dale <rdalek1967@gmail.com> wrote:
> Mark Knecht wrote:
>> On Tue, Nov 1, 2011 at 11:58 AM, Dale<rdalek1967@gmail.com>  wrote:
> Well, it was in my brothers winders rig.  Winders couldn't do anything but
> puke on the keyboard so I brought it down here and put it in my old Linux
> rig.  I mounted it ro and got the data off it FIRST THING.  There was a
> boatload of pictures from their camera.  Anyway, the data seems to be safe
> tho a few may have gotten messed up.  I got to test that in a bit.
>
> Is this terminal or can something be done to correct this?  I did run the dd
> command before I ran the selftest.

Normally, you can extract a little more life out of the drive, but
it's on its last legs. At work, I was once stuck using a drive that
failed on me three times. Each time, it happened to be in the
hibernate.sys file, which meant the machine didn't wake up properly
each time the drive glitched. I was on that drive a few months before
it was finally replaced.

The trouble with that approach, though, is that you don't know when
the drive is going to glitch out, and it's more difficult to diagnose
other issues when it might be a strangely-corrupted file somewhere.

>  I don't think it matters but thought it
> wouldn't hurt either.  If it is terminal, I'll get my screwdriver out and
> see what these drives look like on the inside.  The last one I looked into
> was a old 14" thing many years ago.  Platters were about the size of 33 rpm
> records. lol  Dang I'm old.  O_O

I'm partial to percussive data destruction, myself. The steel platters
will even stop .45 ACP, but they don't stop any rifle round I've
tried. If you want to see what they look like, just look online. If
you want the magnets, I highly recommend K&J Magnetics.[1] I've done a
variety of fun craft projects with them.[2] :)

[1] http://www.kjmagnetics.com/Default.asp
[2] http://www.flickr.com/photos/28208534@N07/sets/72157620071707617/

-- 
:wq

Re: [gentoo-user] Does this drive need a funeral?

[Joost Roeleveld]

On Tuesday, November 01, 2011 02:47:27 PM Dale wrote:
> Mark Knecht wrote:
> > On Tue, Nov 1, 2011 at 11:58 AM, Dale<rdalek1967@gmail.com>  wrote:
> >> Hi,
> >> 
> >> For the first time in my life, I think I have a drive failing on me. 
> >> Here> 
> >> is the info:
> > <SNIP>
> > 
> >> What you folks think?  Can I fix it somehow?  I got a good shovel
> >> handy just in case.
> >> 
> >> Dale
> > 
> > Start doing backups before you write even 1 more email! ;;-)
> > 
> > - Mark
> 
> Well, it was in my brothers winders rig.  Winders couldn't do anything
> but puke on the keyboard so I brought it down here and put it in my old
> Linux rig.  I mounted it ro and got the data off it FIRST THING.

Good idea...
MS Windows has a tendency not to be able to handle failing disks...

> There
> was a boatload of pictures from their camera.  Anyway, the data seems to
> be safe tho a few may have gotten messed up.  I got to test that in a bit.

If there were no read errors, any damaged files were caused by ms windows, not 
the disk.

> Is this terminal or can something be done to correct this?  I did run
> the dd command before I ran the selftest.  I don't think it matters but
> thought it wouldn't hurt either.  If it is terminal, I'll get my
> screwdriver out and see what these drives look like on the inside.  The
> last one I looked into was a old 14" thing many years ago.  Platters
> were about the size of 33 rpm records. lol  Dang I'm old.  O_O

If SMART is saying it will die in 24 hours it will make a nice doorstop :)

I wouldn't use it for data (even throw away stuff) anymore.

--
Joost

Re: [gentoo-user] Does this drive need a funeral?

[Dale]

Dale wrote:
> Hi,
>
> For the first time in my life, I think I have a drive failing on me.  
> Here is the info:
>
> <<<< SNIP >>>>
>
> What you folks think?  Can I fix it somehow?  I got a good shovel 
> handy just in case.
>
> Dale
>
> :-)  :-)
>


OK.  For those that have never seen this before, here is what messages 
looks like when a hard drive is going belly up:

Nov  1 19:08:09 localhost kernel: ata4.01: exception Emask 0x0 SAct 0x0 
SErr 0x0 action 0x6 frozen
Nov  1 19:08:09 localhost kernel: ata4.01: failed command: WRITE DMA EXT
Nov  1 19:08:09 localhost kernel: ata4.01: cmd 
35/00:8c:7f:78:a8/00:03:04:00:00/f0 tag 0 dma 464896 out
Nov  1 19:08:09 localhost kernel: res 
40/00:01:00:4f:c2/00:00:00:00:00/10 Emask 0x4 (timeout)
Nov  1 19:08:09 localhost kernel: ata4.01: status: { DRDY }
Nov  1 19:08:14 localhost kernel: ata4: link is slow to respond, please 
be patient (ready=0)
Nov  1 19:08:19 localhost kernel: ata4: device not ready (errno=-16), 
forcing hardreset
Nov  1 19:08:19 localhost kernel: ata4: soft resetting link
Nov  1 19:08:19 localhost kernel: ata4.01: failed to IDENTIFY (I/O 
error, err_mask=0x3)
Nov  1 19:08:19 localhost kernel: ata4.01: revalidation failed (errno=-5)
Nov  1 19:08:24 localhost kernel: ata4: soft resetting link
Nov  1 19:08:24 localhost kernel: ata4.01: failed to IDENTIFY (I/O 
error, err_mask=0x3)
Nov  1 19:08:24 localhost kernel: ata4.01: revalidation failed (errno=-5)
Nov  1 19:08:29 localhost kernel: ata4: soft resetting link
Nov  1 19:08:29 localhost kernel: ata4.01: failed to IDENTIFY (I/O 
error, err_mask=0x3)
Nov  1 19:08:29 localhost kernel: ata4.01: revalidation failed (errno=-5)
Nov  1 19:08:29 localhost kernel: ata4.01: disabled
Nov  1 19:08:29 localhost kernel: ata4.01: device reported invalid CHS 
sector 0
Nov  1 19:08:29 localhost kernel: ata4: soft resetting link
Nov  1 19:08:29 localhost kernel: ata4: EH complete
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] Unhandled error code
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc]  Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] CDB: Write(10): 2a 
00 04 a8 78 7f 00 03 8c 00
Nov  1 19:08:29 localhost kernel: end_request: I/O error, dev sdc, 
sector 78149759
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] Unhandled error code
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc]  Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] CDB: Write(10): 2a 
00 04 a8 7c 1f 00 03 13 00
Nov  1 19:08:29 localhost kernel: end_request: I/O error, dev sdc, 
sector 78150687
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] Unhandled error code
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc]  Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] CDB: Read(10): 28 00 
00 00 4a f2 00 00 01 00
Nov  1 19:08:29 localhost kernel: end_request: I/O error, dev sdc, 
sector 19186
Nov  1 19:08:29 localhost kernel: FAT: FAT read failed (blocknr 19123)
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] Unhandled error code
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc]  Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] CDB: Read(10): 28 00 
00 00 4a f2 00 00 01 00
Nov  1 19:08:29 localhost kernel: end_request: I/O error, dev sdc, 
sector 19186
Nov  1 19:08:29 localhost kernel: FAT: FAT read failed (blocknr 19123)
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] Unhandled error code
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc]  Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] CDB: Read(10): 28 00 
00 00 4a f2 00 00 01 00
Nov  1 19:08:29 localhost kernel: end_request: I/O error, dev sdc, 
sector 19186

More info:

/dev/sdc1             78112544  39098000  39014544  51% /mnt/media

It won't accept any more files either.  That looks like this:

cp: cannot create directory `/mnt/media/home3/home/dale/.porthole': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.adobe': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.cache': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.gconf': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.fonts': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.gnupg': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.hplip': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.local': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.opera': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.tkdvd': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.fontconfig': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.macromedia': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.scribus': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.ooo3.old': 
Input/output error
cp: failed to preserve ownership for `/mnt/media/home3/home/dale': 
Operation not permitted
cp: cannot create directory `/mnt/media/home3/home/dale2': Input/output 
error
root@smoker / #


So, if you see things like this in your log file, rescue data real 
soon.  Make a note of this since this could happen on your rig one day.

Now I know this is a Western Digital drive.  Let's all face it, they all 
die eventually.  I just find it ironic that it is only a few months out 
of warranty.  :-@

Oh, funny how that drive ran fine on Linux then croaked when put in a 
windoze rig.  Maybe WD just hates M$ as much as I do.  LOL

Dale

:-)  :-)

Re: [gentoo-user] Does this drive need a funeral?

[Dale]

Dale wrote:
>
>
> So, if you see things like this in your log file, rescue data real 
> soon.  Make a note of this since this could happen on your rig one day.
>
> Now I know this is a Western Digital drive.  Let's all face it, they 
> all die eventually.  I just find it ironic that it is only a few 
> months out of warranty.  :-@
>
> Oh, funny how that drive ran fine on Linux then croaked when put in a 
> windoze rig.  Maybe WD just hates M$ as much as I do.  LOL
>
> Dale
>
> :-)  :-)
>

One last update.  When you zero the drive then cfdisk tells you this:

FATAL ERROR: Cannot read disk drive
Press any key to exit cfdisk

I think that means you have a nice new door stop.  My first drive to 
ever fail that I recall.  I still say windoze screwed up my drive.  It 
lasted about 3 days in the windoze rig.

Dale

:-)  :-)

Re: [gentoo-user] Does this drive need a funeral?

[Michael Mol]

On Tue, Nov 1, 2011 at 9:35 PM, Dale <rdalek1967@gmail.com> wrote:
> Dale wrote:
> I think that means you have a nice new door stop.  My first drive to ever
> fail that I recall.  I still say windoze screwed up my drive.  It lasted
> about 3 days in the windoze rig.

It may also be that the Windows rig's PSU is unhealthy.

-- 
:wq

Re: [gentoo-user] Does this drive need a funeral?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 598 bytes --]

On Wed, 2 Nov 2011 10:02:03 -0400, Michael Mol wrote:

> > I think that means you have a nice new door stop.  My first drive to
> > ever fail that I recall.  I still say windoze screwed up my drive.
> >  It lasted about 3 days in the windoze rig.  
> 
> It may also be that the Windows rig's PSU is unhealthy.

Or even the mains supply to that PSU if it is in a different location. I
had a lot of hardware failures after moving house, including several
expensive SCSI drives. They stopped after I bought a UPS.


-- 
Neil Bothwick

Pedestrians come in two types: Quick or Dead.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Does this drive need a funeral?

[Lorenzo Bandieri]

> OK.  For those that have never seen this before, here is what messages looks
> like when a hard drive is going belly up:
 (...)
> So, if you see things like this in your log file, rescue data real soon.
>  Make a note of this since this could happen on your rig one day.
>

Thanks, Dale. Actually I've never experienced an hard drive failure,
but your thread made me want to do one as soon as possible :D

(Besides that, "is going belly up" made me burst out laughing)

Lorenzo

Re: [gentoo-user] Does this drive need a funeral?

[Lorenzo Bandieri]

> Thanks, Dale. Actually I've never experienced an hard drive failure,
> but your thread made me want to do one as soon as possible :D

Sorry, I meant "made me want to do a backup as soon as possible"....

Re: [gentoo-user] Does this drive need a funeral?

[Pandu Poluan]

[-- Attachment #1: Type: text/plain, Size: 343 bytes --]

On Nov 2, 2011 9:22 PM, "Lorenzo Bandieri" <lorenzo.bandieri@gmail.com>
wrote:
>
> > Thanks, Dale. Actually I've never experienced an hard drive failure,
> > but your thread made me want to do one as soon as possible :D
>
> Sorry, I meant "made me want to do a backup as soon as possible"....
>

I almost thought you're a masochist :-P

Rgds,

[-- Attachment #2: Type: text/html, Size: 503 bytes --]

Re: [gentoo-user] Does this drive need a funeral?

[Dale]

Neil Bothwick wrote:
> On Wed, 2 Nov 2011 10:02:03 -0400, Michael Mol wrote:
>
>>> I think that means you have a nice new door stop.  My first drive to
>>> ever fail that I recall.  I still say windoze screwed up my drive.
>>>   It lasted about 3 days in the windoze rig.
>> It may also be that the Windows rig's PSU is unhealthy.
> Or even the mains supply to that PSU if it is in a different location. I
> had a lot of hardware failures after moving house, including several
> expensive SCSI drives. They stopped after I bought a UPS.
>
>

Well, his rig does start up strange.  You have to push and HOLD the 
power button to get it to stay on.  If you just push it like normal, it 
goes back off again.  Sort of gets on my nerves but I don't know if it 
is a mobo or power supply issue.  Could even be something else too.

Hmmmmm.

Dale

:-)  :-)

Re: [gentoo-user] Does this drive need a funeral?

[Dale]

Lorenzo Bandieri wrote:
>> OK.  For those that have never seen this before, here is what messages looks
>> like when a hard drive is going belly up:
>   (...)
>> So, if you see things like this in your log file, rescue data real soon.
>>   Make a note of this since this could happen on your rig one day.
>>
> Thanks, Dale. Actually I've never experienced an hard drive failure,
> but your thread made me want to do one as soon as possible :D
>
> (Besides that, "is going belly up" made me burst out laughing)
>
> Lorenzo
>
>

Well, I live in the sticks.  I see opossums and especially armadillos 
belly up all the time.  They look like those animal balloons.  lol  
Their little feet stuck up in the air and all.  If you ever run across 
one of those, do NOT poke it with a stick.  It can be bad real fast.

I just wish hard drives were as tough as the armadillos tho.

Dale

:-)  :-)

Re: [gentoo-user] Does this drive need a funeral?

[James Broadhead]

On 2 November 2011 01:17, Dale <rdalek1967@gmail.com> wrote:
> Dale wrote:
>>
>> Hi,
>>
>> For the first time in my life, I think I have a drive failing on me.  Here
>> is the info:
>>
>> <<<< SNIP >>>>
>>
>> What you folks think?  Can I fix it somehow?  I got a good shovel handy
>> just in case.
>>
>> Dale
>>
>> :-)  :-)
>>
> Nov  1 19:08:09 localhost kernel: ata4.01: status: { DRDY }
> Nov  1 19:08:14 localhost kernel: ata4: link is slow to respond, please be
> patient (ready=0)
> Nov  1 19:08:19 localhost kernel: ata4: device not ready (errno=-16),
> forcing hardreset
> Nov  1 19:08:19 localhost kernel: ata4: soft resetting link

I have RMA'd many drives upon seeing errors like this. I eventually
tracked it down to a faulty SATA cable. :-/

Re: [gentoo-user] Does this drive need a funeral?

[Dale]

James Broadhead wrote:
> On 2 November 2011 01:17, Dale<rdalek1967@gmail.com>  wrote:
>> Dale wrote:
>>> Hi,
>>>
>>> For the first time in my life, I think I have a drive failing on me.  Here
>>> is the info:
>>>
>>> <<<<  SNIP>>>>
>>>
>>> What you folks think?  Can I fix it somehow?  I got a good shovel handy
>>> just in case.
>>>
>>> Dale
>>>
>>> :-)  :-)
>>>
>> Nov  1 19:08:09 localhost kernel: ata4.01: status: { DRDY }
>> Nov  1 19:08:14 localhost kernel: ata4: link is slow to respond, please be
>> patient (ready=0)
>> Nov  1 19:08:19 localhost kernel: ata4: device not ready (errno=-16),
>> forcing hardreset
>> Nov  1 19:08:19 localhost kernel: ata4: soft resetting link
> I have RMA'd many drives upon seeing errors like this. I eventually
> tracked it down to a faulty SATA cable. :-/
>
>

Well, this one does it with two different cables and it is IDE.  I have 
to admit tho, I was hoping it would work fine after I brought it down 
here and put it in my rig where it used to be.  I even checked the 
jumper to make sure it was set right.

I love grasping at straws tho.

Dale

:-)  :-)

Re: [gentoo-user] Does this drive need a funeral?

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2260 bytes --]

On Tuesday 01 Nov 2011 18:58:14 Dale wrote:
> Hi,
> 
> For the first time in my life, I think I have a drive failing on me.
> Here is the info:
[snip ...]

> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: FAILED!
> Drive failure expected in less than 24 hours. SAVE ALL DATA.

That's not encouraging ...  :-/

Then this:

> 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   018   001   051    Pre-fail
> Always   FAILING_NOW 1904

The Value (018) being lower than the Threshold (051) indicates failure is 
imminent.  Of course it also screams at you that it's "FAILING NOW" in case 
you missed it!  :-))


>    3 Spin_Up_Time            0x0007   087   084   021    Pre-fail
> Always       -       2166
>    4 Start_Stop_Count        0x0032   099   099   040    Old_age
> Always       -       1288
>    5 Reallocated_Sector_Ct   0x0033   199   199   140    Pre-fail
> Always       -       1
>    7 Seek_Error_Rate         0x000b   200   200   051    Pre-fail
> Always       -       0
>    9 Power_On_Hours          0x0032   023   023   000    Old_age
> Always       -       56466
>   10 Spin_Retry_Count        0x0013   100   100   051    Pre-fail
> Always       -       0
>   11 Calibration_Retry_Count 0x0013   100   100   051    Pre-fail
> Always       -       0
>   12 Power_Cycle_Count       0x0032   099   099   000    Old_age
> Always       -       1039
> 194 Temperature_Celsius     0x0022   110   253   000    Old_age
> Always       -       33
> 196 Reallocated_Event_Count 0x0032   199   199   000    Old_age
> Always       -       1
> 197 Current_Pending_Sector  0x0012   199   199   000    Old_age
> Always       -       17
> 198 Offline_Uncorrectable   0x0012   200   200   000    Old_age
> Always       -       10
> 199 UDMA_CRC_Error_Count    0x000a   200   253   000    Old_age
> Always       -       1155
> 200 Multi_Zone_Error_Rate   0x0009   195   085   051    Pre-fail
> Offline      -       191

The remaining values look OK.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]