thedman

I have this exact same issue, did you ever find a permanent fix besides restarting? Also could you share what you did with your user script?

Thank you!

Any update to this Template to pick up the new support for other downloaders that the author added recently. In my case Transmission?

Thanks for the help, I will take a look. When it is unmounted and has the greyed out reboot icon. The check mark does not respond to any clicks. I can only look at the logs. Can I do any unmount/fix via the console? Thanks again for your and anyone else's help.

Diagnostics attached. dserver-diagnostics-20240203-1210.zip

It is usb. I will post diagnostics. It had been running fine for over a year, so maybe some new spin down or power saving on the drive?

I think it eventually must fill up some logs, and the entire unraid system becomes unassailable, the last thing on the console says file system error shutdown on sdi1, and I can't do anything but to hard power off.

I have a strange issue that has started happening the last few months, I always update unraid and plugins weekly. I have a 12 TB usd drive that I use through unassigned devices and use as an on system backup to my main media array. It seems to mount fine on new boot or reboot to sda1, but after some time it tries to remount to sdi1. I am not sure what causes this. Then it fails and just shows a greyed out reboot icon in the plugin. Rebooting fixes again for a while but then it happens again. Attached are the logs from the mounts. Just looking for some assistance on where to look to try and fix. Thanks. -------------------------------------- text error warn system array login Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB) Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] Write Protect is off Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] Mode Sense: 2f 00 00 00 Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 1 09:52:52 dserver kernel: sda: sda1 Feb 1 09:52:52 dserver kernel: sd 0:0:0:0: [sda] Attached SCSI disk Feb 1 09:53:10 dserver emhttpd: TOSHIBA_MG07ACA12TE_2040A0BQFDUG (sda) 512 23437770752 Feb 1 09:53:10 dserver emhttpd: read SMART /dev/sda Feb 1 09:53:22 dserver unassigned.devices: Mounting partition 'sda1' at mountpoint '/mnt/disks/Backupdp'... Feb 1 09:53:22 dserver unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,relatime '/dev/sda1' '/mnt/disks/Backupdp' Feb 1 09:53:22 dserver kernel: XFS (sda1): Mounting V5 Filesystem Feb 1 09:53:23 dserver kernel: XFS (sda1): Starting recovery (logdev: internal) Feb 1 09:53:23 dserver kernel: XFS (sda1): Ending recovery (logdev: internal) Feb 1 09:53:23 dserver unassigned.devices: Successfully mounted '/dev/sda1' on '/mnt/disks/Backupdp'. ** Press ANY KEY to close this window ** After about 45 minutes.... text error warn system array login Feb 1 13:06:57 dserver kernel: sd 9:0:0:0: [sdi] Very big device. Trying to use READ CAPACITY(16). Feb 1 13:06:57 dserver kernel: sd 9:0:0:0: [sdi] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB) Feb 1 13:06:57 dserver kernel: sd 9:0:0:0: [sdi] 4096-byte physical blocks Feb 1 13:06:57 dserver kernel: sd 9:0:0:0: [sdi] Write Protect is off Feb 1 13:06:57 dserver kernel: sd 9:0:0:0: [sdi] Mode Sense: 2f 00 00 00 Feb 1 13:06:57 dserver kernel: sd 9:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 1 13:07:08 dserver kernel: sdi: sdi1 Feb 1 13:07:08 dserver kernel: sd 9:0:0:0: [sdi] Attached SCSI disk Feb 1 13:07:10 dserver unassigned.devices: Error: Device '/dev/sdi1' mount point 'Backupdp' - name is reserved, used in the array or a pool, or by an unassigned device. Feb 1 13:08:57 dserver kernel: sd 9:0:0:0: [sdi] Synchronizing SCSI cache Feb 1 13:08:57 dserver kernel: sd 9:0:0:0: [sdi] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] Very big device. Trying to use READ CAPACITY(16). Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB) Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] 4096-byte physical blocks Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] Write Protect is off Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] Mode Sense: 2f 00 00 00 Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 1 13:08:58 dserver kernel: sdi: sdi1 Feb 1 13:08:58 dserver kernel: sd 9:0:0:0: [sdi] Attached SCSI disk Feb 1 13:09:01 dserver unassigned.devices: Error: Device '/dev/sdi1' mount point 'Backupdp' - name is reserved, used in the array or a pool, or by an unassigned device. Feb 1 14:03:39 dserver kernel: sd 9:0:0:0: [sdi] Synchronizing SCSI cache Feb 1 14:03:39 dserver kernel: sd 9:0:0:0: [sdi] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK Feb 1 14:03:41 dserver kernel: sd 9:0:0:0: [sdi] Very big device. Trying to use READ CAPACITY(16). Feb 1 14:03:41 dserver kernel: sd 9:0:0:0: [sdi] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB) Feb 1 14:03:41 dserver kernel: sd 9:0:0:0: [sdi] 4096-byte physical blocks Feb 1 14:03:41 dserver kernel: sd 9:0:0:0: [sdi] Write Protect is off Feb 1 14:03:41 dserver kernel: sd 9:0:0:0: [sdi] Mode Sense: 2f 00 00 00 Feb 1 14:03:41 dserver kernel: sd 9:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 1 14:03:51 dserver kernel: sdi: sdi1 Feb 1 14:03:51 dserver kernel: sd 9:0:0:0: [sdi] Attached SCSI disk Feb 1 14:03:52 dserver unassigned.devices: Error: Device '/dev/sdi1' mount point 'Backupdp' - name is reserved, used in the array or a pool, or by an unassigned device.

Any chance of making an xteve_vpn docker with zap2it support as well?

Just followed this guide and added device /dev/dri to plexpass container. After hitting apply the container restarts but now Plex is in a continuous loop with these messages. Starting Plex Media Server. s6-applyuidgid: fatal: unable to exec /usr/lib/plexmediaserver/Plex Media Server: No such file or directory Stopping Plex Media Server. Tried removing the device and reapplying but still the same loop Any ideas, would really hate to have to build this all over again after multiple years of use. Solved it. Not sure why though. I am on 6.9.0 beta 35 fyi... It was the chmod -R 777 /dev/dri in the /boot/config/go file that it didn't like. Must need the permissions to be set differently??? But after removing that and rebooting unraid it is now running ok.

Just followed this guide and added device /dev/dri to plexpass container. After hitting apply the container restarts but now Plex is in a continuous loop with these messages. Starting Plex Media Server. s6-applyuidgid: fatal: unable to exec /usr/lib/plexmediaserver/Plex Media Server: No such file or directory Stopping Plex Media Server. Tried removing the device and reapplying but still the same loop Any ideas, would really hate to have to build this all over again after multiple years of use.

Same issue after upgrading. Any idea when the plugin might be upgraded?

Thanks!

How exactly do I revert to that version in Unraid?

I am also having issues after the last few updates, can't say if it was since 6.4.1 but I was pretty sure it was working after that update. Looks like transmission-daemon isn't starting, and when I start the service manually inside the docker I can get to the web interface but get 404 not found messages, Couldn't find Transmission's web interface files. STARTING TRANSMISSIONCONFIGURING PORT FORWARDINGTransmission startup script complete.Wed Feb 7 17:41:53 2018 Initialization Sequence CompletedGot new port 36664 from PIAtransmission auth required[2018-02-07 17:41:53.978] transmission-remote: (http://localhost:9091/transmission/rpc/) Couldn't connect to server[2018-02-07 17:41:53.992] transmission-remote: (http://localhost:9091/transmission/rpc/) Couldn't connect to serverChecking port...[2018-02-07 17:42:04.013] transmission-remote: (http://localhost:9091/transmission/rpc/) Couldn't connect to server