mvanhooff

Or do you have a better way to use the GPU for the VM but also for tdarr transcoding?

But then I won't be able to use the GPU in the VM. Read that starting VM when docker used the GPU of other way around causes serious errors. So my plan was to put the node inside of the VM and start the VM when needed. Or scheduled to do transcoding once a week for a day or so

W10, OSX not possible with this card

Hi all, Let's first start with the current setup. Motherboard: H370M-ITX/ac Processor: Intel Pentium Gold G5400 Boxed HDD: 2x8TB; 1x4TB; 3x16TB Case: Fractal Design Node 304 Black Internal memory: Corsair Vengeance LPX CMK16GX4M2A2400C16 SSD: Samsung SSD 970 EVO Plus 500G Power: Fractal Design Integra M 450W A few years ago I started with the following setup (throughout the years I expanded with the HDD while I started with only 2*4tb 🤥) Recently, I talked to a friend of mine who informed me about tdarr. I was able to transcode a bunch of files and like this docker! Yet, it will take months (year?) to do all my media and was able to get the ASUS PH-GTX1650-O4GD6, 4 GB for a fair price and although I read about the SUPER version, I assume this version will do as well. I think it's a shame to only use the GTX1650 for the tdarr docker! While almost falling asleep I thought, wouldn't it be possible to use the igpu as it is now, and use the GTX1650 for a VM (OS X) where I will run a tdarr node? So unraid tdarr docker server in combination with a VM tdarr node? If so that would be awesome! What would be the steps to "install" the GTX1650? Moreover, I'd like to use the VM to do some basic photo editing (lightroom) and some basic calculations (run R/Matlab/SAS scripts). It doesn't have to be fast is the light but without waiting ages to load a filter in lightroom etc. Would the current setup be sufficient or would you advice to get another CPU (or MOBO?) with integrated GPU (as I think it always nice to have some graphical power for other purposes in the future (or if I download a movie which I want to have it transcoded straight away in plex)) In the near future I will upgrade my SSD while I have to use the mover too much and probably get 2*16gb internal memory. Greetings

Hi all, A few years back I bought setup (attachment). I upgraded with m.2 SSD, and several HDD during the years. I recently started transcoding with tdarr using the iGPU of the G5400 processor, which takes months to finalize I was able to get a good price on the ASUS PH-GTX1650-O4GD6, 4 GB, which I intend to use for: Transcoding my media library using tdarr Creating a few VM's so I need to able to get it working in the VM (e.g. Mac OS VM and windows 11) What are the steps for installation for both purposes? Here I read the following ( This Plugin is only necessary if you are planning to make use of your Nvidia graphics card inside Docker Containers. If you only want to use your Nvidia graphics card for a VM then don't install this Plugin! Both what If I want to use it for both?? Can I use tdarr while using the VM?

Ill buy a new one, for now I shut down my NAS. Ill contact the shop tommorow while the ssd is only a month old! Ill buy a kingston 500gb. https://www.alternate.nl/Kingston/A2000-500-GB-SSD/html/product/1568217?lk=15414 Something like this one?

Did a normal shutdown (worked!). Took out the PCIe M2 SSD and put it back in. Restarted the NAS and started the array, again it took pretty long! After a while the shares came up and eventually the dockers, but I get a error starting them: Then I tried installing a ramdom docker: The hell?? Then I checked my dashboard: Active, but SMART failure 7 unsafe shutdowns (probably the offline online) and extra information: And also the diagnostics.sys What are the best options for now!? Clean install unraid, but that won't fix the offline online problem I suppose.. could it be that it was softwarematically took offline?? I made a backup off the appdata, flashdrive, vm etc. Can somebody give advise if one suggests to buy a new SSD (must be M2 PCIe to not lose a SATA port (that's what the motherboard manual says)). The SSD goes in to a M2 slot tower-diagnostics-20191121-1857.zip

I will do a force shutdown and see if the cashedrive is loose.. otherwise buy a new one I guess? I have a CA-Backup, so I guess it should be "easy" to get it up and running again?

There is the error again: Unraid Cache disk message: 21-11-2019 18:21 Warning [TOWER] - Cache pool BTRFS missing device(s) ADATA_SX6000LNP_2J2820125962 (nvme0n1) Is this the part where the cachedrive is dead!? or loose? ;-)! If so, how can I get it up and running again without loosing all settings? tower-diagnostics-20191121-1725.zip

Ok, the strangest thing happened... I ended the parity check because i wanted to do a clean reboot (despite the 2 times it did not work properly). Eventually after 10-15 minutes, the array started. All my dockers are back, but (not yet) started. It started a parity check itself. I think it is better to let it run now? But still, I don't know where the problems came from! (most recent syslog). The only thing I can think of is that the "usable size; log" was completely full and my docker image is quite big (21gb). Moreover, I think it is better to let deluge and sabnzbd put incomplete downloads on one of my drives straight away instead of first on my cache drive? tower-diagnostics-20191121-1659.zip

Did another diagnostics and the end says something about dockerd: Nov 21 17:30:52 Tower dhcpcd[1675]: br0: failed to renew DHCP, rebinding Nov 21 17:34:23 Tower avahi-daemon[6330]: Joining mDNS multicast group on interface br-8c356d0b587c.IPv4 with address 172.18.0.1. Nov 21 17:34:23 Tower avahi-daemon[6330]: New relevant interface br-8c356d0b587c.IPv4 for mDNS. Nov 21 17:34:23 Tower avahi-daemon[6330]: Registering new address record for 172.18.0.1 on br-8c356d0b587c.IPv4. Nov 21 17:34:23 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): br-8c356d0b587c: link is not ready Nov 21 17:34:23 Tower avahi-daemon[6330]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Nov 21 17:34:23 Tower avahi-daemon[6330]: New relevant interface docker0.IPv4 for mDNS. Nov 21 17:34:23 Tower avahi-daemon[6330]: Registering new address record for 172.17.0.1 on docker0.IPv4. Nov 21 17:34:23 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready Something to do with de dockers not able to connect or something?

I can imagine it is still normal while the system was not completely shut down (but for some reason, the system was not able to do so)! But for some reason, the starting array will not complete! Some extra information: - plugins loaded - shares loaded - dockers kept loading but showed nothing. A few (i guess) hours i updated some dockers.. Should I terminate the parity check? Or should I uncheck the SSD and try to restart the array..

Aah ok! Like i mentioned, i rebooted the system, via ssh while normal reboot did not turn down de system, only the "website" was not reachable. However, after reboot it still complained about not clean shutdown...

Thanks, so the notifications were right. BUT, what does this mean.. it is dead? Or because the logs were full? The only thing extra is that i maybe was downloading a file bigger than my cache memory or something? What should i do now?

Hi all, Out of the blue I got a notification that there was something wrong with my cache (stupid that I forgot to take a screenshot). I looked at shares and there were no failures. All my dockers stopped! I saw on Main that logs were 100%. A forum said, just reboot you're system. I did a reboot but my NAS did not power off. I dove into my putty SSH and got it turned off. I Rebooted and tried to start my array but it got stuck, nothing helped.. Again I pressed shut down, and nothing happened (well, unraid stopped, but not my NAS). I rebooted it again via putty and tried starting maintenance mode which worked, now I am doing a parity check but it takes 8 hours. Maybe somebody can already help me with my diagnostics.zip which I was able to run during the parity check (luckily). For some reason there were more in the flash drive within this hour of problems!! Can somebody check what is going on? The problem started with a notification of my cache SSD (which is hardly a month old). Thanks!! tower-diagnostics-20191121-1510.zip tower-diagnostics-20191121-1525.zip tower-diagnostics-20191121-1539.zip tower-diagnostics-20191121-1553.zip