You’d normally use a software raid implementation these days, and Linux has a number of those. But yeah, dual booting can expose some quirks and filesystems and disk setup in general is one of the most prominent.
Server-level hardware RAID is fine on Linux. It has to, because manufacturers would cut out a huge chunk of their market if they didn’t. Servers are moving away from that, though, and using filesystems with their own software RAID, like zfs.
Cheapo built-in consumer motherboard RAID doesn’t work great on Linux, but it’s also hot garbage that’s software RAID with worse performance than the OS implementation could give you. I guess if you’re dual booting, you’d have to do it that way since I don’t think you can share software RAID between Windows and Linux. It’s still not great.
Cheapo built-in consumer motherboard RAID doesn’t work great on Linux
That is what I actually meant.
I guess if you’re dual booting, you’d have to do it that way since I don’t think you can share software RAID between Windows and Linux. It’s still not great.
That’s why you don’t do RAID at all on a daily driver. You make/buy a NAS for that kind of thing. Maybe just RAID1 in hardware, cuz that’s easy to set up and generally just works, even with low end hardware solutions.
Beware of the W̷̞̬̍̌͘͜ĭ̴̬̹̟͕̒̆̈́n̸̢̧̙̈́̅̂̆̕͜ͅd̵̟̟̪͎̀̀ő̴̼̺̺́̐̂͘w̵̨͊̀s̵̡͎̭̊ ̸͔̬͔̜̊́̈́̌̈́ͅŬ̴͉͚̳̌̉͘͝p̸̼̅̆͐̃̑d̸̜͂ǎ̵̛̯̏͝ť̷̰é̸͇͝ as it can screw up/overwrite your other bootloader completely.
Kinda sucks, when you’ve got a meeting/work and you find out that forced update made your system unbootable/partially unbootable and you now get to live boot in and go fixing the EFI partition manually, in the CLI.
That happened to me once and that’s when I decided feature parity was less important than a reliable system that “just works” for getting things done on a schedule. (I removed windows completely, in case that wasn’t clear)
Anyhow, make sure you install windows to a separate drive that can’t see any others during the windows install, then will keep the bootloader separate.
I ran into similar issues before. My plan was to install Linux on a separate M.2 so Windows won’t interfere and manually boot the OS I want to manually.
After a while, you’ll hit a point where parity is impossible going the other way.
I’m running a striped partition and a mirrored partition with only two drives, and using an SSD to bcache the whole thing. I’ve even got snapshotting set up so I can take live backups.
I have no idea where to start with that setup on Windows.
I had a hell of a time just trying to get Mint to write to an external drive, including unmounting and remounting the drive countless times trying to get it to mount as rewritable (adding it as a mount option wouldn’t work in terminal or in “Disks”), it would just refuse to let me write to it, I could still read everything fine. I finally quit, got a second drive, backed all my stuff up and reformatted the first one, which Mint now sees and writes to just fine despite being configured exactly the same way it was before.
That is a massively condensed story, and if I ever have to look at fstab again I might just have an aneurysm. Y’know how hard it is to write things to an external drive in Windows? You plug it the fuck in.
Anyone who says Linux is ready for the masses is deluding themselves. It’s fine for nerds, people who like to work on their computer, but it is absolutely not ready for people who like to do work on their computer. Not when something as simple as “yes I’d like to save this to an external drive please” turns into a days-long rabbithole of bullshit that culminates in me buying an extra 8TB drive off Amazon.
I am currently dual booting and trying to get feature parity in my Linux install as a reletave newbie.
So far the largest hurdle I’ve been able to solve was getting my RAID array recognized. That sent me down a rabbit hole.
To get it working in Linux I needed to:
To get it working in Windows I needed to:
You’d normally use a software raid implementation these days, and Linux has a number of those. But yeah, dual booting can expose some quirks and filesystems and disk setup in general is one of the most prominent.
20 years ago it was PCMCIA wifi drivers.
Now it seems like it’s always some kind of disk boot filesystem issue.
Are you using hardware RAID? yeah, that doesn’t go too well with Linux… works perfectly in Windows though, cuz their softraid solutions are shit.
Server-level hardware RAID is fine on Linux. It has to, because manufacturers would cut out a huge chunk of their market if they didn’t. Servers are moving away from that, though, and using filesystems with their own software RAID, like zfs.
Cheapo built-in consumer motherboard RAID doesn’t work great on Linux, but it’s also hot garbage that’s software RAID with worse performance than the OS implementation could give you. I guess if you’re dual booting, you’d have to do it that way since I don’t think you can share software RAID between Windows and Linux. It’s still not great.
That is what I actually meant.
That’s why you don’t do RAID at all on a daily driver. You make/buy a NAS for that kind of thing. Maybe just RAID1 in hardware, cuz that’s easy to set up and generally just works, even with low end hardware solutions.
It’s called FakeRAID for a reason.
Why have I never thought about this? Dual boot and bit by bit work on feature parity while still having an OS that’s my daily driver.
Beware of the W̷̞̬̍̌͘͜ĭ̴̬̹̟͕̒̆̈́n̸̢̧̙̈́̅̂̆̕͜ͅd̵̟̟̪͎̀̀ő̴̼̺̺́̐̂͘w̵̨͊̀s̵̡͎̭̊ ̸͔̬͔̜̊́̈́̌̈́ͅŬ̴͉͚̳̌̉͘͝p̸̼̅̆͐̃̑d̸̜͂ǎ̵̛̯̏͝ť̷̰é̸͇͝ as it can screw up/overwrite your other bootloader completely.
Kinda sucks, when you’ve got a meeting/work and you find out that forced update made your system unbootable/partially unbootable and you now get to live boot in and go fixing the EFI partition manually, in the CLI.
That happened to me once and that’s when I decided feature parity was less important than a reliable system that “just works” for getting things done on a schedule. (I removed windows completely, in case that wasn’t clear)
Anyhow, make sure you install windows to a separate drive that can’t see any others during the windows install, then will keep the bootloader separate.
I ran into similar issues before. My plan was to install Linux on a separate M.2 so Windows won’t interfere and manually boot the OS I want to manually.
Proprietary RAID in linux is a shit show. That’s why everyone uses software RAID.
After a while, you’ll hit a point where parity is impossible going the other way.
I’m running a striped partition and a mirrored partition with only two drives, and using an SSD to bcache the whole thing. I’ve even got snapshotting set up so I can take live backups.
I have no idea where to start with that setup on Windows.
I had a hell of a time just trying to get Mint to write to an external drive, including unmounting and remounting the drive countless times trying to get it to mount as rewritable (adding it as a mount option wouldn’t work in terminal or in “Disks”), it would just refuse to let me write to it, I could still read everything fine. I finally quit, got a second drive, backed all my stuff up and reformatted the first one, which Mint now sees and writes to just fine despite being configured exactly the same way it was before.
That is a massively condensed story, and if I ever have to look at fstab again I might just have an aneurysm. Y’know how hard it is to write things to an external drive in Windows? You plug it the fuck in.
Anyone who says Linux is ready for the masses is deluding themselves. It’s fine for nerds, people who like to work on their computer, but it is absolutely not ready for people who like to do work on their computer. Not when something as simple as “yes I’d like to save this to an external drive please” turns into a days-long rabbithole of bullshit that culminates in me buying an extra 8TB drive off Amazon.
I’ve been using Linux for too long because that list of steps sounded completely reasonable to me.