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.

Command line login loop and hanging GUI

Featured Replies

Having an issue with my previously working server. The sequence of events is as follows.

Friday

  • Installed new mobo, CPU, RAM, and a new 14TB drive

  • Updated apps and dockers that needed updates

  • Started preclear of drive to add to array

Saturday

  • Woke up and the server was unreachable, monitor just showed black screen, no command line.

  • Did a hard reboot. Server booted into GUI mode with no issues.

  • Started the preclear again. Preclear finished and the drive was added to the array.

  • Server working fine, dockers were launched everything was working.

Monday

  • Wake up and the server is once again unreachable. The monitor shows the GUI but it's totally frozen. Hard reboot.

  • Server boots up into the command line but seems to be stuck in a login loop, when I try to run any commands such as "diagnostics" it just asks me to login again

  • Tried to boot into the GUI but it's just a black screen.

  • When I try to reach the server from another computer to view the web GUI it asks me to create a new password. When I type in the password and click "set password" the webpage hangs.

  • Got into the command line and saw this error

    • malloc: jobs.c:1435: assertion botched

      free: start and end chunk sizes differ

      Aborting...

  • It was hung on aborting for about 5 minutes, I CTRL+C and was able to get back to the login line, logged in a few times and was eventually able to run "powerdown" in command line.

I have attached syslog and some photos. My research seems to suggest there may be a bad plugin? but wanted some confirmation before I start trying to delete corrupt files or something.

PXL_20250617_151354729.MP.jpg

PXL_20250617_155409286.MP.jpg

PXL_20250617_150209520.MP.jpg

syslog

  • Community Expert

By the description, looks more like a hardware issue, but you can reboot in safe mode to rule out any plugins.

  • Author
36 minutes ago, JorgeB said:

By the description, looks more like a hardware issue, but you can reboot in safe mode to rule out any plugins.

Boot into safe mode was successful. I can't boot into the GUI in safe mode. Still get black screen but command line safe mode and the web GUI works. I got a diagnostics file out and have attached it here.

tower-diagnostics-20250617-1516.zip

  • Community Expert

If it boots in safe mode it suggests a plugin is the issue, uninstall or disable them all and retest in normal mode.

  • Author

Ok I disabled almost all of the plugins except Appdata Backup. I'm assuming as it's such a well used plugin that it's not the issue. The server boots, still won't boot into the GUI (just a black screen with a blinking cursor) but I can access it from the web GUI. I can start the array just fine but when I go to start dockers some of them start and some just don't and then eventually the web GUI becomes unresponsive and I have to reboot. I updated to 7.0.13, thinking maybe there was a bug fix. Managed to pull some diagnostics before the last freeze-up. I was removing the plugins in batches and before I removed the unraid connect plugin the server booted but gave me a "The Unraid API is currently offline" message. Not sure if that's related.

I'm at a loss here, it seems like something fundamental is broken.

tower-diagnostics-20250618-1649.zip

  • Community Expert

GUI boot mode not working is a separate issue, typically related to the GPU.

Btrfs is detecting data corruption and there are also some segfaults, so start by running memtest.

  • Author

Ok memtest identified a bad stick. I have gotten new RAM but is there anything I need to be doing before or after I replace it? Should I run a memtest again or can I just install the new RAM and boot up as normal?

  • Community Expert

I'd suggest running memtest for 24hours to rule out any more bad ram.

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
Reply to this topic...

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.