From owner-freebsd-questions Fri Jan 5 13:25:55 2001 From owner-freebsd-questions@FreeBSD.ORG Fri Jan 5 13:25:52 2001 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from web.cs.ndsu.NoDak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7]) by hub.freebsd.org (Postfix) with ESMTP id 6F16537B400 for ; Fri, 5 Jan 2001 13:25:52 -0800 (PST) Received: (from tinguely@localhost) by web.cs.ndsu.NoDak.edu (8.11.1/8.11.1) id f05LPk248676; Fri, 5 Jan 2001 15:25:46 -0600 (CST) (envelope-from tinguely) Date: Fri, 5 Jan 2001 15:25:46 -0600 (CST) From: mark tinguely Message-Id: <200101052125.f05LPk248676@web.cs.ndsu.NoDak.edu> To: doug.poland@omniresources.com, freebsd-questions@freebsd.org Subject: Re: 4.2R Installation problem -- Read Error In-Reply-To: Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > After the bios and vga boot info appears, I get a screen refresh > and > > Read error > > as the only message. Sounds like a MBR problem? Anyone have a > solution other than re-install? that could be a MBR problem. Boot from the kernel diskette, when the wheel starts spinning, start typing the command: boot> ad(0,a)/kernel -s if it is a boot block problem on the hard disk, it should now be booting (into single user mode via the -s flag, drop that flag if you want to go multiuser. Below assumes single user mode. if this work, then I would check the filessytem: # fsck -p mount the root partition # mount -u /dev/ad0s1a / # or whatever is your partition reload the boot blocks: # disklabel -B ad0 --------------- I have also seen the "ata" driver mess up with some older, lower quality motherboard IDE controlers and had to make a kernel using the old "wd" drivers. --mark tinguely. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message