Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Regularly Not able to Access Web UI

Featured Replies

I've been using unraid for years and never had any issues. Configuration has always been the same. Recently I had an issue where my flash drive was accidentally formatted and I had to re-set up the server.

 

Since that point, I am getting regular issues where the Web UI becomes unresponsive and I am unable to access the server. During this time, shares become unresponsive and cause my media players to freeze/hang.

 

* I am unable to access any disk shares or user shares.

* I can access the FLASH share through SMB.

* I am still able to access any the plugins I use (SABnzbd, Sickbed and Transmission)

 

The only thing I can do is to power off the server with the power button. Before I did this I made a copy of the diagnostics which is attached to this thread. When the server boots back up it has no connection to the internet until it is restarted correctly through the web ui again.

 

Can anyone please help pinpoint the issue as I'm not really sure what I'm looking for in the logs?

 

I'm getting it in the neck from the other half as it always seems to happen when she wants to watch something.  ::)

tower-diagnostics-20160910-0559.zip

  • Community Expert

If enable disable array autostart by editing disk.cfg on your flash drive (in the config folder):

 

change startArray="yes" to "no"

 

Then start in maintenance mode and run xfs_repair on disk4.

  • Author

Output from xfs_repair on disk 4

 

Phase 1 - find and verify superblock...

Phase 2 - using internal log

        - zero log...

        - scan filesystem freespace and inode maps...

        - found root inode chunk

Phase 3 - for each AG...

        - scan (but don't clear) agi unlinked lists...

        - process known inodes and perform inode discovery...

        - agno = 0

        - agno = 1

        - agno = 2

        - agno = 3

        - process newly discovered inodes...

Phase 4 - check for duplicate blocks...

        - setting up duplicate extent list...

        - check for inodes claiming duplicate blocks...

        - agno = 0

        - agno = 1

        - agno = 2

        - agno = 3

No modify flag set, skipping phase 5

Phase 6 - check inode connectivity...

        - traversing filesystem ...

        - traversal finished ...

        - moving disconnected inodes to lost+found ...

Phase 7 - verify link counts...

No modify flag set, skipping filesystem flush and exiting.

  • Community Expert

You have to remove -n from the xfs_repair command to enable repair mode.

  • Community Expert

Just noticed your diagnostics are from September, wrong zip?

  • Author

That was the only diagnostics on the system so I can only presume I've done something incorrectly if it's from September. I'll have to wait until the next time the GUI goes down again I guess.

 

I have re-run xfs_repair without the -n option with the below results.

 

Phase 1 - find and verify superblock...

Phase 2 - using internal log

        - zero log...

        - scan filesystem freespace and inode maps...

        - found root inode chunk

Phase 3 - for each AG...

        - scan and clear agi unlinked lists...

        - process known inodes and perform inode discovery...

        - agno = 0

        - agno = 1

        - agno = 2

        - agno = 3

        - process newly discovered inodes...

Phase 4 - check for duplicate blocks...

        - setting up duplicate extent list...

        - check for inodes claiming duplicate blocks...

        - agno = 0

        - agno = 1

        - agno = 2

        - agno = 3

Phase 5 - rebuild AG headers and trees...

        - reset superblock...

Phase 6 - check inode connectivity...

        - resetting contents of realtime bitmap and summary inodes

        - traversing filesystem ...

        - traversal finished ...

        - moving disconnected inodes to lost+found ...

Phase 7 - verify and correct link counts...

  • Community Expert

Diags showed corruption on disk4, but since they're from September it has probably already been fixed, no harm done but you need to post current diagnostics when the issue manifest again.

  • Author

I'm not sure how long it's been down but I could not access the Web UI again this evening when I arrived home from work.

 

My son tried to watch some cartoons, the 'Media' share appears unresponsive. Trying to access from within my media players causes them to not respond. I also cannot view this share from within the finder on my MacBook.

 

pps are still working fine it's just the Unraid page thats not responding.

 

Hopefully I've attached the right diagnostics this time

tower-diagnostics-20161028-1006.zip

  • 3 months later...
  • Author

Good evening All,

 

I was wondering if anyone might be able to help me with this issue as it's still going on now.

 

I have attached a fresh diagnostics log to this post.

 

Server was not responding, could not access shares and media player would lock up and become unresponsive when trying to play a file. Unable to login to WebGUI. SSH'd into the server and took diagnostics.

 

I then powered the server off using the power button on the front of the machine (I still do not know how to power off safely using the command line, there are so many conflicting posts on the issues searching has not helped)

 

When i powered the machine on I was still unable to reach the WenGUI. I tried to log in via SSH and Telnet but both were not working.

 

I am unsure how to proceed now so I have powered down there machine and removed USB stick to transfer diagnostics here again in the hope of receiving some assistance.

 

Thanks,

 

Jason

tower-diagnostics-20170129-1410.zip

One thing I notice is that your NIC is only running at 100 Mb/s - has been since 28th October. Check the cable and the switch port.

 

  • Author

Hi John,

 

The server is always on 100 Mb/s at the moment. I have moved and not got round to wiring the house with gigabit cable yet. I am aware of this.

 

This should not make my web interface stop responding though.

 

Thanks,

 

Jason

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.