December 31, 200718 yr I am having a weird problem... When I transfer a 700mb file over the network to an share on my unRaid server, it takes about a minute. If I try to transfer it back to my computer, it estimates around 130minutes. Any idea why this is happening? I tried pulling the file off from different computers and getting the same problem. I am tried moving folders around on one of my unRaid drives and that also seems to take eternity. I dont know much about Linux and unRaid, but it takes about a blink of an eye to do this in Windows.
December 31, 200718 yr *cough*vista?*cough* If you are on your windows PC and you're moving files from one drive to the other on the unRaid, you're actually moving the file to your windows PC and then to the other drive. You can use the cp or mv command from the telnet shell (e.g. to move file disk1/DVD/The Matrix.iso to disk2/DVD/The Matrix.iso you'd run mv "/mnt/disk1/DVD/The Matrix.iso" /mnt/disk2/DVD/. This assumes that the DVD directory already exists on disk2.
January 4, 200818 yr I am having a weird problem... When I transfer a 700mb file over the network to an share on my unRaid server, it takes about a minute. If I try to transfer it back to my computer, it estimates around 130minutes. Any idea why this is happening? I tried pulling the file off from different computers and getting the same problem. I am tried moving folders around on one of my unRaid drives and that also seems to take eternity. I dont know much about Linux and unRaid, but it takes about a blink of an eye to do this in Windows. So there's three test cases you've run: 1) Source -> Unraid 2) Unraid -> Source 3) Unraid Drive X -> Unraid Drive Y Case 1 has 700mb in a minute, and case 2 has 700mb in forever. I'll bet that your unfamiliarity with Unix means that for case 3 you really did the Drive X -> Drive Y on your windows box, right? If so, that means what you were really doing was this: Unraid Drive X -> Source -> Unraid Drive Y I bet the issue is a flaky Network card/chip either on the Unraid box or your Windows Box. I had the same issue on my Unraid box in that I could upload files FAST but viewing or otherwise moving files from the Unraid box would be extremely slow. Replacing the network card with a high quality Intel card fixed that problem. Bunch of different ways to troubleshoot this, but the fastest way is to simply buy a new network card, plug it into your Unraid box and see if the problem goes away. If it doesn't, try the new card in the Windows box and see if it goes away. Good luck!
January 6, 200818 yr Author Thanks for the tip. I am in the process of moving into our new home and have the server down. I will post the syslog when I get some time.
January 29, 200818 yr Author Here is my syslog Jan 28 21:54:12 Tower kernel: [ 90.283563] ata1: SATA link down (SStatus 0 SCo ntrol 300) Jan 28 21:54:12 Tower kernel: [ 90.612935] ata2: SATA link down (SStatus 0 SCo ntrol 300) Jan 28 21:54:12 Tower kernel: [ 90.613130] JMB363: IDE controller at PCI slot 0000:06:00.1 Jan 28 21:54:12 Tower kernel: [ 90.613250] PCI: Enabling device 0000:06:00.1 ( 0000 -> 0001) Jan 28 21:54:12 Tower kernel: [ 90.613357] ACPI: PCI Interrupt 0000:06:00.1 -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 Jan 28 21:54:12 Tower kernel: [ 90.613593] JMB363: chipset revision 2 Jan 28 21:54:12 Tower kernel: [ 90.613693] JMB363: 100%% native mode on irq 11 Jan 28 21:54:12 Tower kernel: [ 90.613804] PCI: Setting latency timer of devic e 0000:06:00.1 to 64 Jan 28 21:54:12 Tower kernel: [ 90.613810] ide0: BM-DMA at 0x9b00-0x9b07, BIOS settings: hda:pio, hdb:pio Jan 28 21:54:12 Tower kernel: [ 90.614049] ide1: BM-DMA at 0x9b08-0x9b0f, BIOS settings: hdc:pio, hdd:pio Jan 28 21:54:12 Tower kernel: [ 90.614284] Probing IDE interface ide0... Jan 28 21:54:12 Tower kernel: [ 91.221774] Probing IDE interface ide1... Jan 28 21:54:12 Tower kernel: [ 91.822250] ahci 0000:00:1f.2: version 2.2 Jan 28 21:54:12 Tower kernel: [ 91.822268] ACPI: PCI Interrupt 0000:00:1f.2 -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 Jan 28 21:54:12 Tower kernel: [ 92.828739] ahci 0000:00:1f.2: AHCI 0001.0100 3 2 slots 6 ports 3 Gbps 0x3f impl SATA mode Jan 28 21:54:12 Tower kernel: [ 92.828913] ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part Jan 28 21:54:12 Tower kernel: [ 92.829019] PCI: Setting latency timer of devic e 0000:00:1f.2 to 64 Jan 28 21:54:12 Tower kernel: [ 92.829322] scsi3 : ahci Jan 28 21:54:12 Tower kernel: [ 92.829543] scsi4 : ahci Jan 28 21:54:12 Tower kernel: [ 92.829720] scsi5 : ahci Jan 28 21:54:12 Tower kernel: [ 92.829896] scsi6 : ahci Jan 28 21:54:12 Tower kernel: [ 92.830076] scsi7 : ahci Jan 28 21:54:12 Tower kernel: [ 92.830255] scsi8 : ahci Jan 28 21:54:12 Tower kernel: [ 92.830374] ata3: SATA max UDMA/133 cmd 0xf8822 100 ctl 0x00000000 bmdma 0x00000000 irq 11 Jan 28 21:54:12 Tower kernel: [ 92.830545] ata4: SATA max UDMA/133 cmd 0xf8822 180 ctl 0x00000000 bmdma 0x00000000 irq 11 Jan 28 21:54:12 Tower kernel: [ 92.830716] ata5: SATA max UDMA/133 cmd 0xf8822 200 ctl 0x00000000 bmdma 0x00000000 irq 11 Jan 28 21:54:12 Tower kernel: [ 92.830886] ata6: SATA max UDMA/133 cmd 0xf8822 280 ctl 0x00000000 bmdma 0x00000000 irq 11 Jan 28 21:54:12 Tower kernel: [ 92.832634] ata7: SATA max UDMA/133 cmd 0xf8822 300 ctl 0x00000000 bmdma 0x00000000 irq 11 Jan 28 21:54:12 Tower kernel: [ 92.832806] ata8: SATA max UDMA/133 cmd 0xf8822 380 ctl 0x00000000 bmdma 0x00000000 irq 11 Jan 28 21:54:12 Tower kernel: [ 93.357708] ata3: SATA link up 3.0 Gbps (SStatu s 123 SControl 300) Jan 28 21:54:12 Tower kernel: [ 93.378345] ata3.00: ATA-8: SAMSUNG HD501LJ, CR 100-12, max UDMA7 Jan 28 21:54:12 Tower kernel: [ 93.378449] ata3.00: 976773168 sectors, multi 0 : LBA48 NCQ (depth 31/32) Jan 28 21:54:12 Tower kernel: [ 93.380543] ata3.00: configured for UDMA/133 Jan 28 21:54:12 Tower kernel: [ 93.906664] ata4: SATA link up 3.0 Gbps (SStatu s 123 SControl 300) Jan 28 21:54:12 Tower kernel: [ 93.917217] ata4.00: ATA-8: SAMSUNG HD501LJ, CR 100-12, max UDMA7 Jan 28 21:54:12 Tower kernel: [ 93.917320] ata4.00: 976773168 sectors, multi 0 : LBA48 NCQ (depth 31/32) Jan 28 21:54:12 Tower kernel: [ 93.919418] ata4.00: configured for UDMA/133 Jan 28 21:54:12 Tower kernel: [ 94.326554] scsi 0:0:0:0: Direct-Access Kin gston DataTraveler 2.0 1.00 PQ: 0 ANSI: 2 Jan 28 21:54:12 Tower kernel: [ 94.327663] sd 0:0:0:0: [sda] 1994752 512-byte hardware sectors (1021 MB) Jan 28 21:54:12 Tower kernel: [ 94.328410] sd 0:0:0:0: [sda] Write Protect is off Jan 28 21:54:12 Tower kernel: [ 94.328513] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00 Jan 28 21:54:12 Tower kernel: [ 94.328515] sd 0:0:0:0: [sda] Assuming drive ca che: write through Jan 28 21:54:12 Tower kernel: [ 94.330781] sd 0:0:0:0: [sda] 1994752 512-byte hardware sectors (1021 MB) Jan 28 21:54:12 Tower kernel: [ 94.331528] sd 0:0:0:0: [sda] Write Protect is off Jan 28 21:54:12 Tower kernel: [ 94.331631] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00 Jan 28 21:54:12 Tower kernel: [ 94.331633] sd 0:0:0:0: [sda] Assuming drive ca che: write through Jan 28 21:54:12 Tower kernel: [ 94.331737] sda: sda1 Jan 28 21:54:12 Tower kernel: [ 94.335312] sd 0:0:0:0: [sda] Attached SCSI rem ovable disk Jan 28 21:54:12 Tower kernel: [ 94.335772] usb-storage: device scan complete Jan 28 21:54:12 Tower kernel: [ 94.445644] ata5: SATA link up 3.0 Gbps (SStatu s 123 SControl 300) Jan 28 21:54:12 Tower kernel: [ 94.456048] ata5.00: ATA-8: WDC WD5000AAKS-00YG A0, 12.01C02, max UDMA/133 Jan 28 21:54:12 Tower kernel: [ 94.456154] ata5.00: 976773168 sectors, multi 0 : LBA48 NCQ (depth 31/32) Jan 28 21:54:12 Tower kernel: [ 94.457039] ata5.00: configured for UDMA/133 Jan 28 21:54:12 Tower kernel: [ 94.784994] ata6: SATA link down (SStatus 0 SCo ntrol 300) Jan 28 21:54:12 Tower kernel: [ 95.114366] ata7: SATA link down (SStatus 0 SCo ntrol 300) Jan 28 21:54:12 Tower kernel: [ 95.443739] ata8: SATA link down (SStatus 0 SCo ntrol 300) Jan 28 21:54:12 Tower kernel: [ 95.443914] scsi 3:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5 Jan 28 21:54:12 Tower kernel: [ 95.444265] sd 3:0:0:0: [sdb] 976773168 512-byt e hardware sectors (500108 MB) Jan 28 21:54:12 Tower kernel: [ 95.444379] sd 3:0:0:0: [sdb] Write Protect is off Jan 28 21:54:12 Tower kernel: [ 95.444481] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jan 28 21:54:12 Tower kernel: [ 95.444496] sd 3:0:0:0: [sdb] Write cache: enab led, read cache: enabled, doesn't support DPO or FUA Jan 28 21:54:12 Tower kernel: [ 95.444705] sd 3:0:0:0: [sdb] 976773168 512-byt e hardware sectors (500108 MB) Jan 28 21:54:12 Tower kernel: [ 95.444817] sd 3:0:0:0: [sdb] Write Protect is off Jan 28 21:54:12 Tower kernel: [ 95.444919] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jan 28 21:54:12 Tower kernel: [ 95.444934] sd 3:0:0:0: [sdb] Write cache: enab led, read cache: enabled, doesn't support DPO or FUA Jan 28 21:54:12 Tower kernel: [ 95.445107] sdb: sdb1 Jan 28 21:54:12 Tower kernel: [ 95.468317] sd 3:0:0:0: [sdb] Attached SCSI dis k Jan 28 21:54:12 Tower kernel: [ 95.468643] scsi 4:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5 Jan 28 21:54:12 Tower kernel: [ 95.468964] sd 4:0:0:0: [sdc] 976773168 512-byt e hardware sectors (500108 MB) Jan 28 21:54:12 Tower kernel: [ 95.469077] sd 4:0:0:0: [sdc] Write Protect is off Jan 28 21:54:12 Tower kernel: [ 95.469179] sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Jan 28 21:54:12 Tower kernel: [ 95.469193] sd 4:0:0:0: [sdc] Write cache: enab led, read cache: enabled, doesn't support DPO or FUA Jan 28 21:54:12 Tower kernel: [ 95.469394] sd 4:0:0:0: [sdc] 976773168 512-byt e hardware sectors (500108 MB) Jan 28 21:54:12 Tower kernel: [ 95.469505] sd 4:0:0:0: [sdc] Write Protect is off Jan 28 21:54:12 Tower kernel: [ 95.469607] sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Jan 28 21:54:12 Tower kernel: [ 95.469621] sd 4:0:0:0: [sdc] Write cache: enab led, read cache: enabled, doesn't support DPO or FUA Jan 28 21:54:12 Tower kernel: [ 95.469793] sdc: sdc1 Jan 28 21:54:12 Tower kernel: [ 95.492192] sd 4:0:0:0: [sdc] Attached SCSI dis k Jan 28 21:54:12 Tower kernel: [ 95.492520] scsi 5:0:0:0: Direct-Access ATA WDC WD5000AAKS-0 12.0 PQ: 0 ANSI: 5 Jan 28 21:54:12 Tower kernel: [ 95.492845] sd 5:0:0:0: [sdd] 976773168 512-byt e hardware sectors (500108 MB) Jan 28 21:54:12 Tower kernel: [ 95.492958] sd 5:0:0:0: [sdd] Write Protect is off Jan 28 21:54:12 Tower kernel: [ 95.493060] sd 5:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Jan 28 21:54:12 Tower kernel: [ 95.493074] sd 5:0:0:0: [sdd] Write cache: enab led, read cache: enabled, doesn't support DPO or FUA Jan 28 21:54:12 Tower kernel: [ 95.493274] sd 5:0:0:0: [sdd] 976773168 512-byt e hardware sectors (500108 MB) Jan 28 21:54:12 Tower kernel: [ 95.493386] sd 5:0:0:0: [sdd] Write Protect is off Jan 28 21:54:12 Tower kernel: [ 95.493488] sd 5:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Jan 28 21:54:12 Tower kernel: [ 95.493502] sd 5:0:0:0: [sdd] Write cache: enab led, read cache: enabled, doesn't support DPO or FUA Jan 28 21:54:12 Tower kernel: [ 95.493685] sdd: sdd1 Jan 28 21:54:12 Tower kernel: [ 95.496253] sd 5:0:0:0: [sdd] Attached SCSI dis k Jan 28 21:54:12 Tower kernel: [ 95.496410] ACPI: PCI Interrupt 0000:06:00.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 Jan 28 21:54:12 Tower kernel: [ 96.501749] ahci 0000:06:00.0: AHCI 0001.0000 3 2 slots 2 ports 3 Gbps 0x3 impl SATA mode Jan 28 21:54:12 Tower kernel: [ 96.501921] ahci 0000:06:00.0: flags: 64bit ncq pm led clo pmp pio slum part Jan 28 21:54:12 Tower kernel: [ 96.502028] PCI: Setting latency timer of devic e 0000:06:00.0 to 64 Jan 28 21:54:12 Tower kernel: [ 96.502143] scsi9 : ahci Jan 28 21:54:12 Tower kernel: [ 96.502344] scsi10 : ahci Jan 28 21:54:12 Tower kernel: [ 96.502465] ata9: SATA max UDMA/133 cmd 0xf8838 100 ctl 0x00000000 bmdma 0x00000000 irq 11 Jan 28 21:54:12 Tower kernel: [ 96.502637] ata10: SATA max UDMA/133 cmd 0xf883 8180 ctl 0x00000000 bmdma 0x00000000 irq 11 Jan 28 21:54:12 Tower kernel: [ 96.831105] ata9: SATA link down (SStatus 0 SCo ntrol 300) Jan 28 21:54:12 Tower kernel: [ 97.160477] ata10: SATA link down (SStatus 0 SC ontrol 300) Jan 28 21:54:12 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Jan 28 21:54:12 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0. 0 netmask 255.0.0.0 lo Jan 28 21:54:12 Tower logger: /etc/rc.d/rc.inet1: /sbin/dhcpcd -d -t 60 -h Towe r eth0 Jan 28 21:54:12 Tower kernel: [ 108.501432] r8169: eth0: link up Jan 28 21:54:12 Tower kernel: [ 108.501449] r8169: eth0: link up Jan 28 21:54:12 Tower dhcpcd[1255]: broadcasting DHCP_DISCOVER Jan 28 21:54:12 Tower dhcpcd[1255]: broadcastAddr option is missing in DHCP serv er response. Assuming 192.168.1.255 Jan 28 21:54:12 Tower dhcpcd[1255]: dhcpIPaddrLeaseTime=86400 in DHCP server res ponse. Jan 28 21:54:12 Tower dhcpcd[1255]: DHCP_OFFER received from (192.168.1.1) Jan 28 21:54:12 Tower dhcpcd[1255]: broadcasting DHCP_REQUEST for 192.168.1.144 Jan 28 21:54:12 Tower dhcpcd[1255]: dhcpIPaddrLeaseTime=86400 in DHCP server res ponse. Jan 28 21:54:12 Tower dhcpcd[1255]: DHCP_ACK received from (192.168.1.1) Jan 28 21:54:12 Tower ifplugd(eth0)[1344]: ifplugd 0.28 initializing. Jan 28 21:54:12 Tower ifplugd(eth0)[1344]: Using interface eth0/00:50:8D:9D:C4:C 7 with driver <r8169> (version: 2.2LK-NAPI) Jan 28 21:54:12 Tower ifplugd(eth0)[1344]: Using detection mode: SIOCETHTOOL Jan 28 21:54:12 Tower ifplugd(eth0)[1344]: Initialization complete, link beat de tected. Jan 28 21:54:12 Tower ifplugd(eth0)[1344]: Executing '/etc/ifplugd/ifplugd.actio n eth0 up'. Jan 28 21:54:12 Tower ifplugd(eth0)[1344]: Program executed successfully. Jan 28 21:54:12 Tower kernel: [ 108.908744] fuse init (API version 7. Jan 28 21:54:12 Tower emhttp[1385]: unRAID System Management Utility version 4.2 Jan 28 21:54:12 Tower emhttp[1385]: Copyright © 2005-2007, Lime Technology, LL C Jan 28 21:54:12 Tower emhttp[1385]: Basic key detected, registered to: Unregiste red (-3) Jan 28 21:54:12 Tower emhttp[1385]: shcmd (1): cp /boot/config/group /etc Jan 28 21:54:12 Tower emhttp[1385]: shcmd (2): cp /boot/config/passwd /etc Jan 28 21:54:12 Tower emhttp[1385]: shcmd (3): cp /boot/config/smbpasswd /etc/sa mba/private Jan 28 21:54:12 Tower emhttp[1385]: Device inventory: Jan 28 21:54:12 Tower emhttp[1385]: pci-0000:00:1f.2-scsi-2:0:0:0 (sdd) scsi-SAT A_WDC_WD5000AAKS-_WD-WCAS83683841 Jan 28 21:54:12 Tower emhttp[1385]: pci-0000:00:1f.2-scsi-1:0:0:0 (sdc) scsi-SAT A_SAMSUNG_HD501LJS0MUJ1FPB24936 Jan 28 21:54:12 Tower emhttp[1385]: pci-0000:00:1f.2-scsi-0:0:0:0 (sdb) scsi-SAT A_SAMSUNG_HD501LJS0MUJ1FPB24935 Jan 28 21:54:12 Tower emhttp[1385]: shcmd (4): rmmod md-mod >>/var/log/go 2>&1 Jan 28 21:54:12 Tower emhttp[1385]: shcmd (4): exit status: 1 Jan 28 21:54:12 Tower emhttp[1385]: shcmd (5): modprobe md-mod super=/boot/confi g/super.dat slots=8,16,8,32,8,48 >>/var/log/go 2>&1 Jan 28 21:54:12 Tower kernel: [ 108.943688] md: unRAID driver 0.92.0 installed Jan 28 21:54:12 Tower kernel: [ 109.287396] md: xor using function: pIII_sse (4 932.400 MB/sec) Jan 28 21:54:12 Tower emhttp[1385]: shcmd (6): /usr/sbin/hdparm -S242 /dev/sdb > /dev/null Jan 28 21:54:13 Tower emhttp[1385]: shcmd (7): /usr/sbin/hdparm -S242 /dev/sdc > /dev/null Jan 28 21:54:13 Tower emhttp[1385]: shcmd (: /usr/sbin/hdparm -S242 /dev/sdd > /dev/null Jan 28 21:54:13 Tower emhttp[1385]: shcmd (9): killall -w smbd nmbd Jan 28 21:54:14 Tower emhttp[1385]: shcmd (10): /usr/sbin/nmbd -D Jan 28 21:54:14 Tower emhttp[1385]: shcmd (11): /usr/sbin/smbd -D Jan 28 21:54:14 Tower emhttp[1385]: driver cmd: start STOPPED Jan 28 21:54:14 Tower kernel: [ 110.698494] mdcmd (3): start Jan 28 21:54:14 Tower kernel: [ 110.699303] unraid: allocated 7030kB Jan 28 21:54:14 Tower kernel: [ 110.699404] md1: running, size: 488386552 block s Jan 28 21:54:14 Tower kernel: [ 110.699419] md2: running, size: 488386552 block s Jan 28 21:54:14 Tower emhttp[1385]: driver cmd: check Jan 28 21:54:14 Tower kernel: [ 110.839896] mdcmd (5): check Jan 28 21:54:14 Tower kernel: [ 110.839904] md: recovery thread got woken up .. . Jan 28 21:54:14 Tower kernel: [ 110.839906] md: recovery thread checking parity ... Jan 28 21:54:14 Tower emhttp[1385]: shcmd (12): udevsettle Jan 28 21:54:14 Tower kernel: [ 110.845495] md: using 1152k window, over a tota l of 488386552 blocks. Jan 28 21:54:14 Tower emhttp[1436]: shcmd (13): mkdir /mnt/disk1 Jan 28 21:54:14 Tower emhttp[1436]: shcmd (14): mount -t reiserfs -o noatime,nod iratime /dev/md1 /mnt/disk1 >/dev/null 2>&1 Jan 28 21:54:14 Tower emhttp[1440]: shcmd (13): mkdir /mnt/disk2 Jan 28 21:54:14 Tower emhttp[1440]: shcmd (14): mount -t reiserfs -o noatime,nod iratime /dev/md2 /mnt/disk2 >/dev/null 2>&1 Jan 28 21:54:14 Tower kernel: [ 111.103341] ReiserFS: md1: found reiserfs forma t "3.6" with standard journal Jan 28 21:54:14 Tower kernel: [ 111.103356] ReiserFS: md1: using ordered data m ode Jan 28 21:54:14 Tower kernel: [ 111.111680] ReiserFS: md1: journal params: devi ce md1, size 8192, journal first block 18, max trans len 1024, max batch 900, ma x commit age 30, max trans age 30 Jan 28 21:54:14 Tower kernel: [ 111.112074] ReiserFS: md1: checking transaction log (md1) Jan 28 21:54:14 Tower kernel: [ 111.120864] ReiserFS: md2: found reiserfs forma t "3.6" with standard journal Jan 28 21:54:14 Tower kernel: [ 111.120878] ReiserFS: md2: using ordered data m ode Jan 28 21:54:14 Tower kernel: [ 111.189029] ReiserFS: md2: journal params: devi ce md2, size 8192, journal first block 18, max trans len 1024, max batch 900, ma x commit age 30, max trans age 30 Jan 28 21:54:14 Tower kernel: [ 111.189409] ReiserFS: md2: checking transaction log (md2) Jan 28 21:54:14 Tower kernel: [ 111.279037] ReiserFS: md1: Using r5 hash to sor t names Jan 28 21:54:14 Tower kernel: [ 111.283761] ReiserFS: md2: Using r5 hash to sor t names Jan 28 21:54:15 Tower kernel: [ 111.407438] can't shrink filesystem on-line Jan 28 21:54:15 Tower kernel: [ 111.482444] can't shrink filesystem on-line Jan 28 21:54:15 Tower emhttp[1385]: shcmd (13): mkdir /mnt/user Jan 28 21:54:15 Tower emhttp[1385]: shcmd (14): shfs /mnt/user 0 Jan 28 21:54:15 Tower emhttp[1385]: shcmd (15): killall -HUP smbd Jan 28 22:02:49 Tower kernel: [ 624.443685] spurious 8259A interrupt: IRQ7. Jan 28 22:08:05 Tower emhttp[1385]: shcmd (16): killall -w smbd nmbd Jan 28 22:08:07 Tower emhttp[1385]: shcmd (17): hostname Tower Jan 28 22:08:07 Tower emhttp[1385]: shcmd (18): /usr/sbin/nmbd -D Jan 28 22:08:07 Tower emhttp[1385]: shcmd (19): /usr/sbin/smbd -D Jan 28 22:08:59 Tower emhttp[1385]: shcmd (20): killall -w smbd nmbd Jan 28 22:09:01 Tower emhttp[1385]: shcmd (21): hostname Tower Jan 28 22:09:01 Tower emhttp[1385]: shcmd (22): /usr/sbin/nmbd -D Jan 28 22:09:01 Tower emhttp[1385]: shcmd (23): /usr/sbin/smbd -D Jan 28 22:13:29 Tower in.telnetd[1542]: connect from 192.168.1.125 (192.168.1.12 5) Jan 28 22:13:42 Tower login[1543]: invalid password for `root' on `pts/0' from `192.168.1.125' Jan 28 22:13:46 Tower login[1543]: ROOT LOGIN on `pts/0' from `192.168.1.125' root@Tower:~#
January 29, 200818 yr madhookup, I posted about a similar problem. I was focused on DVD playback streaming, but the reality was it was taking forever to suck data FROM the unRAID. My problem was the onboard Realtek NIC. If you are using the integrated NIC, seriously just try using an add-in NIC instead.
January 29, 200818 yr Author Thanks for the advice, does this look like a good choice? http://www.newegg.com/Product/Product.aspx?Item=N82E16833106121
January 29, 200818 yr Thanks for the advice, does this look like a good choice? http://www.newegg.com/Product/Product.aspx?Item=N82E16833106121 Looks as good as any... This line in your syslog indicates you are indeed using the realtec driver that is currently giving poor read performance. Using interface eth0/00:50:8D:9D:C4:C7 with driver <r8169> (version: 2.2LK-NAPI) Don't forget to disable the onboard NIC in your motherboard bios when you install the new Intel based one. Joe L.
January 29, 200818 yr Thanks for the advice, does this look like a good choice? http://www.newegg.com/Product/Product.aspx?Item=N82E16833106121 fyi - I tried my first experimental build this last weekend on a box that has just happened to already have this nic (onboard was disabled in the bios). I had added it as the onboard was only 10/100. It came right up with unRaid - no problems and it has worked flawlessly with XP and Win2k OS'es as well. This would be my first recommendation for an add-on nic for unRaid or any build for that matter.
January 29, 200818 yr Author Good to hear JRS! Thanks for all the help! I will post my results when I get the NIC in incase anyone else has this problem in the future.
January 29, 200818 yr That NIC looks good. However, I have heard someone recommend a PCI Express-based GigE NIC. Something about the PCI bus maxing out at 33MBps? I dunno, and that's probably not a concern for most anyway--he was talking about HD audio/video streaming.
February 6, 200818 yr I also think I am getting sub-par transfer speeds, and my Unraid server does indeed have a Realtek nic, so I bought 2 of those same Intel cards you posted. Tonight I put 1 in the Unraid server and 1 in my main PC (easier to change out that than the media pc). There was little to no improvement in read speeds. I tested copying a 7GB file from Unraid to my machine, under both XP and Vista SP1 (which dramatically increased network performance, although still not quite as good as XP). It took 6 minutes 35 seconds to copy on XP, and slightly longer on Vista. I calculated that out to about 14.5 MBytes/s on XP and 14 MBytes/s on Vista. Wondering if my cheap Netgear switch might be an issue, I also tried connecting the 2 machines directly to avoid the switch altogether, and it made absolutely no difference in transfer speed. Are these read rates reasonable, or are there other things I should look into? I've seen people on the net claim to get 70-80 MB/s transfer rates from Win2003 servers, so this seems really slow compared to that, but maybe they are exagerating or confusing units (i.e. 80 Mbit/s would be about 10 MByte/s, which is a lot closer).
February 6, 200818 yr Just to chime in here.. I get 17MB on transfers TO the Unraid server. On transfer FROM the server i get 37MB. When I run the dd if='/mnt/disk3/DVD/Apollo 13/apollo13.iso' of=/dev/null i get about 70MB. I am running on a gig network. Does these speeds sound reasonable?
Archived
This topic is now archived and is closed to further replies.