mount_server's "Restore previously mounted volumes" funtionality is bogus.

[bipolar]

I have set, via Tracker, the "Disk mounting during boot" option to "Previously mounted disks".

Via the kottan app, I can see that the ~/config/settings/mount_server file contains the correct values for:

• all the boolean settings (only initialMountRestore set to true in my case)
• 2 messages under info, for the two disks I want to be automatically mounted at boot: "Haiku64" (boot volume), and "Data1" partition.

Yet, upon boot, I end up with 3 volumes being mounted:

• Haiku64 (a 64 bits install of beta5)
• Haiku32 (a 32 bits install of beta5)
• Data1

Similar thing when I boot Haiku32, all the three above get auto-mounted, despite having the correct settings in the mount_server file.

[humdinger]

FWIW, it works for me. 64bit beta5.

[diver]

Same issue here. 64bit latest nightly.

[bipolar]

I've double checked, on both VirtualBox, and on bare metal. Same wrong results everywhere for me with beta5+125, and even on an hrev58095 nightly I had lying around.

In case it change things, I have 7 partitions (6 BFS) on disk1, and 5 partitions on disk2 (2 ntfs, 1 ext4, 2 BFS), and disk3 (1 each of ntfs, ext4, BFS).

For VMs, only disk1 and disk2 are attached. When running bare metal all three disk are present. All disks with MBR-style partitions.

On hrev58095, I tried setting only the boot partition (disk3) and "data1" from disk1... upon reboot, 3 partitions were mounted: boot (disk3), and from disk1: "data1" and "temp1". On a following reboot, one more BFS partition was automounted: "temp2" :-/