| Linux systems use ext2, ext3 and reiserFS file | | | | "unable to read inode block - inode = , block = " |
| systems in general. For all these file systems, inode is a | | | | Here, inode number and block number refer to the |
| significant metadata structure. Inode keeps record of | | | | corresponding details of object whose inode is |
| each file or directory on the drive together with of | | | | damaged. The file system is corrupt and needs Linux |
| other metadata structures. For accessing any of files, | | | | Recovery.o In order to resolve the issue, the file |
| directories or file system objects, system takes | | | | system repair tool fsck can be used to repair.o If |
| reference from its inode. | | | | problem persists, we can format the drive and hence |
| Inode keeps information like file size, file permissions, file | | | | refresh the file system. Lost data can be restored |
| creation and modification details, Access Control List, | | | | using backup. If drive is accessible, data can be easily |
| file type and all such information that form its header. | | | | backed up and used for further restoration. |
| The table of inodes is indexed by inode number. | | | | It is suggested to check the log report status before |
| However if this information corrupts, it indicates file | | | | formatting the drive. Also data backup should be |
| system corruption and need of Linux Data Recovery. | | | | checked for required files. However if user fails to |
| If inodes are corrupt, the system may fail to boot, hang | | | | take valid backup, data loss occurs. In such situations, |
| or may fail to access the required file, with an error | | | | Linux Data Recovery software can be used to |
| similar to: | | | | extract lost information. |