Input Output Error Fsck
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us
Ls Reading Directory . Input/output Error In Linux
Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer input/output error linux site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Input/output error and fsck up vote 0 down vote favorite recently I couldn't mount my hard drive so I booted with a live cd and doing a fsck on that partition. it said Deleted inode 992193 has zero dtime. Fix i entered y and another one it showed me this prompt again and I entered ctrl-C now I'm able to mount that hard disk. but my problem: I can't access some files it says Input/output error If I do fsck again and answer all prompts like (Deleted inode 992193 has zero dtime. Fix) to yes my data will be recovered?! my another data will be lost?! I'm not technical in hard disks so I can't read the manuals. it has some technical issues linux filesystems data-recovery share|improve this question asked Oct 29 '11 at 15:15 sinoohe migrated from stackoverflow.com Nov 6 '11 at 9:11 This question came from our site for professional and enthusiast programmers. add a comment| 2 Answers 2 active oldest votes up vote 4 down vote This is off-topic here, but you need to let the fsck finish, or your filesystem will remain corrupt and you will continue to have problems with it. Run fsck -y, let it complete, and then you should be ok (most of the time). share|improve this answer answered Oct 29 '11 at 16:30 Employed Russian 22612 add a comment| up vote 1 down vote Watch out with performing fsck on a failing drive. If it's an hardware issue, better first make an image of what is still readable with something like ddrescue (see that you get the GNU one, it's the better of the 2 ddrescues that are around). trying to fix the filesystem on a failing disk might wear it out, and limit the amount of data that you'll be able to recover. So first copy, and try fixing the FS on the copy. share|improve this answer answered Oct 29 '11 at 17:00 jpjacobs 22624 I made a backup by dd and do fsck -y after my backup, so my corrupted data has been removed! I didn't want to remove them! so I thing I have to recover my backup data and recover corrupt data by testdisk! –sinoohe Oct
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How do I repair a Fat http://superuser.com/questions/354418/input-output-error-and-fsck 32 Filesystem Partition “input/output error” up vote 1 down vote favorite Some how the partition (Dev/sda2) partition got deleted. So I use TestDisk to bring it back... The first time I did it it erase the whole hard drive... The second time it did restore the partition which is good. But now it is giving me a error massage when I try to open it in Files(Gnome). IF you need it in text here: http://askubuntu.com/questions/478124/how-do-i-repair-a-fat-32-filesystem-partition-input-output-error Error when getting information for file '/media/ubuntu-gnome/Backup/User': Input/output error partitions error-handling fat32 share|improve this question asked Jun 7 '14 at 16:23 MathCubes 2,22462650 check dmesg after getting this error for more details. –psusi Jun 7 '14 at 17:34 add a comment| 2 Answers 2 active oldest votes up vote 0 down vote Try running sudo dosfsck -r a few times and see if that fixes things. Good luck. share|improve this answer answered Jun 7 '14 at 16:40 ubfan1 5,42331322 add a comment| up vote 0 down vote Repair the file system It seems your file system is corrupted. You can attempt to fix it by executing this command in your Terminal: sudo fsck -y /dev/sda2 Replace /dev/sda2 with the appropriate partition you want to fix. share|improve this answer answered Jun 7 '14 at 16:41 Naveen 4,19642956 fsck from util-linux 2.20.1 e2fsck 1.42.9 (4-Feb-2014) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/sda2 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2
Search HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie Input/output error User Name Remember Me? Password Linux - Newbie This Linux forum http://www.linuxquestions.org/questions/linux-newbie-8/input-output-error-222152/ is for members that are new to Linux. Just starting out and have a question? If it is not in the man pages or the how-to's this is the place! Notices Welcome to LinuxQuestions.org, a http://linoxide.com/how-tos/inputoutput-error-bad-blocks-how-to-restart-linux/ 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 output error 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. Are you new to LinuxQuestions.org? Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. If input output error you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely free. Search this Thread 08-25-2004, 06:19 AM #1 rob19 Member Registered: Mar 2003 Location: New Zealand Distribution: Red Hat Linux 8 & 9 Posts: 32 Rep: Input/output error I have been running a Web server with RH9 for about six months now. Everything has been going fine and I have not made any changes for a while. H
LINUX HOWTO | 2 Replies More Bad Disk This article I am trying to explain how to deal with " Input/output error " when you initiate any commands in Linux. I have pointed some examples that reports similar error. # du -bash: /usr/bin/du: Input/output error #mkdir sampledir mkdir: cannot create directory `sampledir': Input/output error Input/output error while running the command mostly due to two reason. Either it could be bad blocks on the disk or someone hacked your machine. In this situation first suggestion would be to check /var/log/messages for any disk related alerts (might see some sense key alerts). tail -n 100 /var/log/messages tail -f /var/log/messages If you notice any disk issues , try any disk utility to confirm this. One option would be use smarttools. You can check smartool option to fix bad blocks. If you already installed it you can take the advantage of that. Next immediate action would be take backup of your system. Good if you already have it :-). If you have good backup its safe to reboot.If your system was hacked there are chances they might messed up your file and system would not work after reboot. You can also try fsck but it really dont fix most time if it bad block issue. Fsck can fix only if it related to any filesystem related issues. Usually fsck will fail in between as when it try to read the file at bad block. Now if try to reboot , it can also give the same output. You can try init 6. # reboot bash: /sbin/reboot: Input/output error # shutdown -r now bash: /sbin/shutdown: Input/output error If the above reboot commands doesnot work try either forced reboot or shutdown . Forced Reboot echo 1 > /proc/sys/kernel/sysrq echo b > /proc/sysrq-trigger Forced Shutdown echo 1 > /proc/sys/kernel/sysrq echo o > /proc/sysrq-trigger You might als