Input/Output error on usb drive
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I have been trying to recover my usb flash drive and have been looking into this question
How to repair a corrupted FAT32 file system
I can not write data or anything into my drive it just gives me the error Input/output error
So I tried
sudo dosfsck -t -a -w /dev/sdb1
and result was like this
fsck.fat 4.1 (2017-01-24)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Automatically removing dirty bit.
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
67:a5/6a, 68:ea/9d, 69:23/81, 70:54/7c
Not automatically fixing this.
/.Trash-1000
Contains a free cluster (1002). Assuming EOF.
After this it gives error of each file in the drive like this
Cluster 3 (50031) is unreadable. Skipping it.
/FRIENDS/Copy of DSC00146.JPG
and then at the end it gives me this
Cluster 0 (52685) is unreadable. Skipping it. Write 4 bytes at
8024884:Input/output error
I couldn't recover my drive. I am asking here after trying my best. Please help me. Thanks
Note : I am using ubuntu 17.10
usb fsck
asked Apr 12 at 7:17
Moeed Azhar
97118
add a comment |Â
up vote
0
down vote
favorite
I have been trying to recover my usb flash drive and have been looking into this question
How to repair a corrupted FAT32 file system
I can not write data or anything into my drive it just gives me the error Input/output error
So I tried
sudo dosfsck -t -a -w /dev/sdb1
and result was like this
fsck.fat 4.1 (2017-01-24)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Automatically removing dirty bit.
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
67:a5/6a, 68:ea/9d, 69:23/81, 70:54/7c
Not automatically fixing this.
/.Trash-1000
Contains a free cluster (1002). Assuming EOF.
After this it gives error of each file in the drive like this
Cluster 3 (50031) is unreadable. Skipping it.
/FRIENDS/Copy of DSC00146.JPG
and then at the end it gives me this
Cluster 0 (52685) is unreadable. Skipping it. Write 4 bytes at
8024884:Input/output error
I couldn't recover my drive. I am asking here after trying my best. Please help me. Thanks
Note : I am using ubuntu 17.10
usb fsck
asked Apr 12 at 7:17
Moeed Azhar
97118
Please also tell me if there is a problem with hardware that can not be fixed ......
– Moeed Azhar
Apr 12 at 7:18
1
I/O errors usually mean faulty hardware. Do you care about the data on the USB drive? You should back it up somewhere then as soon as possible. After that, I would completely zero out the device (overwrite it completely with zeroes) usingsudo dd if=/dev/zero of=/dev/sdX bs=4M(replace sdX with the USB's device name as shown inlsblk. Make sure it is correct, whatever you specify here will be erased, you don't want to accidentally put your hard disk here!). Sometimes this overwriting gets a device back to work, or at least you will know for sure if it's dead. After that you can reformat it
– Byte Commander
Apr 12 at 7:42
This doesn't work ....
– Moeed Azhar
Apr 12 at 17:36
What doesn't work? If you encountered any error messages, please edit your question and describe what exactly did and what happened by adding the full commands you ran and their complete output. We can't guess what's going on on your machine unless you tell us.
– Byte Commander
Apr 12 at 20:00
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have been trying to recover my usb flash drive and have been looking into this question
How to repair a corrupted FAT32 file system
I can not write data or anything into my drive it just gives me the error Input/output error
So I tried
sudo dosfsck -t -a -w /dev/sdb1
and result was like this
fsck.fat 4.1 (2017-01-24)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Automatically removing dirty bit.
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
67:a5/6a, 68:ea/9d, 69:23/81, 70:54/7c
Not automatically fixing this.
/.Trash-1000
Contains a free cluster (1002). Assuming EOF.
After this it gives error of each file in the drive like this
Cluster 3 (50031) is unreadable. Skipping it.
/FRIENDS/Copy of DSC00146.JPG
and then at the end it gives me this
Cluster 0 (52685) is unreadable. Skipping it. Write 4 bytes at
8024884:Input/output error
I couldn't recover my drive. I am asking here after trying my best. Please help me. Thanks
Note : I am using ubuntu 17.10
usb fsck
asked Apr 12 at 7:17
Moeed Azhar
97118
I have been trying to recover my usb flash drive and have been looking into this question
How to repair a corrupted FAT32 file system
I can not write data or anything into my drive it just gives me the error Input/output error
So I tried
sudo dosfsck -t -a -w /dev/sdb1
and result was like this
fsck.fat 4.1 (2017-01-24)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Automatically removing dirty bit.
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
67:a5/6a, 68:ea/9d, 69:23/81, 70:54/7c
Not automatically fixing this.
/.Trash-1000
Contains a free cluster (1002). Assuming EOF.
After this it gives error of each file in the drive like this
Cluster 3 (50031) is unreadable. Skipping it.
/FRIENDS/Copy of DSC00146.JPG
and then at the end it gives me this
Cluster 0 (52685) is unreadable. Skipping it. Write 4 bytes at
8024884:Input/output error
I couldn't recover my drive. I am asking here after trying my best. Please help me. Thanks
Note : I am using ubuntu 17.10
usb fsck
usb fsck
asked Apr 12 at 7:17
Moeed Azhar
97118
asked Apr 12 at 7:17
Moeed Azhar
97118
asked Apr 12 at 7:17
Moeed Azhar
97118
asked Apr 12 at 7:17
Moeed Azhar
97118
asked Apr 12 at 7:17
Moeed Azhar
97118
97118
Please also tell me if there is a problem with hardware that can not be fixed ......
– Moeed Azhar
Apr 12 at 7:18
1
I/O errors usually mean faulty hardware. Do you care about the data on the USB drive? You should back it up somewhere then as soon as possible. After that, I would completely zero out the device (overwrite it completely with zeroes) usingsudo dd if=/dev/zero of=/dev/sdX bs=4M(replace sdX with the USB's device name as shown inlsblk. Make sure it is correct, whatever you specify here will be erased, you don't want to accidentally put your hard disk here!). Sometimes this overwriting gets a device back to work, or at least you will know for sure if it's dead. After that you can reformat it
– Byte Commander
Apr 12 at 7:42
This doesn't work ....
– Moeed Azhar
Apr 12 at 17:36
What doesn't work? If you encountered any error messages, please edit your question and describe what exactly did and what happened by adding the full commands you ran and their complete output. We can't guess what's going on on your machine unless you tell us.
– Byte Commander
Apr 12 at 20:00
add a comment |Â
Please also tell me if there is a problem with hardware that can not be fixed ......
– Moeed Azhar
Apr 12 at 7:18
1
I/O errors usually mean faulty hardware. Do you care about the data on the USB drive? You should back it up somewhere then as soon as possible. After that, I would completely zero out the device (overwrite it completely with zeroes) usingsudo dd if=/dev/zero of=/dev/sdX bs=4M(replace sdX with the USB's device name as shown inlsblk. Make sure it is correct, whatever you specify here will be erased, you don't want to accidentally put your hard disk here!). Sometimes this overwriting gets a device back to work, or at least you will know for sure if it's dead. After that you can reformat it
– Byte Commander
Apr 12 at 7:42
This doesn't work ....
– Moeed Azhar
Apr 12 at 17:36
What doesn't work? If you encountered any error messages, please edit your question and describe what exactly did and what happened by adding the full commands you ran and their complete output. We can't guess what's going on on your machine unless you tell us.
– Byte Commander
Apr 12 at 20:00
Please also tell me if there is a problem with hardware that can not be fixed ......
– Moeed Azhar
Apr 12 at 7:18
Please also tell me if there is a problem with hardware that can not be fixed ......
– Moeed Azhar
Apr 12 at 7:18
1
1
I/O errors usually mean faulty hardware. Do you care about the data on the USB drive? You should back it up somewhere then as soon as possible. After that, I would completely zero out the device (overwrite it completely with zeroes) using
sudo dd if=/dev/zero of=/dev/sdX bs=4M (replace sdX with the USB's device name as shown in lsblk. Make sure it is correct, whatever you specify here will be erased, you don't want to accidentally put your hard disk here!). Sometimes this overwriting gets a device back to work, or at least you will know for sure if it's dead. After that you can reformat it– Byte Commander
Apr 12 at 7:42
I/O errors usually mean faulty hardware. Do you care about the data on the USB drive? You should back it up somewhere then as soon as possible. After that, I would completely zero out the device (overwrite it completely with zeroes) using
sudo dd if=/dev/zero of=/dev/sdX bs=4M (replace sdX with the USB's device name as shown in lsblk. Make sure it is correct, whatever you specify here will be erased, you don't want to accidentally put your hard disk here!). Sometimes this overwriting gets a device back to work, or at least you will know for sure if it's dead. After that you can reformat it– Byte Commander
Apr 12 at 7:42
This doesn't work ....
– Moeed Azhar
Apr 12 at 17:36
This doesn't work ....
– Moeed Azhar
Apr 12 at 17:36
What doesn't work? If you encountered any error messages, please edit your question and describe what exactly did and what happened by adding the full commands you ran and their complete output. We can't guess what's going on on your machine unless you tell us.
– Byte Commander
Apr 12 at 20:00
What doesn't work? If you encountered any error messages, please edit your question and describe what exactly did and what happened by adding the full commands you ran and their complete output. We can't guess what's going on on your machine unless you tell us.
– Byte Commander
Apr 12 at 20:00
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1024265%2finput-output-error-on-usb-drive%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Please also tell me if there is a problem with hardware that can not be fixed ......
– Moeed Azhar
Apr 12 at 7:18
1
I/O errors usually mean faulty hardware. Do you care about the data on the USB drive? You should back it up somewhere then as soon as possible. After that, I would completely zero out the device (overwrite it completely with zeroes) using
sudo dd if=/dev/zero of=/dev/sdX bs=4M(replace sdX with the USB's device name as shown inlsblk. Make sure it is correct, whatever you specify here will be erased, you don't want to accidentally put your hard disk here!). Sometimes this overwriting gets a device back to work, or at least you will know for sure if it's dead. After that you can reformat it– Byte Commander
Apr 12 at 7:42
This doesn't work ....
– Moeed Azhar
Apr 12 at 17:36
What doesn't work? If you encountered any error messages, please edit your question and describe what exactly did and what happened by adding the full commands you ran and their complete output. We can't guess what's going on on your machine unless you tell us.
– Byte Commander
Apr 12 at 20:00