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 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've installed Fedora 15 with Fedora 14 already installed in other partitions, but now I can't boot Fedora 14 as it prompts "no root device found", these are both grub.confQuote:
#boot=/dev/sda
default=0
timeout=120
[code]...
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 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 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 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'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 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 installed Ubuntu 10.10 inside Windows 7 today, Ubuntu 10.10 finished installing and all just fine
but when I try to boot into Ubuntu 10.10 from the boot menu I get this error
"gave up waiting for root device" while booting
and it mentions something about BusyBox
Ubuntu 10.04.1 to prepare a USB flash drive for use as installation media for a new computer that's on the way. When the Linux kernel tries booting up on the flash drive, I get an error saying VFS: Cannot open root device "<NULL>" or unknown-block(8,1).Here's how I got to this point...Created bootable partition on the thumb drive.Put the following files onto the flash drive: initrd.gz, vmlinuz, and ubuntu-10.04.1-server-amd64.iso fromhttp://archive.ubuntu.com/ubuntu/dis...ages/hd-media/Install Grub2 to the drive via grub-install.Put the following into boot/grub/grub.cfg:
Code:
set timeout=120
set default=0
[code]....
Dual 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 decided to install ubuntu in my PC,i downloaded the .ISO image and i installed it in my USB. After trying it and all that i observed that i really liked it and i decided to formally install it to my computer in the hard drive. When i reached the partition thing,i selected to dual boot with Vista and select between each them in every startup,when i clicked FORWARD it gave me an error which i did not read(because,again im a noob) so i clicked cancel.
Today i wanted to go through the process again and now really install it,so again i went to the time zone part and i clicked forward but then,instead of taking me straight to the partition phase,it appeard a window saying "The installer has detected that the following disks have mounted partitions: /dev/sda ...." I clicked yes,to unmount this partitions so it took me to the partition thing,once there i selected the option to install Ubuntu with Vista and select between them i neach startup,then i clicked forward and went to the username/computer name process,once i finished i continued to the next part,the installation,but i selected to import all of my WIndows VIsta default user data,after that i clicked forward and went to the installation process,i went down stairs to eat soemthing while it finishes,i came back and it was finished,it asked me to reboot so i clicked in Restart Now.
When it tried to boot,appeared an error saying: Error: no such devide found: #################### Grub load(or something like that) grub rescue: and it was a command line,since there i havent been able to boot into vista or Ubuntu,im really scared because is the first thing related to OS installing ive done,so i booted my USB and ran the trial and right now im trying to find out what to do from that trial version.
I just went to the INSTALL UBUNTU 10.04 LTS application under the System>Administration Menu and found out that in the partition phase the Install and allow to select between both systems in eahc startup option,i dont know what to do,i foudn out that my HD has still all its data(MUsic/Videos/Folders/Programs/ect.)its just that i cannot boot from it. Also in GParted it appears as /dev/sda1/ and a warning icon besides it,also when i go into information, thers this warning there [URL]
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]....
Fedora 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]....
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'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 RelatedI am trying to extend my / size as its full. Well the volume group is VolGroup00 & logical volume is LogVol00 but when. I run the command vgextend VolGroup00 /dev/sda8. It says volume group not found. Can it be because I have WindowsXP in my /dev/sda1, which falls under same Volgroup??
View 1 Replies View RelatedAn 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
Being able to reset the root password by booting into single usermode by editing grub. This is a MAJOR flaw. I know it makes no real difference against internet bourne attacks, but even so I must say I found it shocking. The only way I've found to stop this is to encrypt the entire HDD, so noone could get into single user mode without first knowing the encryption key/password.
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 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??