Also, here is the current syslog

There has to be something wrong. The smart reports say that the drives are all good

syslog.zip

Also, here is the current syslog

There has to be something wrong. The smart reports say that the drives are all good

Please post a smart report for disk11 

(I think it is /dev/sdm)

 

Based on your syslog, that disk is experiencing UNC media-errors (un-correctable media errors)  Those would show in the smart report as sectors pending re-allocation, or sectors already-re-allocated.

ar  4 07:42:52 Tower kernel: ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Mar  4 07:42:52 Tower kernel: ata14.00: BMDMA2 stat 0xd0009

Mar  4 07:42:52 Tower kernel: ata14.00: failed command: READ DMA EXT

Mar  4 07:42:52 Tower kernel: ata14.00: cmd 25/00:90:7f:14:24/00:03:ad:00:00/e0 tag 0 dma 466944 in

Mar  4 07:42:52 Tower kernel:          res 51/40:ff:0c:16:24/00:01:ad:00:00/f0 Emask 0x9 (media error)

Mar  4 07:42:52 Tower kernel: ata14.00: status: { DRDY ERR }

Mar  4 07:42:52 Tower kernel: ata14.00: error: { UNC }

Mar  4 07:42:57 Tower kernel: ata14.00: configured for UDMA/33

Mar  4 07:42:57 Tower kernel: ata14: EH complete

Mar  4 07:43:00 Tower kernel: ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Mar  4 07:43:00 Tower kernel: ata14.00: BMDMA2 stat 0xd0009

Mar  4 07:43:00 Tower kernel: ata14.00: failed command: READ DMA EXT

Mar  4 07:43:00 Tower kernel: ata14.00: cmd 25/00:90:7f:14:24/00:03:ad:00:00/e0 tag 0 dma 466944 in

Mar  4 07:43:00 Tower kernel:          res 51/40:ff:0c:16:24/00:01:ad:00:00/f0 Emask 0x9 (media error)

Mar  4 07:43:00 Tower kernel: ata14.00: status: { DRDY ERR }

Mar  4 07:43:00 Tower kernel: ata14.00: error: { UNC }

Mar  4 07:43:05 Tower kernel: ata14.00: configured for UDMA/33

Mar  4 07:43:05 Tower kernel: sd 14:0:0:0: [sdm] Unhandled sense code

Mar  4 07:43:05 Tower kernel: sd 14:0:0:0: [sdm] Result: hostbyte=0x00 driverbyte=0x08

Mar  4 07:43:05 Tower kernel: sd 14:0:0:0: [sdm] Sense Key : 0x3 [current] [descriptor]

Mar  4 07:43:05 Tower kernel: Descriptor sense data with sense descriptors (in hex):

Mar  4 07:43:05 Tower kernel:        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00

Mar  4 07:43:05 Tower kernel:        ad 24 16 0c

Mar  4 07:43:05 Tower kernel: sd 14:0:0:0: [sdm] ASC=0x11 ASCQ=0x4

Mar  4 07:43:05 Tower kernel: sd 14:0:0:0: [sdm] CDB: cdb[0]=0x28: 28 00 ad 24 14 7f 00 03 90 00

Mar  4 07:43:05 Tower kernel: end_request: I/O error, dev sdm, sector 2904823308

Mar  4 07:43:05 Tower kernel: ata14: EH complete

Mar  4 07:43:05 Tower kernel: md: disk11 read error

Mar  4 07:43:05 Tower kernel: handle_stripe read error: 2904823240/7, count: 1

Mar  4 07:43:05 Tower kernel: md: disk11 read error

Mar  4 07:43:05 Tower kernel: handle_stripe read error: 2904823248/7, count: 1

Mar  4 07:43:05 Tower kernel: md: disk11 read error

Mar  4 07:43:05 Tower kernel: handle_stripe read error: 2904823256/7, count: 1

Mar  4 07:43:05 Tower kernel: md: disk11 read error

Mar  4 07:43:05 Tower kernel: handle_stripe read error: 2904823264/7, count: 1

Mar  4 07:43:05 Tower kernel: md: disk11 read error

Mar  4 07:43:05 Tower kernel: handle_stripe read error: 2904823272/7, count: 1

Mar  4 07:43:05 Tower kernel: md: disk11 read error

Mar  4 07:43:05 Tower kernel: handle_stripe read error: 2904823280/7, count: 1

Mar  4 07:43:05 Tower kernel: md: disk11 read error

Mar  4 07:43:05 Tower kernel: handle_stripe read error: 2904823288/7, count: 1

Mar  4 07:43:05 Tower kernel: md: disk11 read error

Joe,

Here is the smart report for disk11

I appreciate your help

smart_report_disk11.txt

Joe,

Here is the smart report for disk11

I appreciate your help

That drive is dying, the sooner you can replace it the better.

What in the report tells you that? I am curious.

What in the report tells you that? I am curious.

Mostly the Reallocated Sector count and the Current Pending Sector count

What in the report tells you that? I am curious.

 

There have been 64 sectors re-allocated as they were un-readable

5 Reallocated_Sector_Ct  0x0033  192  192  140    Pre-fail  Always      -      64

and there are 1459 more un-readable sectors pending re-allocation when next written.

197 Current_Pending_Sector  0x0032  195  195  000    Old_age  Always      -      1459

 

As already described, that drive is rapidly dying...  RMA ASAP.

DO NOT PERFORM A PARITY CHECK...  (in fact, best if you un-assign the drive now)

 

Joe L.

Here are smart reports from all disks

Please tell me what drives are failing. I know about disk11.

Thanks

smart_reports.zip

The other drives look ok. There are 2 failed drives and unRAID cannot recover the contents of these disks. You may be able to recover most of disk 11 using recovery software on a Mac or PC. Remove disk11 and reset the array to build new parity.

I ordered a new drive to replace disk11. Should be here this week

disk11 is actually empty. It only has 2 folders on it, no data

I will reset array when replaced and then rebuild parity.

 

You can reset and rebuild parity now. When the new disk comes pre-clear it and then add it to the array.

 

Also, A Mac can only be used for reiserfs data recovery if Linux is installed.

I want to unassign disk11 and then start the array without it. There is nothing on disk11.

How do I do this and still have parity be ok

Then when I get the new drive I will remove the bad one and then preclear the new one and then assign it

 

Remove the drive and follow this procedure:

 

OK so the rebuild finished but when I restarted the unraid system it said it was doing the rebuild again.

Here is the current syslog. The rebuild gets to 98.9% and then seems to really slow down.

I ran a smart report on all drives and they reported as fine.

I have no idea what is going on. please help me get my tower back to normal.

 

How can I tell unraid to just skip the rebuild process and leave the drive empty. There were only a few files on it anyway.

 

Thanks

Simple.

 

Stop the array

Un-assign the disk

Set a new disk configuration  (depending on unRAID version, either use the "initconfig" commanf or use the New Config button on the utilites page.)

Start the array without the disk in the array.  Parity is instantly invalidated when you set a new disk configuration.  It will be calculated again when you next start the array.

New drive has been installed and precleared.

Parity is now rebuilding.

 

Parity rebuilt and working great.

Thanks for the support