@Quazz The files “d1.original.partitions”, “d1.original.fstypes”, “d1.fixed_size_partitions”, “d1.original.swapuuids” are all there. The system tries to load “d1.partitions” which is missing.
So I tried “cp d1.original.partitions d1.partitions” and it works! Even with NVME drives!
This solved it for me, thank everyone!
@Tom-Elliott I’m not that familiar with shell scripting, but given enough time I could figure it out. For now I’ll just try changing the sda2 to nvme0n1p2 and run some more test. If you could provide a script that would be great.
I think I figured out why the resize doesn’t work. Fog tries to load the “d1.partitions” file which isn’t available in any of my images. The images were made with fog 1.2.0. Is this new in recent versions?
Sorry, for going of topic as this doesn’t seem to have anything to do with HW compatibility.
@Tom-Elliott said in Hard drive doesn't expand after image:
postdownloadscript
Yeah, thanks for the hit. It is the postdownloadscript/driverinstall.sh I got from here https://wiki.fogproject.org/wiki/index.php/Auto_driver_Install and it tries to mount sda2.
I’m having the same issue with an Intel NUC6i5 with an Intel SSD 6000p m.2 PCIE NVME drive.
After writing the image it shows “Resizing ntfs volume (/dev/nvme0n1p2) … Done”, but the partition doesn’t get resized.
Further it show “Mounting Windows File System … failed to mount c:”
and “ntfs-3g : Failed to access Volume ‘/dev/sda2’: No such file or directory”
Where did the sda2 come from? Could it be hard coded somewhere?
Running FOG 1.4.0 with the latest Kernel 4.11.0 (updated form 1.2.0 -> 1.3.5 -> 1.40) on Ubuntu 14.04
Imaging an older NUC D54250 with SATA SSD works without problems.
Hi,
I have a couple of new PC’s which I’d like to image with FOG. Unfortunatly the pc freezes up when loading the PXE client. The menu loads and I can choose an option, but after it loads bzImage and init.gz the machine just freezes and has to be killed via power switch. I also tried running the debug task with the same results.
I tested with a different client PC and it all works as expected, so I assume it hase something to do with this specific hw config.
Any ideas what could be causing this?
Thx
Server: