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.

[6.9.1] unRAID froze once again.

Featured Replies

I have posted a topic about it freezing before and I was instructed to keep a syslog going.  Please find attached last 500 lines of the log.  The freeze happened at ~17:11.

 

My previous topic can be found here.

 

I sure would like to get this resolved. 

 

 

freeze.log

Edited by numerica

  • Author

OK, I fixed the br3 DHCP issue and the samba election issue.  What I noticed from the logs is this:

 

Every once in a while, I don't know what it is or what it means, I get this in the logs :

 

May  1 05:23:47 Azat-NAS kernel: hpsa 0000:03:00.0: scsi 8:0:3:0: resetting physical  Direct-Access     ATA      Samsung SSD 860  PHYS DRV SSDSmartPathCap- En- Exp=1
May  1 05:23:59 Azat-NAS kernel: hpsa 0000:03:00.0: device is ready.
May  1 05:23:59 Azat-NAS kernel: hpsa 0000:03:00.0: scsi 8:0:3:0: reset physical  completed successfully Direct-Access     ATA      Samsung SSD 860  PHYS DRV SSDSmartPathCap- En- Exp=1

 

I think that's that HP SCSI driver `hpsa` resetting a disk and a few seconds later it completes the reset.  

 

However, when the system hung that process never finished:

 

May  7 17:10:27 Azat-NAS kernel: hpsa 0000:03:00.0: scsi 8:0:3:0: resetting physical  Direct-Access     ATA      Samsung SSD 860  PHYS DRV SSDSmartPathCap- En- Exp=1
May  7 17:10:32 Azat-NAS nmbd[17557]: [2021/05/07 17:10:32.620474,  0] ../../source3/nmbd/nmbd_incomingdgrams.c:302(process_local_master_announce)
May  7 17:10:32 Azat-NAS nmbd[17557]:   process_local_master_announce: Server UBUNTU at IP 192.168.3.84 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
May  7 17:10:32 Azat-NAS nmbd[17557]: [2021/05/07 17:10:32.620638,  0] ../../source3/nmbd/nmbd_become_lmb.c:150(unbecome_local_master_success)
May  7 17:10:32 Azat-NAS nmbd[17557]:   *****
May  7 17:10:32 Azat-NAS nmbd[17557]:   
May  7 17:10:32 Azat-NAS nmbd[17557]:   Samba name server AZAT-NAS has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.3.78
May  7 17:10:32 Azat-NAS nmbd[17557]:   
May  7 17:10:32 Azat-NAS nmbd[17557]:   *****
May  7 17:10:50 Azat-NAS nmbd[17557]: [2021/05/07 17:10:50.641126,  0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
May  7 17:10:50 Azat-NAS nmbd[17557]:   *****
May  7 17:10:50 Azat-NAS nmbd[17557]:   
May  7 17:10:50 Azat-NAS nmbd[17557]:   Samba name server AZAT-NAS is now a local master browser for workgroup WORKGROUP on subnet 192.168.3.78
May  7 17:10:50 Azat-NAS nmbd[17557]:   
May  7 17:10:50 Azat-NAS nmbd[17557]:   *****
May  7 17:18:06 Azat-NAS nginx: 2021/05/07 17:18:06 [error] 4363#4363: *6615103 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.3.80, server: , request: "GET /Main HTTP/1.1", upstream: 

 

So I this seems like the culprit here.  The hpsa driver is malfunctioning or the HP H240 HBA card that I am using is malfunctioning.  This issue did not happen in 6.8.7.  Perhaps it's the spinning down of drives?  I don't know, I'll experiment.

 

If anyone has any experience with this driver, how to update it, or any info whatsoever, please reply and let me know.  Thanks!  

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.