AinzOolGown

Members
  • Posts

    88
  • Joined

  • Last visited

Everything posted by AinzOolGown

  1. Hi there ! I have a little problem with the Ferdi-client's docker : It's launching good but it's not reachable. Here's the log : ---Checking if UID: 99 matches user--- ---Checking if GID: 100 matches user--- ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Starting...--- ---Can't get latest version of Ferdi-Client, putting container into sleep mode!--- Session terminated, killing shell... ...killed. ---Checking if UID: 99 matches user--- usermod: no changes ---Checking if GID: 100 matches user--- usermod: no changes ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Starting...--- ---Can't get latest version of Ferdi-Client, putting container into sleep mode!--- I tried to manually pull the docker's image but same error Thank you ^^
  2. Hello En effet, tu as bien cliqué sur "Apply" puis "Done" ? Avec çà, si tu fais une recherche sur Jeedom dans les apps, tu devrais voir l'option : Et en cliquant dessus, tu as accès à tous les dockers Jeedom Ce n'est pas le cas ?
  3. Yep sorry, i wasn't very accurate That was it, thank you !
  4. Hi ! I decided to redo a little my Unraid setup and i bought an NVMe wich i want to passthrough to a Windows VM to make a fresh install Unfortunately, i have an error message when i try to launch the VM Execution error - Cannot access storage file '/dev/disk/by-id/nvme-Samsung_SSD_970_PRO_512GB_S5JYNS0N517591V': No such file or directory I watched SpaceInvader One's video but read somewhere that it's an old method, no longer used. If you could tell me about/point me to that "new" method, please ? Here the IOMMU Group related : IOMMU group 16: [144d:a808] 08:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 And the XML : <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Win10Pro</name> <uuid>3c384058-f0a4-b3bb-fec0-439b42dbd875</uuid> <description>Windows 10 Main System</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>33554432</memory> <currentMemory unit='KiB'>33554432</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='5'/> <vcpupin vcpu='1' cpuset='17'/> <vcpupin vcpu='2' cpuset='6'/> <vcpupin vcpu='3' cpuset='18'/> <vcpupin vcpu='4' cpuset='7'/> <vcpupin vcpu='5' cpuset='19'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-4.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/3c384058-f0a4-b3bb-fec0-439b42dbd875_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='6' threads='1'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows 10_2004_French_x64.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.189.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/nvme-Samsung_SSD_970_PRO_512GB_S5JYNS0N517591V'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='nec-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='scsi' index='0' model='virtio-scsi'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:a2:e5:42'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x42' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x42' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0d8c'/> <product id='0x0008'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='none'/> </devices> </domain> Thank you very much !
  5. Yop, si tu as réussi ton install, se serait cool un petit "like" stp Et ajouter [Solved] devant le titre de ton post
  6. Oui, j'avais bloqué aussi là-dessus, jusqu'à ce que je fouille les réglages du CA J'ai testé et cela fonctionne chez moi, pas de souci Je le pense aussi, mais Unraid étant majoritairement US, les appli françaises sont logiquement moins représentées Ce qui serait génial pour les débutants serait d'avoir un docker qui pack Jeedom+MariaDB pré-config'
  7. Hi, the answer in french Je cherchais moi-même un tuto semaine dernière et je suis tombé sur ton post dans les résultats. Du coup quand j'ai fini par trouver des info' intéressantes, je me suis demandé si tu en avais toujours besoin La page est ici : https://community.jeedom.com/t/unraid-et-jeedom/4630 Regarde spécialement le dernier post d'elysium du 31/09, ça devrait pas mal t'aider. Ce n'est pas dit clairement dans son post, mais le user à créer dans mariadb/mysql est forcément "jeedom" (sauf si tu changes la conf du docker Jeedom d'origine, peut-être). Si tu as des question, n'hésites pas !
  8. Finally, i will do an install from scratch, chance to correct some error made with the system. Thank you
  9. True, i have a strange thing, here's a screencap Don't know why, but seems that a \ added itself on every file's name, and with or without it, i can't reach any of the said files O_o Have you even seen that ? Do you know what's the cause can be ? [Edit] I tried to rename the vmdk without space but no luck Then i read some post about "export to OVF" on VMware Workstation, that can output sort of a different vmdk that will pass the qemu-img convert problem (seems that i'm not the only one with this error message ^^). I was having hope, but after multiple changes, export to OVF is still greyed out, even on the vmdk source machine T_T I'm starting to think my only choice is to redo the VM from scratch ~~
  10. Yep, it was stoped I don't have 4.0.4, closest is 4.0.1 and upper version is 4.1
  11. Thanks for your reply ! I tried the qemu-img convert command and got this : qemu-img: Could not open '/mnt/user/ProgSetup/VirtualMachine/VMWare Hosts/Linux_Unix/Debian 10.x 64-bit/Debian 10.x 64-bit.vmdk': Could not open '/mnt/user/ProgSetup/VirtualMachine/VMWare Hosts/Linux_Unix/Debian 10.x 64-bit/Debian 10.x 64-bit.vmdk': Invalid argument I have to type this on unRAID's "Terminal", right ? I'm on 6.8.0, tried various things to "convert" my passphrase to keyfile but none worked, so i'm stuck with this one for now
  12. Hi everyone I'm trying to run a vmdk based VM wich i created originaly on VMware Workstation. So, i followed itimpi's tuto (here) But got stuck anyway on this : Here's my xml if some kind soul could point me where my error is, please ^^ <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Debian 10 x64</name> <uuid>d8ed2ecf-d381-0b6e-f1c7-e461ba0beca3</uuid> <metadata> <vmtemplate xmlns="unraid" name="CentOS" icon="debian.png" os="centos"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='8'/> <vcpupin vcpu='1' cpuset='20'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-4.1'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='2' threads='1'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/ProgSetup/VirtualMachine/VMWare Hosts/Linux_Unix/Debian 10.x 64-bit/Debian 10.x 64-bit.vmdk'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:37:8b:4c'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='fr'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </memballoon> </devices> </domain> Thank you very much
  13. Hi ! Maybe a bug ? When i connect to KDEinDocker (via TightVNC's app or via Firefox directly, same result), i get a blacked "System Settings" panel like this. Thank you Nevertheless, it's a great job, congrats !
  14. Finally, it was both a VPN & a bridging problem I activated bonding, build a bond0 interface but seems like it need the bridging to be activated to (thanks again bonienl !) So, now all good, solved
  15. That was it ! 👍 Thank you very much, i'm so happy right now ^^ And to think it was that simple... Sorry 😥
  16. Very sorry to up this, but it keeps me from moving forward in my tricky setup Pretty please 🙏
  17. Hi there Some time ago, i added a bond0 (with eth0&eth1), and some time after (maybe 2/3 weeks and unrelated), it seems like i cannot choose any other option than virbr0 on VM's network Here is the VM Manager screen : (here, the only choice given is virbr0, there's no other in the dropdown) The Network Settings : And the Windows VM Config : <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='3'> <name>Windows 10</name> <uuid>03fb8fb3-3ef3-90ce-3860-b74c04d11f3a</uuid> <description>VM-Win10Pro [Gaming]</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='14'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='16'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='18'/> <vcpupin vcpu='6' cpuset='8'/> <vcpupin vcpu='7' cpuset='20'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-4.0'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/03fb8fb3-3ef3-90ce-3860-b74c04d11f3a_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='8' threads='1'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/nvme-Samsung_SSD_970_EVO_1TB_S467NX0KA03529E'/> <backingStore/> <target dev='hdc' bus='scsi'/> <boot order='1'/> <alias name='scsi0-0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/MS Windows10x64 - 1903.iso'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.171.iso'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='scsi' index='0' model='virtio-scsi'> <alias name='scsi0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='usb' index='0' model='nec-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:bd:87:c2'/> <source bridge='virbr0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-3-Windows 10/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x2'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x3'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> <address bus='7' device='2'/> </source> <alias name='hostdev4'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1b1c'/> <product id='0x1d00'/> <address bus='1' device='3'/> </source> <alias name='hostdev5'/> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0d8c'/> <product id='0x0008'/> <address bus='5' device='2'/> </source> <alias name='hostdev6'/> <address type='usb' bus='0' port='4'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> (same things here, in graphical view, there's no other option than virbr0 in the dropdown). Idealy, i wish to use the "Custom : Bond0" on certains VM. I'm using unRAID 6.8.0 Thank you for your help ! N.B.: Docker find it without problem
  18. Hi ! Deleted/reinstalled all the way from scratch, seems to finally works ! Thanks Tips : on the "Nextcloud data folder" field, i previously used "/mnt/cache/nextcloud", this time i used "/mnt/user/nextcloud"
  19. Hi Which one ? ^^ Just stop the Docker, wipe the folder and start the docker again ? Thanks
  20. Hi ! I freshly installed NCP (some 2hours ago now), have access to control panel no problem, but NC WebUI loop refresh with "Initializing NextCloudPi for the first time - Please wait..." Can someone help me please ? I'm attaching the config Thank you ^^ And here is the log (edited the docker 2 times to change post argument in hope of..) NCPLog.txt
  21. Hi ! I would like to resize my Windows VM but i think i made some mistake during the installation The fact is i have no .img file containing the VM. Normaly, the NVME disk is not mounted, when i mount it it's like this : root@Tower:/mnt# ls RecycleBin/ cache/ disk1/ disk2/ disks/ user/ user0/ root@Tower:/mnt/disks# ls Rcupration/ Samsung_SSD_970_EVO_1TB_S467NX0KA03529E-part2/ Windows10Pro-x64/ root@Tower:/mnt/disks/Windows10Pro-x64# ls $Recycle.Bin/ Documents\ and\ Settings@ Program\ Files\ (x86)/ System\ Volume\ Information/ adobeTemp/ swapfile.sys* A533F2EC2881* PerfLogs/ ProgramData/ Users/ hiberfil.sys* temp/ Config.Msi/ Program\ Files/ Recovery/ Windows/ pagefile.sys* root@Tower:/mnt/disks/Samsung_SSD_970_EVO_1TB_S467NX0KA03529E-part2# ls EFI/ Is there a way to embed the content of root@Tower:/mnt/disks into a traditionnal .img VM file, please ? Thank you
  22. Hi Find it, that's a VPN problem, when i disconnect it the local network is reachable again I will search how to correct that
  23. Please find it attached, and thank you ! tower-diagnostics-20200322-1306.zip
  24. Hi Frank, nope it is properly fixed by multiple systems