6 hours ago, shpitz461 said:

The NVMe is actually a pass-through to a VM (which is currently off), and it does have an NTFS GPT partition on it.

Give me the output of the following command:

/sbin/udevadm info --query=property --path $(/sbin/udevadm info -q path -n /dev/nvme1n1p1)

There seems to be something in the udev info for this partition that UD is choking on.

 

6 hours ago, shpitz461 said:

I can't config it @ all since there is no cog for it, anything I could do to make it recognize the NTFS partition?

We need to get the udev info cleaned up a bit so UD doesn't choke on it.    I think that UD will recognie the partition once we can clean up the reserved characters that are causing problems.

21 minutes ago, dlandon said:

Give me the output of the following command:

/sbin/udevadm info --query=property --path $(/sbin/udevadm info -q path -n /dev/nvme1n1p1)

There seems to be something in the udev info for this partition that UD is choking on.

Holly Molly, check this out:

Quote

DEVLINKS=/dev/disk/by-id/nvme-ADATA_SX8200PNP_2L172L2JQ5YC-part1 /dev/disk/by-id/nvme-nvme.1cc1-324c3137324c324a51355943-414441544120535838323030504e50-00000001-part1 /dev/disk/by-partlabel/댰㏸〲荾ȩ膳⁢☹悐奃㧎☆䓆ʘᬐج耗ᨲ⛚舴먰常\x3e㇡瀙㊃鮨 /dev/disk/by-partuuid/c8303757-6412-4cd1-af3f-06cd26686f7a /dev/disk/by-uuid/70C4-3780
DEVNAME=/dev/nvme1n1p1
DEVPATH=/devices/pci0000:80/0000:80:01.2/0000:82:00.0/nvme/nvme1/nvme1n1/nvme1n1p1
DEVTYPE=partition
DISKSEQ=64
ID_FS_TYPE=vfat
ID_FS_USAGE=filesystem
ID_FS_UUID=70C4-3780
ID_FS_UUID_ENC=70C4-3780
ID_FS_VERSION=FAT32
ID_MODEL=ADATA SX8200PNP
ID_PART_ENTRY_DISK=259:10
ID_PART_ENTRY_NAME=댰㏸〲荾ȩ膳⁢☹悐奃㧎☆䓆ʘᬐج耗ᨲ⛚舴먰常\x3e㇡瀙㊃鮨
ID_PART_ENTRY_NUMBER=1
ID_PART_ENTRY_OFFSET=1024
ID_PART_ENTRY_SCHEME=gpt
ID_PART_ENTRY_SIZE=204800
ID_PART_ENTRY_TYPE=c12a7328-f81f-11d2-ba4b-00a0c93ec93b
ID_PART_ENTRY_UUID=c8303757-6412-4cd1-af3f-06cd26686f7a
ID_PART_TABLE_TYPE=gpt
ID_PART_TABLE_UUID=8fc3b001-aa82-4c3d-a5df-7b75579322c4
ID_SERIAL=ADATA SX8200PNP_2L172L2JQ5YC
ID_SERIAL_SHORT=2L172L2JQ5YC
ID_WWN=nvme.1cc1-324c3137324c324a51355943-414441544120535838323030504e50-00000001
MAJOR=259
MINOR=11
PARTN=1
PARTNAME=02~)b9!C!!!,!2408>!!
SUBSYSTEM=block
USEC_INITIALIZED=119591522642

No idea how all these characters came about, is there any way to fix them?

The drive is running fine as passthrough in the VM (or even when I boot it baremetal).

31 minutes ago, shpitz461 said:

No idea how all these characters came about, is there any way to fix them?

Not that I know of, but that's why UD is choking on that udev info.

Hey There,

 

I have a very weird issue that is 100% recreatable. basically I have an NVME 1tb ssd which I occasionally use to boot up windows directly from machine boot. i.e. this is not a VM running on unraid. The drive has the following partitions.

 

now for some reason, when I set this drive to "Automount" from settings and reboot or startup the server from power down this is what I see.

 

All I need to do to fix it is click "unmount" and then click "mount" again and all the partitions are then mounted as per the first shot.

 

I also and mostly use this drive to store some VM's so having it automount and then autostart my linux VM is what I used to do. Until now

 

This used to work perfectly fine and without issue! 

 

It started to fail when I upgraded my GPU and forgot to turn off all the pass through before switching the server back on. Adding the new gpu re-arranged all the devices and I ended up with a drive controller being passed through instead of the GPU. My fault 100% yes. So anyone wanting to upgrade anything in the future just reset all the pass through and turn off all auto starts before your proceed! You will save yourself a lot of pain!

 

Long story short I managed to correct the server reconfigure all the drives rebuild a drive from parity so everything is now back up and working accept for auto mounting this particular drive at boot! Please help me  hehe

 

Thank's in advance!

 

 

 

 

 

19 minutes ago, sarf said:

All I need to do to fix it is click "unmount" and then click "mount" again and all the partitions are then mounted as per the first shot.

Do the following:

• Go to the UD Settings and set "Debug Log Level" to "Udev and Hot Plug".
• Reboot - Leave the Auto Mount on.
• Post diagnostics.

8 hours ago, dlandon said:

Not that I know of, but that's why UD is choking on that udev info.

I actually have four of these drives, I checked them all, the other three have normal english text in the attributes.

Here's the output from my other pass-through drive:

Quote

DEVLINKS=/dev/disk/by-id/nvme-ADATA_SX8200PNP_2L172LQJQQLC-part1 /dev/disk/by-id/nvme-nvme.1cc1-324c3137324c514a51514c43-414441544120535838323030504e50-00000001-part1 /dev/disk/by-partlabel/EFI\x20system\x20partition /dev/disk/by-partuuid/87fc32f6-75e5-4bfa-8c69-e4e557de0e8f /dev/disk/by-uuid/421C-2F42
DEVNAME=/dev/nvme0n1p1
DEVPATH=/devices/pci0000:80/0000:80:01.1/0000:81:00.0/nvme/nvme0/nvme0n1/nvme0n1p1
DEVTYPE=partition
DISKSEQ=66
ID_FS_TYPE=vfat
ID_FS_USAGE=filesystem
ID_FS_UUID=421C-2F42
ID_FS_UUID_ENC=421C-2F42
ID_FS_VERSION=FAT32
ID_MODEL=ADATA SX8200PNP
ID_PART_ENTRY_DISK=259:4
ID_PART_ENTRY_FLAGS=0x8000000000000000
ID_PART_ENTRY_NAME=EFI\x20system\x20partition
ID_PART_ENTRY_NUMBER=1
ID_PART_ENTRY_OFFSET=2048
ID_PART_ENTRY_SCHEME=gpt
ID_PART_ENTRY_SIZE=204800
ID_PART_ENTRY_TYPE=c12a7328-f81f-11d2-ba4b-00a0c93ec93b
ID_PART_ENTRY_UUID=87fc32f6-75e5-4bfa-8c69-e4e557de0e8f
ID_PART_TABLE_TYPE=gpt
ID_PART_TABLE_UUID=09cc4037-96b2-4581-9b2e-f7b5f9c8b083
ID_SERIAL=ADATA SX8200PNP_2L172LQJQQLC
ID_SERIAL_SHORT=2L172LQJQQLC
ID_WWN=nvme.1cc1-324c3137324c514a51514c43-414441544120535838323030504e50-00000001
MAJOR=259
MINOR=5
PARTN=1
PARTNAME=EFI system partition
SUBSYSTEM=block
USEC_INITIALIZED=322226792627

Is there anything you can do on your end to eliminate the issue?

I'm going to image it and format, see if it solves the issue.

Thanks!

1 hour ago, shpitz461 said:

Is there anything you can do on your end to eliminate the issue?

Not really.  This is the info reported by udev.  We don't have any control over that.

 

I don't know what you are doing with that disk, but the partition is a vfat partition and if it's not needed, you could manually remove it.  You're best bet would be to reformat the disk and start over.

1 hour ago, dlandon said:

Do the following:

• Go to the UD Settings and set "Debug Log Level" to "Udev and Hot Plug".
• Reboot - Leave the Auto Mount on.
• Post diagnostics.

There you go. Diags attached thanks for looking :)

core-diagnostics-20230208-1422.zip

3 hours ago, sarf said:

There you go. Diags attached thanks for looking

core-diagnostics-20230208-1422.zip 148.18 kB · 1 download

I've made some changes in UD that might help with this issue, but GitHub is struggling today so it may take quite a while before the update is available.  Once you update it, let me know if the issue is fixed.  If not post diagnostics again,  Leave the debug level set as it is.

6 hours ago, dlandon said:

Not really.  This is the info reported by udev.  We don't have any control over that.

 

I don't know what you are doing with that disk, but the partition is a vfat partition and if it's not needed, you could manually remove it.  You're best bet would be to reformat the disk and start over.

Ok, all is well. I couldn't format or preclear via Unraid, got errors, even after i manually removed partitions.

 

What I did to fix it was to just pass it through to my other VM , then used the AData SSD Toolbox to do a secure-erase.

I then restored the backup (using Easeus Todo Backup), and Windows won't boot.

I booted the VM with a Windows 10 retail disc, went to command prompt in recovery, then ran

Quote

bcdboot C:\Windows

And all is well, got back into a running Windows 10 install.

Thanks for the help @dlandon!

6 hours ago, dlandon said:

I've made some changes in UD that might help with this issue, but GitHub is struggling today so it may take quite a while before the update is available.  Once you update it, let me know if the issue is fixed.  If not post diagnostics again,  Leave the debug level set as it is.

You got it! I rebooted twice to make sure and both times all the partitions on the nvme mounted automatically. I run some more tests tomorrow from cold boot as well but hopefully its now fixed! Thank you for the fix and your awesome addon!!

1 hour ago, sarf said:

You got it! I rebooted twice to make sure and both times all the partitions on the nvme mounted automatically. I run some more tests tomorrow from cold boot as well but hopefully its now fixed! Thank you for the fix and your awesome addon!!

Once you are happy that it is resolved, turn off the debug logging.  It could get too chatty.

7 hours ago, dlandon said:

Once you are happy that it is resolved, turn off the debug logging.  It could get too chatty.

will do! I booted this morning from power on, drives all mounted and VM started automatically  thanks again...

I have an unassigned device that used to be formatte as XFS. I an trying to format it as NTFS, but unsuccessfully. See below what I did:

 

1) Remove partition

 

2) Select Format and select NTFS. Confirm with "Yes"

 

3) FS now shows as "XFS" and it is not possible to mount the disk

 

Happy to provide logs if helpful. Any thougths appreciated!

1 hour ago, steve1977 said:

I have an unassigned device that used to be formatte as XFS. I an trying to format it as NTFS, but unsuccessfully. See below what I did:

 

1) Remove partition

 

2) Select Format and select NTFS. Confirm with "Yes"

 

3) FS now shows as "XFS" and it is not possible to mount the disk

 

Happy to provide logs if helpful. Any thougths appreciated!

Lookiing itno it now.

2 hours ago, steve1977 said:

I have an unassigned device that used to be formatte as XFS. I an trying to format it as NTFS, but unsuccessfully. See below what I did:

 

1) Remove partition

 

2) Select Format and select NTFS. Confirm with "Yes"

 

3) FS now shows as "XFS" and it is not possible to mount the disk

 

Happy to provide logs if helpful. Any thougths appreciated!

Use the 'Clear Disk' (the red 'X') next to the DIsk ID to clear the disk.

Thanks. And when you are at it, there is another thing to check out.

 

You kindly included a feature that prevents to remove disabled disks from historic. However, now there are many disks now that are actually part of the array (active), but show up under historic disks (and cannot be deleted). Not sure why, but it could be because they were mapped under a different drive name before and now no longer show up.

2 minutes ago, steve1977 said:

Thanks. And when you are at it, there is another thing to check out.

 

You kindly included a feature that prevents to remove disabled disks from historic. However, now there are many disks now that are actually part of the array (active), but show up under historic disks (and cannot be deleted). Not sure why, but it could be because they were mapped under a different drive name before and now no longer show up.

It's actually a detached disk, not disabled disk.  Post a screen shot of the Historical Devices.

 

Click on the three gears icon of a deteached disk and see it the 'Attach' button shows.

5 minutes ago, dlandon said:

Use the 'Clear Disk' (the red 'X') next to the DIsk ID to clear the disk.

It works after restarting the server.

Here we go. To the right is a black cross, so I cannot remove it. This disk is part of the array though.

 

1 minute ago, steve1977 said:

Here we go. To the right is a black cross, so I cannot remove it. This disk is part of the array though.

 

I need to complete screen shot of Historical devices.

I cut out the serial numbers, but below should help?

 

All your Historical devices except sdv can be deleted.

Yes. Plus another 4 that are at the bottom (didn't fit the screenshot). The issue is with these disks. DOn't think they should be "black tick", but shouldn't show up or also be deletable.