So reboot unraid itself right. I was hoping to avoid that but I'll do that at the next opportunity

Is it at all possible to have a zfs pool that exists within this plugin?

 

What I'm thinking is that I have this one pool of drives that I could use in a USB chasis and just plug in when I need access to them. Sort of like cold storage.

 

They are ZFS pool for speed because when needed it's large video files from a drone as ZFS helps speed up file transfers. 

Edited February 6, 20242 yr by dopeytree

4 hours ago, dopeytree said:

Is it at all possible to have a zfs pool that exists within this plugin?

UD does not mount zfs pools.

Hi

 

I use this wonderful plugin thanks for that!

 

Im using it for a external SSD disk where i store my "Appdata backup"

 

 

But i cant change the "owner" to "nobody" why is that?

 

Can i change it somehow?

 

Thanks!

4 minutes ago, DanielPT said:

But i cant change the "owner" to "nobody" why is that?

What filesystem is the disk formatted as?

I updated UD today and happened to also restart my Unraid server afterwards. Since restarting I'm unable to mount my drive. I get states that my mountpoint name is reserved. However, I also get this error when changing the mountpoint to gibberish. 

 

Portion of my log:

Spoiler

Feb  9 22:27:36 MyServer unassigned.devices: Disk with serial 'CT500P3SSD8_2242E67AF06F', mountpoint 'plex_appdata' cannot be mounted.
Feb  9 22:27:41 MyServer kernel: tun: Universal TUN/TAP device driver, 1.6
Feb  9 22:28:01 MyServer unassigned.devices: Error: Device '/dev/nvme0n1p1' mount point 'plex_appdata' - name is reserved, used in the array or a pool, or by an unassigned device.
Feb  9 22:28:01 MyServer unassigned.devices: Disk with serial 'CT500P3SSD8_2242E67AF06F', mountpoint 'plex_appdata' cannot be mounted.
Feb  9 22:28:13 MyServer unassigned.devices: Error: Device '/dev/nvme0n1p1' mount point 'plex_appdataSLDJHfbasdlkjhfb' - name is reserved, used in the array or a pool, or by an unassigned device.

Any help is appreciated, TIA


Edit1: Adding diagnostics, thanks alturismo
Edit2: Fixed by updating UD

xxxbootleg69xxx-diagnostics-20240209-2316.zip

Edited February 10, 20242 yr by moving
Adding diagnostics

9 minutes ago, moving said:

Any help is appreciated, TIA

may also post your diagnostics so @dlandon can rather give a decent answer what exactly is happening.

Hi All

 

A bit of a critical issue as I can't get my VMs or any Dockers up and online. I upgraded my plugins and Unraid today and now can't mount my NVME drives. I've scoured the net and this thread and have seen people with similar issue but never found a resolution thats relevant to me.

 

Please assist ASAP if possible ❤️ I have tried downgrading back to 6.12.4 but the issue is now persisting.

 

Diagnostics attached. To be clear I'm referring to "Feb 10 13:00:50 mw-nott unassigned.devices: Error: Device '/dev/nvme1n1p1' mount point 'nvme_vms' - name is reserved, used in the array or a pool, or by an unassigned device." Same thing happening for both NVME.

 

 

 

Many thanks for all assistance.

 

EDIT: I have tried to rename the device as well as the Disk Mount Point but it makes no difference.

 

 

EDIT2: I have also updated the password for both disks in UD settings.

 

EDIT3: With UDEV debug turned on in UD.

 

Feb 10 16:15:14 mw-nott unassigned.devices: Error: Device '/dev/nvme0n1p1' mount point 'nvme_appdata' - name is reserved, used in the array or a pool, or by an unassigned device.
Feb 10 16:15:14 mw-nott unassigned.devices: Disk with serial 'Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315736L', mountpoint 'nvme_appdata' cannot be mounted.
Feb 10 16:20:29 mw-nott unassigned.devices: Error: Device '/dev/nvme1n1p1' mount point 'nvme_vms' - name is reserved, used in the array or a pool, or by an unassigned device.
Feb 10 16:20:29 mw-nott unassigned.devices: Disk with serial 'Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315657T', mountpoint 'nvme_vms' cannot be mounted.
Feb 10 16:23:04 mw-nott unassigned.devices: Error: Device '/dev/nvme0n1p1' mount point 'nvme_appdata' - name is reserved, used in the array or a pool, or by an unassigned device.
Feb 10 16:23:04 mw-nott unassigned.devices: Disk with serial 'Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315736L', mountpoint 'nvme_appdata' cannot be mounted.
Feb 10 16:25:39 mw-nott ool www[7907]: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.settings 'save'
Feb 10 16:25:47 mw-nott unassigned.devices: Partition found with the following attributes: serial_short='S4EWNF0M315736L', device='/dev/mapper/nvme_appdata', serial='Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315736L', uuid='0b40712f-132c-4718-9ed5-f04c2752fd36', part='1', disk='/dev/nvme0n', label='S4EWNF0M315736L', disk_label='', array_disk='', fstype='crypto_LUKS', mountpoint='/mnt/disks/nvme_appdata', luks='/dev/nvme0n1p1', file_system='luks', not_udev='', mounting='', unmounting='', pass_through='', mounted='', part_read_only='', pool='', pool_name='', not_unmounted='', disable_mount='', target='', size='0', used='0', avail='0', owner='user', read_only='', shared='1', command='', user_command='', command_bg='true', enable_script='false', prog_name='', logfile='', running='', formatting='', preclearing=''
Feb 10 16:25:47 mw-nott unassigned.devices: Error: Device '/dev/nvme0n1p1' mount point 'nvme_appdata' - name is reserved, used in the array or a pool, or by an unassigned device.
Feb 10 16:25:47 mw-nott unassigned.devices: Disk with serial 'Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315736L', mountpoint 'nvme_appdata' cannot be mounted.
Feb 10 16:26:39 mw-nott unassigned.devices: Partition found with the following attributes: serial_short='S4EWNF0M315657T', device='/dev/mapper/nvme_vms', serial='Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315657T', uuid='a22ec698-8f23-4b3f-9197-cbaa8ebc2d5e', part='1', disk='/dev/nvme1n', label='nvme_vms', disk_label='nvme_vms', array_disk='', fstype='crypto_LUKS', mountpoint='/mnt/disks/nvme_vms', luks='/dev/nvme1n1p1', file_system='luks', not_udev='', mounting='', unmounting='', pass_through='', mounted='', part_read_only='', pool='', pool_name='', not_unmounted='', disable_mount='', target='', size='0', used='0', avail='0', owner='user', read_only='', shared='', command='', user_command='', command_bg='true', enable_script='false', prog_name='', logfile='', running='', formatting='', preclearing=''
Feb 10 16:26:39 mw-nott unassigned.devices: Error: Device '/dev/nvme1n1p1' mount point 'nvme_vms' - name is reserved, used in the array or a pool, or by an unassigned device.
Feb 10 16:26:39 mw-nott unassigned.devices: Disk with serial 'Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315657T', mountpoint 'nvme_vms' cannot be mounted.

 

mw-nott-diagnostics-20240210-1308.zip

Edited February 10, 20242 yr by Mooks

1 hour ago, Mooks said:

Hi All

 

A bit of a critical issue as I can't get my VMs or any Dockers up and online. I upgraded my plugins and Unraid today and now can't mount my NVME drives. I've scoured the net and this thread and have seen people with similar issue but never found a resolution thats relevant to me.

 

Please assist ASAP if possible ❤️ I have tried downgrading back to 6.12.4 but the issue is now persisting.

 

Diagnostics attached. To be clear I'm referring to "Feb 10 13:00:50 mw-nott unassigned.devices: Error: Device '/dev/nvme1n1p1' mount point 'nvme_vms' - name is reserved, used in the array or a pool, or by an unassigned device." Same thing happening for both NVME.

 

 

 

Many thanks for all assistance.

 

EDIT: I have tried to rename the device as well as the Disk Mount Point but it makes no difference.

 

 

EDIT2: I have also updated the password for both disks in UD settings.

 

EDIT3: With UDEV debug turned on in UD.

 

Feb 10 16:15:14 mw-nott unassigned.devices: Error: Device '/dev/nvme0n1p1' mount point 'nvme_appdata' - name is reserved, used in the array or a pool, or by an unassigned device.
Feb 10 16:15:14 mw-nott unassigned.devices: Disk with serial 'Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315736L', mountpoint 'nvme_appdata' cannot be mounted.
Feb 10 16:20:29 mw-nott unassigned.devices: Error: Device '/dev/nvme1n1p1' mount point 'nvme_vms' - name is reserved, used in the array or a pool, or by an unassigned device.
Feb 10 16:20:29 mw-nott unassigned.devices: Disk with serial 'Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315657T', mountpoint 'nvme_vms' cannot be mounted.
Feb 10 16:23:04 mw-nott unassigned.devices: Error: Device '/dev/nvme0n1p1' mount point 'nvme_appdata' - name is reserved, used in the array or a pool, or by an unassigned device.
Feb 10 16:23:04 mw-nott unassigned.devices: Disk with serial 'Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315736L', mountpoint 'nvme_appdata' cannot be mounted.
Feb 10 16:25:39 mw-nott ool www[7907]: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.settings 'save'
Feb 10 16:25:47 mw-nott unassigned.devices: Partition found with the following attributes: serial_short='S4EWNF0M315736L', device='/dev/mapper/nvme_appdata', serial='Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315736L', uuid='0b40712f-132c-4718-9ed5-f04c2752fd36', part='1', disk='/dev/nvme0n', label='S4EWNF0M315736L', disk_label='', array_disk='', fstype='crypto_LUKS', mountpoint='/mnt/disks/nvme_appdata', luks='/dev/nvme0n1p1', file_system='luks', not_udev='', mounting='', unmounting='', pass_through='', mounted='', part_read_only='', pool='', pool_name='', not_unmounted='', disable_mount='', target='', size='0', used='0', avail='0', owner='user', read_only='', shared='1', command='', user_command='', command_bg='true', enable_script='false', prog_name='', logfile='', running='', formatting='', preclearing=''
Feb 10 16:25:47 mw-nott unassigned.devices: Error: Device '/dev/nvme0n1p1' mount point 'nvme_appdata' - name is reserved, used in the array or a pool, or by an unassigned device.
Feb 10 16:25:47 mw-nott unassigned.devices: Disk with serial 'Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315736L', mountpoint 'nvme_appdata' cannot be mounted.
Feb 10 16:26:39 mw-nott unassigned.devices: Partition found with the following attributes: serial_short='S4EWNF0M315657T', device='/dev/mapper/nvme_vms', serial='Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315657T', uuid='a22ec698-8f23-4b3f-9197-cbaa8ebc2d5e', part='1', disk='/dev/nvme1n', label='nvme_vms', disk_label='nvme_vms', array_disk='', fstype='crypto_LUKS', mountpoint='/mnt/disks/nvme_vms', luks='/dev/nvme1n1p1', file_system='luks', not_udev='', mounting='', unmounting='', pass_through='', mounted='', part_read_only='', pool='', pool_name='', not_unmounted='', disable_mount='', target='', size='0', used='0', avail='0', owner='user', read_only='', shared='', command='', user_command='', command_bg='true', enable_script='false', prog_name='', logfile='', running='', formatting='', preclearing=''
Feb 10 16:26:39 mw-nott unassigned.devices: Error: Device '/dev/nvme1n1p1' mount point 'nvme_vms' - name is reserved, used in the array or a pool, or by an unassigned device.
Feb 10 16:26:39 mw-nott unassigned.devices: Disk with serial 'Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315657T', mountpoint 'nvme_vms' cannot be mounted.

 

mw-nott-diagnostics-20240210-1308.zip 208.28 kB · 0 downloads

 

Update....

 

Almost certain it's an Unassigned Devices plugin issue. I fortunately had been taking weekly backups and was able to revert my UD plugin folder and .plg file back to 2024.01.22b.

 

This immediately resolved the issue. Everything is working again but now I'm scared to update to 6.12.6 again, 6.12.4 running stable with the earlier version of UD.

 

Maybe you guys can have a look into it?

 

Cheers

20 minutes ago, Mooks said:

 

Update....

 

Almost certain it's an Unassigned Devices plugin issue. I fortunately had been taking weekly backups and was able to revert my UD plugin folder and .plg file back to 2024.01.22b.

 

This immediately resolved the issue. Everything is working again but now I'm scared to update to 6.12.6 again, 6.12.4 running stable with the earlier version of UD.

 

Maybe you guys can have a look into it?

 

Cheers

Hi all,

 

I'm having the exact same issue. I've troubleshooted just as Mooks had but am unable (don't know how) to roll back to a previous version of UD.

 

Diagnostics attached.

 

Any help is greatly appreciated.,

tower-diagnostics-20240210-1513.zip

1 hour ago, Kakoshka said:

Hi all,

 

I'm having the exact same issue. I've troubleshooted just as Mooks had but am unable (don't know how) to roll back to a previous version of UD.

 

Diagnostics attached.

 

Any help is greatly appreciated.,

tower-diagnostics-20240210-1513.zip 151.77 kB · 0 downloads

 

Did you definitely roll back everything inside the unassigned.devices folder (and delete the .zip of the latest version, which wouldn't have been in your back) as well as replace the .plg file? Then reboot the whole server?

That fortunately worked for me.

13 hours ago, Kilrah said:

What filesystem is the disk formatted as?

Ouh that is a good question

 

Where can i find that? 

 

Can this help?

 

Jan 18 09:51:02 Kratos kernel: sd 1:0:0:0: [sdb] 500118191 512-byte logical blocks: (256 GB/238 GiB)
Jan 18 09:51:02 Kratos kernel: sd 1:0:0:0: [sdb] Write Protect is off
Jan 18 09:51:02 Kratos kernel: sd 1:0:0:0: [sdb] Mode Sense: 47 00 00 08
Jan 18 09:51:02 Kratos kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 18 09:51:02 Kratos kernel: sdb: sdb1
Jan 18 09:51:02 Kratos kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Jan 18 09:51:24 Kratos emhttpd: SAMSUNG_MZ7TD256HAFV-000L9_S17LNSADC18583 (sdb) 512 500118191
Jan 18 09:51:24 Kratos emhttpd: read SMART /dev/sdb
Jan 18 09:52:24 Kratos unassigned.devices: Mounting partition 'sdb1' at mountpoint '/mnt/disks/Backup_external'...
Jan 18 09:52:24 Kratos unassigned.devices: Mount cmd: /sbin/mount -t 'exfat' -o rw,relatime,nodev,nosuid,umask=000 '/dev/sdb1' '/mnt/disks/Backup_external'
Jan 18 09:52:24 Kratos unassigned.devices: Successfully mounted '/dev/sdb1' on '/mnt/disks/Backup_external'.
 

Edited February 10, 20242 yr by DanielPT

In the FS column in UD.

 

7 minutes ago, DanielPT said:

Jan 18 09:52:24 Kratos unassigned.devices: Mount cmd: /sbin/mount -t 'exfat' -o

 

But it's ExFAT. That doesn't support any type of ownership/permissions, everything is always available to anyone.

Edited February 10, 20242 yr by Kilrah

1 hour ago, Mooks said:

 

Did you definitely roll back everything inside the unassigned.devices folder (and delete the .zip of the latest version, which wouldn't have been in your back) as well as replace the .plg file? Then reboot the whole server?

That fortunately worked for me.

Gave that a go and still getting the same error.

 

Thanks for the response though.

17 minutes ago, Kilrah said:

In the FS column in UD.

 

 

But it's ExFAT. That doesn't support any type of ownership/permissions, everything is always available to anyone.

Ouh can you tell me a little more?

 

i can see that the folders are root.

So i cant change that? Do you now my options?

22 minutes ago, DanielPT said:

So i cant change that?

No. That shouldn't be a problem for anything though.

6 hours ago, moving said:

I updated UD today and happened to also restart my Unraid server afterwards. Since restarting I'm unable to mount my drive. I get states that my mountpoint name is reserved. However, I also get this error when changing the mountpoint to gibberish. 

Looks to be an issue with nvme drives and I'm pretty sure I know the problem.  Give me a few hours to resolve and test and I'll release an update.  Unfortunagtely my test server does not have an nvme drive, so it's a little harder for me to test.

Welp I should have looked here before trying to wipe my drives, hopefully if the plugin is broken for NVME drives it may not have actually done anything with the drives.

Nothing major on them really but will have some very unhappy young family members who cannot watch Plex.

14 minutes ago, dlandon said:

Looks to be an issue with nvme drives and I'm pretty sure I know the problem.  Give me a few hours to resolve and test and I'll release an update.  Unfortunagtely my test server does not have an nvme drive, so it's a little harder for me to test.

You're amazing, thanks so much.

8 minutes ago, Damienc said:

Welp I should have looked here before trying to wipe my drives, hopefully if the plugin is broken for NVME drives it may not have actually done anything with the drives.

It only relates to looking up the duplicate names and prevents a mount because it detects a duplicate share name.  It does not affect the drive at all.

8 minutes ago, dlandon said:

It only relates to looking up the duplicate names and prevents a mount because it detects a duplicate share name.  It does not affect the drive at all.

 

That is weird then because I have no duplicate names, I have a "Plex" Unassigned drive and a Share drive which 2 of us in the house use for storing normal files that we don't store on the main array.

It won't mount even if I change the names of the Mounts, for instance I change "Plex" to "Plex2" and it still gives the same messages:

"Device '/dev/nvme2n1' failed to mount. Check the syslog for details."

 

&

 

Feb 10 11:18:58 Raptor unassigned.devices: Error: Device '/dev/nvme2n1p1' mount point 'Plex' - name is reserved, used in the array or a pool, or by an unassigned device.

Feb 10 11:18:58 Raptor unassigned.devices: Disk with serial 'CT2000P3PSSD8_2331E8650B4E', mountpoint 'Plex' cannot be mounted. Feb 10 11:18:58 Raptor unassigned.devices: Running device script: 'Plex.sh' with action 'ERROR_MOUNT'.

Feb 10 11:19:08 Raptor unassigned.devices: Error: Device '/dev/nvme2n1p1' mount point 'Plex2' - name is reserved, used in the array or a pool, or by an unassigned device.

Feb 10 11:19:08 Raptor unassigned.devices: Disk with serial 'CT2000P3PSSD8_2331E8650B4E', mountpoint 'Plex2' cannot be mounted.

Feb 10 11:19:08 Raptor unassigned.devices: Running device script: 'Plex.sh' with action 'ERROR_MOUNT'.

Feb 10 11:19:16 Raptor unassigned.devices: Error: Device '/dev/nvme2n1p1' mount point 'Plex2' - name is reserved, used in the array or a pool, or by an unassigned device.

Feb 10 11:19:16 Raptor unassigned.devices: Disk with serial 'CT2000P3PSSD8_2331E8650B4E', mountpoint 'Plex2' cannot be mounted.

Feb 10 11:19:16 Raptor unassigned.devices: Running device script: 'Plex.sh' with action 'ERROR_MOUNT'.

b 10 11:21:16 Raptor unassigned.devices: Error: Device '/dev/nvme2n1p1' mount point 'Plex2' - name is reserved, used in the array or a pool, or by an unassigned device.

Feb 10 11:21:16 Raptor unassigned.devices: Disk with serial 'CT2000P3PSSD8_2331E8650B4E', mountpoint 'Plex2' cannot be mounted. Feb 10 11:21:26 Raptor unassigned.devices: Error: Device '/dev/nvme2n1p1' mount point 'Plex2' - name is reserved, used in the array or a pool, or by an unassigned device.

Feb 10 11:21:26 Raptor unassigned.devices: Disk with serial 'CT2000P3PSSD8_2331E8650B4E', mountpoint 'Plex2' cannot be mounted.

Feb 10 11:21:26 Raptor unassigned.devices: Running device script: 'Plex2.sh' with action 'ERROR_MOUNT'.

Feb 10 11:21:38 Raptor unassigned.devices: Error: Device '/dev/nvme2n1p1' mount point 'Plex2' - name is reserved, used in the array or a pool, or by an unassigned device. Feb 10 11:21:38 Raptor unassigned.devices: Disk with serial 'CT2000P3PSSD8_2331E8650B4E', mountpoint 'Plex2' cannot be mounted.

Feb 10 11:21:38 Raptor unassigned.devices: Running device script: 'Plex2.sh' with action 'ERROR_MOUNT'.

 

 

Unless I have a different issue or am missing something.
 

3 minutes ago, Damienc said:

Unless I have a different issue or am missing something.

That the issue causes it to falsely detect duplicates when there aren't.

Edited February 10, 20242 yr by Kilrah

Someone please post the output of this command:

cat /var/state/unassigned.devices/share_names.json

 

5 minutes ago, Kilrah said:

That the issue causes it to falsely detect duplicates when there aren't.

Correct, what is happening is UD detects the drive being tested for duplicates as a duplicate rather than ignoring it.

5 minutes ago, dlandon said:

Correct, what is happening is UD detects the drive being tested for duplicates as a duplicate rather than ignoring it.

root@Raptor:~# cat /var/state/unassigned.devices/share_names.json
{
    "\/dev\/nvme1n1p1p": "Bill Damien Storage",
    "\/dev\/nvme2n1p1p": "Plex2"
}root@Raptor:~#