This is a longshot but maybe someone would be able to help me with this. I have a laptop that only has a single NVMe drive. I booted it up today to find "Checking media presence......." after the splash screen and then it booted into BIOS. The BIOS doesn't see the NVMe device. I don't understand how this could've happened because I didn't update anything or change any setting or physically damage or jostle the laptop between the last successful boot and clean shutdown and now. When I boot into an EndevourOS liveusb, the installer can see my entire drive and its associated partitions. I can't access them though, I think because they're encrypted, but even so I feel like I should be able to see them in the filesystem, as I've rescued files like that before (from non-encypted drives). So I can't really make heads or tails of this. If the liveusb is seeing the drive and the correct partitions, it can't possibly be physical damage to the drive itself, right? Or any of the connections? Yet BIOS can't see it for some reason and won't boot into it. If it's worth anything, the OS on it is Arch with grub as the bootloader. Obviously I've tried to reseat the drive, move it to the other available slot, I've toggled on and off all sorts of settings in the bios, and nothing makes any progress. If anyone has any ideas, I'd be grateful. Thanks!
Editting to add: I'm not entirely sure the BIOS doesn't see the device. The menu is fairly unclear. There's a series of lines starting with "NVMe Device", which the corresponding entry is just blank. Then there's two lines of "NVMe Controller", one of which has an entry that I can't select or see more of that says "SAMSUNG (5...", which makes me wonder because my NVMe drive is 512gb, and I wonder if it's listed there? But I can't see anything beyond the elipses so I can't tell. Then the other controller line just says "Empty". Not sure what to make of that.
Second edit: There's a section in BIOS for RAID disks, and in it there's a listing for "Non-RAID Physical Disks" in which my NVMe drive is listed correctly. So maybe it's a bootloader thing? I'm so confused.
Final edit: Thank you so much for the help everyone, even though I'm sure my post was a confused mess. I luckily managed to back up all my files, so it's just a matter of fixing grub or reinstalling at this point. I hate computer :)
to every fucking monster even tangentially involved with this campaign.
I don't know the answers for certain but if you'll forgive a bit of speculation: It seems that automated detection/tracking of such small targets is just simply not there yet. There are manually operated machine guns used for air defense against larger sized drones, which have some level of targeting assistance. As for some sort of Active Protection System (APS) like you're talking about with claymores, I think the detection issue is holding something like that back. Additionally, APS systems are very dangerous to nearby infantry. Apart from zionists being cowards, it's one of the reasons why so many zionist tanks were able to get
, because the Merkavas have APS systems that attempt to shoot down incoming missiles (at ranges beyond 50 meters iirc) that would likely kill a nearby infantry screening force, which kind of forces you to commit the cardinal sin of not protecting your armor with infantry. The other issue that infantry are having with drones is that shotguns with buckshot and similar ammo for other weapons have a fairly limited range. At the speed at which drones tend to close in, you only get a couple effective shots at the drone before it hits. Maybe a system like you're proposing would fair a little better, but small balls do not travel especially far with very much accuracy. Essentially, you need a long range weapon with a decently sized cone of effectiveness, which is why (again, allegedly) Russia and China looking in the realm of energy weapons, but we're still likely very far off from that. My source on that claim comes from comments made by Stanislav Krapivnik on the Duran, but I don't know how much stock to put in his claims.