Re: Error writing ufs log state problem

From: Keg (rhugga_at_yahoo.com)
Date: 09/24/04

  • Next message: Beardy: "Re: Error writing ufs log state problem" 
    Date: 24 Sep 2004 08:07:41 -0700

    Beardy <beardy@beardy.net> wrote in message news:<41534cd1$0$42247$ed2e19e4@ptn-nntp-reader04.plus.net>...
    > Keg wrote:
    > > I am getting this error during boot of a Solaris 9 64-bit system.
    > >
    > > ...
    > > jnic146x1: Target9: Lun28 supported.
    > > jnic146x1: Target9: Lun29 supported.
    > > jnic146x1: Target9: Lun30 supported.
    > > jnic146x1: Target9: Lun31 supported.
    > > WARNING: Error writing ufs log state
    > > WARNING: ufs log for / changed state to Error
    > > WARNING: Please umount(1M) / and run fsck(1M)
    > > Starting VxVM restore daemon...
    > > VxVM starting in boot mode...
    > > ...
    > >
    > > I am remotely managing this machine so I can't boot from CD at the
    > > moment to fsck the root filesystem. Is this something critical or
    > > something I can fix w/o booting from a CD?
    > >
    > > Thx,
    > > rhugga
    >
    > I have had this once, and was left with a read-only root filesystem. My,
    > and I suspect, your only solution is to boot single-user from CD :-(
    > Depending on your filesystem structure, the system might continue to run
    > to some extent - only you can determine that.
    >
    > But if the system panics, and you have a bad log area for root, I
    > suspect that you *will* be paying a visit ;-)
    >
    > Apols for being no help. Hopefully other people in this NG will have
    > better ideas.
    >
    >
    > Beardy.

    Actually I ended up booting from CD an fsck'ing the filesystem several
    times and I still get that error on boot. When I performed the fsck's,
    it found no problems as all. I ran fsck 3 times.

    Any ideas anoyone,
    thx,
    rhugga

  • Next message: Beardy: "Re: Error writing ufs log state problem"

    Relevant Pages