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.

pstmr

Members
  • Joined

  • Last visited

  1. Thanks again! I've sent a request for RMA, and following Gragorg's suggestion; asked if they'd send me a new drive immediately with possible deposit, until they receive the old one. If they don't want to do that, I'll go ahead and do new config to rebuild parity.
  2. Thanks guys, I'll go ahead and RMA. Just to clarify that I'm understanding this doc correctly: https://docs.unraid.net/legacy/FAQ/shrink-array/ So basically, the parity rebuild leaves the array with no safety-net for the duration of the rebuild - for both methods. Is that right? It just occurred to me that, while I don't have another 16 TB replacement drive, I do have some old 2TB drives kicking around. Could I as a temporary measure just clear, format and rebuild to one of those, and maintain parity while I wait for the postal service to do its thing? Or would that not work and the disk has to be able to account for every bit that was on the original drive, even if only 00000000?
  3. Just added a new Seagate 16TB drive to my Unraid. Initial zeroing took about one day, and went by without a hitch. Formatted the drive, and added it to the array. Then had time to move about 50GB onto it before Unraid warned me about SMART errors. So I cancelled the move and used unbalance to scatter everything off it. SMART overall-health self-assessment test result is PASSED... But here are the counters that errored: 5 Reallocated_Sector_Ct PO--CK 100 100 010 - 19 187 Reported_Uncorrect -O--CK 090 090 000 - 10 197 Current_Pending_Sector -O--C- 100 100 000 - 1 198 Offline_Uncorrectable ----C- 100 100 000 - 1 (full SMART log attached) At this point, the drive is completely empty and has 22 hours of total uptime.. Is it normal to have a few bad sectors, or should I just RMA the drive straight away, as is my immediate inclination? (my first time encountering SMART errors..) Additionally, some questions on how to proceed here: I don't have a replacement drive sitting around, so probably looking at 1-2 weeks for a replacement to arrive. In the meantime, can I just remove the faulty data drive from the array (again: it's empty, but not sure if parity "cares") or would I need to fully rebuild parity in that case anyway? Alternatively, could I safely run the array with one missing data drive? Then, once the replacement drive arrives, just put it back in and rebuild? (essentially rebuilding nothing as the drive is empty) Any suggestions on doing a secure wipe before RMA? nwipe? fs-smart-20250206-2048.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.