Present Location: News >> Blog >> Dead HDD

Blog

> Dead HDD
Posted by prox, from Charlotte, on November 06, 2009 at 11:23 local (server) time

So, I think the HDD in my main workstation at home just died:

[26260895.493627] EXT3-fs error (device sda3): ext3_get_inode_loc: unable to read inode block - inode=1401064, block=5603344
[26260895.493627] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
[26260895.493627] end_request: I/O error, dev sda, sector 60715037
[26260895.493627] EXT3-fs error (device sda3): ext3_get_inode_loc: unable to read inode block - inode=1401064, block=5603344
[26260895.493627] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
[26260895.493627] end_request: I/O error, dev sda, sector 60715037
[26260895.493627] EXT3-fs error (device sda3): ext3_get_inode_loc: unable to read inode block - inode=1401064, block=5603344
[26260895.493627] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
[26260895.493627] end_request: I/O error, dev sda, sector 60715037
[26260895.493627] EXT3-fs error (device sda3): ext3_get_inode_loc: unable to read inode block - inode=1401064, block=5603344
[26260895.694211] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
[26260895.694211] end_request: I/O error, dev sda, sector 60846909
[26260906.135862] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
[26260906.135862] end_request: I/O error, dev sda, sector 33714181
[26260906.135862] EXT3-fs error (device sda3): ext3_get_inode_loc: unable to read inode block - inode=557235, block=2228237
[26260906.135862] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
[26260906.135862] end_request: I/O error, dev sda, sector 33714181
[26260906.135862] EXT3-fs error (device sda3): ext3_get_inode_loc: unable to read inode block - inode=557235, block=2228237

My backup is about a week old, so I'm not too worried.  rsync is throwing a major fit right now trying to pull any files in the last week, though.

(destiny:11:20)# uptime 
 11:21:45 up 256 days, 13:11,  9 users,  load average: 0.08, 0.14, 0.09
(destiny:11:21)# sync
zsh: segmentation fault  sync
(destiny:11:21)# cat /var/log/kern.log
cat: zsh: bus error  cat /var/log/kern.log

Oh well.  I guess I'll have to get a new drive.  Current one is a Western Digital WD1600JSRTL (160GB SATA 3.0Gb/sec).

Update: Uh, looks like I just had to reboot.  Somehow my drive spun down and wouldn't spin back up, so things like ext3 were going wild when all I/O was being rejected.  I think the only reason I could login via SSH was because most things were cached in RAM.

> Add Comment

New comments are currently disabled for this entry.