Ubuntu
mountall package

  1. Bug #432620
  2. Comment #12

Comment 12 for bug 432620

Revision history for this message
Amedee Van Gasse (amedee) wrote :

Confirmed with the following fstab:

# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/mapper/lvmvolume-root during installation
UUID=42ea9aa1-9ec5-45df-8e5f-b02e014906a8 / ext4 relatime,errors=remount-ro 0 1
# /boot was on /dev/sda1 during installation
UUID=6f608f1c-3e37-44b2-9f92-6695453a40ce /boot ext2 relatime 0 2
# /home was on /dev/mapper/lvmvolume-home during installation
UUID=3ca8d92c-c04a-433a-825d-57edc77f014f /home ext4 relatime 0 2
# swap was on /dev/mapper/lvmvolume-swap during installation
UUID=0b92ab6a-7dfe-40b6-b227-833c9f136204 none swap sw 0 0
LABEL=vm /media/vm xfs noatime 0 0
LABEL=backup /media/backup xfs noatime 0 0

/media/vm and /media/backup give a short error at boot (but continues), but when the OS is completely loaded, I can do ls /media/vm and see what's in there, so the filesystems are mounted.
Could it be that mountall is running twice during the boot process, and that it doesn't pick up xfs (or jfs, or any other filesystem that is not in kernel but in a module) the first time, but it does the second time?

It's just my pet theory, I don't know.
The only (minor) nuisance is that the error message prevents usplash from displaying properly.