Still present in Intrepid, with Ubuntu (Gnome): $ uname -a Linux Xtal 2.6.27-11-server #1 SMP Thu Jan 29 20:19:41 UTC 2009 i686 GNU/Linux $ mount -V mount from util-linux-ng 2.14 (with libvolume_id and selinux support)
Trying to mount via nautilus a ufs2 partition (FreeBSD) gives the following error messages: Cannot mount volume. Unable to mount the volume. Details: mount: wrong fs type, bad option, bad superblock on /dev/sda9, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so Followed by another message: Unable to mount 245.7 GB Media DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. dmesg | tail gives: [ 263.010367] ppdev0: unregistered pardevice [ 263.542089] ppdev0: registered pardevice [ 263.590167] ppdev0: unregistered pardevice [ 1640.969066] ppdev0: registered pardevice [ 1641.012630] ppdev0: unregistered pardevice [ 1641.260464] ppdev0: registered pardevice [ 1641.302996] ppdev0: unregistered pardevice [ 1641.725921] ppdev0: registered pardevice [ 1641.762763] ppdev0: unregistered pardevice [ 5480.899890] ufs was compiled with read-only support, can't be mounted as read-write It looks like it (hal?) is trying to mount the disk read-write and with the default ufstype (old). Would it be possible to mount ufs2 drives automatically read only, and use type ufs2 instead of the default old? Manually mounting works without a problem: $ sudo mount -r -t ufs -o ufstype=ufs2 /dev/sda9 /mnt/BSD9 $ $ mount ... /dev/sda1 on /mnt/BSD1 type ufs (ro,ufstype=ufs2) /dev/sda5 on /mnt/BSD5 type ufs (ro,ufstype=ufs2) /dev/sda7 on /mnt/BSD7 type ufs (ro,ufstype=ufs2) /dev/sda8 on /mnt/BSD8 type ufs (ro,ufstype=ufs2) /dev/sda9 on /mnt/BSD9 type ufs (ro,ufstype=ufs2) ... Cheers, Bart -- UFS filesystem not automounted https://bugs.launchpad.net/bugs/181452 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs