Jon4got2

I did go through those instructions which brought me to this page which only had the 16.00.10.00 firmware. I'll look for that other firmware, but if you have a different link I'd appreciate it.

Thanks @JorgeB. I was pretty sure I had updated the firmware, but I went through the firmware upgrade process (linked) again just to be safe, and it was on the same version. I have 20 hard drives and an 800 watt GameMax PSU, so I believe I have adequate power. The chassis is an inexpensive chinese unit, so I'm wondering if the backplanes are not distributing the power adequately. Or could be I need to solder these power connections? Anything else that I can check/test?

Hello. Over the last couple years I seem to have a reoccuring "disk failure" that can usually be remedied by changing the drive to a different bay in my JBOD chassis and making a new config or rebuilding the disk. This happens about every 2 to 4 months, but the worst part is once or twice it has happenned that before I get a chance to rebuild the disk or in the middle of it, another disk will fail and I'll lose data. Again, these disk will work fine once moved to another bay. My fairly new 14TB parity disk is now showing read errors, and I'm fairly certain I can move it to another bay and it will fix this read error, but it's now a reoccurring event that I'd really like to get to the bottom of. I assume it's a hardware issue, but before I go spending a ton of money on a new backplane or something for no reason, I'd greatly appreciate some guidance on how to troubleshoot a problem like this that is so infrequent. Thanks in advance. This community has been a life saver and a wonderful resource. tower-diagnostics-20221025-1009.zip

Thanks Squid! I did try all that before. Did it again and made it worse. What I missed was the power cable to the drive enclosure must not have been making good connection. Seems to be working now. Appreciate the help and all the awesome work you do for the community. Have a good one!

Hello. I just finished upgrading my mobo from an Asus Ryzen to an Asus Intel PRIME Z590-A with an i5-10400 and LSI 3008 HBA on my backup system. After spending some time tweaking the bios to get up and running, I had read errors on disk 5. Ran a smart test that came back fine. Cleaned and reseated connections, tried to reset the config, but same results. I moved disk 5 to another bay and reset config, and again after a short bit disk 5 was disabled with read errors. Now, disk 6 is also showing read errors. Could it be that I have some drives on the HBA and some on the mobo SATA controller? This was the configuration before. The only thing I changed besides the momo, cpu, memory was I upgraded the cache to a 1TB samsung 980 Pro NVME and I had to change to UEFI to use the quick sync GPU. Thanks for your help! Jon bunker-diagnostics-20220313-1253.zip

this time after i formatted #5, it mounted properly and seems to be rebuilding and not throwing errors on #7. I'll let this run through and hopefully the second time was the charm. If it doesn't take I'll reboot and send you those diags. Thanks again for your help. I really appreciate it!

looks like i may have uploaded the 1st one twice like you suspected. sorry about that. (foggy brain)

I definitely did the new config. got to where all the blue boxes were next to the drives and restarted the config. I just went through and did it all again. I attached another set of diag. tower-diagnostics-20220310-1347.zip

when i restarted without disk 5, it was not emulated. just showing "not installed" and "unmountable"

new diag attached tower-diagnostics-20220310-1200.zip

Thanks Jorge! Okay I got all that to work except then it asked me to format disk #5, so I did. Now it still says "unmountable" and asking to format again. Tried selecting xfs file system, but no luck. Any ideas?

Hello. I ran into something similar almost a couple years ago, coincidentally I had covid then and just got it now again, and the brain just does not function well with this so please bare with me if you could. I'm running Version: 6.10.0-rc2 mobo: Asus PRIME Z590 processor: i5-11600K HBA: (2) LSI SAS3008 Things have been smooth sailing for the last couple years, but a couple days ago a drive (#5) was throwing up errors. I pulled the drive, cleaned the contacts, reinstalled and ran a smart test which came back fine. I formatted the drive and re-added to the array. In the middle of rebuilding the drive, another disk (#7) started throwing errors. Like a dummy, I stopped the rebuild of #5 about 1/4 way through before the #7 disk had totally failed an was disabled, powered down and cleaned the connections to that one. Rebooted and #7 was disabled. I tried running xfs repair and got: superblock read failed, offset 0, size 524288, ag 0, rval -1 fatal error -- Input/output error I'm currently running an extended smart test on that one. It's obviously a rare chance that 2 drives failed at the same time, so I'm guessing it's a HBA or something to that effect, but my foggy brain is having issues troubleshooting at the moment. I'm hoping someone can poke through these logs and point me in the right direction. I only have one parity drive and really hope I can at least get #7 back up so I can rebuild #5. I truly appreciate your help! Jon tower-diagnostics-20220310-1200.zip

Thanks Meep! I'll give that a shot. Do you think it would help if I deleted the network config file from the USB and reconfigured? Is there a possibility that there is something corrupted with how the Docker passes data to the NIC? Would deleting the Docker and rebuilding possibly fix that?

Beuller? Bueller?

Hello All. I've been having this issue ongoing for a while. The system seems to be somewhat stable if I leave the dockers disabled and the network non bonded, but when I enable bonding 802.3ad I start getting a bunch of "Call Trace" errors and "received packet on bond0 with own address as source address". I have another server with this identical NIC connected to the same switch and same settings with zero problems. After a short while, the docker becomes unresponsive, then I can't get to a command line or run a diagnostic, then the entire system just freezes and it won't even allow a clean shut down by power switch. As I cannot generally pull the diagnostics after issues start occurring, I leave a log window open, and have copied that info to a text file. I'm about to the point of just wiping this entire system and starting over. It's been incredibly frustrating, but my backup machine runs rock solid built with just random crap I had laying around. I'd really appreciate it if someone could guide me in the right direction here. I have today's diagnostics attached as well as the text file. Please let me know if you need any additional info. tower-diagnostics-20210111-0853.zip unraid log 1.11.rtf