-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, Nov 13, 2016 at 12:53:20PM +0100, Thomas Schmitt wrote:
> Hi,
>
> Richard Owlett wrote:
> > I'm tangled up !! I plead for 5 or 6 lines to copy-n-paste.
>
> My proposal deviates from some aspects of your original plan.
Ah, Thomas, you're the fairy :-)
My wish of someone chiming in became true
Yes, option -p makes a lot of sense.
[...]
> Copying disk to partition is not the best thing to do if you want
> to use the copy result directly.
> If the original disk contains partitions - even if it is only a single
> one -, then each should get into a separate storage container. So you
> can mount these containers.
>
> Storage container can be a whole disk device, a partition of a disk
> device, or a data file in a large filesystem which can represent
> large files (i.e. a normal Linux filesystem in a large partition).
>
> Most normal and harmless to use is a filesystem.
> So if you have a partition which is large enough for the whole original
> disk, then i advise to equip it with a filesystem (by e.g. mkfs) and
> to mount it somewhere (e.g. as /mnt/my_sdb6).
As far as I understood, Richard is already doing that: his "big" disk
(where the backup is going to) has already a file system and is mounted.
His "first cut" command
ddrescue /dev/sdc /mnt/repaired.img /mnt/repaired.log
is already copying the raw device /dev/sdc to a file in the target
system.
Thanks
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlgoVi0ACgkQBcgs9XrR2kZY9ACfVNmDcQRN1AoyRFqmdJSN+SyW
yrcAn2N6kjwTHawHElYzaV+2jDCWWtUu
=60fJ
-----END PGP SIGNATURE-----
