can you tell me why Gui isnt accesable till Array Online on Reboot

[comet424]

hi can you guys tell me still haven't figured it out after months..

one.. what is the File Checking on the Console side before the login is doing takes 2 mins  it says

 

and second even though I get the Login on console.. the GUI is inaccesable till the Array is Online..  this shouldn't be 

 

where do I look I tried googling..  but nothing.. but where do I look that causes the 2 min whatever... and why the gui doesn't let you do anything till Array is online

 

[itimpi]

You get an initial delay before the console prompt as UnRAID is loaded into RAM and hardware detection is carried out.

 

The next delay will be after the core Linux underlying Unraid is ready (which is when the console prompt appears) as UnRaid carries out the remainder of the boot process and  Is mounting the array and starting up the underlying system services.    If you do not have the array set to autostart then you get access to the GUI earlier but then have to manually start the array and get a delay at that point.

[comet424]

ah ok..  the first one is the Xfered  it does a 13 meg test 2 different tests but Xfered   %  and shows timer and takes 2 min.. what exactly is that..  I don't have a picture...    whats it scanning my memory or the flash drive or something?

 

yes I have it autostart

when the console login pops up the gui can take 5 min after the login shows..  before its accessible.. but in past  it would load up the gui and I would see it saying   "Mounting the Array"   and starting services   like it used to boot faster..  but I been upgrading my hard drives from 2tb to 12tb so does also  making bigger hard drives slow down the gui...

 

I just don't know why it takes a lot longer to get to the gui then in the past  like the older version of unraid 5 whatever..  when I got to the gui  it would say starting array.. but now it seems  the gui will only show up after the array is started.. and not before the array is started on an auto..

 

but from what your saying I guess its normal  that the gui doesn't show up till after the array is started..... I just remember how in past it was a lot faster  and never had to wait till after the array was started...

 

I did just upgrade my SSD cache drive from my SATA 560mb  WD as I was having issue... so went with a NVME Gen 3  3500mb/3000   and In windows I get 3500mbs  and unraid I get 2500  not sure … and was hoping the faster nvme load up the GUI faster too..  so I just typically  walk away  if I do a reboot and come back 10-15min    used to be only a 2-3 min if after a reboot  the gui would pop up... and not sure if its a AMD Ryzen  X570 issue  as my older board a Intel cpu  booted to gui faster. 

 

but always learning something new everyday

[JonathanM]

2 hours ago, comet424 said:

the first one is the Xfered  it does a 13 meg test 2 different tests but Xfered   %  and shows timer and takes 2 min.. what exactly is that..  I don't have a picture...

Sounds like you may have rclone installed, and it's downloading a fresh copy from the internet.

[comet424]

oh ok I I just uninstalled it.. don't even know how to use it..   was hoping at the time.. a backup that backed up my hpone  like google photos does  automatically wanted my phone to do that with unraid..

 

so  ill try a reboot and see if its gone..

 

maybe one of the other plugins I installed is reason why the gui doesn't populate  that the plugins are running after  the login console screen and not before

 

Edited June 10, 2020 by comet424

[comet424]

@Jonathan  that fixed it..  

but do you happene to know..

on the colsoe side its showing 2 errors before the login

error: failed to connect to the hypervision

error: failed to connect to '/var/rub/libvirt/libvirt-sock': no such file or directory

do you know what those errors mean I realize  no file  but is this a red error or a just a warning. how I fix? and hyperversion  I have it set for VMs  so isn't that the same

 

and the errors I got are in syslog  not sure which ones serious as some cant be found it says  and can any of these be fixed  or are they all normal

 

Jun 10 11:27:04 Tower kernel: tsc: Fast TSC calibration failed
Jun 10 11:27:04 Tower kernel: ACPI: Early table checksum verification disabled
Jun 10 11:27:04 Tower kernel: pci 0000:04:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit]
Jun 10 11:27:04 Tower kernel: pci 0000:04:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit]
Jun 10 11:27:04 Tower kernel: pci 0000:03:02.0: BAR 14: failed to assign [mem size 0x00600000]
Jun 10 11:27:04 Tower kernel: pci 0000:04:00.0: BAR 6: failed to assign [mem size 0x00080000 pref]
Jun 10 11:27:04 Tower kernel: pci 0000:04:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit]
Jun 10 11:27:04 Tower kernel: pci 0000:04:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit]
Jun 10 11:27:04 Tower kernel: pci 0000:04:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit]
Jun 10 11:27:04 Tower kernel: pci 0000:04:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit]
Jun 10 11:27:04 Tower kernel: pci 0000:02:00.0: BAR 14: failed to assign [mem size 0x00b00000]
Jun 10 11:27:04 Tower kernel: pci 0000:03:02.0: BAR 14: failed to assign [mem size 0x00600000]
Jun 10 11:27:04 Tower kernel: pci 0000:03:05.0: BAR 14: failed to assign [mem size 0x00100000]
Jun 10 11:27:04 Tower kernel: pci 0000:03:08.0: BAR 14: failed to assign [mem size 0x00200000]
Jun 10 11:27:04 Tower kernel: pci 0000:03:09.0: BAR 14: failed to assign [mem size 0x00100000]
Jun 10 11:27:04 Tower kernel: pci 0000:03:0a.0: BAR 14: failed to assign [mem size 0x00100000]
Jun 10 11:27:04 Tower kernel: pci 0000:04:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit]
Jun 10 11:27:04 Tower kernel: pci 0000:04:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit]
Jun 10 11:27:04 Tower kernel: pci 0000:04:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit]
Jun 10 11:27:04 Tower kernel: pci 0000:04:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit]
Jun 10 11:27:04 Tower kernel: pci 0000:05:00.0: BAR 4: failed to assign [mem size 0x00004000 64bit]
Jun 10 11:27:04 Tower kernel: pci 0000:05:00.0: BAR 2: failed to assign [mem size 0x00001000 64bit]
Jun 10 11:27:04 Tower kernel: pci 0000:06:00.1: BAR 0: failed to assign [mem size 0x00100000 64bit]
Jun 10 11:27:04 Tower kernel: pci 0000:06:00.3: BAR 0: failed to assign [mem size 0x00100000 64bit]
Jun 10 11:27:04 Tower kernel: pci 0000:07:00.0: BAR 5: failed to assign [mem size 0x00000800]
Jun 10 11:27:04 Tower kernel: pci 0000:08:00.0: BAR 5: failed to assign [mem size 0x00000800]Jun 10 11:27:04 Tower kernel: floppy0: no floppy controllers found
Jun 10 11:27:04 Tower kernel: random: 7 urandom warning(s) missed due to ratelimiting
Jun 10 11:27:04 Tower kernel: ccp 0000:0b:00.1: psp initialization failed
Jun 10 11:27:07 Tower rpc.statd[1981]: Failed to read /var/lib/nfs/state: Success
Jun 10 11:27:19 Tower kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20180810/utaddress-204)
Jun 10 11:27:20 Tower root: Interface "tunl0" added. Warning: no bandwidth limit has been set.
Jun 10 11:27:20 Tower root: Interface "ip_vti0" added. Warning: no bandwidth limit has been set.
Jun 10 11:27:20 Tower root: Interface "gretap0" added. Warning: no bandwidth limit has been set.
Jun 10 11:27:20 Tower root: Interface "br0" added. Warning: no bandwidth limit has been set.
Jun 10 11:27:20 Tower root: Interface "gre0" added. Warning: no bandwidth limit has been set.
Jun 10 11:27:20 Tower root: Interface "erspan0" added. Warning: no bandwidth limit has been set.
Jun 10 11:27:20 Tower root: Warning: parse_ini_file(/var/local/emhttp/var.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php on line 56
Jun 10 11:27:20 Tower root: Warning: Division by zero in /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php on line 62

 

[itimpi]

The parity.check.tuning warning is harmless (and will be fixed when I release the multi-language compatible version).    The hypervisor message probably relates to the VM backup olugin if you have that installed.

[comet424]

ah ok  cool

ya I installed the VM backup other day.. haven't used it yet.. as I saw its a backup for my VMS but that's probably same as the CA Backup

and do you happened to know any of these other errors..  or what the libvirt-sock is?  is that a socket? like a port 

I thought the libvirt was the hot plug plugin in  I uninstalled it and rebooted.. but error was still there so that wasn't it

 

but thanks for the help so far..  least  I know that parity is ok.. 🙂

 

Edited June 10, 2020 by comet424