I cannot get further than GRUB except to rescue mode, when I attempt to boot the main Fedora OS it gets stuck on searching for a disk indefinitely. Gets stuck on Job dev-disk-by\<many symbols>.device/start running (1h / no limit) in the console.

I have a Windows partition on same drive, it also doesn’t boot, it’s rescue command prompt (from where you are instructed to open notepad to rescue files) doesn’t “see” any disk but C: and X: (emerg boot).

I tried booting this machine with two live OS USBs: Fedora and SystemRescue. Neither of them list the SSD (or anything but the USB drive FS itself) in lsblk or the file manager.

Due to lack of storage mediums, I haven’t done a backup in a while. How can I rescue the files? Many passwords are also stuck there, in Firefox manager I wasn’t able to sync due to losing access to the 2FA email.

Edit: SOLVED! Needed to switch disk mode in BIOS/UEFI from RAID to AHCI. IDK how it got to RAID in the first place.

  • nitroemdashOP
    link
    fedilink
    arrow-up
    2
    ·
    3 months ago

    Latest DMESG logs are several days old, I’m not sure I had this problem back then. Nothing seems to be useful there, standard USB connect/disconnect stuff.

    I enabled S.M.A.R.T. in BIOS, it seems it doesn’t see an issue with the drive (PredictFailure in wmic is FALSE)

    PhotoRec and TestDisk do not see the disk when booted from live media, only the 15GB drive itself and 804MB loop0.

    • mvirts@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      3 months ago

      Can you post your dmesg output from booting a live USB? Maybe there will be a clue in there.

      How is this ssd connected? Nvme? Sata?

    • atzanteol@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 months ago

      When you boot a recovery image does it have any dmesg logs though? You should see something there when you try to mount it

      Does “fdisk -l” show all your partitions on that drive?

      • nitroemdashOP
        link
        fedilink
        arrow-up
        1
        ·
        3 months ago

        No, fdisk shows only the drive itself.

        I didn’t find any obvious errors in dmesg logs, but again I don’t know much about them. You may check them out here: https://termbin.com/975x

        • atzanteol@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          2
          ·
          3 months ago

          This seems suspicious

          Found 1 remapped NVMe devices.
          Switch your BIOS from RAID to AHCI mode to use them.
          

          Have you setup a RAID?

          • nitroemdashOP
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            3 months ago

            Don’t recall doing so. I think I saw something about automatic switch to/from RAID and AHCI in boot logs?

            I’ve actually seen “something/AHCI/RAID” switch in BIOS set to RAID. Will try switching to AHCI.

            Edit: IT WORKED! I changed RAID to AHCI, now the system boots as expected. Thank you. Will change to solved.