Everything posted by BeardElk
-
Ram filling up (Unraid 6.10.3) (No, syslog is not enabled)
So, it was plex-docker that were filling up the ram, and I fixed it with a simple script to run every other day to just reboot plex-docker!
-
Ram filling up (Unraid 6.10.3) (No, syslog is not enabled)
Anyone?
-
Ram filling up (Unraid 6.10.3) (No, syslog is not enabled)
Yeah sorry, my head was in another thought when i typed that😅 (Im from Sweden, and Im autistic, sometimes I just "wander off" and keep typing without checking what I just wrote..)
-
Ram filling up (Unraid 6.10.3) (No, syslog is not enabled)
Here's an updated diag with a syslog over the past 6 days. I hope you guys can help me! belk-diagnostics-20220728-2214.zip syslog-192.168.1.111.log
-
Ram filling up (Unraid 6.10.3) (No, syslog is not enabled)
Memory utilization on the diag page. (edit, Dashboard, not diag, my thoughts were elsewhere when i typed that)
-
Ram filling up (Unraid 6.10.3) (No, syslog is not enabled)
Im gonna start by apologizing for the lack of information on my og post. I´ve started a syslog server now, and in a couple of days im gonna post the output of the syslog. (The indication I got for my RAM filling up, is that my RAM is filling up after I start my server. If I boot with 16gb free, I´ve got 10gb free a day later. (Im exaggerating, english is a second language for me)
-
Ram filling up (Unraid 6.10.3) (No, syslog is not enabled)
Diagnostics are attached. And why do I need to setup a syslog server? I get that I need to log as much as possible, but my main goal is to not have to reboot the server every week.
-
Ram filling up (Unraid 6.10.3) (No, syslog is not enabled)
For some unkown reason (to me at least) my ram keeps filling up to the point where I have to shut down VM:s or reboot my server. I´ve got no syslog-server running and I don´t understand why this is happening. Since I'm not fluent in logs, or even what to look for, I'm turning to you golden gentlemen's (and lady's) who have saved me so many times before. On a fresh reboot I've got between 69-72% ram utilization, but 48h later its up at 85%. Got 3 vms running and 17 dockers (normaly 19, but have still not gotten around to fix the fuckall nextcloud/Collabora thing) so they are offline. As I said, no syslog running in the background, and I really cant find what is filling up my ram over time. And before someone says it, I know I'm running kinda short on ram, and its next on my "to do/upgrade list". Diag was downloaded before I rebooted the machine. Since I got my UPS my "record" is 1 month 18 days, but had to shut down vms one after one as it filled up, and I tried solving it myself by looking through everything and googling but I lack the skills. (Fuuuuck me, I forgot to upload the diag, but here it is!) belk-diagnostics-20220719-1824.zip
-
[Support] Nginx Proxy Manager (NPM) Official
I'm kinda new to all this, and just switched over from swag bc this just looked so much easier to use. But I got on quick question, can I run npm on my unraid server, and have it redirect to other stuff on my local network? I've got a 3d printer with octoprint running on a raspberry pi on my network, and npm can see the device and everything "should" work, but I dont even get the welcome page... Just this a "page is unreachable".
-
6.10.0-rc5 Disabled disk.
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 !!!
-
6.10.0-rc5 Disabled disk.
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.
-
6.10.0-rc5 Disabled disk.
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
-
6.10.0-rc5 Disabled disk.
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.
-
6.10.0-rc5 Disabled disk.
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!!!
-
6.10.0-rc5 Disabled disk.
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.
-
6.10.0-rc5 Disabled disk.
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.
-
6.10.0-rc5 Disabled disk.
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.
-
6.10.0-rc5 Disabled disk.
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!!!!
-
6.10.0-rc5 Disabled disk.
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
-
6.10.0-rc5 Disabled disk.
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?!
-
6.10.0-rc5 Disabled disk.
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.
-
6.10.0-rc5 Disabled disk.
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.
-
6.10.0-rc5 Disabled disk.
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
-
HBA Slow transfer speed on "old/excisting" disks
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?
-
HBA Slow transfer speed on "old/excisting" disks
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)