phbigred
-
Posts
265 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by phbigred
-
-
Agreed I remembered something of why 5700 is used. However the issue remains.
-
I'm rebuilding a VM tonight for testing with the new 6.4rc with GPU passthrough due to issues with my old one and getting stuck in the UEFI shell. I'll report on GPU performance in gaming to see if it's any better for some standard benchmarks and 3dmark.
-
My webVNC isn't working either as it's trying to attach to port 5700 rather than 5900 reported by unraid as the used port. External VNC client is working fine and when trying to identify port with 5900 it still doesn't work via webui.
-
Anyone else having random freeze/reboots on 6.3.5? I can't start my VM with any passthrough. As soon as I do the unraid either reboots or completely locks up. Dockers include Plex, hdhomerun. Upon revert everything is back functioning.
-
What dockers/plugins are installed? Have you tried safe mode? Just trying to isolate if it's NAS update related or a plugin/docker or even VM related issue.
-
Toggle the switch at the top right of the screen (Where it says basic view)
-
Check your logs too while running. See if there are any reoccurring pop ups while running. Also for grins pin your CPU for plex in case that might be causing issues. Edit Docker for plex and under Advanced radio toggle look for extra parameters and add something like this...
Extra Parameters: --log-opt max-size=50m --log-opt max-file=1 --cpuset-cpus=0,1,2,3
These settings keep the log for the docker in check and assign certain processors to isolate Plex. In my case with a hexacore with SMT I'm assigning cores 0-3 out of 12 total. Helps contain the dockers so they won't eat up all resources. Can be done for all your dockers if you like. If you have more than a quad core proc, maybe don't use 0,1 as Unraid likes the first couple for itself. Also if using the plex released docker make sure if you are tight on RAM to not set transcode to /tmp as that uses RAM and can cause issues if you don't have a lot of overhead. Just my 2 cents.
-
Watch the entire video, there's other interesting stuff in there too.
*wink wink, nudge nudge* Real opportunity coming I think.
-
8 hours ago, ufopinball said:
Are you running any VMs? It might be worth setting one up. I have the ASUS Prime X370-PRO motherboard, and last I checked (albeit not recently), disabling C-States didn't actually do anything. My guess was that the BIOS setting exists, but the underlying feature was unimplemented. My system stays alive (16 days, 7 hours, 55 minutes) by virtue of having a Windows 10 VM running all the time. This keeps the processor busy enough to keep the sleep states from occurring, and thus it works around the crash issue.
Since you have the ASUS Prime B350M-A board, I am guessing that the C-States setting may not be performing any action on your board, either. You can test power consumption with the C-States enabled/disabled and see if there is a difference. Not sure how you got a week of uptime, maybe you have a VM but it's not always running?
Anyway, something to try out...
- Bill
Good point Bill I haven't seen the issue but I have a vm running 24x7.
-
Any reoccurring notifications in your logs that stand out? I edited late, mind posting what your MB model is and if you are running any overclocks? Might be a previously known or seen problem by the community.
-
3 hours ago, dkuhn said:
https://forums.lime-technology.com/topic/57294-unraid-633-crashing/
Linking my post here as I just found this thread. Having stability issues even with Global C State Control set to "disabled".
Worked for about a week then it crashed, and has been crashing every day since then.
Turn on tips and tweaks troubleshooting mode. Also post diagnostics next time it dies. Are you by chance running plex as a docker and running transcode in memory (/tmp)? Mine was crashing when I had that set so I moved it to a cache location and have been stable since. Also post what plugins and dockers you are running. Also post your MB model as there my be hints for others who have run into your problem.
-
I stand corrected this is required for initial setup. So my thought is still valid for initial configuration, dual pci-e then remove.
-
20 hours ago, dukiethecorgi said:
Hey Everyone-
For a Ryzen build that will be mostly for Plex, no video card needed, should I be looking for a B350 motherboard? I only need a single PCIe slot for a drive controller.
Also, what's the advantage of going big on memory? In my existing unRaid box, most of the 16gb always shows as cached - is this disk caching?
Remember Ryzen doesn't have an on-chip video. You'll need a video card for unraid to boot. You won't need a x370 but a dual pci-e slot B350 with a cheap video card in the first pci-e slot I believe is required to do what you want.
-
No issues on my Ryzen system.
-
Yup again it's related to the version 6 and known issues. If it is too much work revert back to 5 but understand that the 5.x branch is no longer actively supported.
-
Also make sure plex is purging deleted files. I've seen libraries very large, and up to 100GB, and have reindexed mine before from scratch. Make sure the settings for purge deleted items is set in plex settings. Otherwise move it to the array on a single disk if that's not an option.
-
Set appdata share cache to prefer to start out. If it overruns it'll spill onto the array until you get your appdata under control. You must have some apps dumping to it eating the space.
Also so check your docker image file space on the dashboard page. Is it full?
-
Nope the backup is your database with your metadata and viewing/added history. Best bet would be go into your folder and copy it. It may be relatively large (maybe a 100GB) with that much media. So copy to a basic share on your array temporarily. I recommend using docker by linuxIO or the one built by plex. Both are fairly straightforward. Once you set them up there will be a location in your appdata folder with plex that you will move your database to and then start. It should remember everything otherwise you could always rebuild the database. Depends if you want to keep the history and indexing.
-
11 minutes ago, Dazing said:
So i just add the ACS lines to that config file? Is it really that simple?
Yup or change it under advanced settings under vm manager in the settings tab. Either will work and reboot.
-
1
-
-
Yeah do what Jonathan mentioned. Recommend a new drive and process laid out above. Worst case you may be able to recover the missing data outside the array.
-
Parity is showing green which is a good sign. If you want to try you can rebuild your drive, or get a new drive. Before you do either, shut down and reseat cables on disk 1 and on motherboard. I'll have to defer to Turl or someone for a deep dive into diagnostics. Let's hold on steps right now for recovery and verify cabling. Grab one more diag and save it somewhere. Stop the array, change setting auto start array to no in settings under disk settings and shutdown and reseat cabling and turn back on. Then we hold... The disk being green balled on disk 1 makes me hesitant on a rebuild from parity right now.
-
1
-
-
What do the shares show? My guess is appdata lived on disk 1. What does MC show from putty or unraid boot to GUI? Midnight commander you'd back out to /mnt/disk1. Looks like old school dos shell. Take a peek in there.
Who knows your data data may be there but the state it was in when doing the xfs repair might need a reboot to reset the shares back. Report back on what shows in /mnt/disk1 first before going that route. Based on your info will push us one direction or rebuild of disk1.
-
1
-
-
Go to docker settings and see if you appdata location is valid first. Reason you can't see it likely is the docker.img file was corrupted or not found. Do you only have the 2 drives? If so your parity is actually a raid 1 mirror rather than just a non file system parity calculation. Whatever you do any parity rebuild until you confirm configuration with the community prior to problem. This includes drive counts. I don't want you overwriting parity/mirror data if nothing is seen on your drive.
-
1
-
-
1 hour ago, serguey bubka said:
Hi!
He needs the bios rom because he put the nvidia in the first pci-ex slot. Only if you put an AMD in the first place you don't need the rom.
Also, sometimes that's not an option because if you are trying to passthrough a graphic card to a gaming vm, you want to get the 16x lanes. In many boards, the second pci-ex 16x is only 4x.
Sérgio.
Depends on the am4 board. Typically the second pci-e 3.0 x16 when populated with a card in the first slot runs at x8 not x4 speed. I was aware he did that in the first slot. I was talking if he was planning to keep the card in the rig. Almost all X370 and some B350 have this option with 2 pci-e cards. I have yet to see a card for gaming require x16 pci-e 3.0 throughput. Hell pci-e 2.0 x16 is just beginning to be a limiting factor. With this in mind pci-e 2.0 runs x16 at a theoretical 16GB/s and pci-e 3.0 runs x16 at a theoretical 32GB/s. So factoring in half the lanes of x8 on pci-e 3.0 is ~16GB/s. Performance difference between the lanes should be negligible.
*wink wink, nudge nudge* Real opportunity coming I think.
Small UI bug in Azure and Gray
in Prerelease Support [DEPRECATED]
Posted
Anyone else having a problem with getting a scroll bar on the right side? When I RDP in on my phone and try to scroll the page with a cursor I don't have a scroll bar.