Date: Sun, 01 Mar 2009 20:38:40 -0500 From: Alex Kirk <alex@schnarff.com> To: Tamouh Hakmi <hakmi@rogers.com> Cc: questions@freebsd.org Subject: RE: RAID Gone Wild - One Array Split Into Two Message-ID: <20090301203840.130430myl3cd81wk@mail.schnarff.com> In-Reply-To: <106485CFDFE44C7DBD441994EE990916@tamouh> References: <20090301180006.19402mvtopuv9go4@mail.schnarff.com><alpine.BSF.2.00.0903011826500.494@whiskey.ihavefire.com> <20090301202004.19264ty2m0sdne4g@mail.schnarff.com> <106485CFDFE44C7DBD441994EE990916@tamouh>
next in thread | previous in thread | raw e-mail | index | archive | help
This is why I love open-source mailing lists - you never know what =20 sort of awesome you'll find! My question at this point, though, is how in the world I could =20 actually apply this patch, seeing as how the system is in a =20 non-bootable state. Is this something that's already been included in =20 a development branch that I could go download? Or do I need to do =20 something else? Thanks, Alex > Alex, > > This is known problem with FreeBSD and ICH7..ICH8..ICH9 chipsets. =20 > There is a patch for it: > > http://www.nabble.com/Vital-Patches-for-ataraid-with-Intel-Matrix-RAID-(IC= H7)-td16179257.html > > I though didn't test the patch, and funny thing, I posted earlier =20 > today asking if anyone had tried out that patch. > > Hope this helps, keep me posted if you're able to bring it online. > > Thanks, > > Tamouh > >> -----Original Message----- >> From: owner-freebsd-questions@freebsd.org >> [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Alex Kirk >> Sent: March 1, 2009 8:20 PM >> To: Jamie >> Cc: questions@freebsd.org >> Subject: Re: RAID Gone Wild - One Array Split Into Two >> >> >> Does anyone have a clue how I can fix this, preferably while >> >> retaining my data? I could wipe the box if necessary, but >> I'd really >> >> prefer not to, as that would be a huge pain in the butt. >> > >> >> Thanks, >> >> Alex Kirk >> > >> > >> > >> > >> > I would begin by going into the raid BIOS at bootup to see what >> > containers are now configured. If everything is hosed up in >> there the >> > OS isn't going to be able to fix anything. >> > >> > >> > - Jamie >> > >> >> Sorry, should have already gone over this. >> >> The RAID BIOS is terrible - my options are "Create Array", "Delete >> Array", "Reset Disk States", and "Exit". It shows only the >> one array, >> but all four disks show as Offline Member in red there. I'm just >> concerned that if I reset the array or delete it, the state >> table (or >> whatever other magic is involved in making RAID work) will get hosed >> up and the data will be unrecoverable. >> >> Alex >> >> >> ---------------------------------------------------------------- >> This message was sent using IMP, the Internet Messaging Program. >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" >> > > > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090301203840.130430myl3cd81wk>