symlink persist follow-up

Keith keithw at caramail.com
Sat Sep 23 18:13:26 UTC 2023


On 9/23/23 1:24 AM, Grizzly via ubuntu-users wrote:
> Friday, September 22, 2023  at 17:45, Keith wrote:
> Re: symlink persist follow-up (at least in part)
> 
>> On 9/22/23 9:14 AM, Grizzly via ubuntu-users wrote:
>> [snip]
>   
>>> the 22.04 drive is set to auto mount at system start & show on launcher
> 
>> I don't believe the 22.04 partition is being automounted. The dock
>> (launcher) is configured to show user-visible volumes including
>> non-mounted ones. When you click on the 22.04 drive icon on the dock,
>> the partition is mounted and suddenly the symlink isn't broken and you
>> can browse the images in the 22.04 Pictures directory.
>   
>>> is there a step I missed or a way to get that drive "seen" at boot so the link
>>> will work
> 
>> I saw in a previous post you stated that you have 3 OS's on the
>> following partitions:
> 
>> 22.04=sda1
> 
> Lunar
> Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
> /dev/sda1     2048      4095      2048     1M Linux filesystem
> /dev/sda2     4096   1054719   1050624   513M EFI System
> /dev/sda3  1054720 976771071 975716352 465.3G Linux filesystem
> 
>> Win7=sda2
> 
> Win7
> Disk /dev/sdb: 335.35 GiB, 360080695296 bytes, 703282608 sectors
> /dev/sdb1  *     2048 703279103 703277056 335.3G  7 HPFS/NTFS/exFAT
> 
>> 23.10=sda3
> 
> Mantic
> Disk /dev/sdc: 465.76 GiB, 500107862016 bytes, 976773168 sectors
> /dev/sdc1     2048      4095      2048     1M BIOS boot
> /dev/sdc2     4096   1054719   1050624   513M EFI System
> /dev/sdc3  1054720 976771071 975716352 465.3G Linux filesystem

Did you leave off listing any swap partitions from the Ubuntu disks or 
is it on a separate disk? Or are you using swapfiles, or zram for swap 
space? Not that its germane to this issue, but its relevant to questions 
about fstab.

> 
>> Is this still correct?
> 
> If that was written it was a typo, each OS is on it's own drive (see above for
> detail) sdx changes, sometimes the Win7 disk is just not there (usually after a
> few reboots)

Well, I got the information from this post

https://lists.ubuntu.com/archives/ubuntu-users/2023-September/311184.html

   "It is on a different drive, 22.04=sda1, Win7=sda2, 23.10=sda3

   >and just mount it (when you boot 'something else'?)  That's how it's
   >typically done, instead of using links.

   sda1, sda2 & sda3 all mount at boot, grub is on sda1, as is the dirs I
   want to link (or anything that lets me have just one Pictures dir)"

That's a little more than just a typo  :/

> 
>> If so, then boot into 23.10 and run the following
>> in a terminal:
> 
>> $ udisksctl info -b /dev/sda1 |egrep Hint"(Auto|System)"
>> HintAuto:                   false
>> HintSystem:                 true
> 
>> Did you get the the output above?  If not, post what you got.
> 
> Assuming the cmdline was based on the (maybe) typo I ran it for each drive
> 
> kenya at Cludia:~$ udisksctl info -b /dev/sda|egrep Hint"(Auto|System)"
>      HintAuto:                   false
>      HintSystem:                 true
> kenya at Cludia:~$ udisksctl info -b /dev/sdb|egrep Hint"(Auto|System)"
>      HintAuto:                   false
>      HintSystem:                 true
> kenya at Cludia:~$ udisksctl info -b /dev/sdc|egrep Hint"(Auto|System)"
>      HintAuto:                   true
>      HintSystem:                 false

The /dev/sdc is puzzling. If you're booting off of it into 23.10, it 
should be regarded as a system volume and the HintAuto property set to 
false. Were you running 23.10 when you issued the udisksctl command? 
It's not a removable drive, is it?

> kenya at Cludia:~$
> 
>> If you did get the above output, then create a udev rules file called
>> 10-automount-sda1.rules (for example) and place it in /etc/udev/rules.d/
>> . In the file put this following line:
> 
>> KERNEL=="sda1", ENV{UDISKS_AUTO}="1"

Well, if the disk information you provided from above is now correct, 
sda1 in the file should be changed to sda3 since that is where the / 
filesystem of 22.04 lives. However, as noted below if you are going to 
modify 23.10's /etc/fstab to mount /dev/sda3 (22.04), then you don't 
need to create the above udev rule.

> 
>> NOTE: *This modification is only applicable for 23.10. Do not make this
>> change while booted into 22.04.*
> 
>> Reboot (into 23.10) and upon login to gnome, the 22.04 partition should
>> be automounted without needing to click the 22.04 drive icon on the dock.
> 
> Unity login
> 
>> I use this method to automount an exfat partition that's on my main
>> system drive along with 22.04.3 Ubuntu and Win10 to share data between
>> the OS's.
> 
>> Volumes with the HintSystem=true will by default have HintAuto=false and
>> thus not automountable by gnome (udisks) unless you override the
>> HintAuto property either via /etc/fstab, or some automounter daemon, or
>> via a udev rule like the one above.
> 
> what "should" fstab for that drive look like? I did use disks to set it
> automount but ...

Just post both /etc/fstab's from 22.04(?) and 23.10 and the list can 
take a look at them.

  BTW, Jammy Jellyfish is 22.04. Lunar Lobster is 23.04. check 
/etc/issue or /etc/os-release, or "lsb_release -a" to find out what 
version you're running when booted into the older Ubuntu release. (the 
one on /dev/sda3).

> 
> I'm running short of time this morning will be back in 3(ish) hours,
> 
> Many thanks
> 
> Grizz
> 

-- 
Keith




More information about the ubuntu-users mailing list