josh266

Thank you for the review and firmware suggestion. I will look into doing that. I did notice the errors on my cache recently, as it wasn't all that old of a device to be acting up. I'll run the extended SMART test to see what it shows. Thank you again.

This morning I received an e-mail notification that my Unraid had disabled disk 3 due to errors and there were also errors on disk2 (but not disabled yet) Disk 2 was actually replaced with a new precleared drive a few weeks ago after being disabled. I actually opened a topic for that one here - I am assuming I should replace disk 3 with a new precleared drive (so I still have the prior disk if the data is good) but not sure if this is related to the prior issue. Both of these drives are physically next to each other but I haven't looked closely on if they are attached to the same HBA card. The diagnostics zip file is included for any further analysis on what might have caused this. Thank you in advance for any suggestions. At this time I have not shutdown the system and it is emulating disk 3. tower-diagnostics-20230519-0749.zip

Thank you for the review and suggestion. Luckily I have a spare I can use and it's a 14tb so I can add a bit more space.

Sorry my caffeine hadn't kicked in yet and shouldn't have said disk 2 wasn't disabled Here is the latest diagnostics after the array is started. Thanks again, tower-diagnostics-20230424-0743.zip

Thank you. I ran the 'reboot' command this morning and the system came back up. Attached is the new diagnostics. From the main view, disk 2 has the red 'x' but isn't showing disabled anymore (and is not in my unassigned devices tab) My main worry was not having a clean shutdown while disk 2 was emulated. Appreciate any further review of the latest diagnostics. tower-diagnostics-20230424-0716.zip

This morning I was notified by email that disk2 had read errors and then was disabled. I have a spare disk I wanted to swap in place of disk2 but haven't been able to stop the array. When I click on 'stop array' it says are you sure and I choose 'proceed' Nothing happens and eventually I get a time out message (nginx: 2023/04/23 15:21:38 [error] 2338#2338: *4048431 connect() to unix:/var/run/emhttpd.socket failed (11: Resource temporarily unavailable) while connecting to upstream). I checked for the normal activity preventing a clean stop of the array such as files in use using lsof but didn't see anything. I have included diagnostics. At this time the array is still up. Can you help on how to stop the array cleanly if possible? Thank you tower-diagnostics-20230423-1500.zip