Energen

Members
  • Posts

    514
  • Joined

  • Last visited

  • Days Won

    1

Energen last won the day on July 19 2020

Energen had the most liked content!

Recent Profile Visitors

4851 profile views

Energen's Achievements

Enthusiast

Enthusiast (6/14)

88

Reputation

  1. You need to move the downloaded files to a new location before deleting them from the seedbox. Think of the settings -- receive only --- you delete a file from the seedbox and that change is received also. You should think of Syncthing as an intermediate handler and not as a final destination. Download to a temporary location and then move the files out to their permanent residence. This can be handled by Sonarr/Radarr, not sure about Plex.
  2. Apologies for the late response. My setup is actually reverse to yours. I have Unraid as the host for the UPS, i.e. the UPS is connected by USB to Unraid. In the grand scheme of things my Unraid server is the more important piece of equipment to handle in a power outage. Then on my Windows machine I have apcusbd running as the slave, and it gets it's power outage information from Unraid. I imagine though that your setup should be able to be accomplished, you would just have to figure out which combination of settings on Unraid works. In the UPS settings of Unraid you may have to play with the UPS cable and/or UPS type options to figure out how to connect to the Windows apcusbd. It seems that it's probably easier to do it my way though.
  3. Unraid keeps giving me a red warning that Disk 6 has read errors ---- 4, to be precise. Jul 5 01:38:32 UNRAID kernel: md: disk6 read error, sector=1952415512 Jul 5 01:38:32 UNRAID kernel: md: disk6 read error, sector=1952415520 Jul 5 01:38:32 UNRAID kernel: md: disk6 read error, sector=1952415528 Jul 5 01:38:32 UNRAID kernel: md: disk6 read error, sector=1952415536 Regularly scheduled parity checks end ok, no issues there. No other known issues with data on the drive and all SMART tests succeed. Is this warning to be believed? Going back to see other read error threads there's been a lot of talk of the multi zone error rates and things of that nature when suggesting to replace disks, well here's Disk 6's stats: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 270 3 Spin_Up_Time POS--K 187 184 021 - 5650 4 Start_Stop_Count -O--CK 100 100 000 - 59 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 7 Seek_Error_Rate -OSR-K 100 253 000 - 0 9 Power_On_Hours -O--CK 053 053 000 - 34890 10 Spin_Retry_Count -O--CK 100 253 000 - 0 11 Calibration_Retry_Count -O--CK 100 253 000 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 56 192 Power-Off_Retract_Count -O--CK 200 200 000 - 36 193 Load_Cycle_Count -O--CK 196 196 000 - 14032 194 Temperature_Celsius -O---K 122 103 000 - 28 196 Reallocated_Event_Count -O--CK 200 200 000 - 0 197 Current_Pending_Sector -O--CK 200 200 000 - 0 198 Offline_Uncorrectable ----CK 100 253 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 47 In comparison here is Disk 7's stats which would appear to be a more likely candidate for replacement, yet prompt no issues. ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 12655 3 Spin_Up_Time POS--K 198 182 021 - 7083 4 Start_Stop_Count -O--CK 094 094 000 - 6057 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 7 Seek_Error_Rate -OSR-K 199 199 000 - 71 9 Power_On_Hours -O--CK 046 046 000 - 39522 10 Spin_Retry_Count -O--CK 100 100 000 - 0 11 Calibration_Retry_Count -O--CK 100 100 000 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 116 192 Power-Off_Retract_Count -O--CK 200 200 000 - 56 193 Load_Cycle_Count -O--CK 165 165 000 - 105243 194 Temperature_Celsius -O---K 122 107 000 - 30 196 Reallocated_Event_Count -O--CK 200 200 000 - 0 197 Current_Pending_Sector -O--CK 200 200 000 - 0 198 Offline_Uncorrectable ----CK 200 200 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 191 191 000 - 3398 Should disk6 in fact be replaced or is 4 sectors not enough of an issue to worry about and Unraid is just being super sensitive? I'm certainly sure that over the years I've ran drives for a multitude of years with read errors and such and never knew about them and the computer just blissfully kept on chugging along with no problem. Thanks for the info.
  4. 1) Are you sure it's actually encrypted? 2) Do you have other drives in the array that are encrypted with the same passphrase/file? --- If yes, Unraid [most likely] automatically tries to mount the drive with the existing passphrase. You would need to start your array and then remove the passphrase/keyfile before mounting the UD.
  5. Honestly your best bet would be to use google photos for automatic backup, or amazon photos if you have prime. From either of those you could then download them for storage. Not quite an automatic process but without using nextcloud you're somewhat limited to the availability of mobile apps.
  6. How about from the Go file? Is it a passphrase? You could try echo -n "key" > /root/keyfile and see if that works.
  7. How is the keyfile getting to /root? There may be an issue there. I had endless problems using encryption and keyfiles. Decided it wasn't worth the hassle.
  8. Easiest way would be to just name the new docker the same as the old docker... so that the appdata folder is named the same. Nothing else would change in that case. Or you could use a script such as the one linked in my signature to back up essential plex data which you could then use to restore in the new appdata folder..
  9. Once again, this thread is originally 6 years old. HTTPS is already implemented. @SLNetworks look at thread dates before bumping for no reason.
  10. The root of your problem is here So as JorgeB said, your filesystem is corrupt. You can try to repair the BTFRS superblock but I'm not exactly sure what you'd want to do to try.. if you google " can't read superblock on /dev/mapper" or "btrfs repair superblock" or similar terms like that you may find some help.
  11. find * -maxdepth 9999 -mtime +5 -exec rm -vf {} \; -exec /bin/echo {} \; | wc -l | { read count; echo "Done. $count files deleted."; } Grabbed this syntax from a thread on stackoverflow, works good.
  12. So unfortunately you did not read the update notes... https://wiki.unraid.net/Unraid_OS_6.9.0#Linux_Kernel
  13. Does everyone's CPU max out while scanning for photos? This thing was maxing out all my cores/threads until I pinned it down to 2/2 ..
  14. Compute all simply calculates the total size of the data on each share. Unprotected means that there is data that is not protected by the parity array, meaning it hasn't been copied to the array for parity calculation.
  15. I got "hack attempts" from my desktop pc because of a network lan scanner so it really depends on what's connecting or why.