Cannot mount existing ext4 partition

ion-fan · 14. November 2015

Hello i've set up the new stoneburner release of OMV on my cubietruck. Now i want to mount my existing ext4 partition. When i do this via console it works flawlessly but in omv i get the following error:

Code

Fehler #6000:
exception 'OMVException' with message 'Failed to mount '82d27d84-a272-4dfa-b62f-e1f73e211c85': mount: wrong fs type, bad option, bad superblock on /dev/sda1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so
' in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:921
Stack trace:
#0 [internal function]: OMVRpcServiceFileSystemMgmt->mount(Array, Array)
#1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#2 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('mount', Array, Array)
#3 /usr/sbin/omv-engined(500): OMVRpc::exec('FileSystemMgmt', 'mount', Array, Array, 1)
#4 {main}

Alles anzeigen

I cannot see anything in the logfiles. I tried tail -f on all known logfiles but never see anything regarding this error.
Why is it not possible to mount this volume?
Greetings
ion-fan

ion-fan · 14. November 2015

Sorry wrong category. Can a moderator move this thread to the "storage" area?

subzero79 · 14. November 2015

Done, can you try and unmount and mount the disk like this

mkdir /mnt/sda1
mount /dev/sda1 /mnt/sda1 -o defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl

If it complains remove the last option, and if it doesnt, remove user_xatrr and acl then try again

ion-fan · 15. November 2015

thanks for the reply. I've followed your instructions but all three possibilities failed. i tried umount /dev/sda1 but it says that sda1 is not mounted so i tried the supplied command. See following code:

Code

root@cubietruck:~# mkdir /mnt/sda1
root@cubietruck:~# mount /dev/sda1 /mnt/sda1 -o defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so


root@cubietruck:~# mount /dev/sda1 /mnt/sda1 -o defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so


root@cubietruck:~# mount /dev/sda1 /mnt/sda1 -o defaults,nofail,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

Alles anzeigen

ion-fan · 18. November 2015

Does anyone have a clue why this is not working?
It must be possible to mount a normal ext4 partition...
Is there some info missing? Do i have to upload other debugging-data?

ryecoaaron · 18. November 2015

Try checking the partition for errors and mounting:
fsck.ext4 -fv /dev/sda1

If that doesn't work, maybe the journal is missing all together. Do the following and mount:
fsck.ext4 -fv /dev/sda1
tune2fs -O extents,uninit_bg,dir_index,has_journal /dev/sda1

ion-fan · 18. November 2015

Sorry that also didn't work:

Code

root@cubietruck:~# fsck.ext4 -fv /dev/sda1
e2fsck 1.42.5 (29-Jul-2012)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information


       45570 inodes used (0.04%, out of 122101760)
         803 non-contiguous files (1.8%)
           4 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 45555/7
    33781661 blocks used (6.92%, out of 488378385)
           0 bad blocks
           7 large files


       38081 regular files
        7480 directories
           0 character device files
           0 block device files
           0 fifos
           3 links
           0 symbolic links (0 fast symbolic links)
           0 sockets
------------
       45564 files
root@cubietruck:~# mount
/dev/root on / type ext4 (rw,noatime,nodiratime,discard,errors=remount-ro,commit=600)
devtmpfs on /dev type devtmpfs (rw,relatime,size=1031936k,nr_inodes=187008,mode=755)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=131072k,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=131072k)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /tmp type tmpfs (rw,relatime)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
root@cubietruck:~# tune2fs -O extents,uninit_bg,dir_index,has_journal /dev/sda1
tune2fs 1.42.5 (29-Jul-2012)

Alles anzeigen

After that and also after the fsck-check the mount didn't work through openmediavault.
Is there maybe a log were more precise infomation is given what fails?

ryecoaaron · 18. November 2015

Did you try to mount from the command line? A temporary test would be:

mkdir -p /media/test
mount -t ext4 /dev/sda1 /media/test

What is the output of:
fdisk -l
blkid

ion-fan · 18. November 2015

Mount from commandline works. I can see all my files in that folder. Here is the output:

Code

root@cubietruck:~#
root@cubietruck:~# mkdir -p /media/test
root@cubietruck:~# mount -t ext4 /dev/sda1 /media/test
root@cubietruck:~#
root@cubietruck:~#
root@cubietruck:~#
root@cubietruck:~# fdisk -l


Disk /dev/mmcblk0: 15.7 GB, 15720251392 bytes
6 heads, 8 sectors/track, 639658 cylinders, total 30703616 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000b2f35


        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1            2048    30703615    15350784   83  Linux


WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1  3907029167  1953514583+  ee  GPT
Partition 1 does not start on physical sector boundary.
root@cubietruck:~# blkid
/dev/mmcblk0p1: UUID="ae328146-08c2-402c-b2de-14b9cd242693" TYPE="ext4"
/dev/sda1: UUID="82d27d84-a272-4dfa-b62f-e1f73e211c85" TYPE="ext4"

Alles anzeigen

ryecoaaron · 18. November 2015

That probably means the entry for the filesystem in config.xml is bad.

ion-fan · 18. November 2015

can i create a new one? I have nothing useful configured in omv yet...

subzero79 · 18. November 2015

I think is a feature disabled in the kernel of the defaults options of ext4. Does dumpe2fs displays all available features?

ion-fan · 18. November 2015

can u post a usable command? i don't know the right command for a short output.
When i do dumpe2fs /dev/sda1 it throws out a large log which i don't want to post here...

subzero79 · 18. November 2015

dumpe2fs -h /dev/sda1 should give you the info.

ion-fan · 19. November 2015

OK the following output of the command:

Code

root@cubietruck:~# dumpe2fs -h /dev/sda1
dumpe2fs 1.42.5 (29-Jul-2012)
Filesystem volume name:   <none>
Last mounted on:          /ext
Filesystem UUID:          82d27d84-a272-4dfa-b62f-e1f73e211c85
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         unsigned_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              122101760
Block count:              488378385
Reserved block count:     0
Free blocks:              454596724
Free inodes:              122056190
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      907
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Flex block group size:    16
Filesystem created:       Sun Jul 20 20:05:47 2014
Last mount time:          Wed Nov 18 22:19:20 2015
Last write time:          Wed Nov 18 22:19:20 2015
Mount count:              1
Maximum mount count:      -1
Last checked:             Wed Nov 18 21:34:47 2015
Check interval:           0 (<none>)
Lifetime writes:          253 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      1931c1be-899f-4bbe-a4a9-2b36d3d9ad7d
Journal backup:           inode blocks
Journal features:         journal_incompat_revoke
Journal size:             128M
Journal length:           32768
Journal sequence:         0x0008bb50
Journal start:            1


root@cubietruck:~#

Alles anzeigen

Can you see anything not normal?

subzero79 · 19. November 2015

Everything looks almost exactly like mine, except i have different this Filesystem flags: signed_directory_hash

You have unsigned, ATM i am not able to give you an answer about if that's the problem or not. I'll have to dive into the ext4 manual.
Don't know if @ryecoaaron knows the answer

subzero79 · 19. November 2015

Can you run fsck.ext4 -pf /dev/sda1

Check if the directory hash changes to signed then try to mount again in the webui.

ryecoaaron · 19. November 2015

Looks right to me. If fsck doesn't fix it, I would move the files off of it, wipe it, and reformat.

ion-fan · 19. November 2015

ok i tried what subzero79 proposed, but it didn't changed the value to signed. I will save my files and do a wipe. Would be good to do the formatting then with omv right?
Wierd that omv has this problem with my partition... but thanks for the help
If you want i can report if it works with a wipe (which i expect it should)

subzero79 · 19. November 2015

Seems like a problem in the platform from little info I've found on google. You can try and wipe, if still doesn't work maybe take the disk to x86 platform and format it there, see if it makes a difference and put it back.

Jetzt mitmachen!