NetBSD Problem Report #10022
Received: (qmail 10480 invoked from network); 30 Apr 2000 22:54:28 -0000
Message-Id: <200004302252.AAA26580@rumolt.teuto.de>
Date: Mon, 1 May 2000 00:52:49 +0200 (MEST)
From: Martin Husemann <martin@rumolt.teuto.de>
Reply-To: martin@rumolt.teuto.de
To: gnats-bugs@gnats.netbsd.org
Subject: current bootblocks don't boot from wd0a
X-Send-Pr-Version: 3.95
>Number: 10022
>Category: port-i386
>Synopsis: current bootblocks don't boot from wd0a
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: port-i386-maintainer
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Apr 30 22:55:00 +0000 2000
>Closed-Date: Fri Oct 20 12:36:47 +0000 2000
>Last-Modified: Fri Oct 20 12:36:47 +0000 2000
>Originator: Martin Husemann
>Release: Arpil 30, 2000
>Organization:
>Environment:
System: NetBSD rumolt.teuto.de 1.4X NetBSD 1.4X (RUMOLT) #0: Sun Apr 30 19:15:21 MEST 2000 martin@rumolt.teuto.de:/usr/src/sys-i4b/arch/i386/compile/RUMOLT i386
>Description:
Installing bootblocks from -current as of today prohibits booting from
hard disk (wd0a in my case).
The last known working bootblocks are from a snapshot by tron late in March
this year.
>How-To-Repeat:
shutdown now
cd /usr/mdec
./installboot -v -f biosboot.sym /dev/rwd0a
reboot, be hosed
>Fix:
n/a
(If you don't count creating bootblocks on your friendly 1.4.2 system
as a solution)
>Release-Note:
>Audit-Trail:
From: "Perry E. Metzger" <perry@piermont.com>
To: martin@rumolt.teuto.de
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: port-i386/10022: current bootblocks don't boot from wd0a
Date: 30 Apr 2000 19:02:23 -0400
Martin Husemann <martin@rumolt.teuto.de> writes:
> shutdown now
> cd /usr/mdec
> ./installboot -v -f biosboot.sym /dev/rwd0a
> reboot, be hosed
How *exactly* are you hosed? Can you explain precisely what happens?
From: Martin Husemann <martin@rumolt.teuto.de>
To: perry@piermont.com (Perry E. Metzger)
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: port-i386/10022: current bootblocks don't boot from wd0a
Date: Mon, 1 May 2000 01:11:06 +0200 (MEST)
> How *exactly* are you hosed? Can you explain precisely what happens?
You can use this bootblocks to boot from floppy.
But not from wd0a:
try booting from a floppy with that bootblocks and do:
> dev wd0a:
> ls
*hang*
(where *hang* means IDE LED permananently on, nothing happens for 10 or
more minutes)
I've seen this on now on a variety of systems with small (less than 512 MB),
medium (less than 2 GB) and large ( > 20 GB ) disks, BIOSs of all flavours
(with and without LBA support).
Anything newer than aprox. April 1 didn't work for me anywhere.
Installing the bootblocks from images I fetched at end of march always
fixed it, besides I now need custom serial bootblocks.
Martin
State-Changed-From-To: open->feedback
State-Changed-By: simonb
State-Changed-When: Fri Oct 20 05:27:15 PDT 2000
State-Changed-Why:
Is this still an issue for you? I installed a fresh machine with
a recent 1.5_ALPHA2 snapshot and had no bootblock troubles.
State-Changed-From-To: feedback->closed
State-Changed-By: simonb
State-Changed-When: Fri Oct 20 05:36:09 PDT 2000
State-Changed-Why:
Mail to PR submitter bounced, and problem believed not to exist anymore.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.