Re: [tlug] Clunk, Clunk, the Drive is Dead

[Mark Sargent <powderkeg@example.com>]

Hi All,

more info for this. The 1st time it happened, I got the following after 
being dropped to a shell and running fsck as suggested,

Error reading block 'block-number' (Attempt to read block from 
filesystem resulted in short read) while doing inode scan. Ignore error<?>y

Force Rewrite<?>y

After doing this x amount of time, the scan finished, and I gave a 
reboot command. But, it gave a number of errors, that said certain 
files(pids?) were read only. Below is what I recall of those errors.

rm: <filepath> read only file

Sorry, I didn't note it down, and don't have the faulty drive with me 
today. I'll run it again tonight, and post the exact errors.

After having to turn off the power, due to the system locking up, and 
re-booting, I'm back to the point of being dropped to a shell, only to 
finally get to the same sticking point again. I then completely 
re-installed, as there wasn't anything worthwhile on the drive, and just 
to see what would happen. The install was successful, and I had been 
using it for alomost 2 days, when all of a sudden, last evening, I got 
some clunking sounds from the drive, and it locked up the whole system, 
again. Upon re-starting, I was dropped again, to a shell, for the same 
result. Thoughts.? Cheers.

Mark Sargent.