Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 8 May 1995 21:47:03 -0700 (PDT)
From:      "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
To:        wsantee@wsantee.oz.net (Wes Santee)
Cc:        freebsd-current@FreeBSD.org
Subject:   Re: Getting "device not configured" from swapon
Message-ID:  <199505090447.VAA00905@gndrsh.aac.dev.com>
In-Reply-To: <199505090432.VAA00350@wsantee.oz.net> from "Wes Santee" at May 8, 95 09:32:48 pm

next in thread | previous in thread | raw e-mail | index | archive | help
> 
> Hey all.
> 
> I just re-sliced my second drive to include another 10 Megs of swap.
> Now when I boot I get the following message:
> 
> swapon: /dev/wd1b: device not configured
> 
> Here is the important disklabel info from /dev/wd1:
> 
> #        size   offset    fstype   [fsize bsize bps/cpg]
>   a:   173400    61455    4.2BSD     1024  8192    16 	# (Cyl.  241 - 920)
>   b:    20400   234855      swap                    	# (Cyl.  921 - 1000)
>   c:   193800    61455    unused        0     0       	# (Cyl.  241 - 1000)
>   d:   255255        0    unused        0     0       	# (Cyl.    0 - 1000)
>   e:    61200      255    unused        0     0       	# (Cyl.    1 - 240)
> 
> and here is the /etc/fstab file:
> 
> /dev/wd0a		/	ufs rw 1 1
> /dev/wd1a		/var	ufs rw 1 1
> /dev/wd0f		/msdos	msdos rw 1 1
> /dev/wd0b		none	swap sw 0 0
> /dev/wd1b		none	swap sw 0 0
> proc			/proc	procfs rw 0 0

What does ``swapinfo'' say?  Do you have ``swap on wd0 and wd1'' in
your kernel config file:

config		kernel	root on wd0 swap on wd0 and wd1 dumps on wd0


> The /dev/wd0b swap slice is coming up fine.  Anybody know what might
> be going on?  I did accidentally newfs /dev/wd1b along with /dev/wd1a
> but I figured that the swapper would ignore the formatting since it
> likes a raw slice.  This is where the error may lie, but I don't know
> how to 're-clean' the partition (I tried re-writing the disklabel and
> only newfs-ing the /dev/wd1a slice).

You should disklabel -e -r wd1 and set partiton b: to be what you
showed above.  The newfs operation probably set b: to be of type
4.2BSD.


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                   Custom computers for FreeBSD



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505090447.VAA00905>