On 07/13/13 12:34, frantisek holop wrote:
> hi there,
> 
> i have decided to create an encrypted usb stick that
> would be the rsynced backup of my $HOME.
> 
> i started by reading softraid(4). and its only example
> looks scary -- it destroys all data on sd0, my main
> drive for years :]  i know, it is only an _example_
> and should never be copied verbatim, but perhaps it
> also doesnt have to be something so in-my-face
> desctructive just becuse it is an example, especially
> when i am trying to do something totally new and
> potentionally very destructive...
> 
> it was not clear to me right from the beginning that
> the raid volume to be created will be "just another"
> sd* drive (some other systems have special devices),
> explaining that was left enterily to the example,
> and me having only sd* drives (hard drives, memory
> cards, usb sticks) it is not a very useful one
> for me...

Hopefully that was a little more clear in the FAQ.

> 
> i also had a look at the FAQ: 14.21.5 - Softraid Crypto
> and there is this paragraph that does not seem to work:
> 
> """
> Once this is set up, you can then "unlock" the crypto volume when desired 
> with:
> 
>     # bioctl -c C -l /dev/sd1m
>     Passphrase: My Crypto Pass Phrase
>     softraid0: CRYPTO volume attached as sd1
> 
> You can then mount the encrypted volume's partitions using mount as usual.

whoops.  yep, that should be "bioctl -c C -l /dev/sd1m softraid0". fixed.
> """
> 
> i am not sure what "unlock" means. but the command does
> not work, bioctl(4) always takes a device parameter
> according to the man page.
> 
> 
> but so far so good. the stick appears to be under bioctl's care
> and i could mount it.  i will still have to experiment with
> hotplug and friends, and what exactly does
> "softraid0: roaming device sd2a -> sd1a"
> mean, as sd2 is the sd card reader showing up as a usb device...

Roaming means the device isn't where it was previously.  USB devices are
very prone to this, as they are often plugged in post-boot in varying
orders, and that will very often result if a device was hot-plugged last
boot and plugged in at boot this time.

In the case of USB devices, it is probably a non-event, but if you have
physical SCSI-like devices hard-attached to your system, you probably
have had an event, like a drive failure or removal.  Softraid adjusts
quite well, but YOU may wish to think about if there is a larger issue
or not.

Nick.

Reply via email to