Hello,

On my ThinkPad X270, every time I suspend it (using pm-suspend), the SSD stops working and a bunch of "Input/Output" errors come when I read an uncached file.

This started to happen recently.

This also seems to happen on OpenBSD and Windows (On Windows, it straight up BSODs.)

Not using sleep/suspend is not an option because I have to bring this laptop to multiple locations.

smartctl says SSD is fine (passed).

SSD is a SAMSUNG MZVLW256HEHP-000L7.

Thank you for helping me.

Well it's clearly a hardware issue since you have similar problems on three different OSes. I assume you are suspending to ram and not hibernating to disk. A few things you can check:

1. Check your ram with memtest. Let it run overnight and see if any errors are reported;
2. Check with Samsung/Lenovo and see if there is any firmware update for that particular drive. See, for example:
https://support.lenovo.com/us/en/dow...4-bit-thinkpad
3. Check and see if there is any bios update for your motherboard that may address this issue.

You say this recently started happening indicating the drive was waking up normally for some time. It may just be the drive itself is defective or malfunctioning in a way that's not detected by smartctl, i.e. the drive is not properly handling a wake-up signal after suspending for some reason.

I found a workaround. If I remove the HDD password, no I/O errors appear. I think the issue is that the ThinkPad forgets the HDD password when it sleeps, so when you power it on again it can't access the SSD and it gets confused.

I would like to somehow fix this as soon as possible (so I could still use an HDD password). What makes me confused is how the HDD password used to work just fine. I won't mark the thread as solved till I get my HDD passwords working again.

I assume you're talking about a hard drive password set in Lenovo's bios security section. As I understand it, that password key is stored on the disk; if you remove the disk, you still need that password to access the disk even if it is attached to a different box. You get the same problem whether you're running linux, windows or OpenBSD, i.e this is not a linux problem per se.

Given the above, I would conclude you have an issue involving the Lenovo bios properly communicating with the Samsung SSD's firmware. The bios must be able to detect and read the key on the Samsung SSD. Since everything worked before, the question necessarily arises as to what has changed, eg bios updates or changes, Samsung SSD firmware updates.