Damaged Root Inode Post Resizing Hard Drive Volume Article

	1888 Articles Home \| Computer Articles \| Data Recovery Articles \| Windows Articles	Data Recovery RSS
Damaged Root Inode Post Resizing Hard Drive Volume

Resizing is a regular process carried out by almost all Linux users to increase, decrease, create, delete, or reorganize the size of their Linux-based hard drive volumes. To carry out resizing, most of the users opt for an effective third-party partitioning utility.

Author: Tom Patrick

Article Tools:

While the partitioning becomes simple with these utilities, it can also result in corruption of root inode. This mainly occurs when the application malfunctions during resizing process or the partitioning is not performed systematically. In most of these situations, users encounter an error message that does not allow access to data saved in any Linux based hard drive volume. To overcome such situations and to access the volume data, user needs to restore file from an updated backup. However, if the backup file is unavailable or deficient, then the user needs to opt for an effective Linux Data Recovery application.

Consider a practical case wherein you resize your 500 GB hard drive volume and divide it into two volumes. After resizing, when you try to mount any of the divided volumes, they do not mount. Furthermore, you encounter the below error messages:

“root@ubuntu:/# mount /dev/sda1 /media/500gb/
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so”

“root@ubuntu:/# dmesg | tail
[17179650.572000] Bluetooth: L2CAP ver 2.8
[17179650.572000] Bluetooth: L2CAP socket layer initialized
[17179651.772000] Bluetooth: RFCOMM socket layer initialized
[17179651.772000] Bluetooth: RFCOMM TTY layer initialized
[17179651.772000] Bluetooth: RFCOMM ver 1.7
[17181754.432000] EXT2-fs: corrupt root inode, run e2fsck”

After the above error message pop up, the volumes become unmountable, resulting in inaccessibility of the data.

Cause:

As described in the error message the root inode gets corrupted.

Resolution:

To get past the above error message and to access the volume data:

Run 'e2fsck' command to repair corrupt root inode.
If the command fails, reinstall Linux operating system. Re-installation creates new partitions, making the data saved in all the volumes inaccessible. To recover lost data post re-installation, you need to search for effective Linux Data Recovery utility. These Linux Recovery utilities employ intensive recovery procedures to recover formatted volumes and data within them.

About Author

Tom Patrick is a magazine editor currently working on mac file recovery

Article Source: http://www.1888articles.com/author-tom-patrick-28303.html