From owner-freebsd-questions Thu Jun 11 05:05:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29614 for freebsd-questions-outgoing; Thu, 11 Jun 1998 05:05:48 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from leaf.lumiere.net (j@leaf.lumiere.net [207.218.152.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29567 for ; Thu, 11 Jun 1998 05:05:37 -0700 (PDT) (envelope-from j@lumiere.net) Received: from localhost (j@localhost) by leaf.lumiere.net (8.9.0/8.8.8) with SMTP id FAA19544; Thu, 11 Jun 1998 05:05:35 -0700 (PDT) (envelope-from j@lumiere.net) Date: Thu, 11 Jun 1998 05:05:09 -0700 (PDT) From: Jesse To: freebsd-questions@FreeBSD.ORG cc: shimon@simon-shapiro.org Subject: Followup on changing root device to st0s1a Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Previously my system with a DPT SCSI/RAID card and drives wouldn't boot, giving the following error: changing root device to st0s1a panic: cannot mount root I noticed that although the dpt0 device was recognized and loaded, there attached hard drives weren't recognized (this is when booting off the HD -- when booting off the install floppy, it worked). So I compiled a kernel with a DPT driver from another of my systems, then using the fixit mode, copied that kernel onto the system. I then rebooted and started up using that kernel. All is good now. I guess the moral of the story is that the boot-dpt.flp install doesn't put all the drivers/settings necessary to handle a DPT card + drives (in all situations? maybe just some), so you have to make your own. BTW, my drives were just regular Quantum drives. Now to get the system up to par... --- Jesse http://www.lumiere.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message