Kevinb123213

Members
 View Profile  See their activity

  • Posts

    31

  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Kevinb123213's Achievements

Noob

Noob (1/14)

3

Reputation

2

Community Answers

  1. Kevinb123213
    Oh, thank you for this additional info. I’m glad you were able to find a way for it to persist after reboot.
  2. Kevinb123213
    If you have a backup of your USB. Try and restore from there. Looks like unclean shutdowns are the cause of corrupting files.
  3. Kevinb123213
    TL;DR Files ending in a dash seem to indicate some sort of corruption. Long version: Found the solution. I think I should share it as it may help others. Apparently my setup cuts power and resets when I passthrough one of my GPUs - specifically the Nvidida Quadro K600. Knowing that I had an unclean shutdown, I went down the thought processes of data corruption. Which made me remember, a while back I noticed on a corrupted copy unraid usb, the dash ending files (syslinux-) appeared there too. So, I ran the following and pressed option 2 to restore from backup. fsck /boot At this point I restarted and was able to start libvirt. Now time to figure why my K600 is causing reset. -Kevin
  4. Kevinb123213
    Hello, I had an unclean shutdown (power cut and powered back up itself) for some reason when passing a gpu to a vm. Since then, I have not been able to start libvirt. Diag attached. My /etc/libvirt/ dir seems to have been automatically renamed to /etc/libvirt-/. What does a dash at the end of a directory signify? Can I just do the following? mv /etc/libvirt-/ /etc/libvirt/ Noteworthy errors: syslog root: /usr/sbin/libvirtd: error: Unable to initialize network sockets. Check /var/log/messages or run without --daemon for more info. libvirt 17277: error : virNetSocketNewListenUNIX:511 : Failed to bind socket to '/var/run/libvirt/libvirt-sock': Address already in use BTW, deleting libvirt img did not fix the issue. Thanks in advance, Kevin everest-diagnostics-20220926-1422.zip
  5. Kevinb123213
    TL;DR: You can enable blanking (black screen output) as a screen saver by doing the following: 1. Backup slim.conf cp /etc/slim.conf /etc/slim.conf.orginal 2. Edit slim.conf nano /etc/slim.conf 3. look for this line. xserver_arguments -novtswitch -allowMouseOpenFail -quiet -xinerama -v -s 0 -dpms -fp /usr/share/fonts/TTF vt07 4. Change to the following xserver_arguments -novtswitch -allowMouseOpenFail -quiet -xinerama -v -s 1 dpms -fp /usr/share/fonts/TTF vt07 You can disable screen output (no signal output) as a screen saver by doing the following: 1. Repeat steps 1 - 3. 2. Change to the following xserver_arguments -novtswitch -allowMouseOpenFail -quiet -xinerama v -s 1 dpms -fp /usr/share/fonts/TTF vt07 DISCLAIMER: Do this at your own risk. You are responsible if you break your unraid setup. Edit: Is there really no way to blank the output of the screen?
  6. Kevinb123213 started following [6.x.x] [Question] screen sleep for GUI?
  7. Kevinb123213
    Hello, I have a monitor that has Auto Input select. I would like to have the UnRaid GUI be able to sleep after x minutes (blank the video output) when booted into GUI mode. Is there a file I can edit to enable this or command I can execute? I do not see a way to do it the the GUI itself. Ideally, i want the monitor to automatically switch to the secondary input when Unraid's GUI blanks (sleeps) and still be able to wake via usb keyboard/mouse to resume video output. Thank you in advance, Kevin Sent from my iPhone using Tapatalk
  8. Kevinb123213 started following [6.10.0 RC8] [Security] VNC does not allow secure passwords and [6.10.0] [SECURITY] VNC does not allow secure passwords
  9. Kevinb123213
    OP in pre-release section by me for Unraid OS 6.10.0 RC8. Since this issue has persisted into the stable release, I am reposting here. Not sure if allowed to have two posts (prerelease/stable) for the same issue. If this is not allowed, feel free to contact me or adjust as needed. I looked at the full release notes and tried to see if the VNC package that Unraid Linux uses was the cause. I could not figure out which library/package it is. Issue: When editing or creating a VM, the VNC password field in the WebGUI template, does not allow any password greater than 8 characters. This issue was first noticed when turning on a VM just after 6.10.0-RC8 update. I was prompted that my 19 character password exceeded the 8 character limit (as shown similarly in screenshot attached). By today's standards passwords less than 8 characters are considered insecure. Reproduction steps: 1. Inside of Unraid WebGUI, navigate to VMs tab. 2. Select the "ADD VM" button below the list of currently installed VMs to create a new VM. 3. Select VM template type Linux. This shouldn't matter but these are my exact steps for testing. 4. Set primary vDisk size to "10M". 5. Set VNC Password to anything greater than 8 characters. In this case "123456789". 6. Select the button "Create VM". 7. Observe the following error: "VM reation error unsupported configuration: VNC password is 9 characters long, only 8 permitted." everestsrvr-diagnostics-20220518-1203.zip
  10. Kevinb123213
    Hello, As of 6.10.0 rc8, my VM's would not autostart because my vnc passwords contained more than 8 characters. This is a security issue because it imposes a limit on length of passwords which inherently limits the time it takes a malicious user to crack the password. Most platforms require a minimum of 8 characters. Reproduction Steps: 1. Go to VMs Tab -> Select any VM's icon and Edit. 2. Change VNC passsword to anything that contains more than 8 characters. 3. Start the recently edited VM. 4. Observe the message in the screenshot above. NOTE: I did not have this issue on RC7. Thank you all in advance, Kevin everestsrvr-diagnostics-20220511-2103.zip
  11. Kevinb123213
    I tried that too. However, it doesn't give the error just clicking apply does nothing. Issue resolved, Thank you. I feel like an idiot LOL
  12. Kevinb123213
    Hello community, I believe I've found a minor bug in the Dynamix WireGuard. The Local endpoint field doesn't allow certain domain names that are valid. For example the following FQDN will not work although it is valid: 0xFE80FFFF.ddns.net or any domain with a hexadecimal address in it. Please see screenshot attached. Thank you, Kevin
  13. Kevinb123213
    Looks like my motherboard ASUS P8Z77-M are all connected via the Z77 chipset (figure 1). Is it possible altering USB BIOS settings could help? If so, which ones? If I were to go the path of getting a USB PCIe card which would you recommend for best compatibility with UnRAID? I've tested all 4 back USB 2.0 ports and they all seem to give crashes shown in the initial post. I've never had this issue in the past. I probably should note the only change I made before this issue occurred is that I re-flashed same BIOS via ASUS EZ-Flash tool in BIOS. Figure1: Thanks again, Kevin
  14. Kevinb123213
    Thanks, I'll give this a shot. May take some time to get back to you because I have a few USB 2.0 ports.
  15. Kevinb123213 started following [6.7.2] USB I/O Errors
  16. Kevinb123213
    Hello, I'm experiencing a strange issue where the web GUI seem corrupted with a banner across the top saying: "System notifications are disabled..." So, I took a look at my syslog and I seem to be having a disconnect issue with the USB drive I presume. The only fix i've found is rebooting the server. However, it will happen again 2-3 days later. Thanks in advance, Kevin everestsrvr-diagnostics-20191030-2227.zipeverestsrvr-diagnostics-20191030-2227.zip
  17. Kevinb123213
    UPDATE: still crashes in safe mode.. Please help. Suggestions greatly appreciated. Same behavior -- numlock is lit up (can't toggle it as keyboard is frozen) and no access to server via ssh, telnet, ping, nor http/https while in this frozen state. -Kevin
  18. Kevinb123213
    Unfortunately, I'm not using VMs. I was still getting these soft-locks with virtualization disabled in BIOS. However, there was a point in time which I was using VMs and passing hardware through. Just today, I noticed that my Syslinux configuration had hardware ids for passing through old Network cards and graphics cards of which are no longer in the server. I have removed those pcie ids boot flags. If I understand you correctly, you are saying that this could cause these soft-locks?