Update: we are screwed.
Note to users of the AMI MegaRAID Enterprise 1500: although a logical
drive can be expanded w/out requiring a backup/restore, you can only add
ONE NEW DRIVE AT A TIME. attempting to simultaneously add two or more
new drives to an existing logical volume will result in total data loss.
as this is a well-known limitation (at least within AMI) you would think
that the BIOS wouldn't let you do this. live and learn.
-matt
-----------------------------------------------------------------------------
Matthew Nelson
Dynamics Technology, Inc.
21311 Hawthorne Blvd., Suite 300, Torrance, CA 90503-5610
Voice: (310) 543-5433 FAX: (310) 543-2117 Email: [EMAIL PROTECTED]
On Thu, 3 Aug 2000, Matt Nelson wrote:
> ok, here's the sequence of events:
>
> - the machine is: dual piii/733, 1G, AMI MegaRAID 1500 (RAID 5, four
> stripes, 106GB total, 85GB used)
>
> - while attempting to expand a logical drive on the RAID, the controller
> failed two of the existing drives, and ignored the two new drives we
> were trying to add. this is BAAAD for RAID5.
>
> - not having any better recourse, we over-rode the controller, and marked
> the two failed drives as good.
>
> - we re-booted w/out any problems.
>
> - second reboot of the day, we got the dreaded 'unexpected error on drive
> sdb1'.
>
> - running 'fsck -y' resulted in: a bazillion screens of output, mostly
> messages about 'too many bad blocks' and 'clearing inode'.
>
> - fsck restarted itself, and has been giving us 'bad or duplicate blocks
> in inode xxxxx: ' followed by 1100 block numbers. it has reached a
> point where it is doing this for every inode. it has been doing
> this for fourteen hours now.
>
> and now the question:
>
> are we screwed?
>
> thanks,
>
> -matt
>
> -----------------------------------------------------------------------------
> Matthew Nelson
> Dynamics Technology, Inc.
> 21311 Hawthorne Blvd., Suite 300, Torrance, CA 90503-5610
> Voice: (310) 543-5433 FAX: (310) 543-2117 Email: [EMAIL PROTECTED]
>
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
>
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
