TL/DR: one of my drives "disappeared" until a full shut down and re-power up.
I still have no idea what happened, but in the middle of normal usage (a couple browsers open, kate, Libreoffice Calc) the console stop taking commands. It gave me weird errors about "not responding" even to simple "cat" commands and wouldn't let me save any files. One of the browsers froze completely and wouldn't even close. I gave up thinking it would recover itself and started closing what I could and eventually just pressed the reset button.
On restart, it did not boot to my install. Instead, it apparently booted to a different drive (I have 6) and then Kubuntu 24.04 booted up.
To explain why the above happened: I currently have 4 distros installed to a single BTRFS file system: Ubuntu server (which acts as a stand-alone GRUB install), KDEneon (twice - one my "daily driver", the other a new install waiting for the re-base to 24.04) and Kubuntu 24.04. The "normal" boot sequence (if you can call it that, lol) is my system boots to the 2nd NVME drive and boots Ubuntu-server GRUB. That grub menu is set to default to KDEneon after a 5 second delay, which then loads the KDEneon grub menu. The "good" news was since Kubuntu and KDEneon are on the same drive and file system, I knew at least the file system was intact.
The reason Kubuntu booted up when a different drive was booted is - due to the sort of complicated set up outlined above - when I install a new distro to my system, I install the bootloader to a different drive to keep my dedicated GRUB install as my primary boot distro.
So I rebooted again and entered BIOS to see why it was booting to a different drive. My heart skipped a beat when the NVME drive I wanted to boot to was not in the bios list! The BIOS defaulted to the first drive to boot from. Not that I don't have backups, but I didn't want to go through that this morning. After a few seconds I realized I was still able to access the second drive - obviously - because that where Kubuntu is installed. So I powered down, waited a tic, then powered back on into BIOS and NVME drive #2 was back in the list.
At this point I have NO IDEA if it was a hardware or software glitch. KDEneon stopped logging at 9:41 and I didn't get it all sorted out and back into booting to KDEneon until 11:20. The first boot into Kubuntu was at 10:41 so whatever was happening to KDEneon and/or the drive lasted an hour before I mashed the reset button.
It seems very odd the the install itself could have somehow removed the drive from the boot order, but I'm still clueless about what actually happened. The drive itself shows no errors that I can find, but it seems the most likely candidate for causing this is the drive itself.
Right now, I'm refreshing backups.
I still have no idea what happened, but in the middle of normal usage (a couple browsers open, kate, Libreoffice Calc) the console stop taking commands. It gave me weird errors about "not responding" even to simple "cat" commands and wouldn't let me save any files. One of the browsers froze completely and wouldn't even close. I gave up thinking it would recover itself and started closing what I could and eventually just pressed the reset button.
On restart, it did not boot to my install. Instead, it apparently booted to a different drive (I have 6) and then Kubuntu 24.04 booted up.
To explain why the above happened: I currently have 4 distros installed to a single BTRFS file system: Ubuntu server (which acts as a stand-alone GRUB install), KDEneon (twice - one my "daily driver", the other a new install waiting for the re-base to 24.04) and Kubuntu 24.04. The "normal" boot sequence (if you can call it that, lol) is my system boots to the 2nd NVME drive and boots Ubuntu-server GRUB. That grub menu is set to default to KDEneon after a 5 second delay, which then loads the KDEneon grub menu. The "good" news was since Kubuntu and KDEneon are on the same drive and file system, I knew at least the file system was intact.
The reason Kubuntu booted up when a different drive was booted is - due to the sort of complicated set up outlined above - when I install a new distro to my system, I install the bootloader to a different drive to keep my dedicated GRUB install as my primary boot distro.
So I rebooted again and entered BIOS to see why it was booting to a different drive. My heart skipped a beat when the NVME drive I wanted to boot to was not in the bios list! The BIOS defaulted to the first drive to boot from. Not that I don't have backups, but I didn't want to go through that this morning. After a few seconds I realized I was still able to access the second drive - obviously - because that where Kubuntu is installed. So I powered down, waited a tic, then powered back on into BIOS and NVME drive #2 was back in the list.
At this point I have NO IDEA if it was a hardware or software glitch. KDEneon stopped logging at 9:41 and I didn't get it all sorted out and back into booting to KDEneon until 11:20. The first boot into Kubuntu was at 10:41 so whatever was happening to KDEneon and/or the drive lasted an hour before I mashed the reset button.
It seems very odd the the install itself could have somehow removed the drive from the boot order, but I'm still clueless about what actually happened. The drive itself shows no errors that I can find, but it seems the most likely candidate for causing this is the drive itself.
Right now, I'm refreshing backups.
Comment