Linux - couldn't mount RDWR because of unsupported optional features (400)
I try to run Android from SD-card. This card is prepared. There are partitions: boot(FAT32)
, rootfs(ext4)
, system(ext4)
, cache(ext4)
and usedata(ext4)
. Boot partitions has files to run u-boot: MLO
, u-boot.bin
and uImage
. To run it I use commands
mmcinit 0
fatload mmc 0 0x80000000 uImage
setenv bootargs 'console=ttyO2,115200n8 mem=456M@0x80000000 mem=512M@0xA0000000 init=/init vram=10M omapfb.vram=0:4M androidboot.console=ttyO2 root=/dev/mmcblk1p2 rw rootwait rootfstype=ext4'
bootm 0x80000000
Than I see how Linux starts. But after few seconds on step of loading rootfs
I see an error message
[ 4.015655] EXT4-fs (mmcblk1p2): couldn't mount RDWR because of unsupported optional features (400)
[ 4.036499] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 4.079986] List of all partitions:
[ 4.083801] b300 31162368 mmcblk0 driver: mmcblk
[ 4.089660] b301 128 mmcblk0p1 f9f21f00-a8d4-5f0e-9746-594869aec34e
[ 4.097839] b302 256 mmcblk0p2 f9f21f01-a8d4-5f0e-9746-594869aec34e
[ 4.106018] b303 128 mmcblk0p3 f9f21f02-a8d4-5f0e-9746-594869aec34e
[ 4.114288] b304 16384 mmcblk0p4 f9f21f03-a8d4-5f0e-9746-594869aec34e
[ 4.122436] b305 16 mmcblk0p5 f9f21f04-a8d4-5f0e-9746-594869aec34e
[ 4.130676] b306 8192 mmcblk0p6 f9f21f05-a8d4-5f0e-9746-594869aec34e
[ 4.138916] b307 8192 mmcblk0p7 f9f21f06-a8d4-5f0e-9746-594869aec34e
[ 4.147094] 103:00000 524288 mmcblk0p8 f9f21f07-a8d4-5f0e-9746-594869aec34e
[ 4.155334] 103:00001 262144 mmcblk0p9 f9f21f08-a8d4-5f0e-9746-594869aec34e
[ 4.163574] 103:00002 30342128 mmcblk0p10 f9f21f09-a8d4-5f0e-9746-594869aec34e
[ 4.171874] b310 2048 mmcblk0boot1 (driver?)
[ 4.177734] b308 2048 mmcblk0boot0 (driver?)
[ 4.183593] b318 15179776 mmcblk1 driver: mmcblk
[ 4.189453] b319 102400 mmcblk1p1 00000000-0000-0000-0000-000000000000
[ 4.197692] b31a 10240 mmcblk1p2 00000000-0000-0000-0000-000000000000
[ 4.205932] b31b 1 mmcblk1p3 00000000-0000-0000-0000-000000000000
[ 4.214141] b31d 262144 mmcblk1p5 00000000-0000-0000-0000-000000000000
[ 4.222351] b31e 13228032 mmcblk1p6 00000000-0000-0000-0000-000000000000
[ 4.230682] b31f 1572864 mmcblk1p7 00000000-0000-0000-0000-000000000000
[ 4.238891] No filesystem could mount root, tried: ext4
[ 4.244812] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,26)
[ 4.254089] CPU1: stopping
I don't know why it happens.
How can I solve this problem?
linux boot android sd-card u-boot
add a comment |
I try to run Android from SD-card. This card is prepared. There are partitions: boot(FAT32)
, rootfs(ext4)
, system(ext4)
, cache(ext4)
and usedata(ext4)
. Boot partitions has files to run u-boot: MLO
, u-boot.bin
and uImage
. To run it I use commands
mmcinit 0
fatload mmc 0 0x80000000 uImage
setenv bootargs 'console=ttyO2,115200n8 mem=456M@0x80000000 mem=512M@0xA0000000 init=/init vram=10M omapfb.vram=0:4M androidboot.console=ttyO2 root=/dev/mmcblk1p2 rw rootwait rootfstype=ext4'
bootm 0x80000000
Than I see how Linux starts. But after few seconds on step of loading rootfs
I see an error message
[ 4.015655] EXT4-fs (mmcblk1p2): couldn't mount RDWR because of unsupported optional features (400)
[ 4.036499] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 4.079986] List of all partitions:
[ 4.083801] b300 31162368 mmcblk0 driver: mmcblk
[ 4.089660] b301 128 mmcblk0p1 f9f21f00-a8d4-5f0e-9746-594869aec34e
[ 4.097839] b302 256 mmcblk0p2 f9f21f01-a8d4-5f0e-9746-594869aec34e
[ 4.106018] b303 128 mmcblk0p3 f9f21f02-a8d4-5f0e-9746-594869aec34e
[ 4.114288] b304 16384 mmcblk0p4 f9f21f03-a8d4-5f0e-9746-594869aec34e
[ 4.122436] b305 16 mmcblk0p5 f9f21f04-a8d4-5f0e-9746-594869aec34e
[ 4.130676] b306 8192 mmcblk0p6 f9f21f05-a8d4-5f0e-9746-594869aec34e
[ 4.138916] b307 8192 mmcblk0p7 f9f21f06-a8d4-5f0e-9746-594869aec34e
[ 4.147094] 103:00000 524288 mmcblk0p8 f9f21f07-a8d4-5f0e-9746-594869aec34e
[ 4.155334] 103:00001 262144 mmcblk0p9 f9f21f08-a8d4-5f0e-9746-594869aec34e
[ 4.163574] 103:00002 30342128 mmcblk0p10 f9f21f09-a8d4-5f0e-9746-594869aec34e
[ 4.171874] b310 2048 mmcblk0boot1 (driver?)
[ 4.177734] b308 2048 mmcblk0boot0 (driver?)
[ 4.183593] b318 15179776 mmcblk1 driver: mmcblk
[ 4.189453] b319 102400 mmcblk1p1 00000000-0000-0000-0000-000000000000
[ 4.197692] b31a 10240 mmcblk1p2 00000000-0000-0000-0000-000000000000
[ 4.205932] b31b 1 mmcblk1p3 00000000-0000-0000-0000-000000000000
[ 4.214141] b31d 262144 mmcblk1p5 00000000-0000-0000-0000-000000000000
[ 4.222351] b31e 13228032 mmcblk1p6 00000000-0000-0000-0000-000000000000
[ 4.230682] b31f 1572864 mmcblk1p7 00000000-0000-0000-0000-000000000000
[ 4.238891] No filesystem could mount root, tried: ext4
[ 4.244812] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,26)
[ 4.254089] CPU1: stopping
I don't know why it happens.
How can I solve this problem?
linux boot android sd-card u-boot
add a comment |
I try to run Android from SD-card. This card is prepared. There are partitions: boot(FAT32)
, rootfs(ext4)
, system(ext4)
, cache(ext4)
and usedata(ext4)
. Boot partitions has files to run u-boot: MLO
, u-boot.bin
and uImage
. To run it I use commands
mmcinit 0
fatload mmc 0 0x80000000 uImage
setenv bootargs 'console=ttyO2,115200n8 mem=456M@0x80000000 mem=512M@0xA0000000 init=/init vram=10M omapfb.vram=0:4M androidboot.console=ttyO2 root=/dev/mmcblk1p2 rw rootwait rootfstype=ext4'
bootm 0x80000000
Than I see how Linux starts. But after few seconds on step of loading rootfs
I see an error message
[ 4.015655] EXT4-fs (mmcblk1p2): couldn't mount RDWR because of unsupported optional features (400)
[ 4.036499] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 4.079986] List of all partitions:
[ 4.083801] b300 31162368 mmcblk0 driver: mmcblk
[ 4.089660] b301 128 mmcblk0p1 f9f21f00-a8d4-5f0e-9746-594869aec34e
[ 4.097839] b302 256 mmcblk0p2 f9f21f01-a8d4-5f0e-9746-594869aec34e
[ 4.106018] b303 128 mmcblk0p3 f9f21f02-a8d4-5f0e-9746-594869aec34e
[ 4.114288] b304 16384 mmcblk0p4 f9f21f03-a8d4-5f0e-9746-594869aec34e
[ 4.122436] b305 16 mmcblk0p5 f9f21f04-a8d4-5f0e-9746-594869aec34e
[ 4.130676] b306 8192 mmcblk0p6 f9f21f05-a8d4-5f0e-9746-594869aec34e
[ 4.138916] b307 8192 mmcblk0p7 f9f21f06-a8d4-5f0e-9746-594869aec34e
[ 4.147094] 103:00000 524288 mmcblk0p8 f9f21f07-a8d4-5f0e-9746-594869aec34e
[ 4.155334] 103:00001 262144 mmcblk0p9 f9f21f08-a8d4-5f0e-9746-594869aec34e
[ 4.163574] 103:00002 30342128 mmcblk0p10 f9f21f09-a8d4-5f0e-9746-594869aec34e
[ 4.171874] b310 2048 mmcblk0boot1 (driver?)
[ 4.177734] b308 2048 mmcblk0boot0 (driver?)
[ 4.183593] b318 15179776 mmcblk1 driver: mmcblk
[ 4.189453] b319 102400 mmcblk1p1 00000000-0000-0000-0000-000000000000
[ 4.197692] b31a 10240 mmcblk1p2 00000000-0000-0000-0000-000000000000
[ 4.205932] b31b 1 mmcblk1p3 00000000-0000-0000-0000-000000000000
[ 4.214141] b31d 262144 mmcblk1p5 00000000-0000-0000-0000-000000000000
[ 4.222351] b31e 13228032 mmcblk1p6 00000000-0000-0000-0000-000000000000
[ 4.230682] b31f 1572864 mmcblk1p7 00000000-0000-0000-0000-000000000000
[ 4.238891] No filesystem could mount root, tried: ext4
[ 4.244812] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,26)
[ 4.254089] CPU1: stopping
I don't know why it happens.
How can I solve this problem?
linux boot android sd-card u-boot
I try to run Android from SD-card. This card is prepared. There are partitions: boot(FAT32)
, rootfs(ext4)
, system(ext4)
, cache(ext4)
and usedata(ext4)
. Boot partitions has files to run u-boot: MLO
, u-boot.bin
and uImage
. To run it I use commands
mmcinit 0
fatload mmc 0 0x80000000 uImage
setenv bootargs 'console=ttyO2,115200n8 mem=456M@0x80000000 mem=512M@0xA0000000 init=/init vram=10M omapfb.vram=0:4M androidboot.console=ttyO2 root=/dev/mmcblk1p2 rw rootwait rootfstype=ext4'
bootm 0x80000000
Than I see how Linux starts. But after few seconds on step of loading rootfs
I see an error message
[ 4.015655] EXT4-fs (mmcblk1p2): couldn't mount RDWR because of unsupported optional features (400)
[ 4.036499] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 4.079986] List of all partitions:
[ 4.083801] b300 31162368 mmcblk0 driver: mmcblk
[ 4.089660] b301 128 mmcblk0p1 f9f21f00-a8d4-5f0e-9746-594869aec34e
[ 4.097839] b302 256 mmcblk0p2 f9f21f01-a8d4-5f0e-9746-594869aec34e
[ 4.106018] b303 128 mmcblk0p3 f9f21f02-a8d4-5f0e-9746-594869aec34e
[ 4.114288] b304 16384 mmcblk0p4 f9f21f03-a8d4-5f0e-9746-594869aec34e
[ 4.122436] b305 16 mmcblk0p5 f9f21f04-a8d4-5f0e-9746-594869aec34e
[ 4.130676] b306 8192 mmcblk0p6 f9f21f05-a8d4-5f0e-9746-594869aec34e
[ 4.138916] b307 8192 mmcblk0p7 f9f21f06-a8d4-5f0e-9746-594869aec34e
[ 4.147094] 103:00000 524288 mmcblk0p8 f9f21f07-a8d4-5f0e-9746-594869aec34e
[ 4.155334] 103:00001 262144 mmcblk0p9 f9f21f08-a8d4-5f0e-9746-594869aec34e
[ 4.163574] 103:00002 30342128 mmcblk0p10 f9f21f09-a8d4-5f0e-9746-594869aec34e
[ 4.171874] b310 2048 mmcblk0boot1 (driver?)
[ 4.177734] b308 2048 mmcblk0boot0 (driver?)
[ 4.183593] b318 15179776 mmcblk1 driver: mmcblk
[ 4.189453] b319 102400 mmcblk1p1 00000000-0000-0000-0000-000000000000
[ 4.197692] b31a 10240 mmcblk1p2 00000000-0000-0000-0000-000000000000
[ 4.205932] b31b 1 mmcblk1p3 00000000-0000-0000-0000-000000000000
[ 4.214141] b31d 262144 mmcblk1p5 00000000-0000-0000-0000-000000000000
[ 4.222351] b31e 13228032 mmcblk1p6 00000000-0000-0000-0000-000000000000
[ 4.230682] b31f 1572864 mmcblk1p7 00000000-0000-0000-0000-000000000000
[ 4.238891] No filesystem could mount root, tried: ext4
[ 4.244812] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,26)
[ 4.254089] CPU1: stopping
I don't know why it happens.
How can I solve this problem?
linux boot android sd-card u-boot
linux boot android sd-card u-boot
asked Jun 2 '16 at 10:16
DropperDropper
8019
8019
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
The error "EXT4-fs : couldn't mount RDWR because of unsupported optional features (400)" is due to different versions between the partition formatter (mkfs.ext4) and the mounter.
You have two options:
a) Either you have to upgrade the mounter program using a newer distro inside the SD-card.
b) or you have to backup the files, reformat the SD-card with the same distro (the same ext4 versions) you are doing the mounting, and after the reformat copy the files again to the SD-card.
In the second option, care must be taken with the original ext4 options the formatter has put, trying to consider the same options at reformat. Note also that a reformat of partitions doesn't need a repartition of the whole device, so the boot MBR would not be altered.
add a comment |
The ext4 feature (400) is the new metadata_csum feature. If this feature is enabled and old tools are used to mount the filesystem they will only be able to mount read-only.
https://ext4.wiki.kernel.org/index.php/Ext4_Metadata_Checksums
To create a ext4 filesystem without this feature:
sudo mke2fs /dev/sdb1 -O ^metadata_csum
Or turn it off on an already created filesystem:
sudo tune2fs -O ^metadata_csum /dev/sdb1
1
git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/tree/lib/ext2fs/… #define EXT4_FEATURE_RO_COMPAT_METADATA_CSUM 0x0400
– jjcf89
Jul 12 '18 at 14:59
add a comment |
Super-great thanks :) Im already has been tired to find solution in f*kin Inet. Its upperas after upgrade Debian from Jessie to Stretch. Solved by switch off option in /etc/mke2fs.conf in section ext4
New contributor
add a comment |
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
});
}
});
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%2funix.stackexchange.com%2fquestions%2f287159%2flinux-couldnt-mount-rdwr-because-of-unsupported-optional-features-400%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
The error "EXT4-fs : couldn't mount RDWR because of unsupported optional features (400)" is due to different versions between the partition formatter (mkfs.ext4) and the mounter.
You have two options:
a) Either you have to upgrade the mounter program using a newer distro inside the SD-card.
b) or you have to backup the files, reformat the SD-card with the same distro (the same ext4 versions) you are doing the mounting, and after the reformat copy the files again to the SD-card.
In the second option, care must be taken with the original ext4 options the formatter has put, trying to consider the same options at reformat. Note also that a reformat of partitions doesn't need a repartition of the whole device, so the boot MBR would not be altered.
add a comment |
The error "EXT4-fs : couldn't mount RDWR because of unsupported optional features (400)" is due to different versions between the partition formatter (mkfs.ext4) and the mounter.
You have two options:
a) Either you have to upgrade the mounter program using a newer distro inside the SD-card.
b) or you have to backup the files, reformat the SD-card with the same distro (the same ext4 versions) you are doing the mounting, and after the reformat copy the files again to the SD-card.
In the second option, care must be taken with the original ext4 options the formatter has put, trying to consider the same options at reformat. Note also that a reformat of partitions doesn't need a repartition of the whole device, so the boot MBR would not be altered.
add a comment |
The error "EXT4-fs : couldn't mount RDWR because of unsupported optional features (400)" is due to different versions between the partition formatter (mkfs.ext4) and the mounter.
You have two options:
a) Either you have to upgrade the mounter program using a newer distro inside the SD-card.
b) or you have to backup the files, reformat the SD-card with the same distro (the same ext4 versions) you are doing the mounting, and after the reformat copy the files again to the SD-card.
In the second option, care must be taken with the original ext4 options the formatter has put, trying to consider the same options at reformat. Note also that a reformat of partitions doesn't need a repartition of the whole device, so the boot MBR would not be altered.
The error "EXT4-fs : couldn't mount RDWR because of unsupported optional features (400)" is due to different versions between the partition formatter (mkfs.ext4) and the mounter.
You have two options:
a) Either you have to upgrade the mounter program using a newer distro inside the SD-card.
b) or you have to backup the files, reformat the SD-card with the same distro (the same ext4 versions) you are doing the mounting, and after the reformat copy the files again to the SD-card.
In the second option, care must be taken with the original ext4 options the formatter has put, trying to consider the same options at reformat. Note also that a reformat of partitions doesn't need a repartition of the whole device, so the boot MBR would not be altered.
edited Apr 14 '17 at 21:39
answered Apr 14 '17 at 21:34
tormestormes
11113
11113
add a comment |
add a comment |
The ext4 feature (400) is the new metadata_csum feature. If this feature is enabled and old tools are used to mount the filesystem they will only be able to mount read-only.
https://ext4.wiki.kernel.org/index.php/Ext4_Metadata_Checksums
To create a ext4 filesystem without this feature:
sudo mke2fs /dev/sdb1 -O ^metadata_csum
Or turn it off on an already created filesystem:
sudo tune2fs -O ^metadata_csum /dev/sdb1
1
git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/tree/lib/ext2fs/… #define EXT4_FEATURE_RO_COMPAT_METADATA_CSUM 0x0400
– jjcf89
Jul 12 '18 at 14:59
add a comment |
The ext4 feature (400) is the new metadata_csum feature. If this feature is enabled and old tools are used to mount the filesystem they will only be able to mount read-only.
https://ext4.wiki.kernel.org/index.php/Ext4_Metadata_Checksums
To create a ext4 filesystem without this feature:
sudo mke2fs /dev/sdb1 -O ^metadata_csum
Or turn it off on an already created filesystem:
sudo tune2fs -O ^metadata_csum /dev/sdb1
1
git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/tree/lib/ext2fs/… #define EXT4_FEATURE_RO_COMPAT_METADATA_CSUM 0x0400
– jjcf89
Jul 12 '18 at 14:59
add a comment |
The ext4 feature (400) is the new metadata_csum feature. If this feature is enabled and old tools are used to mount the filesystem they will only be able to mount read-only.
https://ext4.wiki.kernel.org/index.php/Ext4_Metadata_Checksums
To create a ext4 filesystem without this feature:
sudo mke2fs /dev/sdb1 -O ^metadata_csum
Or turn it off on an already created filesystem:
sudo tune2fs -O ^metadata_csum /dev/sdb1
The ext4 feature (400) is the new metadata_csum feature. If this feature is enabled and old tools are used to mount the filesystem they will only be able to mount read-only.
https://ext4.wiki.kernel.org/index.php/Ext4_Metadata_Checksums
To create a ext4 filesystem without this feature:
sudo mke2fs /dev/sdb1 -O ^metadata_csum
Or turn it off on an already created filesystem:
sudo tune2fs -O ^metadata_csum /dev/sdb1
answered Jul 12 '18 at 14:57
jjcf89jjcf89
1412
1412
1
git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/tree/lib/ext2fs/… #define EXT4_FEATURE_RO_COMPAT_METADATA_CSUM 0x0400
– jjcf89
Jul 12 '18 at 14:59
add a comment |
1
git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/tree/lib/ext2fs/… #define EXT4_FEATURE_RO_COMPAT_METADATA_CSUM 0x0400
– jjcf89
Jul 12 '18 at 14:59
1
1
git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/tree/lib/ext2fs/… #define EXT4_FEATURE_RO_COMPAT_METADATA_CSUM 0x0400
– jjcf89
Jul 12 '18 at 14:59
git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/tree/lib/ext2fs/… #define EXT4_FEATURE_RO_COMPAT_METADATA_CSUM 0x0400
– jjcf89
Jul 12 '18 at 14:59
add a comment |
Super-great thanks :) Im already has been tired to find solution in f*kin Inet. Its upperas after upgrade Debian from Jessie to Stretch. Solved by switch off option in /etc/mke2fs.conf in section ext4
New contributor
add a comment |
Super-great thanks :) Im already has been tired to find solution in f*kin Inet. Its upperas after upgrade Debian from Jessie to Stretch. Solved by switch off option in /etc/mke2fs.conf in section ext4
New contributor
add a comment |
Super-great thanks :) Im already has been tired to find solution in f*kin Inet. Its upperas after upgrade Debian from Jessie to Stretch. Solved by switch off option in /etc/mke2fs.conf in section ext4
New contributor
Super-great thanks :) Im already has been tired to find solution in f*kin Inet. Its upperas after upgrade Debian from Jessie to Stretch. Solved by switch off option in /etc/mke2fs.conf in section ext4
New contributor
New contributor
answered 10 mins ago
Stra TegerStra Teger
1
1
New contributor
New contributor
add a comment |
add a comment |
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.
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%2funix.stackexchange.com%2fquestions%2f287159%2flinux-couldnt-mount-rdwr-because-of-unsupported-optional-features-400%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