One machine recognized disk as corrupt, works fine on another

Was Jesus good at singing?

What is the actual quality of machine translations?

Does Disney no longer produce hand-drawn cartoon films?

Why doesn’t a normal window produce an apparent rainbow?

How Can I Tell The Difference Between Unmarked Sugar and Stevia?

What's the name of this light airplane?

What is the giant octopus in the torture chamber for?

Taxi Services at Didcot

If you had a giant cutting disc 60 miles diameter and rotated it 1000 rps, would the edge be traveling faster than light?

Using a found spellbook as a Sorcerer-Wizard multiclass

Inconsistent behavior of compiler optimization of unused string

What language is the software written in on the ISS?

Is using haveibeenpwned to validate password strength rational?

Trapping Rain Water

Chemmacros scheme translation

How would a aircraft visually signal "in distress"?

Compiling c files on ubuntu and using the executable on Windows

Should I give professor gift at the beginning of my PhD?

Movie about a boy who was born old and grew young

When conversion from Integer to Single may lose precision

How can drunken, homicidal elves successfully conduct a wild hunt?

How to officially communicate to a non-responsive colleague?

How to retract an idea already pitched to an employer?

Why only the fundamental frequency component is said to give useful power?



One machine recognized disk as corrupt, works fine on another







.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















I have a Western Digital USB hard drive which I typically leave connected to a Raspberry Pi. Today I noticed that the drive wasn't mounted anymore, and didn't see anything in the syslog to explain why. When I ran sudo mount /dev/sdc /media/pi/media-2/ to re-mount it, I got:



mount: wrong fs type, bad option, bad superblock on /dev/sdc,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.


And sudo fsck /dev/sdc gave



fsck from util-linux 2.29.2
e2fsck 1.43.4 (31-Jan-2017)
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/sdc

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>

Found a gpt partition table in /dev/sdc


When I connect it to my laptop running Ubuntu 18.04, it mounts just fine and fsck returns:



fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
media-2: clean, 1175/122093568 files, 422501325/488369920 blocks


On the pi, I tried connecting it to each of the USB ports and it didn't make any difference. Any idea why it works on one machine and not another?










share|improve this question







New contributor



xanderflood is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • you should run lsblk on both systems to double-check you're running your command on the same block device. Hint: "Found a gpt partition table in /dev/sdc"

    – A.B
    1 hour ago


















0















I have a Western Digital USB hard drive which I typically leave connected to a Raspberry Pi. Today I noticed that the drive wasn't mounted anymore, and didn't see anything in the syslog to explain why. When I ran sudo mount /dev/sdc /media/pi/media-2/ to re-mount it, I got:



mount: wrong fs type, bad option, bad superblock on /dev/sdc,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.


And sudo fsck /dev/sdc gave



fsck from util-linux 2.29.2
e2fsck 1.43.4 (31-Jan-2017)
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/sdc

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>

Found a gpt partition table in /dev/sdc


When I connect it to my laptop running Ubuntu 18.04, it mounts just fine and fsck returns:



fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
media-2: clean, 1175/122093568 files, 422501325/488369920 blocks


On the pi, I tried connecting it to each of the USB ports and it didn't make any difference. Any idea why it works on one machine and not another?










share|improve this question







New contributor



xanderflood is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • you should run lsblk on both systems to double-check you're running your command on the same block device. Hint: "Found a gpt partition table in /dev/sdc"

    – A.B
    1 hour ago














0












0








0








I have a Western Digital USB hard drive which I typically leave connected to a Raspberry Pi. Today I noticed that the drive wasn't mounted anymore, and didn't see anything in the syslog to explain why. When I ran sudo mount /dev/sdc /media/pi/media-2/ to re-mount it, I got:



mount: wrong fs type, bad option, bad superblock on /dev/sdc,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.


And sudo fsck /dev/sdc gave



fsck from util-linux 2.29.2
e2fsck 1.43.4 (31-Jan-2017)
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/sdc

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>

Found a gpt partition table in /dev/sdc


When I connect it to my laptop running Ubuntu 18.04, it mounts just fine and fsck returns:



fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
media-2: clean, 1175/122093568 files, 422501325/488369920 blocks


On the pi, I tried connecting it to each of the USB ports and it didn't make any difference. Any idea why it works on one machine and not another?










share|improve this question







New contributor



xanderflood is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











I have a Western Digital USB hard drive which I typically leave connected to a Raspberry Pi. Today I noticed that the drive wasn't mounted anymore, and didn't see anything in the syslog to explain why. When I ran sudo mount /dev/sdc /media/pi/media-2/ to re-mount it, I got:



mount: wrong fs type, bad option, bad superblock on /dev/sdc,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.


And sudo fsck /dev/sdc gave



fsck from util-linux 2.29.2
e2fsck 1.43.4 (31-Jan-2017)
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/sdc

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>

Found a gpt partition table in /dev/sdc


When I connect it to my laptop running Ubuntu 18.04, it mounts just fine and fsck returns:



fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
media-2: clean, 1175/122093568 files, 422501325/488369920 blocks


On the pi, I tried connecting it to each of the USB ports and it didn't make any difference. Any idea why it works on one machine and not another?







hard-disk disk






share|improve this question







New contributor



xanderflood is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.










share|improve this question







New contributor



xanderflood is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








share|improve this question




share|improve this question






New contributor



xanderflood is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








asked 1 hour ago









xanderfloodxanderflood

101




101




New contributor



xanderflood is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




New contributor




xanderflood is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.















  • you should run lsblk on both systems to double-check you're running your command on the same block device. Hint: "Found a gpt partition table in /dev/sdc"

    – A.B
    1 hour ago



















  • you should run lsblk on both systems to double-check you're running your command on the same block device. Hint: "Found a gpt partition table in /dev/sdc"

    – A.B
    1 hour ago

















you should run lsblk on both systems to double-check you're running your command on the same block device. Hint: "Found a gpt partition table in /dev/sdc"

– A.B
1 hour ago





you should run lsblk on both systems to double-check you're running your command on the same block device. Hint: "Found a gpt partition table in /dev/sdc"

– A.B
1 hour ago










0






active

oldest

votes












Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});






xanderflood is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f522735%2fone-machine-recognized-disk-as-corrupt-works-fine-on-another%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes








xanderflood is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















xanderflood is a new contributor. Be nice, and check out our Code of Conduct.













xanderflood is a new contributor. Be nice, and check out our Code of Conduct.












xanderflood is a new contributor. Be nice, and check out our Code of Conduct.
















Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f522735%2fone-machine-recognized-disk-as-corrupt-works-fine-on-another%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...