I have a Feadora 12 Live CD. It booted up fine on my 700 Mhz computer. I've since then put a new HDD in with which I intended to install Fedora on. But now i get this message
Quote:
No root device found. Boot has failed, sleeping forever
What does this mean? How do get the Live CD to boot?
I downloaded fedora 14 64 image then created a bootable flash drive and put the image on the flash drive. I rebooted and tried booting from the flash drive and that's the message I received. What do I do?
View 6 Replies View RelatedI've downloaded Fedora 12 and decided to try and install it on my old laptop which is currently running Ubuntu 9.10 with no problems.
When I boot from the live cd, it starts to load with the 3 bars on the bottom, one on top of the other, one is white, one is dark blue, the other is in between those colours in the spectrum somewhere....
Anyway, the load bars complete and "Fedora 12" turns white, then the following output populates:
mount: unknown filesystem type 'DM_Snapshot_Cow' (<----- repeated a bunch of times) can't mount root filesystem Boot has failed, sleeping forever.
I've taken the kernel 2.6.33.3 and edited the .config file to take out most of the compatibility etc. that I will not be using. I'm run the makes and updated grub. I go to boot it runs through most of the way until I get the following:Quote:/bin/plymouthd: symbol lookup error: /bin/plymouthd: undefined symbol:ply_chara could not read byte from child: SuccessNo root device foundBoot has failed, sleeping forever.'m fairly new to Linux and still more of a dabbler. (Though this seemed more difficult than "Who is root" so I didn't put this in the newbie thread.)Any ideas for what might be wrong?I've tried looking in the config file from something that relates, but they have all been included (Y) in the module.
View 2 Replies View RelatedI have a fresh computer with specs as such:
Hard Drive: Western Digital Caviar Black 500Gb 6Gbs Sata
Asus Sata DVD/CD Burner
Core i3 3.3GHz Sandy Bridge chipset
MSI P67A-GD55 Motherboard
Zotac GTS 450
I have a problem where the live cd gives this error message:
Boot failure, sleeping forever.
I have installed Fedora 12 on my HP laptop which has got a NVIDIA graphics card. I have got latest F12 kernel 2.6.32 as well as default kernel 2.6.31.I have installed Nvidia Proprietary Drivers and modified grub.conf file for 2.6.32 kernel saying blacklist nouvaue so that it can load NVIDIA drivers ...After that I am able to successfully boot into 2.6.32 kernel with Nvidia Proprietary Drivers.Everything seems to be fine .. But suddenly today when I tried to boot into F12 2.6.32 kernel I got the following error
Code:
No Root Device Found
Boot Failed, Sleeping Forever
[code]...
I have 2 Debian OS's and wanted to put Fedora next to it.
Install went ok, but after rebooting it says: "No root device found. Boot has failed, sleeping forever."
During install from the live CD I didn't "v" the boot (efi or something?) because I thought Grub would take care of everything.
Should I just reinstall again and choose the Fedora bootloader? Won't it mess up Grub?
I've created an LiveUSB disk with the USBcreator method in Windows 7.Now the the image is copied succesfully and the USB key is bootable.However when the boot window popsup and I select the verify & boot option, a graphical loading window comes up and right after that the system halts with the error message "Sleeping forever".What am I doing wrong? Or what is Fedora doing wrong with their LiveCD to USB media?I've did a forum search and the exact same issue is described in this thread[URL]
View 5 Replies View RelatedI didn't like my partitioning layout so I have repartitioned and reformatted the drive. I have copied the backed up back onto the hdd, and i have installed grub successfully. Still, when I boot the machine, I get an error message: "No root device found. Boot has failed, sleeping forever.". When installing GRUB, it managed to found /boot/grub/stage1 without a problem, and I have installed it onto the MBR
View 7 Replies View RelatedI'm a long time Linux user. Finally got around to upgrading my Fedora 11 system to Fedora 12 by using the 'preupgrade' tool. The upgrade appeared to go well (downloaded packages, rebooted into installer, etc). However, now that the upgrade is complete, I'm unable to boot my system.
Here's my configuration:
/dev/sda (80Gb)
200Mb /boot partition (ext3)
52Gb / partition (ext4 - managed as logical volume)
2Gb swap partition (managed as logical volume)
20Gb /spare partition (ext3 - managed as logical volume) .....
All worked fine under Fedora 11 for the last few months. Grub now presents me with 'Fedora' and 'Windows XP' boot options. The /boot/grub/menu.lst file is essentially the same as it was for Fedora 11, except for the different kernel versions, etc. The boot sequence shows the Fedora bubble (??) and gets about 80% full when the screen goes black and the message displayed is:
No root device found
Boot has failed, sleeping forever
If I boot Windows, all works fine.
Am able to boot using a SystemRescueCD disk. The disks all look okay and I can mount/modify all partitions, etc. The grub menu.lst file read as follows (sorry, typed in, not copied):
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.32.11-99.fc12.i686.PAE)
root (hd0,0) .....
i am really facing too much problems with fedora 14.yesterday due to low battery my lapi turned off n when i rebooted.
i got a error:-"NO root device found,boot failed...sleeping forever..
Error : no root device found. booting has failed, sleeping forever.
View 1 Replies View RelatedWe have a SuSE/SLES 9 server that boots from a fibre channel card, using volumes from a NetApp filer.
We previously had the server booting from the LUNs on the filer, but after some tinkering around with the fibre channel BIOS, we have the situation where the LUNS seem to be mounted, the OS boots, starts to initialise everything but then stalls, saying:
We have tried loads of combinations of settings in the BIOS and fibre channel BIOS without any success or any idea what may have caused the error.
When I try to boot from Fedora 12 LiveCD system halts with the messages: "No root device found" "Boot has failed, sleeping forever"
View 14 Replies View RelatedI just compiled my first own kernel (I'm using Arch Linux), following the tutorial on the german site. Now I tried to boot it, I ended up failing with this message: Code: Waiting 10 seconds for device /dev/sda1 ... Root device '/dev/sda1' doesn't exist, Attempting to create it. ERROR: Unable to determine major/minor number of root device '/dev/sda1' Here is the important part of my menu.lst:
[Code]....
I simply copy&pasted the Arch-entry, i.e. I also had the disk by uuid there. The failure message was the same, just the root device name was the different name Also, at first I did not have the initrd line in my menu.lst (as written in my tutorial that I may not need it). In this case I had this error message:
[Code]....
I had a windows 7 professional on my computer. I tried dual booting it with ubuntu. While installing ubuntu when it asks which partition you want to install it "as it said your all data in the partition would be erased but not before you confirm" so I selected go back and aborted installation because I didn't wanted that and bang I start my system again an I get this error "no boot device found". I ran my hard disk test it say's passed so I don't think my hard disk is corrupted. I tried using windows 7 recovery disc but I guess it doesn't even detects a operating system on my laptop. I got no back up of my data. Any way to get back my data if I cant get windows back!
View 8 Replies View RelatedI insert my F14 CD and booted the computer; I see the beginning of the installation and the the screen goes black and says:
No root device found.Sleeping forever. Boot failure.
An old machine in our office, running Ubuntu 6.06 all of a sudden will not boot up. I get the following info during boot:
Uncompressing Linux... Ok Booting the kernel
mount: Mounting /root/sda1 /root failed: No such device
mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory
[code]....
I haven't changed anything on the system as far as I'm aware, and I ran some HD diagnostics and everything seems fine. however when I try to mount the drive with the following command:
sudo mount -t ext3 -o rw /dev/hda1 /mnt
I get the following error:
mount: wrong fs type, bad option, bad
superblock on /dev/sda1, missing code
page or helper program, or other error
In some cases useful info is found in
syslog - try dmesg | tail or so
I ran fdisk -l and it says the partition type is Linux. The output after running dmesg | tail :
[12207.483801] init_special_inode: bogus i_mode (101)
[12207.483809] EXT2-fs: corrupt root inode, run e2fsck
[12260.427078] init_special_inode: bogus i_mode (101)
[code]...
Update: After running e2fsck -p /dev/sda1, I get the following info:
/dev/sda1: clean, 142449 / 9584640 files, 5402711 / 19161520 blocks
just installed ubuntu 10.10 on my external usb hdd from my 8gb flash drive doing this on a laptop, my primary hdd (internal) is running windows (230gb of 250gb used) so i got an external hdd (2tb) and I decided to install ubuntu on it
[Code]....
I boot EPC 1000h from usb(Fedora-12-i686-Live). it shows msg at the point about "drm-model-rmfb". ...than it "sleep forever".
View 2 Replies View RelatedWhen I boot off of Debian Kernel 2.6.26-2-686. This is what happens. It stops at attached scsi generic sg5 type 0 After 4 or 5 minutes it comes back and says.
Gave up waiting for root device. Common problems Boot args (cat /proc/cmdline) Check Root= (did the system wait for the right device) Missing modules (cat /proc/modules; ls /dev Alert /dev/sdd8 does not exist dropping to shell /bin /sh: can't access tty; job control turned off If I boot off Debian Kernel 2.6.26-2-686 (single user mode) Then use Control-D it boots fine.
when i start uubuntu it automatically goes to tty with out letting me login. then when i press startx it says:
NVIDIA: failed to initialize the nvidia graphics device pci:0:13:0
nvidia: please check your systems kernal log for additional erroe
nvidia: messages and refer to chapter 8
nvidia: failed to initialize the nvidia graphics device!
nvidia: screen found, but none have a usable configuration
fatal screen error: no screen found
right before this i had activated a nvidia graphics device
Okay, so on occasion when I boot into ubuntu I get this error
[mount: mounting /dev /root/dev failed: no such file or directory]
[mount: mounting /dev /root/sys failed: no such file or directory]
[mount: mounting /dev /root/proc failed: no such file or directory]
[code]...
I get the error when I open any of the kernel versions or any recovery mode. Ubuntu 10.10 Desktop is the only OS installed on the computer, which is a Lenovo S10-3. I can eventually get it to go away, sometimes by repeatedly unplugging it and plugging it back in, and sometimes I will boot into GParted, do nothing, then restart and it will work.I have found some solutions online, but all of them involve the error happening as a result of dual booting with Windows.I have made no major system changes recently, so I can't see anything like that being the problem.
have been fiddling! moved my partitions around (without using any cd by installing grub2 to boot to an iso of gparted).I moved:
swap,ntfs,ext4(fedora13)
to:
swap,ext4(Fedora13),ext4,ntfs,unformated
[code]....
My Fedora 12 System was failed when booting.The message like that : mount: wrong fs type, bad option, bad superblock on /dev/mapper/my_vol missing codepage or helper program, or other error. In some case, useful info is found in syslog - try dmesg | tail or so Can't mount at root filesystem. [drm: drm_mode_rmfb ] *ERROR* tried to remove a fb that we didn't own. Boot has failed, sleep forever. I guess something wrong with my hard disk, so the bootloader can't recognize the filesystem type.
View 2 Replies View RelatedI needed to use CIFS for accessing a NTFS network share. I decided to include CIFS in the kernel and tried compiling and installing it. Now when I (try to) boot in my new kernel with CIFS support, I get the message: gave up looking for root device.
View 5 Replies View Relatederror message
Quote:
"failed to run * as user root, the gksu-run-helper program is not found or is not executable"
Tried googling and checking threads at LQ didnt find a solution or another instance running slackware64 current.. everything built fine, tried and everythings executable...I also have Alien's multilib installed, with only firefox and flashplugin as 32bit, everything else 64bit. I can't open any apps as root by normal user
I've upgraded my squeeze box to linux kernel 2.6.32-5. But it shows mounting "here is the uuid of / " on /root failed: Device or resource busy while booting.Here is the menuentry of linux kernel 2.6.32-5.
[code]....
I've got the F13 LiveCD that I was able to boot and use using the "nomodeset" boot option. From the desktop I'm trying to perform an Install to Hard Drive. I've read the Install from LiveCD post regarding the creation of a /boot partition and a / root partition. I've tried creating them without the LVM group and with. But every time I appempt to install I get...
An error occurred mounting device proc as /proc: mount failed: (9, None). This is a fatal error and the install cannot continue.
Hardware is a Sager 8887 (P4, 3.06HT, 60GB HDD, Radeon 9000 graphics adapter)
I am getting a message at my first re-boot after install of "Error 15: File Not Found", and that's as far as it goes. I just installed Fedora 11 on a Drive that I had recently ran Ubuntu 9.04. I did re-partition and format the drive. I am also running Win XP Pro on another drive, and can boot from either. The computer is older, but all the hardware seemed to work fine with Ubuntu and altough I had to format the install drive a couple times the installation seemed to go ok.
View 4 Replies View Related