Andrew Dens

the redirect link for the support thread associated to this plugin is not working anymore fyi

Just a heads up the latest update is still not working for my nvme drive. I saw in the patch notes there was an update to improve the clear disk however my drive still only works when formatted as ntfs. gringotts-diagnostics-20230205-2139.zip

No worries yeah it does fine, as a workaround for now I guess i'll just format it on windows and then keep it as NTFS windows partitioned then setting it to mount in unraid as that or make a single zfs pool in unraid with this disk and try that.

root@Gringotts:~# wipefs -n /dev/nvme0n1 DEVICE OFFSET TYPE UUID LABEL nvme0n1 0x1fe dos --- I had attempted to format as xfs on UD before running that command

root@Gringotts:~# ls /dev/nv* /dev/nvme0 /dev/nvme0n1 /dev/nvme0n1p1 root@Gringotts:~# zpool import -d /dev/nvme0n1 no pools available to import root@Gringotts:~# sgdisk -Z /dev/nvme0n1 *************************************************************** Found invalid GPT and valid MBR; converting MBR to GPT format in memory. *************************************************************** Warning! Secondary partition table overlaps the last partition by 33 blocks! You will need to delete this partition or resize it in another utility. GPT data structures destroyed! You may now partition the disk using fdisk or other utilities. --- edit I tried formatting with UD after doing the above and it's still got a grey mount button with UD. Appreciate the help guys this issue really stumped me.

Something I noticed that might be part of the problem is when i do ls /dev/disk/by-id I see 2 different nvme drives even though there's only one plugged in? I can try with the nvme drive unplugged and starting up unraid to see what happens or plugging in a different nvme I have a few hot spares of the same brand from the raid 10 before root@Gringotts:~# ls /dev/disk/by-id | grep nvme nvme-CT500P2SSD8_2151E5F48096@ nvme-CT500P2SSD8_2151E5F48096-part1@ nvme-nvme.c0a9-323135314535463438303936-4354353030503253534438-00000001@ nvme-nvme.c0a9-323135314535463438303936-4354353030503253534438-00000001-part1@

gringotts-diagnostics-20230130-1025.zip

I tried zeroing out the device with preclear UD plugin, no luck. I plugged it into a windows pc and formatted it there as ntfs and then plugged back into unraid and that was able to mount by unassigned devices. Then I unmounted, cleared with UD, then tried to format as XFS/BTRFS and NTFS and it's still grey it won't allow mounting.

Yeah I tried clearing the disk a few times with UD and formatting twice no luck with that either. I figured it was an issue with the old zfs pool since I never was able to destroy that pool when it became corrupted so I removed the devices and I don’t see it listed anywhere using zpool status Sent from my iPhone using Tapatalk

gringotts-diagnostics-20230129-1949.zip

When trying to clear/format my nvme drive on Unassigned Devices it's still stays grey on the mount button. The passthrough is not selected for it. I had an NVME disk assigned to UD before however recently I had 4 nvme drives plugged into a mixture of pci-e 1x and 4x lanes which resulted in a serious problem and slow speeds when I attempted to mirror them in zfs raid 10. I ended up having to remove the devices after many hard restarts and testing them on other computers. Anyone have any ideas what I can do to clear out the history of this device or is the best way to zero out the nvme? I've tried creating a new zpool and deleting it with being assigned to the device thinking that would clear it out but no luck.

Can we pin this to near the front page? I had to do some digging to see what ADMIN_TOKEN was supposed to be