Im giving a go fedora silverblue on a new laptop but Im unable to boot (and since im a linux noob the first thing i tried was installing it fresh again but that didnt resolve it).

its a single drive partitioned to ext4 and encrypted with luks (its basically the default config from the fedora installation)

any ideas for things to try?

  • dustyData@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    2 months ago

    Did you reformat the disk before installing? I’ve seen similar fails when the disk is still encrypted. The installer can’t get a hold of a previously encrypted disk. If there’s no valuable data in the disk, load up a live distro run gparted and nuke the disk blank and pristine again, as gparted doesn’t care about encryption. Then try the installer again.

    • nanook@friendica.eskimo.com
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      2 months ago

      @dustyData @evasync When I install, I generally prepare the partitions ahead of time with gparted, whether or not I create an entirely new partition table depends upon whether it is the only OS on the disk or there are multiple. I’m not using any encrypted file systems, I need the machines to be able to boot without my being present to type in a password or pass phrase. So that is not an issue.

    • evasync@lemmy.worldOP
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      no, I just removed them with the live cd and repartitioned it (Im assuming its doing the same thing under the hood?)

      • dustyData@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        You should let the installer do the partitioning. Silverblue and immutable systems are nitpicky about it. Specially if luks is involved. The whole point is that you shouldn’t meddle with the system at a low level at all.

          • dustyData@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            2 months ago

            Sorry, I was not replying to you (not an insult). I assume you are interacting from Mastodon from the format of the comment, and getting pinged on replies to other comments (?). I mean, you do you, absolutely not going to diss people who want absolute control over their system. But immutable distros are fundamentally an entirely philosophically different approach from how traditional Linux distros have been packaged and managed in the past. That said, I didn’t make the installers, I’m just reporting what has been my recent experience toying with immutable distros. The whole point is to automate as much as possible of the deployment and management of an OS, and do the least amount of tedious manual troubleshooting. If you don’t like that, all the other distros are still there, they haven’t gone anywhere. The current recommendation for Fedora Atomic based distros is to use specialized tools like Universal Blue that allows the user absolute freedom to deterministically configure a Fedora install that results in an immutable OS. And the installer is actually pretty flexible to let you choose how you want the disks laid out. But, the idea is that you should let the installer do its job, that’s for what it was made. If you want to do everything by hand just use Arch, that’s what Arch is for.