Ubuntu

UFS filesystem not automounted

Reported by Lars Noodén on 2008-01-09
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
hal (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: d3lphin

When inserting a CF unit with two UFS (OpenBSD) partitions, the unit gets recognized, but the partitions are not mounted and produce complaints.

The work-around is to mount manually:
  sudo mount -t ufs -o loop,ro /dev/sdc1 /mnt/

This is probably a problem with Konqueror or D3lphin.

 Linux macbook 2.6.24-3-generic #1 SMP Thu Jan 3 23:30:29 UTC 2008 i686 GNU/Linux
 DISTRIB_ID=Ubuntu
 DISTRIB_RELEASE=8.04
 DISTRIB_CODENAME=hardy
 DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

Maia Everett (sikon) wrote :

dolphin/d3lphin has nothing to do with this. I'm reassigning it to kdebase, which contains kdebase-kio-plugins, although it may well be a hal issue.

Changed in kdebase:
importance: Undecided → Low

It's still present in the latest release candidate

 Linux macbook 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008 x86_64 GNU/Linux
 DISTRIB_ID=Ubuntu
 DISTRIB_RELEASE=8.04
 DISTRIB_CODENAME=hardy
 DISTRIB_DESCRIPTION="Ubuntu 8.04"

Error:

"mount: wrong fs type, bad option, bad superblock on /dev/sdb4, missing codepage or helper program, or other error..."

$ sudo mount -t ffs /dev/sdb4 /mnt/
mount: unknown filesystem type 'ffs'

Trying to mount manually does not work:
$ sudo mount -t ufs /dev/sdb4 /mnt/
mount: wrong fs type, bad option, bad superblock on /dev/sdb4,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so

$ sudo dmesg | tail
[ 3102.614638] ufs was compiled with read-only support, can't be mounted as read-write
[ 3156.620572] You didn't specify the type of your ufs filesystem
[ 3156.620577]
[ 3156.620579] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
[ 3156.620582]
[ 3156.620583] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 3157.436978] UFS-fs error (device loop0): ufs_check_page: bad entry in directory #2: rec_len is too small for name_len - offset=0, rec_len=12, name_len=260
[ 3157.436993] UFS-fs error (device loop0): ufs_readdir: bad page in #2
[ 3176.255889] ufs was compiled with read-only support, can't be mounted as read-write
[ 3204.918809] ufs was compiled with read-only support, can't be mounted as read-write

Harald Sitter (apachelogger) wrote :

Got nothing to do with kdebase either. Moving to hal, might very well be a kernel issue though.

Bart de Koning (bratdaking) wrote :

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

Lars Noodén (larsnooden) wrote :

Still present in Karmic Koala Alpha 5 for i386:

...
Sep 14 10:20:52 mini kernel: [ 4848.225039] sdb4: <openbsd: >
Sep 14 10:20:52 mini kernel: [ 4848.227787] sd 5:0:0:0: [sdb] Attached SCSI removable disk
root@mini:~# mount -r -t ufs -o ufstype=ufs2 /dev/sdb4 /mnt/
mount: wrong fs type, bad option, bad superblock on /dev/sdb4,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so

root@mini:~# mount -r -t ufs -o ufstype=ufs /dev/sdb4 /mnt/
mount: wrong fs type, bad option, bad superblock on /dev/sdb4,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so

root@mini:~# mount -r -t ufs -o ufstype=ffs /dev/sdb4 /mnt/
mount: wrong fs type, bad option, bad superblock on /dev/sdb4,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so

...

$ apt-cache policy hal
hal:
  Installed: 0.5.13-1ubuntu2
  Candidate: 0.5.13-1ubuntu2
  Version table:
 *** 0.5.13-1ubuntu2 0
        500 http://fi.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

Lars Noodén (larsnooden) wrote :

Still present in the release version of Karmic Koala:

$ lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10

$ apt-cache policy libufs2
libufs2:
  Installed: 7.2-1
  Candidate: 7.2-1
  Version table:
 *** 7.2-1 0
        500 http://fi.archive.ubuntu.com karmic/universe Packages
        100 /var/lib/dpkg/status

$ apt-cache policy linux-image-2.6.31-16-generic
linux-image-2.6.31-16-generic:
  Installed: 2.6.31-16.52
  Candidate: 2.6.31-16.52
  Version table:
 *** 2.6.31-16.52 0
        500 http://fi.archive.ubuntu.com karmic-updates/main Packages
        500 http://security.ubuntu.com karmic-security/main Packages
        100 /var/lib/dpkg/status

from dmesg:

[42186.821767] sd 10:0:0:0: [sdb] Assuming drive cache: write through
[42186.821774] sd 10:0:0:0: [sdb] Attached SCSI removable disk
[42214.144308] ufs was compiled with read-only support, can't be mounted as read-write
[42227.398989] ufs was compiled with read-only support, can't be mounted as read-write

Still Present in Lucyd Linx

# lsb_release -rd
Description: Ubuntu 10.04 LTS
Release: 10.04

[ 4159.502456] ufs was compiled with read-only support, can't be mounted as read-write
[ 4829.333377] ufs was compiled with read-only support, can't be mounted as read-write

Lars Noodén (larsnooden) wrote :

Still not automounting UFS in Precise Pangolin

$ lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04

[ 649.769014] ufs was compiled with read-only support, can't be mounted as read-write

Thomas Hotz (thotz) wrote :

Confirming this bug because it happens to several people.

Changed in hal (Ubuntu):
status: New → Confirmed
dino99 (9d9) wrote :
Changed in hal (Ubuntu):
status: Confirmed → Invalid
Lars Noodén (larsnooden) wrote :

If hal is in "maintenance mode" then which package does this bug really affect? I can see that the problem is still present in Trusty. There, UFS partitions are still not getting mounted when plugged in.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers