couldn't mount because of unsupported optional features
Linux - Embedded & Single-board computerThis forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
couldn't mount because of unsupported optional features
Hello I am working on Embedded Board which runs on 3.2.0 Linux.
I facing problem while trying to mount SRAM disk
---------------------------------------------
root@CPU7001:~ mke2fs -t ext2 /dev/sram
mke2fs 1.42.4 (12-June-2012)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
1024 inodes, 4096 blocks
204 blocks (4.98) reserved for the super user
First data block=1
Maximum filesystem blocks=4194304
1 block group
8192 blocks per group, 8192 fragments per group
1024 inodes per group
Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
------------------------------------------------------
root@CPU7001:~ e2fsck -y /dev/sram
e2fsck 1.42.4 (12-June-2012)
e2fsck: Filesystem revision too high while trying to open /dev/sram
The filesystem revision is apparently too high for this version of e2fsck.
(Or the filesystem superblock is corrupt)
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
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>
----------------------------------------------------------
root@CPU7001:~ mount -t ext2 /dev/sram /sramdisk/
[ 442.566345] EXT2-fs (sram): error: couldn't mount because of unsupported optional features (2000200)
mount: mounting /dev/sram on /sramdisk/ failed: Invalid argument
----------------------------------------------------------
root@CPU7001:~ e2fsck -b 8193 /dev/sram
e2fsck 1.42.4 (12-June-2012)
e2fsck: Invalid argument while trying to open /dev/sram
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
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>
You could of course use a ramfs which just gets mounted and unmounted
mount -t ramfs ramfs /mnt
the system works it all out for you
I'm on Slackware, so /devs possibly different,
looking through my /dev/directory I have devices ram0 ram1 ---> ram15
but no /dev/sram
mkfs /dev/ram1 8192
8192 is the number of blocks
don't push it to make a particular filesystem type
it will work itself out
as an example
make the file system on /dev/ram1
mount it
see how much space is available
bash-4.2# mkfs /dev/ram1 8192
mke2fs 1.42.8 (20-Jun-2013)
Discarding device blocks: done
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
2048 inodes, 8192 blocks
409 blocks (4.99) reserved for the super user
First data block=1
Maximum filesystem blocks=8388608
1 block group
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
bash-4.2# mount /dev/ram1 /mnt
bash-4.2# df /mnt
Filesystem 1K-blocks Used Available Use Mounted on
/dev/ram1 7931 45 7477 1 /mnt
Hi. Are you trying to format on a hardware drive or file?
When I create a ramdisk file (for example a diskette or booteable diskette), i do:
dd if=/dev/zero of=diskette.file bs=1024 count=1440
mkfs.ext2 diskette.file
then, i can mount like:
mount -loop -t ext2 diskette.file /media/floppy
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.