@arnaudrigole said in Dell Optiplex 7060 - getHardDisk error:

I used that trick to switch between “raid on” and “AHCI” during more than one year right now, and it worked well but…

Now we got NVMe SSDs in our new DELL computers, which need to be configured in “Raid ON” as “Sata Operation” to boot on Windows. Do you think that “GetHardDisk” error will be fixed in next versions ?

I think you have two different issues here. The first issue is the raid-on vs ahci mode. This is an age old issue between Intel, Linux, and uefi. With these three amigos working together linux can’t currently see any disks behind this configuration. If you change any of the three (really two) linux will see the disk. From what I understand the issue is related to intel not releasing the uefi raid drivers to the linux community.

The second issue may be new Dell hardware with these NVMe disks.

What version of FOG are you using? What version of FOS Linux kernel do you have installed? What is the model number of the computer with this issue?

Short answer: Maybe

Longer answer:
I don’t have the ability to confirm at the moment. But I can tell you that fog does record imaging registered hosts in a mysql table called imaginglog. The part I’m not sure of is if the log only uses an image id to refer to the host being imaged (logical link to the host table) or it saves the actual host name into this table.

The other thing I would have to check is if a host is deleted, is it a soft delete (only marking the host deleted) or does it remove the record. If its a soft delete it would then be possible to create a mysql query to report imaging even if the host record was not visible in the webgui.

The issue is if the host records are removed from the host table and the imaging log only references the host id field, there is no way to tell when a host was imaged since the pointer to the host table would not link to a valid host (since it was removed from the database)

figured it out thanks to this thread.

https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy

thanks Wayne. I will do this this weekend and if I need help post back here.

All fine, we just had to configure an IP address on the internal network interface and tell the installer to use that for imaging.

Thanks a ton!

None of this is working. So I will just continue to use it with the current version that is installed (1.3.5). Thanks for your help.

@Tom-Elliott you’re a gentleman and a scholar. I won’t believe the things they say about you again. Lol.

@Wayne-Workman I ran

chmod 755 ./installfog.sh

and it works now. Thanks for pointing that out.

@Wayne-Workman Wayne, I will be back in the office tomorrow, and can do so then.

@george1421 The switch we were using also had a network connection connected to it. So when I pulled the connection, instead of using the IP address we used localhost.

@TTellez said in Transition to offline FOG from Online installation?:

Using the browser to connect to FOG It says I need internet access. Or am I doing it wrong?

The login screen contacts fogproject.org to get the estimated number of FOG sites that are operating world-wide. If the FOG server can’t retrieve this information, it’s not a problem. Just business as usual.

@Jaymes-Driver @Tom-Elliott

Thank you so much for your help. I am up and running now on 1.3.5 RC 11.