Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I suggest that you check out the partition in question using fsck. umount the partition, run fsck against the partition to correct any errors, and then mount the partition.
Did you try to move the files with the dd command? If you canceled a dd command in the middle then the partition may be so badly damaged that fsck cannot fix it.
well, now im not worried about copying the files per se, I just want to be able to access them.
first it wasnt mountable, now it is. after that, I tried to access a particularly large folder with over 30 gb of data, and said it had an input/output error, now thats gone. NOW it says 'The folder contents could not be displayed'.
Note that fsck is only suitable for linux partitions formatted as ext2 or ext3
Quote:
Doesnt fsck run the risk of losing data?
Yes, but fsck is clever, and does its best to preserve data. If it finds data it doesn't know what to do with it puts it into lost+found, where you can often recover it.
If the disk is DOS formatted, maybe you should try some DOS-format recovery programs: eg fatback runs on linux.
Note that fsck is only suitable for linux partitions formatted as ext2 or ext3
<snip>
Sorry but you statement about 'fsck' supports only ext2/3 is not correct;
Quote:
excerpt from 'man fsck'
In actuality, fsck is simply a front-end for the various file system
checkers (fsck.fstype) available under Linux. The file system-specific
checker is searched for in /sbin first, then in /etc/fs and /etc, and
finally in the directories listed in the PATH environment variable.
Please see the file system-specific checker manual pages for further
details.
So I suppose you just need to choose the appropriate one.
I have always just used fsck (for my ext3 partitions), maybe I should have used /sbin/fsck.ext3 ? It worked anyway.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.