Bash /bin/ls Input/output Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta bash sbin reboot input output error Discuss the workings and policies of this site About Us Learn more linux input output error about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & linux bash: input/output error Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating
Reading Directory Input Output Error Linux
systems. 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” when accessing a directory up vote 39 down vote favorite 9 I want to list and remove the content of a directory on a input/output error kali linux removable hard drive. But I have experienced "Input/output error": $ rm pic -R rm: cannot remove `pic/60.jpg': Input/output error rm: cannot remove `pic/006.jpg': Input/output error rm: cannot remove `pic/008.jpg': Input/output error rm: cannot remove `pic/011.jpg': Input/output error $ ls -la pic ls: cannot access pic/60.jpg: Input/output error -????????? ? ? ? ? ? 006.jpg -????????? ? ? ? ? ? 006.jpg -????????? ? ? ? ? ? 011.jpg I was wondering what the problem is? How can I recover or remove the directory pic and all of its content? My OS is Ubuntu 12.04, and the removable hard drive has ntfs filesystem. Other directories not containing or inside pic on the removable hard drive are working fine. Added: Last part of output of dmesg after I tried to list the content of the directory: [19000.712070] usb 1-1: new high-speed USB device number 2 using ehci_hcd [19000.853167] usb-storage 1-1:1.0: Quirks match for vid 05e3 pid 0702: 520 [19000.853195] scsi5 : usb-storage 1-1:1.0 [19001.856687] scsi 5:0:0:0: Direct-Access ST316002 1A 0811 PQ: 0 ANSI: 0 [19001.858821] sd 5:0:0:0: Attac
LINUX HOWTO | 2 Replies More Bad Disk This article I am trying to explain how to deal with " Input/output error " when you initiate bashrc input/output error any commands in Linux. I have pointed some examples that reports similar error. #
Centos Input/output 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
Input/output Error Ubuntu
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 http://unix.stackexchange.com/questions/39905/input-output-error-when-accessing-a-directory 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 http://linoxide.com/how-tos/inputoutput-error-bad-blocks-how-to-restart-linux/ 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 also likeHow To Fix / Repair Bad Blocks In LinuxHow To Backup LVM Configuration On Linux (vgcfgbackup & vgcfgrestore)Linux Crontab : How To Configure Cron With Best ExamplesHow To List Linux Pci Devices Using lspci CommandSet Date And Time In Linux And Sync With Hardware (CMOS)Linux Hdparm Command: Display Hard Disk Model and Serial NumberLinux: Manage Spaces And Special Characters In File NameUnderstand Linux Su Command F
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss http://superuser.com/questions/225788/ubuntu-input-output-error the workings and policies of this site About Us Learn more https://bbs.archlinux.org/viewtopic.php?id=187131 about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: output error 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 ubuntu input/output error up vote 5 down vote favorite 2 I'm having a problem with Ubuntu that I'm finding hard to troubleshoot for reasons that will become clear: reboot -bash: /sbin/reboot: Input/output error dmesg input output error -bash: /bin/dmesg: Input/output error ps -e ps: error while loading shared libraries: /lib/libproc-3.2.8.so: cannot read file data: Input/output error lsof -bash: /usr/bin/lsof: Input/output error fsck -bash: /sbin/fsck: Input/output error badblocks -bash: /sbin/badblocks: Input/output error So I can't see what is going on, and I can't remotely reboot. What can I do to get to the bottom of this? Interestingly: init 0 Segmentation fault I can cat /var/syslog but not /var/log/messages or several other important files. less and more don't work, neither do tail or head, etc. linux ubuntu share|improve this question edited Dec 26 '10 at 7:52 asked Dec 26 '10 at 7:23 rplevy 147116 1 Sounds pretty similar to what you get after running sudo rm -rf /. (I did it on purpose, just to see what actually happens.) –AJMansfield Sep 12 '13 at 19:27 add a comment| 1 Answer 1 active oldest votes up vote 6 down vote accepted The system is having severe trouble reading off of your hard disk. It's likely that the disk is dead (almost certain),
after time Pages: 1 #1 2014-09-16 13:51:35 Carl Karl Member Registered: 2013-06-12 Posts: 225 [solved] NFS: "ls: reading directory .: Input/output error" after time Hello,I got the following configuration:NFS-server: Always on, connected via LAN.NFS-clients: 2 computers, connected via LAN and WLAN. On standby: auto umount NFS-share via system-sleep-hook with systemd.This works flawlessly some hours or even days. But after some time, the following happens:1. mount nfs-share: no error message2a. trying to access that folder via filemanager, e.g. thunar: folder seems to be empty (it isn't on server!), but the correct freesize of the NFS-share on server is displayed in the statusbar.2b. trying to access that folder via commandline: $ ls ls: reading directory .: Input/output errorThe very same worked just a few hours before, I haven't changed anything meanwhile. Apart from standby (--> auto umount NFS-share) and resume (manual mount NFS-share) on the clients which worked before, too.Any idea what's going wrong?additional info:server: /etc/exports _______________________ /srv/nfs/myshare 192.168.2.0/24(rw,all_squash,anonuid=33,anongid=33,no_subtree_check)(yes, the mapping is needed and right.)clients:/etc/fstab _______________________ servername:/srv/nfs/myshare /home/carl/nfs nfs4 noauto,soft,user,_netdev,timeo=14,rsize=8192,wsize=8192 0 0/usr/lib/systemd/system-sleep/umount-nfs _______________________ #!/bin/sh case $1 in pre) umount -f /home/carl/nfs ;; esac Last edited by Carl Karl (2014-09-21 17:07:47) Offline #2 2014-09-16 14:15:27 nomorewindows Member Registered: 2010-04-03 Posts: 3,015 Re: [solved] NFS: "ls: reading directory .: Input/output error" after time Somehow your nfs mounts have gone stale. You'd need to remount them or restart nfs related services. Dmesg or syslog output may help. I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...Look ma, no mouse. Offline #3 2014-09-16 14:29:10 Carl