07-24-2018 01:54 AM
Hi, I have an issue that’s not too pressing but is annoying with my UAS-XG.
Ive upgraded the HDDs in the server to 2 12TB drives and done all the raid configuration which all works fine.
When logging into the UAS GUI I keep getting the error ‘an error occurred while fetching data, please see the browser console for additional details.’
Upon looking at the console I’ve got the error ‘DEVICE_STATS_FETCH_FAILED TypeError: Cannot read property ‘toFixed’ of undefined’
If if anyone can shed some light on the issue and is it fixable?
07-24-2018 03:10 AM
We also replaced the stock disks with two WD Gold 12TB, but then we set the unit up from scratch with the ISO and the IPMI interface.
Afterwards we inported the old controller settings.. All went wel.. since then we started to use the disks for Unifi Video. Here also no problems.
07-24-2018 09:12 AM
thanks for your info.
my system has just started running, however I’ve been told by a ubnt employee that the system automatically puts the disks in raid 1, which we need the full 24tb space we put in the system.
as I say, the system is performing as it should apart from the error that’s flagging up.
07-26-2018 01:07 PM
07-26-2018 01:28 PM
Im not sure what the default name was but the mount point that i have to use in UV is /mnt/md0.
As I say, i did as the instructions said, remove original disks and put custom ones in, i did this before even booting the machine for the first time.
Once booted the system didnt see the array, or tell me where it was. i had to do some googling & contact UBNT live chat without a working response.
i have attached an image of the dashboard and the chrome console.
07-30-2018 09:16 AM
07-30-2018 11:05 AM
07-30-2018 11:12 AM
ubnt@BM-CCTV-UAS-24TB:~$ sudo mdadm —detail /dev/md0 [sudo] password for ubnt: mdadm: An option must be given to set the mode before a second device (/dev/md0) is listedThis is the output.
07-30-2018 11:15 AM
07-30-2018 11:19 AM
My apolagies, i did do dash dash, must have mistyped the output below.
ubnt@BM-CCTV-UAS-24TB:~$ sudo mdadm --detail /dev/md0sudo mdadm --detail /dev/md0 mdadm: cannot open /dev/md0sudo: No such file or directory mdadm: cannot open mdadm: No such file or directory /dev/md0: Version : 1.2 Creation Time : Wed Jul 18 17:28:44 2018 Raid Level : raid0 Array Size : 23437508608 (22351.75 GiB 24000.01 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Update Time : Wed Jul 18 17:28:44 2018 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Chunk Size : 512K Name : BM-CCTV-UAS-24TB:0 (local to host BM-CCTV-UAS-24TB) UUID : 93da6827:fa0a1d82:1c3278dd:1a1d1933 Events : 0 Number Major Minor RaidDevice State 0 8 16 0 active sync /dev/sdb 1 8 32 1 active sync /dev/sdc ubnt@BM-CCTV-UAS-24TB:~$
11-27-2018 06:49 PM
12-19-2018 08:23 PM
Sorry @jstngreen24, no fix or response from UBNT or originally poster. I have been traveling lately and will be escalation with UBNT now that I'm back. I'll update this post with the resolution. Are you experiencing the same issue?
01-23-2019 07:40 AM - edited 01-23-2019 07:44 AM
I get this too...
ubnt@ubnt:/dev$ sudo mdadm --detail /dev/md127 /dev/md127: Version : 1.2 Creation Time : Tue Apr 3 16:59:21 2018 Raid Level : raid1 Array Size : 1953382400 (1862.89 GiB 2000.26 GB) Used Dev Size : 1953382400 (1862.89 GiB 2000.26 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Tue Apr 3 17:27:02 2018 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Name : ubnt:0 (local to host ubnt) UUID : 2466aaeb:8ed2803a:1945040d:060c4022 Events : 6 Number Major Minor RaidDevice State 0 8 33 0 active sync /dev/sdc1 1 8 17 1 active sync /dev/sdb1
01-24-2019 02:31 PM
I still had this error, I was asked to see if moving the mount point to the factory one helped but I didn’t find a way of moving the point without risking the data.
Recently the onboard SSD filled right up to the point the system stopped recording, upon stopping and trying to start UV again on the system the dB got corrupted and failed to start.
Im not sure if this is something that may affect others, or if the rising disk space was caused by log files filling up? The dB was 70ish GB.
I factory reset the unit unit using the image on ubnt website and I’m running in raid 1 at the moment until we get chance to change back to raid 0.