I'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]...
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 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]....
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 attempting to upgrade Fedora 12 to 13. I get an error screen that said root could not be found. Four options are given. Not sure exactly their wording, but two appear to allow you to cancel the other two warn that if you reinitialize you will wipe out all data.
I have a Vista partition and a Fedora partition. I've added the vista ntfs partition to fstab with no help. All of the partition use the long UUID form. I added the root location (root (hd0,5) to the upgrade menu item in grub.conf and that didn't work either.
I'm reluctant to proceed for fear of initializing the entire drive. I could live with installing Fedora 13 over the existing partitions.
I have a raid array using mdadm made up of two drives. The drives have two parts, the first for boot information and the 2nd for LVM. Everything but /boot is under LVM management. Originly the two drives were hooked up to a sata controller in a computer with no on-board sata. However I was not able to get the computer to boot to a sata drive off of that controller. So there was an IDE drive with the MBR that loaded grub.
Now the computer in that setup seems to have died. So the drives were moved to another computer with an on-board sata controller and now the bootup works as far as getting to the grub menu. However after the grub menu the error message "Cannot find root device"
I found the boot info script [URL].. note at the time that was run the computer was running with one drive that has a full Debian install with the raid drive in question mounted and chrooted into. The script was ran from the chroot envirment.[URL]..
New install, linux Fedora 15 Alpha. I am trying to switch over to Fedaora, but the bleeping thing keeps saying device/error/cant find the root.
View 4 Replies View RelatedRecently my Ubuntu 10.04 was booting slow and to figure out what was going wrong, I booted Ubuntu in text mode. There I found it was hanging on for 5-6 sec showing "unable to enumerate usb device to Port 1". I know it has something to do with Port1 / usb device, but could not understand and solve it.
View 3 Replies View Relatedthe 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 RelatedFrom one day to the other my system stopped booting properly. Since I (finally) fixed it, I wanted to share my solution. It runs on a fakeraid pair of SSD's of 60 GB each (actually a single Revodrive device, but it shows up as two devices). When Ubuntu 10.10 boots, I'm dropped to a shell.During boot, when I removed "silent splash" from the kernel's command line, I got these messages:
Code:
[ 4.960240] scsi 6:0:0:0: Direct-Access ATA OCZ-REVODRIVE 1.20 PQ: 0 ANSI: 5
[ 4.960425] sd 6:0:0:0: [sdg] 117231408 512-byte logical blocks: (60.0 GB/55.8 GiB)
[cod]....
I doubt that this is what was needed (as I had that already when it didn't work, but I might be required in addition to installing dmraid)
# update-initramfs -a
After installing this, the problem was solved!! This is strange since I don't recall uninstalling this package or changing anything important, for that matter (perhaps did apt-get upgrade, but that's about it!). [URL]
When booting up my IBM Thinkpad Ubuntu stalls giving the following messages:
Cannot open root device "uuid=58a5831c-5757-49f8.....
Kernal Panic - not syncing: Unable to mount root fs on unknown-block
Spurious ACK on isa0060/serio0. Some program might be trying to access hardware directly.
I am or was using Hardy.
It seems to me that the program is telling me it can't find the hard drive or the partition where the OS resides. I have my drive partitioned with into sections for booting, the OS and my Home directory.
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]....
im a rookie at configuring linux and i have problem booting slackware 13.1 just installed. i get a message similar to this Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(8,4) i got this one from another user who has a similar problem, they say i should fix lilo.conf and it actually was pointing to a wrong partition so i fixed it. i also fixed /etc/fstab to make it point to the right partition /dev/sda3. but after fixing the files, it still wants to load something in /dev/sda4, i dont know why so what should i do next, please explain with commands and not just words. edit this is my lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda3
[Code]...
I edited the passwd file to modify the default shell for root from bash to tcshnow when I try to login to root it gives me the following error:"su: /bin/tcsh : No such file or directory"
View 3 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 RelatedHaving 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
I've been trying to configure my tablet's screen rotation. I can get the screen to rotate, but not the wacom rotation.
Code:
$ xsetwacom set "STYLUS" Rotate ccw
Cannot find device 'STYLUS'.
[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 RelatedThe machine boots, graphics come up, login window shows up, but after login there is only the background window (and mouse). My .xsession looks like this:
[Code]....
Recently, I created a device sc0 through device mapper. The divice could be found in /dev/mapper/sc0. My problem is that the device doesn't exist in /dev/partitions which will block my following test.BTW, I found dm-0 in /dev/partitions. Is it the same as /dev/mapper/sc0? But the device /dev/dm-0 doesn't exist!
View 2 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.
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
I've bought an X10 Home Automation USB interface: the CM15.
This is the information lsusb gives:
skerit@KIP-DU-SKER:~$ lsusb Bus 008 Device 002: ID 0bc7:0001 X10 Wireless Technology, Inc. ActiveHome (ACPI-compliant)
But this tells me nothing about where the device file is! How can I find that, or create one myself?
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 Related