HP Z640 - NVME PCI-E Drive
-
-
I’m currently at an appointment so it can’t do anything to fix this right now I just wanted to ensure you all know I’m aware of the issue for right now.
-
I looked through the other post and gave debug mode a try,
I ran lsblk and got the same disk info except it didn’t have any mount information.
But is said nvme0n1 and partition nvme0n1p1 -
Did a debug deploy
I found that fog saw the partition name as /dev/nvme0n11 instead of what was listed in gdisk -l /dev/nvme0n1p1
tried to change the name to no avail. -
@Arrowhead-IT Hey, just wanted to let you know this is all great information. The more details the devs have the better solution they can come up with. Its impossible to have every bit of hardware in the test lab that exists in the wild. So it is key to get support from the user community to help build a better mousetrap.
-
@george1421 That’s what I figured, it seems an odd problem so I’m going to give all the info I can to help find the problem. And plus, these nvme drives think that they are going to become the norm and phase out sata, sas, and scsi, so I’ll do whatever I can to help get FOG working with them.
-
@Arrowhead-IT Thanks for providing information about those devices and helping us. Can you please run another debug session and post the full output of
lsblk -pno KNAME,MAJ:MIN -x KNAME? We need the exact output (especially dev names - which you already provided - AND the IDs. Just take a picture and post it here if you don’t want to bother about typing it all. -
@Sebastian-Roth on it
-
@Sebastian-Roth Here ya go
I think that one possibility of the problem lies in the variable dump from fog.
It lists the partition as /dev/nvme0n11 but fdisk -l or gdisk -l lists it as /dev/nvme0n1p1 -
@Arrowhead-IT Great! Thanks again. I am sure @Tom-Elliott will push the fix pretty soon. Should be fairly easy in your case. But I am a bit worried about these ‘mmcblk0rpmb’ device from the other thread! Tom, should we only look at minor ids smaller than 8?? Might cause issues with GPT systems??
-
@Sebastian-Roth @Tom-Elliott Is there a timeline on when you think this issue will be fixed?
Please and thank you
-
@Sebastian-Roth @Tom-Elliott
I updated to the latest trunk since I noticed one of the commits said that it had adjusted the way partition numbers were found. But sadly it still isn’t working. I will try making it a raw image to see if that works as a workaround like it did for the other person with this problem with the m.2 drive. The debug information lsblk and for variable dump all still have the same information.Thanks,
-JJ -
@Arrowhead-IT We are working on this and try to get this fixed for mmcblk devices as well (another thread). Unfortunately those devices are even more special than your nvme drive but pretty similar naming-wise! As we are all doing this in our free time there is no timeline I can give you. We are onto it and I hope we can give you something to test in the next couple of days. So please bare with us.
-
@Arrowhead-IT i did indeed push a commit that changes how the partitions are numbered but I have not yet put those files into the init. There is a lot of work to go through with it and I don’t want to push something that will break already working imaging right now.
-
@Arrowhead-IT Here we go. I found some time to look into this more closely!
Download init.xz/init_32.xz test files from https://drive.google.com/folderview?id=0B-bOeHjoUmyMazJLZDhGaEl5VTQ&usp=sharing and put into place in /var/www/fog/service/ipxe/ or /var/www/html/fog/service/ipxe/ (probably a good idea to rename the original files instead of just overwriting them!)Please test and report back if capturing/deploy is working (Image type: Multiple Partition - Single Disk, Host Primary Disk: /dev/nvme0n1).
-
Awesome! I’m giving it a try right now. And my apologies if I seemed impatient in my asking, I was just curious and getting all excited.
I currently only have one image and it is a resizable one, we’ll see what happens.Thanks,
-JJ -
@Sebastian-Roth I just tested with a resizable image to no avail. I got some error messages. It looks like some numbering didn’t quite work as expected. Mainly when it is searching for /dev/nvme0n1p instead of /dev/nvme0n1p1 and when it tries to find the image file named d1pp1.img instead of d1p1.img
My apologies that some of these pictures have duplicate information, this happened twice I was just ready with the camera the second time since it happened so fast.
I am currently uploading a non-resizable version of that image to test that idea. I should be able to post results on that test in like 10 minutes or so.
-
@Sebastian-Roth Similar problem with a non-resizable disk, it doesn’t seem to add a 1 at the end of /dev/nvme0n1p
I’m going to do a debug session and see if the lsblk is any different from before and such. Let me know if there’s any other information you need. I’m here to help
On a side note, I did take out the primary hard disk specification and ran a hardware inventory and it found the hard drive just fine on its own. It didn’t get a harddrive manufacturer, model, or s/n but it knows it exist now. Yay progress!
-
Here’s the information from the debug session with the new init. Looks mostly the same. I’m going to try installing windows with default partitions the old fashioned way and I’ll see if image capture works by chance.
-
So here’s some good news, image capture works!
I did just a default multiple partition install of windows and it uploaded no problem.
I had still set the host primary disk to /dev/nvme0n1 in the gui.
I’m going to try re-downloading the image to the same computer
Then I’ll try to downloading the image I actually need on it that is single disk resizable.Thanks for all the help thus far.