On Fri, Jul 30, 2010 at 5:22 PM, Tobias Weingartner <[email protected]>wrote:
> On Thursday, July 29, Fabrice Dubois wrote: > > > > Here I've copied by hand on another pc, what I am seeing on a new > install, > > booting from a new 4.7 amd64. > > > and 4.6 before on there SAS HDs, just blocked completely now...). Don't > know > > why there are now problems when I try to install on one of the two SAS > HDs I > > have (sd0 and sd1). On a Sata HD, from WD, I had no problems. Fdisk works > > without any problems. I am sending also below the dmesg of that > installation > > on the wd0 (the western digital sata hd, where fdisk works). But here, no > > way to send any dmesg, I am blocked or stucked on the fdisk part... > > Are both hard disks given the "BIOS supported" option in the raid card? > I think they are. At least no problem with other OS. > Type 'machine disk' at the "boot> " prompt, do they both show up? > Yes, thanks, new command, didn't knew it :-) (here typing on another pc) Disk BIOS# Type Cyls Heads Secs Flags Checksum fd0 0x0 *none* 80 2 18 0x4 0x0 hd0 0x80 label 1024 255 63 0x2 0xf4f4d40f hd1 0x81 label 1024 40 63 0x2 0xa1dda2fa hd2 0x82 label 1024 40 63 0x2 0xcc13a438 hd3 0x83 label 1024 255 63 0x0 0x7dfce509 hd4 0x84 label 1024 255 63 0x0 0xd19c24bc cd0 0xef label 0 0 0 0xa 0x0 I finally found a solution to that being "stuck" by directly ignoring the CHS and putting there 63 and the total sectors (163862937) of the primary partition. Then, rebooting, another problem but with booting (and I think I'll be now totally OT). So, booting newly with the CD, and redoing the fdisk, the results were then totally normal, not bogus as the first time. So, after installing ignoring the CHS because the values of fdisk were totally bogus, and booting with CD (because couldn't boot on the newly install though grub2), on the second boot though cd, on the fdisk the parameters were normal again, not bogus. The other problem I'm facing now is with booting, and I'm sure OT, but as I am on this, well, hope not spaming "too much"... :-))) Booting with the Western Digital Sata for 4.7 i386 stable works: set root=(hd0,1) chainloader +1 boot But not for the 4.7 amd64 on the second SAS: set root=(hd4,1) chainloader +1 boot It says: NTLDR is missing An "enter" here and 2 other sentences: Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key I tell this because on the past (before 4.7), it worked without problems. But, it is surely not an OpenBSD problem. What I've done after bypassing the CHS from fdisk, even if now it showed correct values, was the "update" command from: http://www.openbsd.org/faq/faq4.html#Install (*WE AREN'T DONE YET!*) My sincere apologies if I'm spaming here with these informations... > -Toby. > Thank you. Fabrice
