I seem to get numerous hard resetting links on my machine. I have precleared all disks with succes and have now assigned  4 of the 12 disks to start out. But the hard resetting of the bus wurries me is this normal behaviour ?

 

I also noticed during the preclear stage that 4 of my 12 disks dropped there speed to around 30mb/s.

 

Attached syslog and setup is in my sig.

 

 

 

 

Nov 12 06:45:45 Tower emhttp: disk20 mount error: 32

Nov 12 06:45:45 Tower emhttp: shcmd (27): rmdir /mnt/cache

Nov 12 06:45:45 Tower emhttp: _shcmd: shcmd (28): exit status: 32

Nov 12 06:45:45 Tower emhttp: disk1 mount error: 32

Nov 12 06:45:45 Tower emhttp: shcmd (29): rmdir /mnt/disk1

Nov 12 06:45:45 Tower kernel: md: using 1152k window, over a total of 488386552 blocks.

Nov 12 06:45:45 Tower kernel: REISERFS warning (device sdf1): sh-2021 reiserfs_fill_super: can not find reiserfs on sdf1

Nov 12 06:45:45 Tower kernel: REISERFS warning (device md1): sh-2021 reiserfs_fill_super: can not find reiserfs on md1

Nov 12 06:45:45 Tower emhttp: _shcmd: shcmd (29): exit status: 32

Nov 12 06:45:45 Tower emhttp: disk2 mount error: 32

Nov 12 06:45:45 Tower emhttp: shcmd (30): rmdir /mnt/disk2

Nov 12 06:45:45 Tower kernel: REISERFS warning (device md2): sh-2021 reiserfs_fill_super: can not find reiserfs on md2

Nov 12 06:45:45 Tower emhttp: shcmd (32): rm /etc/samba/smb-shares.conf >/dev/null 2>&1

Nov 12 06:45:45 Tower emhttp: shcmd (33): cp /etc/exports- /etc/exports

Nov 12 06:45:45 Tower emhttp: shcmd (34): killall -HUP smbd

Nov 12 06:45:45 Tower emhttp: shcmd (35): /etc/rc.d/rc.nfsd restart | logger

Nov 12 06:47:28 Tower in.telnetd[2635]: connect from 192.168.178.25 (192.168.178.25)

Nov 12 06:47:33 Tower login[2636]: ROOT LOGIN on `pts/0' from `comp1'

Nov 12 06:50:16 Tower kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen

Nov 12 06:50:16 Tower kernel: ata2: edma_err_cause=00000020 pp_flags=00000003, SError=00180000

Nov 12 06:50:16 Tower kernel: ata2: SError: { 10B8B Dispar }

Nov 12 06:50:16 Tower kernel: ata2: hard resetting link

Nov 12 06:50:16 Tower kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen

Nov 12 06:50:16 Tower kernel: ata4: edma_err_cause=00000020 pp_flags=00000003, SError=00180000

Nov 12 06:50:16 Tower kernel: ata4: SError: { 10B8B Dispar }

Nov 12 06:50:16 Tower kernel: ata4: hard resetting link

Nov 12 06:50:19 Tower kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Nov 12 06:50:19 Tower kernel: ata2.00: configured for UDMA/133

Nov 12 06:50:19 Tower kernel: ata2: EH complete

Nov 12 06:50:19 Tower kernel: sdb: detected capacity change from 0 to 250059350016

Nov 12 06:50:20 Tower kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Nov 12 06:50:20 Tower kernel: ata4.00: configured for UDMA/133

Nov 12 06:50:20 Tower kernel: ata4: EH complete

Nov 12 06:50:20 Tower kernel: sdd: detected capacity change from 0 to 250059350016

Nov 12 06:57:26 Tower kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen

Nov 12 06:57:26 Tower kernel: ata4: edma_err_cause=00000020 pp_flags=00000000, SError=00180000

Nov 12 06:57:26 Tower kernel: ata4: SError: { 10B8B Dispar }

Nov 12 06:57:26 Tower kernel: ata4: hard resetting link

Nov 12 06:57:26 Tower kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen

Nov 12 06:57:26 Tower kernel: ata3: edma_err_cause=00000020 pp_flags=00000003, SError=00180000

Nov 12 06:57:26 Tower kernel: ata3: SError: { 10B8B Dispar }

Nov 12 06:57:26 Tower kernel: ata3: hard resetting link

 

Anyone any idea ?

 

I decided to ignore it for now and am transfering 1,6 tb test data on the unraid server. And i have not seen it again in the logs as far as i can see, but still i wonder why this happened and if i need to wurry about it.

 

 

Howdy, and I'm really sorry.  I spent over half a day, 2 days ago, trying to research this and better understand SATA errors, especially dispar, and did not find very good answers, and ran out of time to formulate a response.  The best I could find is that the power supply is the most likely cause.  If possible, would you be able to upgrade your power supply?

 

I have to go now, and am going to find it hard to find more time for the next week.

Hehe no need to appolgize,

 

It could be the power supply it is a coolermaster silent pro 500 watt, it delivers 34A (408w) on the 12 volt line and is single rail. I think i have a 700 watt lying around altho for 12 disks i really hope i do not need such a beefy supply.

 

I will measure the 12 volt next time i get this problem to see if i can confirm the theory.

 

Anyway;s i believe if it's the power supply i probably will get the errors again if i do a parity check, so i will try that after the test data has copied.