I wasn't sure if the formatting would cause issues. Here is output with the formatting removed:
log.txt -- output from inxi -Faz
log1.txt -- output from sudo parted -l ; lsblk -f ; mokutil --sb-state; inxi -Fxxxrz
Debian fails to boot on NVMe M.2 disk after UEFI install
Re: Debian fails to boot on NVMe M.2 disk after UEFI install
somebody mentioned inxi -Faz might be too verbose, so here's inxi -Fxxxxz
- Attachments
-
log2.txt
- (3.28 KiB) Downloaded 19 times
Re: Debian fails to boot on NVMe M.2 disk after UEFI install
Here ismrmazda wrote: 2024-05-14 15:11Inxi's default rainbow effect isn't advantageous, but instead annoying, to some users. It can be disabled by adjusting its config file as I do:fabien wrote: 2024-05-14 12:00I agree that a simple redirect is often sufficient, depending on what you want to achieve. Highlighted text also has its advantages (for human vision I mean).-Faz dumps pretty much everything about hardware and much about software, so includes a lot of noise WRT can't find root filesystem issues. It's man page offers more specific, less noisy options, e.g.:Code: Select all
> grep -i color /etc/inxi.conf GLOBAL_COLOR_SCHEME=0 >
For this OP's problem, the following might be useful, possibly more so:Code: Select all
# inxi -Mdpoaz Machine: Type: Desktop System: Gigabyte product: B250M-D3H v: N/A serial: N/A Mobo: Gigabyte model: B250M-D3H-CF v: x.x serial: N/A uuid: 031b021c-040d-0557-ad06-5d0700080009 UEFI-[Legacy]: American Megatrends v: F10 date: 12/14/2018 Drives: Local Storage: total: raw: 1.94 TiB usable: 1.03 TiB used: 795.14 GiB (75.0%) ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: ZTC model: PCIEG3-128G size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: R0629A0 temp: 51.9 C scheme: MBR SMART: yes health: PASSED on: 4 hrs cycles: 526 read-units: 2,494,087 [1.27 TB] written-units: 1,669,622 [854 GB] ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000NM0011 family: Constellation ES (SATA 6Gb/s) size: 931.51 GiB block-size: physical: 512 B logical: 512 B sata: 3.0 speed: 6.0 Gb/s tech: HDD rpm: 7202 serial: <filter> fw-rev: SN02 temp: 34 C scheme: GPT SMART: yes state: enabled health: PASSED on: 1y 262d 2h cycles: 54 Pre-Fail: attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97 ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST1000DM003-1CH162 family: Barracuda 7200.14 (AF) size: 931.51 GiB block-size: physical: 4096 B logical: 512 B sata: 3.1 speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter> fw-rev: CC49 temp: 33 C scheme: GPT SMART: yes state: enabled health: PASSED on: 3y 38d 8h cycles: 74 read: 244.01 TiB written: 6.59 TiB Pre-Fail: attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97 Optical-1: /dev/sr0 vendor: ASUS model: DRW-24B1ST j rev: 1.11 dev-links: cdrom,dvd Features: speed: 125 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r state: running Partition: ID-1: / raw-size: 17.58 GiB size: 17.27 GiB (98.25%) used: 4.79 GiB (27.7%) fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p10 maj-min: 259:10 ID-2: /disks/boot raw-size: 1.17 GiB size: 1.16 GiB (99.06%) used: 694.5 MiB (58.4%) fs: ext2 block-size: 4096 B dev: /dev/nvme0n1p3 maj-min: 259:3 ID-3: /home raw-size: 70.31 GiB size: 69.7 GiB (99.14%) used: 40.69 GiB (58.4%) fs: ext4 block-size: 1024 B dev: /dev/md3 maj-min: 9:3 ID-4: /isos raw-size: 625 GiB size: 619.88 GiB (99.18%) used: 578.4 GiB (93.3%) fs: ext4 block-size: 4096 B dev: /dev/md5 maj-min: 9:5 ID-5: /pub raw-size: 207.03 GiB size: 205.31 GiB (99.17%) used: 165.95 GiB (80.8%) fs: ext4 block-size: 1024 B dev: /dev/md4 maj-min: 9:4 ID-6: /<redact>/E raw-size: N/A size: 250.7 MiB used: 208.2 MiB (83.1%) fs: cifs dev: /dev/E ID-7: /<redact>/G raw-size: N/A size: 1.95 GiB used: 1.91 GiB (97.5%) fs: cifs dev: /dev/G ID-8: /<redact>/I raw-size: N/A size: 2.44 GiB used: 2.04 GiB (83.5%) fs: cifs dev: /dev/I ID-9: /<redact>/J raw-size: N/A size: 58.59 GiB used: 44.23 GiB (75.5%) fs: cifs dev: /dev/J ID-10: /srv raw-size: 7.81 GiB size: 7.71 GiB (98.74%) used: 1.75 GiB (22.6%) fs: ext4 block-size: 1024 B dev: /dev/md2 maj-min: 9:2 ID-11: /usr/local raw-size: 3.91 GiB size: 3.84 GiB (98.31%) used: 2.88 GiB (75.1%) fs: ext4 block-size: 1024 B dev: /dev/md1 maj-min: 9:1 Unmounted: ID-1: /dev/nvme0n1p1 maj-min: 259:1 size: 251 MiB fs: vfat ID-2: /dev/nvme0n1p11 maj-min: 259:11 size: 17.58 GiB fs: ext4 ID-3: /dev/nvme0n1p2 maj-min: 259:2 size: 2.34 GiB fs: hpfs ID-4: /dev/nvme0n1p4 maj-min: 259:4 size: 1 KiB fs: N/A ID-5: /dev/nvme0n1p5 maj-min: 259:5 size: 16.23 GiB fs: swap ID-6: /dev/nvme0n1p6 maj-min: 259:6 size: 3.91 GiB fs: ext3 ID-7: /dev/nvme0n1p7 maj-min: 259:7 size: 17.58 GiB fs: ext4 ID-8: /dev/nvme0n1p8 maj-min: 259:8 size: 17.58 GiB fs: ext4 ID-9: /dev/nvme0n1p9 maj-min: 259:9 size: 17.58 GiB fs: ext4 ID-10: /dev/sda1 maj-min: 8:1 size: 400 MiB fs: N/A ID-11: /dev/sda2 maj-min: 8:2 size: 320 MiB fs: N/A ID-12: /dev/sda3 maj-min: 8:3 size: 320 MiB fs: N/A ID-13: /dev/sda4 maj-min: 8:4 size: 8.01 GiB fs: N/A ID-14: /dev/sdb1 maj-min: 8:17 size: 400 MiB fs: N/A ID-15: /dev/sdb2 maj-min: 8:18 size: 320 MiB fs: N/A ID-16: /dev/sdb3 maj-min: 8:19 size: 320 MiB fs: N/A ID-17: /dev/sdb4 maj-min: 8:20 size: 8.01 GiB fs: N/A #
Code: Select all
efibootmgr -v parted -l lsblk -f cat /etc/fstab # (or wherever fstab may be temporarily mounted for troubleshooting)
efibootmgr -v
parted -l
lsblk -f
cat /etc/fstab
- Attachments
-
log3.txt
- (1.6 KiB) Downloaded 28 times
Re: Debian fails to boot on NVMe M.2 disk after UEFI install
For what ever it is worth, I do not see the Samsung 990 Pro listed on the ASUS site as being compatible with your motherboard.
ASUS B550-Plus
There is also a new bios release for 3 April.
This may be of use to you.
NVME not seen
ASUS B550-Plus
There is also a new bios release for 3 April.
This may be of use to you.
NVME not seen
Re: Debian fails to boot on NVMe M.2 disk after UEFI install
Sorry, been a little under the weather the past few days. Thanks for those links. I do see that there are exactly zero 4TB M.2 NVMe Samsung SSDs on that compatibility list, in spite of the fact that at least one of the models listed appears to have a 4TB version. I plan to try with a 2TB SSD. If that works, I'll think about purchasing a second 1TB or 2 TB drive to add.Augie77 wrote: 2024-05-15 18:06 For what ever it is worth, I do not see the Samsung 990 Pro listed on the ASUS site as being compatible with your motherboard.
ASUS B550-Plus
There is also a new bios release for 3 April.
This may be of use to you.
NVME not seen
Re: Debian fails to boot on NVMe M.2 disk after UEFI install
Not a problem, hope you are feeling better.
The web is loaded with reports of the 990 Pro not working well with Asus boards, the B550 Plus stands out among them. I have seen various suggestions, one is to disable Intel Rapid Storage, one was to disable CSM and TPM/Secure Boot. Mostly saw reports for Windows users.
The issue is not the memory size so much as it is the 990 Pro itself, meaning SPD and other onboard chip management goodies. The Sam 980 seems to fare better and of course, the earlier models work as intended. I would at least update the BIOS and make certain the 990 is in the M2-1 slot. Generally, that is the NVME boot slot. The manual makes no mention of what are bootable slots and no mention of memory size limit for the NVME.
I would take a good look at the second link I previously posted and perhaps ask for help on the AUSU forum site.
The web is loaded with reports of the 990 Pro not working well with Asus boards, the B550 Plus stands out among them. I have seen various suggestions, one is to disable Intel Rapid Storage, one was to disable CSM and TPM/Secure Boot. Mostly saw reports for Windows users.
The issue is not the memory size so much as it is the 990 Pro itself, meaning SPD and other onboard chip management goodies. The Sam 980 seems to fare better and of course, the earlier models work as intended. I would at least update the BIOS and make certain the 990 is in the M2-1 slot. Generally, that is the NVME boot slot. The manual makes no mention of what are bootable slots and no mention of memory size limit for the NVME.
I would take a good look at the second link I previously posted and perhaps ask for help on the AUSU forum site.
Re: Debian fails to boot on NVMe M.2 disk after UEFI install
That file failed to include most information I was seeking. Only the efigbootmgr output had any value, as the rest all came from the installation media. All requested information is needed from the NVME device. Unless and until the NVME can be recognized by something, just like booting NVME, it's not possible.
Copy from log3.txt:
Code: Select all
$ efibootmgr.-v
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001
Boot0000* Windows Boot Manager HD(1,GPT,93e39770-9a62-458a-b6b2-3171354374d0,0x800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................
Boot0001* UEFI OS HD(2,MBR,0xc7e6ef99,0x1b5c,0x2800)/File(\EFI\BOOT\BOOTX64.EFI)..BO
$
Only one ESP is required per PC. The absence of a Debian entry in efibootmgr output implies the Debian installation must have created its own ESP on the NVME.
Has any attempt to boot Debian/NVME been made via UEFI BIOS priority itself, or the UEFI BIOS' BBS hotkey F8 during POST, with and/or without CSM enabled?
My ASUS B560 BIOS has a "Next Boot Recovery Action" option at the bottom of the list that is longer than fits the opened "Boot Configuration" selection screen at once. Have you attempted a similar selection? Do you have or have you tried "Fast Boot" on this screen set to disabled? Does that screen have a NVME driver support selection that you have tried altering (mine has "AMI Native NVMe Driver Support" enabled)? What do you have "Boot Sector (MBR/GPT) Recovery Policy" set to (assuming you have the same thing; I have "Local User Control")?
If you disconnect the SATA drive and remove all USB storage, what happens when you try to boot, both using and not striking F8 during POST?
Re: Debian fails to boot on NVMe M.2 disk after UEFI install
To close this out, I was nearing the end of the return window for the 990 Pro, so I returned it and got a 2TB 970 EVO M.2 SSD instead. Took me a few days to get around to installing it, after I realized that I had accidentally returned the screws and risers that came with my motherboard in the SSD box, thinking they'd come with the SSD. The 970 also didn't have an option that included a heatsink, so I ordered one of those as well. The computer has now been running for several days on a Debian install with the 970 and I haven't noticed any issues yet.