From owner-freebsd-questions Sat May 23 23:59:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26157 for freebsd-questions-outgoing; Sat, 23 May 1998 23:59:58 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26124 for ; Sat, 23 May 1998 23:59:49 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.8/8.8.8) with SMTP id XAA09450; Sat, 23 May 1998 23:59:48 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Sat, 23 May 1998 23:59:48 -0700 (PDT) From: Doug White Reply-To: Doug White To: "Graham C.H.K. Gill" cc: "freebsd-questions@freebsd.org" Subject: Re: Syjet timeout & booting 2:sd(0,a)/kernel In-Reply-To: <199805210924.FAA12293@smtp.interlog.com> 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 On Thu, 21 May 1998, Graham C.H.K. Gill wrote: > I have a Syquest Syjet 1.5G drive attached to my Adaptec 1542CF > controller, and although the FreeBSD (2.2.6) SCSI subsystem has no > problems recognizing and using the drive, I get timeout problems > whenever the Syjet has spun down. As far as I can tell from the DOS > programs that came along with the Syjet, I can set spin down time to as > long as 3 hours but I can't disable it. If I try to access the drive > after it has spun down, the usual result is that the command in > question, e.g. mount, times out before the drive spins back up. The > time out can have few or it can have disastrous consequences, such as a > panic reboot together with inability to properly sync all drives. Yuck. You may want to look into setting up an amd map so that it dismounts the drive when it's quiet and remounts it when you access the drive again. > I have 2 IDE drives but am booting FreeBSD off of my first SCSI drive, > ID 0. I'm using the OS/2 Bootmanager to select which OS to boot. The > FreeBSD bootstrap remembers somewhat imperfectly which drive I last > booted. I type in 2:sd(0,a)/kernel at the boot prompt, which works > fine, but the next time around the loader attempts to boot > 2:sd(2,a)/kernel, which fails, so I type the correct string in. What do > I need to put in my kernel config file or do to the boot blocks to get > the desired behaviour? Add the string 2:sd(0,a)/kernel to the file /boot.config. That will make it the `default'. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message