-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 24 Feb 2004 19:51:44 +0200 (SAST) Rh Conacher <hylton@global.co.za> wrote:
Today I was unable to get my Suse 9.0 system to boot as each time I Ctrl-D'd it rebooted and told me to run fsck manually.
I thought GREAT :( but having asked before on the list I booted with my boot diskette and was presented with the options of boot from harddisk, installation, safe mode, manual install and rescue etc.
I tried the rescue to no avail and even entered the command fsck -VAa / into the additional options with NO luck.
How the hell do I get my system back by completing the fsck!! Depends on what file system you have. If you have ext2 or 3. Assume that /dev/hda1 is root, and /dev/hda2 is a mountable file system, such as /home. When you run fsck from single user mode, make sure that the root partition is mounted read-only. You can test this by trying to create a file. You'll get permission denied if root is mounted ro. If you can write to root, then: mount -o ro,remount /
Make sure the mountable file systems are unmounted. They should be in single user mode when you boot. fsck -fsy /dev/hda1 /dev/hda2 fsck is a generic wrapper to the filesystem specific fscks. If you have reiserfs, then reiser will not let you fix the root file system while it is mounted. So, boot the rescue, and run reiserfsck: reiserfsck --fix-fixable /dev/hda1 There are other options on reiserfsck, but the man page is explicit enough. - -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAO7SD+wA+1cUGHqkRAkvCAJ99jFUJF6X3NmpOdcJV+v+dVj4ojACfZRMm TAhnFM8M/+DzyAy+Wx/b9Cc= =u+H6 -----END PGP SIGNATURE-----