Optiplex 7440 AIO - Cannot find disk on system

[Wayne Workman]

Pinging @Sebastian-Roth and @george1421 on this.

[george1421]

I’m using fog to deploy to the o7040 SFF systems so I know it works.

I guess we need to start with the basics, what version of FOG are you using (look at the numbers on or by the cloud on the FOG management GUI). That will tell us where to go next. I can tell you that the fog trunk ~r7400 and newer as well as 1.3.0-rcX support hte NVMe disks that are in these 7040s.

[george1421]

@george1421 said in Optiplex 7440 AIO - Cannot find disk on system:

I’m using fog to deploy to the o7040 SFF systems so I know it works.

As Wayne pointed out the OP posted 7440 and I understood 7040 (mea culpa).

Either way my question of what version of FOG are you using is still accurate.

[Sebastian Roth]

@pxslip said in Optiplex 7440 AIO - Cannot find disk on system:

I also ran lsblk -pno KNAME,MAJ:MIN -x KNAME and got no output

Sounds like linux does not see your PCIe SSD. I guess this means you are running an older kernel. As George already said, we need to know your FOG version. I guess you should at least see the disk using lsblk if you are running FOG trunk! See here for information on how to get FOG trunk: https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

[pxslip]

I am currently running 1.3.0-RC8, SVN revision 5949. I followed the instructions at https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk to upgrade. Just to add some additional oddness, when I started this project I was running 1.2.0 and it claimed to recognize the drive, however when trying to capture it would fail with Partclone trying to read partitions like :Commands and others that were clearly not the actual drive. Just to add some info regarding the server - it is running on Ubuntu 14.04, I held off upgrading to 16.04 as I had read that it was still potentially iffy. Thanks again for the help!

[george1421]

@pxslip Just for clarity, when you reviewed the error in your OP what version of FOG were you using.

[pxslip]

@george1421 That error occurred when I was running 1.3.0-RC-8.

[george1421]

@pxslip Thank you for setting the stage here. Since this hardware is really new we may be dealing with a driver issue. 1.3.0-rc8 has the latest kernel of 4.7.0

if you boot into a debug capture console again, if you key in just lsblk what do you get for the output?

[pxslip]

@george1421 I was curious about that exact question earlier, sadly I still get no output from the command. Yeah I was wondering if I was going to be fighting uphill since the hardware is so new. Thanks again!

[Tom Elliott]

@pxslip Is it likely the way the drive is being recognized is the issue? Maybe look at the BIOS and see if anything can be changed in regards to how the drive is presented to the system?

[pxslip]

@Tom-Elliott Gahh! I knew I was missing something. In BIOS I can switch the SATA operation mode from some sort of Intel pseudo-RAID to AHCI, and now everything appears to be working. I will report back once I have run a full test of capture and deploy. Thank you all!

[george1421]

@pxslip Ok next round of questions. Is the device in uefi or bios (legacy) mode?

OK scratch that… Good find.

[pxslip]

@george1421 @Tom-Elliott Just wanted to report back to say that everything looks to be working and thank you for your help!