2Piececombo

I rebooted my server and watched the boot process and noticed some odd things right at the end before the display went black. I found this reddit post and one of the suggestions was to install the intel gpu top plugin. I remembered I already has it installed, so I removed it and rebooted to see if that would make any difference... nope. The OP of that thread said he solved his problem by "removing the nomodeset commands in my /boot/syslinux/syslinux.cfg file" so I checked there but it looks completely normal. default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label unRAID OS kernel /bzimage append initrd=/bzroot label unRAID OS GUI Mode menu default kernel /bzimage append initrd=/bzroot,/bzroot-gui label unRAID OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label unRAID OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest Since /dri was missing, I figured I might as well just create it and see if things sorted themselves out. The error about dev/dri went away, but still no login page, just a blank screen. No clue what to do next. Included diags in case that helps. cheers diagnostics-20220623-0245.zip

I recently added a GPU (P600) to one of my unraid servers for use with plex. was getting nothing out of the onboard graphics so I plugged a monitor into the gpu and booted into BIOS and forced it to use the igpu. saved/rebooted, now im getting output from the onboard, until unraid boots. I get the screen where you select gui/nongui/etc, and the whole boot process, but where it would normally show a login page, its just a blank screen. The server is running and can still be accesses via webui. Is there something else I need to modify to get unraid to output via onboard post boot?

What is your qbit set to do? Pause or remove?

How do you properly configure sonarr and a bittorrent client to allow for Sonarr to remove a torrent once it's hit a desired seed ratio? There are settings in both qbittorrent and sonarr to control this behavior and Im not sure which combination of setting to use to make it work properly. In sonarr, seed ratio is set to 1, seed time is set to 1440 minute for all indexers. In qbittorrent, seed ratio is set to 1, seed time is set to 1440 (both tick boxes checked) and is set to pause torrents. I remember once upon a time I had this working, and IIRC qbit needs to be set to pause. Is this not the case? I have torrents that have hit seed ration of 85, they appear to be ignoring ALL seed settings, both from sonarr and qbit.

ive got openvpn setup on my firewall (pfsense) and use the openvpn app on my phone/laptop to connect. Also I found the failed logins. Like an idiot I was looking at the wrong month. My roommate has some antminers running in our garage and the IPs from the failed login attempts match those IPs. I will address this immediately.

On two separate days recently, there were many failed login attempts, 34 and 19. I've checked syslog and im not seeing any records of failed logins on those days. I cant be sure, but it could have been me trying to access my servers smb hare remotely via VPN on my phone. I used an app called Solid Explorer. Sometimes it connects fine, sometimes not. I do remember trying it a bunch of times, possibly on one of those days, and it never connecting. I ended up deleting the saved connection from the app and re-creating it, which did let me connect. My question is, where should I be looking to find details about these failed logins since syslog shows nothing. The exact message I get from Fix Common problems is: Cheers

Im using nginx proxy manager hosted within my own network. But I have to configure the proxy host for sonarr in NPM as http, not https, thus leaving the traffic unencrypted, unless my understanding is incorrect. Ive got several other services behind NPM and they all work fine over https. So I guess Im a little confused about the http/https setting in NPM, then. If I set it to https, I am no longer able to access it. But if I leave it as http, it loads fine and still says the connection is secure. I guess just refers to its connection on the local network? Ideally I would prefer this to be encrypted connection as well, so I could access it via it's local ip, though this is not the end of the world if it wont work.

Has anyone been able to get SSL to work on sonarr? I've seen several people post here about it and they've all gone ignored. I enable SSL and restart, but it does nothing. the config file shows SSL is enabled, but it just doesn't take effect. I notice in Radarr if you enable SSL if gives you a place to enter a path to a file, but sonarr does not do this. I want to make sonarr accessible via the web (behind cloudflare and a reverse proxy) for another remote user to be able to help manage my library but I dont want to do it without SSL working

I cannot get Kutt to work. The GUI wont load, just get a 502 error. The setup seems straightforward enough, so im not sure what else to try.

Something weird has happened today. I've installed nextcloud on 2 different unraid servers in the past, and while neither has been particularly fast, my latest install on a 3rd server is slower than ever. It was actually the fastest, at first. Let me explain.. The server in question has 2 cache pools, one consisting of 2 x 256 SSDs (named 'cache') and the other is 2x16GB optane nvmes (named syspool). Initially, I had appdata located on the syspool and docker.img was located on cache. This configuration was the fastest I've seen nextcloud perform. A side-by-side comparison to my other install showed that this one was faster (only by a second or two) but still, the most responsive I've ever seen the GUI. I wanted to put the docker.img on the optane pool as well, thinking this might further improve performance. Rather than worry about trying to move things around (fresh server so no important data on it) I deleted the dockers/docker.img/appdata. Stopped docker service, and created a new docker.img on the optane pool. I then installed mariadb and nextcloud again, but this time performance was MUCH worse. Slower than my other servers by several seconds. Takes 2-3 seconds longer to switch from one page to another, and then a few more to actually load the content of the page (files/photos/dashboard/etc) I did more testing, deleting everything and starting fresh each time to ensure a clean slate. I tried using a directory instead of btrfs for the docker img, no change in speed. I put everything back to how it was initially (when it was running great) still no change. I don't understand how it could run so great at first, and now run like total crap. Ive seen people suggest redis/memcaching, but im not even concerned with file transfer performance right now, I just want the GUI to perform at least as good as my other servers do. specs for this server are 2 x X5670 cpus and 24GB ram.

Ive recently set up a new server (dual x5687, 24gb RAM) and have issues with nextcloud performance. Ive got 2 cache pools in my server. first is 2x256gb m.2 sata ssds (called 'cache'), the other are 2x16GB optane drives (called syspool) - both in raid 1 for redundancy. my docker img lived on the cache poo, and i put app data on the optane pool thinking it might make nextcloud a bit faster. and at first, it was! I have another very simialr server with nextcloud running, and the performance on the new server was just slightly faster than the old server. I then decided I wanted to try putting the docker img on the optane drives too, just to see what sort of difference that made. I deleted all the dockers/img/appdata to start with a clean slate, stopped docker service, and changed from btrfs img to directory (due to limited space on the optanes) and mapped it accordingly. I set up mariadb and nextcloud again, and suddenly the performance was slow as hell. easily 2-3 times slower than it was before. I again deleted everything and changed from directory to btrfs.img again to see if that made a difference (leaving it on the optane pool) but still just as slow. So again I deleted everything and set it back to how I originally had it. but still, its horribly slow. I then decided to try out postgressql as per this thread, but that made absolutely zero difference. i have no idea why it's suddenly so slow when before it was so fast. But nothing I do seems to work. Has anyone had any luck tracking down performance issues with nextcloud?

Set up a new unraid server today, and once again ran into this issue. Weird thing for me is that it's not a matter of which USB drive you use, or which port you plug into, its the computer running the creator tool. My main PC simply WILL NOT run through the tool successfully, and each previous time I've used another computer to do it. Found the video that someone posted about reformatting/renaming the drive mid-flash and it worked. Can't believe that after this many years of this being a problem, the creators of an entire operating system have not found a fix for this? Kinda blows me away that you can make an amazing server OS, but not a tool that installs it properly? lol Anyway the formatting option does work. Never bothered with the manual way, because why would I when theres a tool to do it for me

A lot of WD drives wont spin up (mine are white label red drives shucked from WD easy store/elements) when a consumer PSU, so you have to cover the 3.3v line. (my old setup was a 2U case/PSU, and the drives plugged into a backplane that was powered via molex. In my new case (fractal XL) im using a standard ATX supply so I had to perform this 'mod'. Yes, Kaptop tape would be ideal, but I didn't have any handy and electric tape has been used many times without issue, so it is what it is I guess.

I was so frustrated I pushed it aside for a week because I couldn't stand to look at it, but came back feeling optimistic that I could solve this. Since the problem has to either be the OS or RAM (since it's the ONLY part that hasnt been swapped out) I took out 6 of the 18 dimms (those 6 are IBM RAM, the rest samsung) which caused the server to boot noticeably faster, and things seemed to be normal for several days, I was even able to complete a rebuild without the server shutting down halfway through. I still lost 1 disk (8TB) worth of data somehow, but it was almost entirely media which can be re-downloaded so oh well I guess... At this point I was feeling pretty good and the problem seemed to be gon! But then tonight, out of nowhere, I noticed the server was once again off. I turned it back on and let it start doing a parity check. It's shut off twice more since then. Im truly at a loss now. This is a different motherboard, with different CPUs, a different PSU, and RAM that tested without error for almost 24 hours straight. There's really no rhyme or reason to the shutdowns. It's sat in Windows for well over a day with no problem. It's only ever shut down while booted into unraid. I realize there's a small chance it could still be a bad stick of RAM, but holy hell testing out 18 dimms is not an easy task.. Especially when it can go days on end without problems. There's no good way to approach this that isn't going to take weeks/months. I've already lost 8tb of data from the crashes/drives going offline/attempted parity syncs and rebuilds. I'm not even posting asking for help anymore, I guess Im just venting at this point. I dunno what to do anymore, aside from backing up what data I can and literally wiping the thing clean and starting fresh. If I do that, I'd want to re-flash the USB that unraid lives on, but if I understand it correctly you can't really re-use the USB because it burns the GUID. Maybe I'm misunderstanding this, but I was under the assumption that once you use the USB creator tool, you cant ruin it again on the same drive.

UPDATE I ordered a replacement board which arrived a few days ago. To solve my 2U psu woes, I decided to migrate to a new case so I could use a standard ATX and save a lot of money. I grabbed an 850w gold from EVGA and the fractal XL R2. Had to do the 3.3v electric tape trick on my HDDs since im no longer using a server grade PSU, but it went fine and upon first boot all drives were showing up, and none seemed to be disappearing. The array was not started, and I left it sitting like this for over 12 hours to see if she was stable. Everything seemed fine so I started the array and let the rebuild begin and went to sleep. I didnt check on it til about noon the following day when I remoted in from work and was not able to access the server. When I got home I booted it back up and let it just sit - no array started, and it stayed on for multiple days no problem. I decided to try to start the array one last time, and it shut off again within an hour. At this point the only 3 suspects I have left are a. RAM. I have done a nearly 24 hour memtest with no errors, it only stopped when the server randomly powered off. This test was done several months ago, when I first started having random shut downs. I've never SEEN bad ram cause a server to go offline in such a manner (not even IPMI was accessible) but I suppose anything is possible? It's pretty difficult to test out this ram, though. I've got all 18 slots filled, so that would take a while. b. Unraid. I'm far too ignorant to even try and explain how unraid could be at fault here, but it has been a constant throughout all of this so it's still a suspect too me. c. the HDDs themselves. I suppose the best thing is to run extended tests on all drives one at a time and see what happens? Any thoughts or suggestions would be wonderful, Im starting to pull my hair out. Having a server offline this long really makes you appreciate high availability...

Dropped in some other CPUs, but no luck. Server will not only shut down randomly, but if left alone, turn back on randomly. I would assume my board is toast at this point, unless theres some other logical explanation for this behavior. What an adventure this has been.

Sadly the server just randomly shut down a few minutes ago. And wouldnt turn back on for several minutes. Gave it another shot, but it restarted twice in a row after severla minutes. Im confident ram is good (did a 24h memtest somewhat recently) so it's either CPU or motherboard. Luckily I have some alternate 1366b CPUs I can swap out. (higher clocks, less cores. sorta worth?) Will update once I disassemble again and swap them out. stay tuned..

Things have improved. After a good CPU repasting using the last of my NT-H1, I used a 1200w PSU that I know to be good and reconnected everything. First boot seemed normal enough, and when I got to the ui things seemed to be stable enough. No disappearing drives or other weirdness. Starting the array left me with a disk 5 showing is good, but disk 1 missing/emulated. GIven that no other disks are showing up as unmountable I guess I can rebuild that disk? The other issue is that my 2nd pool (consisting of 2x500gb SSDs) are both showing as having no filesystem. I had previously moved appdata and VMs off my main cache drive to this second cache pool. Well, copied I guess, because all the data is still on the other cache drive. So it seems that I havent lost anything I had put on this pool, if im understanding things correctly. The other missing drive (download) was never actually formatted to begin with so it's warning can be ignored. I took diags with array stopped, then again after it started, in case that could be useful in some way. As of now it would seem it was the PSU all along. I'm just going to let it sit for a bit and watch it. I stopped all dockers to be safe. If all seems well and stable after a bit ill rebuild the missing disk, unless anyone has a better suggestion. Unfortunately I did have to talk to them two days in a row. And for once it wasn't tech support, it was the billing dept. Better or worse, I don't really know. That entire company can burn to the ground for all I care. Thanks for all the help and suggestions though, appreciate it. Huge thanks to you all. This community is why I use unraid and not something else. You're all wonderful. Accept my humble apologies for being "that guy". cheers

My second CPU wouldnt work without it I actually build PCs as part of my job, so I can confidently say all my cables are good I actually thought about the PSU extender, but sadly would not fit given how cramped my case already is If my words came off in any way as a signal of anger or frustration towards anyone trying to help I apologize. I wrote that after having spent multiple hours on the phone with centurylink. Any anger I felt at the time was merely residual from the hell that is trying to get anything done with that god awful company. Well, my test didnt include booting into linux, but rather a customized WinPE environment. Admittedly not the BEST environment to use, but I had it handy and figured I'd at least be able to observer something in disk management. I'll try a more proper test now, i've just been short on time which has made the whole situation more stressful. I will also disassemble the ol gal and test out that damn PSU. BTW, anyone selling a 700w+ 2U PSU? cheers guys

The array doesnt autostart because the disks show up as missing, but I can still use the drop-down menu and "re-assign" them, at which point unraid seems to think all is well and I can start the array, but when I do it shows 3 disks being un-mountable. Only one disk is plugged into it now. I switched back to the onboard SATA ports thinking the issue could be my HBA, but the problem didnt go away. Also I have reseated everything alread,y that was one of the first things I did once I noticed the odd behavior. I would simply try another PSU (as previously mentioned I have one PSU powering the drives, and another powering everything else) but to remove the 24 pin connector requires the cooler be taken off, but to take the cooler off requires the board be taken out of the chasis, so ive been avoiding this. But I suppose at this point I have no other choice but to do it. My main concern at this point is the drive (drive 5) continues to go online/offline over and over, regardless of what PSU is powering it or what its plugged into (HBA/SATA). And since I only observe this in unraid and nowhere else, im not confident that the "nuclear" option of dumping all data do another location and starting over from scratch will even fix it. If this was a power/motherboard/HBA/etc problem, this same thing SHOULD happen while booted into something else, but it doesnt. ONLY in unraid. What are the odds unraid is somehow the cause? Im feeling rather lost at this point, even with all the help and suggestions I feel like the main problem isnt being addressed (dont get me wrong I truly appreciate everyone here) but Im still stuck on the fact that this issue only seems to happen while booted into unraid. I mentioned previously that I could hear the drive 'restarting' or something, and upon taking the disk in question out and connecting it to another system, it doenst do that. Again, only in unraid. I will try a new PSU, might even make a new unraid USB, pull out all my current disks and throw in some spares to see if somehow my install is somehow bugged. Thanks again everyone

The ups is expected, as I've moved the server into my office away from its usual home and is no longer connected to its ups. those other issues though.. Sounds pretty bad. The psu is a 500w 80+ Gold 2U from seasonic. Im fine with replacing it, the problem is finding another 2U. They seem to not exist right now, at least anything over 500w. I'd really like to go for a 800w but I just can't find them. So maybe time to change cases as well.. All that aside, I still want to have a better idea of what to do about the array. Once im no longer dealing with possibly failing hardware, what do I do about the disks being unmountable (but data still intact)? new config and remap the drives them rebuild parity?

I started an extended smart test, the gui said it never went past 10%, but i refreshed the page after about 30-45 mins and it says last smart test passed. Not sure if that meant the extended or not.. Not good enough not reading unraid diagnostic logs yet. With the array stopped disk 1 has a red X and says "device is disabled, contents emulated" and disk 5 shows missing. If i start the array, 3 disks show that they are unmountable. (dont remember which 3 but i dont really wanna start the array again) At this point is is possible to pick up where I left off? At one point disk 5 did a parity.. sync? im 99% sure it DIDNT say rebuild, and it went very quickly! like multiple gb/s IIRC, too fast for a rebuild. Am I able to somehow import those disks back into the array and tell unraid dont worry about it just rebuild parity as is? If so, will I then run into problems with dockers that we started temporarily while the drives were misbehaving? Also to note, i still hear one of the drive "restarting" it sounds like. But again this only seems to happen while booted into unraid. I'll continue testing this to see if I can recreate it elsewhere. In the mean time, have fun with my logs thanks for the help guys! tower-diagnostics-20210429-2253.zip

I will pull each drive out and test it manually tonight, but I have not seen any SMART warnings pop up other than a temp warning on one of the drives at one point, though I see no reason that would be related to this issue. The issue only seems to happen once the array is started, I can mount the disks just fine while the array is stopped with no issue. But once the array starts things get weird. Im considering pulling the data off all my disks and just nuking the whole thing and starting over. I really need my server up and running again sooner rather than later and I feel like im not making an progress on diagnosing the root problem here.

ive tested out PSU and HBA/cables, but the problem remains. I reverted back to the onboard sata ports and for a moment I thought everything was working okay, but as soon as the array started the problem returned, and unraid is telling me 3 disks are now unmountable. The drives all appear to still have all their data intact when mounted manually with the array stopped. I would assume doing a new config here would be fine, however im scared the disks may continue to "drop" afterwards.

Previous to this problem, I was having an issue where my server was randomly shutting down. After much time and testing I concluded my PSU was simply not enough (500w) and must have been shutting off under heavy load. My drives are powered from a backplane with 2 molex connectors (each molex powers 4 drive bays). To temporarily solve my issue while I decide what to do long term (2U PSUs are kinda rare right now) I connected the backplane to a second PSU with a jumper. This setup has worked fine for several weeks now, so I didn't immediately suspect it could be the cause, especially since there have been no more random shut downs. I suspect my issue could be my HBA (h310) or possibly the cables? The confusing thing to me is that in the BIOS the drives didnt disappear, but when I physically removed a drive the BIOS DID reflect that without a reboot, so I know it could tell if a drive was dropping offline. I guess I'll test in another OS for more conclusive results and report back. TIl then, anything in particular you recommend trying? thanks!!