Date: Thu, 25 May 2006 22:53:34 -0500 From: Kevin Kinsey <kdk@daleco.biz> To: Lisandro Grullon <lisandro.grullon@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Disk Geometry Errors. Message-ID: <44767BBE.5030506@daleco.biz> In-Reply-To: <9a4a258a0605251059w36b7f3c5k8d823c863e82845f@mail.gmail.com> References: <9a4a258a0605240749j6901765auf942c5c6cd99671e@mail.gmail.com> <44747DD3.9040805@daleco.biz> <9a4a258a0605241035v28088f83l845c8c320a44f87@mail.gmail.com> <9a4a258a0605250647q4d0cd33kf6bf95f06af795d8@mail.gmail.com> <9a4a258a0605251059w36b7f3c5k8d823c863e82845f@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Lisandro Grullon wrote: > The current setup I got in the machine is using 2 SATA (200GB each) with > the raid controller that is build into the motherboard (tyan S2885). I > wanted to add additional space and I got a Areca 1120 which could hold > another 8 sata drives. I only have a 5 bay enclosure so I went ahead and > I orderd 5 (300GB) drives. I configure the controller to use Raid 5 with > 4 drives and keep 1 as spare in case of a failure. The problem that is > bothering me is that the OS works great with the RAID 1 configuration. > When I boot into FBSD it all goes ok and I loging and everything , but > when I try configuring the RAID 5 disk set using sysinstall> fdisk I get > the disk geometry error right after selecting the disk set. I am not > sure, but is there a way to find out the disk geometry that the > controller bios is assuming is the correct one. If there is a way to > find that information our, I can just use the "G" option in fdisk and > input the correct disk geometry myself. What aproach is the best one to > take in my case. Thank you. Lisandro What's still not apparent to me is what the real trouble is. I regularly see the "geometry incorrect" message from sysinstall, but have not had it fail to write. I'm pretty sure that's what I'm hearing from Jerry McAllister's response, also. I guess my question for Lisandro is, "can't you just ignore the error, do the write, and be OK?" Of course, I think that if that were the case, this thread would have been over a few posts ago. As for the "G" option, I can't say it's made any difference for me... Have we seen any diagnostic information? Could we see the relevant section of /var/run/dmesg.boot? How about `ls -l /dev/ad* /dev/ar* /dev/da*` ? `bsdlabel /dev/foo` ? Kevin Kinsey -- Reactor error - core dumped!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44767BBE.5030506>