Uh-oh. Never mind "fsck" (yet). Your system can't even find "/dev/sda4" (that is one of the "ERROR:" messages reported) to begin with. The possible causes for this condition are all bad (sorry). I realize this is slow-going, but the next incremental step is to see what your partition table looks like. At that command prompt, try whichever of these two commands produces partition information as output: fdisk -l /dev/sda /sbin/fdisk -l /dev/sda When you created your partitions (sda3 through sda6), did you write down the partition information? If your partition table is messed up, it may be very difficult to recover the table without that information. On Tue, May 22, 2012 at 08:34:04AM -0400, aerospace1028@xxxxxxxxxxx wrote: > decompress linux ... parsing ELF ... done. > booting the kernel. > Running hook udev > Triggering uevents ... done. > ERROR: device "/dev/sda4" not found. Skipping fsck. > ERROR: unable to fid root device "/dev/sda4." > You are being dropped to a recovery shell. > Type "exit" to try and continue booting. _______________________________________________ Blinux-list mailing list Blinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/blinux-list