[11.3-4.1 --> 11.3-5 [EFAULT] Could not destroy memory device: mdconfig: ioctl(/dev/mdctl): Device

[ChuckWhitson]

I've upgraded a few test appliances and I've received the error in the title each time along with the following callback:

Code:

Error: Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/middlewared/job.py", line 349, in run
    await self.future
  File "/usr/local/lib/python3.7/site-packages/middlewared/job.py", line 385, in __run_body
    rv = await self.method(*([self] + args))
  File "/usr/local/lib/python3.7/site-packages/middlewared/schema.py", line 961, in nf
    return await f(*args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/middlewared/plugins/update.py", line 680, in file
    await self.middleware.call('update.destroy_upload_location')
  File "/usr/local/lib/python3.7/site-packages/middlewared/main.py", line 1141, in call
    app=app, pipes=pipes, job_on_progress_cb=job_on_progress_cb, io_thread=True,
  File "/usr/local/lib/python3.7/site-packages/middlewared/main.py", line 1098, in _call
    return await run_method(methodobj, *args)
  File "/usr/local/lib/python3.7/site-packages/middlewared/utils/run_in_thread.py", line 10, in run_in_thread
    return await self.loop.run_in_executor(self.run_in_thread_executor, functools.partial(method, *args, **kwargs))
  File "/usr/local/lib/python3.7/site-packages/middlewared/utils/io_thread_pool_executor.py", line 25, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/middlewared/plugins/update.py", line 754, in destroy_upload_location
    raise CallError(f'Could not destroy memory device: {cp.stderr}')
middlewared.service_exception.CallError: [EFAULT] Could not destroy memory device: mdconfig: ioctl(/dev/mdctl): Device busy

 

[MattTaylor2]

I've upgraded a few test appliances and I've received the error in the title each time along with the following callback:

Code:

Error: Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/middlewared/job.py", line 349, in run await self.future File "/usr/local/lib/python3.7/site-packages/middlewared/job.py", line 385, in __run_body rv = await self.method(*([self] + args)) File "/usr/local/lib/python3.7/site-packages/middlewared/schema.py", line 961, in nf return await f(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/middlewared/plugins/update.py", line 680, in file await self.middleware.call('update.destroy_upload_location') File "/usr/local/lib/python3.7/site-packages/middlewared/main.py", line 1141, in call app=app, pipes=pipes, job_on_progress_cb=job_on_progress_cb, io_thread=True, File "/usr/local/lib/python3.7/site-packages/middlewared/main.py", line 1098, in _call return await run_method(methodobj, *args) File "/usr/local/lib/python3.7/site-packages/middlewared/utils/run_in_thread.py", line 10, in run_in_thread return await self.loop.run_in_executor(self.run_in_thread_executor, functools.partial(method, *args, **kwargs)) File "/usr/local/lib/python3.7/site-packages/middlewared/utils/io_thread_pool_executor.py", line 25, in run result = self.fn(*self.args, **self.kwargs) File "/usr/local/lib/python3.7/site-packages/middlewared/plugins/update.py", line 754, in destroy_upload_location raise CallError(f'Could not destroy memory device: {cp.stderr}') middlewared.service_exception.CallError: [EFAULT] Could not destroy memory device: mdconfig: ioctl(/dev/mdctl): Device busy 

I'm getting the exact same, upgrading from 11.3-U4 to 11.3-U5, anyone got an ideas?

 

[joeschmuck]

I believe I saw a posting which said that the upgrade might need to be done via the ISO file upgrade path (boot and select upgrade) or even via a clean install (boot and select install) and restore the configuration file. Just make sure you start the process by having a backup of your configuration file.

If you have already tried this, then say so but the second option should work.

 

[MattTaylor2]

I believe I saw a posting which said that the upgrade might need to be done via the ISO file upgrade path (boot and select upgrade) or even via a clean install (boot and select install) and restore the configuration file. Just make sure you start the process by having a backup of your configuration file.

If you have already tried this, then say so but the second option should work.

I have not tried that, was hoping to avoid a clean install. I'll try with the ISO see if that works, Thanks!

 

[joeschmuck]

I have not tried that, was hoping to avoid a clean install. I'll try with the ISO see if that works, Thanks!

A clean install does not mean destroying your pool/data, it's just rebuilding the boot drive and by default the boot drive contains very little data and if you save your configuration file via the GUI (read the manual) and then restore it after you do a clean install, your system would be fully operational fairly quick. When you restore your config file the system generally will reboot twice to modify the data for the newer version of FreeNAS/TrueNAS, this is normal.

 

[MattTaylor2]

A clean install does not mean destroying your pool/data, it's just rebuilding the boot drive and by default the boot drive contains very little data and if you save your configuration file via the GUI (read the manual) and then restore it after you do a clean install, your system would be fully operational fairly quick. When you restore your config file the system generally will reboot twice to modify the data for the newer version of FreeNAS/TrueNAS, this is normal.

Upgrade worked by using the ISO, Thanks!

 

[AlexF]

I got same error and upgrade failure, from 11.3-U4.1, using Manual Updates. Clicking Power->Restart, and reboot shows FreeNAS-11.3-U5 . Can I assume upgrade was successful or am I in uncertain state?

root@freenas-NXX:~ # uname -a
FreeBSD freenas-NXX.lan 11.3-RELEASE-p14 FreeBSD 11.3-RELEASE-p14 #0 r325575+c936002dbe2(HEAD): Mon Sep 28 10:46:56 EDT 2020 root@tnbuilds05.tn.ixsystems.net:/freenas-releng/freenas/_BE/objs/freenas-releng/freenas/_BE/os/sys/FreeNAS.amd64 amd64

root@freenas-NXX:~ # cat /etc/version
FreeNAS-11.3-U5 (2e4ded5a0a)

 

[joeschmuck]

While I'd like to tell you that you are fully upgraded and have nothing to be concerned about, if you received an error during the upgrade I would highly recommend that you upgrade using the ISO to ensure all it good. That is what I'd do.