NetBSD Problem Report #25585

Received: (qmail 6685 invoked by uid 605); 15 May 2004 22:10:31 -0000
Message-Id: <200405152218.i4FMIjD7024292@snowdrop.l8s.co.uk>
Date: Sat, 15 May 2004 23:18:45 +0100 (BST)
From: dsl@netbsd.org
Sender: gnats-bugs-owner@NetBSD.org
Reply-To: dsl@netbsd.org
To: gnats-bugs@gnats.netbsd.org
Subject: Cannot boot an alternate root fs if a raid device is marked 'root'
X-Send-Pr-Version: 3.95

>Number:         25585
>Category:       kern
>Synopsis:       Cannot boot an alternate root fs if a raid device is marked 'root'
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat May 15 22:11:00 +0000 2004
>Closed-Date:    
>Last-Modified:  Sun May 16 18:16:01 +0000 2004
>Originator:     David Laight
>Release:        NetBSD 2.0E
>Organization:
>Environment:


Current as of May 14 2004
Architecture: i386
Machine: i386
>Description:
	If I mark a raid set '-A root raid0' then all attepts to boot
	that system use the raid set as the root filesystem - regardless
	as to what is typed to the boot prompt.

	This makes it impossible to have multiple systems on the same
	machine.
>How-To-Repeat:
>Fix:
	Dunno... 
	The current behaviour is usually done by building a kernel with the
	relevant root fs embedded in it.
	IMHO the raid set should only become the root fs if a normal boot
	would have booted a fs in the disk space that holds the raid set.
>Release-Note:
>Audit-Trail:

From: Greg Oster <oster@cs.usask.ca>
To: dsl@netbsd.org
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/25585: Cannot boot an alternate root fs if a raid device is marked 'root' 
Date: Sat, 15 May 2004 16:48:57 -0600

 dsl@netbsd.org writes:
 > 
 > >Number:         25585
 > >Category:       kern
 > >Synopsis:       Cannot boot an alternate root fs if a raid device is marked 
 > 'root'
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    kern-bug-people
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Sat May 15 22:11:00 UTC 2004
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     David Laight
 > >Release:        NetBSD 2.0E
 > >Organization:
 > >Environment:
 > 	
 > 	
 > Current as of May 14 2004
 > Architecture: i386
 > Machine: i386
 > >Description:
 > 	If I mark a raid set '-A root raid0' then all attepts to boot
 > 	that system use the raid set as the root filesystem - regardless
 > 	as to what is typed to the boot prompt.
 > 
 > 	This makes it impossible to have multiple systems on the same
 > 	machine.

 Hmm... last time I looked, if 'boothowto' was set correctly, 
 RAIDframe would not override it, and you can set the root partition 
 to be whatever you want.....  Are you booting with the '-a' option?

 > >How-To-Repeat:
 > >Fix:
 > 	Dunno... 
 > 	The current behaviour is usually done by building a kernel with the
 > 	relevant root fs embedded in it.
 > 	IMHO the raid set should only become the root fs if a normal boot
 > 	would have booted a fs in the disk space that holds the raid set.
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted:

 Later...

 Greg Oster



From: David Laight <david@l8s.co.uk>
To: Greg Oster <oster@cs.usask.ca>
Cc: dsl@netbsd.org, gnats-bugs@gnats.netbsd.org
Subject: Re: kern/25585: Cannot boot an alternate root fs if a raid device is marked 'root'
Date: Sun, 16 May 2004 18:39:07 +0100

 > Hmm... last time I looked, if 'boothowto' was set correctly, 
 > RAIDframe would not override it, and you can set the root partition 
 > to be whatever you want.....  Are you booting with the '-a' option?

 No, just a standard boot where /boot passes the root filesystem
 details into the kernel.

 I have thought of changing the boot command syntax so that it is
 possible to tell the kernel that the root fs is somewhere other
 than where the kernel was loaded from.  However I couldn't think
 of an easy extension to 'boot wd0a:netbsd' :-(

 This would be most useful if/when /boot can read a script file.

 	David

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

From: Greg Oster <oster@cs.usask.ca>
To: David Laight <david@l8s.co.uk>
Cc: gnats-bugs@gnats.netbsd.org, dsl@netbsd.org
Subject: Re: kern/25585: Cannot boot an alternate root fs if a raid device is marked 'root' 
Date: Sun, 16 May 2004 12:15:28 -0600

 David Laight writes:
 > > Hmm... last time I looked, if 'boothowto' was set correctly, 
 > > RAIDframe would not override it, and you can set the root partition 
 > > to be whatever you want.....  Are you booting with the '-a' option?
 > 
 > No, just a standard boot where /boot passes the root filesystem
 > details into the kernel.

 Ahh...  Do you know what/how those details are captured?  Mayhaps 
 it's just a matter of tweaking the checks in rf_netbsdkintf.c to make 
 it behave properly... 

 > I have thought of changing the boot command syntax so that it is
 > possible to tell the kernel that the root fs is somewhere other
 > than where the kernel was loaded from.  However I couldn't think
 > of an easy extension to 'boot wd0a:netbsd' :-(

 boot wd0a:netbsd root:wd1a

 ?  

 Kinda mixing metaphors... 

 > This would be most useful if/when /boot can read a script file.
 > 
 > 	David
 > 
 > -- 
 > David Laight: david@l8s.co.uk

 Later...

 Greg Oster


>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.