I wanted to try out the new Ubuntu 10.04, but since I don't have any CD's available I thought I could use my 9.10 CD and upgrade from it.
1. Installed 9.10 on the entire disk. 2. Went to update manager(?) and clicked the button to upgrade to 10.04 3. It successfully downloaded all the files. 4. When installing the new files it suddenly said that it failed to update, and it stopped. Then I went to do a hardware test, but none of the menus were working.
I had to do a manual shutdown, and reboot the computer. This time I was met with an error "Unable to mount root fs".
I figured the upgrade was the problem, so I reinstalled 9.10 to try without upgrading. 1. Reinstalled 9.10 on the entire disk. 2. Went to update manager(?) and started the normal update for 9.10 so the system would be up-to-date. 3. Same thing happened now, it fails to update and it makes my computer useless.
I've already checked my hardware for errors, can't find any. I've checked the CD for errors, can't find any. I had 9.04 on the same computer a few weeks ago, and it was rock-solid. Worked like a dream. I'm using Win7 now though.
I had 9.10 installed on my IBM Lenovo Thinkpad, x301. I was performing updates as normal, and chose the Upgrade button to upgrade me to 10.04. Everything started fine, but upon reboot, no bueno, Kernel Panic!
The exact message was "Kernel Panic ubuntu - not synching VFS Unable to mount root fs".
I thought this was a grub issue. Since grub2 now is installed... But it was not. I think it ended up being a problem with some of my configuration files.
I have three kernels I tried: 1. 2.6.32-22 2. 2.6.31-21 3. 2.6.31-20
The first threw me into the kernel panic. The second would hang on "init crypto disks" The third would hang on "checking battery state"
I noticed (from reading another thread) that while these are loading up that you can click on alt-ctl-F1 thru F6 and get prompt. (I also had my home directory encrypted, thought that was part of the problem, but it wasnt).
Once I get passed the loging, I am able to poke around. I tried manually start Gnome via "sudo service gdm start", but it failed. Said it was missing a configuration file. Then I tried on "sudo dpkg-reconfigure gdm" and it would not work. Saying some configuration files are missing or broken. It also said something about dpkg --configure -a, I am assuming this configures everything...
So I tried "sudo dpkg --configure -a" And selected 'y' to every option. Which basically installs the package creators default settings, and viola! Works.
Just wanted to share that knowledge for the other stuck in the upgrade hell.
Normally I would just copy my files off and reinstall, but it was encrypted... Another headache. I guess good in case someone stole my laptop.
I've been having problems with the system ever since I replaced the motherboard. Moving slow and just generally acting 'wonky.' Well the other day I reached my frustration limit and wiped the HDD. Up to this point the HDD had been in 2 partitions, one for the DELL diagnostics and one for the OS, XP Pro.
I decided that I wanted to set up the system in a dual-boot during the rebuild so I created a two partitions using the Windows install. Partition one is the DELL Diagnostic partition, partition 2 is the XP Pro partition and partition 3 is to be the Linux partition. All seemed to go well with the Windows install. I got the OS up and running and got all the updates done and drivers installed.
I only have the one HDD in the system so I was going to have to make this dual-boot off of one HDD.
I had previously, within the past week or two, downloaded the .iso and created the disk for FC11.
I went through the install process and successfully installed Linux on the 3rd partition, or so I thought. When I attempted to boot into Linux I got the Kernal Panic error.
My grub file as it exists now is:
If I leave the file as is, I get the kernal panic error but the splash image works fine. If I try to change the 'splash image' and 'root' references from '(hd0,2),' then neither works.
I can boot into Windows XP from the setup as it is now.
I if I boot using my LoaS (FC 11 made at the same time as the images for the cds were downloaded) I can see the hdd and multiple partitions. There seems to be a 'boot' partion, the Linux OS partition, a swap partion, as well as the Dell and XP partions. Now I've tried changing the references in the grub file to reflect the different partitions, basically I've tried 2, 3, 4 and 5, everything but 0 (the dell diagnostics) and 1 (the XP Pro).
I've also re-wiped the HDD and started the whole process over from scratch, thinking maybe I'd hosed something up the first time, but being a firm believer in 'Always do what you've always done and you'll always get what you've always gotten,' and that one of the definitions of insanity it keep performing the same actions over and over and expect different results, I seem to be at impasse here.
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 am running FC13 on a fairly old PC (PIII 500MHz, 384MB RAM, 10GB SCSI disk). It works fine using kernel 184.108.40.206-112.fc13.i686.PAE. After a series of recent updates the system now also has a new kernel 220.127.116.11-56.fc13.i686.PAE.
/boot/conf/grub.conf contains: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) code....
When I try and boot to the newer kernel I get an error like:
Kernel panic - not syncing VFS Unable to mount root fs on unknown block(0,0)
I read on the forum about a similar problem where the fix was to insert the line
but this file doesn't exist and so the boot then hangs with no messages, so I took this line out again. Here is contents of /boot:
$ ls -l total 21148 -rw-r--r--. 1 root root 111391 May 27 04:06 config-18.104.22.168-112.fc13.i686.PAE -rw-r--r--. 1 root root 112291 Sep 15 04:32 config-22.214.171.124-56.fc13.i686.PAE drwxr-xr-x. 3 root root 1024 Jan 23 2010 efi code....
As you may deduce from the above I haven't used the system much so the auto-update hasn't run for several months.
Any help on running / installing the newer kernel appreciated. Note that I am trying to install a wireless LAN card and am following instructions here: url
I got as far as
cd /lib/modules/`uname -r` ls -l
[root@localhost 126.96.36.199-112.fc13.i686.PAE]# ls -l total 3300 lrwxrwxrwx. 1 root root 51 Jun 3 00:52 build -> ../../../usr/src/kernels/188.8.131.52-112.fc13.i686.PAE drwxr-xr-x. 2 root root 4096 May 27 04:08 extra drwxr-xr-x. 11 root root 4096 Jun 3 00:52 kernel code.....
so I have the src files for the newer kernel not the one I am running. I thought it best to stop and think (and ask for help!) rather than break a working machine (but with no wireless LAN!)
I have a Compaq Presario 8000 with an Nvidia Geforce FX 5950 Ultra on which a year ago I upgraded from Fedora 6 to Fedora 9, and this broke the Nvidia driver, since Fedora 9 was shipped with an X server incompatible with Nvidia. I went back to the 2d driver to get X working, and it sat that way for the past year. But recently I wanted to do some 3D work and decided to install Fedora 12, which hopefully has an X server that works with Nvidia.
I decided to do a cold install, re-partitioning my 80G hard drive at the same time. I backed up my data, ran the install CDs with no errors, and booted the system, with an immediate kernel panic: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Doing a Google search, I found over 8,000 hits for that message combined with the keyword Fedora. Several of the hits were on Bugzilla: [URL] I then booted the install disk, chose rescue mode and did - chroot /mnt/sysimage
Ubuntu(10.04) was working fine, then some program crashed or something, and I just switched off (power offed) the computer. When I restarted it, this sort of stuff comes:
mount /dev on /root/dev failed : No such file or directory
and some more lines like that, and then 'Busybox' starts with [intramfs].I booted Ubuntu from a pen drive and ran fsck on the main partition. I just pressed 'y' for a long time (it asks stuff like should it continue repairing or something), and then it was done. I restarted the pc and it booted normally - it looked as if everything was fine.I started google chrome, and it said it couldn't find a personal config file .. ok. Then I tried opening a folder - nothing happens. The system monitor doesn't open, and windows that do open eventually are completely blank. I restarted the pc (this time by doing the normal restart), and it gave me the same 'Busybox' thing.I did the same procedure again, and got the same results. (ubuntu boots, programs dont work, then I restart and the Busybox thing comes again)One More Thing : The Ubuntu installed on the hard disk had all the recent updates (including the latest linux kernel) while the pen drive thing was around 2 months old I think. So maybe that's the cause?
I decided to try to do the 3 distro upgrade stretch from 8.04 to 10.04 this weekend and now I am hung on 9.04 to 9.10.. The upgrade went swimmingly, but I hit a wall upon boot. When I try to load kernel 2.6.31-22 I am greeted with the following error:
[ 20.879845] ACPI: I/O resource vt596_smbus [0x400-0$407] conflicts with ACPI region SMOV [0x400-0x406] Mount of root filesystem failed.
A maintenance shell will now be started ... After doing some digging I found this thread which appears to be similar in the inability to mount the filesystem. However, it does not mention the ACPI error. I tried everything in that thread; verifying device ID's, editing fstab options; running a filesystem check, and flipping the UTC option in the rcS file but nothing worked. The OP of that thread eventually did a fresh install of Karmic; but I would rather not have to go that far.
since running update manager on my daughters net running 10.04 netbook on boot up I get the following on the screen
mount: mounting /dev on /root/dev failed: No such file or directory mount: mounting /sys on /root/sys failed: No such file or directory mount: mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn�t have /sbin/init.
Doesn't seem to matter which version, every time I try to install Software raid on an Ubuntu server system, it blows up with this error. Seems I've had trouble for several versions.
mount: mounting /dev/disk/by-uuid/f35415ee-4c14-4eb1-995f-f19fbcd760c7 on /root failed: Invalid argument mount: mounting /dev on /root/dev failed: No such file or directory mount: mounting /sys on /root/sys failed: No such file or directory
I've done it on Centos Fine, and followed the many different instructions I've seen for Ubuntu. The only luck I've had was with bios raid, but I would much rather let Mdadm handle things.
ubuntu-10.04.2-server-amd64 CD install AMD 1055T 6Core 4GB ram Asus M4A88TD-MUSB3
I install both as letting Ubuntu decide partitions for one drive, do the same for the other, and create a raid, and do them from scratch. No dice, same problem. I've tried that one as logical and as primary too. No difference. Something just doesn't like booting from a raid 1 Mirror. I've tried installing grub on both HDDs (sda1 + sdb1)I've tried several CDs, burned from several machines. Re-downloaded from Torrent and from the website. The DVD drives work since I purchased new DVD drives for both one workstation and the server. Things install fine under CentOS, software raid comes up.
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.
I was using 9.04 for a while because it was working for me, I decided to upgrade yesterday using the Upgrade button on synaptic to 9.10. Now when I boot I get an error message: Code: chroot: cannot execute /etc/apparmor/initramfs: No such file or directory Mount of filesystem failed. A maintenance shell will now be started. CONTROL-D will terminate this shell and re-try I want to try to fix the problem so I do not have to do fresh installation.
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.
I'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 posted a similar problem sometime last week...but a little has changed(mainly I can access my files now): I recently performed the auto upgrade to Ubuntu 10.04 and upon restart of my machine I am presented with 3 screens. The first is a simple "GRUB loading". The second is "mount: mounting none on /dev failed: no such device". The third screen is a series of initializations, i.e. /dev/sda1:
clean, (number of files), (number of blocks) *setting preliminary keymap... and so on until it hits the line: *checking battery status
at which point it will cease loading until i press the power button. The next thing that occurs is it kills all the processes it just initialized and shuts down the computer. I read that this is likely a problem from loading the wrong kernel and I can get into my files (using a boot 9.10 boot key). The problem is I don't know what files to change in order to get my system booting the right kernel.
I have configured the remote installation of Fedora 13 with kickstart with nfs installation method. All work ok until I boot the Fedora 13 client system.
Fed13 client system receives the IP address from dhcp, receives the loader, loads vmlinuz and initrd.img from tftp, load anaconda, configures the network and dev eth0, mounts nfs server to load kickstart file, loads kickstart file (language...) but when it tries to mount nfs server to install from Fedora 13 installation tree it fails.
First, I thought that I had an error on my NFS configuration but I was wrong. I opened tty with ALT+F4 on the Fedora 13 client and I sew this error:
Is this a bug or can I modify anything to correct this error? How?
I upgraded 9.10 to 10.04 via the web. The program announced it would take several hours, and when I came back to check, computer was off (kids?). Anyway, machine boots and 10.04 starts, but then blinks a few times and goes to a prompt. What should I tell it?
I have a 10.04 disc too, but it won't run from that either (Cannot mount dev/loop0 on filesystem.squashfs failed). Same message when I tried to start a nearby Windows machine with it. Disc "verified" when I made it. What's with that?
somehow got Ubuntu 9.10 set up dual boot on my Vista laptop. I installed it somehow off the live cd. Everything working fine and then I decided to update from the update manger to Ubuntu 10.04 (dummy me)!
Got half way through installation and system froze for more than an hour. Had to shut down computer. Now when I select to boot to Ubuntu, computer freezes with this message:
[ 1.068088] Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(8,1)
Can anything, within reason, be done? Should I use windows to uninstall Ubuntu and then try to re-install? If so, can someone tell me how I might have setup dual boot off the live cd? Should I just flog myself?
I was trying to install winbind on a RHEL5 machine and I had to reboot the RHEL machine. When it came back up, I'm not able to log in as root or any other user.When I use root and give a random password, it says invalid username or password but when I use the correct password, I get an Authentication failed pop up box (under GUI). SSh window says invalid password for random passwords and the SSH window disappears when I type in the right password.Can you please let me know if I can somehow get back in by stopping any of the services
I am trying to install linux kernel manually, for this I had compiled linux-2.6.36 with minimum drivers and features. Note that ext2, ext3, jffs file system support and sd ata_piix drivers are set as inbuilt kernel modules.
I had two hard disk for my Intel x86 box sda and sdb. I have running linux on sdb from which I can access sda. sda has one partition sda1 as ext3 fs.
I had created following directories at sda1 root, bin, boot, etc, sbin
After compiling kernel, I had copied bzImage, system map files to boot folder. then using 'grub-install' I had installed grub on sda. after installation I edited grub.conf to setup kernel image.
After this I booted sda by changing HDD boot priorities,And wow I got grub prompt -- linux kernel booted but as soon as it tries to mount file system it dies with error,
I accept that I dont have binaries for init and no initialization stuff in /etc, but I think problem is I am not able to give correct rootfs to kernel.
I have compiled a new kernel 2.6.35 and I can not boot because same error : kernel panic - Unable to mount root fs on unknown-block(0,0). i have motherboard ga-p55a-ud3r and controlleris sata .now i use channel in ACHI mode. when i change it in ide mode it boots but in low graphic mode. then i have compiled modules again with support ACHI_SATA mdoe in xconfig of kernel. but same error occur.
i bought following server about some days ago :Supermicro X8DTi1u Super micro 2x 1TB Sata 2 i want install centos 5.5 64bit on it, i download centos 5.5 64bit from centos.org torrent link but when i want setup centos it says :kernel panic : not syncing : VFS: unable to mount root fs on unknown block(253,3)and also i set adptec raid in my bios and set raid 0 in adptec raid controller (my mainboard has onboard raid) i run any command you think like linux dd, linux all-generic-ide, linux noprobe, linux nostorage and etc but none of them does not work for ,e
I used make-kpkg to generate bzImage from 2.6.39-3-686. After update-grub and booting the new vmlinuz system. I get:
"kernel panic - not syncing: VFS: unable to mount root fs on unknown block(0,0)". grub.cfg shows new entry 'linux/boot/vmlinuz-184.108.40.206-686 root=/dev/sda1 ro quiet' but previous working shows 'linux/boot/vmlinuz-2.6.32-5-686 root=UUID=210a363d-c0ed-4005-b6e8-bbc aeb7abe54 ro quiet'
Am I missing a step? (or two?). Is it possible to do this from 2.6.32? Currently running Debian-220.127.116.11-i386-DVD-1, Squeeze, /release/current/ 20110626-15:45 on a SATA 1T hd.
I have a Dell Inspiron 1720 running Ubuntu v10.04 with a wireless card.My desktop is a Dell Optiflex running WinXP.The desktop is connected via ethernet cable to a Linksys wireless router. Certain folders on the desktop are set for sharing. Up until early last week I was able to access the desktop folders from the laptop with no issues.Suddenly I am now getting this error "Unable to mount location Failed to mount Windows share" whenever I try to access the desktop folders from the laptop.I suspect an upgrade is the culprit, but not sure.