Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nexus.coast.net!simtel!news.sprintlink.net!newsie.dmc.com!news.iii.net!iii1.iii.net!not-for-mail From: hdslip@iii1.iii.net (HD Associates) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Help! CAN'T CHECK FILE SYSTEM Error Date: 21 Jun 1995 05:11:06 -0400 Organization: HD Associates, Inc. Lines: 40 Message-ID: <3s8nnt$g0s@iii1.iii.net> References: <3s5pbe$i1m@gandalf.pic.net> NNTP-Posting-Host: iii1.iii.net In article <3s5pbe$i1m@gandalf.pic.net>, <mglaris@pic.net> wrote: >Help, > >I had a brief power failure, just enough to reboot the computer, and >now FreeBSD will not boot. Upon restart, I get the following error >messages: > >Can't open /dev/rcd0d: Device Not Configured >/dev/rcd0d: CAN'T CHECK FILE SYSTEM >/dev/rcd0d: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY >Automatic file system check failed... help! "/dev/rcd0d" is a CD. Since you can't change the data on it you don't have to fsck it. You have an entry in /etc/fstab to mount the CD at boot up. If you want that, then change the pass number in /etc/fstab to 0 and fsck won't try to check it. It should be something similar to: > /dev/cd0d /cd cd9660 ro 0 0 >I then enter a shell and run fsck like I was told. Device >/dev/rsd0a and /dev/rsd0e seem to check out (at least, there are no >messages that look like error messages). It then reports: > >Can't open /dev/rcd0d: Device not configured The system can't open your CD device. Maybe your CD player isn't powered up? Maybe you don't have a CD player? Look through your "dmesg" output for lines that show the system recognizing your CD; they should be right near where it sees your disks. If this is the only problem on power up just ignore the error, type "^D" and fix things when the system comes up. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267