How do I repair a Fat 32 Filesystem Partition “input/output error”
up vote
5
down vote
favorite
Some how the partition (Dev/sda2) partition got deleted. So I use TestDisk to bring it back... The first time I did it it erase the whole hard drive... The second time it did restore the partition which is good. But now it is giving me a error massage when I try to open it in Files(Gnome).
IF you need it in text here: Error when getting information for file '/media/ubuntu-gnome/Backup/User': Input/output error
partitions error-handling fat32
add a comment |
up vote
5
down vote
favorite
Some how the partition (Dev/sda2) partition got deleted. So I use TestDisk to bring it back... The first time I did it it erase the whole hard drive... The second time it did restore the partition which is good. But now it is giving me a error massage when I try to open it in Files(Gnome).
IF you need it in text here: Error when getting information for file '/media/ubuntu-gnome/Backup/User': Input/output error
partitions error-handling fat32
checkdmesg
after getting this error for more details.
– psusi
Jun 7 '14 at 17:34
add a comment |
up vote
5
down vote
favorite
up vote
5
down vote
favorite
Some how the partition (Dev/sda2) partition got deleted. So I use TestDisk to bring it back... The first time I did it it erase the whole hard drive... The second time it did restore the partition which is good. But now it is giving me a error massage when I try to open it in Files(Gnome).
IF you need it in text here: Error when getting information for file '/media/ubuntu-gnome/Backup/User': Input/output error
partitions error-handling fat32
Some how the partition (Dev/sda2) partition got deleted. So I use TestDisk to bring it back... The first time I did it it erase the whole hard drive... The second time it did restore the partition which is good. But now it is giving me a error massage when I try to open it in Files(Gnome).
IF you need it in text here: Error when getting information for file '/media/ubuntu-gnome/Backup/User': Input/output error
partitions error-handling fat32
partitions error-handling fat32
asked Jun 7 '14 at 16:23
MathCubes
3,01583356
3,01583356
checkdmesg
after getting this error for more details.
– psusi
Jun 7 '14 at 17:34
add a comment |
checkdmesg
after getting this error for more details.
– psusi
Jun 7 '14 at 17:34
check
dmesg
after getting this error for more details.– psusi
Jun 7 '14 at 17:34
check
dmesg
after getting this error for more details.– psusi
Jun 7 '14 at 17:34
add a comment |
3 Answers
3
active
oldest
votes
up vote
1
down vote
Try running
sudo dosfsck -r
a few times and see if that fixes things. Good luck.
This work for me, allows me delete theOrphaned long file name part "2013-12-31--18-26-31 ALPS.KK1.MP1.V2.46
" thanks
– Milor123
Feb 9 '17 at 15:37
add a comment |
up vote
-1
down vote
Repair the file system
It seems your file system is corrupted.
You can attempt to fix it by executing this command in your Terminal:
sudo fsck -y
/dev/sda2
Replace /dev/sda2
with the appropriate partition you want to fix.
fsck from util-linux 2.20.1 e2fsck 1.42.9 (4-Feb-2014) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/sda2 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device>
– MathCubes
Jun 7 '14 at 19:00
What is the filesystem of /dev/sda2?
– Naveen
Jun 8 '14 at 1:52
add a comment |
up vote
-1
down vote
I had this problem about an hour ago, and I was searching to find an answer, then i found this forum. I just fixed my usb, and here is what I did:
sudo mkfs.vfat /dev/sdXY
(Note: This FORMATS ALL DATA on your partition and fixes the problem.)
(Note: First unmount your device)
Now my usb is working as well.
THIS JUST FORMATTED MY DRIVE!!!
– Jamie Hutber
Nov 18 at 21:10
I'm so sorry for what happened to your drive. I had to tell that this format the partition but fixes the problem. I can recovery your hard just like it was before, but don't know how to send you a message. Give me your Gmail or telegram or Instagram ID, I'll help you recovery it as fast as possible. Sorry Again.
– Mohammad Kholghi
Nov 20 at 15:18
add a comment |
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Try running
sudo dosfsck -r
a few times and see if that fixes things. Good luck.
This work for me, allows me delete theOrphaned long file name part "2013-12-31--18-26-31 ALPS.KK1.MP1.V2.46
" thanks
– Milor123
Feb 9 '17 at 15:37
add a comment |
up vote
1
down vote
Try running
sudo dosfsck -r
a few times and see if that fixes things. Good luck.
This work for me, allows me delete theOrphaned long file name part "2013-12-31--18-26-31 ALPS.KK1.MP1.V2.46
" thanks
– Milor123
Feb 9 '17 at 15:37
add a comment |
up vote
1
down vote
up vote
1
down vote
Try running
sudo dosfsck -r
a few times and see if that fixes things. Good luck.
Try running
sudo dosfsck -r
a few times and see if that fixes things. Good luck.
answered Jun 7 '14 at 16:40
ubfan1
9,12141527
9,12141527
This work for me, allows me delete theOrphaned long file name part "2013-12-31--18-26-31 ALPS.KK1.MP1.V2.46
" thanks
– Milor123
Feb 9 '17 at 15:37
add a comment |
This work for me, allows me delete theOrphaned long file name part "2013-12-31--18-26-31 ALPS.KK1.MP1.V2.46
" thanks
– Milor123
Feb 9 '17 at 15:37
This work for me, allows me delete the
Orphaned long file name part "2013-12-31--18-26-31 ALPS.KK1.MP1.V2.46
" thanks– Milor123
Feb 9 '17 at 15:37
This work for me, allows me delete the
Orphaned long file name part "2013-12-31--18-26-31 ALPS.KK1.MP1.V2.46
" thanks– Milor123
Feb 9 '17 at 15:37
add a comment |
up vote
-1
down vote
Repair the file system
It seems your file system is corrupted.
You can attempt to fix it by executing this command in your Terminal:
sudo fsck -y
/dev/sda2
Replace /dev/sda2
with the appropriate partition you want to fix.
fsck from util-linux 2.20.1 e2fsck 1.42.9 (4-Feb-2014) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/sda2 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device>
– MathCubes
Jun 7 '14 at 19:00
What is the filesystem of /dev/sda2?
– Naveen
Jun 8 '14 at 1:52
add a comment |
up vote
-1
down vote
Repair the file system
It seems your file system is corrupted.
You can attempt to fix it by executing this command in your Terminal:
sudo fsck -y
/dev/sda2
Replace /dev/sda2
with the appropriate partition you want to fix.
fsck from util-linux 2.20.1 e2fsck 1.42.9 (4-Feb-2014) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/sda2 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device>
– MathCubes
Jun 7 '14 at 19:00
What is the filesystem of /dev/sda2?
– Naveen
Jun 8 '14 at 1:52
add a comment |
up vote
-1
down vote
up vote
-1
down vote
Repair the file system
It seems your file system is corrupted.
You can attempt to fix it by executing this command in your Terminal:
sudo fsck -y
/dev/sda2
Replace /dev/sda2
with the appropriate partition you want to fix.
Repair the file system
It seems your file system is corrupted.
You can attempt to fix it by executing this command in your Terminal:
sudo fsck -y
/dev/sda2
Replace /dev/sda2
with the appropriate partition you want to fix.
answered Jun 7 '14 at 16:41
Naveen
6,43493564
6,43493564
fsck from util-linux 2.20.1 e2fsck 1.42.9 (4-Feb-2014) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/sda2 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device>
– MathCubes
Jun 7 '14 at 19:00
What is the filesystem of /dev/sda2?
– Naveen
Jun 8 '14 at 1:52
add a comment |
fsck from util-linux 2.20.1 e2fsck 1.42.9 (4-Feb-2014) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/sda2 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device>
– MathCubes
Jun 7 '14 at 19:00
What is the filesystem of /dev/sda2?
– Naveen
Jun 8 '14 at 1:52
fsck from util-linux 2.20.1 e2fsck 1.42.9 (4-Feb-2014) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/sda2 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device>
– MathCubes
Jun 7 '14 at 19:00
fsck from util-linux 2.20.1 e2fsck 1.42.9 (4-Feb-2014) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/sda2 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device>
– MathCubes
Jun 7 '14 at 19:00
What is the filesystem of /dev/sda2?
– Naveen
Jun 8 '14 at 1:52
What is the filesystem of /dev/sda2?
– Naveen
Jun 8 '14 at 1:52
add a comment |
up vote
-1
down vote
I had this problem about an hour ago, and I was searching to find an answer, then i found this forum. I just fixed my usb, and here is what I did:
sudo mkfs.vfat /dev/sdXY
(Note: This FORMATS ALL DATA on your partition and fixes the problem.)
(Note: First unmount your device)
Now my usb is working as well.
THIS JUST FORMATTED MY DRIVE!!!
– Jamie Hutber
Nov 18 at 21:10
I'm so sorry for what happened to your drive. I had to tell that this format the partition but fixes the problem. I can recovery your hard just like it was before, but don't know how to send you a message. Give me your Gmail or telegram or Instagram ID, I'll help you recovery it as fast as possible. Sorry Again.
– Mohammad Kholghi
Nov 20 at 15:18
add a comment |
up vote
-1
down vote
I had this problem about an hour ago, and I was searching to find an answer, then i found this forum. I just fixed my usb, and here is what I did:
sudo mkfs.vfat /dev/sdXY
(Note: This FORMATS ALL DATA on your partition and fixes the problem.)
(Note: First unmount your device)
Now my usb is working as well.
THIS JUST FORMATTED MY DRIVE!!!
– Jamie Hutber
Nov 18 at 21:10
I'm so sorry for what happened to your drive. I had to tell that this format the partition but fixes the problem. I can recovery your hard just like it was before, but don't know how to send you a message. Give me your Gmail or telegram or Instagram ID, I'll help you recovery it as fast as possible. Sorry Again.
– Mohammad Kholghi
Nov 20 at 15:18
add a comment |
up vote
-1
down vote
up vote
-1
down vote
I had this problem about an hour ago, and I was searching to find an answer, then i found this forum. I just fixed my usb, and here is what I did:
sudo mkfs.vfat /dev/sdXY
(Note: This FORMATS ALL DATA on your partition and fixes the problem.)
(Note: First unmount your device)
Now my usb is working as well.
I had this problem about an hour ago, and I was searching to find an answer, then i found this forum. I just fixed my usb, and here is what I did:
sudo mkfs.vfat /dev/sdXY
(Note: This FORMATS ALL DATA on your partition and fixes the problem.)
(Note: First unmount your device)
Now my usb is working as well.
edited Nov 23 at 14:16
answered Jul 9 at 17:13
Mohammad Kholghi
83
83
THIS JUST FORMATTED MY DRIVE!!!
– Jamie Hutber
Nov 18 at 21:10
I'm so sorry for what happened to your drive. I had to tell that this format the partition but fixes the problem. I can recovery your hard just like it was before, but don't know how to send you a message. Give me your Gmail or telegram or Instagram ID, I'll help you recovery it as fast as possible. Sorry Again.
– Mohammad Kholghi
Nov 20 at 15:18
add a comment |
THIS JUST FORMATTED MY DRIVE!!!
– Jamie Hutber
Nov 18 at 21:10
I'm so sorry for what happened to your drive. I had to tell that this format the partition but fixes the problem. I can recovery your hard just like it was before, but don't know how to send you a message. Give me your Gmail or telegram or Instagram ID, I'll help you recovery it as fast as possible. Sorry Again.
– Mohammad Kholghi
Nov 20 at 15:18
THIS JUST FORMATTED MY DRIVE!!!
– Jamie Hutber
Nov 18 at 21:10
THIS JUST FORMATTED MY DRIVE!!!
– Jamie Hutber
Nov 18 at 21:10
I'm so sorry for what happened to your drive. I had to tell that this format the partition but fixes the problem. I can recovery your hard just like it was before, but don't know how to send you a message. Give me your Gmail or telegram or Instagram ID, I'll help you recovery it as fast as possible. Sorry Again.
– Mohammad Kholghi
Nov 20 at 15:18
I'm so sorry for what happened to your drive. I had to tell that this format the partition but fixes the problem. I can recovery your hard just like it was before, but don't know how to send you a message. Give me your Gmail or telegram or Instagram ID, I'll help you recovery it as fast as possible. Sorry Again.
– Mohammad Kholghi
Nov 20 at 15:18
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f478124%2fhow-do-i-repair-a-fat-32-filesystem-partition-input-output-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
check
dmesg
after getting this error for more details.– psusi
Jun 7 '14 at 17:34