Parity Noob Question - Solved


Recommended Posts

Look at the date/time and attach the most recent.

 

Sorry, open with notepad and check time:

 

Mar  8 04:40:01 Tower emhttp: shcmd (1307): rmmod md-mod |& logger

Mar  8 04:40:01 Tower kernel: md: unRAID driver removed

Mar  8 04:40:01 Tower emhttp: shcmd (1308): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger

Mar  8 04:40:01 Tower kernel: md: unRAID driver 2.5.3 installed

Link to comment

Look at the date/time and attach the most recent.

 

Sorry, open with notepad and check time:

 

Mar  8 04:40:01 Tower emhttp: shcmd (1307): rmmod md-mod |& logger

Mar  8 04:40:01 Tower kernel: md: unRAID driver removed

Mar  8 04:40:01 Tower emhttp: shcmd (1308): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger

Mar  8 04:40:01 Tower kernel: md: unRAID driver 2.5.3 installed

 

Sorry for being such a noob. We only use our server for storage, plex and nsb grabbing. Havent gotten new shows in 3 weeks because of this, thanks for dealing with my lack of knowledge about this. I deleted a few folders to reduce size

tower-diagnostics-20160308-1059_1.zip

Link to comment

This disk is still getting UDMA_CRC errors, if you already replaced this cable it may be an enclosure issue, or less likely the SATA port or controller.

 

Device Model:     Hitachi HDS5C3020ALA632
Serial Number:    ML0220F30AVLTD

 

Is that the only one you see getting the error. What file do you see the error in I tried looking

Link to comment

From syslog:

Mar  8 10:23:40 Tower kernel: ata8.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen
Mar  8 10:23:40 Tower kernel: ata8.00: irq_stat 0x08000000, interface fatal error
Mar  8 10:23:40 Tower kernel: ata8: SError: { UnrecovData 10B8B BadCRC }
Mar  8 10:23:40 Tower kernel: ata8.00: failed command: READ DMA EXT
Mar  8 10:23:40 Tower kernel: ata8.00: cmd 25/00:40:c8:af:45/00:05:00:00:00/e0 tag 15 dma 688128 in
Mar  8 10:23:40 Tower kernel:         res 50/00:00:47:00:00/00:00:41:00:00/e1 Emask 0x10 (ATA bus error)
Mar  8 10:23:40 Tower kernel: ata8.00: status: { DRDY }
Mar  8 10:23:40 Tower kernel: ata8: hard resetting link
Mar  8 10:23:41 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar  8 10:23:41 Tower kernel: ata8.00: configured for UDMA/133
Mar  8 10:23:41 Tower kernel: ata8: EH complete
Mar  8 10:23:46 Tower kernel: ata8.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen
Mar  8 10:23:46 Tower kernel: ata8.00: irq_stat 0x08000000, interface fatal error
Mar  8 10:23:46 Tower kernel: ata8: SError: { UnrecovData 10B8B BadCRC }
Mar  8 10:23:46 Tower kernel: ata8.00: failed command: READ DMA EXT
Mar  8 10:23:46 Tower kernel: ata8.00: cmd 25/00:40:48:37:4a/00:05:00:00:00/e0 tag 11 dma 688128 in
Mar  8 10:23:46 Tower kernel:         res 50/00:00:47:00:90/00:00:42:00:00/e2 Emask 0x10 (ATA bus error)
Mar  8 10:23:46 Tower kernel: ata8.00: status: { DRDY }
Mar  8 10:23:46 Tower kernel: ata8: hard resetting link
Mar  8 10:23:46 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar  8 10:23:46 Tower kernel: ata8.00: configured for UDMA/133

 

earlier smart report:

199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       600

 

smart from now:

199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       604

Link to comment

From syslog:

Mar  8 10:23:40 Tower kernel: ata8.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen
Mar  8 10:23:40 Tower kernel: ata8.00: irq_stat 0x08000000, interface fatal error
Mar  8 10:23:40 Tower kernel: ata8: SError: { UnrecovData 10B8B BadCRC }
Mar  8 10:23:40 Tower kernel: ata8.00: failed command: READ DMA EXT
Mar  8 10:23:40 Tower kernel: ata8.00: cmd 25/00:40:c8:af:45/00:05:00:00:00/e0 tag 15 dma 688128 in
Mar  8 10:23:40 Tower kernel:         res 50/00:00:47:00:00/00:00:41:00:00/e1 Emask 0x10 (ATA bus error)
Mar  8 10:23:40 Tower kernel: ata8.00: status: { DRDY }
Mar  8 10:23:40 Tower kernel: ata8: hard resetting link
Mar  8 10:23:41 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar  8 10:23:41 Tower kernel: ata8.00: configured for UDMA/133
Mar  8 10:23:41 Tower kernel: ata8: EH complete
Mar  8 10:23:46 Tower kernel: ata8.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen
Mar  8 10:23:46 Tower kernel: ata8.00: irq_stat 0x08000000, interface fatal error
Mar  8 10:23:46 Tower kernel: ata8: SError: { UnrecovData 10B8B BadCRC }
Mar  8 10:23:46 Tower kernel: ata8.00: failed command: READ DMA EXT
Mar  8 10:23:46 Tower kernel: ata8.00: cmd 25/00:40:48:37:4a/00:05:00:00:00/e0 tag 11 dma 688128 in
Mar  8 10:23:46 Tower kernel:         res 50/00:00:47:00:90/00:00:42:00:00/e2 Emask 0x10 (ATA bus error)
Mar  8 10:23:46 Tower kernel: ata8.00: status: { DRDY }
Mar  8 10:23:46 Tower kernel: ata8: hard resetting link
Mar  8 10:23:46 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar  8 10:23:46 Tower kernel: ata8.00: configured for UDMA/133

 

earlier smart report:

199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       600

 

smart from now:

199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       604

 

I removed the Norco that conataind the drives with the errors and replaced it with a new Norco that I had purchased for expansion. I also put the 8tb drive back in for the parity but I am still getting 3Mb/sec for parity sync. I am attaching a new diagnostic file

tower-diagnostics-20160308-1439.zip

Link to comment

Syslog is clean, no more CRC errors up untill now, nothing else jumps to mind.

 

Could be a disk with slow sectors, those can’t usually be detect with SMART info.

 

You can try running diskspeed with these options:

 

diskspeed.sh –f –s 101

 

You have to stop the parity sync and it will take some time, like 15 minutes per disk, look for a graph like the one below, if they are all ok I’m out of ideas.

diskspeed.png.87949bdeefcc89a1b17e32bf334da786.png

Link to comment

Looks normal, I'm out of ideas.

 

Maybe someone else will see something in your logs, in the meantime re-start the parity sync,  hopefully with the crc issues resolved it will complete or help find the problem in case of more errors.

 

I tried with your awesome help and patience. I will be near prostuff1  who built my server years ago and take it to him to see what he finds wrong. I was hoping to get it working with the help of the users here, thanks so much

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.