[Bug 44157] Re: network drives no longer mounting after update (related to #43962?)
This is a duplicate of https://launchpad.net/distros/ubuntu/+bug/44874 -- network drives no longer mounting after update (related to #43962?) https://launchpad.net/bugs/44157 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 44157] Re: network drives no longer mounting after update (related to #43962?)
*** This bug is a duplicate of bug 44874 *** ** This bug has been marked a duplicate of bug 44874 auto smbfs mount in /etc/fstab causes hald hang at boot -- network drives no longer mounting after update (related to #43962?) https://launchpad.net/bugs/44157 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 44157] Re: network drives no longer mounting after update (related to #43962?)
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. ** Changed in: hal (Ubuntu) Status: Unconfirmed = Needs Info -- network drives no longer mounting after update (related to #43962?) https://launchpad.net/bugs/44157 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 44157] Re: network drives no longer mounting after update (related to #43962?)
** Attachment added: /etc/fstab http://librarian.launchpad.net/2579614/fstab ** Attachment added: /var/log/kern.log http://librarian.launchpad.net/2579616/kern.log -- network drives no longer mounting after update (related to #43962?) https://launchpad.net/bugs/44157 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 44157] Re: network drives no longer mounting after update (related to #43962?)
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. -- network drives no longer mounting after update (related to #43962?) https://launchpad.net/bugs/44157 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 44157] Re: network drives no longer mounting after update (related to #43962?)
** Attachment added: sudo mount -a -v http://librarian.launchpad.net/2579950/mount-a-v -- network drives no longer mounting after update (related to #43962?) https://launchpad.net/bugs/44157 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 44157] Re: network drives no longer mounting after update (related to #43962?)
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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 44157] Re: [Bug 44157] Re: network drives no longer mounting after update (related to #43962?)
[EMAIL PROTECTED]:~$ 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 [EMAIL PROTECTED]:~$ 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 [EMAIL PROTECTED]:~$ On 5/12/06, Simon Law [EMAIL PROTECTED] 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 -- network drives no longer mounting after update (related to #43962?) https://launchpad.net/bugs/44157 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 44157] Re: network drives no longer mounting after update (related to #43962?)
yep, they're there (it was all working fine (and has been for quite some time) untill the hald update the other day) [EMAIL PROTECTED]:~$ 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... [EMAIL PROTECTED]:~$ 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 [EMAIL PROTECTED]:~$ 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.168.3.1/data on /home/akshoslaa/mistress type smbfs (rw) //192.168.3.1/Movies on /home/akshoslaa/Media/Movies type smbfs (rw) //192.168.3.1/Series on /home/akshoslaa/Media/Series type smbfs (rw) //192.168.3.1/wwwroot on /home/akshoslaa/wwwroot type smbfs (rw) [EMAIL PROTECTED]:~$ ls Media/Series/ Copy of Cereni - Holophonic.mp3 Series/ Thumbs.db Recycled/!Sort/ it's odd, it says nothing was mounted, but the drives are coming up just fine. -v is making it ask for the password to the samba shares (it doesn't ask if I just use -a, I just checked) I'm guessing that the typos are preventing it from trying to mount during boot (so commenting the lines out should have the same effect) thereby avoiding whatevers going wrong during boot. Once everythings up and running I can mount them fine, but only if I didn't try during boot. I was getting the same sort of delay as with hald/mount -a when I tried to ls the mount points. (before commenting them out of fstab) -- network drives no longer mounting after update (related to #43962?) https://launchpad.net/bugs/44157 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 44157] Re: network drives no longer mounting after update (related to #43962?)
** Changed in: hal (Ubuntu) Status: Needs Info = Confirmed -- network drives no longer mounting after update (related to #43962?) https://launchpad.net/bugs/44157 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 44157] Re: network drives no longer mounting after update (related to #43962?)
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... -- network drives no longer mounting after update (related to #43962?) https://launchpad.net/bugs/44157 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
