Hi; BTW, this is the security list and RAID things should go over to suse-e..... I have used the Mylex DAC960 driver and cards for quite some time....and I think that the issue you might have come into was that the 1100 is the ExtreameRAID line that came into production around the time of the 2.2.16 if I remember right...so then, yes, you would have probably been much better using a newer ver kernel that had the drivers subsequently relaesed in that series for the 1100....you can take a look at dandelion.com when Leonard maintains some info on the Mylex family. For the mount issue have you defined a logical partition in the DAC Bios? If yes then you will want to lay a F/S on that partition with Yast or manually....I tend to use the RAID for my boot device also simply for the added protection, but you may do a separte drive and such.....either way Yast should do the trick for you once the Logical device is present. Regards, Jon On Tue, 29 May 2001, Magus Ba'al wrote:

I'm running into a problem with my Mylex 1100 scsi raid controller. I have SuSE 7.0 Pro installed. The problem I ran into earlier today was an error running modprobe. It would spit back an error:

modprobe DAC960 modprobe: line 5: Invalid dependency /* For struct iovec */

This happened for all modules during boot, which was a giant pain to manually load the driver using insmod, then restart some services. I found a workaround:

insmod DAC960 Using /lib/modules/2.2.16/block/DAC960.o

But I couldn't use the mylex card, all other cards seemed to work just fine. The mylex card worked fine until I rebooted.

I fixed this problem by upgrading to the 2.2.19 kernel, with all the updates needed to upgrade the kernel (libc, libd, nssv1, shlibs) and now I don't have any problems running modprobe. What I'm running into now is I can't get the system to mount the arrays.

modprobe DAC960

mount /dev/rd/c0d0p1 /blah mount: /dev/rd/c0d0p1 is not a valid block device

lsmod Module Size Used by DAC960 58372 0 (unused) nfsd 182888 4 (autoclean) autofs 9644 2 (autoclean) eepro100 17432 1 (autoclean) memstat 1540 0 (unused) serial 42804 0 (autoclean) aic7xxx 105024 0 (unused)

I've already rebooted, cold boot, even reseated the card for giggles. The card's bios info shows during boot, so the card didn't just magically die at the same time (I hope...). The only thing I can think of is I do have a problematic drive (being replaced soon) that will sometimes not respond. But it shouldn't take down the entire card (i think...). Other than that, nothing has been changed on the box.

Any thoughts, ideas, suggestions, pointers, etc. would be greatly appreciated.

TIA Steve

"I am the Illustrious Postmaster and Grand Poobah of Electronic Transmissions" -Unknown

--------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com