Data Rebuild Speed

nsp24 · December 17, 2021

Hi, I am having a few issues with my server and have swapped a hard drive that had errors and the Rebuild speed has been 2.7MB/sec or less is this usual as its done 9.2% since last night and is reporting 7 days and 16 hours to complete?

Thanks Nick.

itimpi · December 17, 2021

Rebuild speed should similar to a parity check speed as long as there is nothing else happening on the array at the same time.

Your speed suggests there is something else going on affecting the speed. Attach your system's diagnostics to you next post to get informed feedback.

nsp24 · December 17, 2021

12 minutes ago, itimpi said:

Attach your system's diagnostics to you next post to get informed feedback.

Hi here it is thanks!

tower-diagnostics-20211217-1215.zip

itimpi · December 17, 2021

You are continually getting messages like :

Dec 17 10:08:41 Tower kernel: ata5: lost interrupt (Status 0x50)
Dec 17 10:08:41 Tower kernel: ata5.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 17 10:08:41 Tower kernel: ata5.01: failed command: READ DMA EXT
Dec 17 10:08:41 Tower kernel: ata5.01: cmd 25/00:f8:18:26:93/00:03:13:00:00/f0 tag 0 dma 520192 in
Dec 17 10:08:41 Tower kernel:         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 17 10:08:41 Tower kernel: ata5.01: status: { DRDY }
Dec 17 10:08:41 Tower kernel: ata5: soft resetting link
Dec 17 10:08:41 Tower kernel: ata5.00: configured for UDMA/133
Dec 17 10:08:41 Tower kernel: ata5.01: configured for UDMA/33
Dec 17 10:08:41 Tower kernel: ata5: EH complete

in the syslog. I believe ata5 is the parity disk. This suggests either a connection problem (most likely) or the drive itself playing up.

nsp24 · December 17, 2021

2 minutes ago, itimpi said:

You are continually getting messages like :

Dec 17 10:08:41 Tower kernel: ata5: lost interrupt (Status 0x50)
Dec 17 10:08:41 Tower kernel: ata5.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 17 10:08:41 Tower kernel: ata5.01: failed command: READ DMA EXT
Dec 17 10:08:41 Tower kernel: ata5.01: cmd 25/00:f8:18:26:93/00:03:13:00:00/f0 tag 0 dma 520192 in
Dec 17 10:08:41 Tower kernel:         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 17 10:08:41 Tower kernel: ata5.01: status: { DRDY }
Dec 17 10:08:41 Tower kernel: ata5: soft resetting link
Dec 17 10:08:41 Tower kernel: ata5.00: configured for UDMA/133
Dec 17 10:08:41 Tower kernel: ata5.01: configured for UDMA/33
Dec 17 10:08:41 Tower kernel: ata5: EH complete

in the syslog. I believe ata5 is the parity disk. This suggests either a connection problem (most likely) or the drive itself playing up.

Ok thanks Should I pause the Rebuild and try a new cable? I have been getting the problem t6hat I cannot access the tower from my PC and I assume the server has crashed, could this be related to this?

trurl · December 17, 2021

1 hour ago, nsp24 said:

try a new cable?

yes, you can't trust the rebuild with all that going on. Every bit of parity plus every bit of all other disks must be reliably read to reliably rebuild a disk.

nsp24 · December 17, 2021

11 minutes ago, trurl said:

yes, you can't trust the rebuild with all that going on. Every bit of parity plus every bit of all other disks must be reliably read to reliably rebuild a disk.

ok thanks

nsp24 · December 17, 2021

Ok I have replaced every cable to all the drives and also put them in different ports both Parity drives go to the motherboard, im now getting

Tower kernel: ata6: lost interrupt (Status 0x50)
Dec 17 15:53:01 Tower kernel: ata6.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 17 15:53:01 Tower kernel: ata6.01: failed command: READ DMA
Dec 17 15:53:01 Tower kernel: ata6.01: cmd c8/00:20:00:00:00/00:00:00:00:00/f0 tag 0 dma 16384 in
Dec 17 15:53:01 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/10 Emask 0x4 (timeout)
Dec 17 15:53:01 Tower kernel: ata6.01: status: { DRDY }
Dec 17 15:53:01 Tower kernel: ata6: soft resetting link
Dec 17 15:53:01 Tower kernel: ata6.00: configured for UDMA/133
Dec 17 15:53:01 Tower kernel: ata6.01: configured for UDMA/133

how do I work out which drive this is ?

tower-diagnostics-20211217-1607.zip

nsp24 · December 17, 2021

oh by the way I've noticed a sort of ting sound not a click but a ting it only happens occasionally but definitely a hard drive and my estimated rebuild speed has gone up its now 14 kb/sec but has been 292.7 kb/sec

JorgeB · December 17, 2021

6 minutes ago, nsp24 said:

ata6.01:

This is parity2, also de SATA controller is in IDE mode, and that's not ideal, but your board likely doesn't support AHCI.

nsp24 · December 17, 2021

4 minutes ago, JorgeB said:

This is parity2, also de SATA controller is in IDE mode, and that's not ideal, but your board likely doesn't support AHCI.

I will look at that thanks, parity 2 is a relatively new drive 6 months Max what do you suggest I do? this is all very complicated and frustrating!!

Thanks Nick

JorgeB · December 17, 2021

Try yet a different SATA cable, could also be a power issue.

nsp24 · December 17, 2021

43 minutes ago, JorgeB said:

This is parity2, also de SATA controller is in IDE mode, and that's not ideal, but your board likely doesn't support AHCI.

yes I have checked IT does not do AHCI

nsp24 · December 17, 2021

35 minutes ago, JorgeB said:

Try yet a different SATA cable, could also be a power issue.

ok I have swapped cables around tested PSU with a tester all good, also removed and checked power cables and I have noticed the tinging noise has stopped and the rebuild has started again and is saying 10 hours instead of 7 days. is it worth checking syslog to see if the error is still there?

JorgeB · December 17, 2021

19 minutes ago, nsp24 said:

is it worth checking syslog to see if the error is still there?

Always good to make sure.

nsp24 · December 17, 2021

19 minutes ago, JorgeB said:

Always good to make sure.

Ok The system feels so much faster and has already done 8.4% in under 0ne hour where it had taken about 10 hours to do 9%, here is my log files can any experts have a look and see what you think? It all means nothing to me!!

JorgeB · December 17, 2021

1 hour ago, nsp24 said:

Dec 17 15:53:01 Tower kernel: ata6.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 17 15:53:01 Tower kernel: ata6.01: failed command: READ DMA
Dec 17 15:53:01 Tower kernel: ata6.01: cmd c8/00:20:00:00:00/00:00:00:00:00/f0 tag 0 dma 16384 in
Dec 17 15:53:01 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/10 Emask 0x4 (timeout)
Dec 17 15:53:01 Tower kernel: ata6.01: status: { DRDY }
Dec 17 15:53:01 Tower kernel: ata6: soft resetting link
Dec 17 15:53:01 Tower kernel: ata6.00: configured for UDMA/133
Dec 17 15:53:01 Tower kernel: ata6.01: configured for UDMA/133

Look for ATA errors like those above, or post new diags.

nsp24 · December 17, 2021

17 minutes ago, JorgeB said:

Look for ATA errors like those above, or post new diags.

I meant to post them and forgot to attach lol

tower-diagnostics-20211217-1752.zip

trurl · December 17, 2021

At the very end of syslog, don't know if they are continuing.

Dec 17 17:32:57 Tower kernel: ata2: lost interrupt (Status 0x50)
Dec 17 17:32:57 Tower kernel: ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 17 17:32:57 Tower kernel: ata2.01: failed command: READ DMA EXT
Dec 17 17:32:57 Tower kernel: ata2.01: cmd 25/00:00:70:30:24/00:04:0b:00:00/f0 tag 0 dma 524288 in
Dec 17 17:32:57 Tower kernel:         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 17 17:32:57 Tower kernel: ata2.01: status: { DRDY }
Dec 17 17:32:57 Tower kernel: ata2: soft resetting link
Dec 17 17:32:57 Tower kernel: ata2.00: configured for UDMA/133
Dec 17 17:32:57 Tower kernel: ata2.01: configured for UDMA/133
Dec 17 17:32:57 Tower kernel: ata2: EH complete

This is parity

nsp24 · December 17, 2021

20 minutes ago, trurl said:

At the very end of syslog, don't know if they are continuing.

Dec 17 17:32:57 Tower kernel: ata2: lost interrupt (Status 0x50)
Dec 17 17:32:57 Tower kernel: ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 17 17:32:57 Tower kernel: ata2.01: failed command: READ DMA EXT
Dec 17 17:32:57 Tower kernel: ata2.01: cmd 25/00:00:70:30:24/00:04:0b:00:00/f0 tag 0 dma 524288 in
Dec 17 17:32:57 Tower kernel:         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 17 17:32:57 Tower kernel: ata2.01: status: { DRDY }
Dec 17 17:32:57 Tower kernel: ata2: soft resetting link
Dec 17 17:32:57 Tower kernel: ata2.00: configured for UDMA/133
Dec 17 17:32:57 Tower kernel: ata2.01: configured for UDMA/133
Dec 17 17:32:57 Tower kernel: ata2: EH complete

This is parity

Sorry not sure what you mean?

JorgeB · December 17, 2021

There's a new ATA error, but it's just one, and while not ideal it's not a bid deal, bigger problem is when they are constantly repeating.

trurl · December 17, 2021

30 minutes ago, nsp24 said:

Sorry not sure what you mean?

53 minutes ago, trurl said:

At the very end of syslog, don't know if they are continuing.

Post new diagnostics so we can see if

18 minutes ago, JorgeB said:

they are constantly repeating.

nsp24 · December 17, 2021

I'm currently doing a data rebuild would that cause this? its working so much faster now at 24% with 8 hours remaining

trurl · December 17, 2021

22 minutes ago, trurl said:

Post new diagnostics so we can see

nsp24 · December 17, 2021

2 minutes ago, trurl said:

Here it is thank you!!

tower-diagnostics-20211217-1946.zip

Data Rebuild Speed

Recommended Posts

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation