• Posts

  • Joined

  • Last visited

Everything posted by SpecFroce

  1. I found a indication on the Spiceworks community that power saving settings can interfere with server operations and cause random reboots. I'm struggling with the exact same thing myself at the moment so that is the solution i will try to apply. I know this is an old thread but i hope it can help you if you still have server issues. Source: https://community.spiceworks.com/topic/2004865-custom-supermicro-server-rebooting-everytime-the-os-installer-starts-any-os
  2. Hi! i managed to establish a connection to the server, but the tunnell refuses to load normal web pages. I can reach my router, server and switch fine. Any pointers? The tunnell type i chose is "Remote tunneled access". My Unraid-version is 6.8.3.
  3. @eagle470 try to update your BIOS. Maybe there is a underlying problem that can be solved this way.
  4. Hi! Thank you for the suggestion. It worked after i fiddled with it again since i made changes to the remote access config and not the local one. Thanks a lot! I do have some issues getting workloads and uploading results, but i´m attributing that to the general uptick in network traffic and issues with the projects homepage. So to be clear, the change i made was to change the config to the following on this line: <!-- HTTP Server --> #Following allows access from local network <allow v=''/> I´m marking this as solved. Thanks again!
  5. Hi! I had a lot of success with deleting the appdata folder with Midnight commander without the need for reinstalling the container once more. Previously the only values i had changed was my team number and username. The remaining issue is that the web control user interface is not available. The folding itself seems to be operating fine. I see the percentages going up and the log is much better. Here is the current XML-file: <config> <!-- Client Control --> <fold-anon v='false'/> <!-- Folding Slot Configuration --> <gpu v='false'/> <!-- HTTP Server --> #Following allows access from local network <allow v=''/> <!-- Remote Command Server --> #Change password for remote access <password v='PASSWORD'/> <!-- User Information --> #Change Team Number and Username if desired. Currently folding for UnRAID team! <team v='37651'/> <!-- Your team number (Team UnRAID is # 227802)--> <user v='myuser'/> <!-- Enter your user name here --> <passkey v=''/> <!-- 32 hexadecimal characters if provided (Get one here: http://fah-web.stanford.edu/cgi-bin/getpasskey.py)--> <!-- Web Server --> #Following allows access from local network <web-allow v=''/> <!-- CPU Use --> <power v='medium'/> <!-- Folding Slots --> <slot id='0' type='CPU'/> </config> Log snippet: 20:38:16:WU00:FS00:0xa7: Author: Joseph Coffland <joseph@cauldrondevelopment.com> 20:38:16:WU00:FS00:0xa7: Copyright: 2019 foldingathome.org 20:38:16:WU00:FS00:0xa7: Homepage: https://foldingathome.org/ 20:38:16:WU00:FS00:0xa7: Date: Nov 5 2019 20:38:16:WU00:FS00:0xa7: Time: 06:13:26 20:38:16:WU00:FS00:0xa7: Revision: 490c9aa2957b725af319379424d5c5cb36efb656 20:38:16:WU00:FS00:0xa7: Branch: master 20:38:16:WU00:FS00:0xa7: Compiler: GNU 8.3.0 20:38:16:WU00:FS00:0xa7: Options: -std=c++11 -O3 -funroll-loops -fno-pie 20:38:16:WU00:FS00:0xa7: Platform: linux2 4.19.0-5-amd64 20:38:16:WU00:FS00:0xa7: Bits: 64 20:38:16:WU00:FS00:0xa7: Mode: Release 20:38:16:WU00:FS00:0xa7:************************************ Build ************************************* 20:38:16:WU00:FS00:0xa7: SIMD: avx_256 20:38:16:WU00:FS00:0xa7:******************************************************************************** 20:38:16:WU00:FS00:0xa7:Project: 14304 (Run 7, Clone 161, Gen 4) 20:38:16:WU00:FS00:0xa7:Unit: 0x000000069bf7a4d55e66c9fd49550056 20:38:16:WU00:FS00:0xa7:Digital signatures verified 20:38:16:WU00:FS00:0xa7:Reducing thread count from 7 to 6 to avoid domain decomposition by a prime number > 3 20:38:16:WU00:FS00:0xa7:Calling: mdrun -s frame4.tpr -o frame4.trr -cpi state.cpt -cpt 15 -nt 6 20:38:16:WU00:FS00:0xa7:Steps: first=2000000 total=500000 20:38:17:WU00:FS00:0xa7:Completed 88182 out of 500000 steps (17%) 20:38:33:WU00:FS00:0xa7:Completed 90000 out of 500000 steps (18%) 20:38:33:WU00:FS00:0xa7:Completed 90000 out of 500000 steps (18%) 20:39:16:WU00:FS00:0xa7:Completed 95000 out of 500000 steps (19%) 20:39:59:WU00:FS00:0xa7:Completed 100000 out of 500000 steps (20%) 20:40:43:WU00:FS00:0xa7:Completed 105000 out of 500000 steps (21%) 20:41:26:WU00:FS00:0xa7:Completed 110000 out of 500000 steps (22%) 20:42:09:WU00:FS00:0xa7:Completed 115000 out of 500000 steps (23%) 20:42:52:WU00:FS00:0xa7:Completed 120000 out of 500000 steps (24%) 20:42:52:WU00:FS00:0xa7:Completed 120000 out of 500000 steps (24%) [93m20:43:07:WARNING:Denied 1: access to URI: /[0m [93m20:43:07:WARNING:Denied 1: access to URI: /[0m
  6. Hi! I have a issue that affects my Folding@home container. As this problem persisted even after deleting my docker.img i´m coming here for help. The problems i experience is that both the web ui for the container will not load and it does not start up properly so that i cannot fold anything. In these times i would really like to contribute as i once did. This is a little bit from the docker log: [91m19:48:45:ERROR: At: /config/config.xml:1:0[0m [91m19:48:45:ERROR:Exception: Parse failed: 3: no element found[0m [91m19:48:45:ERROR: At: /config/config.xml:1:0[0m [91m19:48:46:ERROR:Exception: Parse failed: 3: no element found[0m [91m19:48:46:ERROR: At: /config/config.xml:1:0[0m [91m19:48:47:ERROR:Exception: Parse failed: 3: no element found[0m Diagnostics are attached. I really want to contribute as i have in the past, so any help is very much appreciated. tower-diagnostics-20200318-2050.zip
  7. Hopefully this fixes the issue. I also have a issue with my folding at home docker not showing the Webui or loading. Especially during these trying times i would like to continue to contribute to the scientific research projects around the world. Do you see anything related to that kind of error in my logs @Squid ? For now i´m marking this as solved since the container appears to work as normal.
  8. Hi everyone. I have issues with my Transmission docker saying Unable to resume file. No space left on device. To try and clear everything up i recently deleted my docker.img and reinstalled my apps to no avail. What can i do to resolve this issue? I also have a warning in fix common issues saying my "Cache Disk free space is less than the cache floor setting". I do not know if these errors are related. See diagnostics attached. Thanks for any help. Edit: I tried to set the minimum free space to 1TB on the downloads folder in case it had any impact. It did not work. Edit 2: It seems like setting the min space to 20GB has solved the issue. I also have some other issues described in the other posts for anyone interested in helping out. tower-diagnostics-20200318-1853.zip
  9. My W10 VM refuses to boot. It freezes during startup. This was not a issue in the previous version.
  10. I like the virtualisation feature and I would like to see overclocking features added in the future. This was a fun way to set up a competition!
  11. Thanks for the input. I can connect with VNC but the bootloop still persists when i get access with or without my graphics card enabled. I´m not sure how i can change the boot loop with the bios settings, but i will try once more to download the Windows ISO to rule out ISO corruption.
  12. @testdasi A disgnostics report is attached and i have put the XML code in the post as described. This is still a issue on RC9 and since i´m running pre-release software i did not find it natural to post in the normal forums. I have also tried to download the VirtIO drivers again and replace my Windows image to no avail. @cybrnook mover has been engaged and all files should be on the cache now to my knowledge. Thanks for the input
  13. Hi everyone. I have had various issues ever since i removed one of my cache drives in the array and replaced it with a 1TB NVME drive and i´m working to restore everything to working order. The main problem is that none of my VMs work. I have tried to setup a new one with the newest Q35 machine type to no avail. What happens is that i get a boot loop when the Tianocore logo comes up and nothing works. I cannot select the windows boot image and i´m feeling frustrated. Please see attached diagnostics and XML-file below. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10</name> <uuid>558b1fca-6048-6a55-d49d-170fd71cc819</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-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/558b1fca-6048-6a55-d49d-170fd71cc819_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='2' 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='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Win10_1903_V1_Norwegian_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.160-1.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <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='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <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='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <interface type='bridge'> <mac address='52:54:00:a6:bd:68'/> <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='2'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='' keymap='no'> <listen type='address' address=''/> </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> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x84' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/appdata/Videobios AMD RX 570 Sapphire/Sapphire.RX570.4096.170323.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x84' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0557'/> <product id='0x2221'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <memballoon model='none'/> </devices> </domain> Edit: ISO corruption seems to be the underlying cause. The november image booted normally. Thanks for all replies and assistance! tower-diagnostics-20191125-2314.zip
  14. Dear Lime tech. I would like to see some direct feedback in the web gui related to performance data for individual drives and the average parity check speed to better judge if i should consider replacing individual drives or if my array is performing normally. With your current userbase and lots of different hardware-configuration, each array already has the data ready to harvest, and to further the lifespan of each system since we with such a feature better know what can be considered a normal average speed for a array parity check, or average drive speeds. A question i have seen frequently appear in the forums, or what can be considered normal wear and tear, based on Smart-data or individual performance of each drive after a parity check has been completed. If such recommendations were to be presented in a user friendly and intuitive way, it can prevent data loss and help end users better understand when drives should be replaced and to make informed decisions when considering proactive maintenance. A new consent option in the user interface could allow for periodic uploads of this kind of user data, and it can be presented with notification boxes or as more detailed info in the smart-data section/elsewhere. Hopefully i have presented my suggestion well enough that this can be implemented. I would be very happy if it comes to fruition.
  15. Before you make any software changes, remember to backup your USB-drive so you can roll back any configuration changes as needed. Before replacing any drives In the array, I would upgrade to the latest Unraid version.
  16. I did. Thanks for clearing that up and for sharing your knowledge
  17. Update your BIOS at the same time so you get the latest fixes too. Good luck with your setup.
  18. Hi! I recently managed to yank out my former cache drive that sat in a pool and format it for use in another system and in the process destroyed my old VMs. I have since focused on maintaining my docker containers and replaced the before-mentioned cache drive with another NVME drive that was larger. Now to the problem at hand: I´m trying to reinstall a VM and i´m having issues with the boot process. The BIOS image shows and the VM goes into a constant boot loop, and i cannot manually boot my downloaded Windows 10 ISO file to make a fresh install. Please see attached diagnostics. I updated to RC5 since i heard that it was better for VMs and had fixed the corruption bug in Plex and had better performance overall. Any help is greatly appreciated. Thanks in advance! tower-diagnostics-20191103-2104.zip
  19. His current motherboard will handle UEFI boot fine. He should remove the dash from the EFI folder and take it for a spin. Use UEFI wherever possible. Unraid boots flawlessly with UEFI.
  20. Hi. I would very much like to see the amount of files being moved measured in GB, estimated remaining time and percentage done for mover jobs in the GUI on the dashboard page. It helps me to plan downtime if i for some reason need to shutdown my server. The current indicator does not give much more info than "mover is running".
  21. 1 : If you have no expansion plans, hold off on buying a additional SATA card. If you absolutely need one, you can pick one up from Ebay, like this one: https://www.ebay.com/itm/Promise-SATA-300-TX4-PCI-SATA-II-3-0Gb-s-4-Port-PCI-Adapter/323948110832?hash=item4b6ccfe3f0:g:FREAAOSwvdxdEaDa A Raid-controller without the proper configuration will not pass on the SMART-data correctly. 2: You can install the empty drives and lastly install the full drive in the server. With the use of the "Unassigned devices"-plugin, you will be able to copy the data from the drive onto the array. 3: You need two graphics cards if you want to use virtual machines. Unraid needs either a integrated GPU or two GPUs in total. Personally i would consider a motherboard from a reputable server OEM like Supermicro and just change over the RAM and CPU from your current motherboard. You can easily relist the motherboard on Ebay and sell it.
  22. You can probably get a server chassis for a good deal if you look at the local marketplaces in your region. As to hardware, go with a LGA 2011 V3 motherboard and scout on Ebay for one that suits your needs: https://www.ebay.com/sch/i.html?_from=R40&_trksid=m570.l1313&_nkw=supermicro+lga+2011&_sacat=0 When it comes to connecting everything together, you should move away from pure SATA and go for SAS2 cables. In that way you will be able to connect the same amount of harddrives with less cables. That makes cable management and airflow better to manage. Also: You might think that remote management like IPMI is unnecessary, but trust me, once you get in to the game, you will benfit from it greatly. Especially if your server is somewhat inaccessible.