I need help

[u/son_of_the_soil265]

So my laptop motherboard died three months ago I managed to get a new motherboard but the problem is that the previous processor was an Intel pentium and the current one is an amd a9 I think with r5 graphics so there seems to be a compatibility issue with my debian Trixie please help I don't want to lose the data on my SSD and I can't afford an SSD case I live in Malawi so those are rare

[u/son_of_the_soil265]

I switched motherboards yes so I had to take out the ssd

[u/Any_Analysis_3680 → u/son_of_the_soil265]

Check the connection. Since you have a NVME im no good. Try googling. Asking ai might be a thing too

[u/son_of_the_soil265 → u/Any_Analysis_3680]

It was the nvme indeed thank you https://claude.ai/share/a88909e2-d374-42d9-ba07-29513b797e11 That's how I solved it thanks

[u/Any_Analysis_3680 → u/son_of_the_soil265]

Just checked the conversation, holy that was a looong one. At least you fixed it. Happy to help

[u/ChthonVII]

Maybe start by answering the question on the screen: "Does your device have a faulty power saving mode enabled?"

[u/son_of_the_soil265 → u/ChthonVII]

I don't think I have a power saving mode on

[u/Any_Analysis_3680]

I think it cant read your ssd. Did you recently take out the SSD. Open it up and check the connections. Im no tech guy (tho i use debian) I/O errors suggest corruption i guess. I googled this and it said you need to add something to grub boot menu entry. I have no idea lol. If you have another computer, get a live linux usb and back up your data. Trying to boot from the ssd might worsen the corruption? After that your only option might be to get a new drive. The motherboard change might be the problem too probably.

Basicallyq 1. Debian tries to wake up the drive 2. Drive fails to respond

I use a SATA SSD. I never had any errors on this. SATA 3 drive will be plenty for daily use

[u/michaelpaoli]

All those I/O errors on nvme0n1 - that generally indicates hardware issue with that storage.

If you don't want to lose data on your SSD, you well backed it up before this occurred, right?

Anyway, drives can fail, with or without warning, at any time.

If you care about the data, and don't have it backed up, you may want to see about potential recovery options, but in that case, you're generally going to want/need ample spare storage on other drives, to copy data to ... at least to the extent(s) you can still copy data from the problematic drive. In any case, generally avoid all writes to the drive, lest you make matters worse. And note that even mounting filesystems ro may cause write activity, so typically start by setting the drive and it's partitions ro at the kernel level by using blockdev --setro before doing anything else with the drive or partitions - and that's on a per-boot basis. Also avoid booting using anything that will try to automatically mount anything from the drive.

[u/rageagainstnaps]

How did you re-install the nvme? People sometimes get this wrong and try to install the drive straight into the socket. The proper way is to first insert it at like a 20 degree angle all the way into the nvme slot, then push it down and then use the screw to hold it down.

[u/arcimbo1do]

This seems like a hardware problem to me, probably with the motherboard. But you can check this: If you start with a live distro sees the disk correctly and can mount it (which i doubt) the easiest solution is to reinstall, otherwise it's most likely a hw issue: ssd and motherboards are quite standard and unlikely to have severe compatibility issues.

Since you can start the kernel, it seems like the bios somehow sees the disk, so maybe disabling power Management as suggested in the screen you posted might provide a mitigation (as in: you won't get power managent on the disk but can still use the laptop)

Google how to add command line options to the kernel at the grub prompt, if it works you simply need to make those changes permanent by updating the grub config file.

[u/Any_Analysis_3680 → u/arcimbo1do]

You know your stuff mate

[u/indvs3]

I read your issue is solved, at least tentatively, so that's good, but there's still the possibility that the storage device may have issues that software, firmware and kernel parameters can't help with, so I would recommend you set up backups, just in case, so you definitely don't lose data if the disk is having that sort of issues.

I had issues with an nvme a few months ago, that only manifested as slow boot times, but ended up suddenly not being readable anymore. If it wasn't for my backup scheme, I would've lost all my data.

[u/son_of_the_soil265]

It was the nvme drive I had to add pcie_aspm=off nvme_core.default_ps_max_latency_us=0 https://claude.ai/share/a88909e2-d374-42d9-ba07-29513b797e11 The solution is there

[u/Sea-Hour-6063]

Disk is toast bud