[SOLVED] Link to folder - broken till I use the link
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I created a link to a folder and saved it to the desktop
When I boot up it's shown as a broken link, but after I access the folder by navigating to it with file mangler and access it the link is repaired, how can I make the link good immediately after booting up my machine?
I'm just guessing, your device probably is not mounted until you access it, then some automount mechanism kicks in and mounts it. Running some command on it like ls will probably trigger automount.
More likely the disk is mounted automatically regardless of access, it just happens later than desktop is painted. Is it a magnetic disk? It may take some time to spin up and that may explain a delay. Check syslog to see what is actually happening.
More likely the disk is mounted automatically regardless of access, it just happens later than desktop is painted. Is it a magnetic disk? It may take some time to spin up and that may explain a delay. Check syslog to see what is actually happening.
Is the link you have on your user Desktop pointing to a location on the same partition and on the same physical device? If not, it is not mounted or available until you access it from either a terminal or file manager. If it is on another partition (other than root or home) or on another device, you would need to put an entry in fstab to have it mounted on boot. If it is on a secondary drive that is not attached permanently, this can create problems, at least slowing down the boot process.
Might be entered as a "usermount" device in /etc/fstab.
It is also possible the system is just being really slow at mounting (I've caught systemd that way a time or two with a "nofail" mount taking longer than usual).
Is the link you have on your user Desktop pointing to a location on the same partition and on the same physical device? If not, it is not mounted or available until you access it from either a terminal or file manager. If it is on another partition (other than root or home) or on another device, you would need to put an entry in fstab to have it mounted on boot. If it is on a secondary drive that is not attached permanently, this can create problems, at least slowing down the boot process.
The link is on my desktop so the links are pointiong to a different physical drive, here's an ls of Desktop
The folders are on /dev/sb5
Home folder is on /dev/sda5
And this is fstab
Code:
jonke@charlie:~$ more /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda5 during installation
UUID=92c6eff1-78fc-4faa-8389-c88454e80d11 / ext4 noatime,errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=EB15-5510 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
jonke@charlie:~$
and add whatever other options needed so it is mounted at boot time and accessible by you. I would recommend however that you select another location to mount it since /media is normally used for auto mounting and relocating it to somewhere under $HOME would be easier for permanent access.
and add whatever other options needed so it is mounted at boot time and accessible by you. I would recommend however that you select another location to mount it since /media is normally used for auto mounting and relocating it to somewhere under $HOME would be easier for permanent access.
I wondered about that, I never specified this specifically when I rebuilt my machine.
What I did was this.
I had Mint running off this drive originally. A added an SSD and just built a new version of Mint on that drive. I never specified anything to do with the original drive which is the one in question. Why it was hung off the /media folder structure is mystery to me.
Last edited by GPGAgent; 02-08-2021 at 09:17 AM.
Reason: typo's
Probably because mint saw it was data and decided to make it available there when needed.It did not mount it in fstab because you did not specify a mount point when you did the install on the other disk.
According to your fstab you do not even have /home on a separate partition. It appears to be part of the / file system.
Probably because mint saw it was data and decided to make it available there when needed.It did not mount it in fstab because you did not specify a mount point when you did the install on the other disk.
According to your fstab you do not even have /home on a separate partition. It appears to be part of the / file system.
That's correct, confuses me, but it's exactly as built by the install process
Whey it was hung of the /media folder structure is mystery to me.
I'm not sure if I understand by the above, but that is the standard location for the various Ubuntu distributions such as Mint. External drives are generally accesible under /media/username.
If you don't have this drive permanently attached, there would be not point in putting an entry in fstab.
I'm not sure if I understand by the above, but that is the standard location for the various Ubuntu distributions such as Mint. External drives are generally accesible under /media/username.
If you don't have this drive permanently attached, there would be not point in putting an entry in fstab.
First let me apologize on my keyboard's behalf for all the typo's - my keyboard at work is equally bad at spelling!
The drive's are all permanently mounted and are installed onto the motherboard bus.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.