When I start up my Ubuntu computer, I get this message that it could not mount all partitions as defined in `/etc/fstab`. I the press [m] (for a terminal instead of s:skip) and run the command `mount -a`. This works fine and mount all entries from fstab successfully. I then press [Ctrl]-[d] to exit the recovery terminal and the startup continues without further problems.
(I only have /etc/home on the /dev/md_d0 but I think it would be difficult to solve this on a headless system.)
As far as I know, the main difference between `mount -a` and `mountall` (used by upstart) is that the latter publishes status output via dbus.
(I also experienced the renaming from `/dev/md0` to `/dev/md_d0` but this is irrelevant for me as I use the UUID to mount the partition in /etc/fstab.)
There has been a post in the German Ubuntu users forum about this problem too: <http:// forum.ubuntuuse rs.de/topic/ home-auf- raid-wird- beim-systemstar t-nicht- gemo/>
When I start up my Ubuntu computer, I get this message that it could not mount all partitions as defined in `/etc/fstab`. I the press [m] (for a terminal instead of s:skip) and run the command `mount -a`. This works fine and mount all entries from fstab successfully. I then press [Ctrl]-[d] to exit the recovery terminal and the startup continues without further problems.
(I only have /etc/home on the /dev/md_d0 but I think it would be difficult to solve this on a headless system.)
As far as I know, the main difference between `mount -a` and `mountall` (used by upstart) is that the latter publishes status output via dbus.
(I also experienced the renaming from `/dev/md0` to `/dev/md_d0` but this is irrelevant for me as I use the UUID to mount the partition in /etc/fstab.)