Re: Inactive raid1 partition failure

2015-08-05 Thread Alex
Hi, >>> I definitely suggest you make a backup of each device superblock and >>> distribute it somewhere safe in the unlikely event two devices in a >>> mirrored array stop cooperating. The superblocks do come in handy from >>> time to time when they can't be acquired once problems happen. >> >> D

Re: Inactive raid1 partition failure

2015-08-04 Thread Chris Murphy
On Tue, Aug 4, 2015 at 9:02 PM, Alex wrote: > Hi, > >>> I panicked a bit, and didn't want to do something stupid (like mdadm >>> -C) before passing it by at least one other person. >> >> I definitely suggest you make a backup of each device superblock and >> distribute it somewhere safe in the unl

Re: Inactive raid1 partition failure

2015-08-04 Thread Alex
Hi, >> I panicked a bit, and didn't want to do something stupid (like mdadm >> -C) before passing it by at least one other person. > > I definitely suggest you make a backup of each device superblock and > distribute it somewhere safe in the unlikely event two devices in a > mirrored array stop co

Re: Inactive raid1 partition failure

2015-08-04 Thread Chris Murphy
On Tue, Aug 4, 2015 at 6:38 PM, Alex wrote: > I panicked a bit, and didn't want to do something stupid (like mdadm > -C) before passing it by at least one other person. I definitely suggest you make a backup of each device superblock and distribute it somewhere safe in the unlikely event two dev

Re: Inactive raid1 partition failure

2015-08-04 Thread Alex
Hi, > It looks like a device is completely missing? > > blkid > blkid.txt > > Then for each md device UUID pair (the md UUID will show up twice in > blkid for each of the three arrays): > > mdadm -E>> mdXraidstats.txt > > Where X=the md device from mdstat. That way you get the superblock > fro

Re: Inactive raid1 partition failure

2015-08-04 Thread Sam Varshavchik
Alex writes: Hi, I have a fedora21 system with three md RAID1 arrays. I had used this system to temporarily access an external array connected to an LSI controller in the system. So I inserted the LSI controller, accessed the data on the disks connected to it, and removed the controller from the

Re: Inactive raid1 partition failure

2015-08-04 Thread Chris Murphy
It looks like a device is completely missing? blkid > blkid.txt Then for each md device UUID pair (the md UUID will show up twice in blkid for each of the three arrays): mdadm -E>> mdXraidstats.txt Where X=the md device from mdstat. That way you get the superblock from each device making up

Inactive raid1 partition failure

2015-08-04 Thread Alex
Hi, I have a fedora21 system with three md RAID1 arrays. I had used this system to temporarily access an external array connected to an LSI controller in the system. So I inserted the LSI controller, accessed the data on the disks connected to it, and removed the controller from the system. Now, a