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.

[SOLVED] Should RMA?

Featured Replies

Hi All,

 

I am running unRAID Pro 4.7 with three WD EARS 2TB drives. I ran pre-clears on all the drives (no jumper, preclear_disk.sh 1.6 using the 'A'  option) and they checked out ok.

 

When I set the initial devices, the parity check begins and the data drives are successfully fotmated. At about 2-3% into the parity check, I start to get an error count on one of the drives. I stopped the check, opened the case and re-positioned the drive (by it's serial number) to use a different power plug and SATA cable.  I booted the array at which point the configuration was invalid so I ran 'initconfig' and re setup the devices and the parity check begun again. Again at about 2-3% into the check, the same drive starts accumulating an error count.

 

Syslog attached.

 

My question is, in your opinion, should I RMA this drive?

 

TIA,

Rick

syslog.zip

get a smart report on the drive, but it is getting lots of un-readable sector errors.

 

Look for sectors pending re-allocation, or sectors already re-allocated.

 

Then, make your decision if an RMA is warranted.

  • Author

Thanks Joe,

 

SMART report attached. I did not know which options to use with 'smartctl' so I used '--all'

 

I also tried '--test=short' and '--test=long' but both of those commands came back to the shell prompt immediately without reporting anything.

 

I cannot tell for sure if the drive is bad but it looks like it.

 

What do you think?

 

Rick

smartctl.txt

there are 204 sectors pending re-allocation, but none have been re-allocated as of yet, since they have not yet been written.

197 Current_Pending_Sector  0x0032  200  200  000    Old_age  Always      -      204

 

The "long" ans "short" tests initiate those respective tests.  You must get a status report after waiting for their completion.

However, both have aborted on the first "read" failure they encountered.

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error

# 1  Short offline      Completed: read failure      90%        41        124593828

# 2  Extended offline    Completed: read failure      90%        41        124593831

# 3  Extended offline    Completed: read failure      90%        41        124593824

 

Basically, time to RMA the drive.

  • Author

Joe,

 

Thanks again for the speedy analysis.

 

I will RMA.

 

Rick

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.