December 19, 201015 yr I've been searching but the results posted haven't helped fix this problem so far... Terrible speeds is what im trying to fix. 2.5 (on a WHS server) and 12.5Mpbs (on a Win7 box) My Unraid box; ASUS P5kpl - cm (also tried a Biostar P43D3) Intel Dual Core E5200 4g OCZ memory 4 WD 2tb black 6 Samsung 2tb (not currently installed) Ethtool eth0 shows speed capable of 1000 but currently at 100 Thanks in advance for any help! http://www.heartlandrc.com/dbtech/syslog.txt
December 19, 201015 yr If you're running at 100Mb on the network, that would explain the slow writes. Fast Ethernet is limited to 12.5Mbps on the wire. I've also experienced slow writes from WHS (Windows 2003 based). I think the protocol tuning on WHS is not optimal. When you switched between your ASUS and Biostar boards, were both boards running Eth0 at 100Mbps? Do you have anything in the network (switch, router, etc.) that is not Gig-E? What does your network utilization look like? See my recent post troubleshooting slow writes: http://lime-technology.com/forum/index.php?topic=9602.0 Looking at the log file, you're also getting errors with your flash drive. Dec 19 07:53:01 Tower kernel: read_file: error 2 opening /boot/config/super.dat Dec 19 07:53:01 Tower kernel: md: could not read superblock from /boot/config/super.dat
December 19, 201015 yr Looking at the log file, you're also getting errors with your flash drive. Dec 19 07:53:01 Tower kernel: read_file: error 2 opening /boot/config/super.dat Dec 19 07:53:01 Tower kernel: md: could not read superblock from /boot/config/super.dat That message is expected since the super.dat file does not exist until after a disk is assigned to the array, and up to that point, no array had been defined. It could not read the file since it did not yet exist. There is nothing wrong with the flash drive. Joe L.
December 19, 201015 yr That message is expected since the super.dat file does not exist until after a disk is assigned to the array, and up to that point, no array had been defined. It could not read the file since it did not yet exist. There is nothing wrong with the flash drive. Point taken - always a learning experience. I see that it goes on to initialize the superblock file... Dec 19 07:53:01 Tower kernel: md: initializing superblock Is this something that only happens at first boot? I don't see a similar error in my log.
December 19, 201015 yr I also have slow transfer rates, but I think it is due to my hardware / bus speed. I am running the following Biostar + AM2 motherboard AMD dual core cpu 1gb memory Promise TX4 (4 port SATA PCI) 9 disks -- 6 onboard sata / 3 on the promise pci controller Gigabit ethernet I pull from my unraid with no probs, at appox 30 - 40mb/sec but when I am writing data to my server i get approx 2.3mb -- 7mb/sec ... I am not that upset about it, it would be nice if it was faster !! but I just figure it is doing parity on the fly so it takes a while longer to write. I did some reading about a cache disk, but was not sure if the cache disk had to match my parity disk size (2TB) or if I could use any disk size. Thx
December 19, 201015 yr Author I may not have setup the array at that point. I formated the flash drive and went back through every setting I could find.. no difference. Swapped MOBO's, no difference. The network is all 1000 but have not checked the integrity of the cable/ends. I have moved the server to another spot with the same results. *EDIT* I just ran a test download from the UnRaid to a win7 box and its smokin' fast at 49Mbps, but upload to the UnRaid from that same machine and it tops out at 2.8Mbps At that rate it would take me a month to transfer my data off the WHS
December 19, 201015 yr I may not have setup the array at that point. I formated the flash drive and went back through every setting I could find.. no difference. Swapped MOBO's, no difference. The network is all 1000 but have not checked the integrity of the cable/ends. I have moved the server to another spot with the same results. *EDIT* I just ran a test download from the UnRaid to a win7 box and its smokin' fast at 49Mbps, but upload to the UnRaid from that same machine and it tops out at 2.8Mbps At that rate it would take me a month to transfer my data off the WHS Cat5e use separate transmit and receive pairs. It would be possible to have different speeds in different directions if the cabling was not correct. step 1 would be to try a different cable.
December 19, 201015 yr Author Different cable and different location as well. Its about 3ft from the switch right now, same results.
December 19, 201015 yr I had a similar situation that I spent hours trying to solve. It turned out to be the gigabit switch. Not sure if it's the drivers unRAID uses or what but win7 to win7 on the SAME mobo/hardware was blazing fast, on unRAID it was crawling. Swapped the switch to a Netgear gigabit and all is well.
December 20, 201015 yr Author I bound and determained to make this work! There's got to be something simple im missing here, just don't know what that would be. I just took down the entire network to form a simple setup; WHS box Win7 box UnRaid box DGS-2208 8-Port 10/100/1000 All boxes have onboard gigbit eth new cable run from each device At times the speed is so slow it stops transfering and looses connection. Its only happening with the UnRaid box though. Transferring from WHS to Win7 is upwards of 50Mb/s
December 20, 201015 yr Author *FIXED* The problem turned out to be a failing drive in the WHS system. Why this affected transfers from the UnRaid box to the Win7 box I'll never know but once the bad WHS drive was removed my transfer rate went from 180bps (yes that slow) to just over 40MB/s! She's flyin now Also forgot to mention I went ahead and installed the 5.0beta as well, last ditch effort I guess... Here's my speed as im shoving files into this machine as fast as i can!
Archived
This topic is now archived and is closed to further replies.