cgsecurity.org

I have seen a couple of pages mentioning the use of COW files to experiment with the disks. Essentially mounting a device which is the original disk, plus a file with the changes to it. So the changes are not written to disk
Examples are given here:
http://stackoverflow.com/questions/7582019/lvm ...

See below

sudo pvdisplay -v /dev/sd[acde]
Using physical volume(s) on command line
Failed to read physical volume "/dev/sda"
Failed to read physical volume "/dev/sdc"
Failed to read physical volume "/dev/sdd"
Failed to read physical volume "/dev/sde"
sudo pvck -v /dev/sd[acde]
Scanning /dev ...

Sorry to keep replying to my post... not self-bumping...

I recovered my notes from backup on how I had assembled the raid (note to self... do not keep recovery info on the drive itself)

The disks were partitioned all in the same way (I had some notes that the partitions were not necessary to ...

ran testdisk quick search on one of the other disks, log extract is below (whole log attached)

It does appear to find the 6T partition of the md disk. Isn't it odd, since the raid 10 is supposed to be striped? Anyhow I don't think I can do anything with it until I build the /dev/md back together ...

I used to have a 4 x 3T mdadm RAID 10 array
When moving to a new PC... something went wrong
Now back on the old PC I only see one disk with a partition:


sudo parted -l
Model: ATA WDC WD30EFRX-68A (scsi)
Disk /dev/sda: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number ...