dchamb

I recently moved my Plex system to use the linuxserver.io plex docker. All seems well except occasionally I see a half second blip on screen during playback. I thought it might be related to the transcode folder, since it looks like it is going to the array. I tried to move it to tmp, but that made the problem worse, even causing some content to not play at all. I also noticed that using Plex.tv webgui it tends to skip ahead 5 seconds or so several times. Any thoughts on what is causing this? I had no problems like this running Plex under the PhaZe plugin. Dale

I had a bad experience going to 6.7.0. Two of my array drives showed up as missing. I rolled back to 6.6.6 and all was well. I will not be updating to 6.7.0. I would encourage you to roll back as well. There's a good chance nothing was corrupted. But in the event there was, it will be a matter of rebuilding the Plex appdata and not the media files. I realize this may not be a small feat if your library is as large as mine, but it beats the alternative. I do wish they would test these releases more diligently before making them available. Dale

Server Version#: 1.14.1.5488-cc260c476 I know the PhAzE Plex plug has been deprecated but does anyone know if it will still run under Unraid 6.6.6? Seems that the Plex server keeps crashing and I’m wondering if its now time to make the move to the Docker container. Also, I haven’t been able to get to the Plex logs. Dale

Monthly parity check shows no errors! Event: unRAID Parity check Subject: Notice [TOWER] - Parity check finished (0 errors) Description: Duration: 23 hours, 49 minutes, 14 seconds. Average speed: 139.9 MB/s Importance: normal Plus that 12TB WD Gold drive has improved the elapsed time of the parity check. I've been very happy with those drives. Dale

My monthly parity check is scheduled for tomorrow so I should know before the weekend is over. Thanks!

I installed my first new drive into the array without using preclear and it went flawlessly! The new drive is a WD Datacenter Gold 12TB which replaced a WD Red 6TB. Here are the stats: Event: unRAID Parity sync / Data rebuild Subject: Notice [TOWER] - Parity sync / Data rebuild finished (0 errors) Description: Duration: 1 day, 33 minutes, 16 seconds. Average speed: 135.8 MB/s Importance: normal Much faster to be fully up and running and have a protected array than it used to be. Good job!

It was a couple of days but that was going through the first 4 phases of preclear. Preclear crashed because of the script problem in phase 5 so I never completed it. I assigned to unRAID and everything has been working fine. My array consists of the 12TB WD Gold for the parity drive, a 10TB Gold data and 3 6TB Red drives and it takes 1 day 40 minutes to do a parity check at 135.1 MB/s.

Thanks Frank1490, Is there a document somewhere that describes how the second parity algorithm works? My unRAID server uses an Intel i5-3570. I'm pretty sure I'm covered. Dale

For clarification, is the second parity drive a mirror of the first parity drive? I can see how it protects the array if the first parity drive fails, or if a data drive fails during a parity drive rebuild. But if 2 data drives fail at the same time, you lose data right?

johnnie.black, Thanks! That did the trick! Preclear works again and reports my drive was successfully precleared. I am rebuilding my parity drive now.

Not sure what is there to kill. I rebooted the unRAID machine and it still says the device is busy. It looks like an error in the script to me.

I used the preclear plugin. But when I try to run the script, it keeps telling me the drive is busy! Why can't I get this thing to preclear? I'm thinking of just putting the drive in the array and forgetting preclear.

Seems the fault lies with preclear. It crashed on a segmentation fault. I'm going to reboot and try it from a command line. Btw, I'm not hung up on the fancy names either. That's just what they call it. I have a 10TB WD Gold that runs like a top so when they came out with a 12TB for the same price as the 10TB I grabbed it up. Being 62 myself I think I'm an old timer myself lol! Sent from my SM-G955U using Tapatalk

Thanks John_M. Are you referring to SMART diagnostics? Sent from my SM-G955U using Tapatalk

I replaced the cable, started preclear again. This time it was going much faster and the CRC error count did not increase from where it was before the cable was replaced. I got through steps 1 through 4, but it has been hung up on step 5 for several hours at 18%. I really need to determine if the drive is faulty even though SMART shows it is fine, or if there is a problem with preclear, or something else. Help! Thanks Dale

Also since it appears from the log report it completed the clear operation successfully, is there a way to verify the drive without going through preclear again? I'd like to know if the drive is usable. It just looks like preclear stopped at 18% of the post clear read.

Frank1940, did you see in my post where I already acknowledged the cable issue and replaced it? This problem of hanging on 18% on the post clear read has occurred after the cable was replaced. It seems like it might be an issue with preclear. Any known problems dealing with a drive of 12TB?

I am running into a problem with preclear on a WD Datacenter Gold 12TB drive. It made it through steps 1 through 4 and started on step 5 where it seems stuck at 18%. The drive also shows spun down. The version of Preclear is 2017.11.14. Here is the log report so far. (The 199-UDMA_CRC_Error_Count 106286 is from a previous attempt where I had a faulty cable. The cable has since been replaced and no more CRC errors have been logged): ############################################################################################################################ # # # unRAID Server Preclear of disk 8DG3KEVD # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [17:14:58 @ 193 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [17:08:12 @ 194 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read in progress: (18% Done) # # # # # # # # # # # # ** Time elapsed: 2:36:56 | Current speed: 239 MB/s | Average speed: 239 MB/s # # # ############################################################################################################################ # Cycle elapsed time: 37:00:08 | Total elapsed time: 37:00:08 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status default # # # # # # ATTRIBUTE INITIAL STATUS # # 5-Reallocated_Sector_Ct 0 - # # 9-Power_On_Hours 93 - # # 194-Temperature_Celsius 35 - # # 196-Reallocated_Event_Count 0 - # # 197-Current_Pending_Sector 0 - # # 198-Offline_Uncorrectable 0 - # # 199-UDMA_CRC_Error_Count 106286 - # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ Segmentation fault root@Tower:/usr/local/emhttp# What do you make of this? Thanks Dale

Hello, I am trying to ready a Western Digital Datacenter Gold 12TB drive to replace my current parity drive. I ran the preclear for over 58 hours making it through 4 of 5 steps before failing on step 5. Here are my questions: 1. Am I dealing with a bad drive? 2. Is there a way to start the preclear without going through steps 1 - 4? 3. Could there be a BIOS issue here? Here is the preclear report: ############################################################################################################################ # # # unRAID Server Preclear of disk 8DG3KEVD # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [17:14:50 @ 193 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [41:09:23 @ 80 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read verification: FAIL # # # # # # # # # # # # # # # ############################################################################################################################ # Cycle elapsed time: 58:33:47 | Total elapsed time: 58:33:47 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status default # # # # # # ATTRIBUTE INITIAL STATUS # # 5-Reallocated_Sector_Ct 0 - # # 9-Power_On_Hours 0 - # # 194-Temperature_Celsius 34 - # # 196-Reallocated_Event_Count 0 - # # 197-Current_Pending_Sector 0 - # # 198-Offline_Uncorrectable 0 - # # 199-UDMA_CRC_Error_Count 131 - # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ --> FAIL: Post-Read verification failed. Your drive is not zeroed. root@Tower:/usr/local/emhttp# Thanks! Dale

These links come up "File Not Found"

I've been searching on this forum for guidance for migrating from the Phaze Plex plugin to the Plex supported docker implementation, but my head is about to explode with all the variations I've been seeing. Is there one place to go to get guidance for making the transition without losing all of my Plex settings? Also, I see reference to backing up the library. I hope this isn't referring to the media library as it is approximately 24TB! Thanks for any help! Dale Sent from my SM-N920V using Tapatalk

So is the data array plus the first parity drive included in the second parity drive's hash? And that would provide the protection in case a parity drive and a data drive fail simultaneously (or 2 data drives for that matter)? Sent from my SM-N920V using Tapatalk

My current unRAID configuration has 1 parity (10TB) and 4 data (6TB) drives. I can see how adding a second parity drive protects the array from a parity drive failure, but are there other ways a second parity drive protects the array? Sent from my SM-N920V using Tapatalk

Big difference in cooling. My WD Red Pro 6TB runs between 45-50 C and the Gold is at least 10 C under that.

Yeah that's what I thought. Faster than a 6TB 7200rpm WD Red Pro!