Troubleshooting log

gistfile1.txt

2020-12-30.14.49
just cleared cmos, havent started working yet today. weirdly... my efi partition was at /dev/nvme2n1p1 this time. Pre-clear it was at /dev/nvme0n1p1. Huh?
edit time:9
efi md5: 58510b1a4fbcf5453354b61aba922994  -

2020-12-30.14.56
Rebooted, running again. efi partition is back at /dev/nvme0n1p1. Weird?
edit time:41
efi md5: 58510b1a4fbcf5453354b61aba922994  -

2020-12-30.15.07
That was weird, so Im trying it again. First attempt to boot debian after clearing cmos fails (reboots without prompt), second attempt succeeds. Puts EFI partition at /dev/nvme2n1p1.
edit time:41
efi md5: 58510b1a4fbcf5453354b61aba922994  -

2020-12-30.15.14
Rebooted, running again. This time the EFI partition is still at /dev/nvme2n1p1. One difference is that the last time I tried this I failed to press F11 to catch the reboot after the failure--so it booted into windows and I had reboot from the windows login screen--there was no indication that updates were installed--could the mere act of booting into windows be altering something?
edit time:10
efi md5: 58510b1a4fbcf5453354b61aba922994  -

2020-12-30.15.19
Rebooted again, again with the F11 vigilance to make sure windows never loads. EFI partition is still in /dev/nvme2n1p1.
edit time:9
efi md5: 58510b1a4fbcf5453354b61aba922994  -

2020-12-30.15.28
Rebooted again, but this time I let it boot to Windows. Missed F11 on the reboot, so I actually booted windows twice in this case. Upon making it back to linux the EFI partition is at /dev/nvme0n1p1
edit time:10
efi md5: 3cedd3283a17d03a2c5dc7dc1f461780  -

2020-12-30.15.35
Rebooted without going into Windows, EFI partition is back at /dev/nvme2n1p1
edit time:10
efi md5: 3cedd3283a17d03a2c5dc7dc1f461780  -

2020-12-30.15.42
Powered off and then back on straight into linux. Efi partition found at /dev/nvme1n1p1
edit time:41
efi md5: 3cedd3283a17d03a2c5dc7dc1f461780  -

2020-12-30.15.47
Powered off and then to the windows login screen, rebooted from there. Efi partition still found at /dev/nvme1n1p1
edit time:10
efi md5: 4f5160de2e84013527f84f736e6b4878  -

2020-12-30.15.54
Powered off and then to the windows, logged in, then rebooted from the desktop. This time the efi partition was at /dev/nvme0n1p1.
edit time:9
efi md5: 12f580427e2b4abbf8d4608fe6b73bec  -

2020-12-30.16.05
Powered off and then straight into linux, EFI partition was still /dev/nvme0n1p1
edit time:41
efi md5: 12f580427e2b4abbf8d4608fe6b73bec  -

2020-12-30.16.14
Powered off and then straight into linux, if my current theory is correct, this will be one of the slower runs
edit time:41
efi md5: 12f580427e2b4abbf8d4608fe6b73bec  -

2020-12-30.16.23
Powered off, then to windows, then rebooted to linux. I think that my video card drivers are "remembering" something from Windows on a reboot that they forget if I power off and boot up later. Also, having booted into Windows changed the EFI partition to /dev/nvme1n1p1
edit time:9
efi md5: 1e3e8758af254a501b6af7ecfefd6da6  -

2020-12-30.16.45
Installed the proprietary nvidia drivers, then powered off, then back into linux. Many other things are now broken, but lets see about this problem...
edit time:41
efi md5: 1e3e8758af254a501b6af7ecfefd6da6  -

2020-12-30.16.56
Rebooted without going into Windows, EFI partition remains at /dev/nvme2n1p1.
edit time:9
efi md5: 1e3e8758af254a501b6af7ecfefd6da6  -

2020-12-30.17.05
Powered off, then to windows, then rebooted to linux. The last run was fast despite having been powered off between windows and linux, it looks like I had to install the proprietary drivers, reboot, and then reboot _a second time_. wtf nvidia.
edit time:9
efi md5: dc6f66543c538f5998d92cd98c9eaf62  -