I am not at my PC, so here's from the top of my head:
To boot from an older snapshot of @ you will have to
1. move the current @ to e.g "@broken", followed by a mv "@lastknowngood" to @
2. Snapshots are usually read-only, which means you need to run "btrfs subvolume @ ....- rw" next.
If you now reboot the lastknowngood snapshot will be active .
But, it's highly likely that your kernel/boot files changed between the broken @ and @lastknowngood. Which means your reboot will fail because of different kernel versions in /boot (newer) and @ (older).
I keep a copy of /boot in my @ so it gets included in the snapshots should I ever need them.
Hence, step 3. cp /bootCopy to /boot
4. reboot
elintendo wrote:d_fajardo wrote:I do not see any recommendations on installing Arch and Windows on separate disks in this article.
What I did was:
1) Plug in only the first harddrive, then install Windows as normal.
2) Remove the first harddrive and plug in the second, then install Arch Linux as normal.
3) Plug in the first harddrive again and set up BIOS to always boot with the drive that has preferred OS isntalled.
4) Whenever I want to boot into the other OS I hit F8 (ASUS motherboards) or F11 (MSI motherboards) after pressing the power button and pick the drive the other OS is installed on.That way there's no risk that Windows and Linux will mess with each other.
I did 1 and 2, but setup my system to boot grub, and added Windows to Grub. Avoids messing with BIOS boot order.
]]>Last working iso for me is 06/01/2023 .... next month throws a kernel panic error and months after that do not even get past acpi erros.
Hardware still works great on any os I throw at it with the exception of winblows 11.
Hope people more knowledgeable than I can find a solution.
For now I will hack it out with a fresh install off an old iso.
Edit
While the 06/01/2023 iso loads fine, it fails on installation of pacstrap ..... due to signature errors.
ezik
]]>FWIW sicne noatime is filesystem agnostic, that's one you can always add.
]]>Ultimately, I returned to the old system Xorg + NVIDIA + Plasma6
]]>1) press "e" to edit kernel starting parameters
2) add entry" maxcpus=1 at the end
3) boot with F10
]]>Problem was solved after reinstalling grub with:
grub-install --target=x86_64-efi --efi-directory=/efi --bootloader-id=GRUB
My next steps will be to boot on USB key to change things on the new partition (now that i got my old arch install back): mount the EFI partition to /efi instead of /boot/efi and generate the fstab again, then go back to my main partition and generate the grub.cfg with the os-prober activated. I'll probably do a backup of grub.cfg before, just in case.
I think grub-customizer is the thing that broke my grub, because that's basically the only thing i did that was not in the manual (but I assumed was safe if it was on the official repo...)
Thank you for the help ! I will mark this as solved and I hope to not break something else soon
]]>