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.
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.
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:
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.
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.
It’s called FakeRAID for a reason.