NetBSD Problem Report #40358

From hannken@eis.cs.tu-bs.de  Sat Jan 10 14:57:54 2009
Return-Path: <hannken@eis.cs.tu-bs.de>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by narn.NetBSD.org (Postfix) with ESMTP id E8E0163B8BA
	for <gnats-bugs@gnats.netbsd.org>; Sat, 10 Jan 2009 14:57:54 +0000 (UTC)
Message-Id: <20090110145750.77FBBE2761@watcher.eis.cs.tu-bs.de>
Date: Sat, 10 Jan 2009 15:57:50 +0100 (MET)
From: hannken@eis.cs.tu-bs.de
Reply-To: hannken@eis.cs.tu-bs.de
To: gnats-bugs@gnats.netbsd.org
Subject: i386 cannot boot 2nd disk
X-Send-Pr-Version: 3.95


>Number:         40358
>Category:       port-i386
>Synopsis:       i386 cannot boot 2nd disk
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jan 10 15:00:00 +0000 2009
>Last-Modified:  Sun Sep 13 23:05:02 +0000 2009
>Originator:     Juergen Hannken-Illjes
>Release:        NetBSD 5.99.6
>Organization:

	
>Environment:

	

	
>Description:
	It is impossible to boot NetBSD from the 2nd disk because
	the biosdisk_open() always sets the BTINFO_BOOTDISK property.
	Unfortunately it is called from module_open() for the 1st disk and
	therefore the loaded kernel believes the boot disk to be hd0.

	
>How-To-Repeat:
	Try "boot hd1a:netbsd".

	
>Fix:
	Yes, please ...

	


>Audit-Trail:
From: Juergen Hannken-Illjes <hannken@eis.cs.tu-bs.de>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: port-i386/40358: i386 cannot boot 2nd disk
Date: Sun, 11 Jan 2009 10:41:44 +0100


 Addendum:
 	It looks more consistent if modules were loaded from the
 	disk the kernel resides on.

 
 -- 
 Juergen Hannken-Illjes - hannken@eis.cs.tu-bs.de - TU Braunschweig (Germany)

 
From: David Laight <david@l8s.co.uk>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-i386/40358: i386 cannot boot 2nd disk
Date: Sun, 11 Jan 2009 10:47:37 +0000


 On Sun, Jan 11, 2009 at 09:45:02AM +0000, Juergen Hannken-Illjes wrote:
 > 
 >  Addendum:
 >  	It looks more consistent if modules were loaded from the
 >  	disk the kernel resides on.

 
 One related issue is that the kernel isn't necessarily loaded from
 the root filesystem.

 
 I've sometimes thought of changing /boot to pass the kernel a different
 root filesystem, but couldn't think of the command syntax.
 But it can easily be done with 'boot -i'.

 
 	David

 
 -- 
 David Laight: david@l8s.co.uk

 
From: Juergen Hannken-Illjes <hannken@eis.cs.tu-bs.de>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: port-i386/40358: i386 cannot boot 2nd disk
Date: Sun, 18 Jan 2009 13:50:12 +0100


 Addendum 2:
 	It looks like this bug is present in 5.0_BETA too.

 
 -- 
 Juergen Hannken-Illjes - hannken@eis.cs.tu-bs.de - TU Braunschweig (Germany)

 
From: "Jared D. McNeill" <jmcneill@invisible.ca>
To: <gnats-bugs@NetBSD.org>
Cc: 
Subject: Re: port-i386/40358
Date: Sun, 13 Sep 2009 19:02:33 -0400


 Does the following change resolve your issue?

 
   http://mail-index.netbsd.org/source-changes/2009/09/13/msg000854.html

 
 Thanks,
 Jared

 
>Unformatted:

 	

 	

Home	PR Database Search