From owner-freebsd-questions Sun Mar 29 19:23:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00500 for freebsd-questions-outgoing; Sun, 29 Mar 1998 19:23:53 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00361 for ; Sun, 29 Mar 1998 19:23:43 -0800 (PST) (envelope-from andre.albsmeier@mchp.siemens.de) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.8.8/8.8.8) with ESMTP id TAA23150 for ; Sun, 29 Mar 1998 19:48:01 +0100 (MET) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by salomon.mchp.siemens.de (8.8.8/8.8.5) with ESMTP id TAA03659 for ; Sun, 29 Mar 1998 19:48:47 +0200 (MDT) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id TAA26515 for ; Sun, 29 Mar 1998 19:48:47 +0200 (CEST) From: Andre Albsmeier Message-Id: <199803291748.TAA28591@intern> Subject: Re: "Read error" on bootup....... In-Reply-To: <351de09b.4814262@mailhost.shellnet.co.uk> from Steven Fletcher at "Mar 28, 98 11:42:00 am" To: ircadmin@shellnet.co.uk (Steven Fletcher) Date: Sun, 29 Mar 1998 19:48:36 +0200 (CEST) Cc: freebsd-questions@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Greetings............ > > I've just installed FreeBSD 3.0 on a machine with 2 Pro's and 256 MB > ram, on a SCSI disk. When attemping to boot, I simply receive the > following error: > > Read error > > That's it. If I put the 3.0 boot floppy into the drive, I can send the > boot options to be: > > 0:sd(0,a)kernel > > And all is well, I can boot up with no problems. However, I'd like to > be able to boot off the harddisk (The partiton is active) without any > user intervention. Could anyone tell me why this is happening, and > possibly on how to fix it? I had this on a Siemens machine (Phoenix BIOS). When installing 2.2.5 in the "not dangerously dedicated mode (or how is it called)" the problem went away. All other (non Siemens machines) machines work great. -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message