On 11/19/14 19:38, Dutch Ingraham wrote: > On 11/19/14 18:18, Bertrand Janin wrote: >> Dutch Ingraham wrote : >>> Just asking for a sanity check. I tried installing 5.6 from CD on a >>> WD1600AAJS HDD and was presented with "Available disks are: none." This >>> seems to be a fairly mainstream drive around for several years (mine being >>> manufactured in 2010), so I just want to check whether I've missed some >>> critical install instruction. I followed section 4.5 of the FAQ and >>> accepted default settings and used entire disk. >>> >>> The same install disk has been used without incident on other installations >>> and a different OS was installed on the HDD after the attempt chronicled >>> above. >>> >>> Your suggestions/advice are appreciated. dmesg to follow: >>> >>> ------------------------ >>> >>> OpenBSD 5.6 (RAMDISK_CD) #303: Fri Aug 8 00:25:26 MDT 2014 >>> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD >>> real mem = 8401186816 (8011MB) >>> avail mem = 8172158976 (7793MB) >>> mainbus0 at root >>> bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xf0450 (82 entries) >>> bios0: vendor Dell Inc. version "A03" date 02/13/2010 >>> bios0: Dell Inc. OptiPlex 780 ... >>> pciide0 at pci0 dev 3 function 2 "Intel Q45 PT IDER" rev 0x03: DMA >>> (unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI >>> pciide0: using apic 8 int 18 for native-PCI interrupt >>> pciide0: channel 0 ignored (not responding; disabled or no drives?) >>> pciide0: channel 1 ignored (not responding; disabled or no drives?) ... >>> pciide1 at pci0 dev 31 function 2 "Intel 82801H RAID" rev 0x02: DMA, channel >>> 0 wired to native-PCI, channel 1 wired to native-PCI >>> pciide1: using apic 8 int 18 for native-PCI interrupt ... >> I don't think it's a drive problem, it doesn't seem to find your disk >> controller at all. I would go in the BIOS and play with the disk controller >> settings. >> >> -b
Absolutely. Disks are disks. it's the interface that you were missing. >> > Excellent - thank you, Bertrand. > > For anyone else with this particular issue and BIOS version, note that > the "SATA Operation" option may need to be set to "legacy." That's best avoided, and I suspect you can. I suspect you went from "Worst setting" to "second worst setting". Looks like your system was set to "RAID" originally. Most of these systems have two options -- AHCI and "Legacy", some have the third option of "RAID". You don't want "RAID"...it is software-only RAID, and under some conditions you can have the BIOS clobber data on the second disk that your non-SW RAID OS set up as a second disk. OpenBSD was one of the first OSs to disable the support of those controlers in that mode to prevent problems, but at least some Linux systems do now, too. AHCI is a huge performance boost over "legacy" in general, and in some cases, the "legacy" support is horrifically slow, slower than the old pciide interfaces that never dreamed of AHCI. Good news is if you flip it from "Legacy" to "AHCI", things will Just Work if you used DUIDs during setup. Nick.
