JFS File System Not mounting in OMV 1.1

BrianP · 26. November 2014

Hello Community,
I've been testing OMV for the last couple weeks with a Raid 6 array and a JFS filesystem.
I just got comfrotable and thought it was perfect, and went to grow the Array which took a little bit of time, but seemed to finish successfully. I then went to try and resize (increase) the jfs filesystem and now get a failed to mount 'uuid' error.

Code

Failed to mount '8be7d4d8-314d-4fd3-988e-667f841c8f7e': mount: wrong fs type, bad option, bad superblock on /dev/md127, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so
Error #6000: exception 'OMVException' with message 'Failed to mount '8be7d4d8-314d-4fd3-988e-667f841c8f7e': mount: wrong fs type, bad option, bad superblock on /dev/md127, 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:887 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}

I've attached some pictures of the WebGuI. The RAID array reports clean, I've tried rebooting the server which does not help

I ssh'ed into the OMV server and tried

Code

/etc/openmediavault# mount -a
mount: wrong fs type, bad option, bad superblock on /dev/md127,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so


openmediavault# fsck.jfs /dev/md127
fsck.jfs version 1.1.15, 04-Mar-2011
processing started: 11/26/2014 10:48:33
Using default parameter: -p
The current device is:  /dev/md127
Block size in bytes:  4096
Filesystem size in blocks:  6837052544
**Phase 0 - Replay Journal Log
logredo failed (rc=-268).  fsck continuing.
**Phase 1 - Check Blocks, Files/Directories, and  Directory Entries
Errors detected in the Primary File/Directory Allocation Table.
Errors detected in the Secondary File/Directory Allocation Table.
CANNOT CONTINUE.

Alles anzeigen

I'm not sure what to try next or what other logs would be helpful, any help is appreciated.

ryecoaaron · 26. November 2014

What did you try to resize it with? jfs is mounting fine in my vm. So, you damaged the filesystem somehow. I would boot using systemrescuecd and do the fsck from there.

BrianP · 27. November 2014

I tried resizing it in the OMV webGUI. I waited till the RAID reshaping had completed then went to File Systems and clicked resize.
I booted a SystemRescue CD as you suggested and tried the fsck command and I get the same error as in OpenMediaVault

Code

root@sysresccd /root % fsck
fsck from util-linux 2.24.1


root@sysresccd /root % fsck.jfs /dev/md127
fsck.jfs version 1.1.15, 04-Mar-2011
processing started: 11/27/2014 18:25:52
Using default parameter: -p
The current device is:  /dev/md127
Block size in bytes:  4096
Filesystem size in blocks:  6837052544
**Phase 0 - Replay Journal Log
logredo failed (rc=-268).  fsck continuing.
**Phase 1 - Check Blocks, Files/Directories, and  Directory Entries
Errors detected in the Primary File/Directory Allocation Table.
Errors detected in the Secondary File/Directory Allocation Table.
CANNOT CONTINUE.

Alles anzeigen

Do you have any other suggestions?

ryecoaaron · 27. November 2014

See if gparted on systemrescuecd can fix it.

subzero79 · 27. November 2014

All I can see if the same version for jfs fsck, which indicates that maybe jfs is not very well maintained. I've found only this thread which doesn't give much hope from

https://www.mail-archive.com/jfs-<woltlab-metacode-marker data-name="email" data-uuid="f9d1f93f-3137-482a-8b99-901b7a5b15e8" data-source="W2VtYWlsXQ==" data-attributes="WyJkaXNjdXNzaW9uQGxpc3RzLnNvdXJjZWZvcmdlLm5ldCJd" data-use-text="0" /><woltlab-metacode-marker data-uuid="f9d1f93f-3137-482a-8b99-901b7a5b15e8" data-source="Wy9lbWFpbF0=" />/msg01634.html

JFS File System Not mounting in OMV 1.1

Jetzt mitmachen!

Tags