[OpenIndiana-discuss] pool messup

[Gabriel de la Cruz]

This is an entry level proliliant, very standard gear. I cannot
believe that you would be the first one using them with ZFS (those
sell really well) Is the Jbod configured? I mean, are all the the
drives correctly defined in whatever config utility provided at boot
time?
Are the drives in both chassis failing?

Supermicro is affordable and pretty basic but I fear using them in any
other way than what they were designed for. Is there something on
those chassis that you were supposed to configure? Those devices are
designed and tested with very traditional raid an jbod setups in
mind... think if there is something you didnt do but you would need to
do in case of setting up a traditional jbod storage...

Back when I had my problem I was testing all the drives 1 by 1 and all
the cables, and all the different combinations of things... it was all
useless. when something so fishy appears beware of the controllers. To
make a memtest is a good idea, you could let it running over night, if
memory corrupts probably there is some hardware problem in the
motherboard.

Thats all that comes to my mind... is the hardrive order swapping
between reboots?

But my bet is supermicro, or the way you configured the jbod utility.

Good luck





On Mon, Apr 11, 2011 at 7:27 PM, Roy Sigurd Karlsbakk <roy at karlsbakk.net> wrote:
> The server is an HP ProLiant DL120 G5. Controller type is LSI SAS1068E with IT firmware (no RAID, only JBOD). Disk chassises are one SuperMicro 12-bay 2U and one SuperMicro 24-bay 4U.
>
> roy
>
> ----- Original Message -----
>> Ummm that bug report says the 2 magic keywords: Jbod, and
>> Supermicro... And the motherboard model is a close one too :O
>>
>> Make sure that jour jbods are configured in whatever type of bios your
>> controller uses, every drive should be a jbod on its own. This looks
>> just like the problem I had (and solved).
>>
>> What board are you using?
>>
>>
>>
>>
>>
>> On Mon, Apr 11, 2011 at 5:08 PM, Roy Sigurd Karlsbakk
>> <roy at karlsbakk.net> wrote:
>> > Looks like this bugger
>> > http://comments.gmane.org/gmane.os.solaris.opensolaris.zfs/34796
>> >
>> > Anyone that knows how this can be fixed?
>> >
>> > roy
>> >
>> > ----- Original Message -----
>> >> Hi,
>> >> your list looks very familiar to me;
>> >> I had something similar on a supermicro motherboard, if you did not
>> >> configure all the independent drives as separate jbods in the raid
>> >> controller, the order of the drives was mysteriously swapping at
>> >> boot
>> >> time. Neither ZFS, neither a conventional raid on Linux was
>> >> working,
>> >> the Linux root mirror was behaving truly funny.
>> >> The hardware was ok, just a bunch of odds.
>> >>
>> >> I never had the time to find the logic behind the problem, I guess
>> >> configuring the raid cards is a good practice... even if you are
>> >> doing
>> >> software raids.
>> >>
>> >> You should check every possible cause, one by one, the painful way.
>> >> Cheers
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> On Mon, Apr 11, 2011 at 2:25 PM, Roy Sigurd Karlsbakk
>> >> <roy at karlsbakk.net> wrote:
>> >> >> It sounds like a bit too much of coincidence that 8 drives have
>> >> >> failed.
>> >> >> Maybe a port extender has failed. It would be of interest to
>> >> >> know
>> >> >> what
>> >> >> these 8 drives have in common.
>> >> >
>> >> > They are in two different chassises, so the only thing in common
>> >> > I
>> >> > can see, is the controller. Also, why on earth do these show up
>> >> > in a
>> >> > new order than in what they were when I created the array?
>> >> >
>> >> > Vennlige hilsener / Best regards
>> >> >
>> >> > roy
>> >> > --
>> >> > Roy Sigurd Karlsbakk
>> >> > (+47) 97542685
>> >> > roy at karlsbakk.net
>> >> > http://blogg.karlsbakk.net/
>> >> > --
>> >> > I all pedagogikk er det essensielt at pensum presenteres
>> >> > intelligibelt. Det er et elementært imperativ for alle pedagoger
>> >> > å
>> >> > unngå eksessiv anvendelse av idiomer med fremmed opprinnelse. I
>> >> > de
>> >> > fleste tilfeller eksisterer adekvate og relevante synonymer på
>> >> > norsk.
>> >> >
>> >> > _______________________________________________
>> >> > OpenIndiana-discuss mailing list
>> >> > OpenIndiana-discuss at openindiana.org
>> >> > http://openindiana.org/mailman/listinfo/openindiana-discuss
>> >> >
>> >>
>> >> _______________________________________________
>> >> OpenIndiana-discuss mailing list
>> >> OpenIndiana-discuss at openindiana.org
>> >> http://openindiana.org/mailman/listinfo/openindiana-discuss
>> >
>> > --
>> > Vennlige hilsener / Best regards
>> >
>> > roy
>> > --
>> > Roy Sigurd Karlsbakk
>> > (+47) 97542685
>> > roy at karlsbakk.net
>> > http://blogg.karlsbakk.net/
>> > --
>> > I all pedagogikk er det essensielt at pensum presenteres
>> > intelligibelt. Det er et elementært imperativ for alle pedagoger å
>> > unngå eksessiv anvendelse av idiomer med fremmed opprinnelse. I de
>> > fleste tilfeller eksisterer adekvate og relevante synonymer på
>> > norsk.
>> >
>> > _______________________________________________
>> > OpenIndiana-discuss mailing list
>> > OpenIndiana-discuss at openindiana.org
>> > http://openindiana.org/mailman/listinfo/openindiana-discuss
>> >
>>
>> _______________________________________________
>> OpenIndiana-discuss mailing list
>> OpenIndiana-discuss at openindiana.org
>> http://openindiana.org/mailman/listinfo/openindiana-discuss
>
> --
> Vennlige hilsener / Best regards
>
> roy
> --
> Roy Sigurd Karlsbakk
> (+47) 97542685
> roy at karlsbakk.net
> http://blogg.karlsbakk.net/
> --
> I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med fremmed opprinnelse. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk.
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>