On 9/23/19 1:07 PM, ToddAndMargo via users wrote:
On 9/22/19 6:06 PM, Samuel Sieb wrote:
> On 9/22/19 5:33 PM, ToddAndMargo via users wrote:
>> The same dd restored perfects to another stick.
>> I do believe want went wrong as the partition
>> structures not being written in the right places.
>> So gzip is out. Rats!
>
> Can you provide the exact commands you used?
# dd status=progress bs=4096 if=/dev/sdx of=DeadStick.FC30_$(date +%Y-%m-%d).dd.gz
??? Do you think that giving a file an extension of gz will automatically result in it
being gzipped?
# dd status=progress bs=4096 if=/dev/sdg of=DeadStick.FC30_$(date +%Y-%m-%d).dd.gz
# file DeadStick.FC30_2019-09-23.dd.gz
DeadStick.FC30_2019-09-23.dd.gz: DOS/MBR boot sector; partition 1 : ID=0x83, start-CHS
(0x4,4,1), end-CHS (0x3ff,254,2), startsector 2048, 15685632 sectors
It isn't gzipped.
Have to then
# mv DeadStick.FC30_2019-09-23.dd.gz DeadStick.FC30_2019-09-23.dd
# gzip DeadStick.FC30_2019-09-23.dd
# file DeadStick.FC30_2019-09-23.dd.gz
DeadStick.FC30_2019-09-23.dd.gz: gzip compressed data, was
"DeadStick.FC30_2019-09-23.dd", last modified: Mon Sep 23 05:24:19 2019, from
Unix, original size 3737124864
and now it is.
# gunzip --to-stdout backup.date.dd.gz | dd status=progress bs=4096 of=/dev/sdx
???
You've created a file named one thing and are using a different name?
And, if your file wasn't gzipped and you tried to ungzip it you'd get
# gunzip DeadStick.FC30_2019-09-23.dd.gz
gzip: DeadStick.FC30_2019-09-23.dd.gz: not in gzip format
So, did you really provide the "exact" commands you used?
--
If simple questions can be answered with a simple google query then why are there so many
of them?