Energen

One of my HGST drives for comparison -- 66588 (7y, 7m, 3d, 12h)

Assuming that your NAS is full and you can't add any new empty drives you're only real option is to move as much data as you can off 1 or 2 of your existing drives onto the other drives, consolodate to as few existing drives that you can. Then add as many new drives that you can replacing the ones you've emptied off. Then repeat that process with the remaining 2TB drives, moving that data to the new empty drives. It's a bit of a hassle, but it's just about the only way to do it. You can use the unblance plugin to simplify the process a little bit to consolodate data.

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.

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.

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.

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.

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.

How about from the Go file? Is it a passphrase? You could try echo -n "key" > /root/keyfile and see if that works.

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.

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..

Once again, this thread is originally 6 years old. HTTPS is already implemented. @SLNetworks look at thread dates before bumping for no reason.

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.

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.

So unfortunately you did not read the update notes... https://wiki.unraid.net/Unraid_OS_6.9.0#Linux_Kernel

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 ..

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.

I got "hack attempts" from my desktop pc because of a network lan scanner so it really depends on what's connecting or why.

So I don't know much about configuring domain names... I only just bought one last week, for the first time ever with Namecheap. Same type of setup, though. @ has to be an IP address and not a hostname. One work around would be if GoDaddy has any automated dynamic ip update api that you could use to update from a user script ... something apparently along the lines of: https://www.godaddy.com/community/Managing-Domains/Dynamic-DNS-Updates/td-p/7862 https://www.instructables.com/Quick-and-Dirty-Dynamic-DNS-Using-GoDaddy/ As for the photos.. I don't have anything set up at the moment but in the past I've used piwigo for a gallery type of display. It is ok, but doesn't offer a very modern feeling interface... so it depends what you're after. Some I've been meaning to try but haven't gotten around to them yet --- librephotos, photoprism, photoview, and chevereto There's a couple threads here about photo dockers... might find some inspiration. If you search for photos in the community apps you'll see all these pop up.

Did you create the keyfile from windows or from the console? (unix file type is required) Not sure if anyone can confirm whether or not a symlink can be used with a keyfile? You should eliminate any potential problem by just copying the file to /root Ultimately I was experiencing a number of problems with autostarting the array and ended up just using echo -n "key" > /root/keyfile in my go file... before I decrypted all my drives again because the encryption was a pain in the arse.

Yes you need it.. that's default. Not sure about the port 8088 though, maybe at some point you specifically changed the WebUI port to 8088 instead of running on 80? (Should be in your settings though).

Can't help you on any of the specifics that you asked about as I'm not an expert of iommu groups, etc.. but I can only add that I briefly started up the latest beta Unraid on my X570 Tomahawk just to see what it looked like for performance on my Ryzen 7 3700X.. and while I didn't actually get into running anything for dockers/vms/etc I didn't notice any obvious issues with the platform. I know this doesn't help you for anything you asked about, sorry about that!

A 'you' problem, somewhere. I just reinstalled my docker and it went smooth, took about 3 seconds. It seems that you are getting blocked from connecting to the Docker website, either by a DNS/firewall/vpn/proxy/ something along those lines. Even something like pi-hole could potentially block you.

You would simply use a Windows version (or Mac, whatever you use) of a backup program to backup your local folders to Unraid. Or just get in the habit of copying your new files to Unraid. I've got a Photos share where all my pictures are stored. When I'm done processing them on PC I move them to Unraid.

Yes you need to roll back to Kodi 18 on the Shield.. different version databases are not compatible. This headless will continue to update the v18 database while the Shield will be looking at the v19 database.

So I'm confused.. You can't install the virtio drivers until the VM is installed... so... do you have the VM installed and then you get an error? Or are you trying to load the virtio drivers during the install and then getting an error? If you are trying to load them during install then you are not following any directions, since the drivers are loaded in Windows after the VM is created. Next.. once you clarify what you're doing here... what are your VM settings for the disk types.. SATA/virtio/IDE.. etc..