From owner-freebsd-alpha Tue Oct 26 16: 9:27 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 3B49714CEC for ; Tue, 26 Oct 1999 16:09:23 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40396>; Wed, 27 Oct 1999 09:04:21 +1000 Content-return: prohibited Date: Wed, 27 Oct 1999 09:09:13 +1000 From: Peter Jeremy Subject: Re: Multia booting woes In-reply-to: <19991026205726.A52927@gsmx07.alcatel.com.au> To: freebsd-alpha@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct27.090421est.40396@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <19991026205726.A52927@gsmx07.alcatel.com.au> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1999-Oct-26 20:57:26 +1000, I wrote: >Latest try: I've dd'd releases/3.2-RELEASE/floppies/boot.flp from >3.2-RELEASE CD-ROM 2 onto a SCSI disk, stuck the disk into the Multia >and it still dies (log below). I put the disk back onto my 386 box and re-checked the contents. This showed about half-a-dozen random bytes were not what I (thought I) wrote. I re-dd'd the boot image and all is now working. I have no idea why the data was corrupted. Sorry for the false alarm. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message