![]() ![]() I tested wiping and undoing it with a VFAT image, and wrote this off the top of my head before reading your version too closely: printf "$(printf '\\x%s' 46 41 54 31 36 20 20 20)" |ĭd bs=1 conv=notrunc seek=$(printf "%d" 0x00000036) of=test.vfat Not good.Īlso, the magic numbers for the filesystems of course need to be in the right places. That shouldn't matter much, in that any partitioning tool should be able to rewrite it as long as the first copy is intact.īut if it was the other way around, and the wrong offset you used happened to be within the size of your disk, you'd end up overwriting some random part of the drive. Using their values would mean that the backup GPT at the end of disk would be left broken. 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 #Wipefs force how toNow all of the 8 disks are 10TB and I do not intend to do a dd of the whole disk, because that's 14hours for each disk, so I'd really appreciate if someone has an idea how to achieve a wipe.OS: Debian Bullseye, uname -a: Linux backup-server 5.10.0-5-amd64 #1 SMP Debian 5.10.24-1 () x86_64 GNU/Linux * dd if=/dev/zero of=/dev/sda bs=1M count=1000 -> no errors (obviously), Proxmox GUI after reload still shows disk as ddf_raid_member * wipefs -fa /dev/sda -> no errors, Proxmox GUI after reload still shows disk as ddf_raid_member Of course you may see that different, because Virtual Environment 7.0-8 is flawless and bug-free already. Whatever you decided, you decided wrong - because that's a bug. ![]() I can click "wipe disk", some are-you-sure-warning appears, I click yes, some progress bar appears. #Wipefs force freeZFS does not see any free disks, because all are marked as ddf_raid_member. Put some disks from an old vmware installation in there, want to create a ZFS pool on them. I/O size (minimum/optimal): 512 bytes / 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I could do wipefs from CLI but works only if I add -a and -f flags.īack to web gui, I tried again and get the same error.ĭisk /dev/sdb: 200 GiB, 214748364800 bytes, 419430400 sectorsĭisk model: VBOX HARDDISK => As you can see, I was testing in VirtualBox. I have tried to wipe out an HDD which I previously using as Ceph OSD drive and get this message:ĭisk/partition '/dev/sdb' has a holder (500) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |