Woke up to some errors, any help would be greatly appreciated, I can't google around till I get off work. 

 

Event: unRAID Parity disk error

Subject: Alert [FATJOE] - Parity disk in error state (disk dsbl)

Description: 2001b4d210fb10816 (sdf)

Importance: alert

 

Event: unRAID array errors

Subject: Warning [FATJOE] - array has errors

Description: Array has 13 disks with read errors

Importance: warning

 

Parity disk - 2001b4d210fb10816 (sdf) (errors 328)

Disk 1 - 2001b4d210fb10804 (sda) (errors 332)

Disk 2 - 2001b4d210fb10827 (sdn) (errors 318)

Disk 3 - 2001b4d210fb10823 (sdj) (errors 318)

Disk 4 - 2001b4d210fb10812 (sde) (errors 318)

Disk 5 - 2001b4d210fb10821 (sdh) (errors 318)

Disk 6 - 2001b4d210fb10822 (sdi) (errors 318)

Disk 7 - 2001b4d210fb10825 (sdl) (errors 318)

Disk 8 - 2001b4d210fb10826 (sdm) (errors 318)

Disk 9 - 2001b4d210fb10810 (sdc) (errors 318)

Disk 10 - 2001b4d210fb10811 (sdd) (errors 318)

Disk 11 - 2001b4d210fb10820 (sdg) (errors 318)

Disk 12 - 2001b4d210fb10824 (sdk) (errors 318)

 

 

 

You might want to run diagnostic.

Ok I'll look up how to do so thanks.

diag attached

fatjoe-diagnostics-20160808-1217.zip

It's quite unusual for 12 disks to have errors at the same time like this - looks like all 12 disks have dropped offline.

I recommend waiting for johnnie black to have a look. He's the resident storage problem expert.

 

My guess is your sata controller card has dropped dead / wonky.

This looks like a controller issue, try re-seating it.

It's quite unusual for 12 disks to have errors at the same time like this - looks like all 12 disks have dropped offline.

I recommend waiting for johnnie black to have a look. He's the resident storage problem expert.

 

My guess is your sata controller card has dropped dead / wonky.

 

yea thats weird.. i can still access my file shares..

 

 

This looks like a controller issue, try re-seating it.

 

re-seating the controller or the parity drive?

 

if parity drive, i should still take down the server correct?

is it safe to take down in the server at its current state?

 

Controller, all your disks have read errors.

Ok thanks, I'll take it offline when I get home. Will update when it comes back.

Then you'll have to do a new parity sync, your Areca doesn't pass SMART info, so can't advise on the disks health, try first on the current parity disk.

Ok thanks. I'll look up how to do the parity sync.

ok powered down and re-seated the card and drives.

 

brought it back up and got this via email and on the dashboard.

 

Event: unRAID array errors

Subject: Notice [FATJOE] - array turned good

Description: Array has 0 disks with read errors

Importance: normal

 

but still have a red X next to the Parity that states its disabled.. and i cant find an option to turn it on or run the parity sync..

 

 

smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.18-unRAID] (local build)

Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

 

=== START OF INFORMATION SECTION ===

Vendor:              Seagate

Product:              ST4000VN000-1H41

Revision:            R001

User Capacity:        4,000,787,030,016 bytes [4.00 TB]

Logical block size:  512 bytes

Rotation Rate:        10000 rpm

Logical Unit id:      0x001b4d210fb10816

Serial number:        Z30134J4

Device type:          disk

Transport protocol:  Fibre channel (FCP-2)

Local Time is:        Mon Aug  8 16:58:40 2016 CDT

SMART support is:    Available - device has SMART capability.

SMART support is:    Enabled

Temperature Warning:  Disabled or Not Supported

 

=== START OF READ SMART DATA SECTION ===

SMART Health Status: OK

 

Current Drive Temperature:    30 C

Drive Trip Temperature:        25 C

 

Manufactured in week 30 of year 2002

Specified cycle count over device lifetime:  4278190080

Accumulated start-stop cycles:  256

Elements in grown defect list: 0

 

Error counter log:

          Errors Corrected by          Total  Correction    Gigabytes    Total

              ECC          rereads/    errors  algorithm      processed    uncorrected

          fast | delayed  rewrites  corrected  invocations  [10^9 bytes]  errors

read:          0        0        0        0          0          0.000          0

write:        0        0        0        0          0          0.000          0

 

Non-medium error count:        0

 

Device does not support Self Test logging

 

attached is the diag

fatjoe-diagnostics-20160808-1642.zip

Stop array, assign parity disk, start array to begin parity sync.

Sorry, you need to unassign it first so it's:

 

stop array, unassign parity, start array, stop array, reassign parity and start array to begin sync.

no change when i stopped the array. it showed up as assigned but still disabled. i changed it to none then back to the disk. when i put it back up its still disabled with no parity disk check

 

Sorry, you need to unassign it first so it's:

 

stop array, unassign parity, start array, stop array, reassign parity and start array to begin sync.

 

that did it sync started!! thank you very much!!!

 

do you accept donations?

 

does the logs indicate if anything is failing? should i be worried?

No problem, the only issue appears to have been the controller, if it fails again in the future you may need to replace it, but most likely it's fine.

thanks again sooo very much..

 

ok im having some serious problems now.. so the unraid is turning itself off. if i power the VM back up it cannot see any of the disk.

 

i have to shutdown unraid then reboot the ESXi host then power up unraid for it to see the disks, then unraid starts the parity sync all over again.

 

this have been running solid for over a year.. the only thing that have changed recently with in unraid was that i installed a number of plugins. i have since removed all plugins rebooted unraid and brought it back up to start another sync.. i'm hoping this is the last..

 

i've attached logs from unraid and also logs from the card ..

 

fatjoe-diagnostics-20160809-1858.zip

192.168.1.36-000.zip

Looks like you're having some hardware issue, my fist though would be the controller, but I can't see how that would make unRAID turn itself off.

 

It could also be ESXi related, afraid can't help you there, I'd suggest trying unRAID bare metal if that's an option and/or using another controller.

 

Also check temps/fans are all OK.

Another potential culprit is the PSU. A wonky PSU can cause weird issues that can be misdiagnosed due to corelation with other issues.

thanks guys.. also working with Areca and their cards logs..

so Areca engineer  came back with this

 

Drive in slot #9 often has time out error since 2016-08-06 19:51:37, it may kick out by storage driver. Please check that drive or re-install to another slot. Sometime disk vibration may lead to command timeout error.

 

so i did so hoping unraid would realize it was just moved but it looks like it gave the disk a new identifier, not sure where to  start. dont want to start breaking things..

 

 

You have to rebuild that disk to the one with the new id or do a new config and trust parity, new config only if nothing was written to that disk after it was disabled.

Crap does that mean I'll loose the data on it?

 

I'll have to look up what new config means.