Input Output Error Ubuntu
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 input/output error linux this site About Us Learn more about Stack Overflow the company Business Learn
Cannot Access Input/output Error
more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ input/output error centos 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 a minute: Sign up Here's how it input output error ubuntu usb 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": $ rm pic -R rm: cannot remove `pic/60.jpg': Input/output error
Ubuntu Input Output Error External Hard Drive
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: [sdb] Test WP failed, assume Write Enabled [19001.865223] sd 5:0:0:0: [sdb] Cache data unavailable [19001.865232] sd 5:0:0:0: [sdb] Assum
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 ls reading directory . input/output error ubuntu to any questions you might have Meta Discuss the workings and rm cannot remove input output error linux policies of this site About Us Learn more about Stack Overflow the company Business Learn more
Cannot Open Directory . Input/output Error
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 http://unix.stackexchange.com/questions/39905/input-output-error-when-accessing-a-directory 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 input / output error, drives randomly refusing to read / write [closed] up vote 4 http://askubuntu.com/questions/15476/input-output-error-drives-randomly-refusing-to-read-write down vote favorite 1 I have an issue with one of our servers running Ubuntu 10.04, it is running BackupPC and collects backups from various machines / servers around the building. On the 8th minute (12:08, 12:18, 12:28 etc) the backups are transferred to an external hard drive, we have three and rotate one drive for another everyday. The problem we are having is we are randomly experiencing input / output errors, when this happens you cannot read / write to the drive, it hasn't unmounted so I can cd to the mount point /media/backup1. The drives are not faulty as it's happening on all of them, so I'm at a loss as to what the problem could be, here is an example of the many errors we get: gzip: stdout: Input/output error /var/lib/backuppc/backuppc_offline: line 47: /media/backup1/Tue/offline.log: Input/output error ls: cannot access /media/backup1/Tue/incr_1083_host1.something.co.uk.tar.gz: Input/output error ls: cannot access /media/backup1/Tue/incr_1088_host1.something.co.uk.tar.gz: Input/output error ls: cannot access /media/backup1/Tue/incr_1089_host1.something.co.uk.tar.gz: Input/output
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 http://askubuntu.com/questions/65830/errno-5-input-output-error-when-trying-to-install Stack Overflow the company Business Learn more about hiring developers or posting ads with us https://bbs.archlinux.org/viewtopic.php?id=165237 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 “errno 5 - output error input/output error” when trying to install up vote 11 down vote favorite 4 Today I downloaded Ubuntu for my laptop. It runs great from a bootable usb, but when I tried to install it, I've got the "errno 5 - input/output error". I tried everything to install it on my laptop, but nothing works (also re-download the iso). system-installation share|improve this question edited Oct 26 '15 at 23:33 Tim 14.6k858100 asked Oct input output error 13 '11 at 20:57 Manuel Andrés Vélez 1252210 add a comment| 8 Answers 8 active oldest votes up vote 8 down vote accepted You may have some bad sectors on the target HDD. To check sda1 volume for bad sectors in Linux run fsck -c /dev/sda1. For drive C: in Windows it should be chkdsk c: /f /r. IMHO chkdsk way will be more suitable as it will remap bad blocks on the HDD while Linux fsck simply marks such blocks as unusable in the current file system. Quote from man fsck.ext2 -c This option causes e2fsck to use badblocks(8) program to do a read-only scan of the device in order to find any bad blocks. If any bad blocks are found, they are added to the bad block inode to prevent them from being allocated to a file or directory. If this option is specified twice, then the bad block scan will be done using a non-destructive read-write test share|improve this answer edited Nov 14 '15 at 7:41 David Foerster 10.7k93052 answered Oct 13 '11 at 21:09 Sergey 1,018814 I format my installation USB to low level from windows, re-mount the iso and it works... my hdd works great but this USB pendrive not. Thanks a lot for the answer –Manuel Andrés V
#1 2013-06-15 11:24:02 epaaj Member Registered: 2011-08-10 Posts: 5 [SOLVED] Disk crash - Input/output error - Error reading blocks Hi guys,I need some help recovering data from a disk that I believe either is completely broken already or it will soon be.It started when trying to browse a specific folder. When i ran "ls" in it I got "Input/output error" for all folders in it. I could not list anything within the folder.I unmounted the hard drive immediately.I noticed several rows with these in dmesg:"[607277.950354] Buffer I/O error on device sdb1, logical block 23320""dd if=/dev/sdb1 of=/mnt/backup/location" gives me about 44kB and then it thinks it is done. The drive is 500GB and almost full. Only one partition.Disk /dev/sdb: 500.1 GB, 500107862016 bytes, 976773168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x000621d7 Device Boot Start End Blocks Id System /dev/sdb1 * 63 976768064 488384001 83 Linux"sudo e2fsck -f /dev/sdb1" gives:e2fsck 1.42.7 (21-Jan-2013) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sdb1 Could this be a zero-length partition?Ran "sudo dumpe2fs /dev/sdb1 | grep -i superblock" to find the superblock locations:Primary superblock at 0, Group descriptors at 1-30 Backup superblock at 32768, Group descriptors at 32769-32798 Backup superblock at 98304, Group descriptors at 98305-98334 Backup superblock at 163840, Group descriptors at 163841-163870 Backup superblock at 229376, Group descriptors at 229377-229406 Backup superblock at 294912, Group descriptors at 294913-294942 Backup superblock at 819200, Group descriptors at 819201-819230 Backup superblock at 884736, Group descriptors at 884737-884766 Backup superblock at 1605632, Group descriptors at 1605633-1605662 Backup superblock at 2654208, Group descriptors at 2654209-2654238 Backup superblock at 4