7hr08ik

All appears good on reboot. Using latest: v580.105.08 GPU is loaded after unlocking array. nvidia-persistenced is in my GO file.

No VMs on my side at all. I will reinstall the latest driver and check now.

Hi just wanted to add my two cents to the driver dropping GPU error. So i have a 1660Ti. Updated to 7.2.0 yesterday. Today i realised my GPU was no longer being found by the plugin. I figured it was a new driver problem as the system was on v580.105.08. So i downgraded to v575.64.05 and rebooted. Before unlocking the array, the plugin showed the driver, gave my the ID and everything. Unlocked the array, and teh GPU was gone. Logs showed this, reepeated; Nov 5 22:04:23 Hal-9000 kernel: NVRM: GPU 0000:08:00.0: RmInitAdapter failed! (0x22:0x51:884) Nov 5 22:04:23 Hal-9000 kernel: NVRM: GPU 0000:08:00.0: rm_init_adapter failed, device minor number 0 i ran; nvidia-persistenced and the GPU reappeared. I have just added it to my GO file. I have not rebooted yet, just happy Tdarr is running correctly again.

Hey guys, So yeah, I woke up to this set of errors. The machine wasnt doing anything out of the ordinary. Just woke up to the errors. Grabbed the diagnostics, rebooted the machine. When i started the array, it half failed......Docker refuseed to start, and most of my shares where missing. Rebooted a 3rd time, and everything appears to be running ok. What could have caused this? Im in the UK, and we are experiencing unusual hot weather recently, but i think my temps have all been ok, albeit high. hal-9000-diagnostics-20250713-0838.zip

Oh FML, i'm going to find a dark corner and cry. On a mere whim, I decided to double check SeaChest...just in case.... Guess what?? Im a moron, both 6TB have NOT changed settings Low Current Spinup, and EPC are still enabled. 😐

All my drives are iron wolf. I have tried applying the firmware fix suggested above, but that did nothing. First 6TB started getting disabled. Swapped cable around, same drive again. New cable, same drive again. Removed the drive from the array. New failures on a different drive, in the same way, on a different SFF cable to the other drive. (2 x SFF 8087 into my HBA) So is it just something with iron wolfs cant spin up properly any more? X doubt. The drives pass SMART, they pass BTRFS scrub. They only break, early morning, several hours after any overnight things finish (cold drives) At this point, I have a couple of options; I have borken multiple drives, that are less than a year old in such a way that they only error out, one after another, in succession, in repeatable ways. My HBA is broken/overheating. (Bought a new 9300-8i, and some airflow) Unraid has changed something that is causing my drives to fail, when coming out of sleep.

Nope. No power splitters. Just PSU cables that came with it. 3 per chain.

This is the same issue i was having with the other drive i just removed from the array. Now im getting it on this drive. Ive bought a new HBA, got a 9300-8i turning up, and a mini Noctua to give it some extra airflow. Im sick of all these errors. It goes from one drive, to the next, to the next. Changed cables, PSU isnt the issue. Once the error starts on a drive, it stays on that drive, until i change a cable, then it starts all over again on a new drive.

Am i right thinking that "I/O error, dev sdd, sector 7888116504" is outside the bounds of the 6TB? Isn't 7888116504 > 6TB?

OK, I REALLY need some help. So, I cleared out offending 6TB drive (WVY043GB). I removed the drive from the array. Made a new config, and set off a parity rebuild. Woke up this morning to ANOTHER bloody drive gave me 24,235 read errors! This is a different drive. Another 6TB, but now showing as Disk4 in the new config. My only choice now is the HBA. It cant be anything else. Does anyone have any recommendations for a new one? hal-9000-diagnostics-20250223-0913.zip

And now....in the middle of the parity rebuild.....the entire system just locked up. Can't even ssh in

So now, i need to wait for the parity sync to finish, empty the drive, and im taking it out. The whine was not there when i started the array without Disk4 (to register the disk missing) Stopped the array Re-added Disk4, and Started the array with parity-sync.....whine.

As I was typing my reply (below). I heard it.....not the clicking....the short repeated 'duh duh DUH....duh duh DUH' little whine. I think we have it....the answer! I have just re-enabled the drive......again....and I have set Spin Down Delay == Never. From my perspective its neither of those. I just dont get it. Maybe the motor is sluggish or something? Either way, this is my last attempt. I've had more than a few system hangs, read errors, cache filling up, just too many problems recently. I've managed to get things sorted, but my last issue is this one drive. It hates me. Maybe it got damaged during one of the colossal If i get any more errors, i think im just going to drop the drive.

Its worth a try. My only other option, is remove/replace

Hi, I re-enabled the drive following THIS