dlandon

The gray 'Array' showing on the UD disks is because Unraid does not recognize them as Unassigned Disks. Try clicking on the double arrows in the upper right of the UD page. That will tell Unraid to re-evaluate Unassigned Disks.

On my test system I have a two disk pool: root@BackupServer:~# btrfs fi show Label: none uuid: b1cdca9c-b741-440c-a843-3bb48838d544 Total devices 1 FS bytes used 896.00KiB devid 1 size 20.00GiB used 6.02GiB path /dev/loop2 Label: none uuid: d521949e-bfae-4e6c-a045-33a23cc4bd12 Total devices 1 FS bytes used 1.93MiB devid 1 size 1.00GiB used 126.38MiB path /dev/loop3 Label: 'Test_Pool' uuid: 7693b0fe-e954-4462-a471-657959e9f299 Total devices 2 FS bytes used 4.15GiB devid 1 size 14.56GiB used 3.28GiB path /dev/sdb1 devid 2 size 28.92GiB used 3.28GiB path /dev/sdc1 On my system it's 'Test_Pool'.

Please show a screen shot of the disks in UD.

@JorgeB It looks like the problem is there are no labels on the sdt and sdr disks. UD won't see disks as a pool unless the UUID and labels (mount points to UD) are the same.

The problem is that UD does not know the pool devices. UD recognizes a pool by the same UUID and label on both devices. It looks like sdt1 and sdr1 are a pool because they are the same UUID. Try setting the mount point on those devices. That will also change the disk label. You may get a message about duplicate mount points. Just try each until the mount point takes.

Your disk has a problem: Jul 13 21:05:34 Jiraiya unassigned.devices: Adding partition 'sdj1'... Jul 13 21:05:34 Jiraiya unassigned.devices: Mounting partition 'sdj1' at mountpoint '/mnt/disks/UA_POOL'... Jul 13 21:05:34 Jiraiya unassigned.devices: Mount drive command: /sbin/mount -t 'btrfs' -o rw,noatime,nodiratime '/dev/sdj1' '/mnt/disks/UA_POOL' Jul 13 21:05:34 Jiraiya kernel: BTRFS info (device sdj1): flagging fs with big metadata feature Jul 13 21:05:34 Jiraiya kernel: BTRFS info (device sdj1): disk space caching is enabled Jul 13 21:05:34 Jiraiya kernel: BTRFS info (device sdj1): has skinny extents Jul 13 21:05:34 Jiraiya kernel: BTRFS error (device sdj1): devid 2 uuid c7264057-941e-45fd-895a-f3329a76976f is missing Jul 13 21:05:34 Jiraiya kernel: BTRFS error (device sdj1): failed to read chunk tree: -2 Jul 13 21:05:34 Jiraiya kernel: BTRFS error (device sdj1): open_ctree failed Jul 13 21:05:34 Jiraiya unassigned.devices: Mount of 'sdj1' failed: 'mount: /mnt/disks/UA_POOL: wrong fs type, bad option, bad superblock on /dev/sdj1, missing codepage or helper program, or other error. ' Jul 13 21:05:34 Jiraiya unassigned.devices: Partition 'Z5215WMY' cannot be mounted. This is an error that is caused by an update to UD Preclear: Jul 13 21:05:34 Jiraiya atd[11438]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libc.so.6: version `GLIBC_2.34' not found (required by /lib64/libresolv.so.2) Jul 13 21:05:34 Jiraiya atd[11438]: PAM adding faulty module: /lib64/security/pam_unix.so Jul 13 21:05:34 Jiraiya atd[11438]: Module is unknown Jul 13 21:05:34 Jiraiya atd[11445]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libc.so.6: version `GLIBC_2.34' not found (required by /lib64/libresolv.so.2) Jul 13 21:05:34 Jiraiya atd[11445]: PAM adding faulty module: /lib64/security/pam_unix.so Jul 13 21:05:34 Jiraiya atd[11445]: Module is unknown Be sure UD Preclear is updated to the latest version and reboot to clear this up.

It's caused by an update to the UD Preclear plugin. Update to the latest UD Preclear and then reboot. It will clear up the issue.

I fixed a bug that might be related to this issue. The mount point permissions were not being set because of a syntax issue in UD.

Reboot.

Reboot. Installing UD Preclear and then removing it will not clear up the issue until you reboot.

Fixed in latest release.

Your smb-extra.conf file is corrupted: #unassigned_devices_start #Unassigndd devices shave includes: (iîclude = /tmp/unassinned/derices/smb-settings.conf #unassig.ed_deviães_gnd Go to Settings->SMB->SMB Extras tab and remove the corrupted text and click 'Apply'. Then uninstall UD and re-install it. The text will be corrected when UD is re-installed. You should probably take your flash drive to a PC and run a check to see if there are other issues with the file system.

An update to UD Preclear is probably causing this problem. Update UD Preclear and reboot. All should be good again.

Glad you sorted it out.

Update UD Preclear and reboot.

Update UD Preclear and reboot.

OK. I see it now.

My bad. You did the right directory. The share configuration is set up correctly. As you can see only 'jus' has read and write access. At a command line type this command: /etc/rc.d/rc.samba restart Give it a few minutes and then see if you can see the share. If that doesn't work, post your diagnostics zip file.

What is the user scrpt that is causing this issue? I expect it will because it has glibc 2.35 already installed and UD Preclear won't upgrade it.

Use this command to look at the samba share configuration for the UD CCTV share: cat /etc/samba/unassigned.devices/CCTV You'll see the user permissions, etc for the CCTV share. You may see something there that gives a clue on the issue you are seeing. Post it here so I can have a look if you don't see anything obvious.

You are not having issues with any Unraid shares?

Yes it will. I've explained how this happens. I see it and have explained how this is happening. It took a while to totally understand the problem because simply uopdating a package should not cause the problems you are seeing. As I've already said, your options are: Do not install UD Preclear. Update to Unraid 6.11-rc1.

The problem is that a plugin you are using is depending on the glibc library installed in Unraid when it starts. a Daemon? When UD Preclear updates the glibc package, the daemon is losing access to the library it needs and then fails. Do you have any idea what is using dlopen? You have two options at this point: Don't install the UD Preclear plugin. Upgrde to Unraid 6.11-rc1 that will be available soon.

The problem is that a plugin you are using is depending on the glibc library installed in Unraid when it starts. a Daemon? When UD Preclear updates the glibc package, the daemon is losing access to the library it needs and then fails. You have two options at this point: Don't install the UD Preclear plugin. Upgrde to Unraid 6.11-rc1 that will be available soon.

The problem is that a plugin you are using is depending on the glibc library installed in Unraid when it starts. a Daemon? When UD Preclear updates the glibc package, the daemon is losing access to the library it needs and then fails. Do you have any idea what is using dlopen? You have two options at this point: Don't install the UD Preclear plugin. Upgrde to Unraid 6.11-rc1 that will be available soon.