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.

New rig and some warnings in syslog

Featured Replies

Building out my new rig and getting ready to start moving data.  I see these warnings in the syslog.  Are any of concern?

 

Quote

Mar 30 08:43:14 Tower kernel: ACPI: Early table checksum verification disabled
Mar 30 08:43:14 Tower kernel: acpi PNP0A08:00: _OSC failed (AE_SUPPORT); disabling ASPM
Mar 30 08:43:14 Tower kernel: acpi PNP0A08:00: ignoring host bridge window [mem 0x000c0000-0x000dffff window] (conflicts with Adapter ROM [mem 0x000db000-0x000e33ff])
Mar 30 08:43:14 Tower kernel: ACPI: \: failed to evaluate _DSM (0x1001)
Mar 30 08:43:14 Tower kernel: pci_bus 0000:7f: busn_res: can not insert [bus 7f-ff] under domain [bus 00-ff] (conflicts with (null) [bus 00-7f])
Mar 30 08:43:14 Tower kernel: pci_bus 0000:7f: busn_res: can not insert [bus 7f] under domain [bus 00-ff] (conflicts with (null) [bus 00-7f])
Mar 30 08:43:14 Tower kernel: floppy0: no floppy controllers found
Mar 30 08:43:14 Tower kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0
Mar 30 08:43:14 Tower kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1
Mar 30 08:43:14 Tower kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0
Mar 30 08:43:14 Tower kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1
Mar 30 08:43:14 Tower kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0
Mar 30 08:43:14 Tower kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1
Mar 30 08:43:14 Tower kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0
Mar 30 08:43:14 Tower kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1
Mar 30 08:43:20 Tower rpc.statd[1970]: Failed to read /var/lib/nfs/state: Success
Mar 30 08:43:28 Tower avahi-daemon[6608]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Mar 30 08:43:29 Tower root: error: webGui/include/ProcessStatus.php: wrong csrf_token

 

Are you running a program called Margarita on a PC by chance? This is know to cause a similar error.

  • Author
3 minutes ago, ashman70 said:

Are you running a program called Margarita on a PC by chance? This is know to cause a similar error.

 

Never heard of it.

Its a third party program people use to do basic monitoring of their unRAID server. If you aren't using it then something else is causing that error.

  • Author

Possibly the preclear disk plugin?  I think that may have been it.  I have since removed it and do not see the error.

 

What about the warnings (yellow).  Normal stuff?

2 hours ago, johnodon said:

What about the warnings (yellow).  Normal stuff?

 

All normal stuff.  Sometimes, a motherboard BIOS update can remove a couple of them, but everyone has lines like those.

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.