Fixed yesterday, see update.

A large amount of tech was based by people and enterprises who emigrated from Russia and are no longer bound by their laws.

When do you expect US to have a proletarlian revolution?

They no longer need them, they are profitable by themselves now.

Yeah, already solved, check the update. Mode was set to RAID over AHCI for some reason.

Tokens are well-defined groups of bytes ranged by frequency of occurrence in texts to efficiently translate them into a sequence of 32 or 64-bit binary integers, an LLM-optimised form if compression. They are well-known, you can play with them here: https://gpt-tokenizer.dev/

Cryptozoologists are in shambles

Don’t recall doing so. I think I saw something about automatic switch to/from RAID and AHCI in boot logs?

I’ve actually seen “something/AHCI/RAID” switch in BIOS set to RAID. Will try switching to AHCI.

Edit: IT WORKED! I changed RAID to AHCI, now the system boots as expected. Thank you. Will change to solved.

I don’t think I changed anything relevant in the bios, I’m always quite careful with changing things there. Maybe I changed boot order to test live USBs a couple times. Reboots are frequent due to system crashes.

Also also, is it possible you have two disks, and grub is on one and your data is on the other? Again, kinda weird question, but it’s a kinda weird situation…

No, only one drive. I tried removing this drive, and it failed to get to GRUB. Plus, the rescue mode on Windows partition on the same drive that boots sees it’s own 200 GB of files, they are definitely can’t be anywhere but on 512 GB SSD.

It appears the time was broken, the logs were new.

Here are logs from the live USB, this link expires in 2 weeks, I will preserve it if you’ll find anything relevant there: https://termbin.com/975x

NVMe

I think I tested the SSD-out scenario without live in.

Only USB drive itself shows under by-id. I don’t have a Windows install USB, the windows I talked about is a partition on the broken disk. It does see the Linux partition with DiskPart but can’t mount it or extract files from BTRFS.

LSPCI lists many cryptic names, “RAID bus controller” sounds like the most promising one. https://termbin.com/287u

No, fdisk shows only the drive itself.

I didn’t find any obvious errors in dmesg logs, but again I don’t know much about them. You may check them out here: https://termbin.com/975x

CP2

No way it got a sequel

Don’t recall

You mean emergency console image? Yeah, that’s what I’ve been working with. Older kernels also don’t work.

For the second one, I checked by removing SSD from slot, it refused to boot to GRUB, BIOS gave an error. So it’s on SSD. Plus, Windows partition console sees all it’s files, ~200GB.

As I wrote, GRUB with all customisations and rescue modes stored on this drive for both Windows and Linux work fine, so I find it unlikely to be a connector problem. Unless such a problem may lead to part of drive working fine and the other not. When SSD is out of socket, BIOS refuses to boot at all and makes loud sounds.

I already removed the drive, contacts seemed clean. Connecting to another computer is the next thing I’m going to try.

External live OSes don’t see the drive, but some things on drive when it is operating (like GRUB) work. DiskPart on Windows partition sees all partitions.

Latest DMESG logs are several days old, I’m not sure I had this problem back then. Nothing seems to be useful there, standard USB connect/disconnect stuff.

I enabled S.M.A.R.T. in BIOS, it seems it doesn’t see an issue with the drive (PredictFailure in wmic is FALSE)

PhotoRec and TestDisk do not see the disk when booted from live media, only the 15GB drive itself and 804MB loop0.

It’s the second week of me troubleshooting mine