Fsck Fatal Error
Contents |
Expert Users Expert-to-Expert. Learn advanced UNIX, UNIX commands, Linux, Operating Systems, System Administration, Programming, Shell, Shell Scripts, Solaris, Linux, HP-UX, AIX, OS X, BSD. Search Forums Show Threads Show
Fsck Example
Posts Tag Search Advanced Search Unanswered Threads Find All Thanked Posts Go to Page... fsck solaris learn unix and linux commands Superblock marked dirty UNIX for Advanced & Expert Users Page 1 of
Fsck Unix
2 1 2 > Thread Tools Search this Thread Display Modes #1 01-28-2013 Castelior Registered User Join Date: Apr 2004 Last Activity: 5 January 2015, 5:27 AM fsck aix EST Location: /FRANCE/Nantes Posts: 96 Thanks: 12 Thanked 0 Times in 0 Posts Superblock marked dirty Good morning! I met a problem on a FS with AIX 5.3 It's not possible to mount the FS because of a dirty superblock. I tried few things without success. I need your help to solve my problem guys. Do you have any idea please? Thanks a lot Code: drp01,/home/root # mount /GSPRES/data Replaying how to run fsck in solaris log for /dev/lvdt1. Fatal: I/O error mount: 0506-324 Cannot mount /dev/lvdt1 on /GSPRES/data: The media is not formatted or the format is not correct. 0506-342 The superblock on /dev/lvdt1 is dirty. Run a full fsck to fix. drp01,/home/root # fsck -y -p /GSPRES/data The current volume is: /dev/lvdt1 Primary superblock is valid. J2_LOGREDO:log redo processing for /dev/lvdt1 Fatal: I/O error exec module "/sbin/helpers/jfs2/logredo64" failed. logredo failed (rc=5). fsck continuing. Primary superblock is valid. *** Phase 1 - Initial inode scan *** Phase 2 - Process remaining directories *** Phase 3 - Process remaining files *** Phase 4 - Check and repair inode allocation map *** Phase 5 - Check and repair block allocation map Block allocation map is corrupt (FIXED) Superblock marked dirty because repairs are about to be written. Fatal: I/O error drp01,/home/root # dd count=1 bs=4k skip=31 seek=1 if=/dev/lvdt1 of=/dev/lvdt1 1+0 records in. 1+0 records out. drp01,/home/root # mount /GSPRES/data Replaying log for /dev/lvdt1. Fatal: I/O error mount: 0506-324 Cannot mount /dev/lvdt1 on /GSPRES/data: The media is not formatted or the format is not correct. 0506-342 The superblock on /dev/lvdt1 is dirty. Run a full fsck to fix. drp01,/home/root # lsfs /GSPRES/data Name Nodename Mount Pt VFS Size Options Auto Accounting /dev/lvdt1 -- /GSPRES/data jfs2 87451238
2009 Basics, Featured, File system, Performance, Tips 1 Comment fsck is a Unix utility for checking and repairing file system inconsistencies . File system can become inconsistent due
Fsck Command In Solaris
to several reasons and the most common is abnormal shutdown due to hardware how does fsck work failure , power failure or switching off the system without proper shutdown. Due to these reasons the superblock in a
Fsck Ufs
file system is not updated and has mismatched information relating to system data blocks, free blocks and inodes . fsck - Modes of operation : fsck operates in two modes interactive and http://www.unix.com/unix-for-advanced-and-expert-users/214371-superblock-marked-dirty.html non interactive : Interactive - fsck examines the file system and stops at each error it finds in the file system and gives the problem description and ask for user response whether to correct the problem or continue without making any change to the file system. Non interactive :fsck tries to repair all the problems it finds in a file system without stopping for user http://www.adminschoice.com/repairing-unix-file-system-fsck response useful in case of a large number of inconsistencies in a file system but has the disadvantage of removing some useful files which are detected to be corrupt . If file system is found to have problem at the booting time non interactive fsck is run and all errors which are considered safe to correct are corrected. But if still file system has problems the system boots in single user mode asking for user to manually run the fsck to correct the problems in file system Running fsck : fsck should always be run in a single user mode which ensures proper repair of file system . If it is run in a busy system where the file system is changing constantly fsck may see the changes as inconsistencies and may corrupt the file system . If the system can not be brought in a single user mode fsck should be run on the partitions ,other than root & usr , after unmounting them . Root & usr partitions can not be unmounted . If the system fails to come up due to root/usr files system corruption the system can be booted with
New fsck Error MessagesNext: Initialization Phase fsck MessagesGeneral fsck Error Messages The error messages in this section might be displayed in any phase after initialization. Although they https://docs.oracle.com/cd/E19120-01/open.solaris/819-2380/tsfsck-30952/index.html offer the option to continue, it is generally best to regard them http://www.shrubbery.net/solaris9ab/SUNWaadm/SYSADV2/p104.html as fatal. They reflect a serious system failure and should be handled immediately. When confronted with such a message, terminate the program by entering n(o). If you cannot determine what caused the problem, contact your local service provider or another qualified person. CANNOT SEEK: BLK in solaris disk-block-number (CONTINUE) Solaris 10: CANNOT SEEK: BLK block-number (CONTINUE) Cause A request to move to the specified block number, disk-block-number, in the file system failed. This message indicates a serious problem, probably a hardware failure. Solaris 10: A request to move to the specified block number, block-number, in the file system failed. This message indicates a fsck fatal error serious problem, probably a hardware failure. If you want to continue the file system check, fsck will retry the move and display a list of sector numbers that could not be moved. If the block was part of the virtual memory buffer cache, fsck will terminate with a fatal I/O error message. Action If the disk is experiencing hardware problems, the problem will persist. Run fsck again to recheck the file system. If the recheck fails, contact your local service provider or another qualified person. CANNOT READ: DISK BLOCK disk-block-number: I/O ERROR CONTINUE? Solaris 10: CANNOT READ: DISK BLOCK block-number: I/O ERROR CONTINUE? Cause A request to read the specified block number, disk-block-number, in the file system failed. The message indicates a serious problem, probably a hardware failure. Solaris 10: A request to read a specified block number, block-number, in the file system failed. The message indicates a serious problem, probably a hardware failure. If you want to continue the file system check, fsck will retry the
in this chapter. "General fsck Error Messages" "Initialization Phase fsck Messages" "Phase 1: Check Blocks and Sizes Messages" "Phase 1B: Rescan for More DUPS Messages" "Phase 2: Check Path Names Messages" "Phase 3: Check Connectivity Messages" "Phase 4: Check Reference Counts Messages" "Phase 5: Check Cylinder Groups Messages" "Cleanup Phase Messages" For information about the fsck command and how to use it to check file system integrity, see "Checking File System Integrity (Tasks)" in System Administration Guide: Basic Administration. fsck Error Messages Normally, the fsck command is run non-interactively to preen the file systems after an abrupt system halt in which the latest file system changes were not written to disk. Preening automatically fixes any basic file system inconsistencies and does not try to repair more serious errors. While preening a file system, the fsck command fixes the inconsistencies it expects from such an abrupt halt. For more serious conditions, the command reports the error and terminates. When you run the fsck command interactively, it reports each inconsistency found and fixes innocuous errors. However, for more serious errors, the command reports the inconsistency and prompts you to choose a response. When you run the fsck command with the -y or -n options, your response is predefined as yes or no to the default response suggested by the fsck command for each error condition. Some corrective actions will result in some loss of data. The amount and severity of data loss might be determined from the fsck diagnostic output. The fsck command is a multipass file system check program. Each pass invokes a different phase of the fsck command with different sets of messages. After initialization, the fsck command performs successive passes over each file system, checking blocks and sizes, path names, connectivity, reference counts, and the map of free blocks (possibly rebuilding it). It also performs some cleanup. The phases (passes) performed by the UFS version of the fsck command are: Initialization Phase 1 - Check blocks and sizes Phase 2 - Check path names Phase 3 - Check connectivity Phase 4 - Check reference counts Phase 5 - Check cylinder groups The next sections describe the error conditions that might be detected in each phase, the messages and prompts that result, and possible responses you can make. Messages that might appear in more than one phase are described in "General fsck Error Messages". Otherwise, messages are organized alphabetically by the phases in which they occur. The following table lists many of the abbreviations included in the fsck error messages. Table 32-1 Err