LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Ubuntu (http://www.linuxquestions.org/questions/ubuntu-63/)
-   -   symlinks and launchers stopped working (http://www.linuxquestions.org/questions/ubuntu-63/symlinks-and-launchers-stopped-working-4175415403/)

tg3793 07-07-2012 09:19 AM

symlinks and launchers stopped working
 
Just upgraded from Lucid Lynx to Maverick Meerkat and my symlinks and launchers stopped working. So far (it's been just a couple of hours) I 'think' that the only symlinks and launchers effected are the ones that used to refer to my external HD, which is MOST (several hundred) of my symlinks and launchers.

This actually happened within the first third of the upgrade process so there must be a configuration file somewhere, fstab or smb.conf (though I'm pretty sure I'm barking up the wrong tree on the latter one) that was altered or replaced.

I notice in nautilus, that the path of my external drive (at the top) still says "Signature Mini" like it always has. However when I do a "CTRL+L" to copy or edit the path, it will then include "/media/sdb1/" in the path name. It hadn't done that previously so I know there is a clue to what has happened there.

I've done some googling and ubuntuforuming, and I'm looking over https://help.ubuntu.com/community/UsingUUID even as I post this.

Help point me in the right direction if you can think of one; thanks!

jv2112 07-08-2012 07:20 AM

I would recomend start with reviewing your /etc/fstab. It directs how things are mounted. :twocents:

tg3793 07-10-2012 09:55 AM

Ok; so I saw this line in my fstab
Code:

/dev/sdb1                                  /media/sdb1          ntfs    nls=iso8859-1,umask=000                  0  0
So, since I know that my external drive is named SignatureMini I'm commented it out and replaced it with this line.
Code:

/dev/sdb1                                  /media/SignatureMini          ntfs    nls=iso8859-1,umask=000          0  0
I'll reboot in a few minutes and see if that doesn't fix the problem.
If I'm goofing up here, any of you masters out there will likely see the problem before I even finish rebooting :-)

tg3793 07-10-2012 12:03 PM

ok; well 'X' out my last idea. I never got around to it. Instead I came across this old thread on another forum where I had had a problem with the smell of familiarity to it.

So what I did to resolve the issue was to comment out the fstab entry for sdb1 completely, I followed the instructions below and everything was back to normal.


Quote:

Originally Posted by Morbius1 (Post 10544164)
Step 1: If you have the external drive mounted - unmount it.

Step 2: Disconnect the exteranl drive from the machine.

Step 3: Make sure your fstab entry for the external drive has been removed.

Step 4: Run the following command:
Code:

sudo mount -a
Step 5: Connect the external drive to the machine



All times are GMT -5. The time now is 12:36 PM.