MindBl0wn

Thanks for your answer. For this specific part of the problem, it seems the right solution. Nvm. My workaround works now and i can continue with my configuration. Thanks so far.

Hi everyboy! Finally tried unraid (coming from omvnas) and seems pretty cool and intuitive so far. But maybe i hit a bug or something. Tested with Version 7.1.2 and 7.1.4 Create Pool: "zfs_tiny" Numbers: 2 Add Disks (2x 2TB identical Iron Wolf) Go inside pool name -> FS: ZFS -> Profile: Stripe - 2 of 2 Disks Startup Array -> A) 1 disk is kicked out of the pool and when i re-add it, i cant change the profile anymore so its default "mirror" is used. OR B) Array starts and only 1.8XTB is shown and the profile is set on mirror again. And here is the Clue: tried it with BTRFS and same behaviour. RAID0 goes to RAID1. Is there a chance that there is some incompability between the Disks? I erased both completely. I formatted them completely. I did a "New Config". What else? Thanks in advance! Maybe some edits: I only use pools and cache, no array because i just want to manage everything like jbod and: in 7.1.4 neither pool 1 or pool 2 would be running as stripe. After downgrading to 7.1.2 first pool works but second still fails. When i use cmdline for creating a zfspool as stripe it works and is shown in zfs master but not as pool :/ I found a workaround. Create pool with 1 disk Add disk (1 pool with 1 disk = stripe, what else.) Erase all Disk in this Pool (Just to be safe) Set FS to ZFS. Start Array. If "Unmountable or no filesystem" -> Check format all unusable disk -> ZFS should come out. CLI: zpool add zfs_small /dev/sdd -f zfs list already displays correctly. Refresh in the browser show also the correct size Stop Array Add 2nd disk (no more!) Done.