June 4, 20179 yr 1 minute ago, ArekDylag said: Why identification of cache devices has changed, is something wrong? Settings/Display Settings/Display world-wide-names in device ID Try setting to Disabled.
June 4, 20179 yr Author 8 minutes ago, limetech said: Settings/Display Settings/Display world-wide-names in device ID Try setting to Disabled. No nothing changed, still the same
June 4, 20179 yr 12 minutes ago, limetech said: Settings/Display Settings/Display world-wide-names in device ID Try setting to Disabled. My NVMe cache also changed, gave me a scare since the array autostarded without it and there were no VMs, display world-wide-names doesn't change anything.
June 4, 20179 yr 1 minute ago, johnnie.black said: My NVMe cache also changed, gave me a scare since the array autostarded without it and there were no VMs, display world-wide-names doesn't change anything. Install Dynamix scsi devices plugin
June 4, 20179 yr 1 minute ago, ArekDylag said: And this appeared in unassigned devices Have you tried the Dynamix scsi devices plugin? It translates WWN names to regular names.
June 4, 20179 yr Author 6 minutes ago, bonienl said: Have you tried the Dynamix scsi devices plugin? It translates WWN names to regular names. i have done this , and the result is it no longer sees the cache pool and the hard drives
June 4, 20179 yr 1 minute ago, ArekDylag said: i have done this , and the result is it no longer sees the cache pool and the hard drives It changes the name of the device and you need to re-assign. This is also explained with the plugin itself. Hope you are doing this on a test machine ...
June 5, 20179 yr Installed RC2. NVMe drive came up as unassigned. Installed SCSI plugin, rebooted, now NVMe drive doesn't appear anywhere. Ideas?
June 5, 20179 yr 11 minutes ago, HellDiverUK said: Installed RC2. NVMe drive came up as unassigned. Installed SCSI plugin, rebooted, now NVMe drive doesn't appear anywhere. Ideas? Same here. I removed SCSI plugin, it came back. It seems the plugin is not compatible yet to this update.
June 5, 20179 yr 14 minutes ago, HellDiverUK said: Installed RC2. NVMe drive came up as unassigned. Installed SCSI plugin, rebooted, now NVMe drive doesn't appear anywhere. Ideas? Can you show the output of ls -l /dev/disk/by-id (with and without the scsi plugin)
June 5, 20179 yr 8 minutes ago, Naiqus said: Same here. I removed SCSI plugin, it came back. It seems the plugin is not compatible yet to this update. Same question as to HellDiverUK, can you show the output of the command: ls -l /dev/disk/by-id (with and without the scsi plugin installed)
June 5, 20179 yr 5 minutes ago, bonienl said: Can you show the output of ls -l /dev/disk/by-id (with and without the scsi plugin) Before install the plugin: Quote Jun 5 11:26 nvme-Samsung -> ../../nvme0n1p1 Jun 5 11:26 nvme-eui.0025385c61b0578f -> ../../nvme0n1 Jun 5 11:26 nvme-eui.0025385c61b0578f-part1 -> ../../nvme0n1p1 After install the plugin, the nvme disk is also disappeared when I run this command.
June 5, 20179 yr I got the NVMe drive up again by removing the SCSI plugin. Output as requested: Without plugin: root@WHS:~# ls -l /dev/disk/by-id total 0 lrwxrwxrwx 1 root root 9 Jun 5 10:26 ata-ST8000AS0002-1NA17Z_Z840EWDM -> ../../sdb lrwxrwxrwx 1 root root 10 Jun 5 10:26 ata-ST8000AS0002-1NA17Z_Z840EWDM-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Jun 5 10:26 ata-ST8000AS0002-1NA17Z_Z840GB57 -> ../../sde lrwxrwxrwx 1 root root 10 Jun 5 10:26 ata-ST8000AS0002-1NA17Z_Z840GB57-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 Jun 5 10:26 ata-WDC_WD40EZRZ-00WN9B0_WD-WCC4E5JFVA9P -> ../../sdd lrwxrwxrwx 1 root root 10 Jun 5 10:26 ata-WDC_WD40EZRZ-00WN9B0_WD-WCC4E5JFVA9P-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 Jun 5 10:26 ata-WDC_WD80EZZX-11CSGA0_VKHPAB2X -> ../../sdc lrwxrwxrwx 1 root root 10 Jun 5 10:26 ata-WDC_WD80EZZX-11CSGA0_VKHPAB2X-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 15 Jun 5 10:26 nvme-SAMSUNG -> ../../nvme0n1p1 lrwxrwxrwx 1 root root 13 Jun 5 10:26 nvme-nvme.144d-533158574e594147393032353338-53414d53554e47204d5a5650563235364844474c2d3030303030-00000001 -> ../../nvme0n1 lrwxrwxrwx 1 root root 15 Jun 5 10:26 nvme-nvme.144d-533158574e594147393032353338-53414d53554e47204d5a5650563235364844474c2d3030303030-00000001-part1 -> ../../nvme0n1p1 lrwxrwxrwx 1 root root 9 Jun 5 10:26 usb-Kingston_DataTraveler_3.0_0026185AA718F0B0E8245CFF-0:0 -> ../../sda lrwxrwxrwx 1 root root 10 Jun 5 10:26 usb-Kingston_DataTraveler_3.0_0026185AA718F0B0E8245CFF-0:0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 Jun 5 10:26 wwn-0x11502352455593644032x -> ../../sdb lrwxrwxrwx 1 root root 10 Jun 5 10:26 wwn-0x11502352455593644032x-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Jun 5 10:26 wwn-0x14568393655441313792x -> ../../sdc lrwxrwxrwx 1 root root 10 Jun 5 10:26 wwn-0x14568393655441313792x-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Jun 5 10:26 wwn-0x16573968809304543232x -> ../../sde lrwxrwxrwx 1 root root 10 Jun 5 10:26 wwn-0x16573968809304543232x-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 Jun 5 10:26 wwn-0x231104799882498049x -> ../../sdd lrwxrwxrwx 1 root root 10 Jun 5 10:26 wwn-0x231104799882498049x-part1 -> ../../sdd1 root@WHS:~# With plugin: root@WHS:~# ls -l /dev/disk/by-id total 0 lrwxrwxrwx 1 root root 9 Jun 5 10:39 ata-ST8000AS0002-1NA17Z_Z840EWDM -> ../../sdb lrwxrwxrwx 1 root root 10 Jun 5 10:39 ata-ST8000AS0002-1NA17Z_Z840EWDM-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Jun 5 10:39 ata-ST8000AS0002-1NA17Z_Z840GB57 -> ../../sde lrwxrwxrwx 1 root root 10 Jun 5 10:39 ata-ST8000AS0002-1NA17Z_Z840GB57-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 Jun 5 10:39 ata-WDC_WD40EZRZ-00WN9B0_WD-WCC4E5JFVA9P -> ../../sdd lrwxrwxrwx 1 root root 10 Jun 5 10:39 ata-WDC_WD40EZRZ-00WN9B0_WD-WCC4E5JFVA9P-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 Jun 5 10:39 ata-WDC_WD80EZZX-11CSGA0_VKHPAB2X -> ../../sdc lrwxrwxrwx 1 root root 10 Jun 5 10:39 ata-WDC_WD80EZZX-11CSGA0_VKHPAB2X-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Jun 5 10:39 usb-Kingston_DataTraveler_3.0_0026185AA718F0B0E8245CFF-0:0 -> ../../sda lrwxrwxrwx 1 root root 10 Jun 5 10:39 usb-Kingston_DataTraveler_3.0_0026185AA718F0B0E8245CFF-0:0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 Jun 5 10:39 wwn-0x11502352455593644032x -> ../../sdb lrwxrwxrwx 1 root root 10 Jun 5 10:39 wwn-0x11502352455593644032x-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Jun 5 10:39 wwn-0x14568393655441313792x -> ../../sdc lrwxrwxrwx 1 root root 10 Jun 5 10:39 wwn-0x14568393655441313792x-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Jun 5 10:39 wwn-0x16573968809304543232x -> ../../sde lrwxrwxrwx 1 root root 10 Jun 5 10:39 wwn-0x16573968809304543232x-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 Jun 5 10:39 wwn-0x231104799882498049x -> ../../sdd lrwxrwxrwx 1 root root 10 Jun 5 10:39 wwn-0x231104799882498049x-part1 -> ../../sdd1 root@WHS:~#
June 5, 20179 yr @Naiqus and @HellDiverUK Can you also post the output of this command: udevadm info /dev/nvme0n1 Ps. I've made an update for the Dynamix SCSI devices plugin to address changes between old and new persistent-rules files, but I doubt it will correct the nvme issue, hence my question above. Edited June 5, 20179 yr by bonienl
June 5, 20179 yr 1 hour ago, bonienl said: @Naiqus and @HellDiverUK Can you also post the output of this command: udevadm -x /dev/nvme0n1 Ps. I've made an update for the Dynamix SCSI devices plugin to address changes between old and new persistent-rules files, but I doubt it will correct the nvme issue, hence my question above. Thanks for your effort and reply. I already updated you plugin. It turned out that the driver is back in the list, but it is not renamed properly. The same with before the plugin installing. The command you gave seems not valid on my machine. I suppose you wanna see the info so here is the output: Quote root@Tower:~# udevadm info /dev/nvme0n1 P: /devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1 N: nvme0n1 S: 500GB_S3EUNX0HC10760J S: 960 S: EVO S: SSD S: disk/by-id/nvme-Samsung S: disk/by-id/nvme-eui.0025385c61b0578f E: DEVLINKS=/dev/500GB_S3EUNX0HC10760J /dev/960 /dev/EVO /dev/SSD /dev/disk/by-id/nvme-Samsung /dev/disk/by-id/nvme-eui.0025385c61b0578f E: DEVNAME=/dev/nvme0n1 E: DEVPATH=/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1 E: DEVTYPE=disk E: ID_PART_TABLE_TYPE=dos E: ID_SERIAL=Samsung SSD 960 EVO 500GB_S3EUNX0HC10760J E: ID_SERIAL_SHORT=S3EUNX0HC10760J E: MAJOR=259 E: MINOR=0 E: SUBSYSTEM=block E: USEC_INITIALIZED=13362312
June 5, 20179 yr 23 minutes ago, Naiqus said: Thanks for your effort and reply. I already updated you plugin. It turned out that the driver is back in the list, but it is not renamed properly. The same with before the plugin installing. The command you gave seems not valid on my machine. I suppose you wanna see the info so here is the output: yes, I needed the 'info' It seems to me the problem comes from the spaces in the serial name: ID_SERIAL=Samsung SSD 960 EVO 500GB_S3EUNX0HC10760J Need LT to further investigate...
June 5, 20179 yr 2 hours ago, HellDiverUK said: So...Disk Speed. 6.3.4 gave 847MB/s on my Samsung NVMe cache drive. 6.4.0rc2 gives the expected 2400MB/s. Nice. How about the new NVMe disk id issue in the array? Have you managed to resolve it?
June 5, 20179 yr root@WHS:~# udevadm info /dev/nvme0n1 P: /devices/pci0000:00/0000:00:1d.0/0000:01:00.0/nvme/nvme0/nvme0n1 N: nvme0n1 S: MZVPV256HDGL-00000_S1XWNYAG902538 S: disk/by-id/nvme-SAMSUNG S: disk/by-id/nvme-nvme.144d-533158574e594147393032353338-53414d53554e47204d5a5650563235364844474c2d3030303030-00000001 E: DEVLINKS=/dev/MZVPV256HDGL-00000_S1XWNYAG902538 /dev/disk/by-id/nvme-SAMSUNG /dev/disk/by-id/nvme-nvme.144d-533158574e594147393032353338-53414d53554e47204d5a5650563235364844474c2d3030303030-00000001 E: DEVNAME=/dev/nvme0n1 E: DEVPATH=/devices/pci0000:00/0000:00:1d.0/0000:01:00.0/nvme/nvme0/nvme0n1 E: DEVTYPE=disk E: ID_PART_TABLE_TYPE=dos E: ID_SERIAL=SAMSUNG MZVPV256HDGL-00000_S1XWNYAG902538 E: ID_SERIAL_SHORT=S1XWNYAG902538 E: MAJOR=259 E: MINOR=0 E: SUBSYSTEM=block E: USEC_INITIALIZED=13438258 root@WHS:~# I'm running the cache fine wihout the SCSI plugin - it's just got the ridiculously long name.
June 5, 20179 yr 1 hour ago, Naiqus said: How about the new NVMe disk id issue in the array? Have you managed to resolve it? It's my cache drive, which works fine once assigned with it's silly long name.
June 5, 20179 yr My unassigned NVMe was not being recognised correctly as an unassigned device. Coming up as 2 devices (although only one) both needing formatting. Thanks @bonienl installed Dynamix scsi plugin. It fixed everything for me and it's now correctly showing and mountable, so have got my VMs Edited June 5, 20179 yr by gridrunner
June 7, 20179 yr i also would like to test the new 6.4rc release, may i ask is its always renaming the drives, i also use a nvme as cache device with all settings, dockers, vm´s ... and if the cache is not mounted, nothing should work anymore i already switched my apache ssl port to 444 so there shouldnt be any conflicts, but the drve issue ... also installed the scsi plugin, rebooted, no changes in names. can i just reassign the cache drive in case it gets different name, also with no data loss ? for an tip thanks ahead EDIT Update done, had to reassign cache drive, system frozen (i assume due VM then auto started), hard reboot, all here now Edited June 7, 20179 yr by alturismo update done
June 23, 20179 yr I've just installed RC5 and I think the nvme drive name changing is why I previously thought my install had gone wrong. I've changed my VM settings and each individual VM XML file to reflect the new long nvme name. Is there any way to get the short name back? I don't mind changing the xml files, but I have a really ugly looking share name now
June 23, 20179 yr 11 hours ago, DZMM said: Is there any way to get the short name back? I don't mind changing the xml files, but I have a really ugly looking share name now Working on it. Solution won't be in -rc6 but will be in place before 6.4 'stable'. Thanks for your patience.
Archived
This topic is now archived and is closed to further replies.