Re: [Bug-ddrescue] Small suggestion regarding the tutorial (in the online doc)

[Adder]

Hi there, again !

> > > Also, I would like to point out that it might be useful to offer a
> > > hint or two at how to distinguish the disks in such cases...
> > 
> > I would be more than happy to offer such hints, if I knew them. Ideas 
> > about this are welcome.
> 
>     All I can say is that this is a genuine fear of mine almost
>     every time I start a ddrescue process, such to the point where
>     I invariably first do an image creation to a temporary
>     drive/server and *then* write the captured image to the new
>     drive. It takes twice the time, but you have the advantage of
>     having a backup image and you don't need to worry about
>     mistakes since one parameter is the drive /dev/sdX, the other
>     is a file/image.
> 
>     For when I really *must* do a drive-to-drive all I can suggest
>     is to examine the brand/model of the drive and compare it to
>     the output in hdparm -i
> 
>         ~$ sudo hdparm -i /dev/sda
>         Model=ST9750420AS, FwRev=0001SDM5, SerialNo=6WS30ZXA
> 
>     It's a risky process, so the only thing you can do is to triple
>     check all your settings *before* pressing enter.

This may sound very childish,
but, before knowing about hdparm -i (i.e. until 5 minutes ago, thank you !),
for disk-to-disk operations,
I have also found that the output of the lsblk command
(or that of the cat /proc/partitions, but lsblk formats in a nicer way)
(did anyone say "format" ? oh no !)
is useful
when the capacity of the output disk is different from (larger than :)
the capacity of the input disk.

In this case (disk-to-disk rescue attempt),
it is important to look at the sizes reported for the disks (sda, sdb)
and not to the sizes reported for the partitions (sda1, sda2, sdb1, sdb2),
because (as everyone here knows better than me)
the output disk becomes identically partitioned to the input disk
after the initial part (e.g. the MBR) is copied.

Thank you ! (-:


--
Bogdan