Installation metrix for dual booting

Hello :raised_hand_with_fingers_splayed::smiley:.

In order to create a (or more) dedicated partitions to dual boot Garuda Dr460nized with Windows 10, what size of a partition is adequate taking in account how much space TimeShift backup program takes on the long run ?

Does the boot loader install itself in the Windows 10 System partition ? If yes, how can we prevent a Windows 10 update to rewrite the boot loader in the System partition then loading the dual boot function ?

Thanks in advance for your answer.
Best regards
iBenny

That is fairly unanswerable. It depends how much software you install and how much data you install. 20GB might be more than you will ever use or 20TB might not be enough.

As far as timeshift snapshots, that also depends. btrfs snapshots only use space as data changes. If you keep your snapshots around for a week, you might be using barely any disk space at all. If you keep them for 10 years, you might be using many times the amount of data you currently have on disk. The same goes for rate of change. If you regularly download large amounts of data and delete it, your snapshots will use more disk space than the opposite.

2 Likes

Welcome iBenny. Given @dalto is right, no one can say what your use case will be I will simply say

MAGIC 8 BALL SAYS YES :wink:

As for the boot loader stuff prepare for Windows to constantly screw it up. Updates can and will nuke it and there isn't much you can do about it. Microsoft doesn't want you to have choice...hell they won't even let you install a second browser anymore muchless share the efi boot partition. :wink:

2 Likes

There’s no way to prevent Windows from “repairing” the boot loader - it will do what it wants, even including re-writing the EFI boot variables completely to restore the defaults.

However, Garuda includes a utility for restoring GRUB in the event this happens - boot the live image, load Garuda Assistant (which should autostart anyway) and there’s a button to click.

Personally, and because I like to know exactly what happens on my system, I have found some success with having a second EFI partition for Linux so there is no overlap at all, then when Windows decides to reset the EFI boot entries I can boot from a live image, mount and chroot into my install, and re-run grub-install.

3 Likes

Dude that's sooooo like work :wink:

You're referring to using Windows aren't you? :grinning:

2 Likes

No no...Windows is like PAIN :wink: Though I will traditionally take Windows over MacOS. That's Painerer.

Hi everybody :raised_hand_with_fingers_splayed::smiley:

Some precisions:
1- I have a BIOS/Mbr system (not UEFI)
2- Yes I'll dual boot w/Windows 10

My HDD0 have more than 4 partitions so the one for Garuda Dr460nized will not be a Primary but a Logical one.

My protection strategy will be this one, considering the following installation scenario :

Scenario :
1- Replace partition
2- No swap partition (I have 24GB Ram)

I presume that if I do this, the boot loader will install itself in the System partition; right ?

If I choose :

1- Manage partitions

and I set a root partition and a home partition, do I have to make also a boot partition or will Garuda automatically use the System partition to install its boot loader ?

Protection :
1- Backing up the System partition Before installing Garuda
2- Backing up the System partition After installing Garuda

so if a Windows upd messes up the System partition, I just have to restore it with the backed up one.

So far so good ?

Best regards
iBenny

What I do to keep windows from messing with my Linux is have a SSD just for windows and one just for Linux and installed both with the other drives disconnected. If you have a laptop obviously that is not really a thing you can do but in any case they both have their own EFI partition and can be booted into by selecting f11 Although when I changed my grub setting recently windows shows up now, so I can boot from both through grub, or I can boot windows from the motherboards boot menu.

Maybe keep a Garuda live usb handy in case windows messes with the boot partition, so you can repair grub if windows messes things up.

If the Garuda Developers themselves will not support Windows & Garuda dual-boot, it will be disingenuous for me to push you to that direction.

If you need to run pesky Windows apps that won't cooperate with Wine, use a VM the same way as I do.

If you really persist of installing both Linux and Windows, use separate drives and use a 3rd party bootloader. That is less prone from bootloader overwriting, but still in all Microsoft's wisdom it really wants for Windows to be the sole ruler of your computer.

1 Like

Sample

lsblk -f
NAME FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
zram0
                                                                            [SWAP]
nvme0n1
│                                                                           
├─nvme0n1p1
│    vfat   FAT32 SYSTEM_DRV
│                       6469-0837                             226,8M    11% /boot/efi
├─nvme0n1p2
│                                                                           
├─nvme0n1p3
│    ntfs         Windows-SSD
│                       3AE6699EE6695B61                                    
├─nvme0n1p4
│    ntfs         WINRE_DRV
│                       527469EC7469D2F1                                    
└─nvme0n1p5
     btrfs              ed159bee-f3f4-4cb1-aeff-997938929ff7    234G     6% /var/log
                                                                            /var/tmp
                                                                            /var/cache
                                                                            /home
                                                                            /srv
                                                                            /root
                                                                            /

By the way, it works, only in case of problems you are on your own. Because the Garuda team are not free Windows employees.

3 Likes

Windows will change your boot sector no matter what. It's not just because it's UEFI. All the suggestions are really like "work." Having to disconnect and reconnect drives, constantly boot off a flash drive to repair things dude just toss Windows in the trash already :wink:

Seriously though why go though all this to keep Windows? What is the killer app you need it for?

VCDS, maybe it will work on wine, but I got M$ with the laptop and when using it always remember why I do not like it. :smiley:

2 Likes

There is a hardware solution for this issue. I use SSD hot swap racks for my computers. It's pretty simple, shut down, swap drives to whichever OS you wish to boot. It takes all of a couple of seconds to swap drives in the caddy and then restart.

Of course I would never waste an SSD on Windows, but small SSD's are super cheap these days.

4 Likes

Lol Wendell did a think on IcyDock today and never hot swapping SSD. I hope your docs have the ground first leads. :wink:

I usually shut down if swapping SSD's. They may be called hot swap racks, but I've never been too confident in that aspect. Icydocks have worked well for me. Although, I have used other brands and they were fine as well.

1 Like

GREAT IDEA djwyman !!! :clap::grinning_face_with_smiling_eyes: :bouquet:

Of course !

But answer this please : when installing Garuda beside a Windows 10 BIOS/MBR pc with the “Replace partition” option, is the boot loader installed on the System partition ? If so, can somebody include a full tree (window style) of System partition here please ?

Thanks in advance.
Best regards
iBenny

Unfortunately, I do not understand the question.