wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
0
I'm encountering this error after creating a brand new partition.
What I did:
# fdisk -l
Disk /dev/sdb: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 6E6B69EE-CD95-47E3-94A0-AA9190306D40
# fdisk /dev/sdb
Welcome to fdisk (util-linux 2.31.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): n
Partition number (1-128, default 1): 1
First sector (34-7814037133, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-7814037133, default 7814037133):
Created a new partition 1 of type 'Linux filesystem' and of size 3.7 TiB.
Partition #1 contains a ext4 signature.
Do you want to remove the signature? [Y]es/[N]o: n
Command (m for help): p
Disk /dev/sdb: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 6E6B69EE-CD95-47E3-94A0-AA9190306D40
Device Start End Sectors Size Type
/dev/sdb1 2048 7814037133 7814035086 3.7T Linux filesystem
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
After that, this was the output of fdisk -l:
Disk /dev/sdb: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 6E6B69EE-CD95-47E3-94A0-AA9190306D40
Device Start End Sectors Size Type
/dev/sdb1 2048 7814037133 7814035086 3.7T Linux filesystem
That's the error I get when mounting:
sudo mount /dev/sdb1 /mnt/data_storage/
mount: /mnt/data_storage: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
It's worth noting that all those operation were executed on the same machine, and that machine is an aarch64 with Ubuntu 18.04.1.
The same operations executed on an x64 Ubuntu 18.04 computer resulted in a correct ext4 partition which I was able to mount and read/write.
What could be the issue here?
linux ubuntu hard-drive partitioning mount
asked Feb 6 at 23:36
HarlandrakaHarlandraka
2401623
add a comment |
0
I'm encountering this error after creating a brand new partition.
What I did:
# fdisk -l
Disk /dev/sdb: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 6E6B69EE-CD95-47E3-94A0-AA9190306D40
# fdisk /dev/sdb
Welcome to fdisk (util-linux 2.31.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): n
Partition number (1-128, default 1): 1
First sector (34-7814037133, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-7814037133, default 7814037133):
Created a new partition 1 of type 'Linux filesystem' and of size 3.7 TiB.
Partition #1 contains a ext4 signature.
Do you want to remove the signature? [Y]es/[N]o: n
Command (m for help): p
Disk /dev/sdb: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 6E6B69EE-CD95-47E3-94A0-AA9190306D40
Device Start End Sectors Size Type
/dev/sdb1 2048 7814037133 7814035086 3.7T Linux filesystem
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
After that, this was the output of fdisk -l:
Disk /dev/sdb: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 6E6B69EE-CD95-47E3-94A0-AA9190306D40
Device Start End Sectors Size Type
/dev/sdb1 2048 7814037133 7814035086 3.7T Linux filesystem
That's the error I get when mounting:
sudo mount /dev/sdb1 /mnt/data_storage/
mount: /mnt/data_storage: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
It's worth noting that all those operation were executed on the same machine, and that machine is an aarch64 with Ubuntu 18.04.1.
The same operations executed on an x64 Ubuntu 18.04 computer resulted in a correct ext4 partition which I was able to mount and read/write.
What could be the issue here?
linux ubuntu hard-drive partitioning mount
asked Feb 6 at 23:36
HarlandrakaHarlandraka
2401623
4
Did you create the file system? For examplemkfs.ext4 /dev/sdb1...
– lx07
Feb 7 at 0:30
It's usually easier to usegpartedto do all the steps automatically, it even does awipefsbefore formatting to avoid any old problems
– Xen2050
Feb 7 at 10:21
@lx07 I didn't. I should try to.
– Harlandraka
Feb 7 at 10:31
@Xen2050 I used GParted the first time. I was on my Ubuntu 18.04 Desktop x64, I deleted all partitions, created a new partition table and an ext4 partition. I was able to mount the partition and write my data, but after connecting the disk to my aarch64 device (a Pine64 equipped with ARMBian) that error appeared.
– Harlandraka
Feb 7 at 10:32
add a comment |
0
0
0
I'm encountering this error after creating a brand new partition.
What I did:
# fdisk -l
Disk /dev/sdb: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 6E6B69EE-CD95-47E3-94A0-AA9190306D40
# fdisk /dev/sdb
Welcome to fdisk (util-linux 2.31.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): n
Partition number (1-128, default 1): 1
First sector (34-7814037133, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-7814037133, default 7814037133):
Created a new partition 1 of type 'Linux filesystem' and of size 3.7 TiB.
Partition #1 contains a ext4 signature.
Do you want to remove the signature? [Y]es/[N]o: n
Command (m for help): p
Disk /dev/sdb: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 6E6B69EE-CD95-47E3-94A0-AA9190306D40
Device Start End Sectors Size Type
/dev/sdb1 2048 7814037133 7814035086 3.7T Linux filesystem
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
After that, this was the output of fdisk -l:
Disk /dev/sdb: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 6E6B69EE-CD95-47E3-94A0-AA9190306D40
Device Start End Sectors Size Type
/dev/sdb1 2048 7814037133 7814035086 3.7T Linux filesystem
That's the error I get when mounting:
sudo mount /dev/sdb1 /mnt/data_storage/
mount: /mnt/data_storage: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
It's worth noting that all those operation were executed on the same machine, and that machine is an aarch64 with Ubuntu 18.04.1.
The same operations executed on an x64 Ubuntu 18.04 computer resulted in a correct ext4 partition which I was able to mount and read/write.
What could be the issue here?
linux ubuntu hard-drive partitioning mount
asked Feb 6 at 23:36
HarlandrakaHarlandraka
2401623
I'm encountering this error after creating a brand new partition.
What I did:
# fdisk -l
Disk /dev/sdb: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 6E6B69EE-CD95-47E3-94A0-AA9190306D40
# fdisk /dev/sdb
Welcome to fdisk (util-linux 2.31.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): n
Partition number (1-128, default 1): 1
First sector (34-7814037133, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-7814037133, default 7814037133):
Created a new partition 1 of type 'Linux filesystem' and of size 3.7 TiB.
Partition #1 contains a ext4 signature.
Do you want to remove the signature? [Y]es/[N]o: n
Command (m for help): p
Disk /dev/sdb: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 6E6B69EE-CD95-47E3-94A0-AA9190306D40
Device Start End Sectors Size Type
/dev/sdb1 2048 7814037133 7814035086 3.7T Linux filesystem
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
After that, this was the output of fdisk -l:
Disk /dev/sdb: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 6E6B69EE-CD95-47E3-94A0-AA9190306D40
Device Start End Sectors Size Type
/dev/sdb1 2048 7814037133 7814035086 3.7T Linux filesystem
That's the error I get when mounting:
sudo mount /dev/sdb1 /mnt/data_storage/
mount: /mnt/data_storage: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
It's worth noting that all those operation were executed on the same machine, and that machine is an aarch64 with Ubuntu 18.04.1.
The same operations executed on an x64 Ubuntu 18.04 computer resulted in a correct ext4 partition which I was able to mount and read/write.
What could be the issue here?
linux ubuntu hard-drive partitioning mount
linux ubuntu hard-drive partitioning mount
asked Feb 6 at 23:36
HarlandrakaHarlandraka
2401623
asked Feb 6 at 23:36
HarlandrakaHarlandraka
2401623
asked Feb 6 at 23:36
HarlandrakaHarlandraka
2401623
asked Feb 6 at 23:36
HarlandrakaHarlandraka
2401623
asked Feb 6 at 23:36
HarlandrakaHarlandraka
2401623
2401623
4
Did you create the file system? For examplemkfs.ext4 /dev/sdb1...
– lx07
Feb 7 at 0:30
It's usually easier to usegpartedto do all the steps automatically, it even does awipefsbefore formatting to avoid any old problems
– Xen2050
Feb 7 at 10:21
@lx07 I didn't. I should try to.
– Harlandraka
Feb 7 at 10:31
@Xen2050 I used GParted the first time. I was on my Ubuntu 18.04 Desktop x64, I deleted all partitions, created a new partition table and an ext4 partition. I was able to mount the partition and write my data, but after connecting the disk to my aarch64 device (a Pine64 equipped with ARMBian) that error appeared.
– Harlandraka
Feb 7 at 10:32
add a comment |
4
Did you create the file system? For examplemkfs.ext4 /dev/sdb1...
– lx07
Feb 7 at 0:30
It's usually easier to usegpartedto do all the steps automatically, it even does awipefsbefore formatting to avoid any old problems
– Xen2050
Feb 7 at 10:21
@lx07 I didn't. I should try to.
– Harlandraka
Feb 7 at 10:31
@Xen2050 I used GParted the first time. I was on my Ubuntu 18.04 Desktop x64, I deleted all partitions, created a new partition table and an ext4 partition. I was able to mount the partition and write my data, but after connecting the disk to my aarch64 device (a Pine64 equipped with ARMBian) that error appeared.
– Harlandraka
Feb 7 at 10:32
4
4
Did you create the file system? For example
mkfs.ext4 /dev/sdb1...– lx07
Feb 7 at 0:30
Did you create the file system? For example
mkfs.ext4 /dev/sdb1...– lx07
Feb 7 at 0:30
It's usually easier to use
gparted to do all the steps automatically, it even does a wipefs before formatting to avoid any old problems– Xen2050
Feb 7 at 10:21
It's usually easier to use
gparted to do all the steps automatically, it even does a wipefs before formatting to avoid any old problems– Xen2050
Feb 7 at 10:21
@lx07 I didn't. I should try to.
– Harlandraka
Feb 7 at 10:31
@lx07 I didn't. I should try to.
– Harlandraka
Feb 7 at 10:31
@Xen2050 I used GParted the first time. I was on my Ubuntu 18.04 Desktop x64, I deleted all partitions, created a new partition table and an ext4 partition. I was able to mount the partition and write my data, but after connecting the disk to my aarch64 device (a Pine64 equipped with ARMBian) that error appeared.
– Harlandraka
Feb 7 at 10:32
@Xen2050 I used GParted the first time. I was on my Ubuntu 18.04 Desktop x64, I deleted all partitions, created a new partition table and an ext4 partition. I was able to mount the partition and write my data, but after connecting the disk to my aarch64 device (a Pine64 equipped with ARMBian) that error appeared.
– Harlandraka
Feb 7 at 10:32
add a comment |
0
active
oldest
votes
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
});
}
});
draft saved
draft discarded
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%2f1402909%2fwrong-fs-type-bad-option-bad-superblock-on-dev-sdb1-missing-codepage-or-help%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
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f1402909%2fwrong-fs-type-bad-option-bad-superblock-on-dev-sdb1-missing-codepage-or-help%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
4
Did you create the file system? For example
mkfs.ext4 /dev/sdb1...– lx07
Feb 7 at 0:30
It's usually easier to use
gpartedto do all the steps automatically, it even does awipefsbefore formatting to avoid any old problems– Xen2050
Feb 7 at 10:21
@lx07 I didn't. I should try to.
– Harlandraka
Feb 7 at 10:31
@Xen2050 I used GParted the first time. I was on my Ubuntu 18.04 Desktop x64, I deleted all partitions, created a new partition table and an ext4 partition. I was able to mount the partition and write my data, but after connecting the disk to my aarch64 device (a Pine64 equipped with ARMBian) that error appeared.
– Harlandraka
Feb 7 at 10:32