Date: Tue, 19 Aug 1997 19:12:11 -0400 From: Randall Hopper <rhh@ct.picker.com> To: questions@freebsd.org Subject: Question about "sysinstall" Errors Message-ID: <19970819191211.29132@ct.picker.com>
next in thread | raw e-mail | index | archive | help
I'm trying to do something I think should be very simple -- run
sysinstall on an installed system to allocate a sizable free slice of disk
to FreeBSD. This will be "wd1s2", with the intent of having:
wd1s2b: 128Meg - SWAP
wd1s2e: the rest - UFS @ /share3
FDISKING in sysinstall worked flawlessly:
Custom-Partition-wd1-Create-<CR>-<CR>-Write-Yes
Then, I got the new slice layed out in the disklabel editor:
Label-Create-128M-SWAP-Create-<CR>-FS-/share3
So far, looks good. I try to "Write" and I get:
"Unable to add /dev/wd1s2b as a swap device: Device not configured"
ktracing sysinstall, I see it's trying to:
swapon( "/dev/wd1s2b" )
I'm wonderering why--I can do that later. Going on, it then immediately
forks off:
newfs -b 8192 -f 1024 /dev/rwd1s2e
It appears there was no "disklabel" before this, so newfs fails. I guess
sysinstall doesn't check the newfs command for failure since it then goes
on and tries to mount the partition:
mount( ..., "/share3", ..., "/dev/wd1s2e" )
which returns Invalid argument yielding the:
"Error mounting /dev/wd1s2e on /share3 : Invalid argument" dialog.
If I try the "newfs -b 8192 -f 1024 /dev/rwd1s2e" by hand in the shell, I
get:
"newfs: /dev/rwd1s2e: `e' partition is unavailable"
The /dev/rwd1s2e does exist, and "disklabel wd1s2" in the shell confirms
the slice was never disklabeled (all blocks are in "c").
Am I doing something wrong here? I'd welcome any tips, suggestions, and
even "Enlightening Flames". Before I resort to disklabeling via cmd-line,
I'd like to make sure that sysinstall isn't an option -- it's definitely
the kinder, gentler, safer way to go for users if it works.
Thanks,
Randall
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970819191211.29132>