casperse

Members
  • Posts

    610
  • Joined

  • Last visited

Posts posted by casperse

  1. Finally I found this under the "3 dots" under /config/hardware on the HA UI

    image.thumb.png.8345781a9e7186c9de8b9c76fe6ba791.png

    The path was: "path": "/dev/serial/by-id/usb-QEMU_QEMU_USB_SERIAL_1-0000:00:07.0-4-if00-port0"

    Thanks everything is up and running and I can get everyone off my back LOL

    Have a great weekend, you saved mine! Cheers

     

  2. 49 minutes ago, SimonF said:

    Did you add the XML manually? It may be you changed the slider to serial when it was connected.

     

    If you added the lines by hand remove them.

     

    Change slider back to off. Disconnect from VM, Change Slider to on and reconnect.

     

    XML should look like this if added via the plugin, I use the alias to remove.

     

        <serial type='dev'>
          <source path='/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DEX-if00'/>
          <target type='usb-serial' port='1'>
            <model name='usb-serial'/>
          </target>
          <alias name='ua-serial001011'/>
          <address type='usb' bus='0' port='4'/>

    Great reading the guide I did add the XML input manually SORRY 

    Everything is now removed:

    image.thumb.png.9058f767c1effc51f169b2cf0f9fd351.png

    So everything should now finally be okay on the Unraid and XML part!

    But for some reason I still get the in HA

    image.thumb.png.d8fdde5e39e33ab73d4b753a2e96612c.png

     

    Might be a stupid Q but how can I validate the path in HA?

          {
            "entry_id": "2bb51ca17b7fa61b8d997ce1d3f2c8a2",
            "version": 3,
            "domain": "zha",
            "title": "ConBee II, s/n: DE2421314 - dresden elektronik ingenieurtechnik GmbH",
            "data": {
              "device": {
                "path": "/dev/serial/by-id/usb-QEMU_QEMU_USB_SERIAL_1-0000:00:07.7-4-if00-port0"
              },
              "radio_type": "deconz"
            },

    Again your help is much appreciated without ZigBee most of the smart house doesn't work - so I am not that popular at home right now LOL 

  3. 40 minutes ago, SimonF said:

    Also you dont seem to have connected as serial, should show like this:

     

    image.thumb.png.97de8b6e8492f2ba15e135bc3f23bbe8.png

    Yes it seem i have this error:

    image.png.dcb3916eddd65d80a5a1ff4809a15432.png

    But I have changed the XML looking in the XML I now have to entries? like someone here also experienced

    What should I do... both here are port 4 should I just change one to something else?

    Again thanks for helping, been at this all day 😞

     

     

    image.thumb.png.b0472ca709aaf9aabde5008c06c1c17f.png

     

     

  4. 13 minutes ago, SimonF said:

    What output do you get if you hover over the virsh error?

     

    The port number is only used if you enable connect as serial via the slider which is required for map Conbee II correctly above 6.9.2

     

    THANKS! SO MUCH - I enabled the Conbee II as a serial and it seem to work now!

    image.thumb.png.c2865935faffe07f24b227a8c9f6b635.png

    My only problem now is that I don't know the correct path in the HA VM anymore?
    I know this is kind of off-topic but do you know how to define/find the new USB path in HA?
     

          {
            "entry_id": "2bb51ca17b7fa61b8d997ce1d3f2c8a2",
            "version": 3,
            "domain": "zha",
            "title": "ConBee II, s/n: DE2421314 - dresden elektronik ingenieurtechnik GmbH",
            "data": {
              "device": {
                "path": "/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2421314-if00"
              },
              "radio_type": "deconz"
            },



     

  5. Hi Again 🙂

    I had many problems attaching the CONBE II stick to my VM running Home assistant

    And I reverted to use your great plugin for this, but for some reason I keep getting this error:

    image.thumb.png.89691439fd48c27e4955b96825107aff.png

    Some think strange the USB for both is using 04?

    image.thumb.png.60b508b2110fede9ae7e5b8f21780586.png

    image.thumb.png.7749e0f31d9305410d730c6c0d8aa2b7.png

     

    Any input to what I can try, would be much appreciated 

  6. Hi All

     

    I am running latest plex docker: plexinc/pms-docker - Docker Image | Docker Hub

     

    After updating I cant start Plex I get

    Preparing to unpack /tmp/plexmediaserver.deb ...
    PlexMediaServer install: Pre-installation Validation.
    PlexMediaServer install: Docker detected.  Preinstallation validation not required.
    Unpacking plexmediaserver (1.29.0.6219-b1b4d4871) ...
    Setting up plexmediaserver (1.29.0.6219-b1b4d4871) ...
    PlexMediaServer install: Docker detected. Postinstallation tasks not required. Continuing.
    [cont-init.d] 50-plex-update: exited 0.
    [cont-init.d] done.
    [services.d] starting services
    [services.d] done.
    Starting Plex Media Server.
    Sqlite3: Sleeping for 200ms to retry busy DB.
    Critical: libusb_init failed

     

    found this but don't know what version to do a roolback to?

    New PUBLIC PMS Version Available - 1.28.2.6151-914ddd2b3 : PleX (reddit.com)

     

    Anyone who knows how to fix this?

    It all started with this, when trying to open the Plex webservice

    This XML file does not appear to have any style information associated with it. The document tree is shown below.

    <Response code="503" title="Maintenance" status="PMS is currently running startup maintenance tasks."/>

     

     

  7. 17 hours ago, casperse said:

    I just got the same?

    image.png.62de4525e3480609acb9b98c3ff1165e.png

     

    Also I can see that my dockers using the Proxynet config in Unraid is offline?

    I am running unraid v. 6.10.3rc1

     

     

    Did the latest update and everything is working something must have changed and caused this...
     

  8. 21 hours ago, casperse said:

    I think I got it working except one thing, and its driving me crazy!

     

    I have the keyboard setup in VM as VNC DK

    And in the macinabox I have the:

    image.png.720d3796f638bce1445b93518f9ddf64.png

    And I have the mapping:

    image.png.e686a05d177a913cc32c78264ff434d0.png

    Also I am using the Splashtop as remote desktop

    Tried both options:

    image.png.6826b4a2722b380c6174e3463ecd9e09.png

     

    How do I get the "@" working the "Alt +2" does not work?

    I have read multiple solutions but no one works?

     

    Anyone - do you have keyboard layout working remotely as US/UK and are you able to write @ with the "action" + 2
    I have tried multiple options and sofar no luck?
    Have you VM template as US vnc default? or have you changed it to native country? (If you got this working) 🙂

  9. I think I got it working except one thing, and its driving me crazy!

     

    I have the keyboard setup in VM as VNC DK

    And in the macinabox I have the:

    image.png.720d3796f638bce1445b93518f9ddf64.png

    And I have the mapping:

    image.png.e686a05d177a913cc32c78264ff434d0.png

    Also I am using the Splashtop as remote desktop

    Tried both options:

    image.png.6826b4a2722b380c6174e3463ecd9e09.png

     

    How do I get the "@" working the "Alt +2" does not work?

    I have read multiple solutions but no one works?

     

  10. Ok I think I got this but how to selct which platform? (Is it your native Unraid platform? or the HW used on the Synology?)
    Version : 0.8.0.3
    --------------------------------------------------------------------------------                                                                                             --------
    Available platform versions:
    --------------------------------------------------------------------------------                                                                                             --------
    apollolake-7.0-41890
    apollolake-7.0.1-42218
    apollolake-7.0.1-42218-JUN
    apollolake-7.1.0-42621
    apollolake-7.1.0-42661
    broadwell-7.0.1-42218
    broadwell-7.0.1-42218-JUN
    broadwell-7.1.0-42621
    broadwell-7.1.0-42661
    broadwellnk-7.0.1-42218
    broadwellnk-7.0.1-42218-JUN
    broadwellnk-7.1.0-42621
    broadwellnk-7.1.0-42661
    bromolow-7.0.1-42218
    bromolow-7.0.1-42218-JUN
    bromolow-7.1.0-42621
    bromolow-7.1.0-42661
    denverton-7.0.1-42218
    denverton-7.0.1-42218-JUN
    denverton-7.1.0-42621
    denverton-7.1.0-42661
    geminilake-7.0.1-42218
    geminilake-7.0.1-42218-JUN
    geminilake-7.1.0-42621
    geminilake-7.1.0-42661
    v1000-7.0.1-42218
    v1000-7.0.1-42218-JUN
    v1000-7.1.0-42621
    v1000-7.1.0-42661
    --------------------------------------------------------------------------------          

    Sorry I have tried to google this but information is not that avaible on this topic 🙂

  11. I tried the community app but I am having some problems?

     

    Uploading files does not get uploaded to the files folder?

    image.thumb.png.a3c0df97714d8dfd1e7a51f3d6da8314.png

    Also windows share shows the folder strange? "M6U1...."

    image.thumb.png.8b84dc768d85144e70a319dc63ab1d41.png

    Also changing the port number breaks the "open webui" on the Unraid docker menu (But thats a smaller problem)

     

     

     

  12. 2 hours ago, keith8496 said:

     

    @casperse - Short answer is "yes".

     

    I was able to pass the NVMEs thru another way and get pretty good performance. I'm not sure what this method is called. It looks like passing thru the raw partitions but it's really the root above the partitions. Using the VirtIO driver yields fast speeds at the expense of CPU cycles. Nice thing about Epyc is that we've got enough cores to afford it. (screenshot attached)

     

    I will continue to tinker with passing the bare-metal NVMe thru. I have not been able to pass the bare-metal NVMe controller thru without severe crashes. I was trying to bind them to VFIO and pass them thru like a GPU. I feel like this is an issue with the motherboard or BIOS. Before this board, I was trying to use Supermicro's equivalent. I was able to pass the bare-metal NVMes on the SuperMicro but had to RMA three of them for dead BMCs before getting the AsRockRack ROMED8-2T.

     

    The BIOS has a lot of options. It took me a few sessions to get the BIOS dialed in for my workload. It's definitely an enthusiast board. Having said that, I don't think Ryzen 3 requires all the tinkering/optimization that I've read about from Ryzen 1 & 2. I have two of my three GPUs passed thru. I expect the third to work just fine, I just haven't set it up yet. Sometimes I have to disconnect my USB devices to boot after a complete disconnect from power.

    Screen Shot 2022-05-14 at 9.39.42 AM.png

    Thanks for the feedback!

     

    I have a Xeon E2100G and even this setup is causing problems during passthrough of the NVidia cards 😞

    I am starting to consider a setup like yours with plenty of possibilities for future expansion!

    But NOT running Unraid as a bare-metal hypervisor (Like I always have done!)

    But instead run Proxmox as my hypervisor and then having all the VM's running here! (Passthrough should be much easier)

    And Unraid running as a virtual setup on Proxmox with HW passthrough of all the drives

    That way I could re-boot Unraid and keep all my VM running + the backup of VM's and snapshots would be built into Proxmox

  13. On 4/13/2022 at 5:44 PM, ich777 said:

    Nice, but just a quick reminder to keep in mind that Emby will stop playback if the buffer runns full, Plex doesn't do that...

     

    I have made the changes and I havnet seen any memory warning for some time, but got one today (Havent found any Emby reference)

    image.thumb.png.c1ce955ee39b3e4cd669dc3e17b8961b.png

     

    Is this just one off these things where you have to upgrade your memory 😞

    Attached new Diag file

    diagnostics-20220508-1427.zip

  14. THANKS again! - I decided to change every path to get the better performance and everything worked great!
    Also updated plugins to do appdata backup etc.... so everything was running just fine and I wanted to check files on my new cache drive

    But this time it was EMPTY! and in my main view I had this:

     

    (This was not present when running the new cache drive at start?)

    image.thumb.png.7997b03bb3674049f42d4d5c3b8f7252.png

    Somehow my new cache drive was in both places?

    Afraid that I had now lost all my cache files I did a reboot and everything is back again?

    I upgraded to rc5 yesterday, not sure this is an error or something else?

  15. 14 hours ago, trurl said:

    attach diagnostics to your NEXT post in this thread

     

    Thanks trurl

    I found a post saying I should reboot again, but that didnt help.

    I then removed the new cache drive it was empty anyway, and then I started without the new cache and stopped and added it again and now its active!

    But I have a question , very afraid to mess up my existing Appdata on my existing cache drive!

     

    If I rename my existing cache to a new name cache_appdata and then start the Docker service!

    Whar will happen to all the paths that are assigned to the currunt path 

    On 4/24/2022 at 4:55 PM, Squid said:

    Those 2 paths are actually more or less identical.  The first is referring to a share on the cache drive and the second is referring to a share on all drives including the cache.

     

    You'd want to stop all the running containers, and edit them to be /mnt/cache_apps/appdata to refer to the correct pool (for anything that had /mnt/cache/appdata).  And also set the appdata share to use cache_apps.  No need to change /mnt/user/appdata to refer to anything else.

     

     

     

    So its actually best and recommended to just use the default /mnt/user/appdata and set prefer Cache!
    And NOT like me and others to have set it manually on each docker to use the /mnt/cache/appdata - because when adding pools and renaming you have to change the paths on all dockers!