Go back to Core?

Hi,

I tried Scale as an experiment, but the overhead of Kube for my little atom was too much.

I know it isn’t supported, but if I go back to a BSD based system (e.g. Core) will the pool be recognised?

I’m happy for a 100% clean restart, but obviously, I’d like to be able to get my pool back :wink:

I guess the main issue is that the ZFS version on the system I switch to should be at least as up to date as the ZFS currently running in Scale? Is that the only issue (given that I’m happy to have a clean system other than the pool).

Many thanks,
Dan

I’d suggest looking into Sandboxes/Linux Jailmaker before switching back to Core.

Its basically very similar to Core Jails, and doesn’t have the overhead of k3s

2 Likes

Thanks, I’ll take a look. How do I kill k3s?

Go into Apps -> Settings -> Unset Pool to disable k3s entirely.

And yes, I’d also recommend the Sandboxes method first if you need super light-weight containers.

2 Likes

For completeness, as long as you did not do a zpool upgrade the pools should not have any issues in going back. Correct me if I am wrong, SCALErs.

1 Like

I guess I can try it with a live USB.

Correct, pools are compatible between versions as long as you don’t upgrade them past what the previous version can read.

I’m just not a fan of running random scripts.

It’s not really random, though I understand your willingness to come back to CORE.

An option is to try jailmaker as mentioned above.

As for switching back to core. If you have not upgraded the pool under scale then you should be fine.

I use mirrored boot, pulled one SSD off, migrated to scale, data pool imported but took 15 minutes, unhappy, replaced the scale boot SSD with the core mirror and I am back to business.

Is it supported? No. Did it work for me? Yes.

Finally got round to this. Sadly it looks like I must have succumbed to the UI nagging me and upgraded the pool (under core):

status: The pool can only be accessed in read-only mode on this system. It
cannot be accessed in read-write mode because it uses the following
feature(s) not supported on this system:
org.openzfs:zilsaxattr (Support for xattr=sa extended attribute logging in ZIL.)

I tried exporting under scale first, but same result.

Importing now back under scale… (seems to be working fine).

Thanks all for tips. I’ve decided to basically run nothing on my NAS except NFS / have a dedicated ‘server’ on top of that.

Should be importable with the 13.3 beta.

3 Likes