Date: Sat, 27 Dec 1997 17:12:36 -0800 From: Studded <Studded@dal.net> To: freebsd-questions@freebsd.org Subject: IDE and SCSI drives not playing well together Message-ID: <34A5A784.8843CB4B@dal.net>
next in thread | raw e-mail | index | archive | help
Ok, got my shiny new IBM DCAS 34330, hooked it to my Adaptec 2940 UW, fiddled with the adapter settings, the drive is detected, runs, OS/2 likes it, freebsd likes it. So I get set to install freebsd onto the new drive, with the plan of migrating my freebsd system from the IDE drive (controlled by OS/2's Boot Manager) to the scsi drive. What I want is this: IDE: Boot Manager or OS-BS (According to the adaptec book, if I have an IDE drive on the system, it will always be the boot drive.) C: DOS FreeBSD partition for /usr/obj (or /usr/src, whichever is better) OS/2 free space SCSI: FreeBSD System OS/2 System So I install FreeBSD just fine, tell it to put an MBR on the scsi disk (although I'm pretty sure I tried it both with and without), installation completes without erros. My problem is that both Boot Manager and OS-BS beta tell me that I can't boot the FreeBSD system I've got on the SCSI disk. I've twiddled all the settings on the adapter, so it SHOULD be bootable. Boot Manager tells me: "Selected partition is not formatted, hit any key." OS-BS tells me "No operating system." I've tried OS/2 fdisk, FreeBSD "fdisk" from sysinstall, even DOS fdisk (yuck :). I've searched the archives, and although there are numerous posts of questions similar to mine, there are not any real answers. The one thing in the archives that works is booting the freebsd system on the IDE disk, and telling it to run the kernel on the scsi disk. This works (in the sense that the freebsd installation on the scsi drive comes up) so I know that the installation is complete on the scsi side. In case it matters, I have the 4 gig scsi disk sliced two ways, with 3240M on the freebsd side and the rest free space where OS/2 is going eventually. One of the installations that I did I even deleted the ide controllers in the visual kernel configurator so that it would think it was the only disk in the system. Still no luck. I think I read somewhere in the archives that there is no way to make two completely seperate freebsd installations work on the same system, so if this problem will magically disappear when I delete the "old" freebsd slice, I can live with it till then. Otherwise, I'm open to suggestions on ways to fix this. Since this is such a FAQ, if someone wants to tackle a software solution, I'd be happy to test patches to -Stable. Thanks, and Happy Holidays, Doug
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34A5A784.8843CB4B>