• 0 Posts
  • 20 Comments
Joined 9 months ago
cake
Cake day: October 4th, 2023

help-circle




  • Per this article from EndeavourOS discovery I was able to repair my similar issue.

    https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/

    However my device wasn’t encrypted. However near the bottom are instructions if you are and they don’t quite match what you said you did. Maybe give it a try?

    "Encrypted installs In case /dev/sda2 is the encrypted root partition you need to unlock:

    sudo cryptsetup open /dev/sda2 mycryptdevice

    It will ask for your LUKS passphrase and unlocks the device into the path /dev/mapper/mycryptdevice

    This path can be used to mount the device:

    sudo mount /dev/mapper/mycryptdevice /mnt

    Followed by mounting the ESP (EFI-System-Partition) into the already mounted system:

    sudo mount /dev/sdXn /mnt/efi

    where in all cases /dev/sdXn needs to be changed according to what is used on your install as partition/device path and the mount path for the ESP needs to get changed according to your installed system in case. If it is /efi you need to mount on /mnt/efi if it is /boot/efi it would be /mnt/boot/efi …"
















  • As a programmer: “your data is boring. I am not interested in leveraging this for anything besides getting the service you are using to work as well as possible”

    Also me as a programmer: “yo, you don’t need that data, stop asking for it. Ohh, your app is broken because it can’t access permissions? Yeet.”

    It’s not about the programmers. It’s about the company and the ability to make money off of data they get from you. You should be the one who gets money for your data. Not Microsoft, not Google etc.

    Is Microsoft making money off of this particular telemetry data? Maybe not. It should always be opt-in