evins@NRL-RADAR.ARPA (08/28/85)
We have a VAX 11/750 running 4.2 BSD [BRL] UNIX, with two RA81 disks. The problem is that when doing a B/1, the system does not boot into single user mode. Instead, when it should enter single user mode, it simply sits there. I will then hit a <CR> and it will procede to invoke /etcrc and go through the fsck disk checks. When I first took charge of this system, it seemed to correctly using B/1 once. The next time I booted the system, it immediately invoked /etc/rc, and fsck found problems with ra0a: INCORRECT BLOCK COUNT I=33 (2 should be 0) (CORRECTED) 1 BLK(S) MISSING BAD CYLINDER GROUPS (SALVAGED) It then procedded to reboot itself, and just before invoking /etc/rc, it just sat there, until I hit a <CR>. I do notice that I had not run 'sync' before the second reboot that I mention. This is when the problem started. My question is: could fsck have damaged the boot block in an attempt to fix something, possibly because I did not run 'sync'? Or, could this be some other problem? Thanks. -Jim Evins
davest%lumiere%tek.uucp@CSNET-RELAY.ARPA (08/29/85)
You use B/2 to bring a 750 up single-user. As has been mentioned on this list before, set your console's baud rate to 1200 to avoid needing to hit <CR> on reboot. The problem is one of flow control. When fsck is run on the root filesystem and a problem is corrected, you should in fact NOT sync before rebooting. This is something that has also been discussed onthis list. -- David C. Stewart uucp: tektronix!davest Small Systems Support Group csnet: davest@TEKTRONIX Tektronix, Inc. phone: (503) 627-5418