Re: Error writing ufs log state problem
From: Thomas Hildebrandt - Sun Germany - ES - SSE (thomas.hildebrandt_at_sun.com)
Date: 10/20/04
- Next message: Daniel Wetzler: "Re: NFS-problem (crashing mashine)"
- Previous message: Mike Miller: "Re: NFS/autofs problem"
- Next in thread: Keg: "Re: Error writing ufs log state problem"
- Reply: Keg: "Re: Error writing ufs log state problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 20 Oct 2004 13:53:23 +0200
Keg,
this problem has been introduced lately by some Veritas patch ... The
recommended workaround is to abandon the logging feature until this
problem has been resolved (i.e., remount your root w/ nologging and make
the appropriate changes in /etc/vfstab).
HIH,
- Thomas
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
-- -- Thomas Hildebrandt
- Next message: Daniel Wetzler: "Re: NFS-problem (crashing mashine)"
- Previous message: Mike Miller: "Re: NFS/autofs problem"
- Next in thread: Keg: "Re: Error writing ufs log state problem"
- Reply: Keg: "Re: Error writing ufs log state problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|