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 Locking Up

Featured Replies

Woke up this morning to find my shares unavailable, the GUI had reverted to the light theme, and my flash drive showing under both Flash and Unassigned Devices. Did a clean reboot through the GUI, it wanted to start a parity check, and then the system locked up at about 2%. No errors on the screen. Only option was to force reboot. Same thing happened; obviously an unclean shutdown was detected so a parity check was triggered, and the system locked up at about 2% again. Shutdown the box, swap the flash drive for a brand new one after testing it, and the same thing happens again, right around the 2% mark of the parity check. Reboot one more time, left the array down, and downloaded diagnostics, which are attached. Temps are fine, no errors in syslog, and I cannot see anything that could be causing this. Was thinking of leaving everything else in my network that uses the unRAID shares offline and starting up the array with a parity check again, but wanted to post here first. Any/all help is greatly appreciated.

morgoth-diagnostics-20180624-1535.zip

  • Author

It just happened again. This time with the array stopped and literally nothing happening. I made no changes and didn't perform any actions.

  • Author

Ok, oddly enough it just recovered without me doing anything. Attaching new diagnostics, but I think the most relevant thing is the following from the syslog:

 

Jun 24 15:34:41 Morgoth kernel: i801_smbus 0000:00:1f.3: Timeout waiting for interrupt!
Jun 24 15:34:41 Morgoth kernel: i801_smbus 0000:00:1f.3: Transaction timeout
Jun 24 15:37:11 Morgoth kernel: i801_smbus 0000:00:1f.3: Timeout waiting for interrupt!
Jun 24 15:37:11 Morgoth kernel: i801_smbus 0000:00:1f.3: Transaction timeout
Jun 24 15:37:11 Morgoth kernel: w83795 0-002f: Failed to read from register 0x02f, err -110
Jun 24 15:40:13 Morgoth kernel: i801_smbus 0000:00:1f.3: Timeout waiting for interrupt!
Jun 24 15:40:13 Morgoth kernel: i801_smbus 0000:00:1f.3: Transaction timeout
Jun 24 15:40:13 Morgoth kernel: w83795 0-002f: Failed to read from register 0x03c, err -110
Jun 24 15:40:58 Morgoth kernel: i801_smbus 0000:00:1f.3: Timeout waiting for interrupt!
Jun 24 15:40:58 Morgoth kernel: i801_smbus 0000:00:1f.3: Transaction timeout
Jun 24 15:40:58 Morgoth kernel: w83795 0-002f: Failed to read from register 0x013, err -110
Jun 24 15:43:33 Morgoth kernel: w83795 0-002f: Failed to read from register 0x03c, err -6
Jun 24 15:43:33 Morgoth kernel: w83795 0-002f: Failed to read from register 0x015, err -6
Jun 24 15:43:33 Morgoth kernel: w83795 0-002f: Failed to read from register 0x03c, err -6
Jun 24 15:43:33 Morgoth kernel: w83795 0-002f: Failed to read from register 0x016, err -6
Jun 24 15:47:14 Morgoth kernel: i801_smbus 0000:00:1f.3: Timeout waiting for interrupt!
Jun 24 15:47:14 Morgoth kernel: i801_smbus 0000:00:1f.3: Transaction timeout
Jun 24 15:47:14 Morgoth kernel: w83795 0-002f: Failed to read from register 0x02f, err -110

 

morgoth-diagnostics-20180624-1556.zip

12 minutes ago, tronyx said:

reverted to the light theme, and my flash drive showing under both Flash and Unassigned Devices

This would mean that your flash drive dropped offline, then re-connected itself.  Try a different port.  Ideally USB2

  • Author
1 minute ago, Squid said:

This would mean that your flash drive dropped offline, then re-connected itself.  Try a different port.  Ideally USB2

 

That's what I was thinking, but wanted to post here first since I've already rebooted a few times. Will try another port and see what happens. This system only has USB 2.0.

  • Author
39 minutes ago, Squid said:

This would mean that your flash drive dropped offline, then re-connected itself.  Try a different port.  Ideally USB2

 

Alright, swapped USB ports, brought it online, mucked around in settings and whatnot for about 20 minutes to get it to read and write to the flash drive and it's been stable so I started the array. Array came online and did NOT require a parity check so that might be a better sign that things are ok. I'll take it slow with starting up other services on the network for now.

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.