Closed rcambrj closed 1 year ago
+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 /mnt/data
and UDR and UDM-SE use /data
.
I can share my UDR if someone is wiling to help!
Can confirm on my UDM SE.
root@UDM-SE:~# info
Model: UniFi Dream Machine SE
Version: 2.5.11.7956
MAC Address: <REDACTED>
IP Address: <REDACTED>
Hostname: UDM-SE
Uptime: 2373436 seconds
Status: Connected (http://localhost:8080/inform)
root@UDM-SE:~# ls /mnt/data/udapi-config/ubios-udapi-server/ubios-udapi-server.state
ls: cannot access '/mnt/data/udapi-config/ubios-udapi-server/ubios-udapi-server.state': No such file or directory
root@UDM-SE:~# ls /data/udapi-config/ubios-udapi-server/ubios-udapi-server.state
/data/udapi-config/ubios-udapi-server/ubios-udapi-server.state
To my knowledge, right now the UDM/P or UXG-Pro use
/mnt/data
and UDR and UDM-SE use/data
.
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: An upcoming version of UDM/UDM-Pro will migrate to UniFi OS 2.x. The process is currently being well-tested internally and will be released shortly, with no specific ETA.
I've noticed on my UDR the udm-boot.service is still searching on boot scripts in /mnt/data/on_boot.d
ExecStart=bash -c 'mkdir -p /mnt/data/on_boot.d && find -L /mnt/data/on_boot.d -mindepth 1 -maxdepth 1 -type f -print0 | sort -z | xargs -0 -r -n 1 -- bash -c \'if test -x "$0"; then echo "%n: running $0"; "$0"; else case "$0" in *.sh) echo "%n: sourcing $0"; . "$0";; *) echo "%n: ignoring $0";; esac; fi\''
I had to change it to /data/on_boot.d to make it work.
My UDM Pro is on 2.x and now uses /data
fyi
root@DreamMachinePro:~# uname -a
Linux DreamMachinePro 4.19.152-ui-alpine #4.19.152 SMP Thu Jan 19 14:13:14 CST 2023 aarch64 GNU/Linux
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.
DATA_DIR="/mnt/data"
case "$(ubnt-device-info firmware || true)" in
1*)
DATA_DIR="/mnt/data"
;;
2*)
DATA_DIR="/data"
;;
3*)
DATA_DIR="/data"
;;
*)
echo "ERROR: No persistent storage found." 1>&2
exit 1
;;
esac
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.state
Does 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.d
tools, so I have no idea whether my/mnt/data
stuff is going to survive a firmware update.To Reproduce
Expected behavior Unclear.
Screenshots N/A
UDM Information
Additional context
cc @opustecnica