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.

Unraid Array broken - Can't open logs

Featured Replies

My temperatures have been really high since my house does have AC and I can't open the windows due to air quality. So I have been trying to watch my Unraid stuff. Then it just stopped working. My errors spiked on my parity and then stuff hit the fan. 

 

So if you look at the Screenshots the logs are taking up all the ram (at least I think). I also just can't open logs to see what happened. I closed the Array but it's still stopping. I'm afraid to reboot the system because I have no idea what's going on. I think I missed information but can't tell as I'm freaking out a little haha. Any advise would be amazing. I can answer any questions to help. 

I have ordered new drives incase I need to make any swaps. Also got a new case on the way to try to help with airflow. Again any advise would be amazing!!!

chrome 2020-10-04 at 22.41.10.png

chrome 2020-10-04 at 22.41.30.png

  • Community Expert

See if you can get the diags on the console by typing "diagnostics", then attach them here.

  • 2 weeks later...

Similar. 

zjk559pjzqt51.png?width=507&format=png&a

 

Also, the terminal window will not open past a certain point of log fullness. You can type but the window refreshes before you can do anything.

 

Just rebooted so I could do something but syslog right now is just boot messages. 

 

I do seem to have a LOT of onboard clock drift. I've seen it be off by hours pretty quickly. Replaced CMOS battery.

 

Edit 2:

Oops. Somehow I had both interfaces enabled on my T310 and bonding enabled. Mind you, the second port wasn't even plugged in so I didn't think much about it. That's probably it.

 

Edit: 

 

Hmm. Oct 17 19:52:56 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:52:56 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:52:56 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:52:56 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:52:56 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:52:56 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:52:56 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:52:56 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:52:57 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:52:57 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:01 BlackTower kernel: net_ratelimit: 39 callbacks suppressed Oct 17 19:53:01 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:01 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:01 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:01 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:01 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:01 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:02 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:02 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:02 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:02 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:06 BlackTower kernel: net_ratelimit: 37 callbacks suppressed Oct 17 19:53:06 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:06 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:06 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:06 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:07 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:07 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:07 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:07 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:07 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0) Oct 17 19:53:07 BlackTower kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:85:cc:ac, vlan:0)

Edited by RealActorRob
Add log data.

  • Community Expert

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread,

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.