spxlabs

@johnnie.black I guess my problem is my failure to understand why I haven't experienced any negative side effects. If the SSDs are unable to zero out then why is the performance still so amazing after 42,000TB of data written to the array?

Oh yes, Parity Check.

So, I have been working on a project using all SSD's in an array and I fear that my testing methodology is giving me invalid beliefs and results. The Array Single parity 1TB ssd 2 data drives, 1TB each Same brand and model SSD for all 3 No cache The Test 1 run = transferring a 48GB video 42 times after each run I do a parity check I randomly select a video to view and see if it plays after each run I delete all the data and start again My array is 2TB's in free capacity my SSDs do support trim, I am not using a trim plugin (on purpose) I am trying to determine when (or even if) write degradation happens in an all SSD array. I have no idea how to properly test for such a thing, so any advice would be impactful. Run #21 I just completed my 21st successful run and the transfer speeds have not significantly varied yet. I have not averaged the data from each run and each parity check yet but a cursory glance has not yielded any noticeable change in writes and reads. As you can image after completing my 21st successful run or transferring an approximate total of 42,336TB of data over the course of one and a half weeks-ish, I figured I would have perhaps noticed something. There has been little deviation in parity check times as well, at least none that my eye has perceived. Crossroads I am still compiling my data at this time and am not truly ready to reveal what I have recorded but I have reached a point where I am either incorrectly testing or I am misunderstanding what is actually going on. What am I doing wrong? What should I be testing for instead? Is there perhaps a better test than doing network file transfers? In what form will I see problems? Yes, I am aware this isn't officially supported. I am just a curious individual and was wondering what the threshold is for performance degradation and/or parity issues with an SSD array. Furthermore, I am aware that if I wanted the ultimate performance I could use a RAID1 cache or some other setup. That is not the point of this project/test. Thank you though.

@Ford Prefect Ahh okay. I'll try and figure out the commit part. After playing around with other containers and this one more. It's starting to look like a no go, at least for my skill set. I really didn't want to use a VM but it's starting to look like that may be the best way to go.

Okay well, I got it working. Unfortunately none of the settings get retained if the server reboots or if I make changes to the docker and it restarts. Super frustrating. However, I managed to update the Ubuntu, obs, and install other tools for some troubleshooting. After a few hours, I could not figure out why the NDI plugin does not pick up any NDI streams. I can ping the docker, it can ping my gaming rig, but it cannot see any NDI stream. Thoughts or experience?

@Ford Prefect Thanks! I'll give it a go and see what happens. Mind if I pester you if things don't work out?

@Nanobug Well if I remember I can just let you know here. Also, I started working late last night. I have no idea how long it will take me to complete. But if you don't hear from me in like a month, I either died, gave up, or forgot. Sooooooooooo oops.

@Nanobug The server does not do any encoding/transcoding/decoding work. It simply takes a single RTMP stream and distributes that stream to multiple platforms of your choosing. Fear not. I am actively working on an OBS-Server container to take a stream from your gaming computer and encode/transcode/decode the stream, then send it off to twitch. But it is proving rather difficult due to my lack of understanding Docker and poor documentation. Stay tuned.

Hey there person. I tried setting this up last night and could not get it to launch. I set the following: Port for VNC as well as the http://[IP]:[PORT] Path /root/.config/obs-studio /mnt/cache/appdate/obs-studio Not sure what else needs to be created or set. It would be really cool if you have more insight on how to get it to work inside of Unraid. For people like me looking at all the build instructions, how to run/start, etc are not helpful for me. I haven't found any container that lists what if any config file needs to help the container run. I'm not a Docker guru so I'm not entirely sure when I need to use a Variable/Path/Port/etc. I'm just a total scrub. Anyway, if you have more information on what needs to be done in Unraid, that would be very helpful.

Yeah that's what I mean, super bizarre. lol -Probably -To be clear, this docker does not do any transcoding, your gaming rig will do all the transcoding work. This setup simply allows you to stream to multiple places at once. -When you port forward, your brother used your public IP:port to reach your server? -He could VPN into your network as an alternative to exposing your system to the internet.

@itimpi is right, the # is to comment that line out and it shoudn't have been read by the container. If you copy and pasted there could have been a hidden character that was breaking things. But if you added that line in and it worked then that makes things super bizarre. Anyway. Glad you got it working.

You could duplicate the container but you would most likely have to change the ports. I have a feeling if you stream to the same container things are not going to work. Client 1 and Container 1: port 1935 Client 2 and Container 2: port 1936 That should work in my mind but this is not something I have tested. Something I am planning to do or work on is figure out how to get two computers to stream to the server and then to twitch. Both computers would basically be like in split screen. However, it seems the best way to do this is use OBS with NDI on the server. Then within the canvas just make sure both computers have equal space. I'd like do this with a container instead of a VM but it is proving rather difficult.

Yup audio worked for me. Only thing I can think of is, to double check your audio capture settings, which I'm sure you have done.

Looks like we need more questions, I'll hop aboard. What would you consider is the luckiest thing to ever happen to you, of all time?

Did I win?

I’m only here because I was told to Get. In. Here. so here I am. https://mobile.twitter.com/spxlabs

Go figure. Just a pipe dream at the moment anyway. I have many other things to work on!

Yeah buddy. Just need to figure out how to get it to work with Handbrake. Pretty awesome stuff!

Nice! I’ll keep it in mind. Now that the linuxserver team has released the Nvidia GPU plugin for all dockers. I may try using gpu transcoding in the future. If that’s even possible.

Negative. WD Reds comprise the array. There is a 1TB NVME drive as the cache drive. The watch folders are set to use cache, this way when pushing data to the server we can achieve up to 1GB/s.

Got everything working up until the part where I need to format my vdisk with Disk Utility, I get an error everytime I try to format the disk. the vdisk I created is set to SATA like you explicitly say. Not sure how to proceed. I have tried formatting the disk with several of the available options, all fail, with the same error.

Tried using 6.3.4 and 6.3.5 to no avail. Basically what I am seeing is during boot of unraid OS it does it's normal thing pretty quickly and then gets stuck at "[TTM] Initiializing pool allocator" Basically everything I can see on screen while it is stuck is as is below: <code>mpt2sas_cm0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (66016600 KB)<br> scsi host1: isci<br> scsi host2: ahci<br> scsi host3: ahci<br> scsi host4: ahci<br> scsi host5: ahci<br> scsi host6: ahci<br> scsi host7: ahci<br> scsi host8: ahci<br> [drm] AST 2300 detected<br> [drm] VGA not enabled on entry, requesting chip POST<br> [drm] Analog VGA only<br> [drm] dram 1632000000 1 16 00800000<br> [TTM] Zone kernel: Available graphics memory: 33008300 kiB<br> [TTM] Zone dma32: Available graphics memory: 2097152 kiB<br> [TTM] Initializing pool allocator</code> I have the exact same model of a server below the one I am trying to use, they are identical minus the RAM and hard drive numbers. The USB device I created for the new server works on the existing server and also other hardware so I don't think it is the USB flash device. I saw some other posts about networking preventing boot up but i don't think that is the issue because I see a line about unRAID using Intel drivers. When I try to boot to the GUI the screen goes black with a blinking cursor, never changes. With both versions. Any thoughts? SOLVED: I just used version 6.4.0-rc9f. booted right up no problem.