s.Oliver

Members
  • Posts

    308
  • Joined

  • Last visited

Everything posted by s.Oliver

  1. or you could use (if available) a free HBA-port to an sata SSD (albeit choose a good one) as an alternative for the NVMe. well, best option if direct passthrough isn't working/available. did you check your BIOS for updates? sometime those problems you mentioned are fixed later on.
  2. well, i used the cache ssd in passthrough mode for several reasons: speed and avoidance of write amplification. for a fast/responsive system, unRAID needs a fast device for it's docker storage and i didn't want to use a block device on another storage in another system. so this has the advantage of (in case it's necessary) to simply boot from the usb-stick natively in unRAID and have everything working (because cache device was passed through). might work, but keep in mind you need to have a filesystem which is built for multi-/user access, or risk corruption of data. more reliable for me (than NFS) was a simple SMB-share from unRAID, configured as storage inside PROXMOX. it's fast and simply works.
  3. well, unRAID uses the USB-stick as a way of validating your license (because it is bound to the hardware UUID of that stick). don't know how to circumvent that, even though i also don't like the single point of failure associated to that way of doing it. once (quite awhile back) i had it setup with in a different way (with a synchronisation between virtual image and the USB-stick, but you had to have it mounted while booting unRAID and in the long run it was prone to failures when you forgot to sync back to the stick, before rebooting, etc.).
  4. just quickly jumped here to give a hint: if your goal is, to boot unraid as a VM inside of Proxmox see my last post (just a few upwards from here). there's no need anymore, to fake/virtualize the usb-stick as vm file or such things. simple create the VM without (or delete later on) a disk associated. passthrough the original usb-stick ("UNRAID" labeled) to that VM and choose this one as boot order 1 (see Options) to boot from. i've set the machine type to Q35 with UEFI for passthrough of hardware hba controllers and other stuff. works perfectly.
  5. i guess it's because unRAID ignores the power button pressed event from the QEMU agent.
  6. tmux funktioniert bei mir jetzt wieder (ohne neustart von unRAID). perl ist ein überbleibsel aus alten zeiten, als unRAID noch bare metal lief. ich hatte alles probiert, inkl. deinstallation via Nerd Pack (aber auch manuell in der shell) – (tmux) hatte nie funktioniert, immer die gleiche obige fehlermeldung. dann schmieß ich perl runter und installierte tmux via Nerd Pack nochmals und voila – funktioniert wieder. ABER: wenn ich jetzt im Nerd Pack nachsehe, ist perl wieder installiert (evtl. eine abhängigkeit von einem anderen tool? aber kein python package) obwohl ich ja zwischenzeitlich schon mal deine version per shell installierte). unter /boot/config/plugins/NerdPack/packages/6.9 sind bei mir jetzt: iftop-1.0.4-x86_64-2.txz iotop-0.6-x86_64-1_fs.tgz mcelog-161-x86_64-1.txz ncurses-terminfo-6.1.20191130-x86_64-1.txz perl-5.32.0-x86_64-1.txz tmux-3.1.0-x86_64-1.txz unrar-5.8.5-x86_64-1_SBo.txz utempter-1.2.0-x86_64-3.txz ich weiß leider nicht mehr genau, was ich per hand letztenendes alles de- bzw. installierte, aber auf jedenfall geht jetzt mein oft benötigtes tmux wieder.
  7. also soeben nochmal mit removepkg sowohl python, als auch tmux deinstalliert. dann von hand installiert, danach leider die gleiche fehlermeldung. nachtrag: funktioniert jetzt wieder. kann es sein, daß das im zusammenhang mit dem (soeben deinstalliertem) perl package steht? obwohl ich jetzt sehe, daß es doch wieder installiert ist – strange.
  8. hab' das mit deinem Python3.9 package probiert – allerdings ohne neustart – immer noch die gleiche meldung. zudem auch noch das slackware 14.2 package "tmux-3.2a-x86_64-1.txz" installiert – keine änderung. btw. NerdPack meldet auch danach beim Update-Check ein Update für tmux als vorhanden. ist ein neustart zwingend notwendig? und sehe ich das richtig, daß ich dann dein Python3.9 + tmux package in den /boot/extra/ lege, sodaß diese dann beim neustart installiert werden (und evtl. vorhandene/bereits installierte versionen überschreiben/ersetzen)?
  9. this latest update of the plug-in made the tools tmux & screen unusable with the same error message. these tools are used daily here and i kindly ask for a fix.
  10. leider hier genau das gleiche problem. wollte eben grad tmux benutzen (screen ebenfalls) und exakt der gleiche fehler. testweise das iSCSI plugIn installiert (ohne neustart zumindest) hat das aber nichts an der fehlermeldung geändert.
  11. UPDATE: since one of the latest PROXMOX updates native booting from an USB device is directly support. No hacks, tricks needed anymore.
  12. thx. for the reminder. i always tend to forget, that i've to look at the beginning (even for actual news) 🙂 works perfect!
  13. Hey 6.9.1 is out! I guess we need an adapted DVB Driver Package? And thx. so much for this work to enhance unRAID!
  14. i've only tested briefly one tune/channel and that worked. my card is a Digital Devices Max A8i (cable). has 8-tuners and was heavily used in the past.
  15. well, couldn't wait and tried my luck – and... it looks good! needs a bit more time to see the longevity/stability of all services, but well, for now, i'm happy.
  16. i can't and don't want to say no. it's only my understanding of drivers for interfaces. well, someone with more knowledge of available drivers needs to chime in. but firewire is old and since a long time depreciated. i loved it back in the day, but alas not always the best technology wins in the long run.
  17. i would imagine, that firewire support needs kernel drivers to be present for that I/O interface.
  18. so basically this means i could move from 6.8.3 (with Unraid DVB PlugIn and so the custom kernel) to v6.9 out of the box and use this DVB-Drivers PlugIn (from ich777) and get my Digital Devices card for TVHeadend up-and-running in no time?! just want to be sure to have a fully supported solution.
  19. i've seen this behavior once by myself, but several times by others. in any case it wasn't necessary to start over. but i just remember it can be a hassle, to get it recognized again. latest case: friend couldn't use firefox to sign in locally to his server. it always used the plex.tv site to login in. after fidling around we used chrome browser and it worked immediately. you could also try to use this url once: http://[ip]:32400/manage maybe some of it helps
  20. hey Maciej, i can report: it works! thanks alot! 😃
  21. thx. mciekb! 🙂 i'll try out whenever i find a few minutes for the downtime
  22. here runs unRAID 6.8.1 now as VM under Proxmox. all is fine so far, but i admit, i don't use VMs inside unRAID (as that can be very tricky with performance). using quite a few dockers and plug-ins, all runs fine. Proxmox as the hypervisor uses KVM/QEMU itself to run VMs. so it would be great to have QEMU Agent support for unRAID as being run as VM (the QEMU agent would then report some informations back to the hypervisor). there's one guy, which did a VMware Tools build for his ESXi as hypervisor. but (and that's fine) he won't/can't do it for the QEMU Agent. so if anybody, or LimeTech, could bring support for the standard QEMU/Agent – that would be fine. thx. alot. PS: Proxmox is free (based on Debian) and has no limitations whatsoever. it can use all (from Debian supported) hardware, offers (built in) ZFS as filesystem and has a quite good GUI and also a respectable user base & forums. it can be (and is offered) with prof. support if wanted.
  23. hi Steven, i do run unRAID as VM under Proxmox v6.x and it uses a qemu-agent to talk to the hypervisor. so my question would be: do you see a way of compiling the necessary QEMU-Agent for unRAID, or is this out of question? a quick search for slackware based QEMU agent showed this for example: https://slackbuilds.org/repository/14.2/system/qemu-guest-agent/ that would be really great and very much appreaciated – and it would offer one more integration of unRAID into another great hypervisor (which is free and has no artifical limitations). and btw. happy new year to ya! 🙂
  24. thx., but i did that from beginning on. it never booted automatically from the USB stick – it entered the EFI shell. when intercepted while initializing BIOS and selecting the proper shown boot device (unRAID USB stick) it boots and everything is fine. not sure, why it doesn't automatically choose it. i'm running on Proxmox v6 and use UEFI/EFI boot because of passthrough'ing serveral PCI devices.