Issue with SSD ADATA SX6000 on My Lafite III 15.6 with Ubuntu 18.04.3 LTS

Q

quicky

Member
Hi all,

This morning I was working on my Lafite III 15.6 ( received at October beginning ) with Kubuntu 18.04 when suddenly the Linux app I was using warned me that it cannot save it settings as settings location was read-only.
I cleanly shutdowned the PC with again an error message saying that System was not able to save a configuration file due to Read-Only filesystem.
After PC stop I tried several time to restart it and each time it stops with the following error message:

Couldn't get size: 0x800000000000000e
MODSIGN: Couldn't get UEFI db list
Couldn't get size: 0x800000000000000e

and then busybox prompt.
As it mentionned UEFI I went to startup setup in Secure boot settings to check everything was fine
Secure Boot enforcement was disabled but instead of having all keys empty I have a single PKPdb key filled of zero.
I tried to remove it ( when receiving the PC I have to disable secure boot and remove all keys to succeed to boot on my SDD ) but it reappear at each time I save UEFI settings and PC restart.
I also tried to restaure default UEFI factory setttings and then remove all test Windows related key but same error message when booting on SSD and the Null key reappear in PKPdb key.

I don't know what to do.
Sometimes I had some few seconds freeze when accessing disk but it was not so frequent, so is it an SSD issue ? an UEFI issue ? other hardware issue ?

The SSD is a 1 To ADATA SX6000 Pro PCIe M.2 2280
20191120_090338.jpg
 
Last edited:
Q

quicky

Member
After modifying grub boot options by replacing
quiet splash
by
nosplash
I saw there was a filesystem issue on my SDD.
After running the indicated fsck command which fix filesystem issue laptop succeed to boot
I will open a separate thread for SSD issues
 
Q

quicky

Member
Hello,

I have a Laptop Lafite III 15 with an ADATA SSD that run Ubuntu LTS 18.04
In general performances are good but in rare cases I have complete PC freeze and sometimes I have some few seconds freeze that seems related to SSD

By looking at dmesg I observe the following
[ 900.590839] pcieport 0000:00:1d.4: AER: Corrected error received: 0000:00:1d.4 [ 900.590843] pcieport 0000:00:1d.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 900.590846] pcieport 0000:00:1d.4: device [8086:9db4] error status/mask=00000001/00002000 [ 900.590847] pcieport 0000:00:1d.4: [ 0] RxErr [ 1414.475147] nvme nvme0: I/O 83 QID 2 timeout, aborting [ 1414.491001] pcieport 0000:00:1d.4: AER: Corrected error received: 0000:00:1d.4 [ 1414.491013] pcieport 0000:00:1d.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 1414.491021] pcieport 0000:00:1d.4: device [8086:9db4] error status/mask=00000001/00002000 [ 1414.491026] pcieport 0000:00:1d.4: [ 0] RxErr [ 1414.606793] nvme nvme0: Abort status: 0x0 [ 1452.375391] pcieport 0000:00:1d.4: AER: Corrected error received: 0000:00:1d.4 [ 1452.375400] pcieport 0000:00:1d.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 1452.375405] pcieport 0000:00:1d.4: device [8086:9db4] error status/mask=00000001/00002000 [ 1452.375409] pcieport 0000:00:1d.4: [ 0] RxErr [ 1813.818228] nvme nvme0: I/O 534 QID 1 timeout, aborting [ 1813.834086] pcieport 0000:00:1d.4: AER: Corrected error received: 0000:00:1d.4 [ 1813.834099] pcieport 0000:00:1d.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 1813.834110] pcieport 0000:00:1d.4: device [8086:9db4] error status/mask=00000001/00002000 [ 1813.834117] pcieport 0000:00:1d.4: [ 0] RxErr [ 1813.949932] nvme nvme0: Abort status: 0x0

Do you observe the same issues with this SSD ?
After some search on Web I see that it could improve things to add pci=noaer option to grub but I wonder if the issue due to hardware that could have a defect or bad management by Operating System ?
 
Last edited:
H

hogfish

Bronze Level Poster
I know very little about pcie, but those sound like hardware problems. I would reseat the SSD for a start and see if that changes anything. Always suspect connector problems first with hardware.
 
Oussebon

Oussebon

Multiverse Poster
If you want to rule out hardware altogether, install a different OS on the system. e.g. image the disk with macrium reflect, install Windows, see if you get the same problem. If you don't, it's probably a Linux issue. If you do, looks like hardware. Either way you can then restore the image you made with Macrium and proceed.
 
D

drgr33n

Active member
Hey, I've just seen your post. It looks like your PC is having some trouble with something on the PCIe bus. By setting pci=noaer when booting will turn off the Advanced Error Reporting but an issue still exists and you may experience further issues with your laptop.

I'm assuming that you've got a NVME drive installed within this laptop? If so, I'd suggest you RMA the laptop as it sounds like you may have a small issue with the drive. NVME connects directly to the PCI bus and I'm guessing that IO issues are causing the AER errors. You could try another kernel as it may be that. Maybe grab a live copy of Ubuntu 19 and see if AER starts flapping. If it doesn't, you know it's a kernel issue and if it does, RMA the laptop so the drive can be tested.
 
You must log in or register to reply here.
Top