Jesse Parkerton wrote:

>... So now when I boot it, it gets through the file system check then:
>
>Can't open /dev/rsd1A: Device not configured
>CAN'T CHECK FILE SYSTEM
>/dev/rsd1a: UNEXPECTED INCONSISTENCY; RUN fsck_ffs Manually
>Automatic file system check failed; help!
>Enter path name of shell RETURN for sh:
>Terminal Type?
>
>    So I turned the system of and botted into OS 7 and reran build devices
>in the installer app.  I rebooted and that fixed it.  I booted a couple of
>days later, same thing.  But rebuild devices again doesn't fix it.  That's
>as far as I can get.  Can someone talk me through this?


Argh. :-)  You should be doing fsck ("FileSystem ChecK") instead
of build devices.  OK, here goes:

  1) Hit return when it stops at the "Terminal type" prompt.
     You should see a  #  shell prompt.

  2) Type   mount   at the prompt -- with any luck, /dev/rsd1a
     is mounted read-only (or better yet, not at all). If not,
     you need to re-mount it read-only (mount -o ro  and there
     may be an option I'm forgetting)

  3) After verifying that it's mounted read-only, type
     fsck /dev/rsd1a

        ******* You do NOT want to run fsck on a *******
        ******* filesystem mounted read-write!   *******

  4) If you get lots of "fix this?' messages, hit Ctrl-C and type
     fsck -y /dev/rsd1a   to let the computer answer yes to all
     those silly prompts.

  5) When it finishes, repeat the fsck command. It should check out
     clean, but I once had a seriously horked-up filesystem that
     required three fsck runs to fix completely. (Compiling a large
     program, running NetBSD from a Jaz drive, will cause this kind
     of heartburn if you want to experience it for yourself. I also
     learned about attributes that way.)

  6) After fsck runs with no errors, press Ctrl-D to escape
     single-user mode and continue with the normal boot.


In general, I hope you shut the computer down by typing
shutdown -h now   instead of just turning it off -- that's
real bad mojo on a Un*x box & could easily cause your
problems.

--
Larry Kollar, Senior Technical Writer, ARRIS

All parts should go together without forcing.  You must remember that
the parts you are reassembling were disassembled by you.  Therefore,
if you can't get them together again, there must be a reason.  By all
means, do not use a hammer.
         -- IBM maintenance manual, 1925



-- 
MaX-list is sponsored by <http://lowendmac.com/> and...

    /      Buy books, CDs, videos, and more from Amazon.com     \
   / <http://www.amazon.com/exec/obidos/redirect-home/lowendmac> \

      Support Low End Mac <http://lowendmac.com/lists/support.html>

MaX-list info:          <http://lowendmac.com/linux/max.shtml>
Send list messages to:  <mailto:[EMAIL PROTECTED]>
To unsubscribe, email:  <mailto:[EMAIL PROTECTED]>
For digest mode, email: <mailto:[EMAIL PROTECTED]>
Subscription questions: <mailto:[EMAIL PROTECTED]>
Archive: <http://www.mail-archive.com/max-list%40mail.maclaunch.com/>

Using a Macintosh? Get free email and more at Applelinks! 
<http://www.applelinks.com>

Reply via email to