(Sorry for the bad pictures - you can't exactly do a screenshot of a crashed system).
A "mount status: { DRDY ERR }" does not necessarily mean hardware failure, even if BIOS reports hard drive failure:
Get a
rescue cd, boot off it, and and fix your partition using fsck, xfs_repair, etc
... using i.e. xfs_repair:
It's strange that a corrupt xfs partition can cause even the BIOS to fail to read the drive, but there you have it ... back in business:
jknight@shadowbox:~$ mount | grep dev\/sd|sort
/dev/sda2 on /boot type ext3 (rw)
/dev/sda3 on / type xfs (rw)
/dev/sda4 on /home type xfs (rw)
/dev/sdb1 on /media/cdrom0 type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096)
Knowing that this is (can be) a symptom of a corrupt filesystem, if you got this on a windows box, it'd be worth trying to boot a linux rescue cd, and run a ntfs or vfat fcsk against it.
Leave a comment