I have been having some issues lately with fedora. This install was pretty reliable and never threw any errors until recently. I also noticed really slow read and write speeds one day. Like 2 times slower then a hard drive. But that went away after some use.

Later that day I updated and it wouldn’t boot. Just a blank screen. I was able to Ctrl alt f1 into a login sceen and run dnf and update.

That fixed it.

Then comes the second issue. I was programming and all of a sudden my python file disappeared out of thin air! Which is funny because I remember saving it. So I downloaded a backed up copy from my nas, and it disappeared again.

I figured it was a problem with Kate so I reinstalled it and it worked and saved files without removing them. Then I shut the computer down when I was done and this morning it boots to a blank screen. And the initial fix I did a while ago doesn’t work. I’m pretty stumped on it and I did capture some photos.

It gets stuck loading this process

Same here

Then it passes them and tries something else

Then we enter this never ending loop.

So what do you guys think? New install of fedora needed or do I need a new ssd?

  • BluescreenOfDeath@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    8 天前

    There’s a program I use on Linux called gsmartcontrol that will run SMART tests on drives.

    Run an extended test on every drive in your computer. If one fails, replace it.

  • nitroemdash@lemmy.wtf
    link
    fedilink
    English
    arrow-up
    5
    ·
    8 天前

    I had the same issue a few weeks ago, same error message. You can find a post about it on my profile. Turns out my BIOS was somehow set to RAID mode and system could not see the drive. I switched it to AHCI and everything was fixed. Check your BIOS settings, if you won’t find the problem there also send DMESG logs from a live USB when it scans for drives.

  • Brickfrog@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    3
    ·
    8 天前

    I can’t say what the issue is but if you’re suspecting memory issues then you should definitely run drive diagnostics. Usually that means you want to install gsmartcontrol (the GUI version of smartctl) or smartctl directly via installing smartmontools.

    With smartmontools installed you’d do something like this in the terminal (on Debian you usually need to run these with sudo, not sure about Fedora)

    smartctl --scan (gives you a list of drives in your system)

    smartctl -a /dev/your-drive (outputs SMART info on the drive, should give you an idea of current status)

    and if your drive is supported you can also run tests, after testing run another smartctl -a to see if anything changes

    smartctl -t short /dev/your-drive (short test usually takes 3-5 minutes)

    smartctl -t long /dev/your-drive (long test, longer more thorough test with SSDs that usually means 30-90 minutes or so)

    With SSDs you usually want to see how many reallocated blocks occurred vs reserve blocks being used up, depends on the drive and what info it provides.

    EDIT: Should be able to do the same with gsmartcontrol if you prefer the GUI.

    • TheOSINTguy@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      7 天前

      I created a live USB and ran smartctl and it didn’t show any issues. I went ahead and reinstalled fedora (the OS was to far gone to repair) and as for all my files they were backed up on my NAS.

      Although files disappearing along with core systems files does point to a hardware issue of some kind, typically you wouldn’t expect a mainstream Linux distro to have a glaring issue like this. So wether it’s something stupid like a dirty contact or it’s a failing transistor there’s only one way to figure out what’s going on here and that’s to keep using it.

  • bigbangdangler@reddthat.com
    link
    fedilink
    English
    arrow-up
    1
    ·
    8 天前

    Any chance this thinkpad has the ssd installed without the caddy?

    If so, it may have intermittent connection issues to the drive. The SATA connectors may not match up quite right. I had a similar issue and it took me a bit to figure out that the caddy really matters on some models (more specifically, you need ≈1mm clearance under the drive for everything to line up properly).