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.

stanh

Members
  • Joined

  • Last visited

  1. I just found the problem. Syslog was being written to local folder on SYSTEM which was on disk 1. When I changed the local syslog folder to be saved in APPDATA (which I moved to the cachepool) disks spin down. All good now.
  2. Ok. I have just changed the system and appdata settings to primary on cache and used Mover to move them to cache. Still no spin down of disk 1 and parity. Where are those share use cache settings? (Note: I have docker and VM services turned off (my hardware can't even do VMs anyway).
  3. Sorry. Here it is. tower-diagnostics-20240313-1901.zip
  4. I have a 4 disk array: 1 parity + 3 data disks, all sata attached to the motherboard (an old Intel DG31, core 2 duo, 4GiB ram). Running unraid 6.12.8. All settings at default. The parity disk and 1 data disk never spin down except with a manual spin down whereupon they spin right back up. File activity plugin reports no activity. No Docker or VM services running. The data disk has a variety of data including systems data. It also has has mac os Time Machine on it but even with that turned off still have the no spin down problem. The other two data disks as well as the ssd in the cache pool spin down as expected.
  5. Thanks. That parity drive did have some unclean shutdowns last week due to a failed graphics card but none recently. In any event, I just pulled that parity drive to put in a larger one and plan to use the smaller old parity drive as a data drive. Man, does it take a long time to resync and resilver drives - at least 24 hrs for the new 8TB parity and repurposing the old 5TB.
  6. Parity check is finding 2 errors after two complete runs (run without error correction). I can't see any errors in the diagnostic sys logs (attached). Are the parity check errors stored in some other log? Also why does the array show "parity is valid" even though there are 2 errors? Note: I have run an extended smart test on the single parity drive and it passed with no errors. Short tests only run on data disks and no errors. Am I correct that I shouldn't upgrade any disks until the errors are cleared? tower-diagnostics-20240303-1444.zip

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.