Solved Latitude 5490, NVMe conversion

[Brickwizard]

As most of you know I do not usually suffer hardware problems I can't fix myself, this has me flummoxed below my post on the dell support site [but I do not expect an answer as the machine is out of warranty.​

So my latitude came with a slow old 2.5 inch SSD, I decided as I had a NVMe M2 2280 in stock I would do the upgrade, I purchased the required mounting bracket, and proceeded, I removed the SSD [with its adaptor and cable] and mounted the NVMe,
I then inserted a USB into the primary [rear] USB port and proceeded to install a new OS., after which I tried to boot it, boot fails with a couple of PXE errors, so as its not required for NVMe's I disabled PXE in the bios, still it would not boot.
Checking in the bios/UEFI It can see the NVMe and i have it ticked to enable [I have also unticked all the SSD'd] and it still didnt boot, so I got my Linux rescue usb and booted that [no problem] and interrogated the NVMe, it shows all the files and folder for the new OS in place,
Desperation set in, I went back to the bios/EUFI and re-st to factory defaults,
The NVMe will still not boot, and constructive suggestions Please

 

[Brickwizard]

I am getting nothing, when i did the first installation I got the PXE errors, so I turned PXE off,I have tried with secure boot both enabled and disabled the NVMe is showing in the UEFI, it also shows on the short boot menu but will not actually boot, I have tried LMDE,MX,Parrot home ,& a couple of others, same results from all, so I booted a mint 21 external drive [no problem] and had a look at the NVMe, its showing all the right partitions and files, I can only think its something stupid that i just cant fathom.

 

[Aristarchus]

Maybe use gparted to see if new hardware is revognized as bootable
If disk does not boot, you should see a message from BIOS (or boot loader) why.
Your OS (kernel?) may be somehow at fault. Maybe try something completely different.
Finally, for whatever reason nvme may actually not work with your laptop.
One solution is booting from usb (as in secure boot where booting from usb is set by design). If you can boot up from usb maybe this will help diagnose the issue.

 

[osprey]

As most of you know I do not usually suffer hardware problems I can't fix myself, this has me flummoxed below my post on the dell support site [but I do not expect an answer as the machine is out of warranty.​

So my latitude came with a slow old 2.5 inch SSD, I decided as I had a NVMe M2 2280 in stock I would do the upgrade, I purchased the required mounting bracket, and proceeded, I removed the SSD [with its adaptor and cable] and mounted the NVMe,
I then inserted a USB into the primary [rear] USB port and proceeded to install a new OS., after which I tried to boot it, boot fails with a couple of PXE errors, so as its not required for NVMe's I disabled PXE in the bios, still it would not boot.
Checking in the bios/UEFI It can see the NVMe and i have it ticked to enable [I have also unticked all the SSD'd] and it still didnt boot, so I got my Linux rescue usb and booted that [no problem] and interrogated the NVMe, it shows all the files and folder for the new OS in place,
Desperation set in, I went back to the bios/EUFI and re-st to factory defaults,
The NVMe will still not boot, and constructive suggestions Please

If the rescue disk booted, then some investigation may be possible with a command from the nvme suite of commands if the package: nvme-cli, is installed on the rescue disk.

In particular, nvme can access its error log with a command, as root, like:

nvme error-log /dev/nvme0n1 -v

where the device name is from your machine. The device name is determinable from the output of the command: lsblk.

If you run the following command and hit the tab key, and then display all the possibilities, the output should show a list of "sub-commands" and plug-in extensions associated with different vendors, some of which may be of interest in gathering info.

nvme <TAB>

To find all the nvme commands available see: man nvme, which refers to the other manpages for the command details.

The output of the error log may be a bit cryptic, so I guess researching any suspicious output online would be the way to go. Since there haven't been any issues here with nvme, I haven't needed to do any such research, so can't help there.

EDIT: Another source of info which may be of interest is in the logs of the installation itself which are usually stored in the directory: /var/log/installer. If, for example, there's a syslog file there, it can be viewed for errors on the off chance that something is revealing.

 

[Brickwizard]

Switched it off for a couple of hours, tried playing with settings again, tried re-installing, this time with grub in a seperate partition, and all i still get is boot media not found, pressF2 to change settings, F5 for self diagnostics, F10 to shut down

 

[kc1di]

I'm not that familar with NVME drives but have seen several comments on different forums that seem to indicate some problems in boot with them.
1st one , said they solved it by making sure AHCI was set in bios.
2nd one, Said you need to modify the following file (it was on Fedora so not sure it will apply here)

Fixing NVME SSD Problems On Linux – Tekbyte

Hope this may be of help.

 

[dos2unix]

I have three systems with NVME drives. I never have to do anything special to make them work.
No special drivers, no special formatting. I do use GPT partitioning.

root@devNUC1:~# fdisk -l
Disk /dev/nvme0n1: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: INTEL SSDPEKKR256G8
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8330A4F0-E6BB-4704-9C29-04885739E053

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 759807 757760 370M EFI System
/dev/nvme0n1p2 759808 7051263 6291456 3G Linux filesystem
/dev/nvme0n1p3 7051264 495695871 488644608 233G Linux LVM

[root@NBG_EX15_GETD ~]# fdisk -l
Disk /dev/nvme0n1: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 09A0425F-2853-45FA-AB17-9D096F9C58E1

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 3907028991 3907026944 1.8T Linux filesystem

root@dellXPS:~# fdisk -l
Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: PC711 NVMe SK hynix 512GB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 1DDA74C2-21FE-4683-8A35-16F1879017E5

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 555007 552960 270M EFI System
/dev/nvme0n1p2 555008 6426623 5871616 2.8G Linux extended boot
/dev/nvme0n1p3 6426624 987910143 981483520 468G Linux LVM

All of these boot fine from the nvme drives. I don't do anything different from normal SSD drives.
The drivers are in the kernel, so the disk type should be transparent to the OS and user.

 

[Brickwizard]

I never have to do anything special to make them work.

neither have I up to now [apart from adding them as second boot in the UEFI]

 

[Brickwizard]

OK Update..A Glimmer of light at the end of the tunnel. I can now boot in using the short boot menu, no problems [I had been juggling some BIOS settings] BUT when you switch on normally, I still get no boot media found
[when i was booted in from short boot menu, I did run update grub, but it made no difference

 

[osprey]

OK Update..A Glimmer of light at the end of the tunnel. I can now boot in using the short boot menu, no problems [I had been juggling some BIOS settings] BUT when you switch on normally, I still get no boot media found
[when i was booted in from short boot menu, I did run update grub, but it made no difference

Perhaps consider upgrading the BIOS/UEFI if the machine is not on the latest.

 

[Brickwizard]

dmesg | grep nvm

brian@Deep-thought:~$ dmesg | grep nvm
[ 2.350803] nvme nvme0: pci function 0000:03:00.0
[ 2.378188] nvme nvme0: allocated 61 MiB host memory buffer.
[ 2.529927] nvme nvme0: 8/0/0 default/read/poll queues
[ 2.533811] nvme0n1: p1 p2 p3
[ 4.735423] EXT4-fs (nvme0n1p3): mounted filesystem with ordered data mode. Quota mode: none.
[ 5.143157] EXT4-fs (nvme0n1p3): re-mounted. Quota mode: none.
[ 5.406020] Adding 8593404k swap on /dev/nvme0n1p2. Priority:-2 extents:1 across:8593404k SSFS
[ 648.309347] nvme 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 648.309349] nvme 0000:03:00.0: device [1e0f:0001] error status/mask=00000001/00002000
[ 648.309352] nvme 0000:03:00.0: [ 0] RxErr (First)
[ 841.821948] nvme 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 841.821959] nvme 0000:03:00.0: device [1e0f:0001] error status/mask=00000001/00002000
[ 841.821972] nvme 0000:03:00.0: [ 0] RxErr

 

[Brickwizard]

brian@Deep-thought:~$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
00:1c.2 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC Controller/eSPI Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-LM (rev 21)
01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)
02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
03:00.0 Non-Volatile memory controller: KIOXIA Corporation NVMe SSD Controller BG4

 

[f33dm3bits]

[ 648.309349] nvme 0000:03:00.0: device [1e0f:0001] error status/mask=00000001/00002000

That doesn't seem like a nice thing to see.

When looking it up online there are mentions of it being a possibility of faulty hardware or a bad connection with the nvme to the motherboard.

I purchased the required mounting bracket, and proceeded, I removed the SSD [with its adaptor and cable] and mounted the NVMe,

First I would update to the most recent motherboard firmware if you haven't already done so, then see what happens. If that doesn't solve it I I would look into testing the nvme drive in another system that doesn't have the need for a mounting bracket to see what happens then. I think it would help to rule out a faulty nvme drive if it does work in another system without a mounting bracket.

 

[Brickwizard]

First I would update to the most recent motherboard firmware if you haven't already done so

That was done before I bought it [fully refurbished]

I would look into testing the nvme drive in another system that doesn't have the need for a mounting bracket

do not have another machine, however I know its working as it now boots from the short boot menu [I was Messing with bios/UEFI settings, I dont know which did it ]
been sitting here since 4-30 am playing with the settings one at a time and not made any difference
I, too, have been scouring the net [now this means nothing to me] on a couple of sites they say add pcie_aspm=off yet on other sites they say making this change causes overheating! Your thoughts, please ?
When i boot it via the short boot, it seems like grease lightning, I didn't get the top end NVMe for speed, but an upper middle so about 10x faster than the basic SSD it came with

 

[f33dm3bits]

however I know its working as it now boots from the short boot menu [I was Messing with bios/UEFI settings, I dont know which did it ]

So it's working now?

on a couple of sites they say add pcie_aspm=off yet on other sites they say making this change causes overheating! Your thoughts, please ?
When i boot it via the short boot, it seems like grease lightning,

I found the following.

• pcie_aspm=off disables ASPM

If the hardware supports ASPM, the operating system enables ASPM automatically at boot time. To check the ASPM support, see the output of the following command:
~]$ journalctl -b | grep ASPM

Warning:
If you forcibly enable ASPM by using pcie_aspm=force on hardware that does not support ASPM, the system might become unresponsive. Before setting pcie_aspm=force, ensure that all PCIe hardware on the system supports ASPM.

Source: aspm

 

[Brickwizard]

So it's working now?

Only by using the short boot [F12] menu
I tried editing Grub, but it didn't like it, what grub editor do you use?

brian@the-answer-42:~$ journalctl -b | grep ASPM
Nov 04 07:21:09 the-answer-42 kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it


well that seems conclusive

 

[dos2unix]

I typically disable all power management in the BIOS/UEFI.
I leave my desktop systems on all the time. I let the OS handle the power management on the laptops.

 

[f33dm3bits]

Only by using the short boot [F12] menu
I tried editing Grub, but it didn't like it, what grub editor do you use?

Do you mean that by pressing f12, you get a device where you want to boot from and then select your nvme drive or do you mean something else? I don't use a grub editor, I edit the /etc/default/grub with vim if I need to change something if you mean that?

 

[Brickwizard]

Do you mean that by pressing f12, you get a device where you want to boot from and then select your nvme drive or

YES

I don't use a grub editor, I edit the /etc/default/grub with vim

will give it a go,

in over 20 yrs I can't ever remember having to edit Grub

 

[f33dm3bits]

YES

What happens when you do that, cause from what I know that's only selecting your boot device after which you should get a bootloader/Grub to boot your system from? Do also get a Grub menu then without getting a Grub rescue?