Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

[Valiran]

16 hours ago, dlandon said:

Your remote server is apparantely not ready to respond to a ping when UD tries to mount the remote share:

Feb 28 10:14:38 ValiSRV1 unassigned.devices: Using Gateway '192.168.1.254' to Ping Remote Shares.
Feb 28 10:14:38 ValiSRV1 unassigned.devices: Mounting Remote Share 'VALISTATION:/volume1/Plex'...
Feb 28 10:14:38 ValiSRV1 unassigned.devices: Remote Server 'VALISTATION' is offline and share 'VALISTATION:/volume1/Plex' cannot be mounted.

 

UD waits for the gateway to be available, then waits 5 seconds before trying to mount remote shares.  I would think this would be enough time to wait for the network to be ready.

 

That's strange because my NAS is always on and accessible 0_o so the "offline" line shouldn't be.

[Valiran]

16 hours ago, dlandon said:

Your remote server is apparantely not ready to respond to a ping when UD tries to mount the remote share:

Feb 28 10:14:38 ValiSRV1 unassigned.devices: Using Gateway '192.168.1.254' to Ping Remote Shares.
Feb 28 10:14:38 ValiSRV1 unassigned.devices: Mounting Remote Share 'VALISTATION:/volume1/Plex'...
Feb 28 10:14:38 ValiSRV1 unassigned.devices: Remote Server 'VALISTATION' is offline and share 'VALISTATION:/volume1/Plex' cannot be mounted.

 

UD waits for the gateway to be available, then waits 5 seconds before trying to mount remote shares.  I would think this would be enough time to wait for the network to be ready.

 

That's strange because my NAS is always on and accessible 0_o so the "offline" line shouldn't be.

Is there a way to insert some delay after a reboot?

[sonofdbn]

 

I have had a similar problem to what @csendre reported a few posts above, as described in the thread above. I followed the suggestion in that thread of removing the SSD that I had as an Unassigned Device (removed virtually) and now everything looks fine except that of course I can't use the SSD.

 

It does look as if something is going wrong with my UD setup, but I haven't changed anything for a long time, except that a few days ago I couldn't access the SSD and had to set the Unassigned Devices SMB Security Settings to Yes (which fixed that issue). And I updated the UD plugin during this time. Currently on 2023.02.26 (and unRAID 6.11.5).

 

I've attached my syslog and diagnostics files. Please note that the syslog covers about 2 - 4 restarts while I tried to fix the problem, as well as unclean shutdowns.

 

Hoping for some advice on how to fix my UD situation.

syslog-192.168.1.14 (3).log tower-diagnostics-20230301-2348.zip

[dlandon]

7 hours ago, csendre said:

Any idea what could be happening?

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

[dlandon]

7 hours ago, Valiran said:

 

That's strange because my NAS is always on and accessible 0_o so the "offline" line shouldn't be.

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.

[dlandon]

4 hours ago, sonofdbn said:

 

I have had a similar problem to what @csendre reported a few posts above, as described in the thread above. I followed the suggestion in that thread of removing the SSD that I had as an Unassigned Device (removed virtually) and now everything looks fine except that of course I can't use the SSD.

 

It does look as if something is going wrong with my UD setup, but I haven't changed anything for a long time, except that a few days ago I couldn't access the SSD and had to set the Unassigned Devices SMB Security Settings to Yes (which fixed that issue). And I updated the UD plugin during this time. Currently on 2023.02.26 (and unRAID 6.11.5).

 

I've attached my syslog and diagnostics files. Please note that the syslog covers about 2 - 4 restarts while I tried to fix the problem, as well as unclean shutdowns.

 

Hoping for some advice on how to fix my UD situation.

syslog-192.168.1.14 (3).log 114.4 kB · 0 downloads tower-diagnostics-20230301-2348.zip 176.31 kB · 0 downloads

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.

[csendre]

1 hour ago, dlandon said:

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

No, this is not the case. I have 32GB of RAM and even when Plex is using it, total usage never goes above 50%. Also, I have been using this setup for almost 2 years and never had an issue until the SSD was added. There should be plenty of space for a lock file. Could this be a memory allocation issue with UD?

 

Another question; if the lock file is already created when Plex is starting to use additional RAM, can this be wiped out? I would presume that it would be write protected from other applications.

Edited March 1, 2023 by csendre

[Ford Prefect]

On 1/21/2016 at 4:55 PM, dlandon said:

Encrypted Dsks

 

• You can format a xfs or btrfs encrypted disk with UD that is compatible with the array.  The disk is created with the array password/passphrase.  You must have at least one encrypted disk in the array.  Unraid 6.8 and greater only.
• You can format an encrypted disk for use outside the array without having an encrypted array.  The disk password is entered when the disk is formatted.  You need to set the disk password in UD settings so the disk will mount.  Unraid 6.8 and greater only.
• A disk encrypted with a different password than the array can be mounted with a disk password set in the UD settings.  A different password can be set for each disk.

My old but quite massive unraid server died on me (Mobo + PSU dead). As it is very old and comprised of a lot of smaller 2TB and 3TB disks, my plan to make the content available ASAP is (and until time and money is avaiilable for a full rebuild) is to purchase a couple of 18TB disks, insert these into my other, second unraid server and then use the UD plugin to move the data over to the new disks.

 

Unfortately, as it seems per the feature statement above, the old server was/is encrypted (passphrase is available) but the existing, to be expanded server is not.

Is there a way to proceed without encrypting the array of the server #2 first?

...maybe by using the two new disks in a pool and encrypt these with the same passphrase and UD will accept that to mount the to-be migrated, old disks?

 

TIA in advance for your feedback.

regards,

ford

[dlandon]

54 minutes ago, csendre said:

No, this is not the case. I have 32GB of RAM and even when Plex is using it, total usage never goes above 50%. Also, I have been using this setup for almost 2 years and never had an issue until the SSD was added. There should be plenty of space for a lock file. Could this be a memory allocation issue with UD?

 

Another question; if the lock file is already created when Plex is starting to use additional RAM, can this be wiped out? I would presume that it would be write protected from other applications.

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

[dlandon]

47 minutes ago, Ford Prefect said:

Is there a way to proceed without encrypting the array of the server #2 first?

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.

[shpitz461]

Hi @dlandon,

this just started happening, any idea what could be wrong?

 

[dlandon]

6 minutes ago, shpitz461 said:

Hi @dlandon,

this just started happening, any idea what could be wrong?

 

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

[shpitz461]

ok, i'll give it a shot, thanks!

[trurl]

2 minutes ago, dlandon said:

Reboot.

Before rebooting

What do you get from command line with this?

df -h /

 

[shpitz461]

A reboot did solve the issue, still no idea what triggered it, I'll keep an eye on it.

Thanks!

[dlandon]

Something got confused and it just showed up on UD.

[csendre]

14 hours ago, dlandon said:

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

Not sure what you mean. I have Plex's /transcode/ folder mapped to /tmp/ in the docker template, pretty much that's it. Is there something else I could do to make sure everything is fine?

[Squid]

9 minutes ago, csendre said:

Not sure what you mean. I have Plex's /transcode/ folder mapped to /tmp/ in the docker template

You always want to map to a subdirectory in /tmp (eg: /tmp/plex)  mapping directly to /tmp means that Plex has the ability to delete anything else within /tmp which may cause a ton of problems.

[csendre]

2 hours ago, Squid said:

You always want to map to a subdirectory in /tmp (eg: /tmp/plex)  mapping directly to /tmp means that Plex has the ability to delete anything else within /tmp which may cause a ton of problems.

Thanks, I'll give this a try

[qw3r7yju4n]

Ive noticed an issue. One of my HDs is not mounted correctly. I cannot view the data but it does show it mounted. When i attempt to unmount it just doesnt. Any ideas?

[dlandon]

Just now, qw3r7yju4n said:

Ive noticed an issue. One of my HDs is not mounted correctly. I cannot view the data but it does show it mounted. When i attempt to unmount it just doesnt. Any ideas?

Post diagnostics.

[qw3r7yju4n]

Just now, dlandon said:

Post diagnostics.

Here ya go. Thanks for the quick service

mediaserver-diagnostics-20230302-1611.zip

[chuckthetekkie]

On 2/22/2023 at 11:09 PM, dlandon said:

That's why.  You shouldn't mount anything at /mnt/disks/ ot /mnt/remotes/.

Then where should I mount my ZFS volumes?  According to the Fix Common Problems thread "/mnt/disks" and "/mnt/remotes" are recommended locations. 

 

 

[dlandon]

14 hours ago, qw3r7yju4n said:

Ive noticed an issue. One of my HDs is not mounted correctly. I cannot view the data but it does show it mounted. When i attempt to unmount it just doesnt. Any ideas?

 

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.

 

[dlandon]

2 hours ago, chuckthetekkie said:

Then where should I mount my ZFS volumes?  According to the Fix Common Problems thread "/mnt/disks" and "/mnt/remotes" are recommended locations. 

 

 

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.