acidmexx

Just another thing on that - today i finished my new Setup considering a 1050ti is my passed Through GPU - still no luck. Installation runs fine - killed the primary Vdisk vom The VM Settings - GPU und Soundcard Passed Through - Black screen. When im going back to VNC - just for testing purposes the bios prompt says - "no bootable device" ... hm just played around to get that vdisk going to run - no luck on that tho the vdisk2 (which i installed lakka on (according to the video) is my bootdevice now as i went through the install process showen in the video with lakka 4.3 like 16 times im off ideas on that ... GPU swap didnt help out either. Anyone here ran into the same issues? br Markus

Hi, Problem on this Reddit-Post is actually that Lakka needs to have a physical GPU available - so VNC or other techs wont work after installation and booting into lakka according to Space Invaders great Video. Passing through the GPU to other Windows VMs isnt a Problem as 2 VMs in my setup work pretty well with that CPU passed through. Seems Lakka is different on that br Markus

Hi Fartmaster, to keep it short and simple .. "NO" i wasnt able to make that VM work - same issue still - tried different GPUs, several installs later still no idea whats goin wrong. Next Project is to move my unraid setup to a more beastmode Hardware - trying again after the swap has been finished - coming back with new thoughts then. Maybe anyone out there got ideas which we both guys arent aware of ? br Markus

Hey pushing this years after last post First - still one of the best Tutorials ever seen when it comes to unraid Thanks for that. Second - ran into Problems .... i installed lakka according to your Walkthrough ... latest version (4.3) on latest unraid release. Install was pretty easy, passing through my gigabyte gtx1050ti not tho the gpu works perfectly on another w10pro VM but doesnt when it comes to lakka. No Lakka Logo, Nothing after booting VM with passed through GPU - only 1 core goes full load ... done. Im Sure i did something wrong but wasnt able to find out as the Install was working well ... May anybody be able to help on that - if yes, pls let me know what i may have to submit on information. Thanks Markus

Hi there, Same issue - different scenario - i recently did a case swap from an Optiplex 7 Series DELL Workstation moving into a Fractal Node 804. As DELL doesnt give a d**n on proper ATX Standards i got myself a swap kit to just be able connecting the Sensors and Front Panel Stuff properly. here : Works pretty well but no chance since months to take control of that CPU fan - Bios says "adaptive CPU Fan Speed" (brilliant ;)) but fan goes up to max all the time. (Coolermaster Hyper 212) Wondering if there is anyway to go to solve this issue and controlling it in unraid?

I can confirm - yes - already had write and read tests on the new Array Disk - alls fine - no errors or anything. also moved the whole server to a new case (new psu) after changing cables - guess i will submit my whole logs as told by ... no need to wait until unraid array dies @ChatNoir

Hi Ladies and Gents, first topic from my side here - hope you all have a good time! Yesterday i installed a new drive to my array, formatted and precleared it and it works perfect. But still a issue is present - Parity checks which i had scheduled daily in the past (just to be sure alls good) dont work any more - means ... after a few hours doin a parity check the unraid server is not reachable anymore and it seems that all disks are spun down ... Just to be detailed (as you can see attached) I got 1 parity WDC 2 Tera, and at the initial config there was another WDC as Disc1 (when Parity works fine) now with another 2 Tera WDC put in the array my unraid just hangs itself after about 5 hours (which is basically the time unraid needed to do a parity check with only one data disk in the array. To me it seems with after starting the parity check on Disk2 Unraid just hangs itself. I would have loved to give you any log or something which is more technical - but right as unraid freezes it doesnt log anything suspicious before that happens ... any ideas ? Thanks for advice! br from Austria Mexx

Thanks for the answer - trying my luck on E-SATA

Hi Ladies and Gents, i read a lot about not using any USB enclosures within unraid - but lets dont talk about unsave data or stuff. Today this thing arrived .... https://www.amazon.de/gp/product/B07G6X524P/ref=ppx_yo_dt_b_asin_image_o03_s01?ie=UTF8&psc=1 pluged in 3 HDDs (2 data, 1 parity) and 1 SSD (cache) assigned them to the array - and all worked pretty well. Until i rebooted my unraid server. Array disks are missing and even if i just want to assign them again - names changed so Im not able to assign the right Disks to the right slots anymore. IS there any solution for keeping array information when coming from usb enclosures or even just assign a specific name to a specific disk which will never change in that case. Already tried out "unassigned Devices" but better havin a "like Raid" array then just using disks for SMB sharing or just data transfer. Any suggestions except using a big boom SAS solution ? Thanks for advices br Mexx