Hard Drive, SSD, & M.2
-
Any ideas on how to get this working?
-
The times that I’ve hard of this the sata operation mode was setup as raid. From what I’m gathering, your sata operation mode is setup for AHCI? So I am really at a loss.
-
After even more digging. There is something hardware related that FOG doesn’t like or isn’t seeing. I put the SED drive into a MMF Dell 7050 and it started imaging without any issues. Maybe its the new quick swap device on it?
I will add due to hardware differences the image crashed upon loading into windows 7 (Yeah I know windows 7)
-
@BREIT Well then I’d expect the controller being the issue here - not the disk itself. Can you please try setting
nvme_load=YESas kernel option in the client’s host settings and try again? -
@sebastian-roth said in Hard Drive, SSD, & M.2:
nvme_load=YES
Sorry I need a little clarification, I go to the host on the web interface and type in nvme_load=YES in the Host Kernel Arguments?
-
@breit said in Hard Drive, SSD, & M.2:
I go to the host on the web interface and type in nvme_load=YES in the Host Kernel Arguments?
Yeah, exactly. Then try booting the client again and see if it can find the drive.
-
That did not work. Same error message comes up.
I did notice this line when booting kernel
populating /dev using udev: udevd[[3096]: error creating epoll fd: Function not implemented -
Hey guys. So I’ve attempted to register a computer this morning with a m.2 hard drive and got the same error message. Just wanted to pass that information along.
I overlooked switching to ACHI on this computer. DOH!
-
@breit What model of hardware is in question?
Also fog is at 1.5.2 with the kernels at 4.16.6. I’m not suggesting that either will fix your issues. Just letting you know there is newer stuff out there. I might hold off on updating FOG until 1.5.3 is released since there are a few annoyances in 1.5.2, but see if the newer kernel finds this nvme drive.
-
Just throwing this out there, might absolutely not be related and me just missunderstanding whats actually happening here.
I had problems Imaging a computer at point when switching from a hdd machine as image-source to an ssd.
I had to change the host primary disk to the correct one - I think from sda to sda2 or something along those lines - for this to work.
Rereading again I suppose this is in another direction, but just in case.
