3 ms·
> the j model documentation was always very specific that they can't support btrfs and you could never initialize the array into that mode The problem was that
by pilsetnieks 6y ago
> the j model documentation was always very specific that they can't support btrfs and you could never initialize the array into that mode
The problem was that the GUI didn't reflect that, which was the bug. And then they "fixed the bug" the same way that they "fixed the glitch" with Milton in Office Space
- luma 6y agoThe GUI never allowed you to create such an array in the first place. If a user goes out of their way to put their storage array into an unsupported configuration, I get a lot less upset when the vendor makes that harder to do.
- justapassenger 6y agoEven if it’s true, that GUI never allowed it (there’re people disputing it), migrating disks between different products from the same NAS manufacturer isn’t what I’d call going out of your way. It’s one of the reasons to stay loyal to the brand when you upgrade. If it’s incompatible, it should be rejected at the start, or changed later with tons of communication and proper checks (like blocking you from further sw upgrades until you migrate your array). Randomly breaking it is Synology going out of their way to hurt users.