Monday, June 15, 2009

Error in Linux “No such file or directory”

When you try to install device drivers on your Linux system, you might fail to do it. It could be due to incompatibility of the operating system Kernel with your device driver or device. You need to install the latest version of Linux kernel. It may include ‘forcedeth’ patch, which is capable of resolving most of the incompatibility issues.

After installing the latest version of Kernel, when you reboot the Linux system, you might face the following error message:“fsck.ext2: No such file or directory while trying to open /dev/hda8. The super block could not be read or does not describe a correct ext2 file system.

If the device is valid and it really contains an ext2 file system (and not swap or ufs or something else) then the super block is corrupt, and you might try running e2fsck with an alternate super block: e2fsck -b 8193 fsck failed.”

As stated in the error message, this problem generally occurs due to super block corruption or file system corruption. Super block and file system are two most important data structure of Linux system. Proper functioning of both these is required for ensuring effective working of the system. After corruption, the operating system could not locate the file and thus can not retrieve it.

To solve this problem, you need to install a fresh copy of super block and file system. It is possible through formatting of the hard drive and reinstallation of operating system. Though, it will remove the errors but will also erase all the data stored on your hard drive. It is the worst scenario of data loss and needs Linux data recovery to get it fixed.

Linux recovery software are easy to use and thus allow you to have simple and fast data recovery Linux. Linux data recovery is feasible with the application of third party Linux recovery software known as Linux data recovery software.This data recovery Linux software works well in all data loss cases and allows Linux data recovery for all sorts of files.

0 comments:

Photoblog