I came down last night to drop some stuff off in the basement and shut the curtains, and sat down to check on something at my desktop PC, I don’t even remember what, and was slightly surprised to see that it was sitting at the BIOS Screen and not the Windows lock screen. My first assumption was, it did an update or something, and the cat was sitting on the keyboard, and cause it to enter the BIOS. They don’t usually sit on the keyboard, but it’s possible.

I rebooted the PC, and…. it just loaded the BIOS again.

Clearly something more than a cat issue.

Both the 1TB M2 NVMe drive and the 2TB add on drive were showing in the BIOS menu, but no boot options were showing available. In fact, it even specifically said something along the lines of “No boot options.” I tried resetting the BIOS settings back to factory default, I had toggled a few things so I could do virtualization, and it was no help.

I dug out a USB key with Linux and booted to that. I mostly wanted to see if I could access the drive still at all. This had to be done with an extremely weird and annoying bright yellow screen where everything was washed out. The Live OS would boot fine and look fine, until it actually got to the point of letting me do anything, when it suddenly seemed to give up it’s video driver causing everything to go wonky.

I managed to squint my way through it and the drive shows up, but it’s not accessible at all.

So I swapped out Ubuntu for a Windows Recovery USB Key. The recovery options (restore, recovery, etc) all failed. These gave a bit more information that the drive was “locked”. I tried a few more options at the command line that I found,

  • bootrec /fixMBR
  • bootrec /fixBoot
  • bootrec /rebuildBCD

But none of these changed anything. I could probably download and run a Windows ISO, but for the moment, I’ve decided on a different route. I booted back into Ubuntu, and just installed that on my 2TD spare drive. It would not take on the 1TB NVMe drive, and the 2TB secondary drive was just all games anyway, so nothing of value would be lost by wiping it clean.

I might, MIGHT just try running this way for a while, though it does have some disadvantages. Mostly, games. Almost everything I’ve been actively playing lately was through the Epic store. And a lot of the games I planned to get to in Steam, don’t work in Linux. There are ways to get them to work though, which I want to look into, but I have not had time yet. I do know Fortnite is flat out not going to work. Not a huge loss, I am kind of getting tired of it again anyway. It has some strict Anti-Cheat which won’t run in any sort of emulated environment.

I also still have my old desktop too I can use. So well, Fortnite may not be out completely, it just, won’t run quite as nice. In fact, I can probably run most of the stuff I want on that machine that won’t work directly in Ubuntu.

Another thing worth mentioning, I am not really out anything file wise. A handful of downloaded files for “TODO” projects that I could download again. I basically never work with files directly on any particular system anymore, it’s always files on the NAS or files in One Drive. The only thing I really lost were the handful of custom Stable Diffusion Embeddings I had created, and I have been meaning to try to rebuild better versions of those anyway.

It will be interesting to see how performance is compared to Windows though. This PC is a pre built gaming PC, so I am sure it’s been somewhat optimized for use with Windows. I have not had a chance to really test it out in a Linux environment at all yet, but I’m interested to see the results. I’d already been toying with the idea of running Linux on this machine but I was worried about how it would handle things like the water cooler. I already don’t have the ability to control the lights on my Keyboard and Mouse, but there may be software to do that available if I look into it.

All in all, I am irritated that the drive died, but I’ve taken it much more in stride than one might expect. I will probably poke at the Windows system some more as well though. The drive doesn’t really act like it’s dead, more like, it’s got some sort of software glitch going on.