dlandon

Ignore it or wait for another FCP update.

Ignore it, or wait for another FCP update.

An update to UD created that folder. FCP is detecting it now. Update FCP.

Sometime ago, a file locking mechanism was added to UD to insure exclusive access when writing files. The idea is to prevent two processes from trying to write a configuration file at the same time. This insures that one process does not overwrite another processe's changes. File locking also applies to saving udev information on devices. The file lock was applied even when just reading the udev file. This created a lot of extra ramfs file system work that was not necessary because the refresh of UD does a lot of udev lookups to be sure the GUI is up to date. Because Linux is so poor at file locking, I had to use my own mechanism. Where this is going is I suspect all that file locking may have been the source of 'stuck' UD where the Unraid wave was constantly showing. If this doesn't clear up the hangs, I have some debugging ideas so we can get to the source of the problem.

There is a new feature in UD to help with plugins that need a mount point folder. UD now creates a mount folder '/mnt/addons'. This folder should be used to mount your plugin devices to prevent FCP warnings and keep your mounts separated from UD. It is recommended you switch to this new folder for your addon and custom mounts. You are welcome to leave the mounts at '/mnt/disks' or '/mnt/remotes'. Things will still work, but if you request support for UD issues, you will be asked to remove them first. One thing to keep in mind is there is a protection added to the '/mnt/addons' so a misconfigured app cannot fill the rootfs and crash the system. If you mount something at '/mnt/addons' before UD is installed, you will see a reboot message over the banner. This is because UD cannot apply the protection while a device is mounted at '/mnt/addons'. You will have to delay any mounts at '/mnt/addons' until UD has installed.

Also, when the UD GUI hangs, show the output of this command: ls -la /tmp/unassigned.devices/

Post diagnostics before you reboot.

I would shut it down, check that cables are secure, boot it up, mount it and remove the data. You will probably have to reformat the disk. Why are you using ext4? XFS or BTRFS would be better choices for Unraid. NTFS if you want Windows read/write capabilities.

A Pool device share will be the name of the Pool device. A multi device pool will have one Pool (and therefore share) name. You can't have a Pool named 'Test' and a share named 'Test' on another Pool device or on the array. That would be duplicates. If that is the case here, there is a problem. Unraid should not allow that.

I have no idea. I don't have any experience with the zfs plugin.

That recommendation was from many years ago because is seemed to be an easy answer to just use the /mnt/disks/ or /mnt/remotes/ because UD applied a protection to prevent the rootfs from filling up if something was misconfigured. While it appears to work in most situations, it is a problem for you because your zfs disk is mounted at /mnt/disks/ before UD has installed. We are trying to re-think this to see if there might be a better answer. If you postpone the zfs mount until after UD starts, you shouldn't get the reboot message.

Your disk is struggling and dropping off-line: Mar 1 23:09:43 Mediaserver flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 1 23:10:02 Mediaserver kernel: EXT4-fs error: 891 callbacks suppressed Mar 1 23:10:02 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm PMS GTP: reading directory lblock 0 Mar 1 23:10:12 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm python3: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 9 TIMES] ### Mar 1 23:10:18 Mediaserver kernel: EXT4-fs error: 880 callbacks suppressed Mar 1 23:10:18 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm python3: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 9 TIMES] ### Mar 1 23:10:39 Mediaserver kernel: EXT4-fs error: 384 callbacks suppressed Mar 1 23:10:39 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm PMS GTP: reading directory lblock 0 Mar 1 23:11:07 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm python3: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 9 TIMES] ### Mar 1 23:11:41 Mediaserver kernel: EXT4-fs error: 405 callbacks suppressed Mar 1 23:11:41 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm PMS GTP: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 1 TIMES] ### Mar 1 23:12:55 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm mono: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 9 TIMES] ### Mar 1 23:13:03 Mediaserver kernel: EXT4-fs error: 34 callbacks suppressed Mar 1 23:13:03 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm mono: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 2 TIMES] ### Mar 1 23:15:19 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm PMS GTP: reading directory lblock 0 Mar 1 23:17:35 Mediaserver emhttpd: spinning down /dev/sdq Mar 1 23:17:37 Mediaserver kernel: EXT4-fs warning (device sdc1): htree_dirblock_to_tree:1072: inode #129368065: lblock 0: comm Thread Pool Wor: error -5 reading directory block Mar 1 23:18:01 Mediaserver sSMTP[5644]: Creating SSL connection to host Mar 1 23:18:01 Mediaserver sSMTP[5644]: SSL connection using TLS_AES_256_GCM_SHA384 Mar 1 23:18:03 Mediaserver sSMTP[5644]: Sent mail for [email protected] (221 2.0.0 closing connection k4-20020ac84784000000b003b869f71eedsm9489451qtq.66 - gsmtp) uid=0 username=xxx outbytes=837 Mar 1 23:18:47 Mediaserver flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 1 23:18:56 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm PMS GTP: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 7 TIMES] ### Mar 1 23:24:18 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm python3: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 9 TIMES] ### Mar 1 23:24:58 Mediaserver kernel: EXT4-fs error: 890 callbacks suppressed Mar 1 23:24:58 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm python3: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 9 TIMES] ### Mar 1 23:25:05 Mediaserver kernel: EXT4-fs error: 1272 callbacks suppressed Mar 1 23:25:05 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm PMS GTP: reading directory lblock 0 Mar 1 23:25:47 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm python3: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 9 TIMES] ### Mar 1 23:25:53 Mediaserver kernel: EXT4-fs error: 404 callbacks suppressed Mar 1 23:25:53 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm PMS GTP: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 1 TIMES] ### Mar 1 23:27:16 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm mono: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 9 TIMES] ### Mar 1 23:28:12 Mediaserver kernel: EXT4-fs error: 37 callbacks suppressed Mar 1 23:28:12 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm PMS GTP: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 2 TIMES] ### Mar 1 23:34:53 Mediaserver flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 1 23:35:22 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm PMS GTP: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 6 TIMES] ### Mar 1 23:39:26 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm python3: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 9 TIMES] ### Mar 1 23:39:48 Mediaserver kernel: EXT4-fs error: 890 callbacks suppressed Mar 1 23:39:48 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm PMS GTP: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 1 TIMES] ### Mar 1 23:40:17 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm python3: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 8 TIMES] ### Mar 1 23:40:20 Mediaserver kernel: EXT4-fs error: 886 callbacks suppressed Mar 1 23:40:20 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm python3: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 9 TIMES] ### Mar 1 23:41:02 Mediaserver kernel: EXT4-fs error: 375 callbacks suppressed Mar 1 23:41:02 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm python3: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 9 TIMES] ### Mar 1 23:42:06 Mediaserver kernel: EXT4-fs error: 404 callbacks suppressed Mar 1 23:42:06 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm PMS GTP: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 8 TIMES] ### Mar 1 23:54:13 Mediaserver kernel: usb 1-3: USB disconnect, device number 7 Mar 1 23:54:13 Mediaserver kernel: sd 9:0:0:0: [sdq] Synchronizing SCSI cache Mar 1 23:54:13 Mediaserver kernel: sd 9:0:0:0: [sdq] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK Mar 1 23:54:14 Mediaserver kernel: usb 1-3: new high-speed USB device number 8 using xhci_hcd Mar 1 23:54:14 Mediaserver kernel: usb-storage 1-3:1.0: USB Mass Storage device detected Mar 1 23:54:14 Mediaserver kernel: scsi host9: usb-storage 1-3:1.0 Mar 1 23:54:15 Mediaserver kernel: scsi 9:0:0:0: Direct-Access Seagate Portable 9300 PQ: 0 ANSI: 6 Mar 1 23:54:15 Mediaserver kernel: sd 9:0:0:0: Attached scsi generic sg2 type 0 Mar 1 23:54:15 Mediaserver kernel: sd 9:0:0:0: [sdq] Very big device. Trying to use READ CAPACITY(16). Mar 1 23:54:15 Mediaserver kernel: sd 9:0:0:0: [sdq] 7814037167 512-byte logical blocks: (4.00 TB/3.64 TiB) Mar 1 23:54:15 Mediaserver kernel: sd 9:0:0:0: [sdq] 4096-byte physical blocks Mar 1 23:54:15 Mediaserver kernel: sd 9:0:0:0: [sdq] Write Protect is off Mar 1 23:54:15 Mediaserver kernel: sd 9:0:0:0: [sdq] Mode Sense: 4f 00 00 00 Mar 1 23:54:15 Mediaserver kernel: sd 9:0:0:0: [sdq] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 1 23:54:18 Mediaserver kernel: sdq: sdq1 Mar 1 23:54:18 Mediaserver kernel: sd 9:0:0:0: [sdq] Attached SCSI disk Mar 1 23:54:18 Mediaserver emhttpd: read SMART /dev/sdq Mar 1 23:54:20 Mediaserver unassigned.devices: Mounting partition 'sdq1' at mountpoint '/mnt/disks/MyExternalDrive'... Mar 1 23:54:20 Mediaserver unassigned.devices: Partition 'sdq1' is already mounted. Mar 1 23:54:35 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm python3: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 9 TIMES] ### Mar 1 23:55:28 Mediaserver kernel: EXT4-fs error: 890 callbacks suppressed Mar 1 23:55:28 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm python3: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 9 TIMES] ### Mar 1 23:56:15 Mediaserver kernel: EXT4-fs error: 1270 callbacks suppressed Mar 1 23:56:15 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm python3: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 9 TIMES] ### Mar 1 23:58:40 Mediaserver kernel: EXT4-fs error: 404 callbacks suppressed Mar 1 23:58:40 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm PMS GTP: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 7 TIMES] ### Mar 2 00:05:18 Mediaserver kernel: EXT4-fs warning (device sdc1): htree_dirblock_to_tree:1072: inode #129368065: lblock 0: comm Thread Pool Wor: error -5 reading directory block ### [PREVIOUS LINE REPEATED 1 TIMES] ### Mar 2 00:07:35 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm PMS GTP: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 1 TIMES] ### Mar 2 00:09:16 Mediaserver emhttpd: spinning down /dev/sdq Mar 2 00:09:29 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm python3: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 9 TIMES] ### Mar 2 00:10:13 Mediaserver kernel: EXT4-fs error: 890 callbacks suppressed Mar 2 00:10:13 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm python3: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 9 TIMES] ### Mar 2 00:10:27 Mediaserver root: Plex-Meta-Manager: Could not download icon https://metamanager.wiki/en/latest/_static/pmm.png Mar 2 00:10:51 Mediaserver kernel: EXT4-fs error: 1270 callbacks suppressed Mar 2 00:10:51 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm python3: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 9 TIMES] ### Mar 2 00:11:17 Mediaserver kernel: EXT4-fs error: 404 callbacks suppressed Mar 2 00:11:17 Mediaserver kernel: EXT4-fs error (device sdc1): __ext4_find_entry:1663: inode #129368065: comm mono: reading directory lblock 0 ### [PREVIOUS LINE REPEATED 9 TIMES] ### Mar 2 00:13:39 Mediaserver kernel: usb 1-3: USB disconnect, device number 8 Mar 2 00:13:39 Mediaserver kernel: sd 9:0:0:0: [sdq] Synchronizing SCSI cache Mar 2 00:13:39 Mediaserver kernel: sd 9:0:0:0: [sdq] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK Mar 2 00:13:39 Mediaserver kernel: usb 1-3: new high-speed USB device number 9 using xhci_hcd Mar 2 00:13:39 Mediaserver kernel: usb-storage 1-3:1.0: USB Mass Storage device detected Mar 2 00:13:39 Mediaserver kernel: scsi host9: usb-storage 1-3:1.0 Mar 2 00:13:40 Mediaserver kernel: scsi 9:0:0:0: Direct-Access Seagate Portable 9300 PQ: 0 ANSI: 6 Mar 2 00:13:40 Mediaserver kernel: sd 9:0:0:0: Attached scsi generic sg2 type 0 Mar 2 00:13:40 Mediaserver kernel: sd 9:0:0:0: [sdq] Very big device. Trying to use READ CAPACITY(16). Mar 2 00:13:40 Mediaserver kernel: sd 9:0:0:0: [sdq] 7814037167 512-byte logical blocks: (4.00 TB/3.64 TiB) Mar 2 00:13:40 Mediaserver kernel: sd 9:0:0:0: [sdq] 4096-byte physical blocks Mar 2 00:13:40 Mediaserver kernel: sd 9:0:0:0: [sdq] Write Protect is off Mar 2 00:13:40 Mediaserver kernel: sd 9:0:0:0: [sdq] Mode Sense: 4f 00 00 00 Mar 2 00:13:40 Mediaserver kernel: sd 9:0:0:0: [sdq] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 2 00:13:44 Mediaserver kernel: sdq: sdq1 Mar 2 00:13:44 Mediaserver kernel: sd 9:0:0:0: [sdq] Attached SCSI disk Mar 2 00:13:44 Mediaserver emhttpd: read SMART /dev/sdq Mar 2 00:13:45 Mediaserver unassigned.devices: Mounting partition 'sdq1' at mountpoint '/mnt/disks/MyExternalDrive'... Mar 2 00:13:45 Mediaserver unassigned.devices: Partition 'sdq1' is already mounted.

Unraid is not supported when running on a Hypervisor. You should look into the backup software and see why the files are not being closed. Depending on the server to time out and close the files is not proper file management.

Are you running Unraid in VMWare?

Post diagnostics.

Something got confused and it just showed up on UD.

Reboot. The csrf_token is managed by Unraid and UD does nothing with csrf.

I'm not sure that will get you anywhere. Show me a screen shot of Settings->SMB Settings.

Remove it.

Go to UD settings and enter the drive password there and UD will use that to mount the disk. You'll need to enter the password for each encrypted disk.

Something might be clobberig the /tmp/ file structure. Confirm that you have Plex handling the /tmp/ file structure properly.

There may be something in the UD config file that is causing this issue. Do this: Remove UD. PM me the '/flash/config/plugins/unassigned.devices/unassigned.devices.cfg'. Remove the '/flash/config/plugins/unassigned.devices/unassigned.devices.cfg' file. Re-install UD. Re-install your SSD device.

That doesn't mean your router/dhcp server has finished handing out IP addresses. Create a User Script that starts on the first array start only with the followiing contents: sleep 10 /usr/local/sbin/rc.unassigned mount autoshares What this will do is wait 10 seconds (feel free to adjust this), and then re-auto mount remote shares. If the share is already mounted, nothing will change. If an auto mount share is not mounted, it will then be mounted.

Your ram is being consumed and there is no more room for UD to create a lock file. The lock is a few bytes.

That's the old drive that is 1% full: Have you confused the old and new drives?