Kernel Panic - Not Syncing(Lenovo ThinkPad Edge)
-
Sorry, my post didn’t see your post until after a refresh reread.
It’s not likely the server RAM is bad, but that the location the file is at on the server, maybe the disk is going BAD?
So the volume containing /var/www/fog/service/ipxe could be bad?
-
What would cause it to work with the old version but not 1.1.0? I’ll try on a different system we have here… Do you have any wikis or anything to assist with building the kernel? I’ve used linux for years… but never really have built a kernel…
-
[quote=“T3charmy, post: 30179, member: 24610”]What would cause it to work with the old version but not 1.1.0? I’ll try on a different system we have here… Do you have any wikis or anything to assist with building the kernel? I’ve used linux for years… but never really have built a kernel…[/quote]
It sounds like one of the disks in the server are going bad and not sending the init properly as you’re saying it’s happening on multiple systems.
Try redownloading the init.xz and init_32.xz to your fog server, if all is well things should start working again, if the disk is bad, chances are you’ll continue to see the problem.
[code]sudo mv /var/www/fog/service/ipxe/init{,_32}.xz /var/www/fog/service/ipxe/init{,_32}BAD.xz
sudo wget -O /var/www/fog/service/ipxe/init.xz https://svn.code.sf.net/p/freeghost/code/trunk/packages/web/service/ipxe/init.xz
sudo wget -O /var/www/fog/service/ipxe/init_32.xz https://svn.code.sf.net/p/freeghost/code/trunk/packages/web/service/ipxe/init_32.xz
[/code] Retry, hopefully all starts working again.Other’s check if the hard drive is bad.
-
I tried on another machine I got same error too. so init.xz/init_32.xz files could be corrupt? where can I get a copy of these files? If I need to… I can try another harddrive in the server and see if that helps…
-
[quote=“T3charmy, post: 30181, member: 24610”]I tried on another machine I got same error too. so init.xz/init_32.xz files could be corrupt? where can I get a copy of these files? If I need to… I can try another harddrive in the server and see if that helps…[/quote]
See Above!
[url]http://fogproject.org/forum/threads/kernel-panic-not-syncing-lenovo-thinkpad-edge.10794/#post-30180[/url] -
Hey! That worked. Looks like it was a corrupt init.xz file! Thanks for all the help! Now just have one small issue I gotta fix(forgot to set the operating system type in image).
-
[url]http://i61.tinypic.com/2m2j7yd.jpg[/url] Now we can get back to imaging these other 30 of 60 laptops!
-
Nice man, best of luck.
-
Or not… Got the first 20% of the image downloaded to the laptop and then it just rebooted out of no where saying the job was completed. Now we’re having the same old issue that we used to have back on 0.32(Unable to locate image store).
-
That’s quite possible that the storage location that’s containing the images are corrupt, or the files that “are” the images are corrupt.
-
Hm. Alright. We had this issue quite a lot on our old server which is one of the reasons we moved to new server … I guess worse case scenario we have to grab one the other laptops and remove it from the domain and reupload the image to server to see if that fixes is… Not sure that the hard drive on the new server is corrupt, but then again it is about 6 years old …
-
I could be bad, it may not be.
I use glusterfs as my storage location and saw, more or less, similar problems. The glusterfs filesystem destroyed my images to the point that I basically just wiped them all and started over. It wasn’t disk related directly, but the data was bad and would force partimage and partclone images to fail and random points.
-
Yea, we’re uploading the image again to see if that fixes the issue. Hopefully all goes well we got a week to do 30 laptops…
-
with the new partclone does it usually upload the whole hard drive? or does it only upload the data that’s actually there? we have 320 GB harddrive on the server but the harddrive we’re uploading from is a 500GB? I’m assuming it’s still like the old method that only uses what is used in image(which is 38GB)
-
That’s correct, unless you tell it to image in raw format.
