m.2 PCIe SSD not recognised in FOG
-
@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/nvme0n1and 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 runfog. -
@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…
-
@Toby777 thank you again. I found the issue that error was spewing out and am rebuilding inits again. Give it about 10 minutes and try updating again. This is very much appreciated.
-
All republished.
-
@Tom-Elliott Thanks Tom, have updated and performed an upload using Single Disk Resizable and it uploaded without any errors.
I also then performed a deployment task of the Image and it was successful, windows boots up fine etc… just saw it come up with an error about changing the hostname.
-
This post is deleted! -
hello, i’m having the same issue with a Samsung SM951 PCIe NVMe as Toby777’s post below.
The only thing that works is ‘raw image’, otherwise i’m getting the same error as Toby777.
I tried different init.xz and init_32.xz as suggested in other posts to no avail.
Running Fog 1.2 on CentOS 6. Any ideas? Thanks!@Toby777 said:
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/nvme0n1When Image is set to Raw Image, it starts the upload…
I’m fine with using Raw Image if that’s what works.
-
@onepotato You may want to upgrade to trunk, as 1.2.0 is not very good with anything labeled other than /dev/{h,s}d* devices.
-
@onepotato Are you running the trunk build of 1.2.0 (a.k.a 1.3.0 beta) or just 1.2.0 stable?
With these memory disk devices, you would be better off upgrading to the trunk build since there has been great strides taken to fix these memory disk devices.
-
@onepotato NVME works on trunk for all partition types. I tested it myself
you can read more about the adventure to getting it working here…
https://forums.fogproject.org/topic/6315/hp-z640-nvme-pci-e-driveOr you can just trust me, it will work and follow the following instructions to upgrade your fog version
https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk -
@Tom-Elliott @Arrowhead-IT @george1421 Thanks. I might stop make it work with 1.2 then!
I did try to upgrade to 1.2 and it just broke everything so I reverted back to 1.2
I tried setting up a new server running CentOS 7 and fog trunk but it’s not working either, just getting a blank page when trying to access the console towards the end of the install to set up the DB.
Anyway. I’ll try and set up a trunk version again!
Thanks for your help
