Date: Sat, 26 Dec 2009 18:40:01 +0100 From: Benny Goemans <benny.goemans@belgacom.net> To: =?iso-8859-2?q?G=F3t_Andr=E1s?= <andrej@antiszoc.hu> Cc: freebsd-amd64@freebsd.org Subject: Re: Intel Matrixraid on amd64 Message-ID: <200912261840.01861.benny.goemans@belgacom.net> In-Reply-To: <40504.188.156.82.138.1261762249.squirrel@mail.deployis.eu> References: <200912251214.19788.benny.goemans@belgacom.net> <40504.188.156.82.138.1261762249.squirrel@mail.deployis.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Andr=E1s, I am indeed aware of the risk that these kind of raid solutions bring with= =20 them and if I would do the whole system anew I would just buy a separate ra= id=20 controller. The thing is that there's now around 1TB of data in a raid configuration si= nce=20 one or two years and I can't change raid controllers easily. This is=20 especially hard since it's a tri boot system (windows, freebsd and a test-o= s). But I suppose that the driver is expected to work on amd64 just as it is on= =20 i386, isn't it? After all everything is showing up fine, it just seems to b= e=20 that sysinstall has a problem using it (maybe the kernel but I'll do some m= ore=20 tests to confirm). Regards, Benny Goemans On Friday 25 December 2009 18:30:49 G=F3t Andr=E1s wrote: > Hi, >=20 > I strongly advise against any of these "raid solutions". I got a very > rough weekend beacuse of the nvidia raid. Here's the short story. >=20 > I got our new webserver with S939 Opteron and the matched nvidia chipset. > That time FreeBSD 6.1 was the actual, so that was installed. When > installing I noticed that the motherboard raid works with FreeBSD so I > went with it. It turned out that it's completely transparent so I was > happy thinking that a simple solution is not likely to go wrong. >=20 > On a weekend I went for the planned maintenance to the coloc facility. > When the reboot came the motherboard nvidia raid told me that I have a > failed Raid1 with one disk. The problem was that after this it refused to > boot anymore. Later it turned out that somewhy 2 weeks ago! the nvidia > raid dropped one disk and that left in that state (it was mountable, > readable quite well etc.) and the other had the actual data. >=20 > Both disk was replaced then beacause I told myself that at least I'd like > to gain something out this huge downtime. Since then gmirror was used and > tried what it would do if I take out one this. Gmirror handled it quite > well, I got a message in the log about the disk failure and everything > went on. With the software raid the nvidia controller or the disk > backplane lost one disk after half a year of uptime but a reboot corrected > it. (There was a small thread about this that time on a FreeBSD maillist.) >=20 > On P=E9n, December 25, 2009 12:14 pm, Benny Goemans wrote: > > Hi, > > > > > > I'm running 8.0-release (i386) on a Asus P5WDG2 motherboard with > > integrated Intel Matrixraid (software raid) controller. Everything runs > > fine in this one. > > > > Since I've noticed 64 bit support for the Nvidia driver I've been trying > > to install the AMD64 8.0 version. During install dmesg shows my hard > > drives and raid drives (ar0, ar1) perfectly, just as it does in the i3= 86 > > version. But when I enter sysinstall it can't locate my drive(s). It ju= st > > doesn't find a single drive, no arN but also no hdaN (which do show up = in > > dmesg). > > > > Has anyone seen this behaviour before and is there some kind of solutio= n? > > Maybe some parameters to sysinstall, extra kernel modules to load that > > are on the install disk or something? > > > > Kind regards, > > > > > > Benny Goemans > > > > > > ps. I'm currently redownloading the iso file for the cd and will check > > its checksum to make sure I don't have some bizarre bad download > > _______________________________________________ > > freebsd-amd64@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200912261840.01861.benny.goemans>