| SCO UnixWare operating system is a Unix-based | | | | error message is VERITAS File inode corruption |
| operating system that is primarily known for its | | | | as a result of transient fiber link failures. |
| reliability, stability and scalability. While the | | | | Resolution: |
| operating system is safe and reliable, it can also | | | | To resolve the above error message and access |
| be corrupted and unmountable due to super block | | | | the data, you need to take these steps: |
| damage or corruption, inode corruption, boot | | | | 1. Unmount the file in order to attempt repairs on |
| errors, VTOC (Volume Tables of Contents) | | | | corrupted inodes. Use the command to analyze |
| damage, OLT (Object Location Table) damage | | | | the superblock on the failing file system: |
| and malicious software like virus. In most cases of | | | | % echo "8192B.p S" | fsdb -F vxfs /dev/vx/rdsk |
| operating system corruption, you encounter an | | | | rootdg/meta |
| error message. Once you encounter the error | | | | 2. Run a full fsck with the -n option to see which |
| message, the data stored in the hard drive | | | | inodes are marked bad |
| becomes inaccessible. To overcome such | | | | 3. Set the "aflag" field to 0x0 using fsdb. This step |
| situations, the best possible way is to restore the | | | | must be done very carefully since it involves |
| data from an up-to-date backup. However, in | | | | writing to the file structure itself. The incorrect |
| case of no backup availability or backup failing | | | | use of fsdb can destroy the file system. |
| short of restoring the required data, you need to | | | | 4. The inode aflag has been cleared for the 3 |
| use advanced SCO UnixWare Data Recovery | | | | inodes. Verify it with fsck. |
| Software. | | | | 5. Now it should be safe to run a full fsck with the |
| Consider a practical scenario, where you | | | | -y option |
| encounter the below error message when you | | | | 6. Mount the file system and check the inodes |
| attempt to boot your UNIX based operating | | | | If the above steps fail to resolve the issue, you |
| system: | | | | need to reinstall the file system. These file |
| "Mar 15 17:26:21 ioccrmprep1 unix: WARNING: | | | | systems act as pointers to the files and folders |
| msgcnt 31 vxfs: mesg 017:vx_ilock - /opt/data | | | | saved on the hard drive. Reinstalling the file |
| ora16/preprod file system inode 10 marked bad" | | | | system will erase all those entries and your data |
| The above error message indicates that inode 10 | | | | will become inaccessible. In such circumstances, |
| has been marked bad. Data saved in the hard | | | | you need to go for an advanced SCO UnixWare |
| drive becomes inaccessible after the above error | | | | Data Recovery Software. Such SCO UnixWare |
| message appears. | | | | Data Recovery tools use advanced scanning |
| Cause: | | | | algorithms to recover your lost data. |
| The root cause for the occurrence of the above | | | | |