Topics created by Fog_Newb

@jj-fullmer

Thanks. That is exactly what I did.

@george1421

I figured it out. /dev/nvme1n1

I wasn’t sure how Linux named NVMe’s.

@Fog_Newb said in Odd issue with Win 10 UEFI images after updating from 1.5.9-RC2.15 to 1.5.9-RC2.17:

Nobody else has access to either FOG server and the only change made was the update from RC2.15 to 1.5.9-RC2.17

And automated Updates…

RC2.19 is not much of a difference. Just preparing for the actual release to come very soon!

@Fog_Newb Yes.

@Sebastian-Roth

Thanks.

I see. I decided to just uninstall the fog client and reinstall the latest and point it to the current fog server.

@Sebastian-Roth

Hell yeah dude, that cleared it right up.

@george1421

I can try that later this week. If manually setting acpi=off in the host configuration kernel parameters field works then wouldn’t that mean the kernel parameter field for groups does not work?

I wish this place would get rid of those awful DC 7800’s

It is not happening anymore. The VM is only 18GB. It takes less than 10 minutes to capture and less than 10 minutes to update FOG. Or visa versa.

The only weird thing I have since noticed is during the install process, when are asked to go to fog/management and hit update database, that page no longer shows up. It just displays the fog login screen. So I just go back to the installer and hit ENTER. It seems to work fine.

Thank you guys. I have now got the latest RC 1.3 and found a problem. I made another thread about it.

@Fog_Newb I am still not convinced you need the acpi=off kernel parameter as you said that it does register properly. Both registration and deploy use the same Linux environment…

The error messages were in the links to the others posts.

This is not of much help. Often error messages seem to be “the same as” but actually are not if you look closely. To be able to help we need a picture of the error on the screen of your machines!

@Sebastian-Roth

Yes.

I just want to add real quick, the DC 7800’s can boot to the menu with any kernel and without and kernel parameters. They fail when deploying.

@Fog_Newb said:

Either use groups as suggested by George or add it to the global settings: FOG Configuration -> FOG Settings -> General Settings -> KERNEL ARGS (not sure if this would cause trouble for other hosts as we don’t know all the other hardware you have)

@Sebastian-Roth

Oh. Got it. That makes sense.

@Fog_Newb said in Capture Hackintosh drive image?:

So I would just put something like “/dev/sdx”?

Exactly! First disk usually ends up to be /dev/sda, second /dev/sdb and so on.

@Tom-Elliott

Nice, it is working now.

There was a slight blip where it got stuck at

Downloading kernel, init and fog-client binaries…

So I ‘quit’ the install removed user fogproject and ran the install again.

I was able to update the database schema, continue the install and login.

New interface looks slick!

Oh yes, that is most likely what it is. It is when you click the wrench at the top right in the web interface.

FOG Version Information
404 Not Found

@Fog_Newb Send me your email address in a direct message (it’s the talk bubble in the top right), and I’ll get a wiki user created for you.

Thanks all. It makes sense why it was happening now.

@Quazz

Yes, it was a legacy 10 install that was converted to EFI.