TRWOV Posted April 25, 2020 Share Posted April 25, 2020 (edited) I put together a new unraid box for personal files and stuff instead of mixing them with the media box but I'm getting some slow transfer speeds both up and down, around 10MB/s. My other unraid box does 30-40MB/s up and 70-80MB/s down which is normal AFAIK. Now, I'm using the trial key as I'd like to buy the license next month (as we're going back to work in two more weeks and money is tight xc ) so I just want to know if this is normal for the trial mode or if I should look for some issue or default setting that I need to change. The drives came from my other box; the drives are ok, I just replaced them with bigger ones. EDIT: the ethernet cable is a CAT5e, tested it with the other box and transfer speeds are fine so I ruled that out Edited April 25, 2020 by TRWOV Quote Link to comment
JorgeB Posted April 25, 2020 Share Posted April 25, 2020 5 minutes ago, TRWOV said: so I just want to know if this is normal for the trial mode No. Quote Link to comment
TRWOV Posted April 25, 2020 Author Share Posted April 25, 2020 bummer, I'll look into the settings again just in case I missed something The switch is a gigabit swicht but IDK, can a switch go bad on the gigabit line and fallback to 100mbps?? The boxes are on different rooms and thus different switches. I think I have a spare, I'll post back ASAP Quote Link to comment
TRWOV Posted April 25, 2020 Author Share Posted April 25, 2020 (edited) Ok more tests: since both have the same motheboard (Asus C60M1-I, love those paired with Node cases ) I swapped the mobo just in case the ethernet port on the board was bad (or wrong settings). Nope, same issue. Putting back the other mobo and looking at the dashboard it's detected as gigabit so I think that leaves out the switch then?? The weird thing is that the other computers connected to the same switch run ok... BTW, I'm using big files for testing, so no random seeks. Edited April 25, 2020 by TRWOV Quote Link to comment
JorgeB Posted April 25, 2020 Share Posted April 25, 2020 You can post the diags grabbed after or during a transfer, there might be some clues there. Quote Link to comment
TRWOV Posted April 25, 2020 Author Share Posted April 25, 2020 What should I post? syslog.txt? Quote Link to comment
TRWOV Posted April 25, 2020 Author Share Posted April 25, 2020 (edited) ohh, it's showing several notices on ata4 Does "Apr 24 08:43:55 Media kernel: ata4.00: configured for UDMA/33" means what I think it means? Quote Apr 24 08:43:49 Media kernel: ata4.00: status: { DRDY } Apr 24 08:43:49 Media kernel: ata4: hard resetting link Apr 24 08:43:55 Media kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 24 08:43:55 Media kernel: ata4.00: configured for UDMA/33 Apr 24 08:43:55 Media kernel: ata4: EH complete Apr 24 08:43:55 Media kernel: ata4.00: exception Emask 0x10 SAct 0x3e00 SErr 0x10200 action 0xe frozen Apr 24 08:43:55 Media kernel: ata4.00: irq_stat 0x00400000, PHY RDY changed Apr 24 08:43:55 Media kernel: ata4: SError: { Persist PHYRdyChg } Apr 24 08:43:55 Media kernel: ata4.00: failed command: READ FPDMA QUEUED Apr 24 08:43:55 Media kernel: ata4.00: cmd 60/40:48:c8:31:91/05:00:00:00:00/40 tag 9 ncq dma 688128 in Apr 24 08:43:55 Media kernel: res 40/00:68:08:42:91/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Apr 24 08:43:55 Media kernel: ata4.00: status: { DRDY } Apr 24 08:43:55 Media kernel: ata4.00: failed command: READ FPDMA QUEUED Apr 24 08:43:55 Media kernel: ata4.00: cmd 60/78:50:08:37:91/01:00:00:00:00/40 tag 10 ncq dma 192512 in Apr 24 08:43:55 Media kernel: res 40/00:68:08:42:91/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Apr 24 08:43:55 Media kernel: ata4.00: status: { DRDY } Apr 24 08:43:55 Media kernel: ata4.00: failed command: READ FPDMA QUEUED Apr 24 08:43:55 Media kernel: ata4.00: cmd 60/48:58:80:38:91/04:00:00:00:00/40 tag 11 ncq dma 561152 in Apr 24 08:43:55 Media kernel: res 40/00:68:08:42:91/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Apr 24 08:43:55 Media kernel: ata4.00: status: { DRDY } Apr 24 08:43:55 Media kernel: ata4.00: failed command: READ FPDMA QUEUED Apr 24 08:43:55 Media kernel: ata4.00: cmd 60/40:60:c8:3c:91/05:00:00:00:00/40 tag 12 ncq dma 688128 in Apr 24 08:43:55 Media kernel: res 40/00:68:08:42:91/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Apr 24 08:43:55 Media kernel: ata4.00: status: { DRDY } Apr 24 08:43:55 Media kernel: ata4.00: failed command: READ FPDMA QUEUED Apr 24 08:43:55 Media kernel: ata4.00: cmd 60/40:68:08:42:91/05:00:00:00:00/40 tag 13 ncq dma 688128 in Apr 24 08:43:55 Media kernel: res 40/00:68:08:42:91/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Edited April 25, 2020 by TRWOV Quote Link to comment
TRWOV Posted April 25, 2020 Author Share Posted April 25, 2020 I'll try swaping the sata cables Quote Link to comment
JorgeB Posted April 25, 2020 Share Posted April 25, 2020 Yes, try that, also check/replace power cable, without full diags it's difficult to say more. Quote Link to comment
TRWOV Posted April 25, 2020 Author Share Posted April 25, 2020 Apparently the sata cables were the culprit Quote Link to comment
Recommended Posts
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.