Re: Strange Software RAID Problem

[list maaghosting net]

   Forrest,
Here is the output of fdisk -l

Disk /dev/sda: 36.9 GB, 36969185280 bytes
255 heads, 63 sectors/track, 4494 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/sda1   *         1      4047  32507496   fd  Linux raid autodetect
/dev/sda2          4048      4366   2562367+  fd  Linux raid autodetect
/dev/sda3          4367      4493   1020127+  82  Linux swap

Disk /dev/sdb: 36.9 GB, 36969185280 bytes
255 heads, 63 sectors/track, 4494 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/sdb1   *         1      4047  32507496   fd  Linux raid autodetect
/dev/sdb2          4048      4366   2562367+  fd  Linux raid autodetect
/dev/sdb3          4367      4493   1020127+  82  Linux swap

  I am assuming it is interesting that fdisk -l still picks up /dev/sda, yes?

  The server is colocated so it will be a little bit of a hassle getting to the
machine and getting everything back online again.  It is not the biggest deal
as there are offsite backups, and the machine is fairly new into service.

  Did you see anything in the RAID config that would indicate to you that
swapping in a new drive would fix the problem?

  Basically, I will have a "limited" amount of time in the facility to perform
the upgrade, so I would like it to go as seemlessly as possible.  What are the
steps in restoring the array?

  Thanks,

  Peter



Quoting "Taylor, ForrestX" <forrestx taylor intel com>:

> On Tue, 2003-11-25 at 14:37, list maaghosting net wrote:
> >    Forrest,
> > Thanks for the response.  I have looked through my messages files and can't
> seem
> > to turn up an errors on the array.  That's what got me confused at first,
> as I
> > was under the impression the raid driver would log to syslog if one of the
> > drives dropped off the array.  Luckily this machine is fairly new to be
> > deployed and there are not too many users on it, so it can be pulled
> offline.
> > 
> > Any suggestions on the steps to rebuild this array?  I would rather not
> have to
> > re-install Redhat+all of the software from scratch, etc :-)
> 
> So it is sda that dropped off the array.
> 
> Is it hot-pluggable?
> Are the lights flashing? 
> What does `fdisk -l` show?
> 
> You may want to find a copy of rescan-scsi-bus.sh and run that to see if
> it finds sda again.
> 
> Again, make sure that you have a full backup, and that it works!
> 
> Forrest
> 
> 
> -- 
> Shrike-list mailing list
> Shrike-list redhat com
> https://www.redhat.com/mailman/listinfo/shrike-list
>