I have been running a data re-build after moving one of my disks into a new backplane running off of a newly installed Supermicro SAS 8 port controller. Don't have the model handy, but it's the one everyone is running here. The upgrade had been planned for some time, but I hadn't gotten around to it until I noticed one of my drives running very slow when watching a show through media center.

 

My original plan was to load up the new controller and backplane, and run pre-clear on the new disks, then replace the slow/failing disk with one of the drives when it was done with the pre-clear. During the upgrade, I inadvertantly swapped 2 of the current drive sata cables, and started the array. When I saw this issue, I attemped to correct it by moving one of the good disks into the new backplane. I realize now this was a mistake, but at the time it seemed simple enough and it wouldn't force me to run a data rebuild. Once I realized I would need to rebuild, I thought it would be ok since I have rebuilt drives numerous times before.

 

So I started the rebuild of the existing good disk in the new backplane location. The problem is, it's running incredibly slow, and I was hoping there was a chance I didn't need to perform the rebuild of this good drive.

 

Summary:

1. Data disk #4 (750gb) running slow, showing 3 errors, but has not failed.

2. Added new Supermicro SAS controller, and added 3-5 backplane with 2 new data disks (2tb).

3. Moved good disk #5 (750gb) into new backplane.

4. Started rebuild of disk #5 while preclear of 2 new disks was ongoing.

5. Disk #4 is still spinning during data rebuild, but rebuild is going very slow.

6. Preclear of 2 new disks is complete.

 

Last check on rebuild was 47.4% complete, but running at 400KB. It has been running for over 36 hrs, and jumps around between 200KB and 2000KB on the rebuild.

 

My question is, since the data disk I'm rebuilding was ok to begin with, do I need to continue the rebuild or is there a way to avoid letting this run for 1-2 more days? Or am I stuck with it since I started it?

 

I did have some transfers to the array going, but I have since stopped all access to the array to avoid any potential issues, and hopefully allow the rebuild to speed up.

 

Any thoughts would be appreciated.

syslog-1-3-9am_part_2.txt

syslog-1-3-9am.txt

You are having massive number of "media errors" on several of your hard disks.  Those are un-readable sectors.

 

On disk3  ( /dev/sdf ):

Jan  1 19:35:58 Atlas kernel: ata5.00: failed command: READ DMA EXT
Jan  1 19:35:58 Atlas kernel: ata5.00: cmd 25/00:00:ef:aa:26/00:04:e1:00:00/e0 tag 0 dma 524288 in
Jan  1 19:35:58 Atlas kernel:          res 51/40:7f:5f:ac:26/00:02:e1:00:00/e0 Emask 0x9 (media error)
Jan  1 19:35:58 Atlas kernel: ata5.00: status: { DRDY ERR }
Jan  1 19:35:58 Atlas kernel: ata5.00: error: { UNC }
Jan  1 19:36:00 Atlas kernel: ata5.00: configured for UDMA/133
Jan  1 19:36:00 Atlas kernel: ata5: EH complete
Jan  1 19:36:03 Atlas kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:36:03 Atlas kernel: ata5.00: irq_stat 0x48000000
Jan  1 19:36:03 Atlas kernel: ata5.00: failed command: READ DMA EXT
Jan  1 19:36:03 Atlas kernel: ata5.00: cmd 25/00:00:ef:aa:26/00:04:e1:00:00/e0 tag 0 dma 524288 in
Jan  1 19:36:03 Atlas kernel:          res 51/40:5f:7f:ab:26/00:03:e1:00:00/e0 Emask 0x9 (media error)
Jan  1 19:36:03 Atlas kernel: ata5.00: status: { DRDY ERR }
Jan  1 19:36:03 Atlas kernel: ata5.00: error: { UNC }
Jan  1 19:36:05 Atlas kernel: ata5.00: configured for UDMA/133
Jan  1 19:36:05 Atlas kernel: ata5: EH complete
Jan  1 19:36:08 Atlas kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:36:08 Atlas kernel: ata5.00: irq_stat 0x48000000
Jan  1 19:36:08 Atlas kernel: ata5.00: failed command: READ DMA EXT
Jan  1 19:36:08 Atlas kernel: ata5.00: cmd 25/00:00:ef:aa:26/00:04:e1:00:00/e0 tag 0 dma 524288 in
Jan  1 19:36:08 Atlas kernel:          res 51/40:5f:7f:ab:26/00:03:e1:00:00/e0 Emask 0x9 (media error)
Jan  1 19:36:08 Atlas kernel: ata5.00: status: { DRDY ERR }
Jan  1 19:36:08 Atlas kernel: ata5.00: error: { UNC }
Jan  1 19:36:09 Atlas kernel: ata5.00: configured for UDMA/133
Jan  1 19:36:09 Atlas kernel: sd 3:0:0:0: [sdf] Unhandled sense code
Jan  1 19:36:09 Atlas kernel: sd 3:0:0:0: [sdf] Result: hostbyte=0x00 driverbyte=0x08
Jan  1 19:36:09 Atlas kernel: sd 3:0:0:0: [sdf] Sense Key : 0x3 [current] [descriptor]
Jan  1 19:36:09 Atlas kernel: Descriptor sense data with sense descriptors (in hex):
Jan  1 19:36:09 Atlas kernel:         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
Jan  1 19:36:09 Atlas kernel:         e1 26 ab 7f 
Jan  1 19:36:09 Atlas kernel: sd 3:0:0:0: [sdf] ASC=0x11 ASCQ=0x4
Jan  1 19:36:09 Atlas kernel: sd 3:0:0:0: [sdf] CDB: cdb[0]=0x28: 28 00 e1 26 aa ef 00 04 00 00
Jan  1 19:36:09 Atlas kernel: end_request: I/O error, dev sdf, sector 3777407871
Jan  1 19:36:09 Atlas kernel: ata5: EH complete
Jan  1 19:36:09 Atlas kernel: md: disk3 read error
Jan  1 19:36:09 Atlas kernel: handle_stripe read error: 3777407808/1, count: 1
Jan  1 19:36:09 Atlas kernel: md: disk3 read error
Jan  1 19:36:09 Atlas kernel: handle_stripe read error: 3777407816/1, count: 1
Jan  1 19:36:09 Atlas kernel: md: disk3 read error
Jan  1 19:36:09 Atlas kernel: handle_stripe read error: 3777407824/1, count: 1
Jan  1 19:36:09 Atlas kernel: md: disk3 read error
Jan  1 19:36:09 Atlas kernel: handle_stripe read error: 3777407832/1, count: 1
Jan  1 19:36:09 Atlas kernel: md: disk3 read error
Jan  1 19:36:09 Atlas kernel: handle_stripe read error: 3777407840/1, count: 1
Jan  1 19:36:09 Atlas kernel: md: disk3 read error
Jan  1 19:36:09 Atlas kernel: handle_stripe read error: 3777407848/1, count: 1
Jan  1 19:36:09 Atlas kernel: md: disk3 read error
Jan  1 19:36:09 Atlas kernel: handle_stripe read error: 3777407856/1, count: 1
Jan  1 19:36:09 Atlas kernel: md: disk3 read error
Jan  1 19:36:09 Atlas kernel: handle_stripe read error: 3777407864/1, count: 1
Jan  1 19:36:09 Atlas kernel: md: disk3 read error
Jan  1 19:36:09 Atlas kernel: handle_stripe read error: 3777407872/1, count: 1
Jan  1 19:36:09 Atlas kernel: md: disk3 read error
Jan  1 19:36:09 Atlas kernel: handle_stripe read error: 3777407880/1, count: 1
Jan  1 19:36:09 Atlas kernel: md: disk3 read error
Jan  1 19:36:09 Atlas kernel: handle_stripe read error: 3777407888/1, count: 1
Jan  1 19:36:09 Atlas kernel: md: disk3 read error
Jan  1 19:36:09 Atlas kernel: handle_stripe read error: 3777407896/1, count: 1
Jan  1 19:36:09 Atlas kernel: md: disk3 read error
Jan  1 19:36:09 Atlas kernel: handle_stripe read error: 3777407904/1, count: 1
Jan  1 19:36:09 Atlas kernel: md: disk3 read error
Jan  1 19:36:09 Atlas kernel: handle_stripe read error: 3777407912/1, count: 1
Jan  1 19:36:09 Atlas kernel: md: disk3 read error
Jan  1 19:36:09 Atlas kernel: handle_stripe read error: 3777407920/1, count: 1
Jan  1 19:36:09 Atlas kernel: md: disk3 read error
Jan  1 19:36:09 Atlas kernel: handle_stripe read error: 3777407928/1, count: 1
Jan  1 19:36:09 Atlas kernel: md: disk3 read error

 

And also apparently on a second disk

Jan  1 18:55:32 Atlas kernel: ata7.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 18:55:32 Atlas kernel: ata7.01: failed command: READ DMA EXT
Jan  1 18:55:32 Atlas kernel: ata7.01: cmd 25/00:40:1f:92:b6/00:00:3d:00:00/f0 tag 0 dma 32768 in
Jan  1 18:55:32 Atlas kernel:          res 51/40:00:2e:92:b6/40:00:3d:00:00/f0 Emask 0x9 (media error)
Jan  1 18:55:32 Atlas kernel: ata7.01: status: { DRDY ERR }
Jan  1 18:55:32 Atlas kernel: ata7.01: error: { UNC }
Jan  1 18:55:32 Atlas kernel: ata7.00: configured for UDMA/133
Jan  1 18:55:32 Atlas kernel: ata7.01: configured for UDMA/133
Jan  1 18:55:32 Atlas kernel: ata7: EH complete
Jan  1 18:55:37 Atlas kernel: ata7.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 18:55:37 Atlas kernel: ata7.01: failed command: READ DMA EXT
Jan  1 18:55:37 Atlas kernel: ata7.01: cmd 25/00:40:1f:92:b6/00:00:3d:00:00/f0 tag 0 dma 32768 in
Jan  1 18:55:37 Atlas kernel:          res 51/40:00:25:92:b6/40:00:3d:00:00/f0 Emask 0x9 (media error)
Jan  1 18:55:37 Atlas kernel: ata7.01: status: { DRDY ERR }
Jan  1 18:55:37 Atlas kernel: ata7.01: error: { UNC }
Jan  1 18:55:38 Atlas kernel: ata7.00: configured for UDMA/133
Jan  1 18:55:38 Atlas kernel: ata7.01: configured for UDMA/133
Jan  1 18:55:38 Atlas kernel: ata7: EH complete
Jan  1 18:56:08 Atlas kernel: ata7.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 18:56:08 Atlas kernel: ata7.01: failed command: READ DMA EXT
Jan  1 18:56:08 Atlas kernel: ata7.01: cmd 25/00:00:37:62:b0/00:01:38:00:00/f0 tag 0 dma 131072 in
Jan  1 18:56:08 Atlas kernel:          res 51/40:00:42:62:b0/40:00:38:00:00/f0 Emask 0x9 (media error)
Jan  1 18:56:08 Atlas kernel: ata7.01: status: { DRDY ERR }
Jan  1 18:56:08 Atlas kernel: ata7.01: error: { UNC }
Jan  1 18:56:08 Atlas kernel: ata7.00: configured for UDMA/133
Jan  1 18:56:08 Atlas kernel: ata7.01: configured for UDMA/133
Jan  1 18:56:08 Atlas kernel: ata7: EH complete
Jan  1 18:56:10 Atlas kernel: ata7.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 18:56:10 Atlas kernel: ata7.01: failed command: READ DMA EXT
Jan  1 18:56:10 Atlas kernel: ata7.01: cmd 25/00:00:37:62:b0/00:01:38:00:00/f0 tag 0 dma 131072 in
Jan  1 18:56:10 Atlas kernel:          res 51/40:00:38:62:b0/40:00:38:00:00/f0 Emask 0x9 (media error)
Jan  1 18:56:10 Atlas kernel: ata7.01: status: { DRDY ERR }
Jan  1 18:56:10 Atlas kernel: ata7.01: error: { UNC }
Jan  1 18:56:10 Atlas kernel: ata7.00: configured for UDMA/133
Jan  1 18:56:10 Atlas kernel: ata7.01: configured for UDMA/133
Jan  1 18:56:10 Atlas kernel: ata7: EH complete
Jan  1 18:56:41 Atlas kernel: ata7.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 frozen
Jan  1 18:56:41 Atlas kernel: ata7.01: failed command: READ DMA EXT
Jan  1 18:56:41 Atlas kernel: ata7.01: cmd 25/00:00:37:62:b0/00:01:38:00:00/f0 tag 0 dma 131072 in
Jan  1 18:56:41 Atlas kernel:          res 40/00:00:38:62:b0/40:00:38:00:00/f0 Emask 0x4 (timeout)
Jan  1 18:56:41 Atlas kernel: ata7.01: status: { DRDY }
Jan  1 18:56:41 Atlas kernel: ata7.00: hard resetting link
Jan  1 18:56:42 Atlas kernel: ata7.01: hard resetting link

 

I suggest getting smartctl reports on all your drives.  At least two of them appear to have a large number of un-readable sectors.

 

Joe L.