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

So, no dice. I followed those instructions and applied the fix to all my drives. I tried swapping the cables around....but the SAME drive disabled. I bought new cable......but the SAME drive disabled. I ran SMART.......passed. I ran BTRFS scrub....passed. So I now have had 3 more instances of the SAME drive disabling. In my anger/stress, i forgot to get diagnostics the 1st and 2nd time. But i have diags from this morning. I have now taken the cables, and the HBA out of the equation. I have found the drive to be in working order.....according to the self tests. At this point Im not buying a new drive, i've spent too much on this recently. I am currently emptying the disk, and going to just remove it from the array. Unless anyone has any ideas? My theory is with the cascade of issues, i've been dealing with recently, i think the drive is just buggered. It doesn't like coming back up from sleep, fails, gets disconnected, with an almost predictable routine. Its not even a year old! hal-9000-diagnostics-20250221-0925_disabled-drive.zip

This is the first time i'm seeing this. I will go through and try these tweaks tomor. Fingers crossed this will fix it

Hello guys, I've been on a journey these past few months.....See my previous post So over the past few months i have done a lot. I recently replaced 6x4TB drives with 3x14TB. My thought was that i had just far far too many drives connected. (8 port HBA, 4 port SATA pci card, and 2 into the mobo. Now I am running with 2 cache plugged directly into the mobo, and 8 drives connected via the HBA: 16 parity ------------- Mobo 16 parity ------------- Mobo 14 ---------- HBA ---- Mobo 14 ---------- HBA ---- Mobo 14 ---------- HBA ---- Mobo 6 ---------- HBA ---- Mobo < --- Current errors 6 ---------- HBA ---- Mobo < --- Previous errors before drives swap 16 ---------- HBA ---- Mobo 16 ---------- HBA ---- Mobo Cache ---------m.2----- Mobo Cache2 --------m.2----- Mobo Download ----- HBA ---- Mobo This morning i woke up with yet another disabled device. But this specific drive has NEVER given me errors. Overnight, the NAS was not doing anything special, nothing heavy, just its usual BTRFS background, and maybe download an episode or 2. As per usual, by simply explaing the problem, my 'desk ducky' has given me an answer I think its time to replace the HBA? or maybe just start with the cables. Any help understanding my issues is greatly appreciated hal-9000-diagnostics-20250215-0951.zip

Well, i've been looking at it, and i can see whats going wrong....my cache is filling up due to TDARR, but everything was working fine until i got the new mover version. I think my understanding of it is just plain wrong. I have removed it, and im going to stick with the built in for a while. I dont know why theres no parity disks showing. I deffinately have 2 x 16TB, but they are were listed as unassigned when i got home. Now they will need to be rebuilt yet again. Im also going to add a 'scratch disk' ssd, and dump all the downloads, tmp, etc on there.

OK, so in my small panic i forgot to read anything......but i now see that it happened again to me. So now i think i need to re-re-build the parity, but REMOVE the cache plugin, and see what happens to me

Hi, Im back again. This time with more confusion..... I got everything rebuilt, this morning i restarted all my dockers, then about an hour ago, i get a notification telling me BOTH my parity drives have disabled. Both the parity drives are plugged into the mobo, but i do have 2 drioves plugged into a pci-e 4 port sata extender... I think its time to swap out some drives and lose a few sata conections....im going to try get down to 8 drives, so im not using the sata extension Any help/advice is much appreciatied. Regards hal-9000-diagnostics-20250123-1538_after_rebuild.zip

I have new cables arriving today, and I might take the opportunity to give the NAS a thorough outdoor dusting 😁 So, if I follow https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself but you say I can rebuild BOTH drives simultaneously? Thank you for your help

There you are hal-9000-diagnostics-20250120-1957-Array_Started.zip

So for a bit of context, I've been hunting down some problems the past few months, and found my issue to be the Mover script plugin thingy. The old one. (I found out there was a new one, simply by accident.) This past few weeks i have been having a new issue. My understanding and configuration of the new mover script plugin, was flawd. So I have had to deal with share cache full problems. I have now reset the plugin, and im not doing any of the fancy bits, just hourly scan and move. My problem is when the cache fills up, the dockers crash out, the appdata gets corrupted, and i cant restore from backup until i have the array up and running again. Which has caused some issues... As you can see.....this is not ideal. I know the cache drive filled up, the log file reached max, which caused the Dockers to bork. So i need to restore that backup again. Then somehow one of the Parity AND a Drive had thousands of Array Errors, and ended up Disabled. My best guess for what happened is bad SATA cables? Both of these drives, and the 2nd parity are all plugged into the mobo, the others are all on my HBA. Obviously I have now shutdown the system, and will wait for the new cables tomor, then give everything a re-seat and maybe a dusting My question is 2 fold; a - WTF happened? b - What do i do next? I have this - https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself But Do i start with the borked Parity or the Drive? Any help and understanding WTF happened here would be very much appreciated Regards hal-9000-diagnostics-20250120-1354_Before reboot.zip hal-9000-diagnostics-20250120-1657_After_reboot.zip

An external would make a few things easier. 4tb drives have now been emptied. Physically swapped. Started the array, made a new config without them. They were disk 3/4 just shuffled things up so my new 16tb will be at the bottom, and then everything will still be in size order, and my mind can be happy. Ok! The 2 new ones are in pre-clear, there is a parity-sync happening too. They'll both take about a day more to complete. Then I can just add the new parity_2 and the extra 16tb to the array. I'm going to let it do whatever it wants in regards to parity checks. Not gonna skip any