Thanks I was think about going big on the boot efi - can it probe for foreign OS on another SSD easily enough by turning on OS Prober or would that be set by default. Is Systemd-boot still experimental (as it was described in 3/ 2024)or has it matured now?
It should find it fine. I have systemd-boot for Tumbleweed with Hyprland on ext4 with its own 4GB efi partition and MacOS with its own efi partition and it shows up in the systemd-boot menu.
@jjis FYI;
Tumbleweed with GNOME DE
lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1 vfat FAT32 ESP 4FEA-283B 3.5G 13% /boot/efi
└─sda2 btrfs TW041826 867ad03d-9a24-45c8-9e92-72a7f526fb5a 915.7G 3% /var
/srv
/usr/local
/root
/opt
/home
/boot/grub2/x86_64-efi
/.snapshots
/boot/grub2/i386-pc
/
sdb
└─sdb1 ext4 1.0 DATA 22fc9318-689e-45fd-94ec-87444bd42ed8 6.1T 10% /data
sdc
sr0
zram0 swap 1 zram0 1382d322-a008-4d6b-9594-7a341fdb38cb [SWAP]
nvme0n1
└─nvme0n1p1 ext4 1.0 iSCSI-1 7bb2a4bb-dc75-4ef2-bcf3-ff0173aa702a
Tumbleweed and Hyprland (dual boot)
lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1 vfat FAT32 EFI 2860-11F4
├─sda2 apfs 79ab6ba8-6b15-4375-851b-9de7b1e236ea
├─sda3 vfat FAT32 ESP 3CCE-F017 3.7G 8% /boot/efi
└─sda4 ext4 1.0 TW051926 64f50aa1-5c81-4741-ad7c-92c4d522b579 161.5G 4% /
Leap 16.0 with GNOME (dual boot with Windows 11 Pro)
lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
└─sda1 ext4 1.0 DATA 3ec5f735-c12f-4c42-8c35-a1721bd0124d 858G 1% /data
sr0
zram0 swap 1 zram0 34581982-186a-4a53-b734-ead7788fc3e5 [SWAP]
nvme0n1
├─nvme0n1p1 vfat FAT32 ESP 86C1-B552 3.9G 2% /boot/efi
├─nvme0n1p2
├─nvme0n1p3 BitLocker 2 b6aac422-9c17-48e3-9197-c65467167560
├─nvme0n1p4 ntfs B2DC3B6DDC3B2ACD
└─nvme0n1p5 btrfs LP031726 0cfbf95a-5a4e-4e0e-af24-5e9ee5eb8b9a 575.1G 18% /var
/usr/local
/srv
/root
/home
/opt
/boot/grub2/x86_64-efi
/boot/grub2/i386-pc
/.snapshots
/
All used Agama for the installations…
1 Like
For the record this is what I ended up with after about 2 or 3 ISO’s as first off I tried the Live CD, but missed the bit about that not being used for installing. Ended up using the offline snapshot image.
Had to go through the installer a few times to try & get it right as the first time it tried to give me a small boot efi. Eventually it seemed to default to 1gb but I couldn’t see anywhere or work out how to enlarge that - so I ran with it, not wanting to go through the whole thing again. I nearly fell into the systemd trap but realised at the last moment (although that may have been OK) & then switched to my preferred GRUB2 via thje left hand menu.
So in the end this is what I ended up with - the first disk being the Windows drive supplied with the PC & the second being the Tumbleweed one as discussed above. It also proposed I think a 16gb swap file maybe(?), although again I though I might have gone bigger on that too, but same comment about not being able to work out how to change the proposal & just wanting to get it done applied.
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
nvme1n1
│
├─nvme1n1p1
│ vfat FAT32 SYSTEM 6CDE-8B57
├─nvme1n1p2
│
├─nvme1n1p3
│ ntfs Recovery 4CB2DEEAB2DED812
└─nvme1n1p4
ntfs 6EF2E221F2E1ECF1
nvme0n1
│
├─nvme0n1p1
│ vfat FAT32 B25A-50C7 1021.6M 0% /boot/efi
└─nvme0n1p2
│ LVM2_m LVM2 XhOlrL-HXi9-1wYM-3mb8-xMaj-t8Vf-2MMbzk
├─system-swap
│ swap 1 c0f64bdf-fb83-4716-945c-20a6ae522544 [SWAP]
└─system-root
btrfs 22d00a64-814a-4124-ad9f-33ce64307c77 897.2G 1% /var
/home
/root
/srv
/usr/local
/opt
/.snapshots
-
Yes! why I have a separate /home partition, that is not BTRFS.
-
Unfortunately, that doesn’t always happen as we hope.
I have not posted update to my recent thread. Altough I can boot to a previous Snapshot (the good one) … I tried to do a “snapper rollback” and it failed. And it appears it will never happen. Thankfully, my /home content is unaffected (of course, also have backups of /home).
One other consideration about #2 … let’s say you are on Snapshot 300 which got corrupted. You find Snapshot 200 the best to rollback to … and you do so. What about the new and changed files happened in your /home sub-directory between 200-300?
Snapper does not take snapshots of /home. Even if the filesystem is btrfs. It does not roll back your personal files.
I guess I was thinking of this option (that page must be outdated, but not updated). But yes, it’s a manual thing:
Adding /home To Snapper
During installation YaST does not setup a snapper config for /home. We can do so manually:
https://en.opensuse.org/openSUSE:Snapper_Tutorial#Adding_/home_To_Snapper
2 Likes
You can do that, but I, from personal experience, would strongly advice against it. Rather use btrfs send/receive. My experience with snapper for /home were not good. Oh, sure it did what it should do, but that in itself came with a lot of minor ( plasma glitches ) to major ( data loss ) issues. You basically have to create snapshots every time something changes in your homedir. Where that is a place that changes constantly. There is a reason why I backup f.e. ~/.local separately ( databases etc ). What I ran into is basically the same as what is the reason that /var is not included in the system snapshots. After a month of configuring / testing I gave up, and went back to my old rsync config.
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.