Re: Looking for confirmation as I enter the acceptance stage.

[blobfish <blobfish@gmx.com>]

[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]

On Wednesday, July 26, 2023 1:49:31 PM EDT Michael Kjörling wrote:
> Ideally, the next step would be to use the copy you made of the broken
> container (that is, in effect, the new drive) to extract data, while
> keeping the original untouched until you have a copy (so that if you
> make a mistake, you can start over from the original). _Do you have,
> or can you get, anywhere that you can realistically put that ~7TB of
> data during copying?_
> 

Ok I got a third drive to receive files. I was getting everything hooked up and 
ready and I ran into a problem. Apparently the clone wasn't completely 
successful? 

parted: //on cloned drive
Error: Invalid argument during seek for read on /dev/sdc
Retry/Ignore/Cancel? I                                                    
Error: The backup GPT table is corrupt, but the primary appears OK, so that 
will be used.
OK/Cancel? OK                                                             
Model: WD easystore 264D (scsi)
Disk /dev/sdc: 8002GB
Sector size (logical/physical): 512B/4096B
Partition Table: unknown
Disk Flags: 

Your procedure for dumping and testing the luks header doesn't work on this 
cloned drive.

I made a screen dump when ddrescue finished. It is attached. What should I do 
next?


[-- Attachment #2: ddresuce_result.png --]
[-- Type: image/png, Size: 32109 bytes --]