Linux Mount Input Output Error
Contents |
error" when mounting windows share on SLE 12 SP1 × × Sorry for the inconvenience Our new site design is ls reading directory . input/output error in linux only available in English right now. Go to the previous
Input/output Error Nfs
site to read in my language Stay here and read in English × Give Us Feedback
Linux Input Output Error Deleting File
Got some feedback about the website? Let us know so we can fix it. For support information, please visit Support. Sales:1-800-796-3700 Support:1-800-858-4000 Connect with us Feedback
Mount.nfs Input/output Error Rhel5
Form We adapt, you succeed. Read Privacy Policy Required Fields* X SUSE Support My Favorites Close Please login to see your favorites. Bookmark Email Document Printer Friendly Favorite Rating: Getting "mount error(5): Input/output error" when mounting windows share on SLE 12 SP1This document (7017413) is provided subject to the disclaimer at the end ls reading directory . input/output error ubuntu of this document. Environment SUSE Linux Enterprise Desktop 12 SP1SUSE Linux Enterprise Server 12 SP1SUSE Linux Enterprise Desktop 12SUSE Linux Enterprise Server 12 Situation When trying to mount a Windows / cifs / samba share it would give the following error: mount error(5): Input/output error Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)In SLE 11 SP3 the same command would work when mounting this same Windows share.Here is a copy of the SP3 syntax that works mount -t cifs //server.suse.com:/home /mnt/test -o username=corpdom\\usernameIn SLE 12 SP1 a similar command would fail mount -t cifs //server.suse.com/home /mnt/test -o username=corpdom\\usernameHere is the error on the command line after running this command mount error(5): Input/output error Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)If you look at the end of "journalctl" you will see these errors. Status code returned 0xc0000001 NT_STATUS_UNSUCCESSFUL CIFS VFS: Send error in SessSetup = -5 CIFS VFS: cifs_mount failed w/return code = -
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings ls reading directory . input/output error centos and policies of this site About Us Learn more about Stack Overflow the cannot open directory . input/output error company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users ls: reading directory .: input/output error nfs 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 systems. Join them; it only takes https://www.suse.com/support/kb/doc?id=7017413 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 removable hard drive. But I have experienced "Input/output error": $ http://unix.stackexchange.com/questions/39905/input-output-error-when-accessing-a-directory 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: Attached scsi generic sg2 type 0 [19001.861733] sd 5:0:0:0: [sdb] 312581808 512-byte logical blocks: (160 GB/149 GiB) [19001.862969] sd 5:0:0:0:
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 https://bbs.archlinux.org/viewtopic.php?id=187131 the following configuration:NFS-server: Always on, connected via LAN.NFS-clients: 2 computers, connected http://askubuntu.com/questions/74105/how-do-you-repair-an-input-output-error-in-an-ntfs-partition 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 output error 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 reading directory . 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 Karl Member Registered: 2013-06-12 Posts: 225 Re: [solved] NFS: "ls: reading directory .: Input/output error" after time Indeed, there could be something interesting in dmesg on the server:[ 4.190117] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [ 4.190596] NFSD: starting 90-second grace period (net
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 you repair an “input/output error” in an NTFS partition? up vote 26 down vote favorite 13 I replaced a buggy Windows Vista installation with Ubuntu. All works fine except that the main HD where I had all my files are now inaccessible. Here is the error message I get: Error mounting: mount exited with exit code 13: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Failed to read NTFS $Bitmap: Input/output error NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows then reboot into Windows twice. The usage of the /f parameter is very important! If the device is a SoftRAID/FakeRAID then first activate it and mount a different device under the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation for more details Is it necessarily a hardware problem? If not, is there a way to repair the HD from Ubuntu? windows ntfs share|improve this question edited May 15 at 19:06 muru 69.1k12125176 asked Oct 31 '11 at 15:13 Calixte 68461528 add a comment| 5 Answers 5 active oldest votes up vote 17 down vote accepted chkdsk /R is a pretty important command when things get hairy with NTFS. Unfortunately I don't know of a Linux tool that comes close to covering everything it does. In short, to run it, you're going to need some sort of Windows recovery disk. If you don't have one to hand, there's an ISO offered up in a thread on another set of support forums (see the first answer). There are tools like ntfsfix (part of the ntfsprogs package) that can do surface checks on NTFS disks but they don't tend to be able to fix the drives. share|im