m.2 PCIe SSD not recognised in FOG

[Tom Elliott]

@Toby777 i don’t want to solve a cased until I’m sure your issue is fixed. Hopefully that is understandable. When you can please just let us know if this can be solved for sure. Thanks.

[Toby777]

@Tom-Elliott Ok no dramas. Will test as soon as the notebook is repaired by Dell. Cheers

[Toby777]

Hi Tom,

Got the Dell tech to replace the motherboard today.

Latest Fog trunk now recognises the nvme SSD.

When the Image is set to Single Disk - Resizable, it hangs at…

* Saving original patition table......................

When Image is set to Multiple Partition Image - Single Disk (Not Resizable), it hangs at…

* Now FOG will attempt to upload the image using Partclone
* Processing Hard Disk: /dev/nvme0n1

When Image is set to Raw Image, it starts the upload…

I’m fine with using Raw Image if that’s what works.

[Tom Elliott]

@Toby777 Was this indefinitely hung, or did you wait a minute and then retry?

I’ve been seeing some “hanging” but it does continue to run, though I’m not 100% if this is truly the same case with the nvme drives.

At least I now know the raw capture still works

[Toby777]

@Tom-Elliott I did leave it running for 5 mins but it still had not progressed on either one except Raw.

[Sebastian Roth]

@Toby777 Could you please run a debug session on this device (WebGUI -> Host -> Basic tasks -> Debug) and run lsblk. What do you get?

Are you sure it said /dev/nvme0n1 when trying single disk resizable?? Asking because this would be the whole disk instead of the first partition. In RAW mode nvme0n1 is fine.

[Toby777]

@Sebastian-Roth Here’s the results of the Debug…

Here is the upload attempt when the Image is set to Multiple Partition Image - Single Disk (Not Resizable)

Damn that screen on the XPS 13 is shiny

[JJ Fullmer]

@Toby777 Are you on the latest trunk?
Download and upload of all image formats is working for me on nvme on the latest.

[Toby777]

@Arrowhead-IT Yup - updated to 5964 this morning on the test server.

[Wayne Workman]

@Sebastian-Roth @Tom-Elliott this might be helpful? https://communities.intel.com/community/itpeernetwork/blog/2014/10/03/upgrade-a-nvme-capable-linux-kernel

[Sebastian Roth]

@Wayne-Workman Thanks for the link but I don’t think we need this as we have a 4.x kernel already running. It seams to recognize the disk and partitions as we see in the lsblk output!

@Toby777 Would you mind another debug session? Please run the following three commands and see if this hangs:

udevadm settle
blockdev --rereadpt /dev/nvme0n1
sfdisk -l /dev/nvme0n1

[Tom Elliott]

@Toby777 I believe I found the hang accidentally. I too was seeing a hang on my side but I don’t know what was causing it. I edited more of the files and retested things and it looks like all is working if you’d be willing to test again. The suggestion I’d make is to schedule the tasking as debug (choose capture like normal and check the schedule as debug) first. That way you can get the info Sebastian is requesting. To perform the tasking at the cmd prompt just type fog. This should make you step through almost every phase so if things hang you can break out. It helps me a little as well as I can more clearly find out what is hanging.

[Toby777]

@Tom-Elliott Thanks Tom. I’m currently interstate for this week so once I’m back at our main office next week, I will perform the testing.
Thanks

[Toby777]

@Tom-Elliott Hi Tom, I updated to trunk 6084 and did the debug testing as you requested. Screen shots below…

Image set to Single Disk - Resizable

Image set to Multiple Partition Image - Single Disk (Not Resizable)

[Tom Elliott]

@Toby777 from debug what’s the output of:

sgdisk -b "/tmp/d1.mbr" /dev/nvme0n1

[Tom Elliott]

I believe I found, and hopefully fixed, this issue. Please re update and try again when you can. Thank you.

[Toby777]

@Tom-Elliott ok cool… will do that now.

The output of the previous command was…

Invalid partition data!

[Toby777]

@Tom-Elliott Same error unfortunately

[Tom Elliott]

@Toby777 for that, I suspect you built the image as MBR? But the original format was in GPT. I’m just guessing as the message from the command you ran earlier seems to indicate a gpt linkage failure.

Can you run fixparts /dev/nvme0n1 and let us know the output? I’d also recommend if it states it needs repair to approve and save the changes to the disk. Then run fog.

[Toby777]

@Tom-Elliott Hi Tom, running that command seems to have resolved the issue and it was able to successfully upload the image to the FOG server. This is while the image was set to Multiple Partition Image - Single Disk (Not Resizable)

When I changed it to single disk - resizable, the below error appeared…