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