Chromebook fails to mount ext4 USB drive with valid FS
On my Chromebook, I followed these steps to make an ext4 partition on a USB drive. Once the process was completed, when the the USB drive is plugged back in, Chromebook detects the drive and mounts it. No problems there.
If I were to mount the USB drive on a Linux host, touch a new file or something, eject and then plug back into the Chrome book, I get the popup saying the media is not recognized. If I were to mount manually from crosh/shell, I get the following error:
mount: /media/removable/foo: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
This is puzzling because the drive is not corrupted at all as I can still mount/read/write same drive on the a Linux host.
Essentially, Chromebook refuses to mount an FS that was used--and is still usable--elsewhere. What could be going wrong here? How can I troubleshoot this?
mount chromebook
asked Dec 22 '18 at 15:18
Jeenu
22614
add a comment |
On my Chromebook, I followed these steps to make an ext4 partition on a USB drive. Once the process was completed, when the the USB drive is plugged back in, Chromebook detects the drive and mounts it. No problems there.
If I were to mount the USB drive on a Linux host, touch a new file or something, eject and then plug back into the Chrome book, I get the popup saying the media is not recognized. If I were to mount manually from crosh/shell, I get the following error:
mount: /media/removable/foo: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
This is puzzling because the drive is not corrupted at all as I can still mount/read/write same drive on the a Linux host.
Essentially, Chromebook refuses to mount an FS that was used--and is still usable--elsewhere. What could be going wrong here? How can I troubleshoot this?
mount chromebook
asked Dec 22 '18 at 15:18
Jeenu
22614
add a comment |
On my Chromebook, I followed these steps to make an ext4 partition on a USB drive. Once the process was completed, when the the USB drive is plugged back in, Chromebook detects the drive and mounts it. No problems there.
If I were to mount the USB drive on a Linux host, touch a new file or something, eject and then plug back into the Chrome book, I get the popup saying the media is not recognized. If I were to mount manually from crosh/shell, I get the following error:
mount: /media/removable/foo: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
This is puzzling because the drive is not corrupted at all as I can still mount/read/write same drive on the a Linux host.
Essentially, Chromebook refuses to mount an FS that was used--and is still usable--elsewhere. What could be going wrong here? How can I troubleshoot this?
mount chromebook
asked Dec 22 '18 at 15:18
Jeenu
22614
On my Chromebook, I followed these steps to make an ext4 partition on a USB drive. Once the process was completed, when the the USB drive is plugged back in, Chromebook detects the drive and mounts it. No problems there.
If I were to mount the USB drive on a Linux host, touch a new file or something, eject and then plug back into the Chrome book, I get the popup saying the media is not recognized. If I were to mount manually from crosh/shell, I get the following error:
mount: /media/removable/foo: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
This is puzzling because the drive is not corrupted at all as I can still mount/read/write same drive on the a Linux host.
Essentially, Chromebook refuses to mount an FS that was used--and is still usable--elsewhere. What could be going wrong here? How can I troubleshoot this?
mount chromebook
mount chromebook
asked Dec 22 '18 at 15:18
Jeenu
22614
asked Dec 22 '18 at 15:18
Jeenu
22614
edited Dec 22 '18 at 16:19
asked Dec 22 '18 at 15:18
Jeenu
22614
asked Dec 22 '18 at 15:18
Jeenu
22614
asked Dec 22 '18 at 15:18
Jeenu
22614
22614
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The problem appears to be that the Linux host (later kernel) modifies the journalling features to contain journal_64bit journal_checksum_v3 which Chromebook (older kernel) is not happy about. The Chromebook kernel quite possibly is missing this fix.
Thanks to LQ for pointers.
answered Dec 23 '18 at 17:39
Jeenu
22614
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});
}
});
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%2fsuperuser.com%2fquestions%2f1386947%2fchromebook-fails-to-mount-ext4-usb-drive-with-valid-fs%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The problem appears to be that the Linux host (later kernel) modifies the journalling features to contain journal_64bit journal_checksum_v3 which Chromebook (older kernel) is not happy about. The Chromebook kernel quite possibly is missing this fix.
Thanks to LQ for pointers.
answered Dec 23 '18 at 17:39
Jeenu
22614
add a comment |
The problem appears to be that the Linux host (later kernel) modifies the journalling features to contain journal_64bit journal_checksum_v3 which Chromebook (older kernel) is not happy about. The Chromebook kernel quite possibly is missing this fix.
Thanks to LQ for pointers.
answered Dec 23 '18 at 17:39
Jeenu
22614
add a comment |
The problem appears to be that the Linux host (later kernel) modifies the journalling features to contain journal_64bit journal_checksum_v3 which Chromebook (older kernel) is not happy about. The Chromebook kernel quite possibly is missing this fix.
Thanks to LQ for pointers.
answered Dec 23 '18 at 17:39
Jeenu
22614
The problem appears to be that the Linux host (later kernel) modifies the journalling features to contain journal_64bit journal_checksum_v3 which Chromebook (older kernel) is not happy about. The Chromebook kernel quite possibly is missing this fix.
Thanks to LQ for pointers.
answered Dec 23 '18 at 17:39
Jeenu
22614
answered Dec 23 '18 at 17:39
Jeenu
22614
answered Dec 23 '18 at 17:39
Jeenu
22614
answered Dec 23 '18 at 17:39
Jeenu
22614
22614
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
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%2fsuperuser.com%2fquestions%2f1386947%2fchromebook-fails-to-mount-ext4-usb-drive-with-valid-fs%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
