network drives no longer mounting after update (related to #43962?)

[akshoslaa]

When I booted this morning, I got stuck n the Loading Hardware Abstratction Layer Message for several minutes before it moved on. Upon entering KDE, I'm greeted with an error about process controller failure (I can't remember the exact error, I can reboot to get it again if it's needed).

From here I discover my network drives (smbfs via fstab) aren't mounted. sudo mount -a gives:

Could not resolve mount point /media/wwwroot

(or equivelent for each of my four network drives)

I can't find anything in the logs about it, apart from this in dmesg, which looks suspicious, and seems to be at about the same point at the long pause during boot.

[4294692.335000] lo: Disabled Privacy Extensions
[4294692.335000] IPv6 over IPv4 tunneling driver
[4294698.088000] drivers/usb/input/hid-core.c: usb_submit_urb(ctrl) failed
[4294698.088000] drivers/usb/input/hid-core.c: timeout initializing reports
[4294698.088000]
[4294698.088000] input: Logitech Logitech Dual Action as /class/input/input4
[4294698.088000] input: USB HID v1.10 Joystick [Logitech Logitech Dual Action] on usb-0000:00:1d.0-1.2

(+2 lines either side so you can see timing (I assume you know how to turn those numbers into something useful :P))

Note this dmesg output is likely a completely seperate issue, (given it's talking about usb devices) but it's the only problem I could find in the logs, and it seems to be in the right spot. (My usb devices all seem to be working fine though.)

more people with the issue at http://ubuntuforums.org/showthread.php?t=172945

[Simon Law (sfllaw)]

Hello,

Could you please include copies of /var/log/kern.log and /etc/fstab?
You should probably redact any passwords you have listed in your
fstab file.

You can attach them to this bug using the following link:
https://launchpad.net/distros/ubuntu/+bug/44157/+addattachment

Thanks.

[akshoslaa (akshoslaa)]

my /etc/fstab as requested.

fstab_smb_credentials_1 is just:
username = username%
password = password

(obviously changed for posting) readable only as sudo.

[akshoslaa (akshoslaa)]

As Requested

[Simon Law (sfllaw)]

Hello,

Your /etc/fstab and the error message given by `sudo mount -a`
don't seem to match up.

With this /etc/fstab, could you please run:
$ sudo mount -a -v
and attach the output to this bug?

Ah yes, you may want to remove that extraneous "3" in your fstab
first, or it just won't work.

Thanks.

[akshoslaa (akshoslaa)]

as requested, plus cat /etc/fstab, and mount so you can see it all properly.

unfortunately -v doesn't seem to offer much new about the problem.

The previous difference was my bad, I edited my original report to a more generic mount point than the ones I actually use (whch have been known to confuse people :P)

as a strange quirk though, while running that initially (after removing that '3' (thanks) I found the movies drive was mounting correctly (the one that had the '3' instead of a '#')
it wound mount and unmount just fine, and the only difference I could find was that it had initally been booted with the typo in fstab (obviously it didn't automount at startup, but after I fixed the typo I could mount/umount it at will) After correcting the typo, I rebooted and it no longer mounts.

I'm going to play around with that a bit later (adding typos, rebooting, removings then and trying to mount - stuff like that) I'll let you know if I have any luck.

Also, fiddling around with stuff from #43962 (where thay have the same hald startup problem as I do) gave me this:

sudo /etc/init.d/dbus restart
Password:
 * Stopping Hardware abstraction layer hald [ ok ]
 * Stopping system message bus dbus [ ok ]
 * Starting system message bus dbus [ ok ]
 * Starting Hardware abstraction layer hald run-parts: /etc/dbus-1/event.d/20hal exited with return code 2

[Simon Law (sfllaw)]

Hello,

I think your mount problems may not be the same, but could be
related.

The -v option was supposed to give us some extra verbosity.

What do the following two commands:
$ sudo mount -v -a
$ sudo mount -a
give as their output?

Thanks.

[akshoslaa (akshoslaa)]

akshoslaa@akhshamineth:~$ sudo mount -v -a
Password:
mount: proc already mounted on /proc
mount: /dev/hda1 already mounted on /media/xp
mount: /dev/hda4 already mounted on /media/dapper_old
mount: /dev/hdb1 already mounted on /media/windows_data
mount: /dev/sda1 already mounted on /media/Documents
mount: /dev/sdb1 already mounted on /media/Media
mount: /media/Documents/Desktop already mounted on /home/akshoslaa/Desktop
mount: /media/Documents/Documents already mounted on /home/akshoslaa/Documents
mount: /media/Documents/Games already mounted on /home/akshoslaa/Games
mount: /media/Documents/dev already mounted on /home/akshoslaa/dev
mount: /media/Documents/bin already mounted on /home/akshoslaa/bin
mount: /media/Media already mounted on /home/akshoslaa/Media_Local
/home/akshoslaa/mistress: invalid option -- v
Could not resolve mount point /home/akshoslaa/mistress
/home/akshoslaa/Media/Movies: invalid option -- v
Could not resolve mount point /home/akshoslaa/Media/Movies
/home/akshoslaa/Media/Series: invalid option -- v
Could not resolve mount point /home/akshoslaa/Media/Series
/home/akshoslaa/wwwroot: invalid option -- v
Could not resolve mount point /home/akshoslaa/wwwroot
nothing was mounted
akshoslaa@akhshamineth:~$ sudo mount -a
Could not resolve mount point /home/akshoslaa/mistress
Could not resolve mount point /home/akshoslaa/Media/Movies
Could not resolve mount point /home/akshoslaa/Media/Series
Could not resolve mount point /home/akshoslaa/wwwroot
akshoslaa@akhshamineth:~$

On 5/12/06, Simon Law <email address hidden> wrote:
> Hello,
>
> I think your mount problems may not be the same, but could be
> related.
>
> The -v option was supposed to give us some extra verbosity.
>
> What do the following two commands:
> $ sudo mount -v -a
> $ sudo mount -a
> give as their output?
>
> Thanks.
>
> --
> network drives no longer mounting after update (related to #43962?)
> https://launchpad.net/bugs/44157
>

--
O)-c

[Simon Law (sfllaw)]

One silly question is whether those directories actually exist:
$ cd /home/akshoslaa
$ ls -ld mistress Media/Movies Media/Series wwwroot

If so, what does
$ sudo mount -t smbfs -o dmask=777,fmask=777,uid=0,gid=0,auto,rw,nouser,credentials=/etc/fstab_smb_credentials_1 //192.168.3.1/data /home/akshoslaa/mistress
say?

Thanks.

[akshoslaa (akshoslaa)]

yep, they're there (it was all working fine (and has been for quite some time) untill the hald update the other day)

akshoslaa@akhshamineth:~$ ls -ld mistress Media/Movies Media/Series wwwroot
drwxr-xr-x 1 root root 4096 2006-05-12 11:01 Media/Movies
drwxr-xr-x 1 root root 4096 2006-05-12 11:01 Media/Series
drwxr-xr-x 1 root root 4096 2006-05-12 11:01 mistress
drwxr-xr-x 1 root root 4096 2006-05-12 11:01 wwwroot

I haven't tested that mount command yet, but figured I'd let you know the result of my 'typo testing'

my network drives are currently mounted.

to achieve this, I 'typoed' out each of the appropriate lines from fstab (I used 3's just to be sure) and rebooted. The long delay loading HAL didn't happen, neither did the dialogue telling me that "the process for the system protocol died unexpectedly" error I have been getting upon forst starting KDE. I opened up a terminal and checked that the drives hadn't mounted (which they hadn't), edited fstab to remove the '3's and ran a sudo mount -v -a...

akshoslaa@akhshamineth:~$ sudo mount -v -a
mount: proc already mounted on /proc
mount: /dev/hda1 already mounted on /media/xp
mount: /dev/hda4 already mounted on /media/dapper_old
mount: /dev/hdb1 already mounted on /media/windows_data
mount: /dev/sda1 already mounted on /media/Documents
mount: /dev/sdb1 already mounted on /media/Media
mount: /media/Documents/Desktop already mounted on /home/akshoslaa/Desktop
mount: /media/Documents/Documents already mounted on /home/akshoslaa/Documents
mount: /media/Documents/Games already mounted on /home/akshoslaa/Games
mount: /media/Documents/dev already mounted on /home/akshoslaa/dev
mount: /media/Documents/bin already mounted on /home/akshoslaa/bin
mount: /media/Media already mounted on /home/akshoslaa/Media_Local
/home/akshoslaa/mistress: invalid option -- v
Password:
/home/akshoslaa/Media/Movies: invalid option -- v
Password:
/home/akshoslaa/Media/Series: invalid option -- v
Password:
/home/akshoslaa/wwwroot: invalid option -- v
Password:
nothing was mounted
akshoslaa@akhshamineth:~$ mount
/dev/hda2 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
/sys on /sys type sysfs (rw)
varrun on /var/run type tmpfs (rw)
varlock on /var/lock type tmpfs (rw)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
devshm on /dev/shm type tmpfs (rw)
lrm on /lib/modules/2.6.15-22-386/volatile type tmpfs (rw)
/dev/hda1 on /media/xp type ntfs (rw,nls=utf8,umask=007,gid=46)
/dev/hda4 on /media/dapper_old type ext3 (rw)
/dev/hdb1 on /media/windows_data type vfat (rw,utf8,umask=007,gid=46)
/dev/sda1 on /media/Documents type ext3 (rw)
/dev/sdb1 on /media/Media type ext3 (rw)
/media/Documents/Desktop on /home/akshoslaa/Desktop type none (rw,bind)
/media/Documents/Documents on /home/akshoslaa/Documents type none (rw,bind)
/media/Documents/Games on /home/akshoslaa/Games type none (rw,bind)
/media/Documents/dev on /home/akshoslaa/dev type none (rw,bind)
/media/Documents/bin on /home/akshoslaa/bin type none (rw,bind)
/media/Media on /home/akshoslaa/Media_Local type none (rw,bind)
//192....

[akshoslaa (akshoslaa)]

alrighty, 'unfixing' fstab and rebooting gives back the long wait for hal

the long delay for ls returns, if giving the following errors:

$ ls -ld mistress Media/Movies Media/Series wwwroot
ls: mistress: Input/output error
ls: Media/Movies: Input/output error
ls: Media/Series: Input/output error
ls: wwwroot: Input/output error

(inspite of the fact that they're there as I showed you before)

sudo mount -t smbfs -o dmask=777,fmask=777,uid=0,gid=0,auto,rw,nouser,credentials=/etc/fstab_smb_credentials_1 //192.168.3.1/data /home/akshoslaa/mistress

gives me the familiar delay, followed by the usual "Could not resolve mount point /home/akshoslaa/mistress"

now for the fun bit :P
I left fstab uncommented, and changed the network drives to noauto and rebooted.

No delay loading hal
no errors starting kde
I can ls the mount points (unmounted) without the delay or errors
I can manually mount each of drives with no delays or errors (eg sudo mount mistress) and access their contents normally.

This gives me a convinient enough work around, I can just set a startup script to mount the drives from noauto once kde is loaded. Now we just need to work out whats going wrong so it can be fixed properly :P (I'm still guessing it's a side effect of whatever went wrong with 43962, and once that gets fixed my problem will disappear too...

[WiLLiE (dazwillie)]

This is a duplicate of https://launchpad.net/distros/ubuntu/+bug/44874