FC5t3 error: mount: could not find filesystem '/dev/root'
FedoraThis forum is for the discussion of the Fedora Project.
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.
I've run linux on laptops for years, but with very superficial knowledge:
I never had to learn how to fix problems, cause I never had problems...
...until my latest laptop. I installed FC2 and it worked fine. I managed
to get FC4 to install after much work, but it wouldn't boot, so I tried
upgrading to FC5test3. Successful install, but it still won't boot.
The error(s) are "Unable to access resume device" on my swap partition
and "mount: could not find filesystem '/dev/root'" even if I eliminate
the swap partition from /etc/fstab.
Here's the exact error I get when I try to boot.
Tabbed entries only show up when I boot without the quiet flag.
(this was copied from the screen... is it written to a file somewhere?)
scsi0 : ata_piix
Vendor: ATA Model: FUJITSU MHV2100A Rev: 0000
Type: Direct-Access ANSI SCSI revision: 05
hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
Unable to access resume device (/dev/hda3)
Creating root device.
hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
Mounting root filesystem.
hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
[<c011a0c6>] panic+0x3e/0x170 [<c011cc17>] do_exit+0x71/0x6cf
[<c011d2f9>] sys_exit_group+0x0/0xd [<c0102bc1>] syscall_call+0x7/0xb
Here's what things look like from rescue mode:
fdisk -l:
Disk /dev/sda: 100.0 GB, 100030242816 bytes
16 heads, 63 sectors/track, 193821 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 203 102280+ 83 Linux
/dev/sda2 204 189758 95535720 83 Linux
/dev/sda3 189759 193821 2047752 82 Linux swap / Solaris
e2label /dev/sda1: /boot
e2label /dev/sda2: /
e2label /dev/sda3: Bad magic number in super-block while trying to open /dev/sda3
Couldn't find valid filesystem superblock.
So it seems like /root trying to be mounted on /dev ... maybe
because fdisk understands my swap setup but e2label doesn't?
I'd appreciate any tips on how to get things to work.
(dmesg output can be supplied, but I didn't see anything helpful in it.)
Oh, and there may also be some odd duplications in df and /etc/mtab:
Distribution: Mandriva 2007. Others are now being tested through Xen. 2 Gigs of Ram is enough to run 3 OS's.
Posts: 847
Thanked: 0
Edit your fstab & the grub boot loader to get rid of the LABEL=/ crap. Tell it to mount the physical device (i.e. /dev/sda2 /). Fedora/Redhat is the only distro I am currently testing that mounts file systems via labels. It sucks when you are doing multipartition distribution installs.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.