ovf creation is failing with wrong fs type, bad option, bad superblock on /dev/mapper/loop0p1

171 views
Skip to first unread message

Santosh

unread,
May 24, 2016, 11:48:50 PM5/24/16
to kiwi
Hi Marcus

ovf creation is failing and I can't seem to find the reason. Can you please take a cursory look at the settings to see if something stands out? I have run fsck many times but still see the same failure. I also ran tune2fs -j command in ext3.py thinking dmesg "JBD2: no valid journal superblock found" thinking journaling could be the reason but no luck there.  

ovf profile:
=========

                <type image="vmx" boot="vmxboot/rhel-07.0" filesystem="ext3" format="vmdk" kernelcmdline="selinux=1"

                                        bootloader="grub2" primary="true">

                        <machine memory="4096" guestOS="rhel7" ovftype="vmware">

                                <vmdisk id="0" controller="ide"/>

                                <vmnic driver="e1000" interface="0" mode="bridged"/>

 

                                <vmconfig-entry>numvcpus = "2"</vmconfig-entry>

                                <vmconfig-entry>cpuid.coresPerSocket = "2"</vmconfig-entry>

                        </machine>       

         <size additive="true" unit="G">32</size>

                        <systemdisk name="AppVG">

                                <!--volume name="home" freespace="500M"/-->

                                <volume name="swap" freespace="8192M"/>

                        </systemdisk>



ovf creation failure log:
===============

[ INFO    ]: 16:01:31 | Syncing system to image

[ INFO    ]: 16:01:31 | --> Syncing boot data at extra partition

[ DEBUG   ]: 16:01:31 | EXEC: [mountpoint /tmp/kiwi_mount_manager.ocx2uqb0]

[ DEBUG   ]: 16:01:31 | EXEC: [mount /dev/mapper/loop0p1 /tmp/kiwi_mount_manager.ocx2uqb0]

[ DEBUG   ]: 16:01:31 | EXEC: Failed with stderr: mount: wrong fs type, bad option, bad superblock on /dev/mapper/loop0p1,

       missing codepage or helper program, or other error

 

       In some cases useful info is found in syslog - try

       dmesg | tail or so.

, stdout: (no output on stdout)

[ INFO    ]: 16:01:31 | Cleaning up FileSystemExt3 instance

[ DEBUG   ]: 16:01:31 | EXEC: [mountpoint /tmp/kiwi_mount_manager.ocx2uqb0]

[ DEBUG   ]: 16:01:31 | EXEC: [mountpoint /tmp/kiwi_mount_manager.ocx2uqb0]

[ DEBUG   ]: 16:01:31 | EXEC: [rm -r -f /tmp/kiwi_mount_manager.ocx2uqb0]

[ INFO    ]: 16:01:31 | Cleaning up VolumeManagerLVM instance

[ DEBUG   ]: 16:01:31 | EXEC: [mountpoint /tmp/kiwi_volumes.lo_eg29z/swap]

[ DEBUG   ]: 16:01:31 | EXEC: [mountpoint /tmp/kiwi_volumes.lo_eg29z]

[ DEBUG   ]: 16:01:31 | EXEC: [rm -r -f /tmp/kiwi_volumes.lo_eg29z]

[ DEBUG   ]: 16:01:31 | EXEC: [vgchange -an AppVG]

[ ERROR   ]: 16:01:31 | KiwiCommandError: mount: stderr: mount: wrong fs type, bad option, bad superblock on /dev/mapper/loop0p1,

       missing codepage or helper program, or other error

 

       In some cases useful info is found in syslog - try

       dmesg | tail or so.

, stdout: (no output on stdout)

[ INFO    ]: 16:01:31 | Cleaning up Disk instance

[ DEBUG   ]: 16:01:31 | EXEC: [kpartx -s -d /dev/loop0]

[ INFO    ]: 16:01:31 | Cleaning up LoopDevice instance

[ DEBUG   ]: 16:01:31 | EXEC: [losetup -d /dev/loop0]

[ INFO    ]: 16:01:31 | Cleaning up InstallImageBuilder instance

[ INFO    ]: 16:01:31 | Cleaning up BootImageKiwi instance

[ DEBUG   ]: 16:01:31 | EXEC: [rm -r -f /root/santosh-kiwi8-conversion-new/appliance/target/appliance/output/vmx/ovf/kiwi_boot_root.680a9265]

[ DEBUG   ]: 16:01:31 | EXEC: [rm -r -f /tmp/kiwi_boot_root_copy.ehmnay9r]

:appliance:createOvf FAILED

 


msm-build-opensuse-110:~/santosh-kiwi8-conversion-new # cat /etc/*release*

openSUSE 13.2 (x86_64)

VERSION = 13.2

CODENAME = Harlequin

# /etc/SuSE-release is deprecated and will be removed in the future, use /etc/os-release instead

NAME=openSUSE

VERSION="13.2 (Harlequin)"

VERSION_ID="13.2"

PRETTY_NAME="openSUSE 13.2 (Harlequin) (x86_64)"

ID=opensuse

ANSI_COLOR="0;32"

CPE_NAME="cpe:/o:opensuse:opensuse:13.2"

BUG_REPORT_URL="https://bugs.opensuse.org"

HOME_URL="https://opensuse.org/"

ID_LIKE="suse"



msm-build-opensuse-110:~/santosh-kiwi8-conversion-new/appliance # lsblk

NAME          MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT

fd0             2:0    1    4K  0 disk

sda             8:0    0  120G  0 disk

├─sda1          8:1    0    1G  0 part /boot

└─sda2          8:2    0  119G  0 part

  ├─vg00-swap 254:0    0    8G  0 lvm  [SWAP]

  └─vg00-root 254:1    0  111G  0 lvm  /


dmesg:

======

5180.474546] loop: module loaded

[ 5290.457865] EXT4-fs (dm-2): mounting ext3 file system using the ext4 subsystem

[ 5290.457994] JBD2: no valid journal superblock found

[ 5290.457996] EXT4-fs (dm-2): error loading journal

Santosh

unread,
May 25, 2016, 1:08:07 PM5/25/16
to kiwi
I changed the underlying FileSystem type from ext3 to ext4 and also removed LVM. Now images are getting created fine. Thanks.
Reply all
Reply to author
Forward
0 new messages