Post upgrade from Core to Scale Error: SMB shares have path-related configuration issues that may impact service stability: volume_1: SMB shares containing the apps dataset are not permitted,

Upgraded Truenas Core 13.0-u6.2 → TrueNAS Scale Dragonfish-24.04.2.5

There are not many posts on this topic, in googling I keep coming back on this constant loop of finding the same posts over and over. After running a while, I got a critical error:

Googling this error, it suggests that I should not be sharing the ‘/mnt/HDD’ path - and I am not - all my shares are at: ‘/mnt/HDD/’

eg:

/mnt/volume_1/backup

My issue is very similar to (but not the same as):

An example of my shares is:

I am sure this is all down to the migration, and I am doing something slightly wrong - having been using this since FreeNAS 11.1 I probably have some cruft hanging around that I am not fully understanding how to resolve, as I don’t fully grok the error meaning. So, things have changed over time, and I am clearly not keeping up.

Do I just need to unshare and reshare these? Is that what the error is suggesting?

What exactly does this error mean?

It mentions the Apps dataset.

Are you running Apps… after migrating from CORE? If so, we’d recommend upgrade to 24.10 - electric Eel

Where is the Apps dataset?

Not running any apps yet. I went dragonfish because I was a little worried about Electric Eel being bleeding edge, but if that’s a recommended path then I will do that right now.

Oh, interesting. It threw a whole bunch more errors after the upgrade to Electric Eel, not going to post the whole thing, as it is long, but here is the gist.

SMB shares have path-related configuration issues that may impact service stability: volume_1: ACL type mismatch with child mountpoint at /mnt/volume_1/ix-applications: volume_1 - NFSV4, volume_1/ix-applications - POSIX, volume_1: ACL type mismatch with child mountpoint at /mnt/volume_1/ix-applications/k3s: volume_1 - NFSV4, volume_1/ix-applications/k3s - POSIX, volume_1: ACL type mismatch with child mountpoint at /mnt/volume_1/ix-applications/catalogs: volume_1 - NFSV4, volume_1/ix-applications/catalogs - POSIX, volume_1: ACL type mismatch with child mountpoint at /mnt/volume_1/ix-applications/default_volumes: volume_1 - NFSV4, volume_1/ix-applications/default_volumes - POSIX,

Looking at the apps dataset, it was blank. I set it to “volume_1” this seems similar to the issue I had here:

Probably cruft carrying over from originally starting out on Freenas 11.1. I think I might have to crawl through everything that is “blank” and define it.

I think the apps were undefined, causing the error? Now I have a whole host of similar errors… Wheee! Upgrades are fun.

Going to have to dig into the new SMB ones.

Well, something definitely did not port over. Looks like all my ACL settings are now blank, probably the cause of the new error:

Will re-define them. I know for SURE these had specific user permissions in 13.06, because I needed to isolate the shares.

Looks like this is just a crawl through all the old leftover cruft from 8 years of running this. Probably will take some time to sort out my directories/datasets/permissions to make the system happy. But at least I have a path forwards. Similar predicament to: