So…I just purchased a brand new WD black SN850X 2TB to store a bunch of games. I installed it on my last NVME slot available no my motherboard, M2C_SB, which I understand doesn’t directly plug into the CPU but onto the motherboard’s southbridge. Not sure if this has any reason for the issue. So, the problem is…whenever the PC suspends (which, by the way, it can go suspended even in the middle of a file transfer…not sure why KDE won’t block that)…anyway, after a suspension, that drive is missing. Checking any partition manager, it shows the NVME drive is still somewhat there, but with no partitions listed. There’s an error 'partition xxxx is not properly aligned". It seems my only option is a reboot. After the reboot, the drive is fine, it’s properly mounted, shows correctly the partition in the disk manager, and runing a check finds no errors. Mind you, there’s 3 NVME drives plugged, only this last one is giving me headaches after suspension.

…what’s causing this? And how can I avoid it?

  • JGrffn@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    3 days ago

    Update your bios, or hope for an update to your bios if you’re up to date. I had similar behavior with an sn850x 4tb on a new system with 2 of them. As soon as I got my motherboard up to date, the problems ended.

    • iturnedintoanewt@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 days ago

      Thanks…I just updated the week prior to receiving the SSD, in order to be sure I didn’t have any compatibility issues…So I guess I’m SOL on that end.

  • Oth@lemmy.zip
    link
    fedilink
    English
    arrow-up
    4
    ·
    3 days ago

    I’ve been having the same problem, and it’s not Linux specific; this happens on both my Linux and Windows partitions. I’ve yet to find a clear cause and no amount of changes to power consumption or boot parameters seems to fix it. In my case, the unit is also the boot/OS drive for both.

    I suspect it’s something related to the NVME, since I did not have the problem with my 1TB unit, it only started after replacing it with a 4TB one. Both are WD, though I don’t have the exact model on hand.

    I’d love to hear back if you find a fix, because it’s got me stumped.

      • Oth@lemmy.zip
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 days ago

        Both are up to date. I actually suspect this is an issue caused by the newer firmware, but there is only one firmware version available when I looked into it.

        I ended up working around the problem, and just using the old NVME as the OS drive and using hibernate rather than sleep. It seems something about going into standby causes the problem, and the system going “cold” by parking onto the disk doesn’t cause the same issue.

      • iturnedintoanewt@lemm.eeOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        2 days ago

        In my case BIOS was updated recently, and seems there’s no new firmware releases for this SSD. So, kinda stuck right now.

  • notanapple@lemm.ee
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    3 days ago

    if you put the same NVME to one of the other slots does it still give this issue?