42 minutes ago, dlandon said:

I haven't run 6.3.5 in a while, but there should be an update button in the upper right part of the plugins page.  Click on that and it will check for updates.

 

There seems to be a problem with your configuration file.  Please post the the /flash/config/plugins/unassigned.devices/unassigned.devices.cfg file.

 

Thanks. I've updated UD to the latest version but I still get the error. See the details in this screencast:

 

https://youtu.be/zhiYnhxgoOs

 

The unassigned.devices.cfg file is empty. 

 

UD did not mount those drives, but thinks they are mounted.  How did they get mounted?

 

What is the output of the command:

mount

 

Another screencast for you. In it I have turned off the external USB drive enclosure and turned it back on. I am able to mount the drives with UD but not unmount them. Here's a screencast demonstrating this: https://youtu.be/MDQNY35Zq3A

 

As requested, the results of mount:

 

 

/dev/loop0 on / type btrfs (rw,relatime,space_cache,subvolid=311,subvol=/btrfs/subvolumes/74<snip>73)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666)
sysfs on /sys type sysfs (ro,nosuid,nodev,noexec,relatime)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,relatime,mode=755)
cpuset on /sys/fs/cgroup/cpuset type cgroup (ro,nosuid,nodev,noexec,relatime,cpuset)
cpu on /sys/fs/cgroup/cpu type cgroup (ro,nosuid,nodev,noexec,relatime,cpu)
cpuacct on /sys/fs/cgroup/cpuacct type cgroup (ro,nosuid,nodev,noexec,relatime,cpuacct)
blkio on /sys/fs/cgroup/blkio type cgroup (ro,nosuid,nodev,noexec,relatime,blkio)
memory on /sys/fs/cgroup/memory type cgroup (ro,nosuid,nodev,noexec,relatime,memory)
devices on /sys/fs/cgroup/devices type cgroup (ro,nosuid,nodev,noexec,relatime,devices)
freezer on /sys/fs/cgroup/freezer type cgroup (ro,nosuid,nodev,noexec,relatime,freezer)
net_cls on /sys/fs/cgroup/net_cls type cgroup (ro,nosuid,nodev,noexec,relatime,net_cls)
perf_event on /sys/fs/cgroup/perf_event type cgroup (ro,nosuid,nodev,noexec,relatime,perf_event)
pids on /sys/fs/cgroup/pids type cgroup (ro,nosuid,nodev,noexec,relatime,pids)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
rootfs on /UNASSIGNED type rootfs (rw,size=6111816k,nr_inodes=1527954)
rootfs on /UNRAID type rootfs (rw,size=6111816k,nr_inodes=1527954)
/dev/md1 on /UNRAID/disk1 type xfs (rw,noatime,nodiratime,attr2,inode64,noquota)
/dev/md2 on /UNRAID/disk2 type xfs (rw,noatime,nodiratime,attr2,inode64,noquota)
/dev/sdb1 on /UNRAID/cache type btrfs (rw,noatime,nodiratime,ssd,space_cache,subvolid=5,subvol=/)
shfs on /UNRAID/user0 type fuse.shfs (rw,nosuid,nodev,noatime,user_id=0,group_id=0,allow_other)
shfs on /UNRAID/user type fuse.shfs (rw,nosuid,nodev,noatime,user_id=0,group_id=0,allow_other)
/dev/sdc1 on /FLASH type vfat (rw,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
shfs on /nobody/.kde type fuse.shfs (rw,nosuid,nodev,noatime,user_id=0,group_id=0,allow_other)
/dev/loop0 on /etc/resolv.conf type btrfs (rw,relatime,space_cache,subvolid=5,subvol=/containers/81<snip>15/resolv.conf)
/dev/loop0 on /etc/hostname type btrfs (rw,relatime,space_cache,subvolid=5,subvol=/containers/81<snip>15/hostname)
/dev/loop0 on /etc/hosts type btrfs (rw,relatime,space_cache,subvolid=5,subvol=/containers/81<snip>15/hosts)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
proc on /proc/bus type proc (ro,nosuid,nodev,noexec,relatime)
proc on /proc/fs type proc (ro,nosuid,nodev,noexec,relatime)
proc on /proc/irq type proc (ro,nosuid,nodev,noexec,relatime)
proc on /proc/sys type proc (ro,nosuid,nodev,noexec,relatime)
proc on /proc/sysrq-trigger type proc (ro,nosuid,nodev,noexec,relatime)
tmpfs on /proc/kcore type tmpfs (rw,nosuid,mode=755)
tmpfs on /proc/timer_list type tmpfs (rw,nosuid,mode=755)

 

17 minutes ago, PeeBee said:

rootfs on /UNASSIGNED type rootfs (rw,size=6111816k,nr_inodes=1527954)
rootfs on /UNRAID type rootfs (rw,size=6111816k,nr_inodes=1527954)
/dev/md1 on /UNRAID/disk1 type xfs (rw,noatime,nodiratime,attr2,inode64,noquota)
/dev/md2 on /UNRAID/disk2 type xfs (rw,noatime,nodiratime,attr2,inode64,noquota)
/dev/sdb1 on /UNRAID/cache type btrfs (rw,noatime,nodiratime,ssd,space_cache,subvolid=5,subvol=/)
shfs on /UNRAID/user0 type fuse.shfs (rw,nosuid,nodev,noatime,user_id=0,group_id=0,allow_other)
shfs on /UNRAID/user type fuse.shfs (rw,nosuid,nodev,noatime,user_id=0,group_id=0,allow_other)
/dev/sdc1 on /FLASH type vfat (rw,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)

I'm no expert on how unRAID mounts devices,  but this does not look right at all.  Where did the /UNASSIGNED and /UNRAID come from?

38 minutes ago, dlandon said:

I'm no expert on how unRAID mounts devices,  but this does not look right at all.  Where did the /UNASSIGNED and /UNRAID come from?

 

This is something I found in volume mappings. I'm new to this so I'm not sure how the mappings occur. 

 

/UNRAID ⇔ /mnt/ /nobody/.kde ⇔ /mnt/user/appdata/kde /UNASSIGNED ⇔ /mnt/disks/ /FLASH ⇔ /boot/

7 hours ago, PeeBee said:

 

This is something I found in volume mappings. I'm new to this so I'm not sure how the mappings occur. 

 

/UNRAID ⇔ /mnt/ /nobody/.kde ⇔ /mnt/user/appdata/kde /UNASSIGNED ⇔ /mnt/disks/ /FLASH ⇔ /boot/

Update to the latest UD 2018.01.08 and then try to mount both UD disks.  It should refuse to mount them because the disks appear as null devices.  This will log some information about what UD sees as the disk serial numbers.  Post the diagnostics so I can see the log from the mount attempts.  I don't think the device where those disks are mounted is providing the information UD needs to properly mount the disks, or UD isn't handling the information properly.

1 hour ago, dlandon said:

Update to the latest UD 2018.01.08 and then try to mount both UD disks.  It should refuse to mount them because the disks appear as null devices.  This will log some information about what UD sees as the disk serial numbers.  Post the diagnostics so I can see the log from the mount attempts.  I don't think the device where those disks are mounted is providing the information UD needs to properly mount the disks, or UD isn't handling the information properly.

 

Another quick screencast for you: https://youtu.be/8qPEz5MxIt8.

 

Here's the error message in UD:

Warning: Illegal string offset 'ID_SERIAL_SHORT' in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1290 
Warning: Illegal string offset 'ID_MODEL' in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1291 
Warning: Illegal string offset 'DEVTYPE' in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1302 
Warning: syntax error, unexpected '=' in Unknown on line 14 in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1279 
Warning: syntax error, unexpected '=' in Unknown on line 22 in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1279 
Warning: syntax error, unexpected '=' in Unknown on line 28 in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1279

Diagnostics attached. 

 

I'll repeat this test tonight with just one drive installed in the enclosure to see how it behaves differently. 

 

Thanks for all your support on this. It's very appreciated. 

 

tower-diagnostics-20180108-0724.zip

1 hour ago, PeeBee said:

 

Another quick screencast for you: https://youtu.be/8qPEz5MxIt8.

 

Here's the error message in UD:

Warning: Illegal string offset 'ID_SERIAL_SHORT' in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1290 
Warning: Illegal string offset 'ID_MODEL' in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1291 
Warning: Illegal string offset 'DEVTYPE' in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1302 
Warning: syntax error, unexpected '=' in Unknown on line 14 in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1279 
Warning: syntax error, unexpected '=' in Unknown on line 22 in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1279 
Warning: syntax error, unexpected '=' in Unknown on line 28 in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1279

Diagnostics attached. 

 

I'll repeat this test tonight with just one drive installed in the enclosure to see how it behaves differently. 

 

Thanks for all your support on this. It's very appreciated. 

 

tower-diagnostics-20180108-0724.zip

The problem is that UD is not getting a disk identifier.   That is why there is nothing next to the icon on the UD devices page.  When the device is null, the result is very messy and is why you are getting all the php errors.  I've updated UD so a device that does not give a disk identifier will not be added to the UD devices.  This doesn't solve your problem, but all those errors and the false indication of a disk being mounted when it is not is extremely messy.

 

Please update once again to 2018.01.08a and then look at the UD page.  Your devices should not show in the UD page.

 

Then show the result of:

ls /dev/

 

EDIT: Also:

ls -l /dev/disk/by-id/

 

Edited January 8, 20188 yr by dlandon

I currently just installed a NVME drive in unassigned devices.

Unraid was able to see this and I just finished performing a preclear and after that the Samsung drive turns off and I am unable to format or mount the buttons are greyed out.

 

How do I mount nvme in unassigned devices.

 

 

57 minutes ago, deaerator said:

I currently just installed a NVME drive in unassigned devices.

Unraid was able to see this and I just finished performing a preclear and after that the Samsung drive turns off and I am unable to format or mount the buttons are greyed out.

 

How do I mount nvme in unassigned devices.

 

 

Click on help and read.  You'll find the answer.

22 minutes ago, dlandon said:

Click on help and read.  You'll find the answer.

 

I followed the steps but after pre-clear it just remains in a standby mode and I cannot delete any partitions.

 

After Tower Login prompt this is what I see

 

blockdev: cannot open dev/nvme0n1p: No such file or directory

 

26 minutes ago, deaerator said:

 

I followed the steps but after pre-clear it just remains in a standby mode and I cannot delete any partitions.

 

After Tower Login prompt this is what I see

 

blockdev: cannot open dev/nvme0n1p: No such file or directory

 

Give me a screenshot of the UD page and diagnostics.

17 minutes ago, dlandon said:

Give me a screenshot of the UD page and diagnostics.

tower-diagnostics-20180108-1729.zip

19 minutes ago, deaerator said:

tower-diagnostics-20180108-1729.zip

Click the red X to delete the preclear status file.

I already did that.

Edited January 8, 20188 yr by deaerator

17 minutes ago, deaerator said:

I already did that.

Show the results from the command:

ls -l /dev/disk/by-id/

 

It looks like the /flash/config/plugins/unassigned.devices/unassigned.devices.cfg file has a problem.  Check the file for references to the disk that is a problem.  Remove all of them and let UD recreate the disk entry.

 

19 minutes ago, dlandon said:

It looks like the /flash/config/plugins/unassigned.devices/unassigned.devices.cfg file has a problem.  Check the file for references to the disk that is a problem.  Remove all of them and let UD recreate the disk entry.

 

That didn't work.

 

Does it matter how this drive is installed.  I am using a pcie riser.

3 minutes ago, deaerator said:

That didn't work.

 

Does it matter how this drive is installed.  I am using a pcie riser.

I don't know.  Try removing the preclear plugin and reboot.

Removing Plugin and reboot didn't do a thing.

 

FML

18 minutes ago, deaerator said:

Removing Plugin and reboot didn't do a thing.

 

FML

Post or pm the unassigned.devices.cfg file.  Something is wrong with it.  UD thinks there is a mount point on that disk.

[Config]
common_cmd = ""
destructive_mode = "enabled"
automount_usb = "no"
preclear_daemon = "no"
samba_v1 = "no"
smb_security = "no"

[Crucial_CT525MX300SSD1_172317666C71]
mountpoint.1 = "/mnt/disks/PLEX"
automount = "yes"
share.1 = "yes"

[Samsung_SSD_960_EVO_250GB_S3ESNX0JC76289K]
mountpoint.1 = "/mnt/disks/POS"
automount = "yes"
share.1 = "yes"

 

8 hours ago, dlandon said:

The problem is that UD is not getting a disk identifier.   That is why there is nothing next to the icon on the UD devices page.  When the device is null, the result is very messy and is why you are getting all the php errors.  I've updated UD so a device that does not give a disk identifier will not be added to the UD devices.  This doesn't solve your problem, but all those errors and the false indication of a disk being mounted when it is not is extremely messy.

 

Please update once again to 2018.01.08a and then look at the UD page.  Your devices should not show in the UD page.

 

Then show the result of:

ls /dev/

 

EDIT: Also:

ls -l /dev/disk/by-id/

 

 

I updated to  2018.01.08a, shut down the server and restarted it with the drives removed. I then plugged in the drives and UD reported them, just like before.

 

ls /dev:

 

ls -l /dev/disk/by-id doesn't work on my system because there's no /dev/disk folder. (Is that because of the volume mappings?)

 

 

 

 

 

 

2 minutes ago, PeeBee said:

 

I updated to  2018.01.08a, shut down the server and restarted it with the drives removed. I then plugged in the drives and UD reported them, just like before.

 

ls /dev:

 

ls -l /dev/disk/by-id doesn't work on my system because there's no /dev/disk folder. (Is that because of the volume mappings?)

 

 

 

 

 

 

If there is no /dev/disk/by-id/ UD cannot find the disk information.  I don't know what you are doing with the volume mappings, but do not do that.