Re: HELP!! /dev/root mount failure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Friday June 9 2006 22:03, Hadders wrote:
>  Hi Ed,
>    It's a pretty standard looking output for grub, as it's the install
> default.
>
>  #boot=/dev/hda
>  default=0
>  timeout=5
>  splashimage=(hd0,0)/boot/grub/splash.xpm.gz
>  hiddenmenu
>  title Fedora Core (2.6.15-1.2054_FC5smp)
>      root (hd0,0)
>      kernel /boot/vmlinuz-2.6.15-1.2054_FC5smp ro root=LABEL=/ rhgb quiet
>      initrd /boot/initrd-2.6.15-1.2054_FC5smp.img
>
>
>  e2label said /dev/hda1 was "/"  and couldn't get a label for /dev/hda3,
> which should be swap. It said "Bad magic number in superblock" So I ran
> mkswap on /dev/hda3 again, to be sure. Then went to /etc/fstab and said to
> use /dev/hda3 for swap, not LABEL=SWAP-hda3
>
>  However, when linux rebooted, same problem.  But I also noticed the boot
> message was still refering to swap as LABEL=SWAP-hda3 not /dev/hda3??
>
>
>
>  Ed Greshko wrote:
> Hadders wrote:
>
> Hello all.
>   I posted this earlier in the week, but decided this morning, I would
> shift my ext3 partition to the front of the disk and have grub install
> onto /dev/hda
>
> But, Grub STILL hangs when it tries to load itself and although I can
> use lilo 22-7 to get the install working I still get this error!
>
> Trying to resume from LABEL=SWAP-hda3
> No suspend signature on swap, not resuming
> Creating root device.
> Mouting root filesystem.
> mount: could not find file system '/dev/root'
> Setting up other filesystems.
> Setting up new root fs
> setuproot: moving /dev failed: No such file or directory
> no fstab.sys, mounting internal defaults
> setuproot: error mounting /proc: No such file or directory
> setuproot: error mounting /sys: No such file or directory
> ...
> Kernel panic ..
>
> I'm at a loss as to how I even approach fixing this?
>
>
> What is the contents of your grub.conf?
>
> What is the output of e2label for each partition?
>
>
> How do I pause the loading cycle, and I can't even go into single user
> mode as I'm not getting that far?!
>
> I still have my GigaRAID ATA bios loaded for the RAID 0 container I
> have, is it possible this is mapping to a memory address and conflicting
> with Grub and setting up dev root?
>
> I'm also using the SMP kernel by default as I have a dual core Intel
> 2.66....  perhaps  I will try the single processor kernels...
>
> HELP, please! ;-)
>
> Hadders
Try reinstalling grub from rescue mode now,  make sure that all labeled 
filesystems in /etc/fstab exist or change either the fslabel or fstab.   The 
main thing to do now seems to be rewrite the boot info.

Attachment: pgpxbKUUbpMYa.pgp
Description: PGP signature


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux