Uggers

I've been reading https://wiki.unraid.net/The_parity_swap_procedure and understand the process but It looks like the array will be down while this goes ahead. If want to replace both Parity Drives and 1 Data Drive and I want the array to be still up with parity my only options would be; 1. Stop Array 2. Unassign 1x Parity Drive 3. Power down, swap drives 4. Power up - PreClear new parity drive 5. Stop array, assign the new parity drive in the slot of the old parity drive and let rebuild parity 6. Repeat for 2nd Parity Drive Then for Data just follow; https://wiki.unraid.net/Replacing_a_Data_Drive

Ah $#%&. I totally missed that, thanks for making me re-read it, apologies for the unnecessary question as well. DOH!

I'm having some issues recently after some docker containers updated. I updated to Unraid 6.9.1 but that didn't seem to help either. Up until recently everything was working all fine. I thought this might be due to the issue with iptables I see people talking about, but I am not sure if it is, and if it is, I don't know if I implemented the fix properly. Basically the error I am getting in Sonnar, Radarr etc is "Unknown exception: The operation has timed out.: 'https://192.168.1.98:8112/json'" My Ports in use are Deluge - 8112 Sonar - 8989 Radarr - 7878 Jackett - 9117 I am using Mullvad as my VPN. As per the screenshot, I added a Variable called VPN_OUTPUT_PORTS and added the Deluge Port. (although now I type that I realise I am not sure even that was correct) My error might have nothing to do with it, but at the time when I Set it all up I followed SpaceInvaderOne's videos so there are probably nuances I glossed over that I don't understand now

Ah fair enough, I thought I had read someone where might be SATA Cables as well I'm probably just confusing the issues now.

Its about 1 hour away from rebuilding but about 20 minutes in I got Reallocated sector count 412 The case I am using is a lian li pc-q25 which has a backplane, so I wonder if maybe that's faulty around that drive. If I shut down unraid, then swap the parity drives around physically, would it be safe to guess if The same drive still has Reallocated sector count issues, the drive is failing (2017 drive) If the other parity drive is now getting Reallocated sector counts, then its likely fault with the backplane on the case (I swapped all SATA cables when I was in the case earlier)

Thank you, appreciate the clarification will stop a follow up question

I believe it is; Disable Array Un-assign Disk Re-enable Array Disable Array Assign Disk Re-enable Array - it will then rebuild parity on that drive Yeah I swapped them over just to make sure.

Latest SMART report It seems to be ok. So I guess I should re-enable the drive and see how it works. WDC_WD30EZRZ-00Z5HB0_WD-WCC4N4XV91CX-20210225-0825.txt

Thanks, I've reseated all the cables and the drive back onto the disk plane. I am now just re-running the extended smart now and will attach results. I thought I'd clicked it last night but I hadn't DOH!

Hey, I'm hoping for a bit of assistance, I got an error pop up for my 2nd Parity drive and then it went disabled. I tried to do a smart test but it wouldn't start. I restarted the box and checked the connections and it seemed ok. The only changes I've had for a few weeks and today was some new downloads and I moved some ISO's and some of my dockers updated. Not to say it couldn't be those things but normal things I guess? I've attached my diagnostics and the quick smart test I was able to run after it restart. I'm running a longer smart test now and will add it on if its needed, but its obviously quite slow. tower-diagnostics-20210224-2231.zip WDC_WD30EZRZ-00Z5HB0_WD-WCC4N4XV91CX-20210224-2232.txt

I asked this question on the Plex docker topic but I am still not 100% sure whats up, My Unraid setup is G4560 16GB Ram Gigabyte Z270N-WIFI Playback is a Nvidia Shield Whenever playing back through Plex, I find the CPU constantly bounced up to 100% and back down again, while I don't think its doing any damage per say,I can hear the noctua fan constantly spinning up and slowing down as it adjusts to the temp. It's spiking alot though. On the playback, I have options to transcode or play original, but I don't have plex pass. I am not sure if this is a feature of the Nvidia Shield or I'm miss understanding the differences between transcoding over local ethernet. Also when playing back some formats I get artifacting on the files, both in Plex and Kodi, but when I play them back on PC or the PC app, they play fine. Attached is my diagnostic files, incase I have done anything dumb with the set up, or something obvious why it could be spiking. Not sure if any other logs that can help. tower-diagnostics-20201019-1156.zip

ah awesome thats great. Quick follow up, is Plex Pass mandatory then? as I get the options to transcode (locally) anyway? and I don't have PlexPass Many thanks.

Wasn't entirely sure where to ask this, but my CPU (a G4560) keeps spiking up to 100% then 20% then 100% while transcoding is going on. I believe its because its not using the igpu to transcode. I wasn't sure how I needed to set this up, if it was something to set up in this container I am using, or a general Unraid setting?

Just wanted to add my diagnostics file tower-diagnostics-20170926-2300.zip I also saw some errors to do with bond{0} and possibly usb port (I can't tell for sure as I wasn't sure how to scroll back up

Hi, I'm having an issue with my server, I power it down regularly when I am away and won't be using it but I have an issue were it doesn't always power up properly. Basically it appears to power up but one of 2 things happen I can't access the server via /tower The server doesn't boot the USB stick I'm using a cruzer fit for the USB stick and hardware is Corsasir SF450 PSU 2x8GB Crucial DDR4 Intel G4560 Gigabye Z170N-Wi-Fi Lian Li - PC-Q25B Crucial 256 SSD for Cache Drive x2 WD 3TB Blue for 2 Parity Drives x2 WD 3TB and 1x WD 2TB Red for storage drives. I move the USB stick to a different port and it will usually boot up. Any thoughts at all, does this sound like a symptom of a fault usb stick?