lzl20110
-
Posts
9 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by lzl20110
-
-
1 minute ago, dlandon said:
Post at the user scripts forum and see if that is the right point to apply the script. It may be too late in the sequence to do what you want.
Ok,thank you very much.
-
19 minutes ago, lzl20110 said:
I try
The priority of'At Stopping of Array' does not seem to be high, and UNRAID still crashes
-
26 minutes ago, dlandon said:
You don't uninstall UD. UD just unmounts all devices in the shutdown sequence.
Try setting up a user script that happens when the 'At Stopping of Array' event occurs with this command:
/usr/local/sbin/rc.unassigned umount //SERVER/share
This will unmount the remote share '//SERVER/share' and should occur before the VM is shut down.
The '//SERVER/share' is the SOURCE shown in UD.
I try
-
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
-
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
-
34 minutes ago, dlandon said:
我不确定我了解您在这里做什么。
你最近怎么样
如果您打开“自动挂载”开关,UD会挂载远程共享,还是VM不挂载?
UD安装?
Simply put, an SMB is automatically mounted after the virtual machine in UNRAID starts
-
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.
-
Is there a delay or timing added to the automount? I tried to use User Scripts, but the effect is not ideal.
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
in Plugin Support
Posted
Dec 4 20:17:33 Tower shutdown[8549]: shutting down for system reboot
Dec 4 20:17:33 Tower init: Switching to runlevel: 6
Dec 4 20:17:33 Tower init: Trying to re-exec init
Dec 4 20:17:34 Tower nginx: 2020/12/04 20:17:34 [alert] 5357#5357: *17132 open socket #22 left in connection 5
Dec 4 20:17:34 Tower nginx: 2020/12/04 20:17:34 [alert] 5357#5357: aborting
Dec 4 20:17:36 Tower kernel: mdcmd (37): nocheck cancel
Dec 4 20:17:37 Tower emhttpd: Spinning up all drives...
Dec 4 20:17:37 Tower kernel: mdcmd (38): spinup 1
Dec 4 20:17:38 Tower emhttpd: Stopping services...
Dec 4 20:17:38 Tower emhttpd: shcmd (270): /etc/rc.d/rc.libvirt stop
Dec 4 20:17:38 Tower root: Domain bef7c4dc-a168-460a-7902-cc1d6c9e8434 is being shutdown
Dec 4 20:17:38 Tower root:
Dec 4 20:19:09 Tower root: Waiting on VMs to shutdown..........................................................................................
Dec 4 20:19:09 Tower root: The following VMs are still running, forcing shutdown: DS3617
Dec 4 20:19:09 Tower kernel: sdc: sdc1 sdc2 sdc3
Dec 4 20:19:09 Tower kernel: sdd: sdd1 sdd2 sdd3
Dec 4 20:19:09 Tower unassigned.devices: Disk with serial 'WDC_WD80EZAZ-11TDBA0_2YGU43JD', mountpoint 'WDC_WD80EZAZ-11TDBA0_2YGU43JD' is not set to auto mount and will not be mounted.
Dec 4 20:19:09 Tower unassigned.devices: Issue spin down timer for device '/dev/sdc'.
Dec 4 20:19:09 Tower unassigned.devices: Disk with serial 'TOSHIBA_MD04ABA400V_2814KSICFMYB', mountpoint 'TOSHIBA_MD04ABA400V_2814KSICFMYB-part2' is not set to auto mount and will not be mounted.
Dec 4 20:19:09 Tower unassigned.devices: Disk with serial 'TOSHIBA_MD04ABA400V_2814KSICFMYB', mountpoint 'TOSHIBA_MD04ABA400V_2814KSICFMYB' is not set to auto mount and will not be mounted.
Dec 4 20:19:09 Tower unassigned.devices: Issue spin down timer for device '/dev/sdd'.
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Dec 4 20:19:09 Tower unassigned.devices: Disk with serial 'WDC_WD80EZAZ-11TDBA0_2YGU43JD', mountpoint 'WDC_WD80EZAZ-11TDBA0_2YGU43JD-part2' is not set to auto mount and will not be mounted.
Dec 4 20:19:09 Tower unassigned.devices: Disk with serial 'WDC_WD80EZAZ-11TDBA0_2YGU43JD', mountpoint 'DiskStation:2' is not set to auto mount and will not be mounted.
Dec 4 20:19:09 Tower unassigned.devices: Issue spin down timer for device '/dev/sdc'.
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Dec 4 20:19:09 Tower root: Domain bef7c4dc-a168-460a-7902-cc1d6c9e8434 destroyed
Dec 4 20:19:09 Tower root:
Dec 4 20:19:09 Tower unassigned.devices: Disk with serial 'TOSHIBA_MD04ABA400V_2814KSICFMYB', mountpoint 'DiskStation:3' is not set to auto mount and will not be mounted.
Dec 4 20:19:09 Tower unassigned.devices: Issue spin down timer for device '/dev/sdd'.
Dec 4 20:19:11 Tower root: Stopping libvirtd...
Dec 4 20:19:11 Tower dnsmasq[5380]: exiting on receipt of SIGTERM
Dec 4 20:19:11 Tower kernel: device virbr0-nic left promiscuous mode
Dec 4 20:19:11 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled state
Dec 4 20:19:11 Tower avahi-daemon[4087]: Interface virbr0.IPv4 no longer relevant for mDNS.
Dec 4 20:19:11 Tower avahi-daemon[4087]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
Dec 4 20:19:11 Tower avahi-daemon[4087]: Withdrawing address record for 192.168.122.1 on virbr0.
Dec 4 20:19:11 Tower root: Network 2214f59d-018d-4270-9f9c-550be516a722 destroyed
Dec 4 20:19:11 Tower root:
Dec 4 20:19:15 Tower root: Stopping virtlogd...
Dec 4 20:19:16 Tower root: Stopping virtlockd...
Dec 4 20:19:17 Tower emhttpd: shcmd (271): umount /etc/libvirt
Dec 4 20:19:17 Tower root: Stopping docker_load
Dec 4 20:19:17 Tower emhttpd: shcmd (274): /etc/rc.d/rc.docker stop
Dec 4 20:19:19 Tower kernel: vetha23e6f8: renamed from eth0
Dec 4 20:19:19 Tower kernel: docker0: port 2(vethef2c3d8) entered disabled state
Dec 4 20:19:19 Tower avahi-daemon[4087]: Interface vethef2c3d8.IPv6 no longer relevant for mDNS.
Dec 4 20:19:19 Tower avahi-daemon[4087]: Leaving mDNS multicast group on interface vethef2c3d8.IPv6 with address fe80::903d:1ff:fe0c:fa9.
Dec 4 20:19:19 Tower kernel: docker0: port 2(vethef2c3d8) entered disabled state
Dec 4 20:19:19 Tower kernel: device vethef2c3d8 left promiscuous mode
Dec 4 20:19:19 Tower kernel: docker0: port 2(vethef2c3d8) entered disabled state
Dec 4 20:19:19 Tower avahi-daemon[4087]: Withdrawing address record for fe80::903d:1ff:fe0c:fa9 on vethef2c3d8.
Dec 4 20:19:27 Tower kernel: device br0 left promiscuous mode
Dec 4 20:19:27 Tower kernel: veth6edc14e: renamed from eth0
Dec 4 20:19:29 Tower kernel: veth90823b5: renamed from eth0
Dec 4 20:19:29 Tower kernel: docker0: port 1(veth81d9b4c) entered disabled state
Dec 4 20:19:30 Tower avahi-daemon[4087]: Interface veth81d9b4c.IPv6 no longer relevant for mDNS.
Dec 4 20:19:30 Tower avahi-daemon[4087]: Leaving mDNS multicast group on interface veth81d9b4c.IPv6 with address fe80::d8c2:86ff:fedb:92cc.
Dec 4 20:19:30 Tower kernel: docker0: port 1(veth81d9b4c) entered disabled state
Dec 4 20:19:30 Tower kernel: device veth81d9b4c left promiscuous mode
Dec 4 20:19:30 Tower kernel: docker0: port 1(veth81d9b4c) entered disabled state
Dec 4 20:19:30 Tower avahi-daemon[4087]: Withdrawing address record for fe80::d8c2:86ff:fedb:92cc on veth81d9b4c.
Dec 4 20:19:32 Tower root: stopping dockerd ...
Dec 4 20:19:33 Tower root: waiting for docker to die ...
Dec 4 20:19:34 Tower avahi-daemon[4087]: Interface docker0.IPv6 no longer relevant for mDNS.
Dec 4 20:19:34 Tower avahi-daemon[4087]: Leaving mDNS multicast group on interface docker0.IPv6 with address fe80::42:f1ff:fe93:aac9.
Dec 4 20:19:34 Tower avahi-daemon[4087]: Interface docker0.IPv4 no longer relevant for mDNS.
Dec 4 20:19:34 Tower avahi-daemon[4087]: Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
Dec 4 20:19:34 Tower avahi-daemon[4087]: Withdrawing address record for fe80::42:f1ff:fe93:aac9 on docker0.
Dec 4 20:19:34 Tower avahi-daemon[4087]: Withdrawing address record for 172.17.0.1 on docker0.
Dec 4 20:19:34 Tower emhttpd: shcmd (275): umount /var/lib/docker
Dec 4 20:19:34 Tower Recycle Bin: Stopping Recycle Bin
Dec 4 20:19:34 Tower emhttpd: Stopping Recycle Bin...
Dec 4 20:19:34 Tower unassigned.devices: Unmounting All Devices...
Dec 4 20:19:35 Tower unassigned.devices: Remote SMB/NFS share '192.168.50.3:/volume2/videos' is not mounted and cannot be unmounted.
Dec 4 20:19:35 Tower unassigned.devices: Remote SMB/NFS share '192.168.50.3:/volume1/PT' is not mounted and cannot be unmounted.
Dec 4 20:19:35 Tower unassigned.devices: Remote SMB/NFS share '192.168.50.3:/volume1/downloads' is not mounted and cannot be unmounted.
Dec 4 20:19:35 Tower emhttpd: /usr/local/emhttp/plugins/user.scripts/backgroundScript.sh "/tmp/user.scripts/tmpScripts/关机/script" >/dev/null 2>&1
Dec 4 20:19:35 Tower emhttpd: shcmd (276): /etc/rc.d/rc.samba stop
Dec 4 20:19:35 Tower wsdd[13483]: udp_send: Failed to send udp packet with Network is unreachable
Dec 4 20:19:35 Tower wsdd[13483]: udp_send: Failed to send udp packet with No such device
Dec 4 20:19:35 Tower wsdd[13483]: udp_send: Failed to send udp packet with Network is unreachable
Dec 4 20:19:35 Tower wsdd[13483]: udp_send: Failed to send udp packet with No such device
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Dec 4 20:19:35 Tower wsdd[13483]: Failed to send bye with No such device
Dec 4 20:19:35 Tower unassigned.devices: Remote SMB/NFS share '192.168.50.3:/volume2/videos' is not mounted and cannot be unmounted.
Dec 4 20:19:35 Tower unassigned.devices: Remote SMB/NFS share '192.168.50.3:/volume1/PT' is not mounted and cannot be unmounted.
Dec 4 20:19:35 Tower unassigned.devices: Remote SMB/NFS share '192.168.50.3:/volume1/downloads' is not mounted and cannot be unmounted.
Dec 4 20:19:36 Tower emhttpd: shcmd (277): rm -f /etc/avahi/services/smb.service
Dec 4 20:19:36 Tower avahi-daemon[4087]: Files changed, reloading.
Dec 4 20:19:36 Tower avahi-daemon[4087]: Service group file /services/smb.service vanished, removing services.
Dec 4 20:19:36 Tower emhttpd: Stopping mover...
Dec 4 20:19:36 Tower emhttpd: shcmd (279): /usr/local/sbin/mover stop
Dec 4 20:19:36 Tower root: mover: not running
Dec 4 20:19:36 Tower emhttpd: Sync filesystems...
Dec 4 20:19:36 Tower emhttpd: shcmd (280): sync
Dec 4 20:19:36 Tower emhttpd: shcmd (281): umount /mnt/user0
Dec 4 20:19:36 Tower emhttpd: shcmd (282): rmdir /mnt/user0
Dec 4 20:19:36 Tower emhttpd: shcmd (283): umount /mnt/user
Dec 4 20:19:36 Tower emhttpd: shcmd (284): rmdir /mnt/user
Dec 4 20:19:37 Tower emhttpd: shcmd (286): /usr/local/sbin/update_cron
Dec 4 20:19:37 Tower emhttpd: Unmounting disks...
Dec 4 20:19:37 Tower emhttpd: shcmd (287): umount /mnt/disk1
Dec 4 20:19:37 Tower root: umount: /mnt/disk1: target is busy.
Dec 4 20:19:37 Tower emhttpd: shcmd (287): exit status: 32
Dec 4 20:19:37 Tower emhttpd: Retry unmounting disk share(s)...
Dec 4 20:19:42 Tower emhttpd: Unmounting disks...
Dec 4 20:19:42 Tower emhttpd: shcmd (288): umount /mnt/disk1
Dec 4 20:19:42 Tower root: umount: /mnt/disk1: target is busy.
Dec 4 20:19:42 Tower emhttpd: shcmd (288): exit status: 32
Dec 4 20:19:42 Tower emhttpd: Retry unmounting disk share(s)...
Dec 4 20:19:47 Tower emhttpd: Unmounting disks...
Dec 4 20:19:47 Tower emhttpd: shcmd (289): umount /mnt/disk1
Dec 4 20:19:47 Tower root: umount: /mnt/disk1: target is busy.
Dec 4 20:19:47 Tower emhttpd: shcmd (289): exit status: 32
Dec 4 20:19:47 Tower emhttpd: Retry unmounting disk share(s)...
Dec 4 20:19:52 Tower emhttpd: Unmounting disks...
Dec 4 20:19:52 Tower emhttpd: shcmd (290): umount /mnt/disk1
Dec 4 20:19:52 Tower root: umount: /mnt/disk1: target is busy.
Dec 4 20:19:52 Tower emhttpd: shcmd (290): exit status: 32
Dec 4 20:19:52 Tower emhttpd: Retry unmounting disk share(s)...
Dec 4 20:19:57 Tower emhttpd: Unmounting disks...
Dec 4 20:19:57 Tower emhttpd: shcmd (291): umount /mnt/disk1
Dec 4 20:19:57 Tower root: umount: /mnt/disk1: target is busy.
Dec 4 20:19:57 Tower emhttpd: shcmd (291): exit status: 32
Dec 4 20:19:57 Tower emhttpd: Retry unmounting disk share(s)...
Dec 4 20:20:02 Tower emhttpd: Unmounting disks...
Dec 4 20:20:02 Tower emhttpd: shcmd (292): umount /mnt/disk1
Dec 4 20:20:02 Tower root: umount: /mnt/disk1: target is busy.
Dec 4 20:20:02 Tower emhttpd: shcmd (292): exit status: 32
Dec 4 20:20:02 Tower emhttpd: Retry unmounting disk share(s)...
Dec 4 20:20:06 Tower root: Status of all loop devices
Dec 4 20:20:06 Tower root: /dev/loop1: [2049]:4 (/boot/bzfirmware)
Dec 4 20:20:06 Tower root: /dev/loop2: [2305]:268435585 (/mnt/disk1/system/docker/docker.img)
Dec 4 20:20:06 Tower root: /dev/loop0: [2049]:3 (/boot/bzmodules)
Dec 4 20:20:06 Tower root: Active pids left on /mnt/*
Dec 4 20:20:06 Tower root: USER PID ACCESS COMMAND
Dec 4 20:20:06 Tower root: /mnt/disk1: root kernel mount /mnt/disk1
Dec 4 20:20:06 Tower root: /mnt/disks: root kernel mount /mnt/disks
Dec 4 20:20:06 Tower root: Active pids left on /dev/md*
Dec 4 20:20:06 Tower root: USER PID ACCESS COMMAND
Dec 4 20:20:06 Tower root: /dev/md1: root kernel mount /mnt/disk1
Dec 4 20:20:06 Tower root: Generating diagnostics...
Dec 4 20:20:07 Tower emhttpd: Unmounting disks...
Dec 4 20:20:07 Tower emhttpd: shcmd (293): umount /mnt/disk1
Dec 4 20:20:07 Tower root: umount: /mnt/disk1: target is busy.
Dec 4 20:20:07 Tower emhttpd: shcmd (293): exit status: 32
Dec 4 20:20:07 Tower emhttpd: Retry unmounting disk share(s)...
I'm very sorry, I don't understand these, I can only send it to you