Have a look.
3 posts were merged into an existing topic: Off Topic Chit Chat - (Silliness factor 5)
Amazing topic and tutorial! I Appreciate all the help! Cheers!
As a - slightly - alternative method, this is how I created a multiboot setup on MULTIPLE physical drives:
DISCLAIMER: DUAL-BOOT AND MULTI-BOOT INSTALLATIONS ARE NOT SUPPORTED BY THE GARUDA DEVELOPMENT TEAM.
ATTEMPT AT YOUR OWN RISK, AS LOSING ALL YOUR DATA AND BEING LEFT WITH AN UNUSABLE SYSTEM CAN BE UPSETTING.
BACK UP YOUR DATA EARLY. BACK IT UP OFTEN. YOU HAVE BEEN WARNED.
- Physically disconnected hard drives not used in the installation process.
- Created a new GPT table partition on the secondary drive using GParted.
- Installed Windows 10 to the secondary drive, manually specifying the size of the install to 200GB.
- Messed around with all the stupid Windows updates and drivers.
- Went into the UEFI bios. Disabled fast boot, CSM support, secure boot etc.
- Ran a live instance of Linux Mint, used GParted again to create an EXT4 partition for another 200GB. (Left the remaining 76GB for over-provisioning.)
- Installed Linux Mint with manual ('something else') partition mounting. Linux Mint grub overwriting the Windows 10 EFI partition as per usual.
- Messed around girlifying Linux Mint to my tastes.
- Used GParted AGAIN to create another GPT partition table and then create a 512MB FAT32 /boot/efi partition (on my PRIMARY 1TB drive this time), making sure the ESP flag was ticked. (KDE partition editor only enables the boot flag. It does NOT and cannot enable ESP, so I had a couple of failed installation attempts here until I worked this out.) Also I manually created my BTRFS partition for Garuda, leaving some overprovisioning room.
- Installed Garuda Linux to my primary drive, manually mounting my partitions again in Calamares.
- Reconnected hard drives not used in the installation process.
- Post-installation, I went into UEFI bios and changed the boot order to set the Garuda EFI partition in first place. The grub instance installed by Linux Mint is ignored from now on, and can update in Mint happily without attempting to overwrite the Garuda grub instance.
- Booted back into Garuda, ran 'sudo grub-update' to make sure all my OSes were visible.
And that's it!
Awesome tips and tutorials guys. I just have one question. Are you guys going to respond to all the help requests when those who follow your tutorials have their systems meltdown from a multi-boot SNAFU.
Anyone can setup a dual boot, it's really not that hard. Fixing a dual boot catastrophe on the other hand can take a ton of skill and expertise. No other repair job in Linux is more complex than some of the messes created by multi booting.
Oh and BTW, the most important part is missing from your tutorials. That's the part where you advise the newbies to backup their system first. Cause sure as the day is long, most of the newbies fresh off the Windows boat will meltdown their system at some point and rarely do most ever perform backups. While you're at it why not do a data recovery tutorial for all the newbs who inevitably lose all their data from this, cause I hate responding to those help requests as well.
Sorry if I'm being hard on you guys, but these complications are some of the most difficult issues to reverse when a breakage occurs. Losing all your precious data can be a heartbreaking life lesson. So be careful, because you're playing with fire if you're inexperienced.
If someone follow my tutorial and have the correct partition table boot/efi on sda1 and Garuda on sda2. There is no WIndows update can overwrite GRUB in the future. That's why it's recommended install Windows first. Otherwise you have to repair again and again the boot partion troubles caused by Windows updates.
@tbg Are you guys going to respond to all the help requests when those who follow your tutorials have their systems meltdown from a multi-boot SNAFU?
Of course I'm eager to help people correctly followed my tutorial. I made it so I'm responsible for it.
@tbg The most important part is missing from your tutorials. That's the part where you advise the newbies to backup their system first.
@tbg Fixing a dual boot catastrophe on the other hand can take a ton of skill and expertise. No other repair job in Linux is more complex than some of the messes created by multi booting.
This is how linux works. There are many solution for a problem. Try it, Test it and face the consequences for all the decision you made and learn from your mistakes, the less effective solutions you tried and choose a better one.
Community is for learn mistakes made by others and solving problems together
and don't blame Devs, Admins and People trying to help you if you make something wrong.
I need some people following my method to test it and feedback how is it going to get Your, the Devs and Admins trust to recommend this as a solution without qualm.
I do appreciate your efforts, and also your offer to help out on the forum.
I wasn't just referring to Windows overwriting grub as the only potential pitfall. You are far underestimating the newbs capacity for causing destruction when performing manual partitioning. Whenever an inexperienced user is at the controls partitioning there is a great possibility they will make an error. This can easily result in an OS partition (or a full data drive) being wiped, or worse yet overwritten. At least if they realize their mistake before actually overwriting the partition might be able to be recovered using testdisk. Once it has actually been overwritten the data is pretty much unrecoverable. This happens far too frequently with those unfamiliar with Linux unfortunately.
After answering thousands of support requests at various Linux forums there's only one thing I know for sure. Newbies have an unlimited capacity for screwing up the most well spelled out and clear instructions. When their mistake only involves changing their desktop wallpaper no big deal. When it comes to mistakenly overwriting partitions, or entire data drives this can have catastrophic repercussions (and the distro often gets blamed).
The unknowing user if only doing a single full disk automatic install of Garuda using Calamares at least has limited potential for causing destruction. As it is assumed that all data will be wiped in this situation the user should hopefully not lose any data mistakenly. When installing a dual boot you never know what kind of mistakes an inexperienced user might make that may cause data destruction.
Along with the advice to backup all data prior to installing I would also add one more piece of advice. I would advise all users to either power down, or physically disconnect any data drives not having an OS installed on it. This simple precaution will eliminate the possibilty of overwriting
a storage drive containing a lifetime's worth of irreplaceable family pictures and videos. Unfortunately, no mater how often you caution users to backup their data it is usually ignored (as it is too much effort for the average Windows user). Simply removing extra data drives from the equation requires little effort in comparison to full backups, so it is more likely to actually be performed. This also helps limit the possibility that if backups were actually made that the user won't mistakenly overwrite the backups themselves.
Sadly, newbies no matter how many times you warn them, usually disregard most cautionary advice. That is why Garuda simply tells users we do not support dual booting. Some users (like everything else) mistake that to mean Garuda is impossible to be installed as a dual boot. Obviously that is not the case, Garuda can be installed as a dual boot like most other distros. We simply mean to caution users in advance that if they insist on installing Garuda as a dual boot not to expect official support on our forum. Some kind user may still come to your rescue if you mess things up badly, but we are simply letting users know not to rely on having dual boot issues officially supported.
I appreciate you guys trying to help others. I am only trying to clarify the distro's position on dual booting and the reasoning behind it. Users will inevitably do whatever they're going to do regardless of how many times they are warned anyways. However, in good conscience an effort should be made to prevent unknowing users from shooting themselves in the foot if at all possible.
I've added a disclaimer. Yes, if I see someone who needs help setting up a multi-boot system, I'll help if I can. Usually my advice will be of the 'nuke it and start again' type. With an added, 'Oh, you did back up your stuff before you started, didn't you?' for good measure.
About dual booting and newbies...
I'm one of them, and would like to dual boot Garuda. Yes I made the system backup (TestDisk) of all my important files, and do not have any other hard drives connected other than the primary SSD.
The procedure I heard was that I first needed to manually make a partition using the disk manager inside of Windows such as this one
And then using UNetBootin with the ISO of the OS I want to install it would automatically set itself to the partition I had created.
Can you either confirm or provide me with another method that I can use?
I am fully aware of what I'm doing and take full responsibility in the consequences.
Welcome to the forum.
Making backup to the same hard-disk that you going to modify is useless,
if your goal is to backup your movies, games, music ...etc.
If you don't have any other data drive, not feel familiar with manual disk partitioning and you want to keep this files, then there is no way for Dual Boot.
That does not answer the question though. I'm just making sure I'm doing the correct procedure. When did I say that my goal was to backup media?
My question is (more precisely), assuming I make the partitions in my disk, how would the correct procedure be for a Dual Boot IF I use UnetBootin?
You don't have to do anything, except select "replace a partition" during installation and mark the appropriate place.
There are plenty of Garuda install tutorials on the internet.
In terms of backup, the important thing is to do it with a reliable external hard drive. Anything connected to the PC during the installation process is at risk.
I don't recommend you use UnetBootin to create your Garuda live installer from the ISO. Personally I have found it okay for Ubuntu-based distros, but unreliable with Arch-based distros (and Garuda is one of those). If you are going to do it from Windows, I suggest Rufus instead.
If you use the Windows partition manager to manually create a partition, it will be an NTFS or FAT partition. You will have to confirm that the Garuda installer is reformatting that new partition to BTRFS during the installation process, or bad things will happen. I don't know what they will be, but I don't suggest you try to find out.
Personally I use GParted and no other software to make changes to partitions, but that means another ISO and another USB to use.
Good luck with your installation.
Please note that use of Rufus is officially not recommended:
- We recommend using Balena Etcher to create a bootable USB stick. You can use dd or its frontends (Mintstick, Popsicle, Imagewriter, Mediawriter) on Linux. Do not use Rufus to flash the iso.
Well, next time I'll choose Balena Etcher.
Personally I use Imagewriter as my go-to, but that's using Linux. The OP clearly implied they'd be creating their media in Windows. I've used Rufus successfully in that situation before, but if you don't recommend it, you don't recommend it.
Since "Knoppix" has existed, I've been using Windows and Linux in parallel, although Windows has gradually become a minor matter.
To make a USB stick bootable, I use Linux on-board tools instead of downloading software under Windows.
well I would like to tell a little experience that just happened to me in DualBoot, because before I from the file explorer itself could access my windows partition and from there I could copy files to my partition of garuda because for a long time I think for an update in Plasma with Dolphin now no longer asks for authentication to enter the partition but you can enter defrente, and just yesterday I entered the partition and delete some heavy files like ISO's I had there, and just when I wanted to return to windows it turned out that the NTFS file system was corrupted, and wait for it to restore the truth I do not beat around the bush so I removed Windows defrente and reinstall it, for the information I lost the truth I manage much Drive, Dropbox, Pcloud and OneDrive so I did not mind losing the windows for a day but it remains as a recommendation.
¡¡Do not enter the windows partition and alter the files!!.
IMO the only reason you should alter any files on a Windows drive from within Linux is to remove a malware infection. Even then, it is best to simply flush an infected system as cleaning it unless you are very adept is very difficult.
IMO it is best to leave any Windows installations invisible/unmounted or mount as read only. Doing otherwise is only looking to create problems unless you are extremely careful.
Although I seldom use it, I too have a separate SSD with windows on it which I never touch with linux, but I do have a larger 1tb drive that has an 800gb ntfs partition for data which I share between both windows and linux.
I write and delete stuff there from both linux and windows without any issues and have done this for years with several different linux flavors. I don't really think it's a problem to manage a disk this way, I'm curious if there isn't something specific about the drive being a boot partition vs just a data partition? I'm very curious to know why there would be issues touching windows disks in a lot more detail.