Re: softraid RAID1 + CRYPTO error writing metadata -- WHEW

2013-02-10 Thread Scott McEachern 

On 02/10/13 14:17, Alexander Hall wrote:

On 02/10/13 08:13, Scott McEachern wrote:


I could have sworn the man page for fsck(8) said something about rule #1
being "don't panic", but I couldn't find it in there.  Must be somewhere
else.  So I didn't panic, watched a bit of TV and thought about it...


I'm pretty sure you're thinking about scan_ffs(8), which however 
suggests the following:


 1. Panic.  You usually do so anyways, so you might as well get it over
with.  Just don't do anything stupid.  Panic away from your
machine.  Then relax, and see if the steps below won't help you
out.
 2. ...

:-)

/Alexander



Ah yes, thanks for the reminder.

--
Scott McEachern

https://www.blackstaff.ca

Re: softraid RAID1 + CRYPTO error writing metadata -- WHEW

2013-02-10 Thread Alexander Hall 

On 02/10/13 08:13, Scott McEachern wrote:


I could have sworn the man page for fsck(8) said something about rule #1
being "don't panic", but I couldn't find it in there.  Must be somewhere
else.  So I didn't panic, watched a bit of TV and thought about it...


I'm pretty sure you're thinking about scan_ffs(8), which however 
suggests the following:


 1. Panic.  You usually do so anyways, so you might as well get it over
with.  Just don't do anything stupid.  Panic away from your
machine.  Then relax, and see if the steps below won't help you
out.
 2. ...

:-)

/Alexander

Re: softraid RAID1 + CRYPTO error writing metadata -- WHEW

2013-02-09 Thread Scott McEachern 

On 02/09/13 22:16, Scott McEachern wrote:
I didn't know what to wipe first, the sweat off my forehead or ... 
well, you get the idea.


I'm tempted to try to use "bioctl -c 1 -l /dev/sd0,/dev/sd1 softraid0" 
and "bioctl -c 1 -l /dev/sd2,/dev/sd3 softraid0" to recreate the 
volumes (just like how I created them the first time around), and 
*hope like hell* I can get my shit back, but before I do that, I 
wanted to get your advice to ensure that's my best possible move.


Hey, you know, maybe it would be best if I reinstalled my previous 
snapshot (Feb7 I think) and use _that_ version of bioctl, no?




I could have sworn the man page for fsck(8) said something about rule #1 
being "don't panic", but I couldn't find it in there.  Must be somewhere 
else.  So I didn't panic, watched a bit of TV and thought about it...


If "bioctl -d" destroys my crypto partitions but yet they can be found 
upon reboot (with the appropriate bioctl command), wouldn't the same 
thing apply if bioctl somehow destroyed my RAID1 volumes?


I went back to the previous snapshot and with very sweaty hands I gave 
it a try, and yes, it does work.  Rerunning the RAID1 creation commands 
happily brought back both volumes.  I then brought back my crypto 
volumes and voila:


softraid0 at root
scsibus4 at softraid0: 256 targets
sd8 at scsibus4 targ 1 lun 0:  SCSI2 0/direct fixed
sd8: 2861588MB, 512 bytes/sector, 5860532576 sectors
sd9 at scsibus4 targ 2 lun 0:  SCSI2 0/direct fixed
sd9: 2861588MB, 512 bytes/sector, 5860532576 sectors
root on sd5a (6be798121798a5a7.a) swap on sd5b dump on sd5b
sd10 at scsibus4 targ 3 lun 0:  SCSI2 0/direct 
fixed

sd10: 666MB, 512 bytes/sector, 1365008 sectors
softraid0: volume sd10 is roaming, it used to be sd11, updating metadata
sd11 at scsibus4 targ 4 lun 0:  SCSI2 0/direct 
fixed

sd11: 858476MB, 512 bytes/sector, 1758159312 sectors
softraid0: volume sd11 is roaming, it used to be sd10, updating metadata

All is well. :)  I feel like I just got off a really wild rollercoaster 
and want to go back for more abuse.  With that said...


I'm going to try that patch again, only this time I'm going to try it 
out a little differently (more slowly, ahem) and see what's happening.  
I'm filled with self-doubt that *I* did something wrong, somewhere.  
Besides, my nerves are shot, so I couldn't sleep now if I tried.


I really want that patch to work, dammit.

--
Scott McEachern

https://www.blackstaff.ca