11.3 Beta - Device Busy

indivision

Guru
Joined
Jan 4, 2013
Messages
806
I just updated to 11.3 Beta.

For me, it looks like the jails kind of worked (they were 11.2 already). But, trying to work on them has been really problematic. It's constantly having issues with "device busy" and mount related errors so that it wont even list the jails in the GUI.

I went ahead and just deleted the old jails to try and start from scratch building them. But, it still throws a device busy error when trying to install a new plugin jail.

Anyone else seeing this?
 

indivision

Guru
Joined
Jan 4, 2013
Messages
806
Specific error I'm seeing now: cannot unmount '/mnt/mnt/optimus/iocage/releases/11.3-RELEASE/root': Device busy
 

ThreeDee

Guru
Joined
Jun 13, 2013
Messages
700
I didn't get any "device busy" errors .. but I couldn't install any new plug ins in 11.3 until I nuked the datasets containing my old jails. I changed what pool the iocage jails would be housed on as well
 

indivision

Guru
Joined
Jan 4, 2013
Messages
806
I didn't get any "device busy" errors .. but I couldn't install any new plug ins in 11.3 until I nuked the datasets containing my old jails. I changed what pool the iocage jails would be housed on as well

Thank you for this. It looks like I was able to get things working again by deleting the jails pools. I actually did try that before and the delete failed. But, something must have changed since then (have been trying various things) because it cleared this time.
 

appliance

Explorer
Joined
Nov 6, 2019
Messages
96
i get constant erros with replication..everything is locked for no reason.
TCG opal SSD drive doesn't show up exactly every second boot.
machine crashes at least once a day.

difficult to copy from UI Shell, as of the silly right click protection, it selects completely different part of the text.
/var/log/messages:

Dec 11 06:10:25 NAS kernel: <118>[152] Call timeout
..
Dec 11 06:10:25 NAS kernel: <118>[153] Setting hostid: 0x3919bc27.
Dec 11 06:10:25 NAS kernel: <118>[153] Starting file system checks:
Dec 11 06:10:25 NAS kernel: <118>[153] Mounting local filesystems:.
Dec 11 06:10:25 NAS kernel: <118>[163] Traceback (most recent call last):
Dec 11 06:10:25 NAS kernel: <118>[163] File "/usr/local/bin/midclt", line 10,in <module>
Dec 11 06:10:25 NAS kernel: <118>[163] sys.exit(main())
Dec 11 06:10:25 NAS kernel: <118>[163] File "/usr/local/lib/python3.7/site-packages/middlewared/client/client.py", line 602, in main
Dec 11 06:10:25 NAS kernel: <118>[163] with Client(uri=args.uri) as c:
Dec 11 06:10:25 NAS kernel: <118>[163] File "/usr/local/lib/python3.7/site-packages/middlewared/client/client.py", line 356, in __init__
Dec 11 06:10:25 NAS kernel: <118>[163] self._ws.connect()
Dec 11 06:10:25 NAS kernel: <118>[163] File "/usr/local/lib/python3.7/site-packages/middlewared/client/client.py", line 177, in connect
Dec 11 06:10:25 NAS kernel: <118>[163] rv = super(WSClient, self).connect()
Dec 11 06:10:25 NAS kernel: <118>[163] File "/usr/local/lib/python3.7/site-packages/ws4py/client/__init__.py", line 223, in connect
Dec 11 06:10:25 NAS kernel: <118>[163] bytes = self.sock.recv(128)
Dec 11 06:10:25 NAS kernel: <118>[163] socket.timeout
..
Dec 11 06:10:25 NAS kernel: <118>[177] Starting syslog_ng.
Dec 11 06:10:25 NAS kernel: <118>[177] [2019-12-11T06:10:25.157313] WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode. Please update it to use the syslog-ng 3.23 format at your time of convenience. To upgrade the configuration, please
 
Top