Hog_Of-War

Put the drive into my desktop. It's got something wrong with it for sure. Makes some normal HDD sounds when it spins up, but the instant I go to access it or format it in NFTS it makes a Beep noise, is removed from Windows, and starts making boot up noises again. Gonna try to RMA it.

And while I was posting that, the drive is disabled and offline again. tower-diagnostics-20230607-1554.zip

You were right. Powered down server, reseat the drives and booted up. 18tb parity drive was seen, assigned it back to parity and started array. Assuming this was a power/connection problem since smart looks good. tower-diagnostics-20230607-1551.zip

Whelp, rebooted the server and now my parity disk is not present at all. Gonna finish prepping a new Parity drive, but this disk will have to wait till I get home to see what's going on with it. tower-diagnostics-20230607-1121.zip

Woke up this morning with the parity disk at 1000+ errors and disabled. I shut down the server, moved it to a different HBA and backplane and then rebooted and told it to rebuild parity hoping that it was a common power/sata problem. That parity rebuild failed 0.8% of the way in with the same symptoms, 1000+ errors and disabled. Tried looking at some smart data for the disk but nothing would load. Currently I'm moving data off another 18tb drive so that i can assign it as parity and rebuild. Can anyone tell me what happened here? is this disk dead? syslog-192.168.1.250 (1).log tower-diagnostics-20230607-1035.zip

Woke up to an out of memory error notification this morning. Anyone able to identify what caused it? Thanks! tower-diagnostics-20230423-0827.zip

After some quick testing, I believe I found the problem. I had changed the "Upon host shutdown" setting to Hibernate and my Home Assistant VM does not respond to a Hibernate command . Based on the help tip for the "VM shutdown time-out" setting Unraid should attempt to shutdown the VM but is not, preventing the array from stopping. Changed that setting back to shutdown and the array now stops in just over a minute as expected. Thanks for helping me through that!

It's now been 20 minutes. Docker tab is confused about if docker is running or not. All of my dockers appear to be access able and the UI works under the warning. Not a single Docker was stopped. Same with VMs. I'm not really convinced that clicking stop array did anything other than change the status at the bottom of the window tower-diagnostics-20230420-1242.zip

Here are the Diags that were in the logs folder, looks like they are from the first reboot this morning based on the time. The -1119 I previously uploaded was also there. I stopped the array and have a stop watch going. Just passed 5 minutes, will update when it finishes. tower-diagnostics-20230420-0846.zip

I have been going through a slew of problems with my server over the past month and all of them have been fixed but now I am no longer able to perform a clean shutdown. I rebooted this morning and when I started the array, it started a parity check for "unclean shutdown detected" which I cancelled and started googling solutions/causes to. The biggest thing I found that seemed generically applicable was changing the shutdown time-out to longer, so I changed it to 420 and commanded another restart. Again another parity sync was started. Attached are my diags from this last reboot and my Syslog file from the last several days. Can anyone help identify what is causing these unclean shutdowns? syslog-192.168.1.250.log tower-diagnostics-20230420-1119.zip

Yeah, server was still up and unable to use mkdir when I downloaded that diag. I ended up rebooting and it has been fine since.

This has happened a few times to me on V6.12.0-RC2. I previously had disks un-mounting during heavy use and was able to troubleshoot that down to bad power connections (i ended up having 10 disks on a single molex cable out of my PSU) now occasionally i lose the ability to use mkdir or create any folders anywhere on the array. I'm sure there are likely other problems as well but this is the most noticeable to me. I get a 'mkdir: cannot create directory '/mnt/user/Media/Torrents/test': No such file or directory' error for all of my attempts. Dockers fail to start if a directory does not exist. Normally i would just reboot the whole system but it would be nice to know whats causing and prevent it, i couldn't find it documented anywhere else in the bug report sections. Thanks in advance for the help! and diagnostics included! tower-diagnostics-20230403-2114.zip

My server has been acting strange the last week and i was trying to troubleshoot it myself and have failed. I was attempting to remove a data disk and shrink my array. I removed all the data off the drive, zero'd it using the user script, removed it, and then was checking parity and during parity disk 7 had like 2000 UDMA CRC errors and was unmounted, pausing the check. I tried resuming but found instead that it just kept erroring. I decided to reboot the server and attempt to just restart the check, but after the reboot disk 7 is now unmountable with a wrong or no file system. So i started to rebuild that disk and this time disk 3 started giving millions of errors and a few CRC errors. so i rebooted again and started rebuild again, and now i have disk 5 giving millions of errors and disk 3 still ticking up CRC errors and disk 7 still unmountable. From what i can tell googling this is usually a sata data cable problem, but to have so many "random" errors across disks im starting to think my PCIE SAS adapter is dying maybe? Looking at the cables, these drives are not even on the same breakout cable Can anyone see anything in the diagnostics from this last boot with CRC notifications on disk 3 and errors on disk 5? tower-diagnostics-20230308-0706.zip

Over the past week several of my drives have been showing read/write errors. First it was a data drive and my Parity drive, I transferred all the data off that drive (Disk10 now) and removed my parity drive and ran my server without either of those in the array, and then another one of my 14TB drives started showing errors. I made sure all my sata cables and power cables were well connected since that's what I found in my Googling. but I'm not really sure what is causing this or if this is a sign of something larger failing than my disks, as I doubt all of my larger new disks are failing so soon. I'm not really sure how to troubleshoot this or where to go from here with so many drives reporting errors. I'm not too worried about data loss overall since all of the array data could be replaced if needed. I would like to get this resolved though as showing this many errors is not something I like. Thanks in advance, let me know what else i can provide to help figure this out! tower-diagnostics-20220110-1343.zip