chris206

Okay, took several more hours than I remembered it would, but parity-check finished with 0 errors. As requested, I uploaded more recent diagnostics. Now, one question I have is, would it be okay for me to turn off syslog mirroring? The documentation warns that it can wear out the usb drive faster if it's left running. tower-diagnostics-20261007-1530.zip

Regarding disk 16, I've been wary of that drive since I got it. Those errors were present two years ago when I first precleared it if I recall correctly. I have four newer hotswap spares and I've considered swapping it out for one of them. There's not much data on it, so the copy wouldn't take much time. It'll take about 22 hours to finish the parity check, so I'll post the requested information along with any updates around this time tomorrow.

I restarted it after a few minutes for my own sanity. So, I should be okay. Edit: checked syslog again and this time it showed up as "check nocorrect", so it was probably good that I stopped and restarted it.

Alright did as suggested and restarted the parity check with corrections off. here's the diagnostics and syslog again. Is there a way to sanity check that write corrections are off? I forgot how the GUI displays the type of parity check in progress. tower-syslog-20261006-1751.zip tower-diagnostics-20261006-1247.zip

Forced shutdown, unplugged everything for several minutes and then powered it all back on. All disks appear as they should, none are disabled. As for the parity check, should I enable maintenance mode first? I figured I should uncheck "write corrections to parity". Is there anything else I should do before starting the array? Changing syslog to mirror was mentioned, would it be good to do that now before starting anything? Also, I should add that the Adaptec card I have does have an audible alarm for chipset overheat. I had that happen when I first got the card before I hooked up a Noctua fan to blow directly on its heatsink. I hadn't had issues since then. Plus, I never heard it alarm ever in the last couple days. It's as loud as the alarm on a UPS and I'm fairly certain it would've woken me up as its in the room next door. I don't know if windows 11 and quick access being buggy in the days leading up to this crash was at fault. I was having issues removing folders on the server from quick access in windows explorer. Anyways, below is the syslog from the reboot. It looks clean to me. tower-syslog-20261006-1716.zip

Alright, started the shutdown process, it certainly seems stuck already after 90 seconds. I'll wait until 10 as suggested and do a force shutdown with the power button.

Should I bother with stopping the array first, or should I let the shutdown attempt to handle that?

I've run into quite the error with my server. Something seemed to have happened with my RAID card which is running in HBA mode. I don't know if the card failed or the CPU did. Noticeable signs I'm running into is the CPU cores being pinned in the dashboard and the LEDs on the raid card are all flashing solid. I also cannot access files on my server. I honestly have no idea what exactly happened. It seems to have started with my UPS; however, I set it up to auto shutdown if it was on battery power for several minutes and the unit itself is new. I've only had it for a few months. (UPS was doing normal things. aacraid is the start of my problems.) Am I at risk of losing my data if I shutdown the server or reboot it? Also, even though it seemed to have thrown some serious errors, my server did not inform me about them. Edit: diagnostics scan seems to be taking quite a long time as well. tower-syslog-20261006-0532.zip

Parity check finished without errors. Everything's all good it seems.

Will do. It's scheduled to start tomorrow and is set up to increment, so I'll report back in a few days with results.

Done. tower-diagnostics-20260110-2152.zip

As the title states, the drives in my DAS didn't appear upon booting my server, because I failed to plug in the external cables correctly. I shutdown my server and the das, fully seated the cables and rebooted. All of my DAS drives show up now and short SMART tests of my two parity drives and disk 16 was completed without issues. These three drives are a part of my DAS along with the 4 12TB unassigned drives. The question I have is, should I proceed with caution still and start my array in maintenance mode to perform further checks? If so, what would those be? I'm due for a quarterly parity check that I've postponed for a week due to swapping hardware in the server. tower-syslog-20260111-0258.zip tower-diagnostics-20260110-2058.zip

To elaborate a bit further. My drives are actually connected to a SAS expander card, that is then plugged into the SAS raid controller. So perhaps the SAS expander had temp issues upon spinup? I need to recheck my drive positions in my tower, but based on previous notes it seems that the drive errors were spread across three different power splitters each on their own individual SATA power cable back to the PSU. Edit: Also, I should add, the 14TB drives and the 4 in unassigned devices are plugged directly into the RAID card through two of the external ports in a DAS.

I believe it should be in IT mode? I would not be surprised if it's setup wrong, I'm certainly an amateur.

Done. I often forget to include that one, thanks. tower-diagnostics-20251221-1506.zip