I have a Micro instance running Ubuntu 10.04 x86 (AMI ami-3e02f257). It has the OS volume attached at /dev/sda1 and a second volume attached at /dev/sdf (reported as /dev/sda1=vol-eaa0e982:attached:2011-03-08T17:17:42.000Z:false, /dev/sdf=vol-44a3ea2c:attached:2011-03-08T17:17:42.000Z:false
).
fstab looks like:
# /etc/fstab: static file system information.
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
LABEL=uec-rootfs / ext3 defaults 0 0
/dev/sda2 /mnt auto defaults,nobootwait,comment=cloudconfig 0 0
/dev/sdf /mnt/osm auto defaults,nobootwait,comment=osmdata 0 0
When I reboot, /mnt/osm does not come online. If I run sudo mount /dev/sdf /mnt/osm
the volume comes online immediately. This was working on a Small instance. When I removed nobootwait
it bricked the instance. Any suggestions? The filesystem needs to come online so that the Postgres cluster running on it can start.
/etc/rc2.d
that callsmount -a
. Is this micro instance not configured to mount the filesystems on boot by default?dmesg
and look toward the end of the output for any errors that might be occurring relating to the mounting of the volume at boot.