Sorry, that I’m not certain of, since that’s an installer-specific thing. I think I’d try that option first, and see if the installer lets you choose the empty drive.

Just spitballing here, but if I read this correctly, you pulled the Windows drive, installed Mint, and then put the Windows drive back in alongside the Mint drive? If so, that might be the issue.

UEFI firmware looks for a special EFI partition on the boot drive, and loads the operating system’s own bootloader from there. The Windows drive has one. When you pulled the Windows drive to install Mint on another drive, Mint had to create an EFI partition on its disk to store its bootloader.

Then, when you put the Windows disk back in, there were two EFI partitions. Perhaps the UEFI firmware was looking for the Windows bootloader in the EFI partition on the Mint disk. It would of course not find it there. In my experience, Windows recovery is utterly useless in fixing EFI boot issues.

It’s possible to rebuild the Windows EFI bootloader files manually, but since you don’t mind blowing away both OS installs, I’d say just install Mint on the second drive while both of them are installed in the system, so the installer puts the Mint bootloader on the same EFI partition as the Windows one. With the advent of EFI, Windows will still sometimes blow away a Linux bootloader, but Linux installers are very good at installing alongside Windows. If it does get stuffed up, there’s a utility called Boot-Repair, that you can put on a USB disk, that works a lot better than Windows recovery.

Why that fellow has such a sterling reputation for honesty and integrity, I can’t imagine why nobody believes him when he says he doesn’t plan to implement it. /s

This is madness, but since this is a hobby project and not a production server, there is a way:

• Shrink the filesystems on the existing disks to free up as much space as possible, and shrink their partitions.
• Add a new partition to each of the three disks, and make a RAID5 volume from those partitions.
• Move as many files as possible to the new RAID5 volume to free up space in the old filesystems.
• Shrink the old filesystems/partitions again.
• Expand each RAID component partition one at a time by removing it from the array, resizing it into the empty space, and re-adding it to the array, giving plenty of time for the array to rebuild.
• Move files, shrink the old partitions, and expand the new array partitions as many times as needed until all the files are moved.

This could take several days to accomplish, because of the RAID5 rebuild times. The less free space, the more iterations and the longer it will take.

If you can assign a second IP address to the network interface, then just do so, and bind the docker container to one, and Adguard Home to the other. Otherwise, the reverse proxy based on the server name is the way.

This just sounds like a bad idea, a solution in search of a problem. Sure, sudo is a setuid binary, but it’s a fairly simple program, and at some point, you have to trust the code. It’s also a very fundamental piece of the system that you want to always work, even (especially!) when other things get borked. The brief description of run0 already has too many potential points of failure.

100%

Nah, Linux is confusing because it’s software. I have a well-paying job in large part because Windows and macOS are confusing as hell, too.