RE: RAID Gone Wild - One Array Split Into Two
What branch is this patch supposed to apply against? I've tried 7.0-RELEASE and 7.1-RELEASE, and judging by the dates involved, it's somewhere in between the two. Or should I be asking this on the freebsd-hackers list, where that patch was originally posted? Alex Alex, This is known problem with FreeBSD and ICH7..ICH8..ICH9 chipsets. There is a patch for it: http://www.nabble.com/Vital-Patches-for-ataraid-with-Intel-Matrix-RAID-(ICH7)-td16179257.html I though didn't test the patch, and funny thing, I posted earlier 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-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Alex Kirk Sent: March 1, 2009 8:20 PM To: Jamie Cc: questi...@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-unsubscr...@freebsd.org 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-unsubscr...@freebsd.org
RAID Gone Wild - One Array Split Into Two
First off, I realize that this may be more of a lower-level hardware question than is appropriate to ask here, but I'm at a real loss, and have no idea who else to ask...so I apologize in advance if I'm being a pest. That said: I've got a FreeBSD 7.0/stable box that is used as the development server for a live system I administer. It recently crapped out on me (the dev box), and I realized that its power supply had kicked the bucket. After going out and replacing the power supply, it booted right back up, I ssh'd in, and when I ran my first userland command - w, FWIW - it froze up solid. I got one more SSH session in attempting to figure out WTF was going on before it wouldn't even log me in any more. After a couple of hard reboots, I decided to attach a monitor to it to see what was going on. It turns out that the RAID5 array on the system had really lost its mind - all four devices that were part of the array were listed as being offline, which of course meant that the system could no longer boot (as it was booting off of the RAID). The controller is an integrated Intel Matrix DHC7R, built onto the motherboard. I looked around the web a bit to try to figure out how to fix this, and ran across a couple of forum posts (which I can unfortunately no longer seem to find) suggesting that this particular controller was prone to an issue where hard power-downs would sometimes make the drives go offline, and that I needed to boot from CD to re-initialize them into their previous state. I tried first with an Ubuntu Linux CD I had handy - which promptly freaked out and dropped me into an emergency shell - and then the FreeBSD 7.0 boot-only disc. The latter was a bit more helpful, because I got this diagnostic: ar0: WARNING - parity protection lost, RAID5 array in DEGRADED mode ar0: 715418MB Intel MatrixRAID RAID5 (stripe 64KB) status: DEGRADED ar0: disk0 READY using ad4 at ata2-master ar0: disk1 READY using ad8 at ata4-master ar0: disk2 READY using ad6 at ata3-master ar0: disk3 DOWN no device found for this subdisk ar1: 715418MB Intel MatrixRAID RAID5 (stripe 64KB) status: BROKEN ar1: disk0 DOWN no device found for this subdisk ar1: disk1 DOWN no device found for this subdisk ar1: disk2 DOWN no device found for this subdisk ar1: disk3 READY using ad10 at ata5-master Now I can see that my problem is that I've somehow got *two* RAID devices, both improperly configured, whereas I'd only had one before. 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 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-unsubscr...@freebsd.org
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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
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-unsubscr...@freebsd.org
RE: RAID Gone Wild - One Array Split Into Two
This is why I love open-source mailing lists - you never know what sort of awesome you'll find! My question at this point, though, is how in the world I could actually apply this patch, seeing as how the system is in a non-bootable state. Is this something that's already been included in a development branch that I could go download? Or do I need to do something else? Thanks, Alex Alex, This is known problem with FreeBSD and ICH7..ICH8..ICH9 chipsets. There is a patch for it: http://www.nabble.com/Vital-Patches-for-ataraid-with-Intel-Matrix-RAID-(ICH7)-td16179257.html I though didn't test the patch, and funny thing, I posted earlier 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-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Alex Kirk Sent: March 1, 2009 8:20 PM To: Jamie Cc: questi...@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-unsubscr...@freebsd.org 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-unsubscr...@freebsd.org
RE: RAID Gone Wild - One Array Split Into Two
Alex, This is known problem with FreeBSD and ICH7..ICH8..ICH9 chipsets. There is a patch for it: http://www.nabble.com/Vital-Patches-for-ataraid-with-Intel-Matrix-RAID-(ICH7)-td16179257.html I though didn't test the patch, and funny thing, I posted earlier 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-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Alex Kirk Sent: March 1, 2009 8:20 PM To: Jamie Cc: questi...@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-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: RAID Gone Wild - One Array Split Into Two
2009/3/2 Alex Kirk a...@schnarff.com: This is why I love open-source mailing lists - you never know what sort of awesome you'll find! My question at this point, though, is how in the world I could actually apply this patch, seeing as how the system is in a non-bootable state. Is this something that's already been included in a development branch that I could go download? Or do I need to do something else? What I'd do is: make a distribution with the patch included in the source tree on another machine with your current KERNCONF, etc if you have backups of them. Then try reinstalling the machine and if backups are on your side all should be OK. I don't follow -current and -hackers much to advise if it has been fixed upstream. If you have another machine where you can check-out current tree and see if patch has been merged there - good. Regards, Dimitar ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
