Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
While using Partition Magic 8.0 to resize my hard drive, I wrecked my partition table. The system crashed when rebooting.
After using the RH9 rescue disk, I was able to resurect the system, but the next reboot caused a forced check for bad blocks. This causes the system to
" /:duplicate /bad block[s] in inode......" and it starts duplicating
This goes on endlessly till the system hangs.
I don't know why but now the RH9 rescue boot disk wont restart the system without the forced check. Neither does the Distro. CD.
Can I stop this bad block duplication? Will I have to start from scratch?
best way to repair the disaster is to back up your "resurected" data (and system if you want to avoid reinstall), then either reinstall, then restore data OR repartition (just to be safe), make new filesystems (e.g. mkfs.ext3 for ext3 filesystem) and restore.
your system may look "resurected", but it still seems to be damaged enough for this procedure if fsck can't repair your partition.
suggestion appreciated, and it would've been great to have backed up the system when the rescue disk restarted it.
however that restart was a one off. after the initial boot up, I rebooted it knowing that a forced file system check would happen, but instead of fixing the problem, the system no longer gets past this point at start up.
worse is that even with the rescue disk, I cant get to a point where backing up would be possible.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.