loyalsnoopdoge

Just updated to 2026.03.30 and the issue is resolved! Thank you!

Hi @chodeus I just moved over from FolderView2. Thank you for taking the time to make this plugin I interact with every day have full functionality again I am encountering the exact same issue as @Joly0 when I have my Preview Overflow set to Default. Hoping this can be fixed in a future update I am currently on unRAID 7.2.4, accessing webUI from Google Chrome on a Mac, and I do not have the Docker Compose plugin installed. This occurs with both Advanced View and Basic View enabled FolderView3 version: 2026.03.28.1

Messed with the cables and had a successful rebuild. You can mark as closed

Thank you! I am interested in mitigating this issue in the future. The SAS to SATA breakout cables and SATA power cables are all relatively new. Is there anything else that could be causing an issue like this? Is it possible that the drives spinning up over the few months in between parity checks could partially loosen the cables?

Thanks for taking a look. Are my issues possibly relate to the issues from this thread with Eos drives?

Hello, I have my parity scheduled to run quarterly. My parity check kicked off this morning, and a couple of hours in to it I received a notice that Disk 5 has been disabled due to read errors and has been assigned a new drive letter in unRAID. The data appears to be in tact, and I am able to rebuild the drive from existing parity, but the drive letter being switched mid parity check is concerning Normally my server works perfectly fine, and I do not have read errors 7 of my drives are Seagate Exos 16TB drives. 1 of the drives is a Seagate Ironwolf Pro The drive that is showing errors is an Exos I have recently replaced my SAS to SATA breakout cables and the power cables on all the drives. I have posted my diagnostics. If someone can please tell me what is going on I would really appreciate it Update: I just tried a data reconstruction on the drive and now I have 2 drives in error states. Uploading another diagnostics file No such file or directory (2): tagged device ST16000NM000E-3NV101_ZX25HQ5B was (sdh) is now (sdj) diagnostics.zip new diagnostics.zip

I was able to fix the Dashboard issue by changing the LED signals from Dynamic to Static, then refreshed and changed them back to Dynamic

Looks like Disk Location's update today broke the Dashboard again Right after updating it I'm unable to load the Dashboard

I'm on 6.12.13 I have 8 of these drives and just had this issue Is this still an issue even on newer versions? Should I disable spindown altogether?

Since my last post I've been hard at work with this thing I just put new drives in with the new HBA and new SAS to SATA breakout cables. I made sure the temps aren't going above 40C on the drives. One of my brand new drives just threw a UDMA CRC error during a parity check I've also re seated the motherboard, and re seated all the connections on it. I also ran memtest for 16 hours to see if my RAM may be a potential issue, even though it's a connection issue I'm at a loss of what to do. do I replace the PSU and/or the motherboard?

Havent had a chance to fully disect the server. will update when I do. Appreciate the support

I have tried replacing the power cables as well. Do you think it could be the SATA connectors on the drives themselves?

UPDATE: Just plugged the drives throwing errors into the SATA ports on my motherboard, and they are still throwing UDMA CRC errors. I assume the drive is toast?

@JorgeBwhen you get a chance would you mind looking at my diagnostics? thank you in advance

Updated diagnostics now with Read errors Please use this one instead diagnostics-20240725-1217.zip

I plan on trying this when I get home today. Will update here

Hello unRAID community. I could use your support My setup: Intel Core i7 12700k 1x Seagate Ironwolf Pro 16TB (Parity 1) 4x WD Red Pro 16TB (Parity 2. Disks 1, 2, & 3) LSI 9400-16i in IT mode (all hard drives connected to this HBA) 2x Samsung 980 Pro 2TB in RAID1 (Cache) My issue: My server has been working great for the last year, then all of a sudden about 2 weeks ago I started getting UDMA CRC errors on all of my data drives during my quarterly parity check. This error is easily reproducible by doing a parity check, or during extended sessions with the mover. The odd thing is, that every time I reproduce the issue, the error will come from 1 or 2 of the drives at random, but not all 3. Eventually if I let the parity check run long enough, unRAID will detect errors on one of the 3 data drives. The concerning thing is that I find it hard to believe that 3 of my drives are failing. 2 of the 3 are ~1 year old, while the last one (which is having the most UDMA CRC issues, is 3 months old) Steps I have attempted to resolve: Updated BIOS on motherboard Updated unRAID to 6.12.11 Verified LSI 9400-16i is running latest firmware Dusted SAS ports on LSi, dusted PCIe slot, dusted SATA ports on HDD's Swapped all mini-SAS to SATA breakout cables for new ones Swapped power cables on HDD's for new ones (from PSU box) Switched LSI card to different PCIe slot Purchased new LSI 9400-16i HBA and installed with another set of brand new mini-SAS to SATA cables Extended SMART tests on all HDD's. All drives passed 2 Extended SMART tests I am running out of ideas to try. Is there anything else I can try, or should I accept that my data drives have gone bad? diagnostics-20240725-1217.zip

@JorgeB Hi there, Thanks for your help. I gave up on the USB drives in the NUC. I returned it and built a new system in the Fractal Design Define 7 XL. I got an LSI 9400 16i and some SAS to SATA breakout cables for my drives. Everything works great!

UPDATE: Looks like the DB is corrupted, but it's odd this has happened multiple times on multiple separate computers with multiple different Docker containers. any ideas what could be causing this? My Plex app data lives on Cache only. I have 2 980 Pro's in BTRFS in RAID1

I’m having a really infuriating issue with my PMS. I just moved over to unRAID with Docker and rebuilt my entire server from scratch multiple times. I have tried Binhex Plex, the official PMS docker, and am now using LinuxServers. This issue has now happened on every single one of them It will work fine for a couple of days and then it will always revert to the same behavior. First, any newly added media will not be detected, and then I completely lose the ability to edit any of my libraries. I cannot modify the folders for the library, the agent, or any of the metadata for any of my library items. I can’t even delete the specific libraries to read them. To me it’s really odd how it will work flawlessly and then randomly decide to cut out I have read all of the other threads about this and none of the suggestions work. I cannot keep rebuilding my entire library and Docker container every few days to remedy this. I need to reliably know that my media will show up when it is added and that I can modify the libraries. If anyone has any insight I would really appreciate it! Plex Media Server Logs_2023-07-31_21-00-19.zip

Hello @phea. Where did you get those SATA power cable extensions? those look amazing but I havent been able to find them anywhere on Amazon or Newegg. The ones I got are way too long in between the connectors

@JorgeB I'm trying a different enclosure, Thunderbolt this time but a similar but slightly different issue is happening this time Could you please look over my log file for this and let me know what you think the issue is? unicornbarfnuc-diagnostics-20230722-1852.zip

So this to you looks like a problem with either my USB cable or my enclosure. For right now I'm locked into doing this over USB, although I could change that in the future What about drivers? How do I go about updating the drivers on unRAID? What about settings in the BIOS on my NUC? are there any settings I could / should change? One other thing that is really weird is that I never get any disk errors when I am scanning / analyzing my Plex library. it only happens during parity sync. It also doesn't happen during read checks

Hello, I’m new to unRAID as of a week ago. I had been running Plex on my gaming PC, but switched over to an Intel NUC with unRAID to take advantage of Docker and ease of use for multiple disks. My Plex media was originally stored on the Seagate drive which used to live inside my gaming PC. My disk setup is as follows: 1x 16TB Seagate Iron Wolf Pro (age 6 months) PARITY 2x 16TB WD Red Pro (age 1 week) STORAGE These drives are in a 5 bay Sabrent USB C enclosure My cache setup is as follows: 2x 2TB Samsung 980 Pro in RAID1 These drives are directly attached to the motherboard Now on to the main issue: I copied my Plex library into my drives and have set up my Docker containers. However when I initiate my parity check it returns with a ton of errors. After it returns the errors, the parity check stops and changes to a read check. Then it tells me that my parity drive is disabled and I am unable to manually initiate another parity sync, it only shows read check. To attempt to remedy this I have tried the unRAID dance where I shut down the array, remove the parity drive, start the array, stop the array, re add the parity drive, and start again. However one of two things will happen when I do this. Either the parity check will start again and return a ton of errors and disable the drives again, or it will flat out just not see my drives at all until I restart unRAID again. I’ve also tried formatting the parity drive before re adding it to the array. I’m also having an issue where sometimes when I try to stop the array it takes a very long time to stop and sometimes it doesn’t stop at all until I reboot. I have attached diagnostics and am hoping someone can tell me how to resolve these errors and what is going wrong. Do I need to nuke my array and start over? I find it very improbable that all 3 drives are damaged, since the Seagate is a known working drive and the WD Red’s are brand new. diagnostics-20230720-0910.zip