[rhn-users] Raid repair
LONNIE TROTTER
ltrotter at ajusd.org
Sat Apr 3 23:47:45 UTC 2004
Jon, I have not used this tool before. I took a quick look and the
possibility of using this may have been the answer I was searching for. I
want to thank you for your insight to my problem.
. On Sat, 03 Apr 2004 08:49:11 +0800, Jon Branch wrote
> Hi Lonnie
>
> Instead of using raidtools could you have tried using mdadm to force your
raid 5 to start?
>
> mdadm is documented in "Managing RAID on Linux" by Derek Vadala from
O'Reilly.
>
> Regards
>
> Jon Branch
> IT Coordinator
> Christian Alliance International School - Hong Kong
>
> ----- Original Message -----
> From: "LONNIE TROTTER" <ltrotter at ajusd.org>
> Date: Tue, 30 Mar 2004 10:17:22 -0700
> To: rhn-users at redhat.com
> Subject: [rhn-users] Raid repair
>
> > Has anyone experienced this.
> >
> > We had a server setup with physical space for six scsi hard drives.
> > The first three were constructed as a RAID1 array while the last three
> > were constructed as a RAID5 array. One of the drives in the RAID5 array
> > failed and was not repairable. The failed drive was removed and a
> > replacement drive put in its place, we booted into linux rescue and
> > fdsik'd the drive creating a partition table exactly the same as the
> > drive that had failed. Went to boot back in to Enterprise to raidhotadd
> > the replacement harddrive to the RAID5 array, but enterprise would not
> > let us do that. The RAID5 array would not start because there were only
> > two drives available, if the broken drive was placed back in the raid
> > would come up in degraded mode. The problem here is that we had no
> > physical space to have both the failed drive and the replacement drive
in
> > at the same time. This meant that the raid would not start, preventing
us
> > from raidhotadding the replacement drive. As a result we copied the data
> > off of the raid while it was in degraded mode, put the replacement drive
> > in and rebuilt the raid array, then copied the data back onto it. This
> > was quite time consuming as the data we were moving around was around 25
> > gigabytes.
> >
> > Lonnie Trotter
> > Network Administrator
> > Apache Junction Unified School District
> > Phone: 480-982-1110 Ext. 2050
> >
> >
> > _______________________________________________
> > rhn-users mailing list
> > rhn-users at redhat.com
> > https://www.redhat.com/mailman/listinfo/rhn-users
> >
>
> _______________________________________________
> rhn-users mailing list
> rhn-users at redhat.com
> https://www.redhat.com/mailman/listinfo/rhn-users
Lonnie Trotter
Network Administrator
Apache Junction Unified School District
Phone: 480-982-1110 Ext. 2050
More information about the rhn-users
mailing list