Date: Mon, 17 Aug 1998 15:20:43 -0700 (PDT) From: David K Phinney <dave@dowco.com> To: freebsd-questions@FreeBSD.ORG Subject: sd3 but not sd3s1? Message-ID: <199808172220.PAA10261@lithium.dowco.com>
next in thread | raw e-mail | index | archive | help
Hi, When I try to use disklabel on sd3s1 I get the error "device not configured". I can use sd3 though, and sd[0-2]s1 with no problems. All the disks are wired-down, and there are two SCSI controllers in use, sd0-2 on one, and sd3 on the other, which is an `amd' controller. Here's the relevant part of my kernel config: controller amd0 controller scbus1 at amd0 disk sd3 at scbus1 target 3 controller ahc0 controller scbus0 at ahc0 disk sd0 at scbus0 target 0 disk sd1 at scbus0 target 1 disk sd2 at scbus0 target 2 #device sd0 device st0 device cd0 The amd chip gets probed first, but I wanted the other disks to be named first. I am experiencing a similar problem on another machine which has only sd0 wired-down. I can't use sd[12]s1 (but I can use sd[12] and sd0s1). Here's its config: controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr controller ahc0 controller scbus0 at aha0 disk sd0 at scbus0 target 0 device st0 device cd0 The ahc's (two controllers) get probed first, but I wanted the disk on aha0 to be named first. All of the /dev files are there. What am I doing wrong, or is this some kind of bug? Please reply by email. Thanks --dave When a fellow says, "It ain't the money but the principle of the thing," it's the money. -- Kim Hubbard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808172220.PAA10261>