Slackware :: Won't Boot After Update - VFS Cannot Open Root Device
Oct 21, 2010
I have been trialling Slack 13.1 on a spare 32b system for a couple of weeks, and today I took the plunge and put it on my main machine. I completely re-partitioned the drive (using the Slack disk) and installed Windows7 on one partition and Slack 13.1 on another. The install worked fine and I tested that it boots from LILO into both Windows and Slack perfectly. I then ran:
I have a redhat ES3 I want virtualized.the virtual machine encounters a problem starting when it is virtualized
There are this message : RAMDISK : couldn't find valid RAM Disk image Starting at 0. VFS: Cannot open root device "LABEL=/" or 00:00 please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on 00:00
Installed Maverick last night... the system has been working fine all day... then on a reboot tonight got the following.
RAMDISK: gzip image found at block 0 usb 1-2: new high speed usb device using ehci_hcd and address 2 uncompression error VFS: Cannot open root device "mapper/mylaptop-root" or unknown-block(0,0)
[code]....
Then it gives the Kernel Panic
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Pid: 1, comm: swapper not tainted 2.6.35-22-generic #35-Ubuntu
Then a call trace...This is a brand new install of Maverick I copied my files onto a USB and did a fresh install on the whole drive using the alternate CD (the desktop and netbook editions both failed to read on my system) was previously using Karmic with no issues. I tried to e2fsck the dev/sda1 from the CD in "repair broken system" mode but the return was "clean" I read that as the file system being intact but this is an area that I have no real knowledge in.
I have added CentOS5.5 x86-64 to a linux box that already contains installations of Ubuntu 9 and SL 5.2. Grub2 was installed with Ubuntu and is on the MBR of the disk. I did not install grub with anaconda/Cent. Grub update in ubuntu finds the Cent install and addes it to the grub.conf, and Cent appears in the grub menu at boot. If I select Cent, I get the following error. VFS: Cannot open root device "sda7" or unknown-block(0,0) Please append a correct "root=" boot option
Below is the output of boot_info_script, which gives the relevant boot file data. There are still grub conf files on the SL install, but grub is not installed there anymore. Boot Info Script 0.55 dated February 15th, 2010 => Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in partition #6 for /boot/grub ..... sda3/boot/grub/grub.conf: # grub.conf generated by anaconda # Note that you do not have to rerun grub after making changes to this file # NOTICE: You do not have a /boot partition. This means that all kernel and initrd paths are relative to /, eg. # root (hd1,2) # kernel /boot/vmlinuz-version ro root=/dev/sdb3 # initrd /boot/initrd-version.img
I am trying to install Ubuntu 10.10 from a USB flash memory stick. It works fine until around 95%, where I get the following warning/error:
[Code]....
I click OK and the installer seems to finish nicely, except the terminal throws several errors along these lines (see photo):
[Code]....
I tried also with 10.04 LTS, the difference being that the install warning appears two or three times instead of once. Some results from googling (Ubuntu Forums, Ubiquity bug) suggest unchecking the initial update options. I am going to try this but I'm not sure if I'll be able to get the boot loader right (there seemed to be problems with this).
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 am using a kernel with no initrd. I have had this kind of panic before. Usually it means that the kernel can access the hard drive because the driver for the controller or filesystem isn't built into the kernel.
The kernel is 2.6.34 vanilla.
My IDE controller is a Silicon Integrated Systems SiS 5513, and I built the driver for it into the kernel BLK_DEV_SIS5513=y
My /boot (hda1) is ext2, and everything else is ext3
EXT2_FS=y EXT3_FS=y
My grub entry (hda2 is my root partition) kernel (hd0,0)/vmlinuz root=/dev/hda2
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:
I have installed the Jack audio connection kit from [URL] The two listed dependencies, libsndfile and libsamplerate are installed and everything seemed to go well, except it's not listed in the KDE menus. But that's Ok. I can start it from /usr/bin/jackd But no I can't because I get these error messages:
oot@ed:/# jackd -R -d alsa jackd 0.116.2 Copyright 2001-2005 Paul Davis and others. jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with System V SHM support. loading driver ..creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit control device hw:0 ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode cannot load driver module alsa
Recently I installed a Linux distro (Pardus) which boots using initramfs. I am completely novice here. In the former configuration I used lilo to boot OpenBSD, Debian and W2k (it is easy for me to configure lilo to boot OpenBSD). But initramfs is a something completely new for me. As I understand it is a virtual file system with a standard directory tree and the information stored on that system is used (to boot the kernel?) to mount the true (physical) root device. The first question is how to properly describe a system (kernel image) booted with initramfs in the lilo.conf.
this error spams about 100 times, then the scanner does indeed work. So I'm not completely broken, but the error messages are of concern, and it slows down the process of scanning for the time it takes to do the messages.
Error in console:
libusb couldn't open USB device /dev/bus/usb/001/001: Permission denied. libusb requires write access to USB device nodes.
I JUST registered here as I have not used Linux in several months. Linux and I have been and off and on relationship, but after I realized Ubuntus limitations Ive pretty much only dealt only with Debian (on PPC as well as x86, and also some Suse on x86).
Anyway, so I just picked up a couple Sun Ultra 5s for free. One had 256MB RAM (4 x 64MB), a 4.3GB IDE HD (no SCSI in the Ultra 5), and booted fine in Solaris up to the login screen at which point it wasnt really any use to me since I dont know the login name or password, and really want to run Linux anyway. The other I am told needed a firmware (chip?) and basically didnt do much more than power on. However, it had a 40GB HD and 2 x 128MB RAM modules. So, I replaced the 4.3GB drive with the 40GB, and replaced 2 of the 64MB RAM modules with 2 128MB modules, for a total of 384MB RAM.
BTW, both machines have the 270MHz Ultra1 CPU. Anyway, I used my main Windows x86 machine (which Im on now), downloaded the Debian SPARC net install, and burned it to a CD. Put the CD in the Ultra 5, installation proceeded nicely, though with one disconcerting message stating the urgency of which a reboot was required (though still telling me to wait for installation to finish). I mean, the whole installation process basically went perfectly except that one odd message.
So, when install is complete, I choose finish installation, the machine reboots, ejects the CD, and then ultimately get a message saying "cant open boot device". I am very new to Sun hardware, and am by no means an expert to Linux. The only thing Ive really tried so far is to type "boot hda" which only causes the same message to appear.
From previous experience, I have written on paper the info for all of my partitions. So I think my Debian install is sitting there waiting to be utilized, but the Sun hardware is oblivious to the fact that theres a perfectly good OS on the machine yearning to be booted.
VFS: Cannot open root device "<NULL>" or unkown-block(202,17) append a correct "root=" boot option Kernel panic not syncing VFS: unable to mount root FS on unkown-block(202,17)
I have a Dell xps with a dual core, 8 gigs ram, a primary hard drive with vista on it, and a secondary with linux in its future. It starts loading vmlinuz but ends up with the kernel panic before anything else. I am able to install earlier cores (5-8) and vista recognizes the ram just fine.
I got a problem with my kernel. The initramfs source is busybox, python and gcc from ubuntu. The busybox have i compiled it self. Python and gcc is from /usr/bin. I gonna install my kernel on a i586 machine. Old yes. On the xTerm (termial) it stand "root device 8,1).
Quote:
VFS: Cannot open root device "sda1" or unknow-block(0,0) append a correct "root=" boot option; here are the available partions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)Pid: 1, comm: swapper Not tainted 2.6.38.3 #1
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
Currently running rc2. Downloaded 11.2 final DVD, md5sum is good, burned DVD, YaST says media check is good. (And for completeness burned a second DVD and get the same problem.)
On booting from the DVD I select "Installation" - a kernel loads and starts checking available h/w devices then crashes with the above message.
Followed by Please append a correct "root=" boot option.
Tried with root=sda1 (partition that is /) and only change is unknown-block (0,0)
My best guess is that I have EXT4 (did a clean install of RC2)? And/or I dont have a swap partition?
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:
I have been working with a project pc. I have a new HD loaded with Linspire. After loading the o/s I replaced the motherboard and cpu. I now have a Biostar A780L (Didn't see it listed on the HCL) and an AMD Athalon II Multi-Core Processor. Now when the pc boots I get an error:VFS: Cannot open root device "343" or 03:43 append a correct "root" boot option Kernel panic: VFS: Unable to mount the root fs on 03:43 I tried reloading the o/s but the disk won't read from the DVD ROM. Checked my BIOS and it appears to me that it should read from the DVD ROM first but it goes to the HD and tries to load the o/s there.
When 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.
I'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) .....
ubuntu 9.10 is not booting shows Gave up waiting for root device.", (initramfs). how to boot normally from this problem. The problem is coming from installed system.
I've installed squeeze and wheezy on an old Toshiba Satellite 210 CS laptop with 48MB RAM and a 20GB IDE harddrive.Grub2 won't boot at all and stops with a "error: cannot allocate real mode pages". The solution to that is to use the grub-legacy package.The boot then fails with "waiting for root device" and drops to an initramfs shell.
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?
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
From 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:
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]
Reboot and select proper boot device or insert boot media in selected boot device and press a key. I got this error after: Reducing my Windows 7 partition by about 100gb. Creating a new partition (100gb) and copying my Ubuntu partition (10gb) to the new partition. After it was copied, and pasted, the original partition was deleted. I now had two partitions a new 100gb Ubuntu partition and a 600gb (or so) Windows 7 partition.
All of this was done using a bootable USB with Ubuntu 10.10 and GParted partition editor. Now when I boot I get the "Reboot and select proper boot device or insert boot media in selected boot device and press a key." error.
