Jump to content
We're Hiring! Full Stack Developer ×

tjb_altf4

Members
 View Profile  See their activity

  • Posts

    1,401

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Everything posted by tjb_altf4

  1. tjb_altf4
    Reminds me... I tried to edit a .yaml file also and saw the same thing, furthermore I downloaded it to view, and it downloaded literally as "FileName", and not "some_config.yaml"
  2. tjb_altf4
  3. tjb_altf4
    I noticed this with rc4 (just before upgrading to rc5), but I had other one off issues so wanted to test after a few reboots/reinstalls... Now on RC5, if I try and stop the VM Manager like in the screenshot below, it fails to shutdown, as seen by the status. This also stops me from making network config changes, as expected when VM Manager is still running Logs indicate the shutdown script has failed, note that I don't have any VMs defined yet (which may be the cause of the array error?) Apr 28 11:56:16 jaskier emhttpd: shcmd (395): /etc/rc.d/rc.libvirt stop Apr 28 11:56:16 jaskier root: /etc/rc.d/rc.libvirt: line 57: NAMES[${id:0:36}]: bad array subscript Apr 28 11:56:16 jaskier emhttpd: shcmd (395): exit status: 1 Apr 28 11:56:16 jaskier emhttpd: shcmd (396): umount /etc/libvirt Further troubleshooting shows it definitely isn't stopped
  4. tjb_altf4
    I've got an N6005 coming for use as a pfsense box, but was planning on testing some other use cases also... happy to help with testing to get hw acceleration working when/if it arrives
  5. tjb_altf4
    You are using Seabios on your Unraid VM, but OVMF on Proxmox. Try reinstalling the VM under Unraid using OVMF for an apples to apples comparison. Also note that while Unraid 6.9.2 is on Q35-5.1, Unraid 6.10.0-rc5 is on the much newer Q35-6.2, so you might see better performance there also.
  6. tjb_altf4
    Upgraded drama free
  7. tjb_altf4
    weird one, couldn't get it to use bash on that template. I cleaned out my templates and started again and now this new container works as it should (bash console)
  8. tjb_altf4
    Changed Status to Closed
  9. tjb_altf4
    I've noticed in the latest RC, a regression error snuck in and the preferred console shell command as defined in the template, is not honoured. I can switch to bash manually (so it is supported), and the same container on my 6.9.2 server does honour this setting. @bonienl
  10. tjb_altf4
    You'd be lucky if AliExpress vendors ship out within 30 days
  11. tjb_altf4
    If hyperthreading is enabled in BIOS, it might be a result of Spectre-Meltdown mitigations, in which case this thread might help:
  12. tjb_altf4
    Yep hyperthreading looks like it is disabled @Vossy lscpu output from diags: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 40 bits physical, 48 bits virtual CPU(s): 12 On-line CPU(s) list: 0-11 Thread(s) per core: 1 Core(s) per socket: 6 Socket(s): 2
  13. tjb_altf4
    Wouldn't work, even if there was support in Unraid for splitting the gpu up, this config only ever supports one discrete video output. Other vGPU "outputs" would need to be streamed with something like parsec, or using something more advanced like looking glass. Craft Computing has some tutorials on doing this on Proxmox (also KVM based like Unraid), and there is even info on doing this with GTX/RTX cards....
  14. tjb_altf4
    Seems to be mostly Samba config, other than some consistency around snapshot folder + naming https://www.samba.org/samba/docs/current/man-html/vfs_btrfs.8.html https://forum.openmediavault.org/index.php?thread/7331-guide-windows-previous-versions-and-samba-btrfs-atomic-cow-volume-shadow-copy/ and one with a ZFS flavour https://forum.level1techs.com/t/zfs-on-unraid-lets-do-it-bonus-shadowcopy-setup-guide-project/148764
  15. tjb_altf4
    For physical machines, you may need to enable WOL, which sometimes gets obfuscated under different named settings. For VMs, WOL should work once those prereqs are in place. Under Settings > Wake On LAN, you will find a network scan tab to find computers... if yours doesn't show you can add the MAC address manually.
  16. tjb_altf4
    Some new bits finally arrived to get the v2 design going
  17. tjb_altf4
    if the docker is still running you can extract the passed envs using docker exec CONTAINERNAME env
  18. tjb_altf4
    I'm not against having options to store elsewhere, but nearly all config related to an unraid server is kept on the flash drive, including the native Unraid docker template solution. It's hardly a bad solution, and is the most Unraidesque solution (as a default).
  19. tjb_altf4
    Amazing work @SimonF
  20. tjb_altf4
    6.10.0-rc4 is currently on OpenSSL 1.1.1m (14 Dec 2021) which has a vulnerability that can leave it open to denial of service attacks. https://www.openssl.org/news/secadv/20220315.txt https://github.com/advisories/GHSA-x3mh-jvjw-3xwx Advice is OpenSSL 1.1.1 users should upgrade to 1.1.1n, which probably missed the last RC upgrade window by a few days.
  21. tjb_altf4
    Small thing I noticed as a brand new user, "show root" was toggled by on default, but had to be untoggle/retoggle to get root to actually show
  22. tjb_altf4
    Seems to be a limitation due in how we are calling ttyd? If we add a salt (time) to the object name like the vanilla webterminal does (which allows multiple sessions), that should get around the issue? openTerminal('ttyd','Web Terminal '+d.getTime(),''); If that's not possible, I did find a workaround, it looks like you can use simply use the URL to create as many new sessions as you want, i.e. http://jaskier.local/logterminal/DiskSpeed/ creates a new terminal session, its just not as elegant as using the GUI as we do now.
  23. tjb_altf4
    In 6.10-rc4 you can no longer have both a docker console and docker log window open, when you open one or the other it overwrites the existing session.
  24. tjb_altf4
    in 6.10, labels are supported, icon being one of those... you should be able to add it to the compose file to get the icon added. Not tested this myself yet though.
  25. tjb_altf4
    Reported temps probably have the wrong offsets in the driver, I see weird temp reporting variations in windows... which one of these 3 temps is the right one here ? haha As long as you have appropriate cooling on there, I wouldn't worry too much unless it starts throttling a lot.
×
×
  • Create New...