Hi,

Drive 4 (200GB) has some errors the other day, not for the first tine. I pulled the old disk drive out and replaced it with a brand new WD20TB drive. Precleared it first. The data rebuild began, but with a rate of about 250KB/s transfer rate. It is extremely slow and I'm quite sure something wrong with the system.

I'm running 4.7 plus version.

Attached please find syslog

please advice

thanks

 

and the syslog...

syslog-2012-09-25_1.txt

Not knowing the errors you had, but /dev/sde is constantly timing out and constantly being reset by the disk controller.

Sep 23 20:43:48 Tower kernel: ata4: SATA max UDMA/133 cmd 0xb000 ctl 0xa800 bmdma 0xa408 irq 23

Sep 23 20:43:48 Tower kernel: ata4.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133

Sep 23 20:43:48 Tower kernel: ata4.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 0/32)

Sep 23 20:43:48 Tower kernel: ata4.00: configured for UDMA/133

Sep 23 20:43:48 Tower kernel: scsi 4:0:0:0: Direct-Access    ATA      WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5

Sep 23 20:43:48 Tower kernel: sd 4:0:0:0: [sde] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)

Sep 23 20:43:48 Tower kernel: sd 4:0:0:0: [sde] Write Protect is off

Sep 23 20:43:48 Tower kernel: sd 4:0:0:0: [sde] Mode Sense: 00 3a 00 00

Sep 23 20:43:48 Tower kernel: sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Sep 23 20:43:48 Tower kernel:  sde: sde1

 

The errors seem to indicate the disk stops responding...

Sep 24 19:55:24 Tower kernel: ata4: lost interrupt (Status 0x50)

Sep 24 19:55:24 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Sep 24 19:55:24 Tower kernel: ata4.00: failed command: READ DMA

Sep 24 19:55:24 Tower kernel: ata4.00: cmd c8/00:00:5f:cd:01/00:00:00:00:00/e0 tag 0 dma 131072 in

Sep 24 19:55:24 Tower kernel:          res 40/00:ff:00:00:00/00:00:00:00:00/10 Emask 0x4 (timeout)

Sep 24 19:55:24 Tower kernel: ata4.00: status: { DRDY }

Sep 24 19:55:24 Tower kernel: ata4: soft resetting link

Sep 24 19:55:24 Tower kernel: ata4.00: configured for UDMA/100

Sep 24 19:55:24 Tower kernel: ata4.01: configured for UDMA/133

Sep 24 19:55:24 Tower kernel: ata4.00: device reported invalid CHS sector 0

Sep 24 19:55:24 Tower kernel: ata4: EH complete

Sep 24 19:55:56 Tower kernel: ata4: lost interrupt (Status 0x50)

Sep 24 19:55:56 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Sep 24 19:55:56 Tower kernel: ata4.00: failed command: READ DMA

Sep 24 19:55:56 Tower kernel: ata4.00: cmd c8/00:00:5f:10:02/00:00:00:00:00/e0 tag 0 dma 131072 in

Sep 24 19:55:56 Tower kernel:          res 40/00:00:01:4f:c2/00:00:00:00:00/10 Emask 0x4 (timeout)

Sep 24 19:55:56 Tower kernel: ata4.00: status: { DRDY }

Sep 24 19:55:56 Tower kernel: ata4: soft resetting link

Sep 24 19:55:56 Tower kernel: ata4.00: configured for UDMA/100

Sep 24 19:55:56 Tower kernel: ata4.01: configured for UDMA/133

Sep 24 19:55:56 Tower kernel: ata4: EH complete

Sep 24 20:04:52 Tower emhttp: resized: /mnt/disk4

 

 

You also have a different issue to contend with if you ever intend to upgrade past 4.7.  You have an HPA on /dev/sdf

Don't worry about this just now, but it will be an issue before you can upgrade.

Sep 23 20:43:48 Tower kernel: ata4.01: HPA detected: current 1953523055, native 1953525168

Sep 23 20:43:48 Tower kernel: ata4.01: ATA-8: WDC WD10EADS-00M2B0, 01.00A01, max UDMA/133

Sep 23 20:43:48 Tower kernel: ata4.01: 1953523055 sectors, multi 16: LBA48 NCQ (depth 0/32)

thanks joe.

It really seems that there are some errors associated with /dev/sde

Any idea if there is a procedure to follow to fix it and then rebuild the replaced?

What was the problem with disk4? It may be better to put the original disk4 back and replace sde. Which drive is sde? Is it the new one?

sde is not the new one.

the old one behaves the same as the the new when I tried to rebuild the data.

Doesn't the old drive already contain data?

Well, the old sda (200GB) has several problems in the past, so after the last malfunction, i've decided to replace it. Now the system is reconstructing the data to the new sda (slowly, very slowly).

Following Hoe comment, trying to think what is the cause for this, do you think my PSU might be too weak?

it's a 300W PSU which powers 5 HDs (not SSD)

 

What model PSU?

EZCool ATX-300 JSP

EZCool ATX-300 JSP

I can't find any stats online for that model, how many amps does it claim it can supply on the 12v rail? I suspect it is too low.

18A

18A

That is probably the cause of your issues. Read here.

Actually, slowly the rebuild data process finished.

I'm going to have a new PSU