Hello,
Has anyone else run into this issue?
I have an external Thunderbolt drive connected to a mini server, I moved the server services data to this external drive (it's just a test for the moment)... Configured some services like DNS and DHCP ...
Now when I test with a reboot of the server, the external disk gets renamed (I tried with just a reboot not stopping any services or eject the disk, as well as ejecting the disk and closing down the server app before the reboot) ... The disk gets a number behind its name, which you can see when you look under /Volumes/, so it becomes disk_name_1 instead of just disk_name.
When I remove the original disk name (without the number) which is inaccessible anyway and then rename the new folder to the original name all things are fine (server app works without issues).
Now I also tried this with iSCSI mounted drives (another experiment)... These volumes get renamed as well after a reboot.
Is there a setting I'm missing somewhere, or is this how it works as is?
Has anyone else run into this issue?
I have an external Thunderbolt drive connected to a mini server, I moved the server services data to this external drive (it's just a test for the moment)... Configured some services like DNS and DHCP ...
Now when I test with a reboot of the server, the external disk gets renamed (I tried with just a reboot not stopping any services or eject the disk, as well as ejecting the disk and closing down the server app before the reboot) ... The disk gets a number behind its name, which you can see when you look under /Volumes/, so it becomes disk_name_1 instead of just disk_name.
When I remove the original disk name (without the number) which is inaccessible anyway and then rename the new folder to the original name all things are fine (server app works without issues).
Now I also tried this with iSCSI mounted drives (another experiment)... These volumes get renamed as well after a reboot.
Is there a setting I'm missing somewhere, or is this how it works as is?