FOG Imaging Not Saving
-
@dpotesta50 Its the other way around, its the target computer disk that is in question.
One way to find out is to schedule a debug capture. Just click on the debug check box when you go to schedule the capture. When you do that pxe boot the target computer after a few presses of the enter key you will be dropped to a linux prompt on the target computer. Then just key in
fogand it will single step you through the capture. When you get to the error, watch what partclone says. Also right after the error, press ctrl-c where it will drop you back to the command prompt, then we can inspect the partclone.log (on the target). It should be in /var/log (on the target). -
Prior to uploading the image, in Windows 10, proper shutdown? Win 10 has that weird sleep boot and depending on which build it is you might have to disable it in the power options FYI. Also there is cmd option to use to properly shut it down prior to uploading the image.
-
@george1421 Sorry to the dumb question but is the target computer the device I’m imaging FROM or imagine TO (The FOG server)
-
@dpotesta50 To flip the question back at you, what computer were you on when this error was thrown. Its that device that has disk issues.
-
@jgallo I think if this was the case, partclone should complain right away the disk is dirty and can’t be cloned. I think the error above is generated after partclone actually starts copying the image. (but I’ve been wrong before…)
-
@george1421 That was the laptop I built the image on. It was at the end of the clone cycle.
-
@dpotesta50 Ok then setup a debug capture and watch partclone as it runs. If your fog server has enough space, partclone should print quickly on the screen what is wrong and then hit the ctrl c at the next debug pause and inspect the partclone logfile.
-
-
@dpotesta50 Keep going its a ways down yet. But now you can see each step fog is doing.
-
@george1421 Looking at log files.
There are a bunch, which one do I need to examine? -
@dpotesta50 If you look at your very first post it mentions /var/log/partclone.log. You can key in
tail /var/log/partclone.logto view the last few lines of that log file. If you need a few more lines you can dotail -30 /var/log/partclone.logto show the last 30 lines.Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
-
@george1421 I will tell you a trick so you can remotely interact with FOS.
- Give root a password with this command
passwd. Just give it an easy password likehello. Do this from the FOS debug console. - Get the IP address of FOS target computer.
ip addr show - Connect to FOS using Putty from a windows computer. Login with
rootandhelloas the password.
Now with putty you can cut and paste commands to the FOS engine. FOS runs in memory, so when you reboot FOS all settings or changes are gone. So this password reset is only temporary.
- Give root a password with this command
-
@george1421 Well…that log file is not there. I sorted the directory by name, no log file.
-
@dpotesta50 Where did you check for that partclone.log file? On your server (wrong) or on the client itself? Although you can get access to the client via SSH there is a much easier route of just taking a video/picture of the error message when it is right on screen in that blue window. Post here and I am sure we’ll figure things out.
-
@sebastian-roth Okay so if I look for the log file on the laptop I’m imaging FROM, how do I do command line navigation? I CTRL-C’d to the command prompt which is blue and says "[Thu Nov 9 root@fogclient /]#
-
@dpotesta50 Trying chat for faster turnover… see the speech bubble in the right top corner of the forum.
-
-
@dpotesta50 Alright, got that. See here: https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit
-
@sebastian-roth I went ahead and rebuilt the image. Ran checkdisk and disabled FAST STARTUP as instructed. So far, the image is still uploading. Before it was done in less then a minute. Now it’s been going for about four or five minutes and it’s only at 13% so something is definitely different.
-
@dpotesta50 It should have told you right away that the disk was dirty and not started at all. So this surprises me a bit. But we see this common with Win10 (not being shutdown properly). We are glad you got it uploading now.
