Dragonfish upgrade to Electric Eel - Apps Fail to migrate and unable to install apps in Electric Eel

Apps and Virtualization
1

I am trying to move from Dragonfish 24.04.2.5 to Electric Eel 24.10.0.2. Apps I have running in Dragonfish are:-
Plex
Prowlar
Radarr
Sonarr
SABnzbd

They are all up to date and stable.

Plex migrates fine but I get the following errors for the other apps.

[{"name": "prowlarr", "error": "Failed to clone and promote ix-volumes: [EFAULT] Failed to clone snapshot: cannot create 'Pool1/ix-apps/app_mounts/prowlarr/config': dataset already exists", "successfully_migrated": false}, {"name": "sabnzbd", "error": "Failed to clone and promote ix-volumes: [EFAULT] Failed to clone snapshot: cannot create 'Pool1/ix-apps/app_mounts/sabnzbd/config': dataset already exists", "successfully_migrated": false}, {"name": "radarr", "error": "Failed to clone and promote ix-volumes: [EFAULT] Failed to clone snapshot: cannot create 'Pool1/ix-apps/app_mounts/radarr/config': dataset already exists", "successfully_migrated": false}, {"name": "sonarr", "error": "Failed to clone and promote ix-volumes: [EFAULT] Failed to clone snapshot: cannot create 'Pool1/ix-apps/app_mounts/sonarr/config': dataset already exists", "successfully_migrated": false}]
root@milton-nas[~]#

If I run ā€œmidclt call -job k8s_to_docker.migrateā€ I get the same error as above.

If I try a clean install of an app I get the following error

ā€œ[EFAULT] Failed ā€˜upā€™ action for ā€˜radarrā€™ app, please check /var/log/app_lifecycle.log for more detailsā€

Error: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/middlewared/job.py", line 488, in run await self.future File "/usr/lib/python3/dist-packages/middlewared/job.py", line 535, in __run_body rv = await self.middleware.run_in_thread(self.method, *args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1364, in run_in_thread return await self.run_in_executor(io_thread_pool_executor, method, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1361, in run_in_executor return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/concurrent/futures/thread.py", line 58, in run result = self.fn(*self.args, **self.kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/service/crud_service.py", line 268, in nf rv = func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/schema/processor.py", line 55, in nf res = f(*args, **kwargs) ^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/schema/processor.py", line 183, in nf return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/plugins/apps/crud.py", line 203, in do_create return self.create_internal(job, app_name, version, data['values'], complete_app_details) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/plugins/apps/crud.py", line 248, in create_internal raise e from None File "/usr/lib/python3/dist-packages/middlewared/plugins/apps/crud.py", line 241, in create_internal compose_action(app_name, version, 'up', force_recreate=True, remove_orphans=True) File "/usr/lib/python3/dist-packages/middlewared/plugins/apps/compose_utils.py", line 57, in compose_action raise CallError( middlewared.service_exception.CallError: [EFAULT] Failed 'up' action for 'radarr' app, please check /var/log/app_lifecycle.log for more details

/var/log/app_lifecycle.log shows the following:-

(ERROR) app_lifecycle.compose_action():56 - Failed 'up' action for 'radarr' app:  permissions Pulling
 radarr Pulling
 radarr Error Head "https://ghcr.io/v2/onedr0p/radarr/manifests/5.15.1.9463": Get "https://ghcr.io/token?scope=repository%3Aonedr0p%2Fradarr%3Apull&service=ghcr.io": dial tcp: lookup ghcr.io on 192.168.2.254:53: no such host
 permissions Error context canceled
Error response from daemon: Head "https://ghcr.io/v2/onedr0p/radarr/manifests/5.15.1.9463": Get "https://ghcr.io/token?scope=repository%3Aonedr0p%2Fradarr%3Apull&service=ghcr.io": dial tcp: lookup ghcr.io on 192.168.2.254:53: no such host```

Can anyone help with this or should I report it as a bug?
2

I would report it as a Bug with the dump they ask for. You can use the Feedback / Report A Bug at the top right of your TrueNAS GUI. Looks like a :grinning:?

3

Thanks, I have done that.

4

I havenā€™t read through your error output in detail, but just as a quick question - do you have an NVIDIA card, and if so, did you make sure the NVIDIA drivers are installed?

5

No Nvidia Card but it does have a SATA expansion card to allow more HDD to be installed.

6

Whilst a SATA expansion card as opposed to an HBA is NOT reccomended - I think its unlikley to be the issue here.

You should post your hardware though

7

Had you previously upgraded this system to any Electric Eel release or development versions and then gone back to Dragonfish?

8

No I had not. I installed 24.10.0.1 but the apps did not migrate so I reverted to Dragonfish.

9

That was probably enough to create the volumes as it tried to migrate though, which would produce the dataset already exists errors when it tried to create them again.

10

So why did I get this error the first time I updated to Electric Eel?

And how do I fix this?

11

If it happened upon upgrade, you should have put in a Bug Ticket. You can still do so in TrueNAS. I would guess they would want you on EE and submitting the dump that way. You should have a smile icon on upper right of GUI home dashboard page. Submit Feedback / Report a Bug.

12

Specs added to Signature. :slight_smile:

1 Like
13

I put a bug report in yesterday and included the debug dump.

14

My guess would be that the migration errored out for a different reason the first time, since the ix-apps dataset doesnā€™t exist in Dragonfish, but without seeing what the error message said then I can only guess.

I would suggest at this point you can either a) wait until our engineering team takes a look at your bug ticket (Iā€™ve brought this thread to their attention) before you make any decisions, or b) revert to your 24.04 boot environment until a future release after this issue has been addressed.

I did help another user through clearing the old data from ix-apps and then redoing the apps migration, but it wasnā€™t a smooth process so I wouldnā€™t suggest that route at this time.

15

Thanks DjP-iX

Everything is stable and running ok on Dragonfish so I will wait as you suggest.

1 Like
16

I also had a problematic upgrade: Dragonfish to EE went well from the OS point of view and all my data is intact, but the app migration didnā€™t. I reverted, using the boot environment options, and I will wait until further updates to EE have occurred. I may have jumped the gun, wanting to be a ā€œgeneralā€ user a bit sooner than I should have.

From a faultfinding/being able to assist point of view, regrettably Iā€™m not yet in a position to go back to EE and try again in order to generate bug reports - too exhausted from the last couple of days of effort trying to sort out problematic apps! Frigate was one app and Motioneye, a custom app, was another: both demanding significant CPU resources under EE (80-100%) compared with DF (30-40%).

(I realise this doesnā€™t help but I wanted to add moral support, and hereā€™s a previous post describing a bit more).

1 Like
17

You might want to submit a Bug Report and debug dump anyway. There may be something of value on the current version your are running. Just make sure to notate Scale rollback and then bug ticket or something like that or point to your post about troubles.

1 Like
18

Good point. Iā€™m doing a bug report - it canā€™t hurt (and Iā€™m pleased to hear it might be relevant)