dealing with a slightly flaky USB drive; unkillable bash process
petter at synth.no
Wed Sep 23 15:08:44 UTC 2015
On Wed, 23 Sep 2015 16:47:52 +0200
Liam Proven <lproven at gmail.com> wrote:
> On 23 September 2015 at 16:16, Adam Funk <a24061 at ducksburg.com> wrote:
> > That sounds interesting. I've been reading the info pages for that
> > --- I guess I can recover the partition on the USB drive to a file
> > with something like this
> > ddrescue <options> /dev/sdc1 path/to/some_file path/to/logfile
> > and then use losetup on the output file?
> Yes you could, but I would *strongly* recommend imaging to a dedicated
> drive. Mixing up whole drives, whole-drive images and partitions is
> tricky and difficult enough and that is /before/ mixing in encryption.
> Buy a drive if necessary.
And I just want to add this: Read and parse your command line *several
times* to make sure you have device nodes in the correct order when
doing imaging of whole partitions/drives, and verify the order in the
man/info page. It's just too easy to image the new, empty drive on top
of the partition you are trying to rescue.
Not meant to be condescending or anything, just a friendly warning.
These types of commands are potentially among the most damaging ones
you can run if you get it wrong.
"Are you sure?"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 213 bytes
Desc: OpenPGP digital signature
More information about the ubuntu-users