Skipping chkdsk?
-
Yeah. I tend to swap between disables/enables as well as if/not-if and my own code gets thrown off like that all the time. I completely understand, haha.
Easy fix though! Might want to report it as a bug, as well.
-
[quote=“dvlsg, post: 4938, member: 1186”]Yeah. I tend to swap between disables/enables as well as if/not-if and my own code gets thrown off like that all the time. I completely understand, haha.
Easy fix though! Might want to report it as a bug, as well.[/quote]
Good idea. I’ll do that. I think Blackout is re-writing that portion of the code in .33 anyway, but I’ll go ahead and do it.Cheers,
astrouga
-
Oh, just a heads up (and I just noticed this) – we just ran a Full Host registration and Inventory, and that [I]did[/I] do a chkdsk, after I switched the setting in the console.
-
Doh! Well who knows then. I’ll see if that happens for me as well.
-
I just tested the “full host registration and inventory” and selected the option to image the system. Seems “chkdsk=1” is passed the append initrd line of the pxe configuration file for the host in this case. If I select the “quick image” option there is no “chkdsk” option in the pxe configuration file.
astrouga
-
OK, seems the fastest was to disable this when you start imaging from the “full host registration and inventory” boot menu option is to edit /var/www/fog/services/auto.register.php and comment out the line that starts with
[CODE]$other .= (" chkdsk=" . ($core->getGlobalSetting(“FOG_DISABLE_CHKDSK”) == “1” ? ‘0’ : ‘1’));[/CODE]
so, it becomes
[CODE]//$other .= (" chkdsk=" . ($core->getGlobalSetting(“FOG_DISABLE_CHKDSK”) == “1” ? ‘0’ : ‘1’));[/CODE]that stops the chkdsk option being added for just this boot menu option.
astrouga
-
Interesting. I currently have it left as-is, since my organization typically doesn’t use quick imaging (we either have scheduled multicasts, or we use full host registration and inventory as new computers come in), but this is definitely good to know. Thanks for looking into it!