Date: Sun, 01 Mar 2009 20:20:04 -0500 From: Alex Kirk <alex@schnarff.com> To: Jamie <jamie@gnulife.org> Cc: questions@freebsd.org Subject: Re: RAID Gone Wild - One Array Split Into Two Message-ID: <20090301202004.19264ty2m0sdne4g@mail.schnarff.com> In-Reply-To: <alpine.BSF.2.00.0903011826500.494@whiskey.ihavefire.com> References: <20090301180006.19402mvtopuv9go4@mail.schnarff.com> <alpine.BSF.2.00.0903011826500.494@whiskey.ihavefire.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> Does anyone have a clue how I can fix this, preferably while =20 >> 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 =20 > containers are now configured. If everything is hosed up in there =20 > 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 =20 Array", "Reset Disk States", and "Exit". It shows only the one array, =20 but all four disks show as Offline Member in red there. I'm just =20 concerned that if I reset the array or delete it, the state table (or =20 whatever other magic is involved in making RAID work) will get hosed =20 up and the data will be unrecoverable. Alex ---------------------------------------------------------------- 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?20090301202004.19264ty2m0sdne4g>