this post was submitted on 30 Oct 2023
792 points (95.2% liked)

linuxmemes

21222 readers
64 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 1 points 1 year ago (1 children)

    At first mostly smaller issues, but they started to pile up, with me not being able to find any solutions for them.
    But then one of the updates in July killed grub, despite me always using the recommended commands after each update, causing me to lose access to the system. I was not skilled enough to recover it as all the guides didn't really give me enough information for me to handle my encrypted setup, so I tried getting help from their forums, where I then got insulted, gaslighted and trolled by a few users, trying to put the blame on me for using grub instead of the default bootloader, completely ignoring the fact that grub very much was the default boot loader, to the point where a moderator ended up locking & hiding the thread, so that it wouldn't leave a bad look on them, telling me I should probably create a new thread if I still need help. I decided this would be my last time with EOS.

    [–] [email protected] 1 points 1 year ago (1 children)

    I think the default bootloader might depend on some config, because for me grub also wasn't the default, I had to reinstall it once though too, but that was because I accidentally booted into windows and it instantly gave me an update which messed up the whole efi partition. No idea if I have an encrypted setup though. I've barely used the forum so I don't know about that. Thanks for the info though.

    [–] [email protected] 1 points 1 year ago (1 children)

    I'm not talking about dual booting but other Linux bootloaders during the installation. I've not had a Windows installation for several years now. If you don't know whether you encrypted your drives or not, then you likely didn't. Either way, if they are it makes figuring out their correct ID's quite complicated and confusing, which was part of the issue. All the related guides to that topic sort of assumed I already knew what the hell I was doing, hence why I tried to ask for help.

    [–] [email protected] 1 points 1 year ago

    In my Installer grub was not the default bootloader but I had a selection and picked grub since that's what I know.

    Not knowing what id your drives have sounds very problematic no wonder you had troubles. I wish you best of luck with your new setup though :)