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.

  • Korhaka@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    1
    ·
    5 hours ago

    If they don’t see the drive at all it’s fucked. If they see the drive but not partition I normally use testdisk to try and recover the partitions, photorec to look for files if that doesn’t work and it’s not encrypted.

    If it isn’t visible at all then you are looking at drive repair, if you are asking this question that probably isn’t something to attempt. Try another set of cables and port just in case that is the issue though.

    • nitroemdash@lemmy.wtfOP
      link
      fedilink
      arrow-up
      1
      ·
      4 hours ago

      External live OSes don’t see the drive, but some things on drive when it is operating (like GRUB) work. DiskPart on Windows partition sees all partitions.

      • Korhaka@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 hours ago

        Every live OS I have ever run can see physical drives if they exist, sounds very odd to not be able to see it from there and yet grub loads.

        If grub loads can you boot a recovery image from there? Are you sure grub isn’t installed anywhere else too

        • nitroemdash@lemmy.wtfOP
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          1 hour ago

          You mean emergency console image? Yeah, that’s what I’ve been working with. Older kernels also don’t work.

          For the second one, I checked by removing SSD from slot, it refused to boot to GRUB, BIOS gave an error. So it’s on SSD. Plus, Windows partition console sees all it’s files, ~200GB.