Wipe and Image from PXE
-
@MattPayerle said in Wipe and Image from PXE:
That said, when scheduling a task, the first option is “Schedule Shutdown on completion” Anyway to add another option that is “Schedule reboot”? This would allow me to schedule items one after another, with the auto reboots in the middle and it would be somewhat automated.
I don’t think I’m following what you’re getting at. Image deployment tasks reboot afterwards by default. Shutdown and reboot are options for snapins already.
-
@Wayne-Workman Ok, so then it is just a learning curve then. It didn’t specify that a reboot was built in. So I can stack tasks against a host (once registered) to do a Normal wipe, and then deploy image. The image below shows the checkbox to shutdown, so I wouldn’t need this, I could leave that unchecked because it would reboot automatically as you say, which is awesome.
Also, there might be an issue with Normal wipe. If I use this basic task (under advanced tasks for each host) OR I create an iPXE menu option as you outline here: https://forums.fogproject.org/topic/7407/dban-booting-into-ad
It halts at this:
This works just fine for a full wipe and fast wipe, I can see it do the work as it does 4 passes, or a quick wipe. But for some reason, normal does this. Thanks again, I appreciate it.
-
@MattPayerle In the picture you posted, it appears normal. It takes a really long time to write zeros across a big drive. If anything, it would indicate an issue with full-wipe, because full-wipe should take x4 longer than normal wipe. @Tom-Elliott.
-
@Wayne-Workman Ok, I let that process sit overnight on a normal wipe and it never did anything. When I did the Full wipe, the process started right away and moved through the blocks, 4 times. It’s on a VM with a fair amount of RAM and CPU and a small drive, so it didn’t take a long time for the full wipe, but the normal wipe never seemed to start at all. Thanks for any insight.
-
@MattPayerle Ok then, you’re right there is a problem. What version of FOG are you on?
-
@Wayne-Workman 1.3.0 RC 5. I tried doing the update to RC 7 but it isn’t pulling properly from git. Do the git pull and installfog.sh and it does the installation, and completes, but the version doesn’t change. Running on Centos 7.
-
@MattPayerle Wherever your repo is that your working with (the fog repo), just delete it and re-clone the whole project.
-
@Wayne-Workman Ok, great tip on that. I am now up to RC-8.
I went ahead and imaged a machine, and then kicked off the normal wipe. It sat at the same screenshot I sent earlier for about 30 minutes, and then shutdown, but I didn’t see any messages, or might have missed them that it was wiped. Regardless, it does wipe the drive because it doesn’t allow it to boot to the hard drive. Perhaps verbosity could be turned on for this? I can use quick wipes for most other things, but it also seems like the full (4 pass) wipe took about 15 minutes long, so I figured this would take about 1/4th the amount of time, but it took nearly twice. So one or the other must be fouled up somewhere. No major rush for me for a fix, but wanted to illuminate a possible bug. Let me know if there is anything else you can think of or need me to test with it, happy to help out where possible.
-
@MattPayerle Can you make a new thread about the output and normal wipe? We are willing to help but this is way off topic of the thread title.
-
@Wayne-Workman Agreed, I figured I should file it as a bug anyway. Thanks for the help here. I’ll post shortly regarding this.
