Error Writing Ufs Log State
accessing ufs log for /mnt; Please run fsck(1M) mount: I/O error mount: cannot mount /dev/dsk/c1t0d0s0 # umount /a # mount /dev/dsk/c1t0d0s0 /a WARNING: Error accessing ufs log for /a; Please run fsck(1M) mount: I/O error mount: cannot mount /dev/dsk/c1t0d0s0 # I ran fsck, # fsck /dev/dsk/c1t0d0s0 ** /dev/dsk/c1t0d0s0 WARNING: Error writing ufs log state WARNING: ufs log for / changed state to Error WARNING: Please umount(1M) / and run fsck(1M) WARNING: Error writing master during ufs log roll WARNING: ufs log for / changed state to Error WARNING: Please umount(1M) / and run fsck(1M) Can't roll the log for /dev/dsk/c1t0d0s0. DISCARDING THE LOG MAY DISCARD PENDING TRANSACTIONS. DISCARD THE LOG AND CONTINUE? 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? n If I say "yes" to remove that file, it will give me a whole bunch errors, then fail. REMOVE? y CANNOT READ: BLK 3146654 CONTINUE? y, "steeles"
known simply as Solaris, is a Unix-based operating system introduced by Sun Microsystems. The Solaris OS is now owned by Oracle. Search Forums Show Threads Show Posts Tag Search Advanced Search Unanswered Threads Find All Thanked Posts Go to Page... learn unix and linux commands Help: root partition crashed, fsck failed. Disk problem? Solaris Tags fsck Thread Tools Search this Thread Display Modes #1 02-04-2008 steeles Registered User Join Date: Jan 2007 Last Activity: 4 February 2008, 5:07 AM EST Posts: 2 Thanks: 0 Thanked 0 Times in 0 Posts Help: root partition crashed, fsck failed. Disk problem? recently this sunfire 280R http://unix.derkeiler.com/Newsgroups/comp.sys.sun.admin/2008-02/msg00005.html (solaris 10) is having problme, it was able to boot up, then all suddent, it failed, and I can't even mount the first disk which contains root partition when I boot up from cdrom. 2 X 36G hard drive, I scan first hard drive by "read", there is no bad block. 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 http://www.unix.com/solaris/52129-help-root-partition-crashed-fsck-failed-disk-problem.html to single user mode). Partition: Code: Part Tag Flag Cylinders Size Blocks 0 root wm 1936 - 24619 31.25GB (22684/0/0) 65534076 1 swap wu 0 - 361 510.65MB (362/0/0) 1045818 2 backup wm 0 - 24619 33.92GB (24620/0/0) 71127180 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned wm 0 0 (0/0/0) 0 6 unassigned wm 0 0 (0/0/0) 0 7 var wm 363 - 1935 2.17GB (1573/0/0) 4544397 Here is the result for fsck. Code: # fsck /dev/dsk/c1t0d0s0 ** /dev/dsk/c1t0d0s0 WARNING: Error writing ufs log state WARNING: ufs log for / changed state to Error WARNING: Please umount(1M) / and run fsck(1M) WARNING: Error writing master during ufs log roll WARNING: ufs log for / changed state to Error WARNING: Please umount(1M) / and run fsck(1M) Can't roll the log for /dev/dsk/c1t0d0s0. DISCARDING THE LOG MAY DISCARD PENDING TRANSACTIONS. DISCARD THE LOG AND CONTINUE? Y ** Last Mounted on / ** Phase 1 - Check Blocks and Sizes PARTIALLY TRUNCATED INODE I=191000 SALVAGE? y ** 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? y CANNOT READ: BLK 3146654 CONTINUE? y THE FOLLOWING SECTORS COULD NOT BE READ: DIRECTORY CORRUPTED I=189225 OWNER=root MODE=40555 SIZE=512 MTIME=Jun 2 12:29 2006 DIR=/wordm2 SALVAGE? y MISSING '.' I=189225 OWNER=root MODE=40555 SIZE=512 MTIME=Jun 2 12:29 2006 DI
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers https://www.experts-exchange.com/questions/21595805/warning-message-during-the-boot-message-FSCK.html Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > warning message during the boot message - FSCK Want to Advertise Here? Solved warning message during the boot message - FSCK Posted on 2005-10-14 Unix OS 1 Verified Solution 3 Comments 2,681 Views Last Modified: 2013-12-27 Please help me with this , we have veritas volume manager installed, the root disk is encapsulated and i find this warning message at the startup. during boot up we see this WARNING: Error writing ufs error writing log state WARNING: ufs log for / changed state to Error WARNING: Please umount(1M) / and run fsck(1M) the vfstab file is bellow : dbss:${PWD} #cat /etc/vfstab #device device mount FS fsck mount mount #to mount to fsck point type pass at boot options # fd - /dev/fd fd error writing ufs - no - /proc - /proc proc - no - /dev/vx/dsk/bootdg/swapvol - - swap - no - /dev/vx/dsk/bootdg/rootvol /dev/vx/rdsk/bootdg/rootvol / ufs 1 no - /dev/vx/dsk/bootdg/var /dev/vx/rdsk/bootdg/var /var ufs 1 no - swap - /tmp tmpfs - yes size=1024m #NOTE: volume rootvol (/) encapsulated partition c1t0d0s0 #NOTE: volume swapvol (swap) encapsulated partition c1t0d0s1 #NOTE: volume var (/var) encapsulated partition c1t0d0s5 /dev/vx/dsk/bootdg/stage /dev/vx/rdsk/bootdg/stage /stage ufs - yes logging,largefiles,suid /dev/vx/dsk/bootdg/u01 /dev/vx/rdsk/bootdg/u01 /u01 ufs - yes logging,largefile,suid /dev/vx/dsk/oradg/u202 /dev/vx/rdsk/oradg/u202 /u202 ufs - yes logging,largefile 0 Question by:p0sreed Facebook Twitter LinkedIn Google LVL 38 Best Solution byyuzh Which version of Solaris and VERITAS Volume Manager are you using? 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: Level 38 Unix OS 32 Message Accepted Solution by:yuzh2005-10-16 Which version of Solaris and VERITAS Volume Manager are you using? 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 enabled may result in persistent warning messages, and in some cases the system may panic