So I've been fighting what appears to be after 5 years, a faulty bios rootkit that is infecting my low-level firmware on USB drives, hard drives, boot roms, motherboard option roms, etc. I have spent more than $ 20,000 in the last 5 years after trying to save my data and remove this strange science from my computer. Burned through hard drives that instantly begin to fail and get corrupted as soon as I connect them to any infected device. Without going into a whole stupid paranoid history of errors, I suppose I will start with the basic questions about certain partition maps that cannot be erased in all my units.
Ideally, what I would like to be able to do is insert a disk drive or USB drive into my computer, set it to zero with the dd command and have it completely erased, to ensure a good map and clean partition format. However, this has proved unusually difficult, as it seems that I can never completely erase all my partition maps. And when it seems that I do, eventually, random phantom partitions come back and start corrupting my hard drives again, seemingly swapping drives at will of hybrid disk partitions, to gpt & # 39; s complete with pmbr & # 39; s, and then to ntfs or fat12-16-32 of mbr This demon must be understood so that I can keep my data from eating constantly alive.
To begin with, a specific example with which I need help is in relation to the USB drive shown in the following image.
Ideally, before partitioning and formatting, I would like to be sure that any MBR or GPT partition map is out of the way.
So in the mac os terminal, I start with a USB key that strangely has two MBR partition maps. One at the beginning of the drive, and one at the end, almost as if trying to act as a gpt disk with a backup header at the end of the disk.
I enter the gpt show / dev / diskxy command
which returns two master boot records under the content tag. One is labeled as a regular "MBR", and the other is labeled as "MBR Part 11".
Partition map photo link 1 (sudo gpt show reveals 2 master boot records)
1) My first question is obvious: what is the second master boot record doing there? Since when are master boot records divided into parts?
Then I run the gpt destroy / dev / diskxy command on the USB drive. However, it destroys (temporarily) the MBR at the end of the disk, the MBR quickly reappears and the MBR at the beginning (sector 1 to 1) of the disk simply remains and is not deleted. Then I proceed to use fdisk to delete the MBR, executing the sudo fdisk -e / dev / diskxy command, then typing delete, and saving and exiting. Fdisk looks like the maps are deleted. However, after disconnecting and reconnecting the unit, gpt show once again shows the additional MBR labeled "Part 11". Gdisk is having the same problems. I can't seem to erase persistently persistent partition maps completely. Can someone help me, please find out how to make all my disks clean the gpt partition maps that do not fluctuate between segmented bits of MBR (I have seen that the content type goes up to "MBR Part 3846273820" before). It seems that something is constantly creating persistent MBRs in all my units to represent some kind of marker points or something like that, almost as if my units were just small pieces of a massive raid server. Could someone with knowledge in partition maps (Rod Smith) in mac os, please explain some of this and help me find external answers? It could be much appreciated!
See more photos attached below. Sorry for the imgur links. I don't have enough points to post photos yet.
Undestroyable Partition maps Mac OS
link @ https://imgur.com/gallery/Phj0cc1
Persistent MBR (in parts) and GPT Partition Maps link @ https://imgur.com/gallery/DbYbHSR
Fdisk partition maps cannot be destroyed on link @ https://imgur.com/gallery/PZdKwaj