I've lost everything and I don't know how to get it back. How can I repair my system all I have is a usb with slax linux. I am freaking out because I had a lot of projects on their that I hadn't pushed to github as well as my configs and rice. Is there any way to repair my system? Can I get a shell from systemd?

top 50 comments

sorted by: hot top controversial new old
[+] 74 points 2 years ago* (last edited 2 years ago) (7 children)
  • load more comments (3 replies)
    [–] 38 points 2 years ago (1 child)

    Not an endavour/arch user, but have been in similar situation.

    What I did:

    • boot into live USB
    • mount the problematic rootfs
    • chroot to it
    • run pacman update

    Archwiki has a nice article on chroot

  • source
  • hideshow 2 child comments
  • [–] 2 points 2 years ago (3 children)

    Is this work for every system? Like Fedora?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 2 points 2 years ago

    You may need to adapt the last part to your needs.

    Example:

    • for Fedora, you'd use dnf instead of pacman
    • if your bootloader is broken, you'd want to run grub-install or grub-mkconfig
    • if your initramfs doesn't recognize your new partition, you'd want to regenerate it with the current fstab or crypttab
  • source
  • parent
  • [–] 23 points 2 years ago (4 children)

    Boot to a liveUSB of the distro of your choice, create a chroot to your install, and then run a Pacman update from there.

    Googling “Arch rescue chroot” should point you in the right direction. Good luck!

  • source
  • hideshow 5 child comments
  • [–] [S] 4 points 2 years ago* (last edited 2 years ago) (2 children)

    Will this work from slax linux? I am sorry if I seem like I can't fix the issue myself seeing as you have given the resources for me to do so but what would be the exact steps to do that?

  • source
  • parent
  • hideshow 4 child comments
  • [–] 6 points 2 years ago (3 children)

    I’ve never used Slax but it should, boot the liveUSB and enter terminal.

    The general process is:

    • Boot to live Slax
    • Mount your install
    • Mount /proc, /sys, /dev
    • Enter the chroot
    • Check if networking is working
    • Attempt to run commands in your chroot
    • Exit the chroot
    • Unmount everything
    • Boot back to your install

    https://wiki.archlinux.org/title/Chroot

  • source
  • parent
  • hideshow 3 child comments
  • load more comments (3 replies)
  • [–] 4 points 2 years ago* (last edited 2 years ago)

    It should work, afaik chroot always use the binaries of the system you chrooted, so you will be able to use pacman normally. I don´t remember if chroot will mount the efi partition by default, you can do this before go to chroot (again, I'm have some memory issues but I believe that /dev does not mount as well if you just use chroot, this is why arch have arch-chroot that mounts this kind of stuff but you can mount before so it should work).

    Assuming you are using systemd boot on efi partition (that is likelly if you have not changed the installer defaults), what I would do:

    • On your live CD run sudo fdisk -l to get what is the efi partition, usually will be /dev/sdb1 since sda will be your usb, you should be able to see something like that.

    • Then you will mount your endevour partition, in your situation should be sudo mount /dev/sdb2 /mnt/mydisk but check your fdisk command output.

    • Now you will have to mount the efi partition sudo mount /dev/sdb1 /mnt/mydisk/efi

    • Then you can use chroot /mnt/mydisk/ and proceed to do a pacman -Syu, this should trigger the post scripts that create the kernel images on the efi partition.

  • source
  • parent
  • load more comments (3 replies)
    [+] 14 points 2 years ago (15 children)
  • load more comments (14 replies)
    [–] 8 points 2 years ago (1 child)

    Been here before, but didn't bother asking for help. Just used a liveusb to grab what I needed and reinstalled. I need to learn how to chroot ...

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 7 points 2 years ago (3 children)

    To add to the other responses, after you recovered your stuff you could probably like moving to an immutable OS if you risk having power issues often, the transactions won't be applied until everything is done so if anything happens during a transaction you'll just remain at your last usable state

  • source
  • hideshow 6 child comments
  • [–] 6 points 2 years ago (1 child)

    I had the same thought, but didn't want to sound insensitive.

    Saying "Your fault, using Arch for something important is a bad idea, you should have made a backup before", while he fears all his important data is gone, would have been rude and very unhelpful.

    But immutable distros solve these issues, yes. Since I switched to Silverblue I've never been more relaxed than ever. If something goes bad, I just select the old state and everything works, and updates never get applied incompletely like here.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 years ago (1 child)

    Note that this isn't about immutability but atomicity. Current immutable usually have that feature aswell but you don't need immutability to achieve it.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 years ago

    Yeah you're right, however searching "linux distro with atomic updates" doesn't seem to turn up much, as you say, in most cases the two features happen to come together and the distros that have them are mostly known for the former

  • source
  • parent
  • [–] 6 points 2 years ago

    If nothing else, your files are all fine. You can mount your drive on a different system (like a live USB) and copy all your files.

  • source
  • [–] [S] 4 points 2 years ago

    Thank you all for offering advice. I did eventually get it working and repaired all the packages.

  • source
  • [–] 4 points 2 years ago (1 child)

    Other people will probably give you better answers, but I think the solution is quite easy: chroot and relauch the update.

  • source
  • hideshow 2 child comments
  • [–] 4 points 2 years ago*

    There is nothing worth of freaking out in your situation. Your files shouldn't have been impacted at all.

    Boot from LiveUSB and reinstall the packages you were updating, maybe reinstall grub too.

    There are tons of guides for this in the Internet, like this one: https://www.jeremymorgan.com/tutorials/linux/how-to-reinstall-boot-loader-arch-linux/

    Edit: since you probably use systemd-boot, as I can see from your post, obviously the grub part of my comment shouldn't be done. Replace those parts with systemd-boot reinstallation. Even better if pacman will update it, because there's probably some hook already to do things manually and you won't have to touch systemd-boot at all

  • source
  • [–] 3 points 2 years ago

    Assuming you have access to a secondary computer to make a LiveUSB

    • boot a live disk/USB on your PC and copy the data you want off. Then reinstall the OS.

    • If you haven’t got a drive you can move data to, from the live OS, partition your disk and move the data to the new partition CAUTION ON PARTITIONING

  • source
  • [–] 3 points 2 years ago*

    Boot a live Linux, chroot into your system, run pacman again and fix your systemd boot to include a fallback option for the next time this happens.

  • source
  • [–] 3 points 2 years ago (1 child)

    Does Timeshift work on Arch? If so I would look into it, saved my ass a few times.

  • source
  • hideshow 2 child comments
  • [+] 2 points 2 years ago* (last edited 2 years ago)
    [removed by mod]
  • source
  • load more comments
    view more: next ›