Kernel panic - not syncing: VFS
-
@Data31337 FOG should detect the arch and send out the right image x64 vs x86. But you may be on to something. Let me check to see if the 745s are x64 compatible. Fog should send out bzImage_32 for a 32 bit system and init_32.xz for 32 if something gets mixed up and the init doesn’t match the bzImage then this error will be thrown.
[edit] The 745 supports EMT64 not sure if that would cause any issues or not, still researching.
-
@Data31337 Seems like the 745 some kind of 32bit/64bit system. I found a couple of posts on the internet which state that this machine is actually capable of running a 64 bit OS. As well the manual all CPUs have EM64T.
Looking forward to see if the error goes away if you force to boot with bzImage32/init_32.xz - maybe the 64 bit support is just fake…
[edit] Interestingly enough I just found a debian kernel package for those EM64T CPUs… Trying to find out what this is about. [/edit]
-
@Tom-Elliott Could you please build a kernel with CONFIG_MPSC enabled to see if this is helping here? I had no idea this did exist in the kernel.
As well I am wondering if we should add CONFIG_MK8 - although I am not sure if all those options would work in the same kernel binary. Haven’t tried it myself. Just doing some research on the web. -
No problem, I was following the other thread and noticed he got it working using the dnsmasq. Would this be something recommended to try out? As of right now its just a fully updated WebUI/svn/FOG and my experience with dnsmasq isn’t the greatest but I can learn.
-
@Data31337 Please don’t go for dnsmasq. I’d even suggest the other guy to switch over to ISC-DHCP as dnsmasq still does not properly support UEFI or even BIOS/UEFI together.
I am almost absolutely sure that dnsmasq wouldn’t make it work for you! Please let us know which boot file you are using.
undionly.kpxe? -
Sorry if this is a dumb question but how can I find out? Is there a log file I can check to see which one is getting pushed out? Configuration wise, I haven’t changed anything.
[edit] I am able to get to the FOG Menu once again, where as last changes I was not able to, but when I select anything it displays the same Kernel panic - not syncing error, along with device descriptor read/64, error -71 [/edit]
-
@Data31337 Do you use FOG as DHCP server as well or do you have a different DHCP in your network? Maybe you have two DHCP servers which would explain why you sometimes get to the menu but sometimes not. Please run
sudo grep filename /etc/dhcp/dhcpd.confon the FOG server and post a picture here.I am wondering about the
device descriptor read/64, error -71… Can’t remember having seen this ever. Can you please post a picture of that as well?
[edit] A well, that seems to be an (unrelated) USB error… probably save to ignore if you don’t use USB NIC [/edit] -
We have DHCP setup on a Server 2008 R2 VM along with ADDS if that helps. And then you were also correct with the USB Error, I had a USB Stick with the FOG client on it that was still plugged in. I think it was getting the error because it wasn’t recognizing it.
[edit] DHCP is pushing out the pxelinux.0 [/edit]
-
@Data31337 said:
DHCP is pushing out the pxelinux.0
Well then, change it to
undionly.kpxeand I am almost certainly sure that things will work then! -
@Data31337 said in Kernel panic - not syncing: VFS:
[edit] DHCP is pushing out the pxelinux.0 [/edit]
Great find. It looks like legacy iPXE stuff [ edit legacy syslinux] bit us twice in a short period of time. Just so we know where, where did you get the instructions to use pxelinux.0 from in dhcp?
-
Haazah! You were correct. I reset the setting and it boots to registration and doesn’t get hung up!
Again, I appreciate all your hard work in figuring this out and helping me out!
-
@Data31337 Please identify where you found the guidance to use pxelinux.0?
-
And I was staring to get worried it was something in the code.
-
It was in one of the old installer files, before I upgraded to trunk (Possibly in 1.2.0, or 0.32 which were the only 2 older generations I had installed along with older wiki page).
Please everyone take my up-votes you guys have been amazing help while working through this!
-
@Data31337 Thanks for the feed back. I was trying to drive at was it posted on a fog wiki somewhere. If it was we need to get that removed asap. But it looks like you had it from another source. I’m just trying to avoid this issue for the next guy.
If you run into FOG issues again, don’t forget we are here to help.
-
Oh, my mistake, it was a administrator error, it was in the installation text when configuring the ./installfog.sh in the beginning, I didn’t read through the updated DNS steps, and left it to the previous DNS setup. I just ran through it again trying to find the step and it looks like its been corrected.
-
Hi,
I just updated from 1.2 to (Running Version 1.3.0-RC-1 SVN Revision: 5936) and since then when I try to quick register a host or just check the compatibility of a client with Fog, I am getting this message:
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
I am using a dnsmasq environment.
Honestly I don’t know where to start to get this solved. Any help would be greatly appreciated.
-
@George-Lebay First let me shame you with you should start your own thread, because your conditions may be different.
Where we’ve seen this is if someone is using an old version of the iPXE kernel. Everything will work except when you try to boot into the FOS engine (the linux OS that captures and deploys images on the target computer).
Since you are using dnsmasq and dnsmasq uses the .0 files (like undionly.kpxe.0) I would have to ask this
- What do you have configured for dhcp option 67 {boot file} in dnsmasq?
- How did you create the .0 file in /tftpboot? Did you just copy undionly.kpxe or did you create a link from undionly.kpxe to undionly.kpxe.0?
-
Thanks for the quick reply. I understand I should have started a new thread. Sorry about this. I don’t know what to answer to your first question. Can you be more specific on where I can find this information (dhcp option 67 {boot file} in dnsmasq) ? My Fog configuration have been running smoothly for several years and I havent made any modification for a long while and I don’t have a great knowledge when it comes to Linux or Fog. About the other question, I created a link from pxelinux.0 to undionly.kpxe. This was done way before I made to update to Fog 1.3.
For what it’s worth, in the ltsp.conf file, the boot filename line is set to : dhcp-boot=pxelinux.0 -
@George-Lebay change pxelinux.0
