Ask Your Question
0

Failed to create instance Error: Can't find ext4 filesystem?

asked 2014-11-18 00:53:13 -0500

splucena gravatar image

updated 2014-11-26 05:31:46 -0500

I have followed installation guide from this link http://docs.openstack.org/icehouse/install-guide/install/apt/content/nova-compute.html (http://docs.openstack.org/icehouse/in...)

I have successfully configured 3 nodes controller, compute and network all using ubuntu server 14.04 on virtualbox. In horizon I can see that my instance has been assigned an IP address but will just keep on spawning.

I had this error when creating an instance (compute bash not in any logs) * This is right after I press enter on nova boot from controller node

VFS: Can't find ext4 filesystem

FAT-fs bogus number of reserved sector

unexpected reply

I believed I have exhausted google but found little regarding this error. Could someone please shed light or point me to a direction on how I can troubleshoot this error.

Error logs appeared on the compute bash when I run nova boot from the controller.

I have followed the recommended/default settings when installing base OS.

Here's what I get when running fdisk -l

Disk /dev/sda: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders, total 20971520 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: 0x000e428c

Device Boot      Start         End      Blocks   Id  System

/dev/sda1   *        2048      499711      248832   83  Linux

/dev/sda2          501758    20969471    10233857    5  Extended

/dev/sda5          501760    20969471    10233856   8e  Linux LVM

Disk /dev/mapper/compute1--vg-root: 9219 MB, 9219080192 bytes
255 heads, 63 sectors/track, 1120 cylinders, total 18006016 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: 0x00000000

Disk /dev/mapper/compute1--vg-swap_1: 1258 MB, 1258291200 bytes
255 heads, 63 sectors/track, 152 cylinders, total 2457600 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: 0x00000000

Disk /dev/mapper/compute1--vg-root doesn't contain a valid partition table
Disk /dev/mapper/compute1--vg-swap_1 doesn't contain a valid partition table

Here's for the mount command

/dev/mapper/compute1--vg-root on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
cgroup on /sys ...
(more)
edit retag flag offensive close merge delete

Comments

Hi, I am running Juno with 3 node cluster. Everything worked fine with adding VMs, but now I added new compute node, launching VM on the newer node fails giving error message: [ 709.761962] EXT4-fs (nbd13): VFS: Can't find ext4 filesystem [ 709.762119] EXT4-fs (nbd13): VFS: Can't find ext4 files

sa-shukla gravatar imagesa-shukla ( 2014-12-15 19:03:36 -0500 )edit

I get error for libvirt also, so am confused whether the issue is with disk creation or libvirt unable to configure console monitor.

sa-shukla gravatar imagesa-shukla ( 2014-12-15 19:06:50 -0500 )edit

The VFS error has nothing to do with disk creation. On my part it was misconfiguration of some configuration on my controller and compute node. I've noticed that even with the VFS error I can still launch intances and attach new compute nodes. Check your new compute node configurations.

splucena gravatar imagesplucena ( 2014-12-17 09:11:47 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-11-18 20:59:38 -0500

SamYaple gravatar image

Where are you seeing that error message, which log?

Can you give me some details about the way the base OS was installed in Virtualbox? Partitioning, filesystems, mounts, etc

edit flag offensive delete link more

Comments

@sam, i have updated my question to contain information you were asking.

splucena gravatar imagesplucena ( 2014-11-18 23:00:10 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-11-18 00:37:11 -0500

Seen: 1,768 times

Last updated: Nov 26 '14