Jump to content

Pinch

Members
  • Posts

    84
  • Joined

  • Last visited

Posts posted by Pinch

  1. I have been struggling to get gpu passthrough working for some time now, but it just won't work on Unraid.

     

    When ESXi is installed on the system, the gf 1070 will pass through fine to a Windows guest, but the same on Unraid will result in code 43 -- the install is a virtual machine.

     

    Hyper-V has been set to 'no', but despite of this Windows still clearly states the system is a virtual machine in the task manager*. Nothing's hidden from the guest it seems.

     

    Edit: Yeah, turns out Hyper-V should be set to 'yes'. Still didn't fix the problem, but finally got an error in the log.

     

    The hardware:

    Gigabyte Aorus Pro X570 + Asus ROG Strix X570-E Gaming (tried both; same problem)

    Ryzen X3950

    EVGA 1070

     

    I have tried all the xml additions googling help with code 43 will give to no avail.

    Since the OS is saying it's a virtual machine, I'm not suprised by the Nvidia drivers being aware too... -- this must be the issue, right?

    Booting without a VNC gpu will give a black screen.

    ROM has been dumped and set up.

     

     

    Does anyone have any idea why Windows won't get fooled? I am fairly desperate at this point.

     

    *On the 'Performance' tab. If the system's not virtual, it will state whether it is virtualization-capable or not.

  2. Has anyone successfully built the custom drivers?

    I tried twice in two different environments, but got the same script error in both cases.

     

    I don't currently have any of the test environments running, so I am unable to provide the exact error -- for now, I'm just curious if anyone's actually managed to build the drivers using the provided scripts?

  3. 4 hours ago, aptalca said:

    Post your docker run/create command

    Sorry, of course:

    /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d 
    --name='openvpn-as' 
    --net='bridge' -e 
    TZ="Europe/Paris" -e 
    HOST_OS="unRAID" -e 
    'PGID'='100' -e 
    'PUID'='99' -p 
    '943:943/tcp' -p 
    '9443:9443/tcp' -p 
    '1194:1194/udp' -v 
    '/mnt/user/appdata/openvpn-as':'/config':'rw' 
    --cap-add=NET_ADMIN
    'linuxserver/openvpn-as' 

     

    Edit: It's fixed, though now idea why. I reinstalled openvpn-as and it threw the "ERROR: Cannot ioctl TUNSETIFF as0t0: Device or resource busy (errno=16)'" in the webui when trying to start the server. Changing nothing, but perhaps trying to start the server a few more times, it was suddenly running and working.

     

    It's working, but I don't think the problem is solved.

  4. I am completely stumped by this: My OpenVPN-AS has been running perfectly and then out of nowhere stopped working.

     

    When it stopped working I was still able to connect on the TCP port, but after restarting the container a few times, that stopped working too. The unraid server has been restarted to no avail.

     

    The logs showed errors pointing to the interface or ports being already in use, which made no sense to me...

    After having tinkered with some settings (after it stopped working -- setting the container to privileged mode and only listen to UDP on port 1194 in the web ui), I am not seeing any errors in the log, but the server still doesn't listen on the UDP port.

     

    Can anyone explain to me what this means:

    root@Tower:~# netstat -an | grep 943
    tcp6       0      0 :::943                  :::*                    LISTEN
    root@Tower:~# netstat -an | grep 1194
    udp6       0      0 :::1194                 :::*

     

    The web ui (943) is working fine, telnet'ing to 1194 on localhost results in connection refused.

    UNIX is not my strong suit; what am I to gather from the fact that it doesn't appear to 'LISTEN' on port 1194?

     

    If I switch off privileged mode, the errors are back:

    2019-08-07T09:22:20+0200 [stdout#info] OVPN 0 ERR: 'Wed Aug  7 09:22:20 2019 ERROR: Cannot ioctl TUNSETIFF as0t0: Device or resource busy (errno=16)'
    2019-08-07T09:22:20+0200 [stdout#info] Server Agent initialization status:
    2019-08-07T09:22:20+0200 [stdout#info] {
    2019-08-07T09:22:20+0200 [stdout#info]   "errors": {
    2019-08-07T09:22:20+0200 [stdout#info]     "iptables_web": [
    2019-08-07T09:22:20+0200 [stdout#info]       [
    2019-08-07T09:22:20+0200 [stdout#info]         "error", 
    2019-08-07T09:22:20+0200 [stdout#info]         "service failed to start due to unresolved dependencies: set(['web'])"
    2019-08-07T09:22:20+0200 [stdout#info]       ]
    2019-08-07T09:22:20+0200 [stdout#info]     ], 
    2019-08-07T09:22:20+0200 [stdout#info]     "openvpn_0": [
    2019-08-07T09:22:20+0200 [stdout#info]       [
    2019-08-07T09:22:20+0200 [stdout#info]         "error", 
    2019-08-07T09:22:20+0200 [stdout#info]         "process started and then immediately exited: ['Wed Aug  7 09:22:20 2019 ERROR: Cannot ioctl TUNSETIFF as0t0: Device or resource busy (errno=16)']"
    2019-08-07T09:22:20+0200 [stdout#info]       ], 
    2019-08-07T09:22:20+0200 [stdout#info]       [
    2019-08-07T09:22:20+0200 [stdout#info]         "error", 
    2019-08-07T09:22:20+0200 [stdout#info]         "service failed to start or returned error status"
    2019-08-07T09:22:20+0200 [stdout#info]       ]
    2019-08-07T09:22:20+0200 [stdout#info]     ], 
    2019-08-07T09:22:20+0200 [stdout#info]     "web": [
    2019-08-07T09:22:20+0200 [stdout#info]       [
    2019-08-07T09:22:20+0200 [stdout#info]         "error", 
    2019-08-07T09:22:20+0200 [stdout#info]         "process started and then immediately exited: 2019-08-07T09:22:18+0200 [stderr#error] twisted.internet.error.CannotListenError: Couldn't listen on 0.0.0.0:943: [Errno 98] Address already in use."
    2019-08-07T09:22:20+0200 [stdout#info]       ], 
    2019-08-07T09:22:20+0200 [stdout#info]       [
    2019-08-07T09:22:20+0200 [stdout#info]         "error", 
    2019-08-07T09:22:20+0200 [stdout#info]         "service failed to start or returned error status"
    2019-08-07T09:22:20+0200 [stdout#info]       ]
    2019-08-07T09:22:20+0200 [stdout#info]     ]
    2019-08-07T09:22:20+0200 [stdout#info]   }, 

    Netstat is showing the same thing as before. The web ui is loading, but I am unable to sign in using the correct credentials.

     

    What happened? Why did this stop working all of the sudden?

  5. Success!

     

    Flashing the M1015 on the ASRock resulted in the PAL error, but my trusted old unraid tower with an Asus mb did it without issues.

     

    So the M1015 is flashed as an LSI 9211-IT with the latest P17 fw and pass-through is working! I chose to flash the BIOS too, although I have no intention of connecting a boot disk to the controller - is longer boot time really the only drawback of flashing the BIOS? If yes, that's not a problem.

     

    An odd thing is that when connecting an old Toshiba 160GB 2.5'' to the M1015 it won't recognize it. It works fine when connecting it to the onboard ASM1062. I have no intention of actually using this disk, but am still wondering why it won't work...

     

    I couldn't find a definitive answer for this one: will drive spin-down work? ATM I have a spinner and an SSD connected to the M1015 being passed through; both drives are apparently spun down, which doesn't make sense - my old tower would never show an SSD as spun down, so I don't know if I can trust unraid on this one...

     

    EDIT: Silly me, the SSD in the old tower is the cache disk with a lot of plugins running, so even if it was a spinner it would never be spun down - is it normal for unraid to show an SSD as spun down when it's idle?

  6. Hmm, seems like I'm either really unlucky that the ASRock card won't pass-through or there's something wrong with my setup.

     

    It doesn't make sense 5.0 doesn't recognize any of the controllers...

     

    I took the chance and ordered an M1015... As far as cross flashing goes, I get a lot of hits where people's been flashing it as a LSI-9240-8i, but you mentioned LSI-9211-8i. Any specific reason you're using that controller?

     

    Do you happen to have a link of some sort regarding the cross flashing? :)

  7. I meant the setup utility wouldn't even recognize any controller, so there was no disk available to install to (had one disk hooked up to each controller).

     

    5.5 supports only the Lynx Point controller (don't know about the Marvell controller)

    5.1u1 supports both the Lynx Point, ASM1062 and the 88SE9120, but can't pass-through the Marvell

    5.0 apparently supports none

  8. Thanks :)

     

    Keeping this thread on subject, I just moved an ASRock SATA3 (Marvell 88SE9128 / 88SE9120) from the old tower to check if ESXi would recognize it. It does and disks are read fine.

     

    But when passing it through to either unRAID or a Win7 VM, neither can see the controller - Win7 doesn't even show anything unrecognized in the system management.

     

    I am planning on replacing this controller either way (it only has two ports), but is it odd that ESXi can use it, but apparently not pass it through? Will a different - confirmed working - controller most likely still work?

  9. I've installed the VMware tools using the plg. They work fine, but had to install them manually too. I am planning on running most of my existing plugins in seperate VMs, but I hate not knowing why it's not working as intended!

     

    Well, you have twice the speeds I'm getting during parity check... I have no idea what's wrong...

  10. So I'm in the process of migrating to a new unraid build running in ESXi and everything is going surprisingly well, but before I actually move the disks there are a few issues left unexplained.

     

    No matter the combination of disks (virtual and/or physical) I "only" get around 50-60MB/s during parity check. This isn't exactly slow, but it's still well below my current tower which runs quite consistently at ~80MB/s - on hardware that is nowhere near as good as the new server. Even if I map two virtual disks from two independent SSDs, this is still the performance I'm getting.

     

    What's your experience? Is 50-60MB/s to be expected?

     

     

    Another thing, and this is what's holding me back on moving the disks, is that plugins (.plg) located in /boot/config/plugins won't install automatically. I can installplg them manually and they work fine - even after a reboot.

    This isn't a big issue, but since it's such a basic feature I'm worried I've set up something wrong...

     

     

    I'm using the pre-built VMDK posted on these forums and unraid is currently installed on a 3GB USB3 stick. The disks are being passed through on a ASM1062 controller.

  11. I have no need for the added features in 5.5, so as long as I'm not the only one having issues, I'll have faith it'll be fixed at some point...

     

    If only I knew why plugins aren't being automatically installed, I would be ready to migrate to the new server. It's not really an issue since they can be installed manually, I just hate not knowing why it's not working!

  12. While on the subject of ESXi and unRAID, what's your experience with performance? I am currently not able get more than 50-60MB/s on parity checks - doesn't matter if I only have virtual disks mapped or if only disks on the pass-throughed controller are mapped.

     

    Another weird thing is that plugins (.plg) located in /boot/config/plugins won't install automatically. If I installplg them manually they work, also after a reboot...

     

    I'm close to being ready to move my current array from my old server, but am still a bit hesitant because of the performance issue and the plugins not installing (it's such a basic feature, makes me think I've set up something incorrect).

     

    I'm using the pre-built VMDK from http://lime-technology.com/forum/index.php?topic=26639.0.

  13. So I tried both resetting the BIOS and at the same time installed ESXi 5.1u1 instead of 5.5 - much to my own surprise pass-through worked!

     

    Tried reinstalling 5.5, not changing any BIOS setting, and it was broken again, so it appears 5.5 is the issue...

     

    I'd like to know why 5.5 fails, but at the moment 5.1u1 works, so I'm happy :)

  14. Hey BobPhoenix

     

    Nice to hear someone's had success passing through onboard devices!

     

    I've triple checked the BIOS and everything regarding virtualization has been enabled, but I'll try starting from the bottom and reset to defaults.

     

    The MB should be able to automatically fetch updates through the BIOS, which claims there are none.

  15. Thanks for your response.

     

    Everything VT-d related has been enabled in the BIOS.

     

    Although most people do seem to use addon cards, I haven't come across anything that made it clear that onboard devices won't work, but my issues seem to indicate you're right.

     

    I'll try with an addon card.

  16. Hey guys

     

    This is an amazingly difficult google and it doesn't seem like any of the existing ESXi threads cover this...

     

    This isn't unRAID related as such, but I figured I'd start here: I'm trying to set up unraid on an ESXi build, but am having some trouble using pass-through.

     

    I have an ASRock Extreme6 z87 motherboard with an Intel Core i5 4670 connected. Both support VT-d etc.

     

    If I pass anything through, unRAID won't recognize it. If I pass it to a Windows VM instead, Windows sees it, but can't use it. It doesn't matter what I try to passthrough, but take fx the ASM1062 SATA3 controller: at first it's recognized as a "SATA controller", but apparently missing the drivers. Installing the drivers enables Windows to see it as "ASM106x controller" but still with a yellow exclamation mark and an error code 10 (can't start the device).

     

    I've tried passing through the GPU, SATA controller and NIC, all show the same issue. Is this just a clear sign that my hardware doesn't support pass-through?

  17. KidCastro and 720side, are you aware of this?

    Hey Reginald, giving your rc12a build a go, my hdhomerun isn't working... As far as I can tell from your scripts, userhdhomerun isn't being packaged with the new bzroot. Are you sure it is?

     

    EDIT: Compiled userhdhomerun, placed it on the flash and symlinked it to /usr/bin/ and everything's working again. Thanks :)

     

    Try copying my userhdhomerun to your flash drive and add something like this to the go file (above the line that actually loads it of course):

    ln -s /boot/custom/userhdhomerun /usr/bin/userhdhomerun

     

    See post below for file.

  18. I just don't get this: WW's tvheadend has been working flawlessly with my HDHomerun Dual on rc4, rc8a and rc12a. Piotrasd's tvheadend sometimes works, but mostly it doesn't and it's never failing in the same way twice.

     

    If I boot unraid and install WW's plg, tvheadend works great. If I stop tvheadend through the unraid webui and through SSH install and start the updated version:

    installpkg /boot/custom/tvheadend/tvheadend-20130426-i686-1PTr.txz
    tvheadend -c /mnt/cache/.appdata/tvheadendnew -u nobody -g video -f

    XBMC on my HTPC (OpenELEC) can usually start streaming the first one or two channels I try to watch. At some point XBMC will display "Connection lost" / "No input detected" / "Access denied" / "Disconnected from Tvheadend", and tvheadend will have stopped working. Most of the time I can still access the tvheadend webui, but sometimes I can't - when it's accessible, everything is loading REALLY slow, though...

     

    If I stop tvheadend through the unraid webui (the updated version - the plugin seems to handle stopping the process fine even though it didn't start it originally), reinstall WW's build and start it, it's giving me the same errors as the updated version does (remember, WW's build works fine upon bootup). The webui is still accessible and it's clearly the old tvheadend running.

     

    WW's tvheadend's config dir is /mnt/cache/.appdata/tvheadend.

     

     

    I'm not expecting a solution, but maybe someone could point me in the right direction?

     

    EDIT: I haven't enabled anything in the updated tvheadend that wasn't working in the old version (timeshifting etc.).

  19. You should create an apps share rather than a hidden folder, v5 has the ability to create the folder/share and let the mover know to leave the apps directory alone.

    Figured it out, check my updated post.

     

    On a side note, and it's actually quite amazing how I'm able to get these things working considering my complete lack of unix skills, how does one stop the tvheadend process properly? I mean, without just killing it?

  20. Ironicbadger, I've been running WW's tvheadend build for a while and have been wanting to upgrade for some time, but haven't been able to do it either.

     

    Correct me if I'm wrong but the install itself should be fairly easy (taken from CHBMB's post a few pages back): grab libidn and tvheadend from https://truck.it/p/Vq3zpArAKB, copy them to your flash (/boot) and add the following to your go file, changing the paths to where you put your files:

    # TVHeadEnd Install
    installpkg /boot/packages/libidn-1.19-i486-1.txz
    installpkg /boot/packages/tvheadend-20130426-i686-1PTr.txz
    sleep 10 && sudo -u root tvheadend -c /mnt/cache/.apps/tvheadend -u nobody -g video -f

     

    Doing this, however, I can't seem to access the web interface with any user/password combination. With the firstrun (-C) argument I can access the webui, but changes aren't being saved - restarting tvheadend (not unraid) will set all settings to default. This is probably because the /mnt/cache/.apps/tvheadend directory isn't being created, but I can't figure out why...

     

    As it always is, this was a problem with the permissions; tvheadend doesn't create the new config dir, so I created it (with root user), but tvheadend didn't have read/write running as nobody. Running tvheadend as root didn't, oddly enough, work either.

    Setting owner of the new config dir to nobody fixed the problem.

     

    So to sum up how to install the updated tvheadend:

    Download the files and modify your go file

    Create the new config dir and make sure the owner is nobody

    Launch tvheadend with the -C flag and create an admin user in the webui

    Restart tvheadend, sign in and start setting up

×
×
  • Create New...