Short summary:
It turns out that I must have formatted three of the drives, which is
why I only got one listed when I scanned them. It turns out the one
command line:
mdadm --assemble /dev/md0 /dev/hde1 /dev/hdf1 /dev/hdg1 /dev/hdh1
did it perfectly. I had been doing it without the "1" on th
On Tue, Oct 17, 2006 at 02:21:19PM -0400, Hal Vaughan wrote:
> On Tuesday 17 October 2006 11:15, michael wrote:
> > On Tue, 17 Oct 2006 03:07:01 -0400, Hal Vaughan wrote
> >
> >
> > > Does anyone have experience rebuilding a mdadm RAID when the config
> > > info has been wiped out? (I wouldn't th
On Tuesday 17 October 2006 17:34, michael wrote:
> > In the future, I'll build my own .conf files just to be sure. In
> > the long run, I'm just going to find a RAID controller that does
> > hardware RAID5, preferably one that's hot swappable, and just
> > rebuild the RAID on that.
> >
> > > I als
> In the future, I'll build my own .conf files just to be sure. In
> the long run, I'm just going to find a RAID controller that does
> hardware RAID5, preferably one that's hot swappable, and just
> rebuild the RAID on that.
>
> > I also like to run / from a raid array. /boot is a mirror,
> >
On Tuesday 17 October 2006 11:15, michael wrote:
> On Tue, 17 Oct 2006 03:07:01 -0400, Hal Vaughan wrote
>
> > I have a server with one drive that has the boot and system on it
> > and a RAID5 device managed by mdadm. The RAID is made up of 3 hard
> > drives with a 4th spare also hooked up.
> >
>
On Tue, 17 Oct 2006 03:07:01 -0400, Hal Vaughan wrote
> I have a server with one drive that has the boot and system on it
> and a RAID5 device managed by mdadm. The RAID is made up of 3 hard
> drives with a 4th spare also hooked up.
>
> The system drive crashed and I restored it. The problem i
6 matches
Mail list logo
