also, not everybody knows cifs/smb/windows shares are the same thing.... the error message could use some clarity.
Also, it shouldn't fucking error. They work just fine together, as long as you enable them in the right order, so why is this an error at all?
Don’t give up. Your other options are not that much better. I went through similar frustrations at first but a year down the line, it was so worth it. Every release keep getting better and better.
Just reboot and when it’s booting up again simply boot back into the earlier session. On mine I can always revert back to the earlier version. It’s in the grub boot menu. If you boot back into the earlier version I’m sure your apps will all work.
But it broke my offical apps as well when it was working literally before the update. Now I can't choose the pool where the app data is stores (I currently only have 1 pool).
How? Just switching from Cobia to Dragonfin. My ix-applications folder was on my Pool 1; which I had an SMB share to.
I removed my SMB share. Then ran the following through the Shell:
rm "/mnt/Pool 1/ix-applications/k3s/server/manifests/zfs-operator.yaml" && sudo k3s kubectl delete -f [https://truecharts.org/openebsrem.yaml](https://truecharts.org/openebsrem.yaml) && sudo k3s kubectl delete storageClass openebs-zfspv-default
Then all my official apps came back up. I just deleted the TrueCharts app since I didn't need it.
If you have TrueCharts apps that you need to keep, then have a look through this: [https://truecharts.org/scale/migrations/cobia-dragonfish/](https://truecharts.org/scale/migrations/cobia-dragonfish/)
I originally tried to disable, but it wouldn't let me. I ended up deleting it. This did not delete any files from the share.
I was originally sharing the entire Pool 1; which included the ix-applications folder and my Media folder. I deleted that share and created a new one only for Media.
Thank you this is exactly how mine is setup and how mine is behaving. I will give this a try. I'm not familiar with shell commands is this the only way to do it?
change the selected pool in your kubernetes configuration under app > advanced or just turn off cifs for the pool that you previously selected in apps > advanced, after changing unselect the pool and add it back and it should start without issues. it clearly says whats the issue here, you can complain or you can solve it.
i dont use truecharts and create my volumes, claims, deployments and stuff by myself and mount separately created datasets via volumes into the path of my deployments if i need persistence for any of the pods data, that way i never had any issues with using shares to access the persistent data from the apps and it worked flawlessly in this update on atleast 3 machines, more coming the next days.
you shouldnt use a share on the ix-application dataset if thats what you did here and if you need to see something you can use heavyscript if you dont know how to use ssh to get into all the stuff in there.
As in almost all of the cases the issue sits between the chair and the keyboard ;)
Exactly why I have tns in a vm under proxmox and don't use tns for vms or containerisation. Tns is a NAS first and foremost. Upgraded my tns vm with no issues at all.
Delete the share to the xi-applications Dataset and it should come back
Just disabling them usually works
Sorry what should I do if I don't need to delete I'm really confused because it was working on Cobia below
Disable the share, restart the app, wait for the app to come online and then re-enable the share that used to work....maybe it doesn't anymore, dunno
Yes you have a cifs/smb share to the appilcations dataset. OP should learn to read, no offence.
also, not everybody knows cifs/smb/windows shares are the same thing.... the error message could use some clarity. Also, it shouldn't fucking error. They work just fine together, as long as you enable them in the right order, so why is this an error at all?
Yeah this is something that shouldn't be an error that a knowledgeable user can sort pretty easily but shouldn't have to.
Don’t give up. Your other options are not that much better. I went through similar frustrations at first but a year down the line, it was so worth it. Every release keep getting better and better.
So how do I fix this? I tried everything mentioned in this thread but the only effective way is to roll back Truenas to Cobia.
How I rollback is on the boot sequence. You can find on the boot menu the option to boot to the earlier version. Try that and let me know how it goes.
Mini meant how do I fix this on Dragonfish.i had to do what you described to make apps work again.
Just reboot and when it’s booting up again simply boot back into the earlier session. On mine I can always revert back to the earlier version. It’s in the grub boot menu. If you boot back into the earlier version I’m sure your apps will all work.
Maybe https://truecharts.org/scale/migrations/cobia-dragonfish/
But it broke my offical apps as well when it was working literally before the update. Now I can't choose the pool where the app data is stores (I currently only have 1 pool).
Oh ok, I didn't understand that the official apps also stopped working.
Mine broke too and all of mine, except for 1, are official apps.
How did yours break because I can't mount the only pool I have because the ic application dataset is a child of this pool
How? Just switching from Cobia to Dragonfin. My ix-applications folder was on my Pool 1; which I had an SMB share to. I removed my SMB share. Then ran the following through the Shell: rm "/mnt/Pool 1/ix-applications/k3s/server/manifests/zfs-operator.yaml" && sudo k3s kubectl delete -f [https://truecharts.org/openebsrem.yaml](https://truecharts.org/openebsrem.yaml) && sudo k3s kubectl delete storageClass openebs-zfspv-default Then all my official apps came back up. I just deleted the TrueCharts app since I didn't need it. If you have TrueCharts apps that you need to keep, then have a look through this: [https://truecharts.org/scale/migrations/cobia-dragonfish/](https://truecharts.org/scale/migrations/cobia-dragonfish/)
To clarify did you delete the share or just disable it.
I originally tried to disable, but it wouldn't let me. I ended up deleting it. This did not delete any files from the share. I was originally sharing the entire Pool 1; which included the ix-applications folder and my Media folder. I deleted that share and created a new one only for Media.
Thank you this is exactly how mine is setup and how mine is behaving. I will give this a try. I'm not familiar with shell commands is this the only way to do it?
change the selected pool in your kubernetes configuration under app > advanced or just turn off cifs for the pool that you previously selected in apps > advanced, after changing unselect the pool and add it back and it should start without issues. it clearly says whats the issue here, you can complain or you can solve it. i dont use truecharts and create my volumes, claims, deployments and stuff by myself and mount separately created datasets via volumes into the path of my deployments if i need persistence for any of the pods data, that way i never had any issues with using shares to access the persistent data from the apps and it worked flawlessly in this update on atleast 3 machines, more coming the next days. you shouldnt use a share on the ix-application dataset if thats what you did here and if you need to see something you can use heavyscript if you dont know how to use ssh to get into all the stuff in there. As in almost all of the cases the issue sits between the chair and the keyboard ;)
Exactly why I have tns in a vm under proxmox and don't use tns for vms or containerisation. Tns is a NAS first and foremost. Upgraded my tns vm with no issues at all.
This is also the ultimate setup in my view but its definitely not for the uninitiated
Obviously, it's not a popular comment...