Fedora Installation :: F12 LiveCD "No Root Device Found?
Nov 17, 2009When I try to boot from Fedora 12 LiveCD system halts with the messages: "No root device found" "Boot has failed, sleeping forever"
View 14 RepliesWhen I try to boot from Fedora 12 LiveCD system halts with the messages: "No root device found" "Boot has failed, sleeping forever"
View 14 RepliesI 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 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 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 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.
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 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 RelatedI 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'm having a problem trying to customize Ubuntu 11.04 LiveCD.Everything went well until I tried to run the system updates on the LiveCD.This is the error message output:
Code:
root@lkjoel-desktop:/# sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
code....
i've just burned a livecd (fedora 11), but it doesn't work correctly.it says after i hit boot:
BUFFER I/O error on device sr0 logical block 352328
and then something else, which is similar so i didn't write it down.i read on bugzilla, that is should try to append the boot command with pci=nomsi, but it doesn't work for me
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]....
I am trying to install fedora 14 from live CD (USB boot) in my system which already has Windows 7. The installation goes fine however when I reboot the system I get 'No bootble device found' error. install fedora on the entire hard disk which I cannot do right now.
In Bios there are 'Native' and 'Legacy' options for 'ATA/IDE Mode' and if I select 'Native', 'Configure SATA as' option is enabled with options 'AHCI' and 'IDE'. I reinstalled fedora with all possible configuration, Legacy mode, Native + AHCI, Native + IDE but got the same error when booting. I have also tried options; MBR on /dev/sda and first boot record on /dev/sda5.
fdisk -l :
Device Boot Start End Blocks Id System
/dev/sda1 2048 78782463 39390208 5 Extended
/dev/sda2 78782760 211897349 66557295 7 HPFS/NTFS
[Code]....
the message on the title only happens with Ubuntu. In Fedora, it just stops booting from LiveCD with "WARNING: Cannot find root file system!". The rest of the symptoms are the same.I'm trying to install Fedora LiveCD on an IBM i Series notebook (model 1161-21X). It's a Celeron powered unit with RAM expanded to 512MB. It has a 10GB HDD, and an internal CD-ROM drive. Although it has two USB ports (1.1), it cannot boot from a USB drive, so no pendrive nor external CD unit solution possible.When I boot from LiveCD, it stops booting with the message above. Looking atsg, there's no CD-ROM driver loaded. Also, there's a char device for sg0, but no block device for it, so no way to mount it. It seems that the driver module has been removed from the kernel. I'm currently running Fedora Core 5 in it. This very same problem happens with any Ubuntu newer that 6 or any Fedora post 7.
View 2 Replies View RelatedDual PII 400, 512Mb with a Promise SuperTrak 100 IDE Array Controller. At present I have only one drive on the controller, configured for 1 JBOD array. I install FC9 with no problem. New partition is created and formatted, Grub is installed, and then... Grub is found and booted, but then I get:
Reading all physical volumes. This may take a while... No volume groups found Volume group "VolGroup00" not found Unable to access resume device (/dev/VolGroup00/LogVol01) mount: could not find filesystem '/dev/root' I can boot in rescue mode, chroot to the installed system. I changed the kernel boot parm "root=/dev/VolGroup00/LogVol00"
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'm having a problem going from F12>F13 using preupgrade with a wired internet connection. The current F12 installation is up to date. The upgrade crashes with the "the root for the previously installed system was not found". I've also tried upgrading using YUM and was also unsuccessful. Has anyone run into this problem with this upgrade?
View 6 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.
I have a Dell Vostro 3300, i5 460 processor with a NVIDIA 310M Graphics Card. I'm doing a KUBUNTU 10.10 (Maverick) install with the following results. The Live CD boots just fine to, "TEST," or "Install." Installation goes fine. However, the graphics card being used is the Intel i915. I have tried installing the NVIDIA drivers directly from the, "Additional Drivers," tool and after the reboot I get through the boot screen to the console. I try to manually startx and I get the errors, "no device found," "no screens found." The second install I tried purging and blacklisting the nouveau drivers and entering safe mode. Then using apt-get install nvidia-current. After that, nvidia-xconfig. Same results.
The third attempt I re-installed and this time downloaded the drivers from the Nvidia site (version 256.53). Blacklisted nouveau, remove all nvidia, updated initramfs, etc. The install went fine however I still end up at a console after boot with the same messages as above. No device found, no screens found. I've tried searching through the forum and web and have tried things like adding the modset option along with many other hacks, tips and fixes. still, no go.I can live with the Intel graphics for now although I lose 512MB of memory. Unfortunately there is no way to disable or change this set-up in the BIOS. I've seen quite a few bug reports at Launchpad:
1. Is this something I should just wait til a fix comes? Will a fix come?
2. Is there, or will there be an official Updated Ubuntu Guide for Maverick to install NVIDIA drivers with this tecnology?
3. Lastly, is there anything else I should try??
I just (for the first time ever) installed a version of Ubuntu. It is 10.04. I installed off of the Live Disk. I was having a great time until the first time I went to boot into it and I got the message
"Error: No such device: "long number" Grub Rescue> "
[Code]...
I tried to upgrade from Fedora 8 to Fedora 12, but after preupgrade got everything ready I rebooted. Anaconda searched for storage devices and then said "No upgrade root found". What can i do to continue the upgrade manually?
View 1 Replies View RelatedFedora 14 is used throughout the whole problem. The problem started when I wanted to install Fedora 15 DVD by making a bootable USB key. The size of the USB stick is 8 GB. The problem happened when I (following the tutorial) wrote the line [URL]... livecd-iso-to-disk command associated with the path to the ISO DVD and the partition on the USB stick. the USB stick has the device name /dev/sdb , 1 partition sdb1.
I then noticed that it was mentioned to unmount the USB drive before doing this command. so, while the terminal had written in it "Checking" , I pressed CTRL+C to stop the execution and then pressed on the arrow beside the device in the computer window (Which I think that it unmounts the device). The actual problem started here. I then tried to mount the device but couldn't, It said the device was not found. so I removed the drive and inserted it again, the OS didn't automount the USB drive, I tried to manually mount it but it said the device is not found or doesn't exist. then I used fdisk -l, It said that the sdb didn't have a valid partition table. Also the size of the device is wrongly reported. It should be 8 GB but it is reported to be 2 TB?!
[code]....
I think the wrong partition table made it think that it has a certain number of sectors which isn't real,that made it think that the device is 2 TB large....
I'm facing a problem on Boot on San installation, Os is installed, now I'm trying to define mapper device
for others lun/disk with alias for multipath references
Code: # pvcreate /dev/dm-14 /dev/mapper/disk_bin_rac
Device /dev/dm-14 created
[code]....
this is my first setup of ubuntu. And I�m quite familar to Linux allthoug it�s been a while since my last setup. Anyway, my system is brand new and consist of the following parts:
AMD Athlon X2 240e on MSI 880GMA-E45 (SB850)
4GB RAM (DDR3)
All drives connected by SATA using onboard SB850 ordered by:
1 LG BluRay optical drive
2 WD Caviar Green WD10EARS 1TB
3 WD Caviar Green WD20EARS 2TB
4 WD Caviar Green WD20EARS 2TB
5 WD Caviar Green WD20EARS 2TB
6 WD Caviar Green WD15EARS 1,5TB
I set the SATA controller to AHCI because I want to set up a software raid (level 5) on the three 2TB-disks. The first disk (1TB) should be the ubuntu boot disk (no raid). The last one (1,5TB) is currently not connected - it will be added later. First I struggled booting the ubuntu server 10.10-CD (x64) from the bluray drive - after succesfull starting the setup procedure it told me that it cannot access the drive. It seems that drivers are missing. No problem - I connected an usb dvd drive to the system and gave it a try.
The boot order was set to usb-dvd, then bluray, then the first harddisk (1TB). Setup seems to run fine using the usb dvd drive. I�ve chosen the first disk (shown as /dev/sda) for the installation. It was automatically configured as one big root-partition and a small swap-partition. Grub was installed on the MBR of the first disk. But after restart GRUB tells me "Gave up waiting for root device" and "ALERT! /dev/disk/by-uuid/whatever does not exist. Dropping to a shell!". Obviously the boot loader cannot find (or access) the volume containing the kernel.
I made some research and found some other people complaining about some mixup of hdaX and sdaX devices on SATA devices - but these statements where from 2007. Another point is that the USB optical drive is my boot device while the installation runs, but not afterwards - does this matter? I also tried installing Ubuntu server 10.04, but is behaves the same. Please keep in mind that the goal is to have ubunto server 64bit running on this system - that�s it. No dual boot is needed. And there is no data on any disk that should be taken care. It�s a very new system. Where should I start to fix this issue? What�s wrong with the current linux boot loader using SATA disks connected to SB850 SATA controller?
I did an installation of Ubuntu 8.1 on my laptop. I ran the live CD first to check that everything was ok and got no problems. But when I try to boot I get this error:
Boot from (hd0,0) ext3 e194- long number
Gave up waiting for root device.
Alert /dev/disk/by-vvid/e194- long number
I tried a different hard drive with the same results. So I installed XP and everything worked fine. This makes me believe that all of the hardware is ok and I have some config screwy.
Having finally made the switch from Windows (7 Professional) to Linux (Fedora 13) on my laptop, I'm now trying to get all my devices working, specifically an Olympus VN-4100PC Digital Voice Recorder. I've installed odvr and it works in root, but not as a normal user. The installation instructions say: odvr *requires* access to the user-space USB interface.
It is recommended to place "41-odvr.rules" into "/etc/udev/rules.d" or setup your own udev rules rather than running odvr as root. After changing udev rules, don't forget to run "udevcontrol reload_rules" and to replugin your DVR. Again, root privileges are required unless udev is properly setup. The file "41-odvr.rules" (designed for Ubuntu) has the following content:
SUBSYSTEM=="usb", SYSFS{idVendor}=="07b4", SYSFS{idProduct}=="020d", ACTION=="add", GROUP="audio", MODE="0664"
I tried just doing what it said and copying it to "/etc/udev/rules.d" but it didn't seem to work. Looking at other files, I then changed it to:
SUBSYSTEM=="usb", ATTR{idVendor}=="07b4", ATTR{idProduct}=="020d", ACTION=="add", GROUP="audio", MODE="0664"
And now if I do "ls -l /dev/bus/usb/002", I get:
crw-rw-r--. 1 root audio 189, 134 Oct 15 01:21 007
Which seems to suggest that it is running the "41-odvr.rules" file, since lsusb gives:
Bus 002 Device 007: ID 07b4:020d Olympus Optical Co., Ltd Digital Voice Recorder VN-240PC
But odvr still doesn't work as a normal user, giving:
Failed to open Olympus device: couldn't claim interface
out in finding root device of fedora 14. I've windows XP and fedora 14 installed on. this is the output for blkid
/dev/sda1: UUID="962C8EA82C8E834B" TYPE="ntfs"
/dev/sda5: UUID="262C06BF2C068A4F" TYPE="ntfs"
/dev/sda6: UUID="cbcf539a-dee1-4f2f-b68c-ce315ae76e0f" TYPE="ext4"
[code]...
I have a Netbook Remix install on an SD card that won't boot. Grub2 in the recovery mode shows it fails finding the root files by using UUID. It's my first Grub2 install and I'm not sure how to go about debugging it. The machine boots the same version from a USB stick.
View 1 Replies View RelatedI got the message "Gave up waiting for root device after I rebooted an Ubuntu 10.04 system I thought I restored by unpacking a tar.gz at the base of the directory tree I made for backup purposes.
View 1 Replies View Related