Date: Sat, 4 Oct 1997 10:49:35 -0600 (MDT) From: Cowan Bowman <cowan@cyberport.com> To: Jaye Mathisen <mrcpu@cdsnet.net> Cc: questions@FreeBSD.ORG Subject: Re: /dev/rccd1c: CAN'T CHECK FILE SYSTEM Message-ID: <Pine.BSI.3.95.971004102519.24212A-100000@hippo.cyberport.com> In-Reply-To: <Pine.NEB.3.95.971003173939.540q-100000@mail.cdsnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 3 Oct 1997, Jaye Mathisen wrote: > > Some of the memory limits are too low in login.conf for the /etc/rc > settings. > > Raise them. > > A quick fix is to do: > > /bin/csh > unlimit > fsck drives > ^D a few times until it finished booting. I raised all the memory limits to infinity in login.conf for /etc/rc and still recieved the original error. Out of couriosity I rearanged the entries in my fstab file so it would check /dev/rccd1c before /dev/rccd0c, then finally /dev/rsd3a. ccd0 contains sd1a and sd2a. ccd1 contains sd4a and sd5a. The original fstab file was the following /dev/rsd0a / /dev/rsd0s2e /tmp /dev/rsd0s3b /swap /dev/rsd0s4e /usr /dev/ccd0 /news /dev/sd3a /alt /dev/ccd1 /alt.binaries The boot sequence in the original post by me at the bottom shows the error I would get with the above fstab settings. I changed the fstab to the following and recieved a slightly different error. /dev/rsd0a / /dev/rsd0s2e /tmp /dev/rsd0s3b /swap /dev/rsd0s4e /usr /dev/ccd1 /alt.binaries /dev/ccd0 /news /dev/sd3a /alt Here is a copy of the boot sequence with the fstab changes. Automatic Reboot in progress... /dev/rsd0a: clean, 41139 free (363 frags, 5097 blocks, 0.6% fragmentation) /dev/rsd0s2e: clean, 127054 free (14 frags, 15880 blocks, 0.0% fragmentation) /dev/rsd0s4e: clean, 1375393 free (8913 frags, 170810 blocks, 0.6% fragmentation) /dev/rccd1c: clean, 8214362 free (10 frags, 1026794 blocks, 0.0 fragmentation) cannot alloc 2979842 bytes for lncntp /dev/rccd0c: CAN'T CHECK FILE SYSTEM. /dev/rccd0c: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Automatic file system check failed... help! Enter pathname of shell or RETURN for sh: <RETURN> erase ^H, kill ^U, intr ^C # fsck -p /dev/rccd0c /dev/rccd0c: clean, 6139467 free (11 frags, 767432 blocks, 0.0% fragmentation) # exit ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Device busy ccdconfig: ioctl (CCDIOCSET): /dev/ccd1c: Device busy Skipping disk checks ... [continues to boot through network and starting daemons.] END of Boot Sequence. It looks like as soon as it tries to fsck a second ccd device it get the error. All the memory limits in etc.conf have been raised to infinity. The system is a Pentium Pro 200 with 128 Megs of memory. If anyone has any further Ideas, I would appreciate your comments. It would be nice to get the system to boot without any manual intervention. Thanks, Cowan > > On Fri, 3 Oct 1997, Cowan Bowman wrote: > > > > > I get the following error when my system boots. > > > > [Boots mesages previous to these are OK] > > > > /dev/rccd0c:clean, 6139467 free (11 frags, 767432 blocks, 0.0% fragmentation) > > /dev/rsd3a:clean, 4069357 free (13 frags, 508668 blocks, 0.0% fragmentation) > > cannot alloc 1989121 bytes for statemap > > /dev/rccd1c: CAN'T CHECK FILE SYSTEM. > > /dev/rccd1c: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > > Automatic file system check failed... help! > > Enter pathname of shell or RETURN for sh: > > > > > > I hit enter to go into single user mode, run fsck manually, it checks out > > fine. I exit and it continues to boot without any problems. > > > > Anyone have any Ideas what is happening? > > If any more info is needed mail me and I'll reply with the info. > > > > Thanks, Cowan > > > ------------------------------------------------------------------------ Cowan L. Bowman | Cyberport Station System Administrator/Accounting | Four Corner's Finest Internet Access cowan@cyberport.com | http://www.cyberport.com | Voice: 505-324-6400 Fax: 505-324-6401
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.95.971004102519.24212A-100000>