DrLucasMendes

Members
  • Posts

    39
  • Joined

  • Last visited

Everything posted by DrLucasMendes

  1. I found this comment in reddit. "You can snapshot VMs as unraid provides them default by navigating to the storage device it exists on, and doing cp --reflink=always vdisk1.img vidks1_snapshot.img" Regarding refllink: "The reflink is typically meant for whole files but a partial file range can be also copied, though there are no ready-made tools for that. cp --reflink=always source target" https://btrfs.readthedocs.io/en/latest/Reflink.html
  2. OMG OMG OMG!!! THANK YOU SOOOO MUCH!!!!!!! 🤩 🤩 🤩 🤩 🤩 🤩 🤩 🤩 🤩 🤩 🤩 🤩 🤩 🤩 🤩
  3. I had the same problem when I added a nvme in my system. In my case, I found out that Unassigned Devices plugins were messing up something and not letting the Web GUI boot. I access ssh (ssh root@SERVERIP) I manually delete them in the flashdrive rm /boot/config/plugins/unassigned.devices/* rmdir /boot/config/plugins/unassigned.devices rm /boot/config/plugins/unassigned.devices-plus/* rmdir /boot/config/plugins/unassigned.devices-plus rm /boot/config/plugins/unassigned.device* I also had to manually delete all removed plugins too before re-instaling the Unassigned devices back. rm /boot/config/plugins-removed/* After it, I reboot the system. It came back to normal and I reinstalled the Unassigned devices plugins back. I hope it helps. All the best, Lucas
  4. THANK YOU!!!! I just removed my TRIM cron. Wish all a great week. Lucas
  5. I am having the same problem. It worked fine in 6.8.*, however, now after updating to 6.9.1 and further to 6.9.2 it is not showing at the GUI. I can download it. But does not show.
  6. Dear friends, After I updated my server to unraid 6.9.2 I cannot see my drives attributes in the GUI. The only one that shows up is my nvme. It has been a while, and I cannot figure it out why. In my diagnose files, attributes are there. @FlorinS how did you manage to find which plugging was conflicting? The only difference I can think, besides the NVME been NVME, is that NVME was installed after my unraid server was updated to 6.9.2. I look forward to hearing from you guys, Lucas Mendes whitehouse-diagnostics-20210803-0937.zip HDDs and SSDs NVME
  7. Ohh, thank you!. I will redo the settings with your suggestions. Should I set "Privileged" on in the NPM? I forgot HOST network provides the UNRAID server IP to the docker. I will follow your Plex suggestion @mgutt making a new bridge network and add it to the NPM. I think it is the safe way to go. Thank you very much for your time and dedication. Your work is awesome. Lucas
  8. Dear @mgutt I think I found a typo in your template because I don't remember in setting this folders. It seems that you set Data and Certificates to /mnt/cache/appdata instead of /mnt/user/appdata. My UNRAID has different cache drivers and I found the NPMO appdata in the wrong drive. LOL I don't know if it was something I did before and my UNRAID kept the template saved. However, I would suggest for you to double check there. Thank you again. All the best, Lucas
  9. Yes @Candle, you are right!! Now that you pointed to the right direction, I found this: Thank you!!!
  10. Reverse Proxy Docker container (Bitwarden) in network bridge on port 8080 not working. Dear friends, I finally was able to migrate. I was having a huge problem with Bitwarden (from: vaultwarden/server). I still don't know if it is something on my system or on NPMO. My Docker in BW is set on bridge and NPMO is in network br0. NPMO is using SQLite When I added my proxy settings, as below, however it did not work. (it used to work with jlesage version). (I changed my real domain to mydomain.com for the screenshots). To make it work, I had to add "bridge" network as Post Arguments in the advanced view of NMPO. And had to use the internal IP of BW and port 80. My question is: Am I missing some somthing on my UNRAID server to make NMPO in br0 to have access to the 192.168.100.250:8080 or is something wrong with NPMO that it does not accept port 8080 as the Forward Port? Thank you in advance, Lucas
  11. Working like a charm!!! On Sunday I will migrate all the hosts. Thank you again!!!
  12. Looking forward to have the SQLITE as default in your NPM Docker. All the best, Lucas
  13. I changed the line echo "/boot/config/plugins/user.scripts/scripts/StartVMs/script" | at now to /bin/bash /boot/config/plugins/user.scripts/scripts/StartVMs/script So I can trigger the other script. However be aware that you can use just the second script (the big one) with "At Startup of Array" option I hope I was able to assist. All the best, Lucas
  14. Great!!! Now we at least know where are the problems. Try to reinstall Dynamix Cache and see if everything keeps running in low CPU. When your Hassio is on (kicking the CPU to the sky), is it working? If yes, let's check its logs. Also, be sure to have it updated. All the best, Lucas
  15. Here is my Hassio.XML file. Hassio.XML Take a look and see if you can find anything there that might help you. Also, double check if your dockers and plugins are updated. There is something going on with your Dynamix.Cache trying to find your Nextcloud.
  16. Hi @Jokerigno I am checking your Logs here looking for anything that might be in some "infinite loop" and kicking your CPU high. It seems it is still you Hassio kicking it high at 79.4% of your CPU ___________________ "root 15472 79.4 10.9 2558664 2228892 ? SLl 19:17 27:13 /usr/bin/qemu-system-x86_64 -name guest=Hass.io,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-Hass.io/master-key.aes -blockdev {"driver":"file","filename":"/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"} -blockdev {"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"} -blockdev {"driver":"file","filename":"/etc/libvirt/qemu/nvram/c72b2bf3-b7fe-ef94-e9fa-acdefb509fec_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"} -blockdev {"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"} -machine pc-q35-2.11,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format -cpu host,migratable=on,host-cache-info=on,l3-cache=off -m 2048 -overcommit mem-lock=off -smp 1,sockets=1,dies=1,cores=1,threads=1 -uuid c72b2bf3-b7fe-ef94-e9fa-acdefb509fec -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=32,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -boot strict=on -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 -device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 -blockdev {"driver":"file","filename":"/mnt/cache/domains/hassos_ova-4.6.qcow2","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"} -blockdev {"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"qcow2","file":"libvirt-1-storage","backing":null} -device ide-hd,bus=ide.2,drive=libvirt-1-format,id=sata0-0-2,bootindex=1,write-cache=on -fsdev local,security_model=passthrough,id=fsdev-fs0,path=/mnt/user/cctv/ -device virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=cctv,bus=pci.1,addr=0x0 -netdev tap,fd=34,id=hostnet0,vhost=on,vhostfd=35 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1b:e4:0c,bus=pci.4,addr=0x0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,fd=36,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=2 -vnc 0.0.0.0:0,websocket=5700 -k it -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 -device virtio-balloon-pci,id=balloon0,bus=pci.3,addr=0x0 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on root 7548 22.9 0.1 1038296 34560 ? Ssl 19:10 9:22 /usr/local/sbin/shfs /mnt/user -disks 31 -o noatime,allow_other -o remember=0 root 9121 9.3 0.1 1334300 22620 ? Sl 19:11 3:47 /usr/sbin/libvirtd -d -l -f /etc/libvirt/libvirtd.conf -p /var/run/libvirt/libvirtd.pid root 8152 4.7 0.4 2285284 86492 ? Sl 19:10 1:55 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=10m --log-opt max-file=1 --log-level=er ___________________ Do you have next cloud installed? Dynamix.cache is kicking some CPU (79%), looking for /mnt/disk4/nextclud ___________ root 7807 0.1 0.0 5208 3484 ? S 19:10 0:03 /bin/bash /usr/local/emhttp/plugins/dynamix.cache.dirs/scripts/cache_dirs -e appdata -e backup -e domains -e isos -e system -l off root 5244 0.0 0.0 4184 2808 ? S 19:51 0:00 \_ /bin/bash /usr/local/emhttp/plugins/dynamix.cache.dirs/scripts/cache_dirs -e appdata -e backup -e domains -e isos -e system -l off root 5425 0.0 0.0 2648 820 ? S 19:51 0:00 \_ /bin/timeout 30 find /mnt/disk4/nextcloud -noleaf root 5428 79.0 0.1 29008 27212 ? R 19:51 0:03 \_ find /mnt/disk4/nextcloud -noleaf _______________________
  17. I was checking your logs. And it seems you Hassio is kicking you CPU high. Give me some minutes, I will share my hassio xml with you. So you can compare and see any difference.
  18. In my case, yes and no. I found two problems. A - Qcow2 disk full (no relation with UnRaid 6.9.0) B - Some craziness with XML files. A problem: Disk Full! How I fixed it. 1 - Backup qcow2 disk cd /mnt/user/domains/Hassos/ cp hassos_ova-5.8.qcow2 hassos_ova-5.8.bkp 2 - Them I increased 1Gb using the command qemu-img resize hassos_ova-5.8.qcow2 +1G Restarted the VM. It did not start. It stayed in a black screen with a dot. I realize it was just some VNC problem there. I pressed "2" and "Enter" and it booted. I found out what was fulling my qcow2 disk (it was my media folder). Connected via Samba, delete all the old videos there. Stoped recording videos from my Ring Door Bell inside the qcow2 drive (stupid idea I had) LOL. BOOM!!! Everything works fine now. B Problem: In some of my attempts, I had some problem with the boot EFI. Something related to the XML files (that I was not patience enough to dig in and figure it out.) I had a copy of the original XML before starting to make changes. But Lucas = No Patience. LOL So, To fix it I just deleted the VM (without deleting the VDisk!!!) and made a new one using the HA OS on unRaid! instructions (link: https://community.home-assistant.io/t/ha-os-on-unraid/59959 ) using my new increased +1Gb qcow2 disk as SATA disk. I hope that helps you to have Unraid 6.9.0 installed with your Hassio VM working! All the best, Lucas
  19. Did someone have the same problem? I am keeping my Hassio VM off by now and I will work with it during the weekend to try to fix it. If someone have the same problem it will be a pleasure to work together and find a solution. All the best, Lucas
  20. I had the same problem with Macinabox BigSur after removing the graphic card and trying to get back to VNC. I also had to change the controllers that were on bus='0x00' slot='0x01' to slot='0x02' to fix the problem. Thank you!!!!! This community is AMAZING!!!!
  21. Good news!!! It seems that with the last Safari update, it is now working with UnRAID VNC.
  22. Fala grandes!!! Impressionado com teu projeto e com tua máquina @agarkauskas. Me espantei com os SSDs tmb. Rs. Minha configuração é inversa à sua. Rs. Um SSD de cache e vários HDDs no array RS. Eu vou ser sincero com vocês, tendo à usar o standard com relação a partição, XFS para o Array e BRTFS para o cache. É tanta coisa para aprender com o UnRAID que primeiro estou aprendendo sobre como deixar tudo em standard, para depois dar minha customizada pessoal. Eu era mais antenado com computador durante a Era IDE, antes do SATA. Rs. Então tudo é novidade para mim. E entrando na área Enterprise então, uma grande curva de aprendizado existe à minha frente. Mas como o @cesarvogcomentou, temos que deixar a mente ativa. E em se tratando de tecnologia, atualmente é um conhecimento que se tornou necessidade. É como saber inglês, no passado era um diferencial, hoje é parte do currículo base de quem entra em uma faculdade. Aliás @cesarvog, o @SpaceInvaderOne é show. Acho que já assisti todos os videos dele. E toda vez que vou fazer algo, assisto novamente video, pois sempre há um detalhe que ele explica que faz a diferença em funcionar ou não. Meu próximo projeto está sendo migrar meu Proxy Reverso do Docker NginxProxyManager para o pfSense. Já tentei 3 vezes e nada. Vai ser igual o Time Machine, uma hora sigo o passo a passo dos videos pela 5 vez e vai simplesmente funcionar. HAUhAUhauAHua Hoje estou rodando o pfSense em uma maquina virtual no UnRAID. Uma doidera quando desligo o Array para algum ajusto ou reinicio o servidor. AhuAHAUahUA. Assim que conseguir rodar o pfSense + ACME + HaProxy para fazer o proxy reverso, penso em adquirir uma maquina Dell R210 exclusiva pro pfSense. Já achei por 150-250 dólares. Achei alguns desktops DELL tmb por 100 dólares usados. Mas quero colocar tudo em Rack, deixar tudo organizado e meu TOC aliviado. RS. Além de que viciei no IDRAC rs. Não ter que ir até o computador para dar reboot e verificar tudo que esta acontecendo durante o Boot remotamente, meu DEUS, IDRAC é vida. AHuAhAUhUAhAU Forte abraço, Ótimo feriado.
  23. Agora tenho certeza que foi alguma bobeira minha. AHuAHuaHauhAUhAU Sem alterar o Owner, esta tudo funcionando. Fazendo o backup em duas maquinas distintas com dois usuários distintos. Máquina 1: Máquina 2: Foi apenas seguir com mais calma o video que aqui funcionou direitinho. Não precisei mudar o Owner. Valeu @cesarvog o incentivo de tentar novamente com o seu exemplo. Abraço Lucas