> The first thing I need to do is test patches for Marco. After we know
> things work correctly with "normal" hardware and firmware, then I can
> satisfy my curiosity and go mucking about with the firmware to see what
> happens. If you see a puff of blue smoke coming from my place, cross
> your fingers and hope that I still have a few more lives left. ;-)
I realize it's only been three days, but have you had any interesting
results so far? My MegaRAID i4 card just came in the mail today, and given
the contents of this thread, I'm a bit concerned about installing it in a
production environment (i.e. the server that's sending this mail). Normally
I would just wait and see, but unfortunately, I'm between a rock and a hard
place here, as the disk my /home partition lives on started to fail on me
yesterday ("uncorrectable data error" messages during fsck after a power
outage).
I'm hoping that, since my setup is not identical to yours, I'll be OK for
the time being. Given the following configuration:
Motherboard: Intel (can't remember the model, it was bought new @ CompUSA
~1.5 years ago)
Processor: Celeron 1.8GHz
RAM: 512MB
RAID_HBA: LSI MegaRAID i4
Firmware: Unknown, as card has not yet been installed
Disks: 3 Maxtor 6Y200P0
Physical: 1 disk/channel
Logical: 1 Logical Device (RAID 5)
Booting From: Fujitsu MPB3032ATU E attached via motherboard's primary IDE
interface (pciide0:0:0)
OS Version: Currently OpenBSD 3.5, had planned to upgrade to 3.8 at the time
of RAID install
roughly how likely am I to run into a problem like this, or any other
problem that would cause my RAID to malfunction during normal operation as
the location of my /home and possibly /var or /usr partitions? Specifically,
if I just replace my dying drive with the RAID (and possibly move over /var
& /usr) and make no special demands on it such as trying to boot from it or
using the RAID mgt, am I going to run into problems?
I hate to ask such a broad question, but I want to make sure that I've
covered all possible angles here. I'm more than happy to clarify the above
as necessary, and/or to track down more specific information on my hardware
if doing so would be useful. Further, if there is anything I can do to help
fix this problem (test Marco's patch, send output of developer-specified
commands, etc.), I will be more than happy, provided that I don't have to
take my system down for long stretches of time (i.e. several hours) at a
time.
Thanks,
Alex Kirk
