kernel panic after upgrade

ch3i

@fry_p said in kernel panic after upgrade:

I have this too. 7985 Git. Optiplex 990’s and Optiplex 5040’s both fail when trying to register.

Edit: I would also like to know if there is a way to revert or roll back through trunk. I am an idiot and have no test environment, so anything like this issue impacts production heavily.

svn update -r relase_number

fry_p

@ch3i said in [kernel panic after upgrade](/topic/7686/kernel-panic-after-upgrade/3

svn update -r relase_number

I just tried and got this error

fry_p

@fry_p said in kernel panic after upgrade:

@ch3i said in [kernel panic after upgrade](/topic/7686/kernel-panic-after-upgrade/3

svn update -r relase_number

I just tried and got this error

Never mind I was in the wrong directory lol

Tom Elliott

@fry_p You need to be in the root of the trunk, not bin.

So:

cd ~/trunk
svn up -r <someversionnumber>
cd bin
./installfog.sh -y

george1421

On point of the original post.

What did you upgrade from and to?

Where I have seen this error about not syncing vfs is when people upgrade from pre 1.x to 1.2.0 or 1.2.0 trunk. They forget to update dhcp option 67 {bootfile} from pxelinux.0 to undionly.kpxe. The old version of iPXE doesn’t like the way the inits are compressed.

Bob Henderson

@george1421

Updated from whatever the last git release was to 7895 . Option 67 is set to undionly.kpxe, as I had been using trunk before. Same issue.

Is there a way to roll back if you’re using git instead of SVN?

george1421

@Bob-Henderson Rolling back releases is not typically advised since the database also gets updated between certain releases. These changes are not rolled back when you install a previous git/svn version. There is a risk of having a broken FOG install.

I would open a new thread because your situation may be unique. If you have a problem the devs need to get it worked out. They are pushing to get 1.3.0 released, and if you have a bug, then so will someone else. So it needs to get sorted out, please.

Bob Henderson

@george1421

Makes complete sense.

Already have one open, as someone else is having the issue as well. He seems to have found a likely culprit, where the FS is setup to ext42 instead of ext4… More info here:

https://forums.fogproject.org/topic/7690/kernel-panic-on-quick-register

Sorry, didn’t mean to threadjack, but it appears to be the same problem. Can we merge?