Herbiewalker

I had to order different SSDs but after installing them they popped right up in the interface.

Tried a couple times and no luck with that either

bump

I have tried another plugin with the fans but it wouldnt start since the json file has to be configured, otherwise no luck.

Howdy, I just setup my second unraid server to test some things out but this setup is different since I am using an old Dell R420 I had laying around instead of building the server myself. I have a couple of issues I can see (and maybe some I don’t) that I was wondering if anyone had some experience with. 1. The first one is the Hard drives are not coming though correctly. For this server it has a H310 mini that I flashed to LSI IT firmware using this guild (https://fohdeesha.com/docs/perc.html) This flash allowed me to see the four 2.5” WD Blue 1TB spinner drives but I still don’t see the 4 WD Gold SSDs I have plugged in. Also, On the front panel of the R420 I can see the lights only for the WD Gold SSDs lit up, but the LED lights are not on for the WD Blue spinner drives for some reason. When I go into the iDRAC7, it shows there are no physical disks in the system. I think this is because of flashing the H310 to LSI mode but not sure…. I am not sure why the 4 WD Gold SSDs are not getting passed through, but some ideas would be great! 2. The second problem is the fan speeds. My other UNRAID server seems to take care of the fan speeds automatically but the R420 just seems to set the fans to max and won’t spin them down to a normal level. I eventually had to SSH into the iDRAC and run this command to get the fans to spin down: racadm set system.thermalsettings.ThirdPartyPCIFanResponse 1 This made it more tolerable to be around but doesn’t seem like a permanent fix since the fans are now set to the below setting. Other things of note, I installed a bunch of plugins to try and get started but couldn’t get anything configured that seemed to work for the fans or the SSDs. I have also attached the diagnostics, please let me know if you need other information. Any help would be great! Thanks dragonmount-diagnostics-20230125-1708.zip

Anyone know what these warnings mean?? Should I be worried about them? 2022-09-27 14:20:07.807171 [info] Host is running unRAID 2022-09-27 14:20:07.891166 [info] System information Linux TwoRivers 5.15.46-Unraid #1 SMP Fri Jun 10 11:08:41 PDT 2022 x86_64 GNU/Linux 2022-09-27 14:20:07.971460 [info] OS_ARCH defined as 'x86-64' 2022-09-27 14:20:08.052278 [info] PUID defined as '99' 2022-09-27 14:20:11.346467 [info] PGID defined as '100' 2022-09-27 14:20:14.628101 [info] UMASK defined as '000' 2022-09-27 14:20:14.683779 [info] Permissions already set for '/config' 2022-09-27 14:20:14.761082 [info] Deleting files in /tmp (non recursive)... 2022-09-27 14:20:14.848771 [info] TRANS_DIR defined as '/transcode' 2022-09-27 14:20:14.985667 [info] Starting Supervisor... 2022-09-27 14:20:19,309 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2022-09-27 14:20:19,310 INFO Set uid to user 0 succeeded 2022-09-27 14:20:19,325 INFO supervisord started with pid 7 2022-09-27 14:20:20,329 INFO spawned: 'plexmediaserver' with pid 71 2022-09-27 14:20:20,330 INFO reaped unknown pid 8 (exit status 0) 2022-09-27 14:20:21,331 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-09-27 14:25:16,625 WARN received SIGTERM indicating exit request 2022-09-27 14:25:16,625 DEBG killing plexmediaserver (pid 71) with signal SIGTERM 2022-09-27 14:25:16,626 INFO waiting for plexmediaserver to die 2022-09-27 14:25:19,629 INFO waiting for plexmediaserver to die 2022-09-27 14:25:22,632 INFO waiting for plexmediaserver to die 2022-09-27 14:25:25,635 INFO waiting for plexmediaserver to die 2022-09-27 14:25:26,636 WARN killing 'plexmediaserver' (71) with SIGKILL 2022-09-27 14:25:26,636 DEBG killing plexmediaserver (pid 71) with signal SIGKILL Created by... supervisord.log

Hello, I am looking to do a fresh build on unraid and dont want to lose my poster art, collections, and config settings. I would like the Plex container to be as new as possible so what databases should I save to keep those few things? Thanks

Hey can anyone double check my radarr settings. I cannot connect to any of my indexers on radarr for some reason. I checked my indexer accounts and api keys which are good. I can ping and traceroute to the indexer sites from the console of the docker container, which is proxied through SABnzbd. I can also run a test from SABnzbd to usenet servers just fine, but my darr dockers just wont connect to the indexers.... The last time something was passed to SABnzbd for download was over a day ago. I have been looking through the logs and see errors but dont really see anything that I understand to make changes on. Is there any other info I should attach?? radarr.txt supervisord.log

I completed the uninstall and reinstall like you laid out here and I can see one of the two GPUs in the Nvidia Driver plugin again (the other GPU is in pass-through to a VM so not sure if it should show up here). I have the server diag from before the change as well if your interested. Let me know if you want the one after and I can upload it too. tworivers-diagnostics-20220910-1756.zip

I was unable to start my plex container (I got an bad parameter error which I think was the nvidia card not being seen by the system so the nvidia setting wasn't allowing it to start). I took those options out and now can start the container. I cannot open the webpage though, so seeing that I am getting an error in my plex logs I restored my appdata from backup but that did not fix the issue. Any ideas on how to fix this issue?? Here is the plex log error which mentions a database but I don't know how to fix that or would the binhex FAQ (Q5. So i see from Q4 that i do have Plex database corruption, how can i attempt to fix this?.) work to fix a malformed disk image? Error: Unable to set up server: sqlite3_statement_backend::loadOne: database disk image is malformed (N4soci10soci_errorE) 2022-09-10 16:36:49,527 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23168105593008 for <Subprocess at 23168106022176 with name plexmediaserver in state RUNNING> (stdout)> 2022-09-10 16:36:49,527 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23168106027696 for <Subprocess at 23168106022176 with name plexmediaserver in state RUNNING> (stderr)> 2022-09-10 16:36:49,528 INFO exited: plexmediaserver (exit status 255; not expected) 2022-09-10 16:36:49,528 DEBG received SIGCHLD indicating a child quit 2022-09-10 16:36:50,532 INFO spawned: 'plexmediaserver' with pid 1597 2022-09-10 16:36:51,535 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-09-10 16:36:53,478 DEBG 'plexmediaserver' stdout output: Error: Unable to set up server: sqlite3_statement_backend::loadOne: database disk image is malformed (N4soci10soci_errorE) 2022-09-10 16:36:53,485 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23168105594112 for <Subprocess at 23168106022176 with name plexmediaserver in state RUNNING> (stdout)> 2022-09-10 16:36:53,486 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23168106027408 for <Subprocess at 23168106022176 with name plexmediaserver in state RUNNING> (stderr)> 2022-09-10 16:36:53,486 INFO exited: plexmediaserver (exit status 255; not expected) 2022-09-10 16:36:53,487 DEBG received SIGCHLD indicating a child quit 2022-09-10 16:36:54,490 INFO spawned: 'plexmediaserver' with pid 1609 2022-09-10 16:36:55,493 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-09-10 16:36:57,426 DEBG 'plexmediaserver' stdout output: Error: Unable to set up server: sqlite3_statement_backend::loadOne: database disk image is malformed (N4soci10soci_errorE)

For the passthrough is it still a thing that AMD is harder to work with for a gaming VM in unraid or is threadripper easy to passthrough?? What kinds of GPUs did you slot in the board or plan on slotting?

Nice bit of work there! I am about to add a second unraid server to my setup as well. Did you have any problems resourcing what you wanted for your 2022 build for a price you wanted to pay?

My Unraid USB Flash died over the weekend and thanks to MyServers it was a breeze to get the new USB up and running Thanks Unraid/MeSyerver team!

Do you have an option on your router to flush the DNS cache? If not then you might need a restart on the router to reset the old DNS settings so it picks up the new static IP. It looks like you are pinging your server name from a windows box which could also have a old DNS cache which you can reset with the command 'ipconfig /flushdns' and reset with 'ipconfig /registerdns' this should clear out any old DNS settings on the windows box and pull fresh DNS from the DNS server (router). If the problem still persists after those tips then I would go with a setting needs configured or turned off in the router to get DNS working. Another option is to skip using your router as the DNS in the server settings and point straight to a different DNS like cloudflare, google, or quad 9. I have also seen some setups point to a PieHole for DNS....

There might be a docker for it, I assume you have check the community apps to see what's out there? I am not sure about the Unraid OS itself having that capability though.

What is he static IP on your server? 192.168.0.16?? What is the subnet/gateway from your router for your network to make sure everything is talking correctly? Also I think DNS rebranding is an option in your router you need to turn off to be able to setup the SSL certs.

I am glad WD did help out. I since I had bought the drive for about $13.5 a TB I dont want to pay current prices if I can help it. I do plan to keep all the drive cases from now on tho....

It was I am pretty pleased with WD!

I have just one UPS running right now. The other one needs new batteries, just another project for the list of things to complete

Well looks like I might have to get on that level! I know every time a thunderstorm would blow through and threaten the electricity, the pucker factor was real.

So, it all started one day at the end of May when I noticed that my 14 TB parity drive was no longer part of the array…... Of course, I immediately freak out and start clicking like mad to make sure everything else is working and I haven’t lost any data, which thankfully it seemed everything was ok, and it was just the parity drive. I pull the drive and check the tape on the pins to make sure it still covering the pins and I even re-tape it to make sure there isn’t an issue with that. Still nothing! Well, I pull the drive out of the server again and connect it back up to a USB connector and power it up that way. When plugged into my windows laptop it doesn’t pop up at all as a USB device. I used the Disk Manager, Diskpart, and finally moved it over to a Linux box to see if I could get anything off that system. Needless to say, nothing I tried had any effect or was able to read the drive. To this day I am still not sure what is the matter with that drive but if anyone is interested, I attached some diagnostics to this post that are a before after kind of thing. So on to the next idea! The drive was only about 8 months old so I guess RMA was the next thing to try especially since a new 14TB drive costs more than my whole build now…... Ahh the RMA process is so special *insert sarcasm*. I go to the WD site and start the process and right off the bat I get a sour taste about how this process is going to happen. I ended up selecting shipping through WD and inputting my info to buy the shipping label. I get the confirmation and wait for the email. One day, two days, and on the third day I log back in to see what’s going on with my RMA. Its still processing but says there is an issue with getting the label. Ok, no biggy; I start the label process over and use a different payment method. Same thing happens I check the statements and of course I see pending payment for both labels on the different cards. At this point it’s time to open up a in person chat/email with WD and figure this out. Spent two days in an email chain with them only to come to the conclusion that I can’t get a shipping label from their site. I get the correct information to ship them the drive via the last email from the RMA ticket I opened and head to the post office to send it. Ewwuhfff, finally the hard part is over! or so I think at the time. I track the package a few days later to make sure it arrives and see that is has been delivered to the WD RMA address, Ahh success! But alas an email arrives in my inbox the next day saying “Per our warranty policy: “If upon inspection of your returned Product WD suspects fraud or deems such Product to be counterfeit, WD may, in its sole discretion, confiscate such Product or take such other actions as it deems necessary.”” This was not a response I was expecting. The drive was registered to my WD account and had been there for the 8 months since I bought it. Also, I am not sure how to counterfeit a drive, but I guess it’s a scam that goes around and could even be a big deal now that Chia is driving up prices on hard drives and reducing inventory. Well, I waited a few hours before replying so I wouldn’t say anything harsh because they are just doing their job. I ended up replying with screenshots of my RMA account and registration to reiterate the drive was mine and to ask if they had run any diagnostics on the drive to determine what the issue could be. The next email I received was “Upon inspection of your returned (DRIVE-SN XXX) product, it was determined the product was altered. The drive returned is an internal bare drive only. The model returned is not a user-serviceable unit and not intended to opened. WD's limited warranty provides that, subject to the following limitations, each Product will be free from defects in material and workmanship and will conform to WD's specification for the particular Product.https://support.wdc.com/warranty/warrantypolicy.aspx?lang=en As a one-time accommodation, as well with an acceptable Proof of Purchase (POP); a replacement will be shipped to you.” So while WD RMA gave me a hard time at first they did end up replacing the drive for me, as a one time accommodation…. Well, this process took month and for that time I only had one of two parity disks in my array. It left me pretty nervous this whole time but my data made it through. The parity-Sync/Data-Rebuild is in process and will be completed in about 17 hours. Now I wonder if need to just have an extra drive on hand at all times, but I would need to wait for the prices to drop/even out before I get a drive that sits on the shelf????? What do yall think about this RMA experience and what are your stories about RMA if you have used it. Also do you keep a spare drive sitting around or just wait till a drive goes out for replacement? tworivers-diagnostics-20210528-While Bad HHD is in the server.zip tworivers-diagnostics-20210528-While Bad HHD is plugged in as USB.zip

It is using SATA and Tape. It appears to be on, it ran in that configuration and worked fine for 6 months. Just a normal server reboot is when this became noticeable.

So I did a reboot of my Unraid server today in prep for the upgrade to 6.9.X When my server booted back up my second parity disk was missing from the array (See Picture). I checked the cables and swapped the other parity disk into that slot to make sure it would still work and that one had no problems when I moved it. So the cables and LSI controller are good. I pulled the HHD out of my server and connected it to a easystore USB board and the drive is now seen in unraid but as a 3 TB drive (See Picture. I dont know what happened and could use some help. I thought the drive was just bad (its only 6 months old so I can RMA) but since it was readable via USB I am unsure again. My Attached diagnostics are while the HHD is in the server and while attached as a USB. Im not sure if that makes a difference...... Is there any other info that might be needed? tworivers-diagnostics-20210528-While HHD is plugged in as USB.zip tworivers-diagnostics-20210528-While HHD is in the server.zip

Your TV folder, I assume, is linked to a docker (like Plex, Emby) to play the files. So even if the VM you use to watch is off the docker might still be reading some files from the folder..... my 2 cents

I am looking at this same setup with a 10G NIC in a PCI slot, and the MotherBoard 1G NICs. Haven't been successful in getting all the traffic to prioritize the 10G connection.... Hopefully someone has the answer!