Topic: Server Drive Crash

[GlitchFreak]

Hey everyone

It's 09:45 PM and a client just called and told me that the server is presenting IO errors. There is also a clicking sound from the drive.

No recent backups (yeah I know), but I was wondering what commands I could use to restore and/or fix the file system after I clone the drive tomorrow. Any resources will be appreciated!

Kind regards
Kelso

[Stefano]

in my experience, with I/O errors and a clicking hd there's no much to do..

anyway, I've managed to clone a failing hd... freezing it
you should shut down your server, let the hd cold down, then use a icepack to keep it as cold as possible

HTH

[GlitchFreak]

Thanks, will definitely give it a shot!!

[thomasch]

Thanks, will definitely give it a shot!!

Be careful with icepack/cooling.
While cooling the hdd can save you some data, the condensation can make it worst.
Put your hdd inside a vacuumed zipbag to prevent condensation touching your hdd electronic circuits.

read here :
http://lifehacker.com/5515337/save-a-failed-hard-drive-in-your-freezer-redux

thomas

[StuC]

I've put one in the freezer (in multiple bags) with serial/power leads attached.
The idea being condensation on hitting a warmer room as you prep it for run up is a serious risk, if you can leave it in the bag it came out of the freezer and just keep it between ice blocks for first run the handling is reduced and temperature rise time is much longer. Obviously seal the ends of the cables too. (for some hard drives I.E. non raid you could try a USB - IDE/SATA adapter in the bag but the slower data rate may defeat the extra time)

Plan what data you need most before power up and copy it in logical chunks before trying anything too large. It means sitting with it but sometimes you only get one chance and the drive fails fully the same day.

Drives that "click" regularly (in my experience) benefit less than ones that just die but will run for 20 minutes from cold.

[GlitchFreak]

Thanks guys. I successfully cloned the drive. The initial sectors where GRUB resided were corrupted but an upgrade from the SME installation sorted that out.

They are now fully working again!!

Thanks again for the help!