BeardElk

Forgot to post an update, but everything is good now! Rebuild was good, and my monthly parity check was good as well. Thanks for all the help @itimpi , @trurl and @JonathanM !!!

Thanks! Archived notifications said [DISK INVALID] on disk 2 and started to think that it might be the cause. Edit: Sec edit: I just discovered that when I re-seated my hba and all the sata cables I swapped out hba 1-4/5-8 so its 5-8/1-4. I know thats not a problem with unraid, just wanted to point it out. that i'm aware of it.

Now I just got this error : "Unraid Status: 30-04-2022 01:20 Notice [BELK] - array health report [FAIL] Array has 7 disks (including parity & cache)" Diag included. I've Got 7 disk with my dual cache (1 parity 4 data 1 cache 1 cache backup (or whatever its called). Edit: It's still rebuilding, don't know if its normal to get this error message. belk-diagnostics-20220430-0122.zip

I had a backup, but yesterday i decided to move it off site (have had it on site but what good does that do in case of fire), and for some reason I felt it would be easier to just wipe it clean and move it, rather then just move it and go through the config to get it working...... Its a synology nas and the setup was hell. Dont hate me please.

I´m also pretty sure I caused it myself. I have mounted a 40mm fan on my hba, and 2 days ago I wanted to make sure the fan were still spinning, so I "shoved" my hand into the case and sure enough, the fan was spinning. In the process I must have shifted the hba or the cables to the hba, causing the write error. I do have notifications set up, but for some reason (i've noticed stuff like this before) it most likely got reset when I upgraded to rc5. The config was right, just the options to notify were un checked, so i did not get a notification...... I've learned my leason, never shove your hand in a server thats powered on, and double check notifications after upgrade!!!

Thank you for your answer! I´ve read up on this stuff tonight so I'm sure I'll get ny data back, but I just didn't want to fuck something up by starting a rebuild, to then learn that you (awesome) guys could have figure out why it got disabled in the first place before I started the rebuild, etc etc.

Thanks! I didn't get that! But I'll follow the link you gave me and rebuild the drive, and if(and hopefully not when) it happens again, I'll be sure to grab diag BEFORE i reboot my server. As I said, I freaked out and thought a reboot might fix it. Thanks any way! I now feel like I can move forward and rebuild the drive! I didn't wanna fuck up again (like when I rebooted) so I kinda wanted confirmation that I could start to rebuild the drive and not fuck anything else up.

Yes, thats why I said thanks! I tried to explain why I haven't been able to find it when I searched for it. But if you turn down your passive aggressiveness and read my whole post, I Said that I'm Still Unsure What Made Unraid Turn My Disk Disabled, So I Would Appreciate If Someone Could Help Me????? I didnt ask for someone to roast me, I just asked for help.

I've tried that, but I'm not sure what to search for. I've tried re-enable disk, that gave nothing. English is a second language for me and on things like this I just draw blanks. Thanks btw!! Tho I'm still not sure what made unraid turn my disk disabled, so if someone could help, it would be much appreciated!!!!

Yeah I know I fucked up there. I freaked out when I saw that disk2 was disabled and thought a reboot might fix it. belk-diagnostics-20220429-2331.zip

I've never had to rebuild a drive so I got no clue on how to do it. Every "guide" I can find links to something on unraid forums that's no longer accessible. I've checked the file system on the drive with -nv, all good. Now what?!

I get this notification when I restart my array: "Unraid array errors: 29-04-2022 22:39 Notice [] - array turned good Array has 0 disks with read errors" Same disk is still disabled tho.

Is it something with rc5?? I wanna start rebuild, but no point doin a rebuild on rc5 if its just gonna give me the same error again, best downgrade in that case.

Titles says it all, updated to rc5 when it was released, yesterday everything was fine, today I got a disabled disk and unsure of Why. Smart looks good to me, but I´m no expert. Recently installed a lsi 9211-8i hba, flashed to it. I´ve never had a problem before installing the hba, but i don't know if its got something to do with it. Diag included. belk-diagnostics-20220429-2248.zip

If I run a manual parity sync, and then start a movie on plex, they collectivly slow down to 30-40mb. Is this a result of the 9211-8i? Bc if I run a parity sync, all my drives are reporting the same reads. And If I try to transfer a file, it fucking sucks. I had better transfer speed when the drives were connected to the motherboard. Do I need du Pay up and Shut up and get a 3008 HBA?

As the title says, I get somewhat "slow" (60-70MB/s) transfer speeds with my drives that existed before I got my HBA card. Thats both drive to drive, and over network to another pc. The new hdd thats never been connected to anything besides the hba card performe as expected. Its my 4 drives thats been connected via mb sata thats "under performing". I don´t know if this is normal or not, I just cant understand or see why the speed should differ. I can get excpected transfer speed (107-112MB/s) both over network and drive to drive if nothing else is using any of the drives (ie = unraid with all dockers stopped, all vms stopped). But as soon as I start plex or any other docker that has/uses files on those drives, the speed gets halved. I´ve tried the HBA card in x16/x8/x4 and its all the same. Is this to be expected or is something wrong? (Previously I had all my drives connected directly to my mb, but when I got my HBA I switched them all (and added 1 new drive) to my HBA) (HBA is an LSI 9211-8i (flashed by me) to P20 IT ((2118it.bin/mptsas2.rom/x64sas2)) (Worth mentioning is that I Cannot get the "avago setup - press crtl c" to ever show up on this mb. I flashed it on another uefi pc that was more accessible, enabling csm to get the card to show up and then flashing it. With this mb I haven´t gotten the card to show up even with csm/legacy boot) And I´ve checked that the card Is flashed to IT on that avago settings page tho, nvram and bios and rom are all correct)

THANK YOU! Had no idea that plug-in even existed!

On my gigabyte board I had to add "modprobe it87 force_id=0x8628" to my go file, so if you try to just type that in the terminal and see if your fans show up, thats all you need to do. Might be a diffrent ID for you, what does sensors-detect show?

Yes, I´ve ran sensors-detect! But i´m gonna try the NCT6687 plug-in!

Yeah, but I got an almost to good to be true deal on the board so I can live with this. Its just a "nice to have" to get it working.

Did not work. All I get is cpu temps and mb temps, no pwm controler.

The problem has something to do with that my MSI board uses nct6687d which is supposedly added to nct6683, but something with patches and something else fucks something up. It should be working but is not and I´m not 100% on the rest. I´ve tried modprobe-ing every possible thing I could think of but nothing works, both with (force_id=0xa20) and without. If anyone got any ideas im all ears!

So i just changed motherboard from a gigabyte z590 to a msi z590 and now i cant get any info on fanspeed etc. On my gigabyte board I had to include "modprobe it87 force_id=0x8628" in my go file for my fans to show up, but i got no clue on what I´m doing and I´ve tried googling to find some kind of help but nothing. If anyone could help me with this I would be forever grateful! I´ve run sensors-detect and the only thing that gave me was "HWMON_MODULES="coretemp nct6683" "

Never mind! I got it! If anyone in the future run into the same problem as I did, stop the docker, add your 16 digit mullvad login to both your docker vpnusername and vpnpassword, then add whatever wireguard server you want to connect to in "\\yourserver\appdata\binhex-qbittorrentvpn\wireguard" and everything should work! At least it did for me!

Just a quick question, I´ve just switched from azirevpn to mullvad, what do I set as username/password within the docker? Nothing? I´ve tried using my # identifier for just username, and just password, and both, but nothing works. And yes, I´ve switched wg0 to the wg server I wanna connect to! And thank you @binhex for all your work! You are a fucking legend!!