Identical NVMe drives
-
@sebastian-roth Sorry for the delay, I have some busy days behind me. I ran the debug task and lsblk on an Intel NUC with a single NVME drive. On the NUC, the results were the same, the WWN field was empty, while the name and serial were ok.
-
@george1421 said in Identical NVMe drives:
On any computer with an NVMe drive or only one that has more than one nvme drive??
Really on any machine you have available, be IT single or multi disk, HDD or NVMe…
My guess is that our FOS
lsblkhas this kind of bug where it cannot read the WWN. -
@testers Anyone keen to test and give some feedback on the output of
lsblk -pdo NAME,SERIAL,WWNin a debug session? No need to take a picture and post that here. Just let me know of WWN is shown in the output or empty.Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
@sebastian-roth said in Identical NVMe drives:
Anyone keen to test and give some feedback
Sorry I forgot about this thread. I’ll give you the results tomorrow. You just need a yes or no on the WWN or do you want me to test with multiple hardware to see if its hardware specific?
I think lsblk is part of busybox. I don’t know if buildroot has the full app or not. I haven’t look as of now.
-
@george1421 Thanks! My guess is that the WWN will be empty on any hardware. Though it would be good to test on three or so different systems. Yes, could be a minified version of lsblk that we have in buildroot, not sure. Though SERIAL seems to work.
-
@sebastian-roth said in Identical NVMe drives:
feedback on the output of lsblk -pdo NAME,SERIAL,WWN in a debug session
Testing shows that the wwn value is not displayed/present on
Dell 7450 (msata)
Dell 7400 nvme
Dell 9420 nvme
Dell 5420 nvmeExcept for the msata drive the serial number was present.
Patch to add real lsblk to buildroot: https://patchwork.ozlabs.org/project/buildroot/patch/20160225171433.7e200dfc@free-electrons.com/
(I didn’t look into it more than to see what needed to be updated in
package/util-linux/util-linux.mk) -
@george1421 Nice, thanks heaps for your testing and the research! Will see if I can add this. Interesting you didn’t even get the serial in the mSATA…
-
Hi, sorry for bumping this thread, I myself got carried away with other tasks.
As I read the test results, the serial should work for NVME drives on all tested systems. Does this solution have a chance to be merged into the next FOG release?
In the meantime I’m alright with using the modified init file provided by @Sebastian-Roth.
There may also be a chance that I need to capture and deploy our nvme PCs in the near future, in that case I will post the results here.
-
@mrp Thanks for bringing this topic up again. I lost track of this as well. Just found some time to bring it all back to mind. We’ll surely merge this into the official FOG code sooner or later. Right now we are preparing for a next release soon I am a bit worried about adding the changes I made back in November now in a rush to an official release. We plan to put out another release this year and this would be perfect to be included then.
We might even add the full lsblk code mentioned by George to make WWN work as well.
Please let me know when you get to capture and deploy your NMVe PCs.
-
@mrp I just did a fresh build using the newer version of buildroot which we now use officially as well. Please download the init.xz file here for your next tests: https://github.com/FOGProject/fos/releases/testing
-
@mrp Added to the official FOS inits now. Can’t wait any longer for you to test.
