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.

blocker85

Members
  • Joined

  • Last visited

Everything posted by blocker85

  1. Just closing the loop on this. After the comment by JorgeB, I re-seated all sata power connectors and replaced the sata cables connected to the motherboard. I then reassigned the parity drive to parity2. Everything has been running fine for the last week. Thanks!
  2. Thanks for responding! After the Drive entered an error state a couple of times, I assigned it to Parity1, not realizing that the parity drives are not interchangeable. Good to know. I'll assign it back to Parity2 I'll swap out the Sata cables to see if that changes anything. I can also grab a new sata power connector as well to see if that's the issue. I'm currently running the power connector off of a molex port, for two drives only. The remaining six drives are on a dedicated Sata power cable. Not sure if that creates a potential issue.
  3. So, my unraid array has been running nearly issue free for years. But, it was time to expand storage, so I recently bought three 16TB drives, one to replace my aging parity drive, one to replace an old 2tb drive, and a third for when another drive goes bad. All my drives currently run off of a pcie SATA breakout board, but the new parity drive is utilizing one of the on-board SATA ports. When adding the new parity drive, I stopped the array, assigned the new parity drive as "Parity 2" and started the array. It took about two days, but it looks like it successfully completed the parity operation to make the 16tb drive a party drive. I then stopped the array, unassigned the old "Parity 1" drive, added the old parity drive as an array disk and started the array again. Within minutes, the new parity drive showed tens of millions of errors and the drive fell into an error state. Since then, any time I try to bring the array online, the drive errors out and I typically cannot even bring the array offline without doing a hard reset. I feel like I'm probably missing something obvious, but I'm still a relative noob on server maintenance, so I'm here to consult the experts. Help! Diagnostics attached. Appreciate any insight you can provide. Thanks all. tower-diagnostics-20231111-1025.zip
  4. I have a dual E5-2650 server and when I check the available features of the cpu via the unraid terminal, it does not indicate that it supports SSE4.2. Am I basically out of luck for creating a Mojave VM?

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.