[Server not responding]

42 minutes ago, JorgeB said:

Start here:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

 

 

And i also found this setting:

Ryzen on Linux can lock up due to issues with c-states, and while this should mostly affect 1st gen Ryzen there are reports that 2nd and even 3rd gen can be affected in some cases, make sure bios is up to date, then look for "Power Supply Idle Control" (or similar) and set it to "typical current idle" (or similar).

 

So i have changed that tho i have a Ryzen 3700XT

[Server not responding]

30 minutes ago, JorgeB said:

Start here:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

 

 

thanks, seams like i have found something.

But how do i fix it?

 

0 /mnt/rootshare

0 /mnt/addons

0 /mnt

 

 

Finished.

NOTE: If there is any subdirectory from /mnt appearing in this list, then that means that you have (most likely) a docker app which is directly referencing a non-existant disk or cache pool

script: memorystorage.plg executed

Executing hook script: post_plugin_checks

[Server not responding]

Second time now in 2weeks. Hade to pull the plugg and restart. And now i cant get to som shares.

getfanserver-diagnostics-20230417-2321.zip

[[support] OBS-NDI]

Hi new question,

 

Is it possible to transfer for example pictures to the docker?

So if the game PC reboot you still get a picture instead of the black screen.

 

[[support] OBS-NDI]

10 hours ago, mountaintop said:

Johan,

I just tested again on a fresh container and after making sure my OBS was open on my gaming PC it shows up on the drop down list as a source as it should.

 

 

Did you give the docker container an IP as thought its another device on your network? (IE: i uses 192.168.1.x and my docker container has an IP of 192.168.1.250) or does it have a docker assigned IP like 172.16.x.x?  If its the docker assigned IP, change to using your bridge device (br0 most likely) for networking and give it a normal IP on your network and the problem should be resolved.  

 

The NDI plugin uses avahi / mdns to broadcast service availability, make sure that nothing is blocking communication.  (firewall, having docker container on a different LAN segment, using docker internal IP instead of bridged networking will all cause avahi not to work.)

Don´t realy know how but now it works. Did change device for network so i got like 172.16.x.x and then i changed back to br0 and now it works fine:)

[[support] OBS-NDI]

On 3/21/2023 at 1:26 AM, mountaintop said:

Hi gents,  Waited a bit to work on fixing this myself and ended up revamping a bit of it back to the old system to get it to work.

 

The new accetto/ubuntu vnc based image does not play well with avahi so NDI is unable to locate sources.

 

I've posted the changes to: https://github.com/mountaintopsolutions/docker-obs-ndi-ng

 

The summary is:

Went back to the old container format for now.  based on the old images when this was first published.

Updated to ubuntu 22.04

Updated OBS to 29.0.2

Updated NDI plugin

Fixed startup scripts.

 

The images are available for the unraid OBS-NDI plugin at
https://hub.docker.com/r/mountaintopsolutions/docker-obs-ndi-ng

 

they can be imported by changing the repository URL for the OBS-NDI image to:

 

mountaintopsolutions/docker-obs-ndi-ng:legacy-latest

 

or if you want to stay safe and not get any updates

 

mountaintopsolutions/docker-obs-ndi-ng:legacy-1.0

 

This container uses port 5900 for direct VNC connections and 5901 for novnc connections.

 

Please let me know if you have any problems or suggestions.

 

for the "NG" part of docker-obs-ndi-ng I have rebuilt the accetto based image, fixed the issues, and have it running manually but it needs some startup script changes that will require rebuilding the entire accetto base image to fix, as avahi and dbus need to start with xvnc.  When i have time to fix that I will publish those images, but this should get everyone back streaming for now.

 

-- DC

 

Screenshot attached showing we are cooking with gas again!

Hi,

I have it up and running but i cant find any "Source name"

 

When i set up VM win10 and install it works fine but i can´t get it to work with the Docker.

 

/Johan

[Shares all gone and can´t create new one either. Disk 1 is wrong size after change]

22 hours ago, itimpi said:

Initially you run the check to see if any issues are reported.   The link provided tells you what you have to do to do to proceed to the repair stage.

Thanks for help. I ran the check and after that i ran in the console "xfs_repair -L /dev/md1".

Now it works fine! Both problems.

[Shares all gone and can´t create new one either. Disk 1 is wrong size after change]

1 hour ago, itimpi said:

Have you tried running a file system check on disk1?   The syslog says that it has corruption and that Unraid has been unable to extend the file system to fill the drive.

Yes i have done that but it dosen’t say anything. As i understand after check it supposed to suggest repair(?)

[Shares all gone and can´t create new one either. Disk 1 is wrong size after change]

Hi,

2 problems.

1. All shears are gone and i cant create new. I can access files directly in web GUI.

2. I have replaced disk 1 with a new lager disk. 480gb SSD > 4tb HDD. But it still says 480gb size in web GUI.

 

I have rebooted stoped and started array multiple times. 

I have in the same process changed cache disks. Can this be the problem?

 

Diagnostics attached

getfanserver-diagnostics-20230326-0944.zip