Samson

Thank you guys. I think i may have to restart from scratch. I do have a case opened with unifi support but i doubt they will disable the MFA requirement temp so i can log in.

Happy New years all. Wondering if you can help me. My Unraid system was down for a month. After i fixed it, the unifi-controller docker (by linuxserv.io) asked me to authenticate. It sent the MFA to a defunct email address. I always thought it was local managed. In the past 5-6 years, i would be asked to authenticate BUT it never ever sent out an MFA code. Now after reading that the linuxerv.io docker is not updated, i have upgraded to the reborn docker and used a backup (that was automated to the appdata directory) to restore. It still sends the MFA code to the defunct email address. Is there any way i can get back to locally managing the docker? or somehow reset my creds so i can get back in. Or is my only option to reset my APs and start from scratch. Thanks in advance for any help.

Hi, Noticed that you have the Unifi AC Pro. Did you update to 5.10? Any Issues? The post at the top of this page complains of adoption issues. Wondering if you have the same.

Hi, Can someone kindly analyse my results. I was only looking for the # of sectors pending re-allocation. But then I noticed some info under changed attributes just now. Anything I should be concerned about. This was a brand new seagate from newegg.ca bought during boxing day. I already put it in an array and dumped some data on it. Didnt have any issues doing that. If the whole .txt file is needed, i can upload. Thanks in advance. Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ========================================================================1.15 Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == invoked as: ./preclear_disk.sh -A -c 2 /dev/sdb Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == ST4000VN000-1H4168 Z302ETV6 Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Disk /dev/sdb has been successfully precleared Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == with a starting sector of 1 Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Ran 2 cycles Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Using :Read block size = 8388608 Bytes Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Last Cycle's Pre Read Time : 8:49:25 (125 MB/s) Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Last Cycle's Zeroing time : 8:05:33 (137 MB/s) Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Last Cycle's Post Read Time : 17:43:19 (62 MB/s) Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Last Cycle's Total Time : 25:49:52 Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Total Elapsed Time 60:29:15 Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Disk Start Temperature: 28C Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Current Disk Temperature: 27C, Jan 10 12:06:22 Tower preclear_disk-diff[10878]: == Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ============================================================================ Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb Jan 10 12:06:22 Tower preclear_disk-diff[10878]: ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Jan 10 12:06:22 Tower preclear_disk-diff[10878]: Raw_Read_Error_Rate = 102 119 6 ok 3878896 Jan 10 12:06:22 Tower preclear_disk-diff[10878]: Spin_Retry_Count = 100 100 97 near_thresh 0 Jan 10 12:06:22 Tower preclear_disk-diff[10878]: End-to-End_Error = 100 100 99 near_thresh 0 Jan 10 12:06:22 Tower preclear_disk-diff[10878]: Airflow_Temperature_Cel = 73 72 45 ok 27 Jan 10 12:06:22 Tower preclear_disk-diff[10878]: Temperature_Celsius = 27 28 0 ok 27 Jan 10 12:06:22 Tower preclear_disk-diff[10878]: No SMART attributes are FAILING_NOW Jan 10 12:06:22 Tower preclear_disk-diff[10878]: Jan 10 12:06:22 Tower preclear_disk-diff[10878]: 0 sectors were pending re-allocation before the start of the preclear. Jan 10 12:06:22 Tower preclear_disk-diff[10878]: 0 sectors were pending re-allocation after pre-read in cycle 1 of 2. Jan 10 12:06:22 Tower preclear_disk-diff[10878]: 0 sectors were pending re-allocation after zero of disk in cycle 1 of 2. Jan 10 12:06:22 Tower preclear_disk-diff[10878]: 0 sectors were pending re-allocation after post-read in cycle 1 of 2. Jan 10 12:06:22 Tower preclear_disk-diff[10878]: 0 sectors were pending re-allocation after zero of disk in cycle 2 of 2. Jan 10 12:06:22 Tower preclear_disk-diff[10878]: 0 sectors are pending re-allocation at the end of the preclear, Jan 10 12:06:22 Tower preclear_disk-diff[10878]: the number of sectors pending re-allocation did not change. Jan 10 12:06:22 Tower preclear_disk-diff[10878]: 0 sectors had been re-allocated before the start of the preclear. Jan 10 12:06:22 Tower preclear_disk-diff[10878]: 0 sectors are re-allocated at the end of the preclear, Jan 10 12:06:22 Tower preclear_disk-diff[10878]: the number of sectors re-allocated did not change.