Re: Error writing ufs log state problem

From: Beardy (beardy_at_beardy.net)
Date: 09/24/04 

Date: Thu, 23 Sep 2004 23:24:41 +0000

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.

Relevant Pages

  • Re: Error writing ufs log state problem
    ... recommended workaround is to abandon the logging feature until this ... > Starting VxVM restore daemon... ... > VxVM starting in boot mode... ... > moment to fsck the root filesystem. ...
    (comp.sys.sun.admin)
  • ATAng problems
    ... which my root filesystem is residing. ... If I choose 'Safe mode' in the boot menu, ... <ACPI PCI bus> on pcib0 ... on ppbus0 ...
    (freebsd-current)
  • Re: Making a zpool bootable on an x86 system
    ... The context is that we have a system which had a UFS root filesystem, we've done a live upgrade to ZFS, and either mistakes have been made or LU doesn't work right, or something, so it will not now boot. ... displays "grub> " from where we could may be work out how to proceed but actually can't due to stupidity or tiredness (I think this must be stage2 loading but not finding a menu?); ... My feeling is that there must be some concrete set of steps to do, involving installing bootblocks and configuring the menu file which will make the machine bootable, assuming the zpool is OK, which I think it is, but I don't know what it is. ...
    (comp.unix.solaris)
  • Re: Debian Unstable wont boot on 2.6.15-1/grub/raid1
    ... If I boot up on 2.6.16-1 the system will ... busybox shell. ... udev is not involved until after the root filesystem is mounted. ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". ...
    (Debian-User)
  • Re: No controller detected when boot FreeBSD 7.0
    ... with hptrrand (unlike the usual behaviour of most Raid Controller ... affect the other -- but that changing the way the boot messages are displayed has managed to draw your attention to it. ... Manul root filesystem specification: ... but it seems that no disk devices were found... ...
    (freebsd-questions)