Disk Read Error Read Failed Input Output Error
Contents |
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other failed input output error 5 Support Launchpad Answers Ubuntu IRC Support AskUbuntu Official Documentation User Documentation Social
Volume Erase Failed Input Output Error
Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu set scan parameters failed input output error Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support Hardware [ubuntu] Vuze Error: Disk read error - read fails/input/output error Having
Fortigate Fgtag.c - 154: Disk Read Failed: Input/output Error
an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Results 1 to 1 of 1 Thread: Vuze Error: Disk read error - read fails/input/output error Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode October ubuntu input output error external hard drive 15th, 2014 #1 jacobyscastleinthe View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date Oct 2014 Beans 1 Vuze Error: Disk read error - read fails/input/output error When i try to download any torrents this happens. It just says Error: Disk read error - read fails/input/output error in red right away, Ive tried uninstalling and reintstalling vuze but it doesn't work. HELPPP Im running Ubuntu 14.04 LTS Attached Images error.jpg (95.4 KB, 1 views) Adv Reply Quick Navigation Hardware Top Site Areas Settings Private Messages Subscriptions Who's Online Search Forums Forums Home Forums The Ubuntu Forum Community Ubuntu Official Flavours Support New to Ubuntu General Help Asus Ubuntu Support (CLOSED) Dell Ubuntu Support (CLOSED) Ubuntu One (CLOSED) Installation & Upgrades Hardware Desktop Environments Networking & Wireless Multimedia Software Ubuntu Studio Mythbuntu Ubuntu Specialised Support Ubuntu Phone and Tablet Ubuntu Development Version Security Virtualisation Ubuntu Servers, Cloud and Juju Server Platforms Ubuntu Cloud and Juju Gaming & Leisure Emulators Wine Development & Programming Packaging and Compiling Programs Development CD/DVD Image Testing Ubuntu Application Development Ubuntu Dev Link Forum Programming Talk Reposit
#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 https://bbs.archlinux.org/viewtopic.php?id=165237 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 http://forum.vuze.com/Thread-Read-fails-result-too-large 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 output error 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 input output error 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 26542
» Read fails - result too large Thread Rating: 0 Vote(s) - 0 Average 1 2 3 4 5 Thread Modes Read fails - result too large Qofcheez Fresh Torrenter Posts: 3 Threads: 1 Joined: Sep 2014 Reputation: 0 #1 09-16-2014, 06:07 AM Over the past couple of weeks I've been dowloading a massive file - 160G. I'd gotten around 80% of it. Yesterday after a brief software update (OSX Snow Leopard) I suddenly lost the connection and got an error. Every attempt to restart the download has resulted in "Error: Disk read error - read fails - result too large". It always happens at 18.7% of the check. I did notice I was out of room on my hard drive so delete items to give me over 100G room (and emptied the trash) Since then I have: 1. updated Vuze 2. ran repair permissions in the disk utility 3. restarted numerous times 4. forced recheck of file 5. Tried running check with next to nothing else running I am really hoping not to have to start the download again, it has been going for so long and I was so close to finishing! Any thoughts? Find Reply GaryE Swarm Master Posts: 338 Threads: 2 Joined: Aug 2014 Reputation: 8 #2 09-16-2014, 09:53 AM (This post was last modified: 09-16-2014, 09:54 AM by GaryE.) It is a single file? Or multiple files? You said a file but I just want to be sure. If it is indeed a single file . . . the fact that you ran out of disk space might explain the problem. I am far from on expert on such things . . . but I would suspect that if you started writing a file and you ran out of space that the HD would go a bit haywire. You repaired the disk using disk utility (which seems like the right step to me) however, due to you running out of space and repairing the disk etc it is very possible that you really only have about 18% of the file at this point. I have had similar problems before . . . and it usually comes down to a bad file or a bad disk sector or something. I have not experienced this problem in several years but what I think I remember doing was to delete the bad file and just go on leeching the torrent. If the torrent really is just one huge file . . . this will of course mean deleting the whole thing and starting over. On the other hand if the torrent is indeed made up of individual files (which I find much much more likely) you just need to figure out which file(s) are at that 18.7% point and just delete those. Report back and I can try to explain to you how to find out which files to delete (assuming it is a multi file torrent). Find Reply Qofcheez Fresh Torrenter Posts: 3 Threads: 1 Joined: Sep 2014 Reputation: 0 #3 09-16-2014, 11:00 AM (This post was last modified: 09-16-2014, 1