Disconnection during transfer

[tafkap]

Hi,

i have a problem when i transfer a file to my unRAID server. The transfer begin with about 40Mb/s, and suddenly after some seconds the transfer does nothing and resume and does nothing etc. i don't know what happen. I must test on an other PC.

I don't use the network card's motherboard but a D-Link DGE-528T.

Any idea ?

Tonight i will post the log file.

[Billped]

Previously you had a network cable issue.  Are you perhaps bending/kinking the cable?


Bill

[tafkap]

No i don't thinks so because it's a new cable and small, about 50 centimeters.

[tafkap]

Shit, and now i have errors on parity disk, i changed the SATA cable but i have always errors. 

One part of my log file :

Code: [Select]

Feb  8 19:29:52 Tower in.telnetd[1176]: connect from 192.168.0.5 (192.168.0.5)
Feb  8 19:29:53 Tower login[1177]: ROOT LOGIN  on `pts/0' from `192.168.0.5'
Feb  8 19:30:39 Tower kernel: [  110.220002] spurious 8259A interrupt: IRQ7.
Feb  8 19:39:12 Tower kernel: [  622.182392] spurious 8259A interrupt: IRQ15.
Feb  8 19:58:31 Tower kernel: [ 1779.019024] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Feb  8 19:58:31 Tower kernel: [ 1779.019029] ata1.00: (BMDMA stat 0x25)
Feb  8 19:58:31 Tower kernel: [ 1779.019037] ata1.00: cmd c8/00:00:27:e0:c3/00:00:00:00:00/e7 tag 0 cdb 0x0 data 131072 in
Feb  8 19:58:31 Tower kernel: [ 1779.019040]          res 51/40:e5:43:e0:c3/00:00:00:00:00/e7 Emask 0x9 (media error)
Feb  8 19:58:31 Tower kernel: [ 1779.153566] ata1.00: configured for UDMA/133
Feb  8 19:58:31 Tower kernel: [ 1779.153574] ata1: EH complete
Feb  8 19:58:34 Tower kernel: [ 1782.081471] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Feb  8 19:58:34 Tower kernel: [ 1782.081476] ata1.00: (BMDMA stat 0x25)
Feb  8 19:58:34 Tower kernel: [ 1782.081483] ata1.00: cmd c8/00:00:27:e0:c3/00:00:00:00:00/e7 tag 0 cdb 0x0 data 131072 in
Feb  8 19:58:34 Tower kernel: [ 1782.081486]          res 51/01:e5:43:e0:c3/00:00:00:00:00/e7 Emask 0x1 (device error)
Feb  8 19:58:34 Tower kernel: [ 1782.137696] ata1.00: configured for UDMA/133
Feb  8 19:58:34 Tower kernel: [ 1782.137702] ata1: EH complete
Feb  8 19:58:37 Tower kernel: [ 1785.044601] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Feb  8 19:58:37 Tower kernel: [ 1785.044605] ata1.00: (BMDMA stat 0x25)
Feb  8 19:58:37 Tower kernel: [ 1785.044613] ata1.00: cmd c8/00:00:27:e0:c3/00:00:00:00:00/e7 tag 0 cdb 0x0 data 131072 in
Feb  8 19:58:37 Tower kernel: [ 1785.044615]          res 51/01:e5:43:e0:c3/00:00:00:00:00/e7 Emask 0x1 (device error)
Feb  8 19:58:37 Tower kernel: [ 1785.101879] ata1.00: configured for UDMA/133
Feb  8 19:58:37 Tower kernel: [ 1785.101885] ata1: EH complete
Feb  8 19:58:40 Tower kernel: [ 1788.007729] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Feb  8 19:58:40 Tower kernel: [ 1788.007733] ata1.00: (BMDMA stat 0x25)
Feb  8 19:58:40 Tower kernel: [ 1788.007740] ata1.00: cmd c8/00:00:27:e0:c3/00:00:00:00:00/e7 tag 0 cdb 0x0 data 131072 in
Feb  8 19:58:40 Tower kernel: [ 1788.007742]          res 51/40:e5:43:e0:c3/00:00:00:00:00/e7 Emask 0x9 (media error)
Feb  8 19:58:40 Tower kernel: [ 1788.066063] ata1.00: configured for UDMA/133
Feb  8 19:58:40 Tower kernel: [ 1788.066069] ata1: EH complete
Feb  8 19:58:43 Tower kernel: [ 1790.962582] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Feb  8 19:58:43 Tower kernel: [ 1790.962586] ata1.00: (BMDMA stat 0x25)
Feb  8 19:58:43 Tower kernel: [ 1790.962594] ata1.00: cmd c8/00:00:27:e0:c3/00:00:00:00:00/e7 tag 0 cdb 0x0 data 131072 in
Feb  8 19:58:43 Tower kernel: [ 1790.962596]          res 51/40:e5:43:e0:c3/00:00:00:00:00/e7 Emask 0x9 (media error)
Feb  8 19:58:43 Tower kernel: [ 1791.020265] ata1.00: configured for UDMA/133
Feb  8 19:58:43 Tower kernel: [ 1791.020271] ata1: EH complete
Feb  8 19:58:46 Tower kernel: [ 1793.942266] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Feb  8 19:58:46 Tower kernel: [ 1793.942271] ata1.00: (BMDMA stat 0x25)
Feb  8 19:58:46 Tower kernel: [ 1793.942278] ata1.00: cmd c8/00:00:27:e0:c3/00:00:00:00:00/e7 tag 0 cdb 0x0 data 131072 in
Feb  8 19:58:46 Tower kernel: [ 1793.942281]          res 51/01:e5:43:e0:c3/00:00:00:00:00/e7 Emask 0x1 (device error)
Feb  8 19:58:46 Tower kernel: [ 1793.994431] ata1.00: configured for UDMA/133
Feb  8 19:58:46 Tower kernel: [ 1793.994448] sd 1:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
Feb  8 19:58:46 Tower kernel: [ 1793.994453] sd 1:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Feb  8 19:58:46 Tower kernel: [ 1793.994458] Descriptor sense data with sense descriptors (in hex):
Feb  8 19:58:46 Tower kernel: [ 1793.994461]         72 03 13 00 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb  8 19:58:46 Tower kernel: [ 1793.994469]         07 c3 e0 43
Feb  8 19:58:46 Tower kernel: [ 1793.994473] sd 1:0:0:0: [sda] ASC=0x13 ASCQ=0x0
Feb  8 19:58:46 Tower kernel: [ 1793.994478] end_request: I/O error, dev sda, sector 130277443
Feb  8 19:58:46 Tower kernel: [ 1793.994488] ata1: EH complete
Feb  8 19:58:46 Tower kernel: [ 1793.994549] md0: read error!
Feb  8 19:58:46 Tower kernel: [ 1793.994552] handle_stripe read error: 130277376/0, count: 1
Feb  8 19:58:46 Tower kernel: [ 1793.994563] md0: read error!
Feb  8 19:58:46 Tower kernel: [ 1793.994566] handle_stripe read error: 130277384/0, count: 1
Feb  8 19:58:46 Tower kernel: [ 1793.994575] md0: read error!
Feb  8 19:58:46 Tower kernel: [ 1793.994578] handle_stripe read error: 130277392/0, count: 1
Feb  8 19:58:46 Tower kernel: [ 1793.994587] md0: read error!


[RobJ]

i have a problem when i transfer a file to my unRAID server. The transfer begin with about 40Mb/s, and suddenly after some seconds the transfer does nothing and resume and does nothing etc.

Are you aware that this sounds normal for the way that unRAID behaves (stopping and starting) when files greater than about 800MB's are written TO an unRAID server?  On a gigabit network, data is dumped into the server faster than can be written and processed to both the data and parity drives, so it appears to pause for a bit, and then resume transferring.  I believe Tom has hinted that he may be addressing this in the next release.

If you are aware of that, and this is something a lot more severe than that, then please excuse this comment.

I don't believe the parity disk errors are related to the above.  Sorry, seems to be a new problem.

[dunnno]

Bumping this 4 years old thread because I've got the exact same problem as told in the 1st post : pause during the first 10% of the transfer, then hang, then server got disconnected from my mac.

[RobJ]

Bumping this 4 years old thread because I've got the exact same problem as told in the 1st post : pause during the first 10% of the transfer, then hang, then server got disconnected from my mac.

I'm sorry, but this board is for v4 problems, and you are using a very different version than he did, plus the problem seems different in that he never mentioned getting disconnected.  If you don't mind, please start a new post within the General Support board, and include a syslog captured right after the issue happens.  See Include your VERSION and SYSTEM LOG for support issues.