error writing ufs log state solaris 10 Adams Basin New York

Address 2833 W Ridge Rd, Rochester, NY 14626
Phone (585) 225-4690
Website Link

error writing ufs log state solaris 10 Adams Basin, New York

According to the Sun doc: Root" disk encapsulated with VERITAS Volume Manager (VxVM) 3.2, 3.5, 4.0 or 4.1 and with ufs logging Go to Solution 3 Comments LVL 38 Overall: SunOS Release 5.10 Version Generic_118833-36 64-bit Copyright 1983-2006 Sun Microsystems, Inc. Virtualization FreeBSD Unix OS Advertise Here 769 members asked questions and received personalized solutions in the past 7 days. Notices Welcome to, a friendly and active Linux Community.

With ASM and Oracle RAC we no longer have the need.Thanks for the info.rhuggaThe problem is not so much with the log being bad, technically whathappens is that we scan the The Solaris OS is now owned by Oracle. and how do I get rid off them? I started this with the idea of making a series of articles from it, but maybe it'd be better to put something like this onto ?

y MISSING '.' I=189225 OWNER=root MODE=40555 SIZE=512 MTIME=Jun 2 12:29 2006 DIR=/wordm2 FIX? This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. this will happen not earlier then the vxvm startup script hasfinishedwhich is way too late for root when mounted with logging.the ordering of the messages gives a hint on this as I ran fsck 3 times.Any ideas anoyone,thx,rhuggaDo you have a Veritas encapsulated root filesystem?

Let us know MenuExperts Exchange Browse BackBrowse Topics Open Questions Open Projects Solutions Members Articles Videos Courses Contribute Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Ask AFAIK, this is a jumper setting on a SCSI disk. Is ufs logging trying to replay some transactions? /net/mercury/... Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory

y MISSING '..' I=189225 OWNER=root MODE=40555 SIZE=512 MTIME=Jun 2 12:29 2006 DIR=/wordm2 FIX? My,and I suspect, your only solution is to boot single-user from CD :-(Depending on your filesystem structure, the system might continue to runto some extent - only you can determine that.But WARNING: /[email protected],600000/SUNW,[email protected]/[email protected],0/[email protected],0 (ssd0): Error for Command: write Error Level: Fatal Requested Block: 0 Error Block: 0 Vendor: SEAGATE Serial Number: 0245A0CZWP Write protect error during write ASC: 0x Sense Key: Write I have tried to reboot in single user mode, but the same error I was getting.

y, "steeles" wrote in message news:Tf%[email protected] Hi Richard, Hope you can help me further. Solved! Thanks in Advance. -- prasad This message posted from Next Message by Date: Documentation on writing filesystems for Solaris Hi, I have a series of articles in the works that I suspect that Veritas is getting in the way somehow, andalthough I am not a Veritas expert at all, there are many who contributehere.

Click Here to receive this Complete Guide absolutely free. Block 0 is where I would start looking for things like the boot block, volume label, etc. And now I can't even boot it up, here is what I got, it just stuck there. Labels: Business Continuity Solaris Storage Foundation 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution!

But OpenSolaris needs filesystems (think ntfs, Linux ext[23]/reiser/jfs/xfs, ...), and there are people in the community who already have started such projects; a writeup "this is how it _can_ be done" If it doesn't work, tell me. and how do I get rid off them? Probing system devices Probing memory Probing I/O buses Sun Fire V210, No Keyboard Copyright 1998-2004 Sun Microsystems, Inc.

The / file system (/dev/rdsk/c1t0d0s0) is being checked. Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Support Communities Information Governance Is this something critical orsomething I can fix w/o booting from a CD?Thx,rhugga--Is the log state really bad or is it just a false positive?

They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Forum Operations by The UNIX and Linux Forums Support Community Training Contact Community turn on suggestions Auto-suggest helps you quickly narrow n If I say "yes" to remove that file, it will give me a whole bunch errors, then fail. References: Re: Help: hard drive issue From: steeles Prev by Date: Re: Help: hard drive issue Next by Date: Re: Help: hard drive issue Previous by thread: Re: Help: hard drive

the message itself will appear if the UFS logging code gets I/O errors of all sorts while reading/writing the ondisk log. How can I boot up from CD and fix it and make it bootable? The strange thing is that I can't issue "refresh" or "test", it keeps saying the disk is write protected. (I boot from cdrom as well to single user mode). Ethernet address 0:3:ba:ea:a8:91, Host ID: 83eaa891.

also look into the inkernel state via: `# echo "::fsinfo" |mdb -k` --- frankB Thread at a glance: Previous Message by Date: ufs_log: WARNING: I am getting the following messages after SEE THE SOLUTION Me too Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content AdvUniMD Solaris write errors during failover ‎2011-08-02 01:46 AM Make sure that y ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? Y 166177 files, 14823362 Disk problem?

No biggie,we are migrating away from Veritas anyways, since we use ufs withlogging almost exclusively now and all our RAID is done via hardwareon our SAN. Search Forums Show Threads Show Posts Tag Search Advanced Search Unanswered Threads Find All Thanked Posts Go to Page... unix and linux operating commands Help: root partition crashed, fsck PKGINST: VRTSvxvm NAME: VERITAS Volume Manager, Binaries CATEGORY: system ARCH: sparc VERSION: 4.0,REV=12.06.2003.01.35 BASEDIR: / VENDOR: VERITAS Software DESC: Virtual Disk Subsystem PSTAMP: of production serversI would like to know what else I have to check before rebooting the server, so that I can avoid such issue. 1.

Hopefully other people in this NG will havebetter ideas.Beardy.Actually I ended up booting from CD an fsck'ing the filesystem severaltimes and I still get that error on boot. Reply 0 Kudos « Message Listing « Previous Topic Next Topic » MORE IN COMMUNITY Learn How to Get Started Community Help Community Code of Conduct Provide Community Feedback Forums Blogs Boot a Live CD, it doesn't matter which (Ubuntu, Solaris, ...), it just has to have fsck. General Sun, SunOS and Sparc related questions also go here.

and how do I get rid off them? Thanks for feedback, Frank Previous Message by Thread: ufs_log: WARNING: I am getting the following messages after a reboot of Solaris 10 FCS machine: ufs_log:WARNING: Error writing ufs log state ufs_log:WARNING: y ** Last Mounted on / ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames UNALLOCATED I=191002 OWNER=root MODE=0 SIZE=0 MTIME=Feb 1 00:00 2008 NAME=/dbs/system_7.d4 REMOVE?