I tried to apply the recommendation of question:
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
After running that command:
sudo mount --bind /dev /mnt/dev
I get this error message:
mount: mount point /mnt/dev does not exist
fdisk -l returns
/dev/sda1
/dev/sda2
/dev/sda5
do I need to mount sda2 and sda5?
Any info that can help me rescue that serve
How to chroot from live session to #! on diskAssumption: #!
hi
i have installed windows 7 then Ubuntu , all works find so far
after i installed windows xp , the grub2 got deleted ofc and windows xp was booting directly , so i repaired my grub
{
1 sudo mount /dev/sdXY /mnt
2 sudo mount --bind /dev /mnt/dev && sudo mount --bind /dev/pts /mnt/dev/pts && sudo mount --bind /proc /mnt/proc && sudo mount --bind /sys /mnt/sys
So I had the perfect Ubuntu 12 / Windows 7 dual boot set-up -- until I had to re-install Windows 7.
After the deed, GRUB2 was of course wiped out, thus my Ubuntu installation is rendered inaccessible.
I have tried these steps:
mount /dev/sda5 /mnt #This is where my Ubuntu installation resides.
mount /dev/sda1 /mnt/boot #Indicated by the `*` under `Boot` when doing `fdisk -l`
mount --bind /mnt
Hi i recently installed ubuntu 8.04 on my desktop and in the upgrades menu i gave upgrade to ubuntu 10.04.3 LTS but after installing it started giving me this error
[ 0.694063] Kernel panic - not syncing: VFS: Unable to mount root
fs on unknown-block(0,0)
Please help as i am new to ubuntu and also get back to me for additional info if required.
ubuntu kernel ubuntu-10.04 vfs
Desde un live cd.
sudo mkdir linux
sudo mount /dev/sdXY linux/
sudo mount -t proc /proc linux/proc
sudo mount --bind /dev linux/dev
sudo chroot linux/
grub-install /dev/sda
el grub está aca
sudo gedit /etc/default/grub
I have been dual booting Windows 7 Home Premium and Ubuntu 12.04 for several months now, and I recently ran into a problem where GRUB (or Burg) would fail to load. It gets stuck at the "GRUB Loading" screen and fails to boot. I also have Burg installed. I have reinstalled GRUB from a Live CD and the problem returned a week later.
Hello
just upgraded to kernel 3.4.3-1.fc17.x86_64 and it went panic after 2 minutes.
Now I get a kernel panic message when booting the machine:
Code:
Kernel panic - not syncing: VFS: Unable to mount root fs n unknown-block(0,0)
Pid: 1, comm: swapper/0 Not tainted 3.4.3-1.fc17.x84_64 #1
and the call trace which I'm not reporting.
Using old kernels gives me a filesystem error, requiring to ex
ok after following your suggestion this is what happenedcrunchbang@crunchbang:~$ sudo suroot@crunchbang:/home/crunchbang# TARGET=/media/sda1root@crunchbang:/home/crunchbang# mkdir -p $TARGETroot@crunchbang:/home/crunchbang# mount /dev/sda1 $TARGETmount: /dev/sda1 already mounted or /media/sda1 busymount: according to mtab, /dev/sda1 is already mounted on /media/sda1root@crunchbang:/home/crunchbang
Email this page
