ttttubby

I just ordered a 6TB SATA drive from a used server part ebay store but received a 6TB Seagate Exos SAS drive instead. Fortunately I have a hard drive cage that is compatible with SAS drives and an LSI HBA card, so I was able to get it up and running, but I noticed like all of you that the SAS drive would not spin down. Followed the process outlined in this reddit thread (https://www.reddit.com/r/unRAID/comments/11r4ock/comment/jc8i1za/?utm_source=share&utm_medium=web2x&context=3) to install your plugin and it looked like everything was working properly until the mover tried to move some files to that disk. Then I got an 'X' next to the SAS drive and had to remove it from my array. Since Unraid 7.2 is supposed to offer some support for SAS drives I tried installing that and while the command: sg_start --stop /dev/sdX worked to spin things down while it was in unassigned devices (still had a green ball next to it but the temperature reading was an *), it also unmounted it and gave me the following error codes: 17:48:06: UNKNOWN(0x2003) Result: hostbyte=0x00 17:48:06: I/O error, dev sdh, sector 0 op 0x0:(READ) 17:48:06: Buffer I/O error on dev sdh, logical block 0 Does this mean that this drive is just incompatible with my server unless I want to leave it powered on 24/7? BTW contacted the ebay seller and told them item was not as described (I ordered a SATA drive after all) and they sent me a beat to shit HGST drive from June 2014 with gouges on the front like it had been thrown into a trash can with other drives.

Quick troubleshooting with Gemini and I think I've discovered the culprit. My target drive was hooked up to the LSI card which was causing the issue... what is wrong with my LSI card you ask? I don't have active cooling installed! Ordered a 60mm fan to ziptie to it and I expect all of my stability problems will disappear

I'm starting to think that there is something wrong with this LSI SAS card. Had a hard drive start to show bad sectors and used unbalance to move things off of it. I suspect that either the problem drive or the target drive was attached to the LSI card and caused things to freeze up again.

Well I've been stable for three weeks knock on wood but I think the mistake was putting my cache on the LSI SAS card. Probably something to do with sleep states.

Took out the extra drives, moved my cache to the onboard controller and switched my SATA settings to AHCI. Hopefully this puts an end to my issues. Will check back if I continue to run into problems.

Yeah, I have a couple of unassigned devices - my old 500gb cache drive and one of my old 2tb drives - which was replaced with a 12tb drive. I will pull both of those when my parity check has finished (so tomorrow).

I also noticed in my BIOS that my onboard SATA controllers are running in IDE mode rather than AHCI. Two questions: is there any chance this might be causing my issues? will changing from IDE mode to AHCI cause any issues with my current setup? Or would I need to reformat the drives etc?

Well, I just had my first crash (unraid became unresponsive) since installing the new ram so I don't think that was the problem. Syslog again doesn't say much. Looks like things locked up while the mover was doing its thing. I've attached the syslog and the diagnostics again. I'm trying to figure out what might be the failure point without shutting down all of my dockers etc as they are all doing mission critical work. Most recent upgrades/hardware changes: Cache Drive: swapped an old mechanical 500GB model to an ADATA 512gb SSD Oct 2024 - HDD upgrade: my most recent hard drive upgrade involved adding two 12tb refurbished HUH721212ALE601 hard drives - both of which passed preclear and show no errors Nov 2024 - HDD Interface: swapped out two PCI-E 2x SATA expansion cards for one LSI SAS2008 PCI-Express Fusion-MPT SAS-2 controller (which my cache drive is currently plugged into - but my 12tb drives are not) Dec 2024 - Flash Drive: swapped from a failing USB stick to a sandisk microUSB adapter with a sandisk microUSB for easier swapping in case of future failure I swapped in the SAS controller and the new hard drives at the same time. The flash drive swap came shortly after system reboots (because unraid was becoming unresponsive like it does now) started stalling on boot (some daemon wasn't starting - biz something). At the time I thought replacing the flash drive solved all of my problems and it did fix the daemon stalling but now that I think about it, the reason for the reboots was never quite clear - and it seems to be the same problem that I am currently running into. I can't remember if I was running into these stability problems with UNRAID before swapping out all of these parts in and around November 2024. The reason for all of the hardware changes was because I needed more space on the server, but I think the server was stable before that. I'm starting to think that the LSI SAS controller might be causing the issue, or at least that is what I'm hoping given that replacing the hard drives would be prohibitively expensive at the moment. Since the latest system freeze happened while the mover is running, I wonder whether moving my cache drive off of the SAS controller and onto one of the onboard sata ports might fix the problem. I would appreciate any input anyone might be willing to provide. syslog-192.168.0.10 (1).log tower-diagnostics-20250807-1015.zip

Had 12gb of DDR3 ram in the form of three mismatched sticks (two from a 2x4gb set and one stick from a different set). Amazon had a 16gb set (2x8gb) for less than $20 so I pulled the trigger and replaced them all. Hope that will sort out my issue. Fingers crossed.

I also swapped out my USB flash drive a few months ago with a USB microSD card reader. That seemed to solve my problem... until it didn't.

Unfortunately this happens pretty randomly. It will be fine for weeks and then one day be randomly unresponsive. Also, is there a trick to make memtest run multiple passes until it fails? When I tried using the memtest that comes with unraid, I couldn't figure out how to make it run continuously to stress test.

This is getting really frustrating. My unraid server keeps locking up at random times and won't respond without a reboot. I enabled syslog server and nothing is raising red flags to me, but I would appreciate whatever guidance you all might be able to provide. From what I can gather from the syslog, the server went down early this morning (7/28/2025) at 3:52am. Things I've tried: Memtest - passed IPVlan switched to macvlan syslog-192.168.0.10.log tower-diagnostics-20250728-0853.zip

I think so. Is there any way for me to check this?

Switched my two new 12tb drives to the onboard SATA ports and everything seems to be stable. Fingers crossed.

This is getting really really frustrating. As I noted above, even after swapping out the SAS breakout cable, I'm still seeing the same issues (my new drives keep disconnecting during preclear). The only thing I can think to do now is swap the sata cables so that the new drives are connected directly to the motherboard and old drives are connected to the SAS breakout cable. But even if that gets my new drives up and running properly is it going to do so at the cost of my older drives' stability?

I have swapped out the SAS breakout cable that was attached to the new drives. We will see what happens.

Have not had a crash again yet, but my unassigned devices are acting weird. Currently on the "main" page, under unassigned devices it says: "Timeout: Failed to get unassigned devices information - check the syslog." On the "Dashboard" page, the unassigned devices are there - or at least they were... now it only shows one of the unassigned devises. (and in the time it has taken me to write this post they are now both gone). My CPU, an Intel® Core™ i5-3475S CPU @ 2.90GHz, is currently fluctuating between 85% - 100% Upon checking the syslog, I'm not seeing any errors beyond the warnings that my ReiserFS disks are going to be removed from future kernels. Is this a problem with my LSI card? Or one of my breakout cables? (Come to think of it, the new drives that are struggling to preclear are both on the same breakout cable with nothing else attached to that breakout cable). Attached is the current syslog (mind you, the system is still up and running, er... limping along - the server is definitely less responsive with the CPU pinned as it is). tower-syslog-20241111-1801.zip

About a week or so ago I bought a couple of 12tb drives to add to my array. In the process I replaced a couple of Syba 1xpci-e 2x SATA controllers with an LSI SAS9201 8i H3-25268 SAS card. Everything installed ok, and my array was up and running again. I added the unassigned disk plugin, and the preclear add on and I started to preclear the 12tb drives. Again, everything looked good. Until... Unraid went completely unresponsive. I couldn't access it using its IP address. I couldn't putty in to shut it down. I usually run my server headless, but I plugged in a monitor and it didn't work either. So I performed a hard reboot Parity check took 8 hours but everything came back fine. Saw something in the syslog that made me think I needed to update my mobo bios. Updated the bios today. Everything seemed to be working well so I resumed the preclear on those two drives. Couple hours later and my server was unresponsive again. I would appreciate whatever help you can provide. I have attached the last three diagnositics (which I found on the unraid flashdrive) as well as the most recent syslog. tower-diagnostics-20241110-1726 (1).zip tower-diagnostics-20241110-1517 (1).zip tower-diagnostics-20241106-1332 (1).zip tower-syslog-20241110-2327.zip

Parity check passed. Everything looks ok. Sooo relieved.

Update Time: I took a chance that the motherboard had a dying capacitor or something causing it to fail due to the extra voltage and I ordered a replacement motherboard from eBay and crossed my fingers that nothing else (including the CPU) was damaged. The new board was an Asus h77. It had 6 sata ports rather than 8 but fortunately I had a second pcie sata controller. Once I confirmed that the new board was working I plugged in my hard drives and my unRAID USB and viola... My server is back up as if nothing happened! Parity check is running now but so far so good. Fingers crossed that this thing will limp along until the chip shortage ends and I build a new gaming rig and donate my old one for building a replacement unRAID server.

So a couple of nights ago lightning struck just outside of my house. I didn't realize until the next morning but there were several casualties. I lost my cable modem (which Spectrum replaced for free) two monoprice 8 port switches, a 4x hdmi switch and my relatively old but previously bulletproof unraid server which would no longer turn on. I ordered a replacement power supply to see if I could get it going again but alas, no dice. I had upgraded the CPU a little while back (from a Pentium G630t to a Core i5 3475S) so I tried popping the old CPU back in but again, no power at all. My motherboard was an ASROCK H77 Pro4/MVP and I had 8-9 drives of various capacities (4tb parity, 2x4tb, 3x2tb, and 2x1tb) with a 500gb cache drive. I used it primarily for Plex and sabnzb and it served my purposes just fine. At this stage I'm inclined to start from scratch maybe re-using at least the 4tb drives though after the lightning strike I don't know how trustworthy they'd be (if they still work at all). I hadn't planned on starting over and don't have much of a budget, but at this stage I don't think I can afford to get all of the modern bells and whistles. My gaming rig, which is long overdue for an upgrade itself is an i74490k but it too was exposed to the lightning (though it seems to be operating normally at the moment). I'd love some recommendations for moving forward. Any and all advice would be appreciated.

So I was able to get Sonarr to work properly by following the instructions on Q26 of the recommended post and adding my local server to the ignored addresses field in Sonarr. So far so good. Unfortunately I've been procrastinating in my move from couchpotato to Radarr. In the settings for couchpotato, there doesn't seem to be an "ignored addresses" field. Am I overlooking something in the couchpotato UI? Or is there some other way to make couchpotato work properly. Thanks

Thank you. Figured it out right before you posted. I guess I should bookmark this to see when it gets fixed.

How did you revert?!

Still not working for me. Are you using RSA4096? Or are you using RSA2048?