Adding Images Back in
-
The way the system works.
rec.img.000 needs to exist in the image path AND sys.img.000 needs to exist in the image path (/images/Optiplex9010I5Catia/{rec.img.000,sys.img.000})
If rec.img.000 does not exist, that’s perfectly fine as it just things it’s a single partition image. However, if sys.img.000 doesn’t exist, it can’t image because there’s no data to image.
Remember, linux is also case sensitive. The difference between Optiplex9010i5Catia and Optiplex9010I5Catia could cause things to stop as well.
-
Checked Case sensitive and that is fine. Checked and verified that rec.img.000,sys.img.000 are both present and they are. Can root be the owner on the rec and sys?
[url=“/_imported_xf_attachments/0/973_ScreenShot543.png?:”]ScreenShot543.png[/url]
-
Is the Path in the Image setting set to /images/Optiplex9010I5Catia
-
Yep.
[url=“/_imported_xf_attachments/0/974_ScreenShot544.png?:”]ScreenShot544.png[/url]
-
Last question(s),
Is this image of partimage or partclone format?
Can you run the task as a debug mode. When at prompt, type fog and press enter. Once it fail’s, break out (CTRL+C) and cd to /images/Optiplex3010I5Catia/
Thank you for the patience and understanding.
-
It is a partimage and new development. When it came up with the original error telling me that it was going to restart - I pressed ctrl -c and it rebooted and went through the entire image process - and successfully. I am going to try it again.
-
Ok did it again. Ignore the ctrl-c part … It must have just timed out and rebooted. It errors on first boot and then goes and images once it reboots itself.
-
Sounds like you’re having issues with NFS if you can try and restart the NFS service that would probably help out
-
Restarting NFS didn’t seem to help. Not horribly concerned about this one - it only shows itself to us in IT so waiting for one additional boot cycle isn’t that big of a deal. It looks like we are also getting stuck on the FOG boot menu screen though. If I hit enter on the boot from HD then it just starts the timer over. If I hit escape it blinks a “_” in the top left corner.
-
try changing the exit type
-
Changed it through all 3 and no luck. Grub brought it to grub prompt. Sanboot gets stuck on fog screen and exit just puts up the blinking “_”.
-
Any more ideas?
-
will the computer boot with the network cable unplugged?
-
It’s making me think the partitions are in GPT format
-
Yes it will boot without network cable. GPT is possible - if so what can I do? I will check on GPT.
-
The debug task, there is a program I’ve had in the init for a while called fixparts.
run
[code]fixparts /dev/sda[/code]Make the adjustments as necessary and save. If you do this from an Upload-Debug task, your image will be able to be pushed to clients as well. Once saved all you’ll need to do is run:
[code]fog[/code] And it should upload your data. Then, hopefully, your system will boot properly. -
Two questions.
I have it in debug mode - what do I do now?
Second - do I need to do this to every machine - different image - or just once on a single machine?
[url=“/_imported_xf_attachments/0/989_ScreenShot548.png?:”]ScreenShot548.png[/url]
-
Is there an instruction set on how to use this somewhere?
-
The easiest I can give is to just press the letter w.
-
Do I need to do that on every computer or just a one time deal?
