Jump to content

RiDDiX

Members
  • Posts

    174
  • Joined

  • Last visited

Posts posted by RiDDiX

  1. On 7/23/2021 at 1:24 PM, ich777 said:

    Can you try to ping unRAID from the container Console and see if it actually can reach it?

    You are right.. I cant ping my unraid server... Any clue? xD

     

    I dont know how, but it fixed itself, after I restarted the whole unRAID xD

    • Like 1
  2. Hello, first off all.

     

    Thank you for these nice plugins. Nearly all of them are working for me except the Adguard Exporter, I entered all informations the right way but when I start it, it instantly stops. I dont know why logs dont show any errors. I use my adguard home on unraid with its own IP-Adress. Docker allow host is enabled and so on.

     

    I cant figure out why this wont work.

  3. 4 hours ago, glennv said:

    Solved the mysterous VNC bootloop issue.

    1.  Log in with a GPU passed thru (i used RDP as my GPU showed black at the time)

    2. Set autologin in user options (seems to be an issue with login process looping in some cases)

    3. Reboot without GPU passed thru and now VNC works fine.

     

    Do you also experience some laggs within a few seconds? It seems fluid but nearly every 5 seconds its get laggy, but immideatly back to normal, then again a short lagg and back to normal XD

    Maybe I revert back to Big Sur xD

  4. On 5/12/2021 at 11:32 PM, Ghostly2002 said:

    Yes Sir, this solved my bad VM-performence aswell. But i had the problem with deactivate the hyper-v. If this happen, use this command in prompt as Administrator. bcdedit /set hypervisorlaunchtype off 

     

    I have also bad performance problems but these occurs just when I access shares on the unraid and move files from unraid to unraid and so on. Then my Win 10 VM gets unusable slow till the transfers are finished.

    My VM got 12 Cores, 16GB RAM, Passedthrough SSD (its own SSD not a VDISK), Passedthrough RX580.

    My problems just are noticable when accessing files on unraid, like opening a archiv file, moving or copying files within unraid or from my VM to a unraid share... Even while downloading directly with Firefox within my VM it gets slow asf... (Sorry but its laggy and unsuable till downloads/file accessing/moving/copying is finished).

    With my MacOS VM also 12 Cores, 16GB RAM, Passedthrough SSD (its own SSD not a VDISK), Passedthrough RX580... Everyhing there works "normally"...

    When I use my gaming PC to access unraid and move or copy files everything is fine and useable even on the VM, also my problem just occurs when use my Win 10 VM and I do something on the unraid shares and or do some downloads within my VM....

  5. I got nearly the same situation. My VM as is runs okish. But when downloading within it or copying/moving files over the network. My Win 10 VM gets unresponsivness and nearly unusable while downloading or moving files from the Network-Share.

     

     

    My VM got passedthrough 8 Cores (No "Hyperthreading" ones). 16GB of RAM (no balloning). RX580 and a passedthrough SSD 500GB. When I download or copying/moving files from the share or downloading games through steam my system gets really sluggish unresponsive and usuable till the download / file transfer is finished...

    I already reinstalled it switched from if440 to Q35, disabled Hyper-V and all other suggesstions but nothing seems to fix my problem.

     

    Also it seems to be a Microsoft / Windows problem because my MacOS Big Sur VM runs fast and fine...

  6. 37 minutes ago, wblondel said:

    After an hour going crazy wondering why I couldn't see any menu to add my libraries on my own server, I noticed that Plex Media Server can't start.image.png.f715561a2b8ef4be4796fd9acb8a95ae.png

     

    It is a new installation. I will try with an older version

     

     

    EDIT: OK now Plex Media Server started. I logged in again, but same thing.... can't see any admin settings or anything to add libraries.... am I stupid or what? When I go to "My media" it tells me to install plex media server. Few years ago it was so simple. Maybe I'm missing something very obvious

     

    EDIT2 : I installed plexinc/pms-docker instead and it worked out of box. I was greeted with a configuration page and was able to add libraries.

     

    Sometimes it is better to use the "original" delivered software xD

    Its still sad, that the linuxserver.io version of plex-docker dont work. But I usually also try to use the "official" version. Most of the time less pain.

    Maybe this will be fixed with an updated docker-image.

  7. 23 minutes ago, jonathanm said:

    The only downside is that it still burns a license slot, so if you are bumping against a 6 drive basic license you may as well use the slot for something meaningful. With no parity assigned, the drive is as fast as it can be, the only real limit is no trim for SSD's in array slots.

     

    What I'm getting at is I don't see why people are so hung up on the "requirement" that you have an array defined when the definition of an array is pretty much any block storage device. Pretty much any implementation I can think of can use that storage for something.

     

    I use on my "primary" unraid for "normal" things. For what is it even used for xD. Like as NAS / Backup (SMB) and for a lot of Dockers and VMs. My second Unraid is just for testing purposes. Where I test around with custom patches (kernel) and drivers. And docker settings for my network enviroment.

     

     

  8. 1 hour ago, Jaster said:

    "The devil I know" is basically my thought... just wondering if unraid will run without an array with just a pool or some unattached devices..?

     

    24 minutes ago, jonathanm said:

    No. Currently you must have 1 data disk defined. That shouldn't be an issue, you could technically assign a scrap 1GB USB to it if you want.

     

    Ups I really "overread" this. Will a USB-Drive really work as Array-Disk? Nice to know. I just used old HDDs like my 120GB Hitachi or WD Raptor xD

  9. 1 minute ago, ishcabittle said:

    Throwing my hat into the boot loop pile.  At first I thought I was not following the directions precisely, but seeing others with the same experience I feel more confident I'm doing things correctly and it is just bugging out.

     

    Hackintosh stuff is always related to hardware and apples decisions. Sometimes it works "out-of-the-box" sometimes it is needed to investigate.

    As far for me I had also some trouble at the beginning because it was my first Hackintosh VM with passthrough hardware.

    After some research and help here in the forum I got everything working and my expertise is to never give up. xD

    It is always hard to help, when just shorts informations are given. Most of the problems depents of settings within the xml file itself.

     

    Correct mount-points, correct hardware ids and so on.

  10. 5 hours ago, Jaster said:

    Hi Guys,

    I'm running a few unraid servers and am very happy. Now I need to add some hardware just for virtualization (windows 10 VMs). I don't need an array or raid as the data and backups are stored on another unraid server. Can I / Should I setup a box like that on unraid or rather go for another OS?

     

    For me goes it the same way as meep already said. OK you could go with ESXi or Proxmox, but for me Unraid did this all a lil bit "nicer" for me.

    I like the fact that if needed or wanted, you could do more with Unraid without the hassle to reconfigure everything again. Like you want to use Windows 10 VMs in a corporate enviroment, like my company do. If you have the licences you could set up a Docker KMS-Server with your provided Keys and many other nice things.

    But keep in Mind, that if you maybe want to play games on the VMs check their Anti-Cheat, because many Anti-Cheat softwares are kicking/banning people which run their games on VMs.

  11. This seems to be a interessting topic 🙂

     

    I use my Unraid Server heavily for VMs, Big Sur 11.3.1 heavily for graphic design and video edition (passedthrough RX 580, 8 Cores and 16GB of RAM), Windows 10 for normal Workflows like maintaining my works Servers (RDP) and sorting my Unraid Server shares (passedthrough GT630, 4Cores, 8GB RAM).

    And a ton of Dockers, AdGuard Home, AdGuard Home Sync (for my Pi as Backup), JDownloader, Plex, Krusader, putty, Confluence (Atlassian), mysql-servers, MKVToolNix, Handbrake, Firefox (normal Browsing), Firefox-Facebook (just for Facebook, Instagram...), Firefox-Sync-Server, sabnzbd, heimdall and thunderbird.

    It seems to be alot and yes it maybe is but I like the fact using my already configured machine for such things. Around my wattage usage is 140-180 Watts.

     

    I will in the near future just use SSDs instead of normal HDDs because faster and silent. For Backups I'll use my HDDs then in my Synology-NAS. My Synology just now bring me my DDNS for my Unraid stuff. xD It works a lot nicer then duckddns and all others because I like the Synology UI for setting up reverse proxies and it is build in why not use it.

     

    Yeah also a lot, but more efficant then my normal Workstation with an i9-9900K and a RTX 2080Ti (around 200-450Watts nearly at idle xD yes no coreparking and all energy saving things are turned off, because I want to game and it should always be fluid as possible while gaming...).

     

    I already switched most of my workflows to my Unraid VMs and use my "workstation" sometimes just for gaming purposes. (Cuz many games kick or and will ban you if you use VMs as Gaming-Stations "sad").

     

    My energy-provider loves me because I pay them a lot but what I can do for my private and selfhosted life I do. Also I like the fact to be free as possible when it goes to hosted things like "cloud-storage, Sync-Servers and so on....".

  12. 20 minutes ago, Zulu2k said:

     

    that's strange. Which Unraid version do you have? Are you changing the config of the docker container? 

    I install the container and don't change any settings and then just run it. Then the notify script and then the helper script. After that, I start the VM and select the base image, which then bootloops.

     

    I already did some bad things to my macos vm. A few sites before you can ready my problems. I solved them with some great help here.

    After I fixed my first macos I tried just to do the same but with clear configs (this means I just set up my macinabox config and created my VMs. After creation I renamed them and created directly another one.

    I always just edited the xml file directly (advanced view within the VM settings). Because you just need macinabox for starting downloading the bigsur-install-media and setting up the bigsur-opencore.img.

    You could also just use one created xml file and add a new vm and just paste the xml file content to the new VM. Keep in mind to adjust the vdisk / hdd path and the name and UUID.

     

    I got so already two working VMs and one in the pipeline for dirty testings xD

     

    Sorry forgot to mention that I use Unraid 6.9.2

  13. 44 minutes ago, jmmrly said:

    Hmm. I'm only using SWAG as it runs a couple of wordpress sites as well as running proxy. This is my proxy config;

    
    server {
        listen 443 ssl;
        listen [::]:443 ssl;
        server_name plex.*;
        include /config/nginx/ssl.conf;
        client_max_body_size 0;
        proxy_redirect off;
        proxy_buffering off;
        location / {
            include /config/nginx/proxy.conf;
            resolver 127.0.0.11 valid=30s;
            set $upstream_app 192.168.1.235;
            set $upstream_port 32400;
            set $upstream_proto http;
            proxy_pass $upstream_proto://$upstream_app:$upstream_port;
            proxy_set_header X-Plex-Client-Identifier $http_x_plex_client_identifier;
            proxy_set_header X-Plex-Device $http_x_plex_device;
            proxy_set_header X-Plex-Device-Name $http_x_plex_device_name;
            proxy_set_header X-Plex-Platform $http_x_plex_platform;
            proxy_set_header X-Plex-Platform-Version $http_x_plex_platform_version;
            proxy_set_header X-Plex-Product $http_x_plex_product;
            proxy_set_header X-Plex-Token $http_x_plex_token;
            proxy_set_header X-Plex-Version $http_x_plex_version;
            proxy_set_header X-Plex-Nocache $http_x_plex_nocache;
            proxy_set_header X-Plex-Provides $http_x_plex_provides;
            proxy_set_header X-Plex-Device-Vendor $http_x_plex_device_vendor;
            proxy_set_header X-Plex-Model $http_x_plex_model;
        }
    }

     

    and all I get is this;

    image.png.dda7482a3edd833e9ab5e9682d996f5c.png

     


    I dont know if this is correct but it seems you are missing a lot of ports for plex.

    3005, 32410, 32410, 32412, 32413, 32414, 32469, 8324 and the udp port (1900). I never did this with swag as "proxy". Also I am using the plexinc/pms-docker (but linuxserver.io should work the same way).

    I just use OpenVPN Server to connect from everywhere directly into my lan network and then stream from everywhere. XD without Plex-Pass.

  14. 1 hour ago, Zulu2k said:

    And what about a fresh installation? Should we wait for a patch?

     

    Fresh Installations should work fine. I added already two new Big Sur 11.3.1 without any problems. Maybe I am just lucky? xD

    I already own a MacBook Air 2018 and I like the fact of working with both simutainusly. I Love Unraid and Spaceinvaderone for this script/app. Hackintosh-Systems are often just pain in the a**, but with Unraid everything seems so clean ❤️

  15. On 5/6/2021 at 1:36 PM, glennv said:

    Thanks, but somehow stuck with the same issues (just bootlooping when upgrading from 11.2 to 11.3.1 or on case of new install just looping from the start.

    Will give up for now as not sure what is going on here. Will wait for a macinabox upgrade 

    Thats bad. Maybe you could provide me the XML file of your VM?

    I updated now two times my Mac Big Sur VM without any problems. My first problem was a bad OpenCore config xD (my fault)

     

     

  16. 13 hours ago, NotClear said:

    Big Sur was running fine for me then I had to rebuild my VM and since then I get the same error. I have tried to remove all data and restart. I think it is either the Unraid update or the Big Sur update 11.3.X. It could also be that Opencore needs an update. 

    Bildschirmfoto 2021-05-03 um 01.27.27.png

    You should just try to recreate your Macinabox. This means. Delete both created userscripts, then remove the Docker-App and then remove the "app" macinabox.

    Now go into the Community-Apps and reinstall the Macinabox app with your settings.

  17. On 4/30/2021 at 9:23 AM, RiDDiX said:

     

    You should be able to update if you use the "Big-Sur-OpenCore.img" provided by macinabox (which you maybe have removed like me because you want to use your "boot drive (efi)". If you use the clear BigSurOpenCore.img which macinabox provide in /mnt/users/isos then you should be able to update. But maybe some devices wont work while you update it. After the update you should be able to use your own OpenCore again.

    I tested this within a cloned version of my bigsur without editing again my OpenCore. ^^

     

    https://easyupload.io/zyte8s

     

    Here I uploaded the standard BigSur-opencore.img

     

    Your xml should then be looks like this:

     

    
    <disk type='block' device='disk'>
          <driver name='qemu' type='raw' cache='writeback'/>
          <source dev='/dev/nvme0n1'/>    <--- SHOULD BE EDITED WITH YOUR HDD IF PASSTHROUG! --->
          <backingStore/>
          <target dev='hda' bus='sata'/>
          <boot order='5'/>           <--- Your Boot-Order needed to be changed! --->
          <address type='drive' controller='0' bus='0' target='0' unit='2'/>
        </disk>
        <disk type='file' device='disk'>
          <driver name='qemu' type='raw' cache='writeback'/>
          <source file='/mnt/user/isos/BigSur-opencore.img'/> <--- PATH TO YOUR BigSur-opencore.img FILE! --->
          <target dev='hdb' bus='sata'/>
          <boot order='1'/>        <--- Your Boot-Order needed to be changed set this while you want to update to "1" --->
          <address type='drive' controller='0' bus='0' target='0' unit='3'/>
        </disk>

     

     

    33 minutes ago, glennv said:

    Anyone want to share a working EFI qcow image to boot BigSur 11.3 (or 11.3.1) ?

    Tried to update my old 11.2 which did not work even after applying earlier mentioned penryn passthry fix.

    Tried a fresh MAcinabox, but also not booting (same as previous posters).

     

     

     

    Here you go!

    https://easyupload.io/zyte8s

    • Thanks 1
  18. On 4/28/2021 at 8:14 PM, lmanstl said:

     

    That is a much easier method to remove the old VM.

     

     

    I was under the impression that this configuration was supposed to be automatic. If this is the only solution to my issue, then I will probably wait to see if an update solves my problem. I looked into this but it looks like a multi hour plist altering process and messing around in MacOS is not worth that much more of my time.

     

    You should be able to update if you use the "Big-Sur-OpenCore.img" provided by macinabox (which you maybe have removed like me because you want to use your "boot drive (efi)". If you use the clear BigSurOpenCore.img which macinabox provide in /mnt/users/isos then you should be able to update. But maybe some devices wont work while you update it. After the update you should be able to use your own OpenCore again.

    I tested this within a cloned version of my bigsur without editing again my OpenCore. ^^

     

    https://easyupload.io/zyte8s

     

    Here I uploaded the standard BigSur-opencore.img

     

    Your xml should then be looks like this:

     

    <disk type='block' device='disk'>
          <driver name='qemu' type='raw' cache='writeback'/>
          <source dev='/dev/nvme0n1'/>    <--- SHOULD BE EDITED WITH YOUR HDD IF PASSTHROUG! --->
          <backingStore/>
          <target dev='hda' bus='sata'/>
          <boot order='5'/>           <--- Your Boot-Order needed to be changed! --->
          <address type='drive' controller='0' bus='0' target='0' unit='2'/>
        </disk>
        <disk type='file' device='disk'>
          <driver name='qemu' type='raw' cache='writeback'/>
          <source file='/mnt/user/isos/BigSur-opencore.img'/> <--- PATH TO YOUR BigSur-opencore.img FILE! --->
          <target dev='hdb' bus='sata'/>
          <boot order='1'/>        <--- Your Boot-Order needed to be changed set this while you want to update to "1" --->
          <address type='drive' controller='0' bus='0' target='0' unit='3'/>
        </disk>

     

  19. 43 minutes ago, lmanstl said:

    I tried to set this up. Initially I forgot to switch from Catalina to Big sur. After it finished downloading Catalina, I did that and restarted macinabox but the helper script still created the Catalina VM. I managed to delete that VM after some trouble and having to run the command virsh undefine --nvram "Macinabox Catalina" to allow me circumvent the error saying that there is nvram allocated to the domain preventing me from removing the VM in the webUI (this is probably the wrong way to do this but it was the solution that popped up on google), then remove the iso files, the custom_ovmf folder, the disk image, and the macinabox appdata folder and restart macinabox with the correct settings.

     

    After doing all that, I got Big Sur loaded and booting. however after selecting MacOS base system for the initial install the apple logo shows up and then a loading bar for a few seconds and then it reboots with the message "your computer restarted because of a problem" on the following install attempt and I am completely unable to advance any farther. 

     

    I repeated the reset steps listed above and went back to Catalina and had the same issue. (still currently installed and not working)

     

    I have no idea if I messed up or if my server just doesn't want to work. Any assistance would be appreciated.

    Nah, you dont messed up your server. You should just enable "expert view" within editing the VM and empty your xml completely.

    Than you should be able to remove your VM (without the vdisk!). The vdisk can you manually remove within the domains folder on your server.

     

    I fixed my problem myself. I got a bad OpenCore Config.plist. I just redid my OpenCore and then I was able to update just fine from Big Sur 11.2.3 to 11.3.

×
×
  • Create New...