New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Has /mnt/data changed to /data? #402
Comments
|
+1 - can also confirm on a vanilla UDM SE following the OS version previous to 2.5.11 there is no /mnt/data, everything is now in /data I had to create a symbolic link for /mnt/data to /data for many of the items I had previously installed on reinstall after flattening and restoring to default to test what the default mounts and filesystem layout was such as peacey's split VPN and others as many of the scripts, systemctl etc hard code to /mnt/data. If I didnt have the symbolic link there were things getting created in /mnt/data but not /data, OS upgrade I lost /mnt/data and so on.... |
|
Maybe that's the reason why I can't make neither PiHole or AdGuard to work on my UDR? |
|
To my knowledge, right now the UDM/P or UXG-Pro use |
|
I can share my UDR if someone is wiling to help! |
|
Can confirm on my UDM SE. |
Maybe the upcoming UniFi OS 2.0 update for UDM Base and UDM Pro will change that in the same sense as UDR and UDM-SE? From the latest EA Firmware (1.12.30, 3 days ago) for UDM Base and UDM Pro: |
|
I've noticed on my UDR the udm-boot.service is still searching on boot scripts in /mnt/data/on_boot.d I had to change it to /data/on_boot.d to make it work. |
|
My UDM Pro is on 2.x and now uses |
|
Yeah it seems like most scripts will need to have this snippet from https://github.com/unifi-utilities/unifios-utilities/blob/803e077f5df440fffe0dd26618214d5452dce1d3/on-boot-script/remote_install.sh at the top always now. |
Describe the bug
In #401 I describe that a file which others appear to expect at
/mnt/data/udapi-config/ubios-udapi-server/ubios-udapi-server.state, but on my UDMSE is located at/data/udapi-config/ubios-udapi-server/ubios-udapi-server.stateDoes this indicate a critical change in how UDMSE is architected? Did it change in a recent update? Is it nothing to be concerned about? I only just installed the
on_boot.dtools, so I have no idea whether my/mnt/datastuff is going to survive a firmware update.To Reproduce
Expected behavior
Unclear.
Screenshots
N/A
UDM Information
Additional context
cc @opustecnica
The text was updated successfully, but these errors were encountered: