14

Diskless boot on FC17 fails when trying to mount nfs rootfs

view full story
linux-howto

http://forums.fedoraforum.org – Hello, I am trying to setup a FC17 diskless client to PXE boot and mount nfs the root file system. The first steps are OK: kernel and initramfs are properly tftp downloaded and the boot process starts fine on the client but it crashes with the following message: Code: VFS: Cannot open root device "nfs:134.158.16.7:/data/diskless/root" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: 0b00    1048575  sr0  driver:sr Kernel panic - not syncing: VFS : Unable to mount root fs on (HowTos)

sine's picture
Submitted by sine on 07/04/2012 – Made popular on 07/04/2012

Stories similar to Diskless boot on FC17 fails when trying to mount nfs rootfs

I'm trying to install opensuse using the internet install feature. After the loading linux kernel screen, I see a black screen with a lot of commands/steps. It keeps hanging at the line: [2.202543] [<c0804db73>] kernel_thread_helper+0x7/0x10

And at the same time, caps-lock and scroll lock lights on my keyboard are blinking. What does this mean?

I foolishly installed the newest kernel update... now I can't boot anymore.

Once I rebooted, grub presented me it's friendly console.

Hi folks.

Updated recently to kernel 3.4 and getting kernel panic on boot.

Code: Loading Fedora (3.4.2-1.fc16.x86_64) Loading initial ramdisk... [    9.224897] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) .... 3.3.x works fine, so I don't think it's a filesystem problem.

Please help!

What's up guys. I could use a little help with this if any one may know or seen this before..

Situation :

I am trying to get my kernel zImage smaller so it will boot, over time is got bigger and bigger, but am getting stuck on black screen after splash screen..

Here is the kernel log...

This was a new install of 10.04. It worked for 3 days and now the dvd won't mount. The dvd worked fine as I've used it over the past few days. I mounted an iso and since then, I can't get the physical drive to work. Now, when I try mount /dev/dvd /media/dvd/ mount: /dev/sr0: unknown device

Code: ls -l /dev | grep dvd

i did yum update yesterday.

after that when start my system boot failed.

Code: Error : kernel panic - not syncing VFS unable to mount root FS on unknown block(0,0)           PID 1 comm swapper not tainted I am able to boot system in recovery mode. But in recovery mode i need to press Ctrl-D to come out of shell

What i want is previous state of my system.

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

Diskless NFS boot 36 weeks 2 days ago

I've been struggling to get my diskless pc to boot using this guide.It seems the kernel is loaded properly from tftp but the root filesystem fails to mount. This is what I get:http://dl.dropbox.com/u/29192523/Screen … 044316.jpgThe server is Arch-based, it didn't work with an Ubuntu server either though.

Hi, New to Linux, I run the update-manager, and get the message that there's no more room in /boot. This is interesting, as I do recall having to update the kernel 'back in the day', but haven't done so this time. Anyway ..