• [6.9] After moving to 6.9 local GUI mode not working


    NLS
    • Minor

    The whole system seems to be working (VMs, containers, shares)... BUT the local (own) server GUI is not working.
    It actually stays on a clean black screen with a blinking cursor.

    I thought everything was dead until I tried to access web GUI from my main PC and saw everything (else) was ok.
    I rebooted once to see if it was a one time issue, but it wasn't.

    Not sure if the issue classifies as "minor" as it is quite major at least for me (I don't run the server headless).

     

    quasar-ultima-diagnostics-20210306-1918.zip




    User Feedback

    Recommended Comments



    5 hours ago, limetech said:

    Please try GUI safe-mode boot.

    No go.
    Same thing - goes to a blinking cursor.

    Actually it is worse because with no plugins, nothing starts to setup my network (DNS etc.) so I need to access the server using IP. :D
     

    Link to comment

    Safe mode GUI boot brought it back for me.

    Tried some additional things to see if they affected it when not in Safe mode:

    1. Disabled all VMs
    2. Disabled all Docker Containers

     

    None of those affected the behaviour.  I can try rolling back to an older Nvidia driver too.  

     

    What would you like next, a list of plugins?

    Edited by Kaldek
    Link to comment

    OK I've now also tried rolling back to an earlier nvidia driver, and disabling driver patching for multiple streams.  No effect, still no local GUI.

    Link to comment

    Weird how safe mode brought it back for you but not for me.
    I was hoping we are facing the exact same issue.

     

    Link to comment

    Hello,

     

    Like Kaldek, I've got the exactly same issue after intalling 6.9 version from 6.8.3. Everything worked fine in previous version.

     

    How could someone help me? I post diagnostic and Update assistant report if that could help to recover le GUI Mode (webGUI mode works fine from a distant computer)

     

     

    Here is the Update assistant report :

    Current unRaid Version: 6.9.0 Upgrade unRaid Version: 6.9.0
    NOTE: You are currently running the latest version of unRaid.
    Checking for plugin updates / OK: All plugins up to date
    Checking for plugin compatibility / OK: All plugins are compatible
    Checking for extra parameters on emhttp / OK: emhttp command in /boot/config/go contains no extra parameters
    Checking for disabled disks / OK: No disks are disabled
    Checking installed RAM / OK: You have 4+ Gig of memory
    Checking flash drive / OK: Flash drive is read/write
    Checking for valid NETBIOS name / OK: NETBIOS server name is compliant.
    Checking for ancient version of dynamix.plg / OK: Dynamix plugin not found
    Checking for VM MediaDir / DomainDir set to be /mnt   / OK: VM domain directory and ISO directory not set to be /mnt
    Checking for mover logging enabled / OK: Mover logging not enabled
    OK: /boot/config/extra.cfg does not exist
    No issues were found with your server that may hinder the OS upgrade. You should be good to go

    diagnostics-20210308-1137.zip

    Link to comment
    6 minutes ago, limetech said:

    There is a plugin causing this.

     

    Well how about me, that safe mode did not bring it back?

     

    Link to comment
    5 minutes ago, trurl said:

    Are you booting UEFI?

    No.  I use IOMMU groups and pass through devices to VMs so I use legacy boot.

    Link to comment
    1 hour ago, limetech said:

    There is a plugin causing this.

    That's great but how do we find out which plugin?  I mean, I was running 6.9.0-rc2 for months without issue and suddenly 6.9.0 has a problem.  It's not like I've added some wacky plugin that behaves badly.

    I'm used to being able to diagnosing stuff in Linux log files.  I've searched syslog and can't find anything, and I'm not sure where else I can look.

    Edited by Kaldek
    Link to comment

    Same thing for me.

    I can access the GUI from a network computer, but I have a black screen with the blinking curson direct on the server.

    I get a video output during loading (all the white text on the black background, but no login screen)

    NO VM

    Docker autostart is disabled

    Array autostart is disabled

    Safe mode +GUI give me the same result

     

     

    Here is my config (very modest): 

    Gigabyte H97N-WIFI (with latest bios)

    Xeon E3-1245 v3 (using onboard graphics)

    16 GiB DDR3

    2 HDD for the array

    1 HDD for the parity

    1 SSD for caching

    See attached file for my log

    alligator-diagnostics-20210308-2022.zip

    Edited by Guill.St-P
    Link to comment

    For those of you who have no other plugins installed. And, it still doesn't work

     

    I have created a new thread under:
     

     

    Edited by cortana
    Link to comment
    4 hours ago, cortana said:

    For those of you who have no other plugins installed. And, it still doesn't work

     

    I have created a new thread under:
     

     


    But I opened this thread and I don't have other plugins that affect the local GUI I think, so why is this very thread not good for this?

    I am also using UEFI.

     

    Edited by NLS
    Link to comment

    I don't think we need to create a new topic either...

    Update from this morning, server is still up and runnning, but still no GUI on the server itself. No more flashing cursor either now; just a black screen.

    Thanks to all the unraid team and community for the support!

     

    edit: 6.9.1 update did not fixed the problem

    Edited by Guill.St-P
    Link to comment
    16 hours ago, Kaldek said:

    That's great but how do we find out which plugin? 

    Prime suspects:  nvidia-driver.plg followed by NerdPack.plg

     

    Delete the offenders from /config/plugins on the flash drive and try again.  Nvidia probably just needs a reinstall after a clean boot.

    Link to comment
    1 minute ago, Squid said:

    Prime suspects:  nvidia-driver.plg followed by NerdPack.plg

     

    Delete the offenders from /config/plugins on the flash drive and try again.  Nvidia probably just needs a reinstall after a clean boot.


    (although you don't seem to refer to me)

    I don't have nvidia at all in there.
    But I do have nerdpack.
    I will remove and reboot.

     

    Link to comment
    13 minutes ago, NLS said:


    (although you don't seem to refer to me)

    I don't have nvidia at all in there.
    But I do have nerdpack.
    I will remove and reboot.

     

     

    Removing nerdpack (and rebooting) did NOT fix this for me.

     

    Link to comment

    Sounds like the graphics drivers are talking over, are you all using a graphics driver, i.e. NVIDIA or putting a file in modprobe.d for AMD/INTEL?

     

    I dont have a primary external GPU (Motherboards are SM with BNCs) on my systems so cannot test, but was doing some testing of a Mint VM with an RTX passed thru where the screen wouldn't show correctly as I didnt have the Nvidia drivers loaded in the VM. To allow me to get to a point where I could login I had to set in the grub boot loader the following nomodeset

     

    Does something like this need to be added to syslinux options? Not saying this is the solution but is it worth a try?

     

    nomodeset(I know we are not running X)

    The newest kernels have moved the video mode setting into the kernel. So all the programming of the hardware specific clock rates and registers on the video card happen in the kernel rather than in the X driver when the X server starts.. This makes it possible to have high resolution nice looking splash (boot) screens and flicker free transitions from boot splash to login screen. Unfortunately, on some cards this doesnt work properly and you end up with a black screen. Adding the nomodeset parameter instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded.

     

     

    Link to comment
    40 minutes ago, Squid said:

    Prime suspects:  nvidia-driver.plg followed by NerdPack.plg

     

    Delete the offenders from /config/plugins on the flash drive and try again.  Nvidia probably just needs a reinstall after a clean boot.

     

    Thanks for the follow-up Squid

    No nvidia drivers for me.

    I have nerdpack. Disabling it did not fix the issue.

     

    NLS and me have a very similar CPU.

    He have i7-4771 and I have Xeon E3-1245 v3.

    Both are Haswell LGA1150 CPUs with Intel HD4600 integrated graphics.

    Can this be the source of the issue? Like the nvidia drivers seems to be...

    Link to comment

    I tried using "nomodeset" with the append command at boot, it had no effect.

    For what it's worth I'm running an Nvidia Quadro P400 on a system with no on board video. (EVGA X99 Micro2 and Xeon E5-2630L).

     

    Also updated to 6.9.1, no effect.

    Edited by Kaldek
    Link to comment

    Small amount of progress here.  I removed the nvidia plugin and rebooted and was greeted with a Local GUI.

    Re-installed the Nvidia plugin and rebooted, only to lose the local GUI again.

    Link to comment



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.