Posted on Monday, May 24, 2010 at 11:29 PM
A Linux based computer system becomes unbootable in case its file system gets corrupted or damaged. In most of these situations, a Linux user encounters an error message that does not allow him/her to access the data saved on the Linux hard drive. Few main causes for corruption in file system (either EXT4, EXT3, or EXT2) can be improper system shutdown, inode corruption, superblock damage, virus infection, accidental system shutdown, and operating system malfunction.
To overcome such situations, the user needs to repair the damaged file system using 'e2fsck' command. This command checks and repairs the corrupted files system in almost all cases. However, the command does not ensure 100% repair in all file system corruption scenarios. For cases where the above command fails, the user needs to reinstall Linux operating system and then restore data from an updated backup. But, in the absence of a valid backup, you will need to opt for a commercial Linux Recovery application...
Posted on Monday, May 24, 2010 at 12:20 AM
LVM (Logical Volume Manager) is a part of Linux operating system kernel, which manages hard drives and other mass storage devices. It is a way of allocating disk space into various volumes, which can easily be resized or extended instead of hard drive partitions. You can not place Linux /boot/ partition on logical volume group as it is not readable by the Linux boot loader.
You can easily extend a logical volume, using lvextend utility. It also supports extension of the snapshot logical volumes. Before you proceed for extending a Linux volume, you must first create an absolute backup of entire volume. In case the logical volume extending process gets interrupted or halted, you may lose access to logical volumes and encounter data loss. At this point, you have to opt for Linux data recovery software to get your valuable data back.
The lvextend command-line utility, offers you the following options to perform a series of operations on your logical volume-...
Posted on Friday, May 21, 2010 at 12:45 AM
Like other computer operating systems, Linux also comprise of various components, which include Superblock. Superblock is a significant metadata of the Linux operating system, which describes file systems on the Linux hard drive. The system components have interdependency and work together to keep your system functional. However, if any of these system components or data structures gets damaged, the system may not work properly and you can not access stored data from the hard drive. This behavior leads to critical data loss situations and require Linux Data Recovery to be fixed.
Under some situations, you can not mount your Linux file system and the data stored on the Linux hard drive volumes can not be accessed. Most of the problem occurs in a dual-boot system. When you try repairing your Linux file system on the root partition, process could not complete successfully. It renders your entire system inaccessible.
When you run fsck utility on the affected Linux hard drive, without 'L' option, you may come across the below error message:...
Posted on Sunday, May 16, 2010 at 11:01 PM
Are you finding difficulties in mounting your Linux system disk? The problem could be due to corruption in the file system. To address such issues, Linux OS provides fsck utility. It is a command-line utility, which checks integrity and consistency of the Linux file system. In addition, it finds errors and fixes them, if possible. However, if you run this utility on a mounted file system, then you may not be able to access the data at all. In such cases, you should use a third-party Linux data recovery software to perform data recovery Linux system.
Consider a scenario wherein you have accidentally run fsck on a mounted Linux OS. The inode root gets damaged and all inodes start calling similar blocks. When you try to mount the volume after fsck, the following error message is discovered:
"Mount: wrong fs type, bad option, bad superblock on /dev/hda1, missing codepage or helper program, or other error. In some cases useful info is found in syslog - try dmesg | tail or so"...