wayner
-
Posts
536 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by wayner
-
-
Pretty sure it goes in \appdata\unifi\data\sites\default
-
So it looks like we are going to have more fun in around 15 months. Unifi just announced that a bunch or products are being EOLed. So it looks like that for controller versions that come after March 2021 you will no longer be able to configure the EOL devices, which include:
UAP-Outdoor
UAP-Outdoor+
UAP-Pro
UAP-IW
UAP (v1+v2)
UAP-LR (v1+v2)
UAP-AC-EDU
UAP-AC-IW-PRO
So we may need to keep a legacy controller version of whatever was the latest as of March 1, 2021.
-
I believe that ubnt/ubnt works for the devices - maybe for the docker as well?
-
I upgraded the container to 5.12.35 and then had to ssh into all of my devices and issue the set-inform command. But everything seems good now. Thanks for your help.
p.s. My WAPs were running 4.0.15.9872 so they appeared to be above the minimum version for 5.12.35. I am in the process of updating them.
-
Last night after I upgraded to the new container, and things didn't go well, I rolled back to the old container with 5.4.60. I then had to do a bunch of futzing around to get the controller to re-adopt the UAPs. In some instances a reboot was enough, but on one or two others I did have to manually issue the set-inform command, and even that didn't work on one of them - I had to restore factory defaults and start over.
-
I saw that so I haven't mentioned on the Unifi forums that I am using unRAID. It looks like I have two options to get upgraded:
1) Jump right in and jump to 5.12.35. Then I may have to ssh into the UAPs and do a manual upgrade and potentially do some other manually stuff to get them running.
2) Install controller 5.6.4 in Windows. Then I will probably have to adopt all of the devices, upgrade them to the latest version. Then install the docker version 5.12.35 and adopt the devices into the docker version.
Any feeling on which is easier? I have at least one of my UAPs with newer firmware so maybe I will do step 1 and ensure that I can get that UAP adopted and then work on the other four.
-
Here is the advice that I received on the Unifi forums:
QuoteYou can first upgrade to 5.6.40 to get all the firmware updated, then you can upgrade to 5.12.35 if you don't have any UAP AC's, UAP AC v2's, UAP AC OD's or PicoM2's.
The problem is that there doesn't seem to be a readily available 5.6.40 version for unRAID. Perhaps I can try 5.7 and see how it goes.
Worst case scenario - can I just manually upgrade the firmware on my UAPs (and USG if required) from an ssh session?
-
Thanks Hoopster. I did see some discussion about moving the network setting from bridge to host, I assume that is what you mean. I wasn't really in a loop you as it hadn't even adopted my devices yet.
-
Upgrading from 5.4.6 to 5.12 didn't go so well. The Controller didn't know about any of my devices, and it seemed stuck on adopting. So I went back to 5.4.6.
Maybe going from 5.4.6 to 5.12 is too much of an upgrade. Anyone know if things would go better if I just went to 5.7 first? And then if things look good I can go to 5.12 later, or try 5.9 as a further interim step.
-
I think the issue that I may be having is that I am using the old version of this docker that predates the ability to use latest, lts, etc. I installed the docker a couple of years ago and I can't remember changing docker versions other than doing regular updates.
If that is the case then do I just stop the old docker, install the new docker, and point it at my old appdata folder?
-
Here is my docker run command:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='unifi' --net='bridge' -e TZ="America/New_York" -e HOST_OS="unRAID" -e 'PUID'='99' -e 'PGID'='100' -p '8080:8080/tcp' -p '8081:8081/tcp' -p '8443:8443/tcp' -p '8843:8843/tcp' -p '8880:8880/tcp' -p '3478:3478/udp' -v '/mnt/user/appdata/unifi':'/config':'rw' 'linuxserver/unifi'
-
How do I find the docker run command? I am trying to do this all via my phone or tablet remotely over VPN right now so it is a bit tricky.
-
9 hours ago, Hoopster said:
5.12.35 is the latest version available in this LSIO UniFi container if you use the :latest tag.
On my Docker page in unRAID it says that I am up to date. The repository that I appear to be using is linuxserver/unifi.
When I go into the Unifi Controller settings that is what I see the version is 5.6.40
Is there any way to force an update? Or a reinstall without losing all of my settings and config?
-
What's the latest version of controller? I have version 5.6.40 of the docker installed and there appears to be no update available for my docker. I just upgraded the firmware on one of my APs and this is causing me to get tons of emails as in [UniFi] Alert: UniFi-55Hill AP Generated Event. This appears to be a known bug and requires a controller upgrade or a AP firmware downgrade. I would prefer to do the upgrade. Is there a new version coming soon?
FYI - it looks like the latest version of Unifi website for all OSes is 5.12.35. There also appears to be a 5.6.42 version. My unRAID OS version is a bit behind at 6.4.1
-
I am confused about the configuration of the download folder. By default it is set to /downloads. But where exactly is that folder on my unRAID server? Is it contained in one of my shares? If I wanted to change to a share that is mounted at /mnt/user/media/videos then can I just enter this into the config settings in the web UI? And does the address that I entered above make sense?
-
I recently updated this docker and now when I try to go to the web UI I get a 404/Not found error - nginx/1.16.1
I am using bridge mode (br0) mode with an IP of 192.168.1.240.
To try to fix it I temporarily tried host mode and tried to change the Host Port 1 to 9980. I have since changed it back but this seems to have screwed up my docker start command.
Here is the docker start command: (notice the 'TCP_PORT_9980'='80' command
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='rutorrent' --net='br0' --ip='192.168.1.240' -e TZ="America/New_York" -e HOST_OS="unRAID" -e 'TCP_PORT_9980'='80' -e 'TCP_PORT_51413'='51413' -e 'UDP_PORT_6881'='6881' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/media/downloads':'/downloads':'rw' -v '/mnt/user/appdata/rutorrent':'/config':'rw' 'linuxserver/rutorrent' 6c87d2509a9bf8c68bfca32fb4d9aac37fa19e6dc3f9053319fdcadae9459615Help!
edit - I "fixed" this by deleting the docker, deleting the appdata folder and reinstalling.
-
OK great - I was just worried that this file may appear to still be on another drive as well and that the corruption issue, if there is one, will persist when this drive is gone.
-
I am clearing out a cache drive as it appears to be failing. I am following this process: https://wiki.unraid.net/Replace_A_Cache_Drive
I started this on Sunday. Mover appears to be having trouble in moving one specific file. Originally my cache drive was 240GB and there was 110GB used and 130GB free. For some reason there is still 140MB used (according to the Main screen in the web UI). The file not moved is /mnt/cache/domains/whs2011/vdisk3.img. Obviously this relates to a WHS2011 VM that I was trying to run in the past. This file is listed as being 1.07TB in size when I view an index of /MNT/USER/DOMAINS/WHS2011 which doesn't make any sense since it is supposed to be on the Cache drive which is only 240GB in size and is almost empty. Is this file corrupt?
(Copy/Paste of index in question)
INDEX OF /MNT/USER/DOMAINS/WHS2011
TYPE NAME SIZE LAST MODIFIED LOCATION
Parent Directory
vdisk1.img 183 GB 2017-02-06 04:47 Disk 4
vdisk2.img 1.07 GB 2017-02-06 03:20 Disk 4
vdisk3.img 1.07 TB 2017-02-05 16:36 Cache
I have tried to rerun Mover a couple of times and it doesn't make any more progress.
Any ideas on what to do? To be honest I don't use this VM as I could never get it working properly. Can I just delete this/these files from an ssh session?
-
16 hours ago, Frank1940 said:
(4) See here:
You can find several more posts by Googling with these terms--- unraid increase docker .img size
I found that before but I don't appear to have an option to change the size. The only setting I have on the Docker Setting page is Enable Docker (Yes/No). Perhaps I have to stop all of the dockers first, or disable the dockers?
-
Thanks Johnnie - that looks perfect. I thought I had a spare 240GB SSD but I don't so I have to wait for a new one to come from Amazon.
-
I am having this same problem of Mover not moving files off of my cache drive.
I have a share called isos and I have set the Use Cache Disk Option to Yes.
I have then gone to the Main page and clicked the "Move Now" button.
My log shows:
Sep 1 23:25:48 Hoylake emhttpd: req (12): cmdStartMover=Move+now&csrf_token=**************** Sep 1 23:25:48 Hoylake emhttpd: shcmd (3322): /usr/local/sbin/mover &> /dev/null &But the file is still there:
INDEX OF /MNT/USER/ISOS .sagetv <DIR> 2018-01-24 04:13 Disk 3 Windows 10 <DIR> 2017-08-28 21:44 Disk 4 chromiumos_image.img 8.75 GB 2017-08-28 12:10 Disk 3 GRMSHSxFREO_EN_DVD.iso 4.31 GB 2013-01-04 19:12 Disk 3 ubuntu-16.04.1-desktop-amd64.iso 1.51 GB 2017-01-07 09:51 Cache
Any tips on what to do to get Mover to start moving files off of my Cache disk? Do I have to stop the array to make this happen?
-
It looks like my Cache disk is failing (see here) so I am going to replace it. I am going from these directions (Replacing or upgrading your Cache drive - for unRAID v6.2 and above), are those the correct instructions or are there newer instructions - note that I am currently running unRAID 6.4.1?
A few questions:
- It looks like the process is to move the files from the Cache drive to the array using Mover, then to disable and remove the cache drive, install a new cache drive and then to use Mover to move the files to the new cache drive. Is there a more direct method where you add a second cache drive, move the files from the first cache drive to the second cache drive, and then to remove the first cache drive?
- Step 3 in these instructions is "Click on Shares and set all shares present on your Cache disk to Use cache disk: Yes. This will cause the Mover to move all shares OFF the Cache drive!" Why do you change the Use cache disk to Yes rather than No? How does changing the setting to Yes to cause the files to move off of the cache drive?
- My cache drive that is failing is a 240GB SSD. It is currently over 50% full. Is there any reason to use a larger cache drive now that larger SSDs are cheaper?
- Is there anything that I should do now that I have a new drive, like change how much space the dockers can use? I occasionally get errors that my docker space is getting full . How do I increase the space that docker uses as I don't see it in Settings-Docker (even under Advanced view - here is what it currently shows):
Label: none uuid: 97f1537f-8546-4942-ba6b-174c665d70f3 Total devices 1 FS bytes used 12.26GiB devid 1 size 20.00GiB used 17.27GiB path /dev/loop2Is there anything else I should do while I am at this?
Thanks for your help!
-
I don't have a solution but I posted about the exact same issue at the exact same time. Keep an eye on my thread and I will keep an eye on yours in case someone only responds to one of the threads.
-
For the last few days I have been getting errors from my unRAID server like the following:
Event: unRAID Cache disk SMART health [1] Subject: Warning [HOYLAKE] - raw read error rate (failing now) is 34213 Description: ST240HM000_Z4N0013X (sdc) Importance: warningBut I ran an extended SMART test where the result is "SMART overall-health self-assessment test result: PASSED"
How can it have Passed with a read error rate that is failing?
Should I replace my cache drive? It is a Segate 240GB SSD. It has been in continuous use since I built this server a little over 2.5 years ago.
Here is the full SMART text file:
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.14.16-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST240HM000 Serial Number: Z4N0013X LU WWN Device Id: 5 000c50 02ff04f93 Firmware Version: C675 User Capacity: 240,057,409,536 bytes [240 GB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: Solid State Device Form Factor: 2.5 inches Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sat Aug 31 16:25:44 2019 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled ATA Security is: Disabled, frozen [SEC2] Wt Cache Reorder: Unavailable === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED See vendor-specific Attribute list for marginal Attributes. General SMART Values: Offline data collection status: (0x02) Offline data collection activity was completed without error. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 558) seconds. Offline data collection capabilities: (0x19) SMART execute Offline immediate. No Auto Offline data collection support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. No Selective Self-test supported. SMART capabilities: (0x0002) Does not save SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 38) minutes. SMART Attributes Data Structure revision number: 0 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate -OSR-- 001 001 006 NOW 35077 5 Reallocated_Sector_Ct PO--CK 100 100 036 - 0 9 Power_On_Hours -O--CK 075 075 000 - 22890 12 Power_Cycle_Count -O--CK 100 100 020 - 97 171 Unknown_Attribute -O--CK 100 100 000 - 0 172 Unknown_Attribute -O--CK 100 100 000 - 0 181 Program_Fail_Cnt_Total -O--CK 100 100 000 - 0 182 Erase_Fail_Count_Total -O--CK 100 100 000 - 0 194 Temperature_Celsius -O---K 036 000 000 - 36 (Min/Max 20/58) 201 Unknown_SSD_Attribute -O--CK 100 100 000 - 0 204 Soft_ECC_Correction -O--CK 091 091 000 - 25571 231 Temperature_Celsius PO--C- 062 062 010 - 39 234 Unknown_Attribute -O--CK 100 100 000 - 525154 241 Total_LBAs_Written -O--CK 100 100 000 - 28220 242 Total_LBAs_Read -O--CK 100 100 000 - 3965 250 Read_Error_Retry_Rate -O--CK 100 100 000 - 35079 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x03 GPL,SL R/O 5 Ext. Comprehensive SMART error log 0x04 GPL,SL R/O 8 Device Statistics log 0x07 GPL,SL R/O 2 Extended self-test log 0x10 GPL R/O 1 SATA NCQ Queued Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa8 GPL VS 1041 Device vendor specific log 0xa8 SL VS 255 Device vendor specific log 0xb7 GPL,SL VS 4 Device vendor specific log SMART Extended Comprehensive Error Log Version: 1 (5 sectors) Device Error Count: 114 (device log contains only the most recent 20 errors) CR = Command Register FEATR = Features Register COUNT = Count (was: Sector Count) Register LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8 LH = LBA High (was: Cylinder High) Register ] LBA LM = LBA Mid (was: Cylinder Low) Register ] Register LL = LBA Low (was: Sector Number) Register ] DV = Device (was: Device/Head) Register DC = Device Control Register ER = Error register ST = Status register Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 114 [13] occurred at disk power-on lifetime: 22406 hours (933 days + 14 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 00 e0 00 Error: ABRT Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b0 00 d2 00 f1 00 00 00 c2 4f 00 00 00 39d+21:51:06.154 SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE ec 00 00 00 00 00 00 00 00 00 00 00 00 39d+21:51:06.154 IDENTIFY DEVICE f5 00 00 00 00 00 00 00 00 00 00 00 00 39d+21:51:06.154 SECURITY FREEZE LOCK ec 00 00 00 00 00 00 00 00 00 00 00 00 39d+21:51:06.154 IDENTIFY DEVICE ef 00 03 00 45 00 00 00 00 00 00 00 00 39d+21:51:06.154 SET FEATURES [Set transfer mode] Error 113 [12] occurred at disk power-on lifetime: 22020 hours (917 days + 12 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 00 e0 00 Error: ABRT Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b0 00 d2 00 f1 00 00 00 c2 4f 00 00 00 23d+20:16:40.944 SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE ec 00 00 00 00 00 00 00 00 00 00 00 00 23d+20:16:40.944 IDENTIFY DEVICE f5 00 00 00 00 00 00 00 00 00 00 00 00 23d+20:16:40.944 SECURITY FREEZE LOCK ec 00 00 00 00 00 00 00 00 00 00 00 00 23d+20:16:40.944 IDENTIFY DEVICE ef 00 03 00 45 00 00 00 00 00 00 00 00 23d+20:16:40.944 SET FEATURES [Set transfer mode] Error 112 [11] occurred at disk power-on lifetime: 21945 hours (914 days + 9 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 00 e0 00 Error: ABRT Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b0 00 d2 00 f1 00 00 00 c2 4f 00 00 00 20d+17:26:27.854 SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE ec 00 00 00 00 00 00 00 00 00 00 00 00 20d+17:26:27.854 IDENTIFY DEVICE f5 00 00 00 00 00 00 00 00 00 00 00 00 20d+17:26:27.854 SECURITY FREEZE LOCK ec 00 00 00 00 00 00 00 00 00 00 00 00 20d+17:26:27.854 IDENTIFY DEVICE ef 00 03 00 45 00 00 00 00 00 00 00 00 20d+17:26:27.854 SET FEATURES [Set transfer mode] Error 111 [10] occurred at disk power-on lifetime: 21868 hours (911 days + 4 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 00 e0 00 Error: ABRT Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b0 00 d2 00 f1 00 00 00 c2 4f 00 00 00 17d+12:15:43.844 SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE ec 00 00 00 00 00 00 00 00 00 00 00 00 17d+12:15:43.844 IDENTIFY DEVICE f5 00 00 00 00 00 00 00 00 00 00 00 00 17d+12:15:43.844 SECURITY FREEZE LOCK ec 00 00 00 00 00 00 00 00 00 00 00 00 17d+12:15:43.844 IDENTIFY DEVICE ef 00 03 00 45 00 00 00 00 00 00 00 00 17d+12:15:43.844 SET FEATURES [Set transfer mode] Error 110 [9] occurred at disk power-on lifetime: 20883 hours (870 days + 3 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 00 e0 00 Error: ABRT Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b0 00 d2 00 f1 00 00 00 c2 4f 00 00 00 26d+03:54:38.180 SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE ec 00 00 00 00 00 00 00 00 00 00 00 00 26d+03:54:38.180 IDENTIFY DEVICE f5 00 00 00 00 00 00 00 00 00 00 00 00 26d+03:54:38.180 SECURITY FREEZE LOCK ec 00 00 00 00 00 00 00 00 00 00 00 00 26d+03:54:38.180 IDENTIFY DEVICE ef 00 03 00 45 00 00 00 00 00 00 00 00 26d+03:54:38.180 SET FEATURES [Set transfer mode] Error 109 [8] occurred at disk power-on lifetime: 20255 hours (843 days + 23 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 00 e0 00 Error: ABRT Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b0 00 d2 00 f1 00 00 00 c2 4f 00 00 00 00:00:00.020 SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE ec 00 00 00 00 00 00 00 00 00 00 00 00 00:00:00.020 IDENTIFY DEVICE f5 00 00 00 00 00 00 00 00 00 00 00 00 00:00:00.010 SECURITY FREEZE LOCK ec 00 00 00 00 00 00 00 00 00 00 00 00 00:00:00.010 IDENTIFY DEVICE ef 00 03 00 45 00 00 00 00 00 00 00 00 00:00:00.010 SET FEATURES [Set transfer mode] Error 108 [7] occurred at disk power-on lifetime: 19759 hours (823 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 00 e0 00 Error: ABRT Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b0 00 d2 00 f1 00 00 00 c2 4f 00 00 00 00:00:00.010 SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE ec 00 00 00 00 00 00 00 00 00 00 00 00 00:00:00.010 IDENTIFY DEVICE f5 00 00 00 00 00 00 00 00 00 00 00 00 00:00:00.010 SECURITY FREEZE LOCK ec 00 00 00 00 00 00 00 00 00 00 00 00 00:00:00.010 IDENTIFY DEVICE ef 00 03 00 45 00 00 00 00 00 00 00 00 00:00:00.010 SET FEATURES [Set transfer mode] Error 107 [6] occurred at disk power-on lifetime: 18993 hours (791 days + 9 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 00 e0 00 Error: ABRT Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b0 00 d2 00 f1 00 00 00 c2 4f 00 00 00 00:00:00.020 SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE ec 00 00 00 00 00 00 00 00 00 00 00 00 00:00:00.010 IDENTIFY DEVICE f5 00 00 00 00 00 00 00 00 00 00 00 00 00:00:00.010 SECURITY FREEZE LOCK ec 00 00 00 00 00 00 00 00 00 00 00 00 00:00:00.010 IDENTIFY DEVICE ef 00 03 00 45 00 00 00 00 00 00 00 00 00:00:00.010 SET FEATURES [Set transfer mode] SMART Extended Self-test Log Version: 1 (2 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 22890 - # 2 Short offline Completed without error 00% 22889 - Selective Self-tests/Logging not supported SCT Commands not supported Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 2) == 0x01 0x008 4 97 --- Lifetime Power-On Resets |||_ C monitored condition met ||__ D supports DSN |___ N normalized value SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x0008 2 0 Device-to-host non-data FIS retries 0x0009 2 0 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 18 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x000d 2 0 Non-CRC errors within host-to-device FIS 0x000f 2 0 R_ERR response for host-to-device data FIS, CRC 0x0010 2 0 R_ERR response for host-to-device data FIS, non-CRC 0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC 0x0013 2 0 R_ERR response for host-to-device non-data FIS, non-CRC
[Plugin] CA Appdata Backup / Restore v2
in Plugin Support
Posted
What is considered the best practice in terms of where to store backups to ensure that you don't lose them. Presumably the backups should be also stored on a drive somewhwere other than your unRAID server in case it totally dies. Do people save their backups somewhere in the cloud? To other PCs on their LAN? External hard drives?