And, it looks like that didn't help. The filesystem is still read-only, and when I try to boot without the live USB the BIOS doesn't find any bootable media at all. I think it's time to throw in the towel and reinstall the OS. Thanks for all the help, everyone!
I am kind of surprised the repair operation didnât have more of an effect (one way or the other).
Did you have a chance to check in /mnt/warehouse/garuda-root
? Iâm curious about the state of your files.
The restore doesn't seem to have worked, my /
looks like it's a fresh new install, as near as I can tell. My /home
is no longer on its own partition. On the up side, the data in that partition is all still there--I just need to set it to be the new location of /home
and I guess get my NFS shares set back up, then start testing out hardware to be sure my video card is still working, reinstall programs, and so on.
Any tips on setting up my existing partition as /home
?
If you use the manual partitioning option, you can just mount p3 at /home
and choose "Contents: keep".
Sort of like this: Manual partinioning on Windows Dualboot - #5 by BluishHumility, except you can format the EFI as well if Garuda is the only installation on the disk. Just don't format p3 if you want to keep it.
Just found that; thanks! It looks like things are largely just working now, though I've got some "You are not authorized to execute this file" messages with certain programs (like my password manager, frustratingly). These may be things that I need to reinstall or something.
If you do reinstall, I'd recommend you just grab all packages (yay -Qq
) and back up changed configuration files and then reinstall your system. You can just append all the Qq packages to yay -S
and you got all of your packages back. Configuration files can just be overwritten
This isnât quite right because you will end up explicitly installing all of your dependencies. Better to add -e
or even -et
when creating the package list so dependencies are left out of it.
-e, --explicit
Restrict or filter output to explicitly installed packages. This option can be combined with -t to list explicitly installed packages that are not required by any other package.
Then, when you install the packages the dependencies will be correctly installed as dependencies.
pacman -Qqet
Hm. I had issues with that just not listing some of the packages I had manually installed. Weird.
In some cases it even lists packages that shouldnât be listed there. I can see blisp
in there and I never installed that manually.
If you add the -t
option, it will remove explicitly installed packages (on purpose) if that package is provided by something else. This helps keep the list of explicitly installed packages as minimal as possible.
Packages will be marked as explicitly installed if you have ever used a method like you described above for installing a list of packages that was generated from a -Qq
dump, since that will include dependencies.
Another thing that can cause a dependency to be explicitly installed is if it is not a true dependency but is needed for a makepkg, and is not removed afterward.
If you want to, you can change a package from being explicitly installed to being installed as a dependency by reinstalling with the --asdeps
option.
sudo pacman -S --asdeps [package name]
That seems unlikely because nothing uses this package as a dependency.
pacman -Sii blisp
Repository : extra
Name : blisp
Version : 0.0.4-1
Description : ISP tool & library for Bouffalo Labs RISC-V Microcontrollers and SoCs
Architecture : x86_64
URL : https://github.com/pine64/blisp
Licenses : MIT
Groups : None
Provides : None
Depends On : glibc
Optional Deps : None
Required By : None
Optional For : None
Conflicts With : None
Replaces : None
Download Size : 75.66 KiB
Installed Size : 173.29 KiB
Packager : Maxime Gauduin <alucryd@archlinux.org>
Build Date : Thu 03 Aug 2023 10:19:19 AM EDT
MD5 Sum : a232812494a0f20c65a75337e81806e3
SHA-256 Sum : 5805413aa47c58e419c673cfc81a96d9ffc400d94925f80640aa31d9b6619e1d
Signatures : 0F65C7D881506130
Just to follow up here, I did end up reinstalling, keeping the data from the /home
partition. It worked quite smoothly; so far, I haven't noticed any problems. The few programs that I needed to install worked just fine with the data in /home
.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.