My machine has been acting up and i cannot get the gui to load at all. I figured i would run diagnostics but since i cant access the gui i obviously cannot do that. Is there a way to manually run diagnostics from the command line? 

Yes, just type   diagnostics  on the command line.   You will find the file in the logs directory on your Flash Drive.

So, any suggestions if running diagnostics has taken ~18 minutes so far and nothing is being generated?

It took about thirty seconds to one minute on my Test Bed server.  This is the output on the screen.
 

diagnostics
Starting diagnostics collection... done.
ZIP file '/boot/logs/rose-diagnostics-20170522-1013.zip' created.

What are you seeing?

 

EDIT:  How much memory do you have?  I think everything is done in RAM up to the final zipping of the file.

Edited May 22, 20179 yr by Frank1940

root@Storage:~# diagnostics
Starting diagnostics collection...

Been running since about 1 minute after your first post

I modified my original post with this question.  (I think we cross posted.)   How much memory do you have?  I think everything is done in RAM up to the final zipping of the file.

32 gigs

All assigned as available to the server or have you allocated some to VM's or Dockers?   (It could be that your Flash Drive is not writable.)

 

Why are you using the command line?   I can only assume that you have other issues and the GUI is not available.  Can you access the shares? 

I was able to access the shares, was unable to access the gui or any running containers. Just hooked a monitor up to the box and saw a Disabling IRQ #18 message on the screen. Not sure what that means and without logs im not sure if im going to be able to figure out what the hell happened. 

Edited May 22, 20179 yr by hermy65

Importance of an IRQ getting disable depends on what's using it, after reboot type:

 

cat /proc/interrupts

 

And check what's using IRQ18

I downgraded to 6.3.3 prior to seeing your message to see if that helps. This is what i see using your command above

 

18:     601755       7851       7386       8481       9263      12039       8049       7874  IR-IO-APIC  18-fasteoi   i801_smbus, eth0

 

Well that didnt help. Machine was up for 3-4 minutes then the Disabling IRQ #18 happened again and everything went unresponsive. Should i make a new post about this since its not really the same issue as the thread title suggests?

NIC is using IRQ18, if it's not onboard try another slot.