Coming soon - Get a detailed view of why an account is flagged as spam!
view details

This post has been de-listed

It is no longer included in search results and normal feeds (front page, hot posts, subreddit posts, etc). It remains visible only via the author's post history.

4
Volume portability, question of choices.
Post Flair (click to view more posts with a particular flair)
Post Body

I have maintained my data in different formats and in if the copies I have is in ZFS form.

Platform of choice is macOS. Figured I wanted to repurpose a Mac mini. For reasons I won’t go into the base OS has to be macOS.

I used a hypervisor for both Truenas Scale and StarWind. Both use ZFS and Debian (the later is Ubuntu).

I have 2 copies so accidental nuking of my array isn’t stressful and with thunderbolt only the drives are a bottleneck. Restoring is a non issue.

macOS ZFS volumes install features that truenas Scale doesn’t like. StarWind can create pools with out issue and can be mounted in macOS and vice versa.

Why does Scale create Linux partitions on each drive like traditional Linux raid when using ZFS? Mac ZFS will not import and explicitly complains about the Linux partitions. StarWind does not do that and it’s easy to imp/exp.

I would love to give truenas ago but “custom” partitions reduces portability. Scale is not Arm64 ready and when I sunset my intel macs I’ll have arrays I can’t migrate because of a software lock-in.

Author
Account Strength
100%
Account Age
7 years
Verified Email
Yes
Verified Flair
No
Total Karma
8,783
Link Karma
504
Comment Karma
8,045
Profile updated: 1 week ago
Posts updated: 9 months ago

Subreddit

Post Details

We try to extract some basic information from the post title. This is not always successful or accurate, please use your best judgement and compare these values to the post title and body for confirmation.
Posted
1 year ago