Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA Path: utzoo!linus!philabs!cmcl2!seismo!brl-tgr!tgr!evins@NRL-RADAR.ARPA From: evins@NRL-RADAR.ARPA Newsgroups: net.unix-wizards Subject: Problem w/ B/1 Message-ID: <1075@brl-tgr.ARPA> Date: Wed, 28-Aug-85 16:20:30 EDT Article-I.D.: brl-tgr.1075 Posted: Wed Aug 28 16:20:30 1985 Date-Received: Thu, 29-Aug-85 08:40:36 EDT Sender: news@brl-tgr.ARPA Lines: 26 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 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 . 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