Actually krw fixed some things in the scsi midlayer a few weeks ago because the size was not being calculated properly.
Send us some dmesg so that we can determine if it is the same thing. On Wed, Jul 13, 2005 at 09:17:25PM +0200, Per-Olov Sjvholm wrote: > Hi misc > > I have used LSI logic 150-4 SATA MegaRAID controllers in many installations > and have never ever seen a problem. > > Now at a customer site we have installed four OpenBSD 3.7 on new 1U HP G3 > servers and are using LSI logic 150-4 cards. We have on each server set up > two 160 Gb Maxtor disks in a mirror and installed OpenBSD to "use all disk". > Just before the slice editor for the partitions I can see a warning on the > screen about not being able to correctly determine disk geometry. However... > OpenBSD sees the exact size of the mirror as you see in the raid controller > bios. And the server works as it should. It all looks correct after a reboot > and nothing suspicious in the dmesg or any log. Running fdisk after reboot > shows what is expected. > > > The only strange thing is that my home server (also 3.7) running on the same > 150-4 (also latest card bios) controller but with two maxtor 250Gb disks > shows: > [EMAIL PROTECTED]:~#sysctl machdep.bios.diskinfo > machdep.bios.diskinfo.0=bootdev = 0xa0000202, cylinders = 80, heads = 2, > sectors = 18 > machdep.bios.diskinfo.128=bootdev = 0xa0000204, cylinders = 1023, heads = 255, > sectors = 63 > But the customer server (don't have the output) shows one more row similar to > the first row (same CHS info) but with a different 0xa0000202. But I do not > know if this has anything to do with it. > > > > > *What is happening here? > *Why haven't I seen this before? > *Is it dangerous or can be put it to prod as everything seems to work ok? > > > Thanks in advance > /Per-Olov > -- > GPG keyID: 4DB283CE > GPG fingerprint: 45E8 3D0E DE05 B714 D549 45BC CFB4 BBE9 4DB2 83CE > > [demime 1.01d removed an attachment of type application/pgp-signature]
