Subject: Re: Root login refused on TTY!
To: Rick Copeland <rickgc@calweb.com>
From: Brian D Chase <bdc@world.std.com>
List: port-vax
Date: 05/24/1998 12:44:47
On Sun, 24 May 1998, Rick Copeland wrote:


> howto 0x0, bdev 0x11, booting...done. (31332+22252)
> 
> >> NetBSD/vax boot [970702 21:52] <<
> : /netbsd
> 700416+38912+75784 start 0x9c078
> [ netbsd symbol table not valid ]
> Copyright (c) 1996, 1997 The NetBSD Foundation, Inc.  All rights reserved.
> Copyright (c) 1982, 1986, 1989, 1991, 1993
>     The Regents of the University of California.  All rights reserved.
> 
> NetBSD 1.3 (GENERIC) #1: Fri Jan 16 16:09:22 CET 1998
>     ragge@multivac:/usr/hej/src/sys/arch/vax/compile/GENERIC
> 
> realmem = 25077760
> avail mem = 19966976
> Using 1224 buffers containing 1253376 bytes of memory.
> backplane0 (root)
> cpu0 at backplane0: MicroVAX 3500/3600
> cpu0: CVAX microcode rev 4 Firmware rev 83
> uba0 at backplane0: Q22
> mtc0 at uba0 csr 174500 vec 774 ipl 17
> mscpbus0 at mtc0: version 3 model 14
> mscpbus0: DMA burst size set to 4
> mt0 at mscpbus0 drive 0: TK70
> uda0 at uba0 csr 172150 vec 770 ipl 17
> mscpbus1 at uda0: version 6 model 13
> mscpbus1: DMA burst size set to 4
> ra0 at mscpbus1 drive 0: RA72
> qe0 at uba0 csr 174440 vec 764 ipl 17
> qe0: delqa, hardware address 08:00:2b:0b:48:ee
> boot device: ra0
> root on ra0a dumps on ra0b
> ra0: size 1953300 sectors
> root file system type: ffs
> Automatic boot in progress: starting file system checks.
> /dev/rra0a: 378 files, 8207 used, 1424 free (8 frags, 177 blocks, 0.1% fragmenta
> tion)
> /dev/rra0a: MARKING FILE SYSTEM CLEAN
> /dev/rra0e: 5996 files, 87268 used, 364008 free (3744 frags, 45033 blocks, 0.8%
> fragmentation)
> /dev/rra0e: MARKING FILE SYSTEM CLEAN
> /dev/rra0g: file system is clean; not checking

> 12d: not found
> setting tty flags
> starting network
> 12d: not found

Those "12d: not found" messages a slighty bothersome.  I've no idea what
they mean, and I guess that's why they don't set right with me.  Had you
ever previously attempted to install NetBSD/vax on this drive, maybe back
in the days of 1.2D?  Just a guess.  Could be remnants from a previous
install.

> configuring network interfaces:.
> WARNING:  no swap space configured!

Did you set up the disk without any swap?  Yeah sure you've got plenty of
memory, but what about someday when you want to do some high-resolution
3D rendering on your uber-VAX and that RAM just isn't quite enough? :-)  

> starting system logger
> checking for core dump...
> savecore: no core dump
> starting rpc daemons: portmap.
> mount_ffs: /dev/ra0g on /export: No such file or directory

That's interesting.  Sounds like either your /etc/fstab doesn't quite
match up with the disk partitioning, or something's gone horribly wrong
here.

> starting nfs daemons:.
> creating runtime link editor directory cache.
> checking quotas: done.
> building databases...
> clearing /tmp
> updating motd.
> standard daemons: update cron.
> starting network daemons: inetd.
> starting local daemons:.
> Sun May 24 03:31:49 PDT 1998
> May 24 03:31:50  init: kernel security level changed from 0 to 1
> 
> NetBSD/vax (Amnesiac) (console)
> 
> login: root
> root login refused on this terminal.
> May 24 03:31:56  login: LOGIN root REFUSED ON TTY rra0h
> login:

And then this is quite a gem.  It's refusing a login on a device name
which would normally be the raw device name for a disk partition.
Methinks /dev is at least partially trashed.

>From here I would probably be inclined to rebuild my /dev.  Boot to single
user mode...  Er, hmm... I'm not sure if there's a way to do this from the
boot prompt. (?)  

To port-vax: Anyone know how to put a system in single user mode when
   you can't explicitly edit the /etc/rc.conf or by sending a TERM signal
   to pid 1 from the multi-user state?  Basically, is there a bootflag to
   do this?

Once you get it in single user mode, cd to /dev and run a `./MAKEDEV all'.
If that doesn't clear things up, you may need to remove the existing
devices first and then re-run `./MAKEDEV all'.

I suspect something went wrong with how the drive was copied, so you may
find some other problems as well.  The above boot time messages indicate
some potential problems with the partitioning perhaps.

-brian.
---
Brian "JARAI" Chase | http://world.std.com/~bdc/ | VAXZilla LIVES!!!