HFS+ USB drives (e.g. for Time Capsule) often mount with "(1)" appended to their names on restart

[m_listed]

This breaks Time Capsule and any computers on LAN that are auto-mounting/mapping the network share, since the name is now unrecognizable.

On RT-AC68U with latest Merlin. Only happens with HFS+ shares such as Time Capsule/Mac-formatted drives, not NTFS ones. Logs:

Feb 14 04:34:08 hotplug[929]: USB /dev/sdc3(hfs) failed to mount at the first try!
Feb 14 04:34:08 usb: USB /dev/sdc3(hfs) failed to mount At the first try!
Feb 14 04:34:08 syslog: USB hfs fs at /dev/sdc3 mounted on /tmp/mnt/Media(1)
Feb 14 04:34:08 usb: USB hfs fs at /dev/sdc3 mounted on /tmp/mnt/Media(1).

Has anyone else had this problem?

 

[L&LD]

Use search. Define the name of the drive to fix the issue.

 

[m_listed]

Use search. Define the name of the drive to fix the issue.

But the name of the drive is defined, as in it has a name (it's not just named sda/sdb/sdc/etc.). Unless there is something else that has to be done.

 

[ColinTaylor]

If it's plugged into a USB3 port try changing it to a USB2 port.

 

[m_listed]

If it's plugged into a USB3 port try changing it to a USB2 port.

It's not, it's plugged into the USB 2.0 port.

I checked the source and I seem to be falling victim to the following check:

int the_same_name = 0;
        while(check_if_file_exist(mountpoint) || check_if_dir_exist(mountpoint)){
            ++the_same_name;
            sprintf(mountpoint, "%s/%s(%d)", POOL_MOUNT_ROOT, the_label, the_same_name);
        }

Was obvious anyway; seems the path to the HFS+ mounts are not getting cleared from the cache upon loss of link.