Everything posted by chris206
-
HBA card failure? Need help diagnosing and troubleshooting
Well, I ordered the necessary parts today; however the server ran into the same issue again. The previous time it took almost two weeks, this time it lasted roughly three days. It'll be about a week for everything to arrive, so I'll likely leave my server powered down until I can test the new card. As for replacing the card, is there a recommended procedure? I imagine I should replace the card and power up the system without the drives plugged in so I can verify the firmware is correct and do any other necessary steps. Also, is it okay for me to wait to do the parity check after the card is replaced? It's been a while since I did a swap of this kind. Lastly, I noticed something curious this time. I noticed one of my unassigned drives stopped reporting it's temperature and even disappeared from the unassigned devices section under the main tab. I don't know if that is important, but I felt it was worth mentioning. Is it possible for a failing drive to cause the HBA issues? tower-syslog-20261101-0048.zip
-
HBA card failure? Need help diagnosing and troubleshooting
All the drives in my system are SAS, used enterprise drives.
-
HBA card failure? Need help diagnosing and troubleshooting
Would a LSI 9300-8i with an HP 761879-001 AEC-83605 12GB SAS EXPANDER CARD be a suitable setup? The expander has 9 ports so even with two of them occupied by the HBA, I could plug into 28 drives total, which is enough for my current setup. The only caveat being that I'd have to run cables through adapters from the expander to the drives in my DAS. Total cable length for the drives in the DAS should be no more than 5-6m. There's no expander on the other end, simply an 8i8e adapter to the drives in that case.
-
HBA card failure? Need help diagnosing and troubleshooting
Yeah, I'll likely go with the 9305-16i as it's in my budget. Hopefully these sellers on eBay are being honest about where they sourced the card from. As for the parity check, once again, it finished without errors. So, I'll certainly be moving forward to change the card within a week or so. tower-syslog-20261029-0908.zip
-
HBA card failure? Need help diagnosing and troubleshooting
Could an LSI 9212-4i4e be a suitable I already have a SAS expander, so I shouldn't need 24-ports technically. The adaptec card was one of the first ones I came across with external ports. I see there are 9305-16i cards, but they seem to be missing the additional 2 miniSAS ports. I suppose that was a cost cutting measure and they simply reused the same board for 24i and 16i cards. I was also looking at the LSI 9300-16i earlier; however, I saw a lot of posts claiming it runs hot. Either way, I should be able to get the eight external ports I need with a 16i card as well as an adapter. I only need eight internal ports for the expander, so it shouldn't be an issue. Most 24-port cards seem out of the budget I want to spend anyways.
-
HBA card failure? Need help diagnosing and troubleshooting
Well, the same error happened again. I'm going to go through the process of checking the drives again. I'm still at a loss for why this error is happening. Could it be that the ram or cpu is going bad and causing the error? The reason I ask this is due to the fact that I've been using this controller for well over a year without issues and now it's all of a sudden having problems. The rest of the system is over five years old. Also, I'll have to see if I can find a suitable replacement for this card. It had the right number of ports that I needed for my setup and I'm not sure LSI makes one with a similar configuration. Edit: So far reporting the same outcome as last time. Forced Shutdown Power cycle via unplugging system boot system, no errors start array, followed by canceling automatic parity check start non-correcting parity check I'll report back in a day or so once the parity check completes. Also re-enabled syslog mirror during this process. tower-syslog-20261028-0156.zip
-
HBA card failure? Need help diagnosing and troubleshooting
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
-
HBA card failure? Need help diagnosing and troubleshooting
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.
-
HBA card failure? Need help diagnosing and troubleshooting
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.
-
HBA card failure? Need help diagnosing and troubleshooting
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
-
HBA card failure? Need help diagnosing and troubleshooting
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
-
HBA card failure? Need help diagnosing and troubleshooting
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.
-
HBA card failure? Need help diagnosing and troubleshooting
Should I bother with stopping the array first, or should I let the shutdown attempt to handle that?
-
HBA card failure? Need help diagnosing and troubleshooting
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
-
DAS drives didn't show up initially due to the cables not being fully seated, after fixing should I start my array in maintenance mode first?
Parity check finished without errors. Everything's all good it seems.
-
DAS drives didn't show up initially due to the cables not being fully seated, after fixing should I start my array in maintenance mode first?
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.
-
DAS drives didn't show up initially due to the cables not being fully seated, after fixing should I start my array in maintenance mode first?
Done. tower-diagnostics-20260110-2152.zip
-
DAS drives didn't show up initially due to the cables not being fully seated, after fixing should I start my array in maintenance mode first?
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
-
How to keep Windows Explorer from spinning up the disks in my Array?
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.
-
How to keep Windows Explorer from spinning up the disks in my Array?
I believe it should be in IT mode? I would not be surprised if it's setup wrong, I'm certainly an amateur.
-
How to keep Windows Explorer from spinning up the disks in my Array?
Done. I often forget to include that one, thanks. tower-diagnostics-20251221-1506.zip
-
How to keep Windows Explorer from spinning up the disks in my Array?
I am using power splitters. There should be a max of five drives on each SATA power cable if I'm recalling correctly. The SAS card itself has a noctua 40mm fan attached to it that is constantly spinning at ~3k rpm. I could certainly open up the back of my tower and trace each drive back to their respective power cable.
-
How to keep Windows Explorer from spinning up the disks in my Array?
Today I decided to start using a different approach to managing my drives in my array. I thought I'd start spinning them down after an hour of no usage. This seemed reasonable until I ran into an issue when I opened windows explorer on my PC to access a local file which has a share folder from my array mapped as a network drive. I traced my array drives all spinning up to the opening of windows explorer. This led to five of my drives having four read errors each, which I assume was related to the drives not being fully spun up when explorer tried to access some data on them. My filesystem seemed to have some issues as I couldn't see any of the folders/files on the mapped network drive. I went ahead and stopped my array and started it back up, which unRaid reported as error free and the errors disappeared on the main tab in the GUI. I was also able to browse the folders properly after doing this. So, my primary question is, how can I prevent windows explorer from doing this in the future? I removed a network folder that had been pinned automatically to quick access by windows, but there's also a few files in the history of explorer too. Should I turn off indexing for the mapped network drive? Also, should I be concerned about those five drives throwing four read errors each and the filesystem not being accessible until I stopped and started it back up? tower-syslog-20251221-0439.zip
-
XFS - Corruption of in-memory data
Finally reran xfs_repair through the CLI. The GUI for check filesystem doesn't seem like it'll refresh itself after taking the array out of maintenance mode. Anyways, I uploaded the output from the CLI. Seems like it zeroed the log and mentioned moving files to the lost + found, but I didn't see that folder on the disk after starting the array. Everything still checks out okay and that previous warning I was worried about is no longer there. Not entirely sure what caused the issue with reporting the remaining freespace, but I've got a new drive in my server, so hopefully it won't happen again. Thanks for all of the help. xfs_repair_log_20250824.txt
-
XFS - Corruption of in-memory data
Alright, should I run that through the terminal as well or is the GUI fine? I don't remember having the ability to change flags in the check filesystem section for the disk's page.