Solaris 10 error writing ufs log state

solaris 10 error writing ufs log state

(8) The system cannot be booted (ufs logging errors). To boot from a CD-ROM device, use the medium of Solaris 10 5/08 or earlier. To restore Solaris I am getting this error during boot of a Solaris 9 bit system. jnicx1: Target9: Lun28 supported. WARNING: ufs log for / changed state to Error. Insert a bootable Solaris CD/DVD and boot into single-user mode with boot cdrom -s Feb 9 sol10zone login: ROOT LOGIN /dev/console.

youtube video

Solaris 10 Basic Commands: Part 1

Final: Solaris 10 error writing ufs log state

Solaris 10 error writing ufs log state
PSPCOMIC SDL_IMAGE ERROR OUT OF MEMORY
Call of duty 5 direct x error
FATAL ERROR 121 OKI PRINTER
Solaris 10 error writing ufs log state

Solaris 10 error writing ufs log state - that

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 or 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 2a &#; Check Duplicated Names

  • Phase 2b &#; Check Pathnames

  • Phase 3 &#; Check Connectivity

  • Phase 3b &#; Verify Shadows/ACLs

  • 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  Error Message Abbreviations

Abbreviation

Meaning

Block number

Duplicate block number

Directory name

Cylinder group

Time file was last modified

Unreferenced

Many of the messages also include variable fields, such as inode numbers, which are represented in this book by an italicized term, such as . For example, this screen message:

INCORRECT BLOCK COUNT I=

is shown as follows:

INCORRECT BLOCK COUNT I=

General fsck Error Messages

The error messages in this section might be displayed in any phase after initialization. Although they offer the option to continue, it is generally best to regard them 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 (CONTINUE)

Solaris

CANNOT SEEK: BLK (CONTINUE)
Cause

A request to move to the specified block number, , in the file system failed. This message indicates a serious problem, probably a hardware failure.

Solaris A request to move to the specified block number, , in the file system failed. This message indicates a 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 : I/O ERROR CONTINUE?

Solaris

CANNOT READ: DISK BLOCK : I/O ERROR CONTINUE?
Cause

A request to read the specified block number, , in the file system failed. The message indicates a serious problem, probably a hardware failure.

Solaris A request to read a specified 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 read and display a list of sector numbers that could not be read. If the block was part of the virtual memory buffer cache, fsck will terminate with a fatal I/O error message. If fsck tries to write back one of the blocks on which the read failed, it will display the following 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 WRITE: BLK (CONTINUE)

Solaris

CANNOT WRITE: BLK (CONTINUE)
Cause

A request to write the specified block number, , in the file system failed.

If you continue the file system check, fsck will retry the write and display a list of sector numbers that could not be written. If the block was part of the virtual memory buffer cache, fsck will terminate with a fatal I/O error message.

Solaris A request to write a specified block number, , in the file system failed.

If you continue the file system check, fsck will retry the write and display a list of sector numbers that could not be written. If the block was part of the virtual memory buffer cache, fsck will terminate with a fatal I/O error message.

Action

The disk might be write-protected. Check the write-protect lock on the drive. If the disk has hardware problems, the problem will persist. Run fsck again to recheck the file system. If the write-protect is not the problem or the recheck fails, contact your local service provider or another qualified person.

Initialization Phase fsck Messages

In the initialization phase, command-line syntax is checked. Before the file system check can be performed, fsck sets up tables and opens files.

The messages in this section relate to error conditions resulting from command-line options, memory requests, the opening of files, the status of files, file system size checks, and the creation of the scratch file. All such initialization errors terminate fsck when it is preening the file system.

Can't roll the log for . DISCARDING THE LOG MAY DISCARD PENDING TRANSACTIONS. DISCARD THE LOG AND CONTINUE?
Cause

fsck was unable to flush the transaction log of a logging UFS file system prior to checking the file system for errors.

Action

Answering yes means the file system operations that were in the log, but had not been applied to the file system, are lost. In this case, fsck runs the same checks it always runs and asks the following question in phase 5:

FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGE)

Answering yes at this point reclaims the blocks that were used for the log. The next time the file system is mounted with logging enabled, the log will be recreated.

Answering no preserves the log and exits, but the file system isn't mountable.

bad inode number to ginode
Cause

An internal error occurred because of a nonexistent inode . fsck exits.

Action

Contact your local service provider or another qualified person.

cannot alloc bytes for blockmap cannot alloc bytes for freemap cannot alloc bytes for statemap cannot alloc bytes for lncntp
Cause

Request for memory for its internal tables failed. fsck terminates. This message indicates a serious system failure that should be handled immediately. This condition might occur if other processes are using a very large amount of system resources.

Action

Killing other processes might solve the problem. If not, contact your local service provider or another qualified person.

Can't open checklist file:
Cause

The file system checklist file (usually ) cannot be opened for reading. fsck terminates.

Action

Check if the file exists and if its access modes permit read access.

Can't open
Cause

fsck cannot open file system . When running interactively, fsck ignores this file system and continues checking the next file system given.

Action

Check to see if read and write access to the raw device file for the file system is permitted.

Can't stat root
Cause

fsck request for statistics about the root directory failed. fsck terminates.

Action

This message indicates a serious system failure. Contact your local service provider or another qualified person.

Can't stat Can't make sense out of name
Cause

fsck request for statistics about the file system failed. When running interactively, fsck ignores this file system and continues checking the next file system given.

Action

Check if the file system exists and check its access modes.

: (NO WRITE)
Cause

Either the -n option was specified or fsck could not open the file system for writing. When fsck is running in no-write mode, all diagnostic messages are displayed, but fsck does not attempt to fix anything.

Action

If -n was not specified, check the type of the file specified. It might be the name of a regular file.

IMPOSSIBLE MINFREE= IN SUPERBLOCK (SET TO DEFAULT)
Cause

The superblock minimum space percentage is greater than 99 percent or less than 0 percent.

Action

To set the parameter to the default 10 percent, type y at the default prompt. To ignore the error condition, type n at the default prompt.

: BAD SUPER BLOCK: USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; e.g., fsck[-f ufs] -o b=# [special ] where # is the alternate superblock. See fsck_ufs(1M)
Cause

The superblock has been corrupted.

Action

One of the following messages might be displayed:

CPG OUT OF RANGE FRAGS PER BLOCK OR FRAGSIZE WRONG INODES PER GROUP OUT OF RANGE INOPB NONSENSICAL RELATIVE TO BSIZE MAGIC NUMBER WRONG NCG OUT OF RANGE NCYL IS INCONSISTENT WITH NCG*CPG NUMBER OF DATA BLOCKS OUT OF RANGE NUMBER OF DIRECTORIES OUT OF RANGE ROTATIONAL POSITION TABLE SIZE OUT OF RANGE SIZE OF CYLINDER GROUP SUMMARY AREA WRONG SIZE TOO LARGE BAD VALUES IN SUPERBLOCK

Try to rerun fsck with an alternative superblock. Specifying block 32 is a good first choice. You can locate an alternative copy of the superblock by running the newfs -N command on the slice. Be sure to specify the -N option; otherwise, newfs overwrites the existing file system.

UNDEFINED OPTIMIZATION IN SUPERBLOCK (SET TO DEFAULT)
Cause

The superblock optimization parameter is neither nor .

Action

To minimize the time to perform operations on the file system, type y at the prompt. To ignore this error condition, type n.

Phase 1: Check Blocks and Sizes Messages

This phase checks the inode list. It reports error conditions encountered while:

  • Checking inode types

  • Setting up the zero-link-count table

  • Examining inode block numbers for bad or duplicate blocks

  • Checking inode size

  • Checking inode format

All errors in this phase except , , , and terminate fsck when it is preening a file system.

These messages (in alphabetical order) might occur in phase 1:

BAD I=
Cause

Inode contains a block number with a number lower than the number of the first data block in the file system or greater than the number of the last block in the file system. This error condition might generate the error message in phase 1 if inode has too many block numbers outside the file system range. This error condition generates the error message in phases 2 and 4.

Action

N/A

BAD MODE: MAKE IT A FILE?
Cause

The status of a given inode is set to all 1s, indicating file system damage. This message does not indicate physical disk damage, unless it is displayed repeatedly after fsck -y has been run.

Action

Type y to reinitialize the inode to a reasonable value.

BAD STATE TO BLKERR
Cause

An internal error has scrambled the fsck state map so that it shows the impossible value . fsck exits immediately.

Action

Contact your local service provider or another qualified person.

DUP I=

Solaris

DUP I=
Cause

Inode contains a block number , which is already claimed by the same or another inode. This error condition might generate the error message in phase 1 if inode has too many block numbers claimed by the same or another inode. This error condition invokes phase 1B and generates the error messages in phases 2 and 4.

Solaris Inode contains a block number , which is already claimed by the same or another inode. This error condition might generate the error message in phase 1 if inode has too many block numbers claimed by the same or another inode. This error condition invokes phase 1B and generates the error messages in phases 2 and 4.

Action

N/A

DUP TABLE OVERFLOW (CONTINUE)
Cause

fsck could not allocate memory to track duplicate fragments. If the -o p option is specified, the program terminates.

Solaris There is no more room in an internal table in fsck containing duplicate block numbers. If the -o p option is specified, the program terminates.

Action

To continue the program, type y at the prompt. When this error occurs, a complete check of the file system is not possible. If another duplicate fragment is found, this error condition repeats. Increase the amount of virtual memory available (by killing some processes, increasing swap space) and run fsck again to recheck the file system. To terminate the program, type n.

Solaris To continue the program, type y at the prompt. When this error occurs, a complete check of the file system is not possible. If another duplicate block is found, this error condition repeats. Increase the amount of virtual memory available (by killing some processes, increasing swap space) and run fsck again to recheck the file system. To terminate the program, type n.

EXCESSIVE BAD FRAGMENTS I=inode-number (CONTINUE)

Solaris

EXCESSIVE BAD BLOCKS I=inode-number (CONTINUE)
Cause

Too many (usually more than 10) fragments indicate an invalid disk address. If the -o p (preen) option is specified, the program terminates.

Solaris Too many (usually more than 10) blocks have a number lower than the number of the first data block in the file system or greater than the number of the last block in the file system associated with inode . If the -o p (preen) option is specified, the program terminates.

Action

To continue the program, type y at the prompt. When this error occurs, a complete check of the file system is not possible. You should run fsck again to recheck the file system. To terminate the program, type n.

EXCESSIVE DUP BLKSDUPLICATE FRAGMENTS I=inode-number (CONTINUE)

Solaris

EXCESSIVE DUP BLKS I=inode-number (CONTINUE)
Cause

Too many (usually more than 10) fragments are claimed by the same or another inode or by a free-list. If the -o p option is specified, the program terminates.

Solaris Too many (usually more than 10) blocks are claimed by the same or another inode or by a free-list. If the -o p option is specified, the program terminates.

Action

To continue the program, type y at the prompt. When this error occurs, a complete check of the file system is not possible. You should run fsck again to recheck the file system. To terminate the program, type n.

INCORRECT DISK BLOCK COUNT I=inode-number ( should be ) (CORRECT)

Solaris

INCORRECT BLOCK COUNT I=inode-number ( should be ) (CORRECT)
Cause

The disk block count for inode is incorrect.. When preening, fsck corrects the count.

Solaris The block count for inode is , but should be . When preening, fsck corrects the count.

Action

To correct the disk block count of inode by , type y at the prompt. .

Solaris To replace the block count of inode by , type y at the prompt. To terminate the program, type n.

LINK COUNT TABLE OVERFLOW (CONTINUE)
Cause

There is no more room in an internal table for fsck containing allocated inodes with a link count of zero. If the -o p (preen) option is specified, the program exits and fsck has to be completed manually.

Action

To continue the program, type y at the prompt. If another allocated inode with a zero-link count is found, this error condition repeats. When this error occurs, a complete check of the file system is not possible. You should run fsck again to recheck the file system. Increase the virtual memory available by killing some processes or increasing swap space, then run fsck again. To terminate the program, type n.

PARTIALLY ALLOCATED INODE I= (CLEAR)
Cause

Inode is neither allocated nor unallocated. If the -o p (preen) option is specified, the inode is cleared.

Action

To deallocate the inode by zeroing out its contents, type y. This might generate the error condition in phase 2 for each directory entry pointing to this inode. To ignore the error condition, type n. A no response is appropriate only if you intend to take other measures to fix the problem.

PARTIALLY TRUNCATED INODE I= (SALVAGE)
Cause

fsck has found inode whose size is shorter than the number of fragments allocated to it. This condition occurs only if the system crashes while truncating a file. When preening the file system, fsck completes the truncation to the specified size.

Solaris fsck has found inode whose size is shorter than the number of blocks allocated to it. This condition occurs only if the system crashes while truncating a file. When preening the file system, fsck completes the truncation to the specified size.

Action

To complete the truncation to the size specified in the inode, type y at the prompt. To ignore this error condition, type n.

UNKNOWN FILE TYPE I= (CLEAR)
Cause

The mode word of the inode shows that the inode is not a pipe, character device, block device, regular file, symbolic link, FIFO file, or directory inode. If the -o p option is specified, the inode is cleared.

Solaris The mode word of the inode shows that the inode is not a pipe, special character inode, special block inode, regular inode, symbolic link, FIFO file, or directory inode. If the -o p option is specified, the inode is cleared.

Action

To deallocate the inode by zeroing its contents, which results in the error condition in phase 2 for each directory entry pointing to this inode, type y at the prompt. To ignore this error condition, type n.

Solaris Phase 1B: Rescan for More DUPS Messages

This sections contains phase 1B fsck messages in the current Solaris release.

When a duplicate fragment is found in the file system, this message is displayed:

fragment DUP I=
Cause

Inode contains a fragment number that is already claimed by the same or another inode. This error condition generates the error message in phase 2. Inodes that have overlapping fragments might be determined by examining this error condition and the error condition in phase 1. This is simplified by the duplicate fragment report produced at the fsck run.

Action

When a duplicate block is found, the file system is rescanned to find the inode that previously claimed that block.

Phase 1B: Rescan for More DUPS Messages

This sections contains fsck messages if you are not running at least the Solaris Express 1/06 release and in the Solaris 10 release.

When a duplicate block is found in the file system, this message is displayed:

block-number DUP I=
Cause

Inode contains a block number that is already claimed by the same or another inode. This error condition generates the error message in phase 2. Inodes that have overlapping blocks might be determined by examining this error condition and the error condition in phase 1.

Action

When a duplicate block is found, the file system is rescanned to find the inode that previously claimed that block.

Phase 2: Check Path Names Messages

This phase removes directory entries pointing to bad inodes found in phases 1 and 1B. It reports error conditions resulting from:

  • Incorrect root inode mode and status

  • Directory inode pointers out of range

  • Directory entries pointing to bad inodes

  • Directory integrity checks

When the file system is being preened ( option), all errors in this phase terminate fsck, except those related to directories not being a multiple of the block size, duplicate and bad blocks, inodes out of range, and extraneous hard links.

These messages (in alphabetical order) might occur in phase 2:

BAD INODE TO DESCEND
Cause

An fsck internal error has passed an invalid state to the routine that descends the file system directory structure. fsck exits.

Action

If this error message is displayed, contact your local service provider or another qualified person.

BAD INODE NUMBER FOR '.' I= OWNER= MODE= SIZE= MTIME= DIR= (FIX)
Cause

A directory has been found whose inode number for &#;&#; does not equal .

Action

To change the inode number for &#;&#; to be equal to , type y at the prompt To leave the inode numbers for &#;&#; unchanged, type n.

BAD INODE NUMBER FOR '..' I= OWNER= MODE= SIZE= MTIME= DIR= (FIX)
Cause

A directory has been found whose inode number for &#;&#; does not equal the parent of .

Action

To change the inode number for &#;&#; to be equal to the parent of , type y at the prompt. (Note that &#;'' in the root inode points to itself.) To leave the inode number for &#;&#; unchanged, type n.

BAD RETURN STATE FROM DESCEND
Cause

An fsck internal error has returned an impossible state from the routine that descends the file system directory structure. fsck exits.

Action

If this message is displayed, contact your local service provider or another qualified person.

BAD STATE FOR ROOT INODE
Cause

An internal error has assigned an impossible state to the root inode. fsck exits.

Action

If this error message is displayed, contact your local service provider or another qualified person.

BAD STATE FOR INODE=
Cause

An internal error has assigned an impossible state to inode . fsck exits.

Action

If this error message is displayed, contact your local service provider or another qualified person.

DIRECTORY TOO SHORT I= OWNER= MODE= SIZE= MTIME= DIR= (FIX)
Cause

A directory has been found whose size is less than the minimum directory size. The owner , mode , size , modify time , and directory name are displayed.

Action

To increase the size of the directory to the minimum directory size, type y at the prompt. To ignore this directory, type n.

DIRECTORY : LENGTH NOT MULTIPLE OF (ADJUST)

Solaris

DIRECTORY : LENGTH NOT MULTIPLE OF (ADJUST)
Cause

A directory has been found with size that is not a multiple of the directory block size .

Solaris

A directory has been found with size that is not a multiple of the directory block size .

Action

To round up the length to the appropriate disk block size, type y. When preening the file system (-o p option), fsck only displays a warning and adjusts the directory. To ignore this condition, type n.

Solaris

To round up the length to the appropriate block size, type y. When preening the file system (-o p option), fsck only displays a warning and adjusts the directory. To ignore this condition, type n.

DIRECTORY CORRUPTED I= OWNER= MODE= SIZE= MTIME= DIR= (SALVAGE)
Cause

A directory with an inconsistent internal state has been found.

Action

To throw away all entries up to the next directory boundary (usually a byte boundary), type y at the prompt. This drastic action can throw away up to 42 entries. Take this action only after other recovery efforts have failed. To skip to the next directory boundary and resume reading, but not modify the directory, type n.

DUP/BAD I= OWNER=O MODE=M SIZE= MTIME= TYPE= (REMOVE)
Cause

Phase 1 or phase 1B found duplicate fragments or bad fragments associated with directory or file entry , inode . The owner , mode , size , modification time , and directory or file name are displayed. If the -op (preen) option is specified, the duplicate/bad fragments are removed.

Solaris

Phase 1 or phase 1B found duplicate blocks or bad blocks associated with directory or file entry , inode . The owner , mode , size , modification time , and directory or file name are displayed. If the -op (preen) option is specified, the duplicate/bad blocks are removed.

Action

To remove the directory or file entry , type y at the prompt. To ignore this error condition, type n.

DUPS/BAD IN ROOT INODE (REALLOCATE)
Cause

Phase 1 or phase 1B has found duplicate fragments or bad fragments in the root inode, ( inode number 20, of the file system.

Solaris

Phase 1 or phase 1B has found duplicate blocks or bad blocks in the root inode (usually inode number 2 of the file system.

Action

To clear the existing contents of the root inode and reallocate it, type y at the prompt. The files and directories usually found in the root inode will be recovered in phase 3 and put into the directory. If the attempt to allocate the root fails, fsck will exit with: . Type n to get the prompt. Type: y to respond to the prompt, and ignore the error condition in the root inode and continue running the file system check. If the root inode is not correct, this might generate many other error messages. Type n to terminate the program.

EXTRA '.' ENTRY I= OWNER= MODE= SIZE= MTIME= DIR= (FIX)
Cause

A directory has been found that has more than one entry for &#;&#;.

Action

To remove the extra entry for &#;&#; type y at the prompt. To leave the directory unchanged, type n.

EXTRA '..' ENTRY I= OWNER= MODE= SIZE= MTIME= DIR= (FIX)
Cause

A directory has been found that has more than one entry for &#;&#; (the parent directory).

Action

To remove the extra entry for `' (the parent directory), type y at the prompt. To leave the directory unchanged, type n.

IS AN EXTRANEOUS HARD LINK TO A DIRECTORY (REMOVE)
Cause

fsck has found an extraneous hard link to a directory . When preening (-o p option), fsck ignores the extraneous hard links.

Action

To delete the extraneous entry type y at the prompt. To ignore the error condition, type n.

OUT OF RANGE I= NAME= (REMOVE)
Cause

A directory entry has an inode number that is greater than the end of the inode list. If the -p (preen) option is specified, the inode will be removed automatically.

Action

To delete the directory entry type y at the prompt. To ignore the error condition, type n.

MISSING '.' I= OWNER= MODE= SIZE= MTIME= DIR= (FIX)
Cause

A directory has been found whose first entry (the entry for &#;&#;) is unallocated.

Action

To build an entry for &#;&#; with inode number equal to , type y at the prompt. To leave the directory unchanged, type n.

MISSING '.' I= OWNER= MODE= SIZE= MTIME= DIR= CANNOT FIX, FIRST ENTRY IN DIRECTORY CONTAINS
Cause

A directory has been found whose first entry is . fsck cannot resolve this problem.

Action

If this error message is displayed, contact your local service provider or another qualified person.

MISSING '.' I= OWNER= MODE= SIZE= MTIME= DIR= CANNOT FIX, INSUFFICIENT SPACE TO ADD '.'
Cause

A directory has been found whose first entry is not &#;&#;. fsck cannot resolve the problem.

Action

If this error message is displayed, contact your local service provider or another qualified person.

MISSING '..' I= OWNER= MODE= SIZE= MTIME= DIR= (FIX)
Cause

A directory has been found whose second entry is unallocated.

Action

To build an entry for &#;&#; with inode number equal to the parent of , type y at the prompt. (Note that &#;'' in the root inode points to itself.) To leave the directory unchanged, type n.

MISSING '..' I= OWNER= MODE= SIZE= MTIME= DIR= CANNOT FIX, SECOND ENTRY IN DIRECTORY CONTAINS
Cause

A directory has been found whose second entry is . fsck cannot resolve this problem.

Action

If this error message is displayed, contact your local service provider or another qualified person.

MISSING '..' I= OWNER= MODE= SIZE= MTIME= DIR= CANNOT FIX, INSUFFICIENT SPACE TO ADD '..'
Cause

A directory has been found whose second entry is not &#;&#; (the parent directory). fsck cannot resolve this problem.

Action

If this error message is displayed, contact your local service provider or another qualified person.

NAME TOO LONG
Cause

An excessively long path name has been found, which usually indicates loops in the file system name space. This error can occur if a privileged user has made circular links to directories.

Action

Remove the circular links.

ROOT INODE UNALLOCATED (ALLOCATE)
Cause

The root inode (usually inode number 2) has no allocate-mode bits.

Action

To allocate inode 2 as the root inode, type y at the prompt. The files and directories usually found in the root inode will be recovered in phase 3 and put into the directory. If the attempt to allocate the root inode fails, fsck displays this message and exits: . To terminate the program, type n.

ROOT INODE NOT DIRECTORY (REALLOCATE)
Cause

The root inode (usually inode number 2) of the file system is not a directory inode.

Action

To clear the existing contents of the root inode and reallocate it, type y at the prompt. The files and directories usually found in the root inode will be recovered in phase 3 and put into the directory. If the attempt to allocate the root inode fails, fsck displays this message and exits: . To have fsck prompt with , type n.

UNALLOCATED I= OWNER= MODE= SIZE= MTIME= type=(REMOVE)
Cause

A directory or file entry points to an unallocated inode . The owner , mode , size , modify time , and file name are displayed.

Action

To delete the directory entry , type y at the prompt. To ignore the error condition, type n.

ZERO LENGTH DIRECTORY I= OWNER= MODE= SIZE= MTIME= DIR= (REMOVE)
Cause

A directory entry has a size that is zero. The owner UID, mode , size , modify time , and directory name are displayed.

Action

To remove the directory entry , type y at the prompt. This results in the error message in phase 4. To ignore the error condition, type n.

Phase 3: Check Connectivity Messages

This phase checks the directories examined in phase 2 and reports error conditions resulting from:

  • Unreferenced directories

  • Missing or full directories

These messages (in alphabetical order) might occur in phase 3:

BAD INODE TO DESCEND
Cause

An internal error has caused an impossible state to be passed to the routine that descends the file system directory structure. fsck exits.

Action

If this occurs, contact your local service provider or another qualified person.

DIR I= CONNECTED. PARENT WAS I=
Cause

This is an advisory message indicating a directory inode was successfully connected to the directory. The parent inode of the directory inode is replaced by the inode number of the directory.

Action

N/A

DIRECTORY LENGTH NOT MULTIPLE OF (ADJUST)

Solaris

DIRECTORY LENGTH NOT MULTIPLE OF (ADJUST)
Cause

A directory has been found with size that is not a multiple of the directory block size B. (This condition can recur in phase 3 if it is not adjusted in phase 2.)

Action

To round up the length to the appropriate disk block size, type y at the prompt. When preening, fsck displays a warning and adjusts the directory. To ignore this error condition, type n.

Solaris

To round up the length to the appropriate block size, type y at the prompt. When preening, fsck displays a warning and adjusts the directory. To ignore this error condition, type n.

lost+found IS NOT A DIRECTORY (REALLOCATE)
Cause

The entry for is not a directory.

Action

To allocate a directory inode and change the directory to reference it, type y at the prompt. The previous inode reference by the directory is not cleared and it will either be reclaimed as an unreferenced inode or have its link count adjusted later in this phase. Inability to create a directory displays the message: and aborts the attempt to link up the lost inode, which generates the error message in phase 4. To abort the attempt to link up the lost inode, which generates the error message in phase 4, type n.

NO lost+found DIRECTORY (CREATE)
Cause

There is no directory in the root directory of the file system. When preening, fsck tries to create a directory.

Action

To create a directory in the root of the file system, type y at the prompt. This might lead to the message NO SPACE LEFT IN / (EXPAND). If the directory cannot be created, fsck displays the message: and aborts the attempt to link up the lost inode. This in turn generates the error message later in phase 4. To abort the attempt to link up the lost inode, type n.

NO SPACE LEFT IN /lost+found (EXPAND)
Cause

Another entry cannot be added to the directory in the root directory of the file system because no space is available. When preening, fsck expands the directory.

Action

To expand the directory to make room for the new entry, type y at the prompt. If the attempted expansion fails, fsck displays: and aborts the request to link a file to the directory. This error generates the error message later in phase 4. Delete any unnecessary entries in the directory. This error terminates fsck when preening is in effect. To abort the attempt to link up the lost inode, type n.

UNREF DIR I= OWNER= MODE= SIZE= MTIME= (RECONNECT)
Cause

The directory inode was not connected to a directory entry when the file system was traversed. The owner , mode , size , and modification time of directory inode are displayed. When preening, fsck reconnects the non-empty directory inode if the directory size is non-zero. Otherwise, fsck clears the directory inode.

Action

To reconnect the directory inode into the directory, type y at the prompt. If the directory is successfully reconnected, a message is displayed. Otherwise, one of the error messages is displayed. To ignore this error condition, type n. This error causes the error condition in phase 4.

Phase 4: Check Reference Counts Messages

This phase checks the link count information obtained in phases 2 and 3. It reports error conditions resulting from:

  • Unreferenced files

  • A missing or full directory

  • Incorrect link counts for files, directories, symbolic links, or special files

  • Unreferenced files, symbolic links, and directories

  • Bad or duplicate fragments in files and directories

    Solaris

    Bad or duplicate blocks in files and directories

  • Incorrect total free-inode counts

All errors in this phase (except running out of space in the directory) are correctable when the file system is being preened.

These messages (in alphabetical order) might occur in phase 4:

BAD/DUP I= OWNER= MODE= SIZE= MTIME= (CLEAR)
Cause

Phase 1 or phase 1B found duplicate fragments or bad fragments associated with file or directory inode . The owner , mode , size , and modification time of inode are displayed.

Solaris

Phase 1 or phase 1B found duplicate blocks or bad blocks associated with file or directory inode . The owner , mode , size , and modification time of inode are displayed.

Action

To deallocate inode by zeroing its contents, type y at the prompt. To ignore this error condition, type n.

(CLEAR)
Cause

The inode mentioned in the error message immediately preceding cannot be reconnected. This message does not display if the file system is being preened because lack of space to reconnect files terminates fsck.

Action

To deallocate the inode by zeroing out its contents, type y at the prompt. To ignore the preceding error condition, type n.

LINK COUNT I= OWNER= MODE= SIZE= MTIME= COUNT SHOULD BE corrected-link-count (ADJUST)
Cause

The link count for directory or file inode is but should be . The owner , mode , size , and modification time of inode are displayed. If the -o p option is specified, the link count is adjusted unless the number of references is increasing. This condition does not occur unless there is a hardware failure. When the number of references is increasing during preening, fsck displays this message and exits:

Action

To replace the link count of directory or file inode with , type y at the prompt. To ignore this error condition, type n.

lost+found IS NOT A DIRECTORY (REALLOCATE)
Cause

The entry for is not a directory.

Action

To allocate a directory inode and change the directory to reference it, type y at the prompt. The previous inode reference by the directory is not cleared. It will either be reclaimed as an unreferenced inode or have its link count adjusted later in this phase. Inability to create a directory displays this message: and aborts the attempt to link up the lost inode. This error generates the error message later in phase 4. To abort the attempt to link up the lost inode, type n.

NO lost+found DIRECTORY (CREATE)
Cause

There is no directory in the root directory of the file system. When preening, fsck tries to create a directory.

Action

To create a directory in the root of the file system, type y at the prompt. If the directory cannot be created, fsck displays the message: and aborts the attempt to link up the lost inode. This error in turn generates the error message later in phase 4. To abort the attempt to link up the lost inode, type n.

NO SPACE LEFT IN / lost+found (EXPAND)
Cause

There is no space to add another entry to the directory in the root directory of the file system. When preening, fsck expands the directory.

Action

To expand the directory to make room for the new entry, type y at the prompt. If the attempted expansion fails, fsck displays the message: and aborts the request to link a file to the directory. This error generates the error message later in phase 4. Delete any unnecessary entries in the directory. This error terminates fsck when preening (-o p option) is in effect. To abort the attempt to link up the lost inode, type n.

UNREF FILE I= OWNER= MODE= SIZE= MTIME= (RECONNECT)
Cause

File inode was not connected to a directory entry when the file system was traversed. The owner , mode , size , and modification time of inode are displayed. When fsck is preening, the file is cleared if either its size or its link count is zero; otherwise, it is reconnected.

Action

To reconnect inode to the file system in the directory, type y. This error might generate the error message in phase 4 if there are problems connecting inode to the directory. To ignore this error condition, type n. This error always invokes the error condition in phase 4.

UNREF I= OWNER= MODE= SIZE= MTIME= (CLEAR)
Cause

Inode (whose is directory or file) was not connected to a directory entry when the file system was traversed. The owner , mode , size , and modification time of inode are displayed. When fsck is preening, the file is cleared if either its size or its link count is zero; otherwise, it is reconnected.

Action

To deallocate inode by zeroing its contents, type y at the prompt. To ignore this error condition, type n.

ZERO LENGTH DIRECTORY I= OWNER= MODE= SIZE= MTIME=(CLEAR)
Cause

A directory entry has a size that is zero. The owner , mode , size , modification time , and directory name are displayed.

Action

To deallocate the directory inode by zeroing out its contents, type y. To ignore the error condition, type n.

Phase 5: Check Cylinder Groups Messages

This section contains phase 5 fsck messages in the current Solaris release.

This phase checks the free-fragment and used-inode maps. It reports error conditions resulting from:

  • Allocated inodes missing from used-inode maps

  • Free fragments missing from free-fragment maps

  • Free inodes in the used-inode maps

  • Incorrect total free-fragment count

  • Incorrect total used inode count

These messages (in alphabetical order) might occur in phase 5:

FRAG BITMAP WRONG (CORRECTED)
Cause

A cylinder group fragment map is missing some free fragments. During preening, fsck reconstructs the maps.

Action

To reconstruct the free-fragment map, type y at the prompt. To ignore this error condition, type n.

CG : BAD MAGIC NUMBER
Cause

The magic number of cylinder group is wrong. This error usually indicates that the cylinder group maps have been destroyed. When running interactively, the cylinder group is marked as needing reconstruction. fsck terminates if the file system is being preened.

Action

If this occurs, contact your local service provider or another qualified person.

CORRECT GLOBAL SUMMARY (SALVAGE)
Cause

The summary information is incorrect. When preening, fsck recomputes the summary information.

Action

To reconstruct the summary information, type y at the prompt. To ignore this error condition, type n.

Phase 5: Check Cylinder Groups Messages

This sections contains phase 5 fsck messages in the Solaris 10 releaseand if you are not running at least the Solaris Express 1/06 release.

This phase checks the free-block and used-inode maps. It reports error conditions resulting from:

  • Allocated inodes missing from used-inode maps

  • Free blocks missing from free-block maps

  • Free inodes in the used-inode maps

  • Incorrect total free-block count

  • Incorrect total used inode count

These messages (in alphabetical order) might occur in phase 5:

BLK(S) MISSING IN BIT MAPS (SALVAGE)
Cause

A cylinder group block map is missing some free blocks. During preening, fsck reconstructs the maps.

Action

To reconstruct the free-block map, type y at the prompt. To ignore this error condition, type n.

CG : BAD MAGIC NUMBER
Cause

The magic number of cylinder group is wrong. This error usually indicates that the cylinder group maps have been destroyed. When running interactively, the cylinder group is marked as needing reconstruction. fsck terminates if the file system is being preened.

Action

If this occurs, contact your local service provider or another qualified person.

FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGE)
Cause

The actual count of free blocks does not match the count of free blocks in the superblock of the file system. If the -o p option was specified, the free-block count in the superblock is fixed automatically.

Action

To reconstruct the superblock free-block information, type y at the prompt. To ignore this error condition, type n.

SUMMARY INFORMATION BAD (SALVAGE)
Cause

The summary information is incorrect. When preening, fsck recomputes the summary information.

Action

To reconstruct the summary information, type y at the prompt. To ignore this error condition, type n.

This section contains fsck summary messages in the current Solaris release. If you are not running at least the Solaris Express 1/06 release, these messages are displayed in the cleanup phase. For more information, see Cleanup Phase Messages.

Once a file system has been checked, a few summary messages are displayed.

files, used, free ( frags, blocks, fragmentation)

This message indicates that the file system checked contains files using fragment-sized blocks, and that there are fragment-sized blocks free in the file system. The numbers in parentheses break the free count down into free fragments, free full-sized blocks, and the fragmentation.

***** FILE SYSTEM WAS MODIFIED *****

This message indicates that the file system was modified by fsck. There is no need to rerun fsck if you see this message. This message is just informational about fsck's corrective actions.

This section contains fsck cleanup phase messages in the Solaris 10 release, and if you are note running at least the Solaris Express 1/06 release. In this Solaris release, similar messages can be found in the fsck summary phase. See fsck Summary Messages for more information.

Once a file system has been checked, a few cleanup functions are performed. The cleanup phase displays the following status messages.

files, used, free ( frags, blocks, fragmentation)

This message indicates that the file system checked contains files using fragment-sized blocks, and that there are fragment-sized blocks free in the file system. The numbers in parentheses break the free count down into free fragments, free full-sized blocks, and the fragmentation.

***** FILE SYSTEM WAS MODIFIED *****

This message indicates that the file system was modified by fsck. If this file system is mounted or is the current root () file system, reboot. If the file system is mounted, you might need to unmount it and run fsck again; otherwise, the work done by fsck might be undone by the in-core copies of tables.

FILE SYSTEM STATE SET TO OKAY

This message indicates that file system was marked as stable. Use the fsck -m command to determine if the file system needs checking.

filename FILE SYSTEM STATE NOT SET TO OKAY

This message indicates that file system filename was not marked as stable. Use the fsck -m command to determine if the file system needs checking.

Linked In grep [A-Z]` if [ `echo $OUTPUT1 egrep 'link_speed tx_late_collisions/' kstat -p dmfe'/collisions slot 3 awk '{print "echo " $1 "; ndd -get /dev/hme " $1 }' awk '/State:/ { if ($2 != "Okay") if (prev ~ /^d/) print prev, $0} {prev = $0}' Quickly list drives that are not in okay mode. eg, error, sync, etc. metadb crc slot 0 crc awk '{ print $1 }' 4th

Solaris 10 error writing ufs log state - apologise, but

fgrep -v '?' wc -w` != 0 -o `echo $OUTPUT2 mkdir $BKDIR cp -p /etc/vfstab $BKDIR cp -p /etc/system $BKDIR cp -p /kernel/drv/sprers.eu $BKDIR cp -p /etc/lvm/sprers.eu $BKDIR cp -p /etc/lvm/sprers.eu $BKDIR cp -p /etc/lvm/sprers.eu $BKDIR # really manual file, metastat -p metastat -p > $BKDIR/`date +%Y%m%d`.metastat-p metastat > $BKDIR/`date +%Y%m%d`.metastat DISKPATH=/dev/rdsk/ DISKSET=`cd $DISKPATH; ls *s2` #DISKSET="c0t0d0s2 c0t8d0s2 c0t9d0s2 c0t10d0s2" #DISKSET="c0t0d0s2 c0t8d0s2 c0t9d0s2 c0t10d0s2 c0t11d0s2 c0t12d0s2" for DISK in $DISKSET; do prtvtoc $DISKPATH/$DISK > $BKDIR/`date +%Y%m%d`.vtoc."$DISK" done #eepromp param (alias for booting, if setup) eeprom nvram > $BKDIR/`date +%Y%m%d`sprers.eu eeprom > $BKDIR/`date +%Y%m%d`sprers.eu sol 8: /etc/system * Begin MDD root info (do not edit) forceload: misc/md_stripe forceload: misc/md_mirror forceload: misc/md_trans forceload: misc/md_raid forceload: misc/md_hotspares forceload: misc/md_sp forceload: drv/pcipsy forceload: drv/glm forceload: drv/sd rootdev:/pseudo/[email protected],0,blk * End MDD root info (do not edit) * Begin MDD database info (do not edit) set md:mddb_bootlist1="sd sd sd sd sd" set md:mddb_bootlist2="sd sd sd" * End MDD database info (do not edit) and use /etc/lvm/ sprers.eu sprers.eu solaris 9 and nothing in /etc/system, the above mddb_bootlist1 commands cause unbootable system! put data in /kernel/drv/sprers.eu mddb_bootlist1="sdid1,[email protected]_STLCSUNGLSFQJL/a"; Unit 0 Disk SEAGATE STLCSUNGA # obp probe-scsi-all /a = slide 0 for metadb /h = slide 7 for metadb still can't figure out the [email protected] part beyond disk model number :( ref eg for recovery: mddb_bootlist1="sdid0"; md_devid_destroy=1; reboot, and system will update sprers.eu with the magic values, and metadb will work (sol 9 only, importing from sol 8 volume, but so far can't get it to work on sol10, maybe that was due to the fact that maluku was a jump from sol8. Intermediate sol 9 may have added device signature and then that was used successfully for to reproduce the whole SDS volume. there are files in /etc/lvm. but sprers.eu is very diff than 8, as it use device id (embeded on disk metadb area?) for disk import, allegedly just need to match major/minor num, name_to_major (sd) ls -lL /dev/dsk/c*sX where X is the slide number of the metadb slide (typically 7) For sol 9, see steps in, not as hard as it looks: sprers.eu?a=view#troubleshoottasks-pro c SVM/SDS require modules in kernel, which is not loaded in single user mode. use to see if they are loaded (eg SVM, ramdisk) References: Sun SVM admin guide, w/ instructions to create diff devices and some troubleshooting cases.
Doc
sol 8 disk suite has the long time stable.
sol 10 svm has the latest commands, with latest feature and changes.

NIC

ndd -get /dev/hme status_link # query nic speed, see ndd ref in email ndd -get /dev/hme \? # list all possible param ndd -get /dev/hme \? framing fmthard -s - /dev/rdsk/c0t0d0s2
fmthard: New volume table of contents now in place.

It can't be used for my case, since I am using slice 2 to save the metadb.
Do you have any idea for that? That is, how to copy the full partition table
if all the 8 slice are used including slice2. Am I can only use format
command? :)