Date: Thu, 12 Mar 1998 07:41:11 -0600 From: Richard Wackerbarth <rkw@dataplex.net> To: freebsd-stable@FreeBSD.ORG Subject: New kernel slice code still has problems Message-ID: <l03130300b12d90094bfc@[208.2.87.4]>
next in thread | raw e-mail | index | archive | help
I have been running a late February 2.2.5. Last night, I
rebuilt the world to try the new kernel changes.
When I attempted to reboot a new kernel, everything went
fine until ...
It gave the message that it was changing the root to sd0s5a.
It then failed, saying that it cannot mount root.
The only way up is to reboot with the old kernel.
I consider this "broken-ness" a serious problem for the "stable"
branch.
At a minimum, I need to know what I need to do to configure a new
kernel that will boot.
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 65536 0 4.2BSD 0 0 0 # (Cyl. 0 - 31)
b: 282608 65536 swap # (Cyl. 32 - 169*)
c: 4178874 0 unused 0 0 # (Cyl. 0 - 2040*)
e: 61440 348144 4.2BSD 0 0 0 # (Cyl. 169*- 199)
f: 3769290 409584 4.2BSD 0 0 0 # (Cyl. 199*- 2040*)
shrimp: {6} df
Filesystem 512-blocks Used Avail Capacity Mounted on
/dev/sd0a 63550 56212 2254 96% /
/dev/sd3e 1013214 235922 696236 25% /usr
procfs 8 8 0 100% /proc
/dev/sd1a 4053342 880786 2848290 24% /pub/FreeBSD
/dev/sd3f 1519838 235186 1163066 17% /home
/dev/sd3g 1013214 82 932076 0% /tmp
/dev/sd0f 3656040 876530 2487028 26% /mnt
shrimp: {7} cd /usr/src/sys/i386/conf
You have new mail.
shrimp: {8} grep sd DATAPLEX
config kernel root on sd0
# type. For example, if you wire a disk as "sd3" then the first
# non-wired disk will be assigned sd4.
disk sd0 at scbus0 target 0
disk sd1 at scbus0 target 1
disk sd2 at scbus0 target 2
disk sd3 at scbus0 target 4
device sd4 #SCSI disks
Richard Wackerbarth
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?l03130300b12d90094bfc>