On Wednesday, October 26, 2011 11:38:27 AM Ann wrote: > Another last thought. As there is nothing really to recover, we could > reconfigure the server and then just reinstall the application.
Do it. Sorry I didn't have time to check this list today until now. I manage servers for a living. Lots of them. Mostly CentOS, but more than a few Debian and Ubuntu based as well. The Linux kernel will always remount a file system read-only if it detects drive errors; simply to save the data you've got. > fsck.ext3: Bad magic number in super-block while trying to re-open > /dev/sda1 e2fsck: io manager magic bad! Look at post 4 of this thread (it doesn't matter that it's a fedora forum; the issue is kernel-specific, not OS-specific): http://forums.fedoraforum.org/archive/index.php/t-51985.html But if it's easy enough to rebuild, I'd do it. What we do in this kind of case, is replace the drive (and rebuild RAID since we run RAID on our servers). We always have spares. And then we know we've got a good drive. Then we take the supect drive to the workbench, wipe it, reformat it, and exhaustively test it for a few days. If it passes, it goes back to the DC as a spare; if not, we wipe it again if possible, and then destroy it or send it to a recycleer, depending on how sure we are that we've removed all the data. Jeff -- Jeff Lasman Post Office Box 52200, Riverside, CA 92517 Our jplists address used on lists is for list email only Phone +1 909 266-9209, or see: "http://www.nobaloney.net/contactus.html";
_______________________________________________ LinuxUsers mailing list LinuxUsers@socallinux.org http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers
