You're lucky that wipefs actually prints out the parts it wipes.Įcho -en '\x45\x46\x49\x20\x50\x41\x52\x54' | dd of=/dev/sda bs=1 conv=notrunc seek=$((0x00000200))īut note that the offsets there are different from the ones in your case! You'll need to use the values you got from wipefs.īased on the offset values (0x3b9e655e00 vs 0x37e4895e00), they had a slightly larger disk than you did (~256 GB vs ~240 GB). data 1050624 468860927 467810304Ĭan I / Should I just hit Write (Write partition structure to disk)? If not, why not? Just now, I ran the testdisk on that SSD drive, and it found many partitions, but only these two match the original: TestDisk 7.1, Data Recovery Utility, July 2019ĭisk /dev/sda - 240 GB / 223 GiB - CHS 29185 255 63ġ P EFI System 2048 1050623 1048576 Ģ P Linux filesys.
I will quote the wipe and undo parts from there, I want to know if it's sound and I can safely execute it on my server, which I did not yet reboot, and since then trying to figure out a work-around from this hell of a typo: I might have found an article hosted on, namely: dev/sda: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa dev/sda2: 2 bytes were erased at offset 0x00000438 (ext4): 53 ef dev/sda1: 2 bytes were erased at offset 0x000001fe (vfat): 55 aa dev/sda1: 1 byte was erased at offset 0x00000000 (vfat): eb
Sector size (logical/physical): 512 bytes / 4096 bytes I am looking for a way of undoing this wipefs command: wipefs -all -force /dev/sda? /dev/sda
0 kommentar(er)
