I've been doing a lot of poking and prodding the system over the last few days, and I think I found part of the problem and why the previous efforts haven't worked... At least I hope I'm seeing the end of the process...
The initial Debian install was done in BIOS mode, and as a result none of the UEFI information / drive partitions were on the SSD, so it would always come up in BIOS mode, and because the drive didn't have the right partition setup, it wouldn't allow the steps you suggested to put the UEFI information on the drive and fix the GRUB install... I made a rEFInd USB stick - and it wouldn't boot of that. Then I tried a rEFInd CD, and it would boot, but didn't seem able to solve the drive problem.
Unfortunately in the process of doing this I wiped out the first couple partitions on both the SSD and the NVMe drive, and didn't seem able to get them back nicely. So I ended up getting the Live system USB stick to do a re-install, in UEFI mode, on just the SSD. The system now comes up in UEFI mode, and here is the new lsblk output - note that it now has a /boot/efi partition on sda1.
Now that I have gotten the UEFI boot problem solved, I plan to try some of your earlier suggestions again, to get the system to use the NVME drive after the initial boot. Thanks again for all your help and advice.
ex-Gooserider
The initial Debian install was done in BIOS mode, and as a result none of the UEFI information / drive partitions were on the SSD, so it would always come up in BIOS mode, and because the drive didn't have the right partition setup, it wouldn't allow the steps you suggested to put the UEFI information on the drive and fix the GRUB install... I made a rEFInd USB stick - and it wouldn't boot of that. Then I tried a rEFInd CD, and it would boot, but didn't seem able to solve the drive problem.
Unfortunately in the process of doing this I wiped out the first couple partitions on both the SSD and the NVMe drive, and didn't seem able to get them back nicely. So I ended up getting the Live system USB stick to do a re-install, in UEFI mode, on just the SSD. The system now comes up in UEFI mode, and here is the new lsblk output - note that it now has a /boot/efi partition on sda1.
Code:
[ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD"EFI boot on HDDlsblk -fNAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTSsda├─sda1 vfat FAT32 D102-EF8B 493.1M 1% /boot/efi├─sda2 ext2 1.0 12b619f8-905e-423a-94f9-60275e79a662 362.7M 23% /boot├─sda3 ext4 1.0 41fd5d38-d92d-42aa-8397-6b799fd2c8a5 30.3G 15% /├─sda4 ext4 1.0 21965877-d556-4549-881f-2e7376ad7fad 9.3G 0% /tmp├─sda5 ext4 1.0 d1907436-29c1-4492-af5c-dce0e406b537 4.5G 9% /var├─sda6 ext4 1.0 SSD-HOME c65b8967-ed09-423a-b6cc-9775dfc85828 223G 59% /home└─sda7 ext4 1.0 844be5ea-cabd-428d-9e17-4b999eccd917 9G 0% /usr/localsdb├─sdb1 ntfs Win10 54CFFDF62E1AE6AC└─sdb2 swap 1 ae87123a-5ed7-4b58-880c-e6ac7778456d [SWAP]sdc├─sdc1 ext2 1.0 old-BOOT 8e660124-c9f7-4a7f-b23d-3c1329d2c09b├─sdc3 ext4 1.0 old-ROOT 1f996152-b19e-49ab-9614-2fd81d5f289d├─sdc4 ext4 1.0 old-VAR fb1851c6-feac-46fd-977a-d3c6ef582629├─sdc5 ext4 1.0 old-VAR-MAIL 7e88d9b1-eba3-4bd3-bf4e-92c9871a8946├─sdc6 ext4 1.0 old-TMP c33a5cb7-dda4-4807-bb3d-dc56acb68864└─sdc7 ext4 1.0 old-HOME 733320af-925c-4226-ad57-a74b29f589c0sdd└─sdd1 ext4 1.0 music 898a5610-cbe3-4ee3-a7ba-2d475353cf4fsde└─sde1 ext4 1.0 /dev/sde e800cb22-d170-4868-a332-cc044df93202sdfsdgsdhsdisr0nvme0n1├─nvme0n1p3 ext4 1.0 nvme-root 41e382ca-bdd5-447d-b716-03323c13d44e├─nvme0n1p4 ext4 1.0 nvme-temp 9a3b2e91-ace0-4a91-a761-1dffde4ef7b4├─nvme0n1p5 ext4 1.0 nvme-var d2636e2a-f119-43d1-bc28-639f12f27388├─nvme0n1p6 ext4 1.0 nvme-HOME b800c322-1156-492e-b270-2a6096291121└─nvme0n1p7 ext4 1.0 nvme-usr-local db44152e-9c5a-46b5-8d0c-4b5b61a35058ex-Gooserider
Statistics: Posted by ex-Gooserider — 2024-04-22 20:48 — Replies 17 — Views 646