Subject: Re: "sysinst" failure: "mount_ffs: /dev/sd0d on /usr: Device not configured" printed
To: Allen Briggs <briggs@wasabisystems.com>
From: Boo Geum Jung <bgjung@etri.re.kr>
List: port-sandpoint
Date: 03/13/2002 21:42:17
sysinst is executed on netbsd.GENERIC with nfs.
So, I setup file system at sd0.

=====================
biomask 20 netmask 30 ttymask 30
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 6 lun 0: <IBM, DDYS-T18350N, S96H> SCSI3 0/direct
fixed
sd0: 17501 MB, 15110 cyl, 6 head, 395 sec, 512 bytes/sect x 35843670 sectors
sd0: sync (50.0ns offset 16), 16-bit (40.000MB/s) transfers, tagged queueing
boot device: <unknown>
root device: sd0a
dump device (default sd0b):
file system (default generic):
root on sd0a dumps on sd0b
root file system type: ffs
Enter pathname of shell or RETURN for sh:
We recommend creating a non-root account and using su(1) for root access.
# df
Filesystem  1K-blocks     Used     Avail Capacity  Mounted on
root_device     84715    39441     41038    49%    /
# mount /usr
mount_ffs: /dev/sd0d on /usr: Device not configured
# swapctl -A
swapctl: adding /dev/sd0b as swap device at priority 0
# swapctl -l
Device      1K-blocks     Used    Avail Capacity  Priority
/dev/sd0b       67545        0    67545     0%    0
# exit
Thu Mar 14 04:06:10 GMT 2002
swapctl: /dev/sd0b: Device busy
Starting file system checks:
/dev/rsd0a: 2050 files, 39441 used, 45274 free (26 frags, 5656 blocks, 0.0%
frag
mentation)
/dev/rsd0a: MARKING FILE SYSTEM CLEAN
Can't open /dev/rsd0d: Device not configured
CAN'T CHECK FILE SYSTEM.
/dev/rsd0d: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY.
THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY:
        ffs: /dev/rsd0d (/usr)
Automatic file system check failed; help!
Setting tty flags.
Setting sysctl variables:
Starting network.
Hostname: sandpoint1.etri.re.kr
add net 127.0.0.0: gateway 127.0.0.1
Configuring network interfaces: fxp0.
add net default: gateway 129.254.180.1
Adding interface aliases:
Building databases...
kvm_mkdb: not found
dev_mkdb: not found
install: not found
Checking for core dump...
savecore: /dev/wd0a: Device not configured
Mounting all filesystems...
mount_ffs: /dev/sd0d on /usr: Device not configured
Clearing /tmp.
find: not found
Checking quotas:eval: /usr/sbin/quotacheck: not found
 done.
eval: /usr/sbin/quotaon: not found
Setting securelevel: kern.securelevel: 0 -> 1
grep: not found
Updating motd.
sed: not found
cmp: not found
starting local daemons:.
logger: not found
/etc/rc: WARNING: $ipfs is not set properly.
logger: not found
/etc/rc: WARNING: $ifwatchd is not set properly.
Thu Mar 14 04:06:14 GMT 2002
Mar 14 04:06:14 init: can't exec getty '/usr/libexec/getty' for port
/dev/tty00:
 No such file or directory
Mar 14 04:06:44 init: can't exec getty '/usr/libexec/getty' for port
/dev/tty00:
 No such file or directory
Mar 14 04:07:14 init: can't exec getty '/usr/libexec/getty' for port
/dev/tty00:
 No such file or directory
Mar 14 04:07:44 init: can't exec getty '/usr/libexec/getty' for port
/dev/tty00:
 No such file or directory
Mar 14 04:08:14 init: can't exec getty '/usr/libexec/getty' for port
/dev/tty00:
 No such file or directory
<== Nothing appeared anymore.

=====================

----- Original Message -----
From: "Allen Briggs" <briggs@wasabisystems.com>
To: "Boo Geum Jung" <bgjung@etri.re.kr>
Cc: <port-sandpoint@netbsd.org>
Sent: Friday, March 08, 2002 12:47 AM
Subject: Re: "sysinst" failure


> On Wed, Mar 07, 2001 at 02:50:46PM +0900, Boo Geum Jung wrote:
> > Could not open /etc/disktab
> > sysinst terminated.
> > Should I put disktab at /etc directory in ramdisk.fs?
>
> That's probably a good start.  I think there are other problems that you
> may run into with sysinst.  I haven't had a chance to look at it, but I
> did have it terminate on me in several cases.
>
> You can install by hand, though.  Basically, you need to:
>
> 1. Use the disklabel program to initialize and partition your
>    disk,
>
> 2. Use newfs to make a filesystem on selected partitions,
>
> 3. Mount the filesystems,
>
> 4. Transfer the distribution files or NFS mount them,
>
> 5. Unpack the distribution files, and
>
> 6. Configure the timezone, /etc/rc.conf, passwords, etc...
>
> -allen
>
> --
>  Allen Briggs                     briggs@wasabisystems.com
>  http://www.wasabisystems.com/    Quality NetBSD CDs, Sales, Support,
Service
> NetBSD development for Alpha, ARM, M68K, MIPS, PowerPC, SuperH, XScale,
etc...
>