Kernel panic - not syncing: VFS
-
Ubuntu 14.04
FOG SVN 7853I just recently upgraded with a clean install of FOG and am now running into the problem with the Kernel Panic - not syncing: VFS. Was wondering if anyone else has ran into this issue and how’d they fix it? I’ve been scouring the internet looking for solutions and most of them require reinstalling with a Rescue CD which I don’t exactly have. I have tried Updating/Upgrading Ubuntu and Rerunning the ./installfog.sh. Also tried downgrading the kernel.
-
This is the second or third one I’ve seen today. Not sure what is going on with the build. But the error basically says there is an issue with the init (virtual hard drive) to where its either damaged or not constructed properly.
Can you run
svn upto update your svn and then reinstall the update using the bin/installfog.sh script again. -
I know I updated my dev box today at 1p and it fixed an issue that was in the build at 6a EDT today.
Cross link duplicate issue
https://forums.fogproject.org/topic/7555/upgrade-to-trunk-kernel-panic -
I’m not sure of what the problem is, but I’m 99% sure it’s not related to kernel, and as this particular user is on current, it’s got to be some setting that’s a little borked at the moment.
-
I just updated it the svn last night, I will update the svn and FOG again today, if that doesn’t work I’ll check out the settings.
-
I think I forgot to add some details to the issue:
SVN: Updated to 5585
FOG: Revision 7881
Machines to be imaged: Dell Optiplex 745; HP DC5750S Small Form Factor -
@Data31337 are you using dnsmasq in your environment?
-
No, not to my knowledge, just DHCP and DNS on a Win 2008 R2 machine.
-
@Data31337 OK trying to draw a parallel with another thread with the same reported issue.
-
I’ve been following the other thread too, I noticed we are both trying to image the same style PC the Optiplex 745. One thing I noticed was that FOG is pushing out a 64 Bit version of BZImage & Init when I know the PC’s Ive been trying to image are 32 bit. I tried modifying the kernel’s in the configuration to push the 32 bit and I recieved a “Image not found” written over several different lines, I can get a exact error message if that would be more helpful.
-
@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?