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


dlandon

5735 posts in this topic Last Reply

Recommended Posts

1 hour ago, dlandon said:

I don't think the disk is going off line.  I don't see anything in the log that indicates it went offline.  It looks like UD is throwing php errors when getting the unassigned disks.  I've fixed the php errors.  This will be in the next release.  You won't see them, but if the process of getting the unassigned disks fails, none of your disks will show.

 

I suspect a problem with disk information when a disk is hot plugged.  Does this issue show up at random, or is there an event like a disk being hot plugged and then the problem shows?

 

Start with your server freshly booted and wait for the issue to happen.  When it does, post here and I'll walk you through some trouble shooting steps.

Not sure what you mean by hot plug. But the issues seems to be random. Only thing on the nvme drive are VM domains which most of the time are off and unused. 

Thank you just rebooted server I will keep you poster.

Link to post
  • Replies 5.7k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

New release of UD.  Changes: When changing the mount point (which is also the share name), the mount point is checked for a duplicate of a user share or another UD device.  Samba cannot handle

While I appreciate your interest in esthetics, there is more to consider than just 'aligning' disk drive mounts: This disk is mounted without a UD script, it is probably better to put it in th

<step on soap box> Keep in mind that the Unraid array disk configuration is static and doesn't change until it is stopped.  UD has to deal with hot plugged disks, devices being dynamically

Posted Images

9 minutes ago, jluna said:

Not sure what you mean by hot plug. But the issues seems to be random. Only thing on the nvme drive are VM domains which most of the time are off and unused. 

Thank you just rebooted server I will keep you poster.

Plugging in a USB disk, flash drive, etc is hot plugging.

Link to post
4 minutes ago, dlandon said:

Plugging in a USB disk, flash drive, etc is hot plugging.

Oh yes however drive I'm using is not a USB disk. 

 

After server reboot unassigned drive seems to be mounted but still seeing the same error messages. VMs fail to start saying directory does not exist. 

unassinged.thumb.png.a97d4c423bc6d50c915e016dab2703a3.png 

Link to post
1 hour ago, jluna said:

Oh yes however drive I'm using is not a USB disk. 

 

After server reboot unassigned drive seems to be mounted but still seeing the same error messages. VMs fail to start saying directory does not exist. 

unassinged.thumb.png.a97d4c423bc6d50c915e016dab2703a3.png 

Your disk is mounted fine.  The issue is with remotes shares and maybe iso mounts.  This will occur if the configuration files are corrupted.

 

Delete the following files and then reboot:

/flash/config/plugins/unassigned.devices/samba_mount.cfg

/flash/config/plugins/unassigned.devices/iso_mount.cfg

 

If the problem persists, you need to remove your UNRAID flash drive and check it on a computer and fix any file problems.

 

Once that is cleared up, we can take a look at why your app can't see the mounted nvme disk.

Link to post

Here's a strange problem:

 

I have an always-attached (mechanical) USB hard drive mounted through UD.

I have SSD Trim set to run 7AM daily through the built-in scheduler.

It seems? unRAID recognizes this USB disk as an SSD and tries to trim it.

I don't know if that's because UD's reporting it as an SSD or SSD detection happens outside UD.

 

(I don't see the error every time trim runs but syslog server's been buggy lately so maybe it's just not logged.)

Sep 30 07:00:03 NAS kernel: blk_update_request: critical target error, dev sdb, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Oct  1 07:00:02 NAS kernel: blk_update_request: critical target error, dev sda, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Oct  2 07:00:02 NAS kernel: blk_update_request: critical target error, dev sda, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Oct  7 07:00:09 NAS kernel: blk_update_request: critical target error, dev sda, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Oct  9 07:00:02 NAS kernel: blk_update_request: critical target error, dev sdb, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Oct 11 07:00:02 NAS kernel: blk_update_request: critical target error, dev sdb, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Oct 13 07:00:08 NAS kernel: blk_update_request: critical target error, dev sdb, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Oct 22 07:00:08 NAS kernel: blk_update_request: critical target error, dev sdb, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Oct 24 07:00:08 NAS kernel: blk_update_request: critical target error, dev sdb, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Oct 26 07:00:01 NAS kernel: blk_update_request: critical target error, dev sdb, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Oct 27 07:00:09 NAS kernel: blk_update_request: critical target error, dev sdb, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Oct 30 07:00:08 NAS kernel: blk_update_request: critical target error, dev sda, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Nov  6 07:00:08 NAS kernel: blk_update_request: critical target error, dev sdb, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Nov 10 07:00:08 NAS kernel: blk_update_request: critical target error, dev sdb, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Nov 11 07:00:02 NAS kernel: blk_update_request: critical target error, dev sda, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Nov 13 07:00:09 NAS kernel: blk_update_request: critical target error, dev sdb, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Nov 14 07:00:09 NAS kernel: blk_update_request: critical target error, dev sda, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Nov 15 07:00:09 NAS kernel: blk_update_request: critical target error, dev sdb, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Nov 16 07:00:08 NAS kernel: blk_update_request: critical target error, dev sdb, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Nov 17 07:00:02 NAS kernel: blk_update_request: critical target error, dev sdb, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Nov 20 07:00:09 NAS kernel: blk_update_request: critical target error, dev sdb, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Nov 22 07:00:08 NAS kernel: blk_update_request: critical target error, dev sda, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Nov 24 07:00:08 NAS kernel: blk_update_request: critical target error, dev sdb, sector 76096 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Nov 26 07:00:03 NAS kernel: blk_update_request: critical target error, dev sda, sector 76048 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
Dec  2 07:00:08 NAS kernel: blk_update_request: critical target error, dev sdb, sector 76048 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0

 

nas-diagnostics-20201203-0844.zip

Link to post

Hi, 
I used UD a while now - everything is working fine :)
I now bought some new disks and precleared them. After preclear I tried to format one to ntfs but after the success message the disk ist still without filesystem nevertheless if I try ntfs or xfs...
Does anyone has a cloue?

 

image.thumb.png.8bc9efb35f009e5caecebd5ca7db19ab.png
The disk was freshly precleared and zeroed - I just clicked on the red X from preclear-disk plugin...

Here is the last log from the formatting
image.png.7af8df93886268ee2da4cbcd168b74c6.png

Link to post
1 hour ago, sauerm said:

Hi, 
I used UD a while now - everything is working fine :)
I now bought some new disks and precleared them. After preclear I tried to format one to ntfs but after the success message the disk ist still without filesystem nevertheless if I try ntfs or xfs...
Does anyone has a cloue?

 

image.thumb.png.8bc9efb35f009e5caecebd5ca7db19ab.png
The disk was freshly precleared and zeroed - I just clicked on the red X from preclear-disk plugin...

Here is the last log from the formatting
image.png.7af8df93886268ee2da4cbcd168b74c6.png

Can you post diagnostics?  It looks like UD cannot get the disk information.  All the '-' indicate that something is missing and UD just filled in a '-'.

Link to post
On 12/1/2020 at 3:52 AM, dlandon said:

The automount of disks is done on the server event "disks_mounted" so UD disks are mounted when VMs and Docker containers are started.

 

The automount of remote shares is done on the server event "started" so the network is available and the mounts will be successful.

 

When you say a user script is not ideal, what does that mean?

I mount the SMB shared in the virtual machine. Every time I start UNRAID, it will not be automatically mounted. The automatic mounting needs to be after the virtual machine is started.

Link to post
On 12/2/2020 at 1:56 PM, dlandon said:

Your disk is mounted fine.  The issue is with remotes shares and maybe iso mounts.  This will occur if the configuration files are corrupted.

 

Delete the following files and then reboot:

/flash/config/plugins/unassigned.devices/samba_mount.cfg

/flash/config/plugins/unassigned.devices/iso_mount.cfg

 

If the problem persists, you need to remove your UNRAID flash drive and check it on a computer and fix any file problems.

 

Once that is cleared up, we can take a look at why your app can't see the mounted nvme disk.

I deleted the two files you suggested but still getting the same error. 

I'm sorry for the rookie question but what do you mean by fix any file problems on a computer? 

Link to post

I'm not sure I understand what you are doing here.

4 hours ago, lzl20110 said:

I mount the SMB shared in the virtual machine.

How are you doing that?

4 hours ago, lzl20110 said:

Every time I start UNRAID, it will not be automatically mounted.

UD will mount a remote share if you turn on the 'Auto Mount' switch, or is the VM not mounting it?

4 hours ago, lzl20110 said:

The automatic mounting needs to be after the virtual machine is started.

THE UD mounting?

Link to post
4 hours ago, jluna said:

I deleted the two files you suggested but still getting the same error. 

I'm sorry for the rookie question but what do you mean by fix any file problems on a computer? 

I am releasing a new version of UD today that should stop those php errors.

 

What I meant was take the USB flash drive to a Windows computer and check the file system using Windows.

Link to post
1 hour ago, sauerm said:

Sure, thanks.
I also attached the full disk log as I found two errors regarding UD in lines 164 and 194. I marked them with '-->'.

storage-diagnostics-20201204-0823.zip 174.46 kB · 0 downloads UD_disk_log.txt 41.2 kB · 0 downloads

You are having some disk errors:

Nov 14 16:18:28 STORAGE kernel: ata4.00: exception Emask 0x10 SAct 0xfe00 SErr 0x190002 action 0xe frozen
Nov 14 16:18:28 STORAGE kernel: ata4.00: irq_stat 0x80400000, PHY RDY changed
Nov 14 16:18:28 STORAGE kernel: ata4: SError: { RecovComm PHYRdyChg 10B8B Dispar }
Nov 14 16:18:28 STORAGE kernel: ata4.00: failed command: READ FPDMA QUEUED
Nov 14 16:18:28 STORAGE kernel: ata4.00: cmd 60/40:48:38:b6:2a/05:00:d5:00:00/40 tag 9 ncq dma 688128 in
Nov 14 16:18:28 STORAGE kernel: ata4.00: status: { DRDY }
Nov 14 16:18:28 STORAGE kernel: ata4.00: failed command: READ FPDMA QUEUED
Nov 14 16:18:28 STORAGE kernel: ata4.00: cmd 60/40:50:78:bb:2a/05:00:d5:00:00/40 tag 10 ncq dma 688128 in
Nov 14 16:18:28 STORAGE kernel: ata4.00: status: { DRDY }
Nov 14 16:18:28 STORAGE kernel: ata4.00: failed command: READ FPDMA QUEUED
Nov 14 16:18:28 STORAGE kernel: ata4.00: cmd 60/40:58:b8:c0:2a/05:00:d5:00:00/40 tag 11 ncq dma 688128 in
Nov 14 16:18:28 STORAGE kernel: ata4.00: status: { DRDY }
Nov 14 16:18:28 STORAGE kernel: ata4.00: failed command: READ FPDMA QUEUED
Nov 14 16:18:28 STORAGE kernel: ata4.00: cmd 60/d0:60:f8:c5:2a/00:00:d5:00:00/40 tag 12 ncq dma 106496 in
Nov 14 16:18:28 STORAGE kernel: ata4.00: status: { DRDY }
Nov 14 16:18:28 STORAGE kernel: ata4.00: failed command: READ FPDMA QUEUED
Nov 14 16:18:28 STORAGE kernel: ata4.00: cmd 60/f0:68:c8:c6:2a/04:00:d5:00:00/40 tag 13 ncq dma 647168 in
Nov 14 16:18:28 STORAGE kernel: ata4.00: status: { DRDY }
Nov 14 16:18:28 STORAGE kernel: ata4.00: failed command: READ FPDMA QUEUED
Nov 14 16:18:28 STORAGE kernel: ata4.00: cmd 60/40:70:b8:cb:2a/05:00:d5:00:00/40 tag 14 ncq dma 688128 in
Nov 14 16:18:28 STORAGE kernel: ata4.00: status: { DRDY }
Nov 14 16:18:28 STORAGE kernel: ata4.00: failed command: READ FPDMA QUEUED
Nov 14 16:18:28 STORAGE kernel: ata4.00: cmd 60/40:78:f8:d0:2a/05:00:d5:00:00/40 tag 15 ncq dma 688128 in
Nov 14 16:18:28 STORAGE kernel: ata4.00: status: { DRDY }
Nov 14 16:18:28 STORAGE kernel: ata4: hard resetting link
Nov 14 16:18:29 STORAGE kernel: ata4: SATA link down (SStatus 0 SControl 300)
Nov 14 16:18:34 STORAGE kernel: ata4: hard resetting link
Nov 14 16:18:35 STORAGE kernel: ata4: SATA link down (SStatus 0 SControl 300)
Nov 14 16:18:37 STORAGE kernel: ata4: hard resetting link
Nov 14 16:18:47 STORAGE kernel: ata4: softreset failed (device not ready)
Nov 14 16:18:47 STORAGE kernel: ata4: hard resetting link
Nov 14 16:18:51 STORAGE kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Nov 14 16:18:51 STORAGE kernel: ata4.00: configured for UDMA/133
Nov 14 16:18:51 STORAGE kernel: ata4: EH complete

 

I'm not exactly sure what you have done, but it looks like preclear is running on that disk at the same time you are trying to format it:

Nov 15 18:20:51 STORAGE unassigned.devices: Error: shell_exec(/sbin/blockdev --getsz /dev/sdi | /bin/awk '{ print }' 2>/dev/null) took longer than 2s!
Nov 15 18:25:17 STORAGE preclear.disk: Pausing preclear of disk 'sdi'
Nov 15 18:25:21 STORAGE preclear.disk: Resuming preclear of disk 'sdi'
Nov 15 18:25:58 STORAGE preclear.disk: Pausing preclear of disk 'sdi'
Nov 15 18:26:04 STORAGE preclear.disk: Resuming preclear of disk 'sdi'
Nov 15 18:30:20 STORAGE preclear.disk: Pausing preclear of disk 'sdi'
Nov 15 18:30:23 STORAGE preclear.disk: Resuming preclear of disk 'sdi'
Nov 15 18:31:48 STORAGE preclear.disk: Pausing preclear of disk 'sdi'
Nov 15 18:31:48 STORAGE preclear.disk: Resuming preclear of disk 'sdi'
Nov 15 18:43:48 STORAGE preclear.disk: Pausing preclear of disk 'sdi'
Nov 15 18:43:50 STORAGE preclear.disk: Resuming preclear of disk 'sdi'
Nov 15 18:45:30 STORAGE preclear.disk: Pausing preclear of disk 'sdi'
Nov 15 18:45:37 STORAGE preclear.disk: Resuming preclear of disk 'sdi'
Nov 15 18:49:41 STORAGE preclear.disk: Pausing preclear of disk 'sdi'
Nov 15 18:49:44 STORAGE preclear.disk: Resuming preclear of disk 'sdi'
Nov 15 18:50:01 STORAGE preclear.disk: Pausing preclear of disk 'sdi'
Nov 15 18:50:06 STORAGE preclear.disk: Resuming preclear of disk 'sdi'
Nov 15 18:50:47 STORAGE preclear.disk: Pausing preclear of disk 'sdi'
Nov 15 18:50:50 STORAGE preclear.disk: Resuming preclear of disk 'sdi'
Nov 15 18:51:10 STORAGE preclear.disk: Pausing preclear of disk 'sdi'
Nov 15 18:51:19 STORAGE preclear.disk: Resuming preclear of disk 'sdi'

If you are preclearing any disks let them finish.  Then remove the preclear plugin.  Reboot and then see if you can format the disk.

 

Watch the log for the disk errors and solve that.

Link to post
34 minutes ago, dlandon said:

我不确定我了解您在这里做什么。

你最近怎么样

如果您打开“自动挂载”开关,UD会挂载远程共享,还是VM不挂载?

UD安装?

Simply put, an SMB is automatically mounted after the virtual machine in UNRAID starts

Link to post
1 hour ago, dlandon said:

You are having some disk errors:

 

I'm not exactly sure what you have done, but it looks like preclear is running on that disk at the same time you are trying to format it:

 

If you are preclearing any disks let them finish.  Then remove the preclear plugin.  Reboot and then see if you can format the disk.

 

Watch the log for the disk errors and solve that.

Thanks again, didnt recognized that. SMART values looked good.
Yes, I had a second pre-clear running on another disk (same type). It finished just now.

image.thumb.png.339e0c2526f258bc15a1f32466460cba.png
I will make a intense system diagnostic now. Thanks for your thoughts 👍


EDIT:
A Server-Restart and/or deletion of the pre-clear plugin solved the problem.

image.thumb.png.3e2959c0a51cd6e50dc85b362b922b65.png
The disks are formatted as intended.

 

image.png


EDIT2:
I Still get these ATA6 Errors. Thought it would be a Cable issue. 
Could it be a controller issue or is the disk faulty?

Dec 4 12:56:25 STORAGE kernel: ata6: SATA max UDMA/133 abar m2048@0xa1340000 port 0xa1340280 irq 128
Dec 4 12:56:25 STORAGE kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 4 12:56:25 STORAGE kernel: ata6.15: Port Multiplier 1.2, 0x1b21:0x1092 r0, 3 ports, feat 0x5/0xf
Dec 4 12:56:25 STORAGE kernel: ata6.00: hard resetting link
Dec 4 12:56:25 STORAGE kernel: ata6.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
Dec 4 12:56:25 STORAGE kernel: ata6.01: hard resetting link
Dec 4 12:56:25 STORAGE kernel: ata6.01: SATA link up 3.0 Gbps (SStatus 123 SControl 330)
Dec 4 12:56:25 STORAGE kernel: ata6.02: hard resetting link
Dec 4 12:56:25 STORAGE kernel: ata6.02: SATA link up 3.0 Gbps (SStatus 123 SControl 330)
Dec 4 12:56:25 STORAGE kernel: ata6.00: supports DRM functions and may not be fully accessible
Dec 4 12:56:25 STORAGE kernel: ata6.00: ATA-9: WDC WD120EDAZ-11F3RA0, 5PJJBWAF, 81.00A81, max UDMA/133
Dec 4 12:56:25 STORAGE kernel: ata6.00: 23437770752 sectors, multi 0: LBA48 NCQ (depth 32), AA
Dec 4 12:56:25 STORAGE kernel: ata6.00: supports DRM functions and may not be fully accessible
Dec 4 12:56:25 STORAGE kernel: ata6.00: configured for UDMA/133
Dec 4 12:56:25 STORAGE kernel: ata6.01: ATA-8: WDC WD20EADS-00R6B0, WD-WCAVY0819486, 01.00A01, max UDMA/133
Dec 4 12:56:25 STORAGE kernel: ata6.01: 3907029168 sectors, multi 0: LBA48 NCQ (depth 32), AA
Dec 4 12:56:25 STORAGE kernel: ata6.01: configured for UDMA/133
Dec 4 12:56:25 STORAGE kernel: ata6.02: ATA-8: WDC WD20EARS-00J2GB0, WD-WCAYY0234353, 80.00A80, max UDMA/133
Dec 4 12:56:25 STORAGE kernel: ata6.02: 3907029168 sectors, multi 0: LBA48 NCQ (depth 32), AA
Dec 4 12:56:25 STORAGE kernel: ata6.02: configured for UDMA/133
Dec 4 12:56:25 STORAGE kernel: ata6: EH complete
Dec 4 12:56:25 STORAGE kernel: sd 6:0:0:0: [sdg] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB)
Dec 4 12:56:25 STORAGE kernel: sd 6:0:0:0: [sdg] 4096-byte physical blocks
Dec 4 12:56:25 STORAGE kernel: sd 6:0:0:0: [sdg] Write Protect is off
Dec 4 12:56:25 STORAGE kernel: sd 6:0:0:0: [sdg] Mode Sense: 00 3a 00 00
Dec 4 12:56:25 STORAGE kernel: sd 6:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 4 12:56:25 STORAGE kernel: sdg: sdg1
Dec 4 12:56:25 STORAGE kernel: sd 6:0:0:0: [sdg] Attached SCSI removable disk
Dec 4 12:56:58 STORAGE emhttpd: WDC_WD120EDAZ-11F3RA0_5PJJBWAF (sdg) 512 23437770752
Dec 4 12:57:13 STORAGE unassigned.devices: Issue spin down timer for device '/dev/sdg'.

 

Edited by sauerm
Link to post
20 minutes ago, steve1977 said:

Is it possible to mount network disks (connected to my wifi router)?

Yes, if the router shares them with SMB.  UD can mount them as remote shares.

21 minutes ago, steve1977 said:

And then could I even include these into an array (without parity drive as this would obviously fail due to network speed).

No.  You can only add physical disks to the array.

Link to post
34 minutes ago, dlandon said:

谁会自动挂载SMB和VM?怎么样?

When UNRAID is turned on, UD's automatic mounting SMB should be after the virtual machine is started, and when UNRAID is shut down, UD should be uninstalled in advance, otherwise UNRAID will be stuck

Link to post

Small observations I noticed for a couple weeks now. Every morning at 6am I do a automated BTRFS snapshot for my VMs on the cache drive to an UD drive. This works for over a year without any issues so far. What I have noticed starting on 23.11.2020 is that the allocation of the UD drive isn't shown correctly when I visit the main page after the snapshot anymore. The snapshots are created as usual (70-80G per day) but the allocation isn't showing the new values. I see the same values as the day before. Refreshing the main page isn't triggering a rescan of the drive. I am on 6.8.3 and installing plugin updates as they come in, nothing else has changed. Almost every day I check for updates.

 

If I do a "BTRFS sub list /mnt/disks/backupdrive" for the UD drive the values are shown correct again. If I don't do this, the old values are still shown. I never had to do this before. For me this is a small problem, because I have to clean old snapshots once every 1-2 months by hand on the 1,5TB drive to not fully filling it up. @dlandon I know it's not really a big think, but maybe someone can explain me whats the reason for this new behaviour.

Link to post
4 minutes ago, lzl20110 said:

When UNRAID is turned on, UD's automatic mounting SMB should be after the virtual machine is started, and when UNRAID is shut down, UD should be uninstalled in advance, otherwise UNRAID will be stuck

UD has no way of knowing when a particular VM is started and that it needs to wait for that VM.  The shutdown process is controlled by Unraid and UD devices are unmounted as one of the last things.  VMs and Dockers are shutdown first.  This is done because when a user has a VM or their Dockers on a UD disk, it can't be unmounted until VMs and Dockers are shutdown.

 

You'll have to find another way of doing this.

Link to post
2 minutes ago, dlandon said:

UD无法知道何时启动特定VM,以及它是否需要等待该VM。关闭过程由Unraid控制,并且卸载UD设备是最后的事情之一。VM和Docker首先关闭。这样做是因为,当用户在UD磁盘上拥有VM或Docker时,只有在VM和Docker关闭后才能将其卸载。

 

您将必须找到另一种方法。

User Scripts can be used to delay UD mounting, but I have not found a way to uninstall UD before UNRAID shutdown

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.