unRAID Server release 3.0-beta4 available


limetech

Recommended Posts

Main change in this release has to do with logging.  In particular, we might have finally figured out the solution to the "connection reset by peer" messages constantly being written to the system log.  To turn these messages off, go to the Settings page and you will see a new variable called "Smb ports".  Default value of this is "445 139", but setting it to "139" should eliminate these messages for most people.  The cause of these messages is due to the way (drum roll please) Microsoft initiates connections on shares.  Read more about it here.

 

Another change of interest is that we are reverting to the pre-3.0 method of interrupt handling (that is, non-apic mode).  Using apic-mode was a sort of experiment to see what performance impact it might have.  apic-mode is necessary for multi-CPU support, but since unRAID Server doesn't yet support multi-CPU, we decided to take it out because it might be the source of "lock ups" and "slowdowns" some customers are seeing in the 3.0-beta releases.

 

If this release proves to be stable, it will become 3.0 "final", and we can carry on with 3.1 and new features.

 

If anyone is wondering what happened to 3.0-beta3 - that was a special build for a single customer solely to add VIA sata support.

 

Again, a big "Thanks" to all the beta testers!

 

Here are the release notes:

 

unRAID Server 3.0-beta4 Release Notes

Upgrade Instructions
--------------------
If you are currently running unRAID Server 3.0-beta1 or higher, it is only
necessary to copy the two files:

bzimage
bzroot

to the top directory of your Flash, replacing those files already on the
Flash.  There are two ways to do this:

1. Shut down your server, remove the Flash and plug it into your PC.  Copy
the two files from the new release, plug the Flash back into your server and
reboot it.

OR

2. If your server is running, simply copy the two new files to the 'flash'
share, go to the Management Utility and reboot.


If you are installing this release to a new Flash, please refer to
instructions on our website at:

http://www.lime-technology.com/wordpress/?page_id=19


Changes from 3.0-beta3 to 3.0-beta4
-----------------------------------

Improvement: messages previously sent only to console are now sent to syslog.

Improvement: Management Utilty Settings page:
- changed wording of "Master browser" to "Local master" to agree with
corresponding Samba config variable.
- added "Smb ports" setting to permit Samba to answer to ports 445 and 139,
or just 139.  Setting this to just port 139 may solve problem of syslog
filling up with superfluous "connection reset by peer" messages.

Bug fix: Managament Utility Devices page:
- if device is missing, also display device assignment string

Change: revert to pre-3.0 method of interrupt handling (non-apci). This may
solve issues related to ide irq timeouts.


Changes from 3.0-beta2 to 3.0-beta3
-----------------------------------

Improvement: added support for the following SATA chipsets:
- nvidia
- via
- sis
- vitesse


Changes from 3.0-beta1 to 3.0-beta2
-----------------------------------

Improvement: increased both Read and Write performance.  Give read streams
priority over write streams.

Improvement: added support for Realtek GigE and Broadcom GigE.

Improvement: added "Flash vendor" and "Flash Model" to Devices page.

Improvement: simplify hard drive assigment.

Bug Fix: prevent superfluous logging messages from filling up syslog.

Bug Fix: fix intermittant problem where configuration data in
config/super.dat could get trashed if user types 'poweroff' from a telnet
window.

Bug Fix: fixed problem where sometimes SATA drivers wouldn't get loaded
automatically.

Bug Fix: fixed problem where sometimes system would think drives are
spun-down, when actually they are spun-up.

Link to comment

Upgraded to 3.0 server release 3.0-beta4

Once reentered the flash drive, and restarted, was unable to launch //tower (the web management utility) for at least 10 minutes.

Logged in unraid as root and found the following error messages. My system currently has a parity drive and a data drive, no data moved on the system yet, both drives seagate 500GB Sata.

 

 

Tower login: root

Linux 2.4.33.

root@Tower:~#

root@Tower:~# tail -f /var/log/syslog

Sep 30 17:30:36 Tower smbd[1079]: [2006/09/30 17:30:36, 0] lib/util_sock.c:write

_socket(455)

Sep 30 17:30:36 Tower smbd[1079]:  write_socket: Error writing 4 bytes to socke

t 5: ERRNO = Connection reset by peer

Sep 30 17:30:36 Tower smbd[1079]: [2006/09/30 17:30:36, 0] lib/util_sock.c:send_

smb(647)

Sep 30 17:30:36 Tower smbd[1079]:  Error writing 4 bytes to client. -1. (Connec

tion reset by peer)

Sep 30 17:40:06 Tower emhttp[1006]: shcmd (11): ln -sf /usr/share/zoneinfo/Etc/G

MT /etc/localtime-copied-from

Sep 30 17:40:06 Tower emhttp[1006]: shcmd (12): cp /etc/localtime-copied-from /e

tc/localtime

Sep 30 17:40:06 Tower emhttp[1006]: shcmd (13): date -s '9/30/2006 9:39:33 AM'

Sep 30 09:39:33 Tower emhttp[1006]: shcmd (14): hwclock --localtime --systohc

Sep 30 09:39:34 Tower emhttp[1006]: shcmd (15): /usr/sbin/hdparm -y /dev/sdc >/d

ev/null

Sep 30 09:39:34 Tower emhttp[1006]: shcmd (16): /usr/sbin/hdparm -y /dev/sdb >/d

ev/null

 

Link to comment

I am using the xcopy command to copy files from my PC to the Tower. They are connected via a Gigabit switch, and my PC has a gigabit network card installed.

I am monitoring network speed via Task Manager, and it is using up to a maximum of 14%.

Is this normal? Are there any other ways to monitor network speed and overall network performance?

Link to comment

No "real" errors there... the "Error writing 4 bytes to client." and "Connection reset by peer" is a side effect of the way Windows connects to shares.  Try going to the Settings page and set the "Smb ports" to "139" & see if these go away.

 

As for not being able to connect for 10 minutes - that's definitely not riight.  If possible send entire syslog to me ([email protected]).

 

As for network speed - most you're going to get currently is around 15-20MB/sec sustained.  Is there a background parity-sync in process?

Link to comment

Tower is only saying parity is valid. How would I know if there is a parity check in the background?

Disks are really cool compared to the temperature in my other DIGN case (30C in Unraid server vs 41C in Dign case). I think the fan on the 4 in 3 unit is doing an admirable job.

How do I obtain a full syslog for you?

I typed the command tail -f /var/log/syslog just now and it is showing what I copied above. Any reason why it is not saying that all my divx movies are being transferred across, I have already copied probably 25 avi files across...

Installed DU Meter, and it is reporting varying speeds between 16 and 17 mB/sec.

Link to comment

Managed to transfer divxs fine to Unraid with xcopy, now transferring dvds.

When I got up this morning, Unraid was down, no connectivity even with telnet.

Hard reboot and then run the following command:

 

cat /var/log/syslog

 

This is the syslog:

 

================================================================================

 

Oct  1 19:12:55 Tower kernel: ACPI: Power Resource [uRP1] (off)

Oct  1 19:12:55 Tower kernel: ACPI: Power Resource [FDDP] (off)

Oct  1 19:12:55 Tower kernel: ACPI: Power Resource [LPTP] (off)

Oct  1 19:12:55 Tower kernel: ACPI: Power Resource [uRP2] (off)

Oct  1 19:12:55 Tower kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9

10 *11 12 14 15)

Oct  1 19:12:55 Tower kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs *3 4 5 6 7 9

10 11 12 14 15)

Oct  1 19:12:55 Tower kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9

10 11 12 14 15)

Oct  1 19:12:55 Tower kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9

*10 11 12 14 15)

Oct  1 19:12:55 Tower kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9

10 11 12 14 15) *0, disabled.

Oct  1 19:12:55 Tower kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9

10 11 12 14 15) *0, disabled.

Oct  1 19:12:55 Tower kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9

10 11 12 14 15) *0, disabled.

Oct  1 19:12:55 Tower kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *9

10 11 12 14 15)

Oct  1 19:12:55 Tower kernel: PCI: Probing PCI hardware

Oct  1 19:12:55 Tower kernel: ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11

Oct  1 19:12:55 Tower kernel: ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 3

Oct  1 19:12:55 Tower kernel: ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5

Oct  1 19:12:55 Tower kernel: ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10

Oct  1 19:12:55 Tower kernel: ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 9

Oct  1 19:12:55 Tower kernel: PCI: Using ACPI for IRQ routing

Oct  1 19:12:55 Tower kernel: Linux NET4.0 for Linux 2.4

Oct  1 19:12:55 Tower kernel: Based upon Swansea University Computer Society NET

3.039

Oct  1 19:12:55 Tower kernel: Initializing RT netlink socket

Oct  1 19:12:55 Tower kernel: Starting kswapd

Oct  1 19:12:55 Tower kernel: NTFS driver v1.1.22 [Flags: R/O]

Oct  1 19:12:55 Tower kernel: ACPI: Power Button (FF) [PWRF]

Oct  1 19:12:55 Tower kernel: ACPI: Processor [CPU1] (supports C1, 8 throttling

states)

Oct  1 19:12:55 Tower kernel: ACPI: Processor [CPU2] (supports C1, 8 throttling

states)

Oct  1 19:12:55 Tower kernel: keyboard: Timeout - AT keyboard not present?(ed)

Oct  1 19:12:55 Tower kernel: keyboard: Timeout - AT keyboard not present?(f4)

Oct  1 19:12:55 Tower kernel: RAMDISK driver initialized: 16 RAM disks of 120000

K size 1024 blocksize

Oct  1 19:12:55 Tower kernel: loop: loaded (max 8 devices)

Oct  1 19:12:55 Tower kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00

beta4-2.4

Oct  1 19:12:55 Tower kernel: ide: Assuming 33MHz system bus speed for PIO modes

; override with idebus=xx

Oct  1 19:12:55 Tower kernel: ICH6: IDE controller at PCI slot 00:1f.1

Oct  1 19:12:55 Tower kernel: ICH6: chipset revision 3

Oct  1 19:12:55 Tower kernel: ICH6: not 100%% native mode: will probe irqs later

Oct  1 19:12:55 Tower kernel:    ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings:

hda:pio, hdb:pio

Oct  1 19:12:55 Tower kernel:    ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings:

hdc:pio, hdd:pio

Oct  1 19:12:55 Tower kernel: SCSI subsystem driver Revision: 1.00

Oct  1 19:12:55 Tower kernel: kmod: failed to exec /sbin/modprobe -s -k scsi_hos

tadapter, errno = 2

Oct  1 19:12:55 Tower kernel: kmod: failed to exec /sbin/modprobe -s -k scsi_hos

tadapter, errno = 2

Oct  1 19:12:55 Tower kernel: usb.c: registered new driver usbdevfs

Oct  1 19:12:55 Tower kernel: usb.c: registered new driver hub

Oct  1 19:12:55 Tower kernel: ehci_hcd 00:1d.7: PCI device 8086:265c (Intel Corp

.)

Oct  1 19:12:55 Tower kernel: ehci_hcd 00:1d.7: irq 9, pci mem e000cc00

Oct  1 19:12:55 Tower kernel: usb.c: new USB bus registered, assigned bus number

1

Oct  1 19:12:55 Tower kernel: ehci_hcd 00:1d.7: enabled 64bit PCI DMA

Oct  1 19:12:55 Tower kernel: ehci_hcd 00:1d.7: USB 2.0 enabled, EHCI 1.00, driv

er 2003-Dec-29/2.4

Oct  1 19:12:55 Tower kernel: hub.c: USB hub found

Oct  1 19:12:55 Tower kernel: hub.c: 8 ports detected

Oct  1 19:12:55 Tower kernel: host/uhci.c: USB Universal Host Controller Interfa

ce driver v1.1

Oct  1 19:12:55 Tower kernel: host/uhci.c: USB UHCI at I/O 0xc800, IRQ 9

Oct  1 19:12:55 Tower kernel: usb.c: new USB bus registered, assigned bus number

2

Oct  1 19:12:55 Tower kernel: hub.c: USB hub found

Oct  1 19:12:55 Tower kernel: hub.c: 2 ports detected

Oct  1 19:12:55 Tower kernel: host/uhci.c: USB UHCI at I/O 0xcc00, IRQ 10

Oct  1 19:12:55 Tower kernel: usb.c: new USB bus registered, assigned bus number

3

Oct  1 19:12:55 Tower kernel: hub.c: USB hub found

Oct  1 19:12:55 Tower kernel: hub.c: 2 ports detected

Oct  1 19:12:55 Tower kernel: host/uhci.c: USB UHCI at I/O 0xd000, IRQ 5

Oct  1 19:12:55 Tower kernel: usb.c: new USB bus registered, assigned bus number

4

Oct  1 19:12:55 Tower kernel: hub.c: USB hub found

Oct  1 19:12:55 Tower kernel: hub.c: 2 ports detected

Oct  1 19:12:55 Tower kernel: host/uhci.c: USB UHCI at I/O 0xd400, IRQ 11

Oct  1 19:12:55 Tower kernel: usb.c: new USB bus registered, assigned bus number

5

Oct  1 19:12:55 Tower kernel: hub.c: USB hub found

Oct  1 19:12:55 Tower kernel: hub.c: 2 ports detected

Oct  1 19:12:55 Tower kernel: Initializing USB Mass Storage driver...

Oct  1 19:12:55 Tower kernel: usb.c: registered new driver usb-storage

Oct  1 19:12:55 Tower kernel: USB Mass Storage support registered.

Oct  1 19:12:55 Tower kernel: NET4: Linux TCP/IP 1.0 for NET4.0

Oct  1 19:12:55 Tower kernel: IP Protocols: ICMP, UDP, TCP, IGMP

Oct  1 19:12:55 Tower kernel: IP: routing cache hash table of 4096 buckets, 32Kb

ytes

Oct  1 19:12:55 Tower kernel: TCP: Hash tables configured (established 32768 bin

d 65536)

Oct  1 19:12:55 Tower kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0

.

Oct  1 19:12:55 Tower kernel: RAMDISK: Compressed image found at block 0

Oct  1 19:12:55 Tower kernel: hub.c: new USB device 00:1d.7-7, assigned address

2

Oct  1 19:12:55 Tower kernel: scsi0 : SCSI emulation for USB Mass Storage device

s

Oct  1 19:12:55 Tower kernel:  Vendor: SanDisk  Model: U3 Cruzer Micro  Rev:

2.15

Oct  1 19:12:55 Tower kernel:  Type:  Direct-Access                      ANSI

SCSI revision: 02

Oct  1 19:12:55 Tower kernel: Attached scsi removable disk sda at scsi0, channel

0, id 0, lun 0

Oct  1 19:12:55 Tower kernel: SCSI device sda: 1003153 512-byte hdwr sectors (51

4 MB)

Oct  1 19:12:55 Tower kernel: sda: Write Protect is off

Oct  1 19:12:55 Tower kernel: Partition check:

Oct  1 19:12:55 Tower kernel:  sda: sda1

Oct  1 19:12:55 Tower kernel: Freeing initrd memory: 25076k freed

Oct  1 19:12:55 Tower kernel: VFS: Mounted root (ext2 filesystem) readonly.

Oct  1 19:12:55 Tower kernel: Freeing unused kernel memory: 80k freed

Oct  1 19:12:55 Tower logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig lo 127.0.0.1

Oct  1 19:12:55 Tower logger: /etc/rc.d/rc.inet1:  /sbin/route add -net 127.0.0.

0 netmask 255.0.0.0 lo

Oct  1 19:12:55 Tower logger: /etc/rc.d/rc.hotplug start (entering script)

Oct  1 19:12:55 Tower kernel: sk98lin: Network Device Driver v8.35.2.3

Oct  1 19:12:55 Tower kernel: ©Copyright 1999-2006 Marvell®.

Oct  1 19:12:55 Tower kernel: eth0: Yukon Gigabit Ethernet 10/100/1000Base-T Ada

pter

Oct  1 19:12:55 Tower kernel:      PrefPort:A  RlmtMode:Check Link State

Oct  1 19:12:55 Tower kernel: ata1: SATA max UDMA/133 cmd 0xE800 ctl 0xE402 bmdm

a 0xD800 irq 10

Oct  1 19:12:55 Tower kernel: ata2: SATA max UDMA/133 cmd 0xE000 ctl 0xDC02 bmdm

a 0xD808 irq 10

Oct  1 19:12:55 Tower logger: /etc/rc.d/rc.inet1:  /sbin/dhcpcd -d -t 60 -h Towe

r eth0

Oct  1 19:12:55 Tower kernel: ata1: dev 0 ATA-7, max UDMA/133, 976773168 sectors

: LBA48

Oct  1 19:12:55 Tower kernel: ata1: dev 1 ATA-7, max UDMA/133, 976773168 sectors

: LBA48

Oct  1 19:12:55 Tower kernel: ata1: dev 0 configured for UDMA/133

Oct  1 19:12:55 Tower kernel: ata1: dev 1 configured for UDMA/133

Oct  1 19:12:55 Tower kernel: ATA: abnormal status 0x7F on port 0xE007

Oct  1 19:12:55 Tower kernel: ata2: disabling port

Oct  1 19:12:55 Tower kernel: scsi1 : ata_piix

Oct  1 19:12:55 Tower kernel: scsi2 : ata_piix

Oct  1 19:12:55 Tower kernel:  Vendor: ATA      Model: ST3500630AS      Rev:

3.AA

Oct  1 19:12:55 Tower kernel:  Type:  Direct-Access                      ANSI

SCSI revision: 05

Oct  1 19:12:55 Tower kernel:  Vendor: ATA      Model: ST3500630AS      Rev:

3.AA

Oct  1 19:12:55 Tower kernel:  Type:  Direct-Access                      ANSI

SCSI revision: 05

Oct  1 19:12:55 Tower kernel: Attached scsi disk sdb at scsi1, channel 0, id 0,

lun 0

Oct  1 19:12:55 Tower kernel: Attached scsi disk sdc at scsi1, channel 0, id 1,

lun 0

Oct  1 19:12:55 Tower kernel: SCSI device sdb: 976773168 512-byte hdwr sectors (

500108 MB)

Oct  1 19:12:55 Tower kernel:  sdb: sdb1

Oct  1 19:12:55 Tower kernel: SCSI device sdc: 976773168 512-byte hdwr sectors (

500108 MB)

Oct  1 19:12:55 Tower kernel:  sdc: sdc1

Oct  1 19:12:57 Tower kernel: eth0: network connection up using port A

Oct  1 19:12:57 Tower kernel:    speed:          1000

Oct  1 19:12:57 Tower kernel:    autonegotiation: yes

Oct  1 19:12:57 Tower kernel:    duplex mode:    full

Oct  1 19:12:57 Tower kernel:    flowctrl:        symmetric

Oct  1 19:12:57 Tower kernel:    role:            slave

Oct  1 19:12:57 Tower kernel:    irq moderation:  disabled

Oct  1 19:12:57 Tower kernel:    scatter-gather:  enabled

Oct  1 19:12:57 Tower kernel:    tx-checksum:    enabled

Oct  1 19:12:57 Tower kernel:    rx-checksum:    enabled

Oct  1 19:12:57 Tower kernel:    rx-polling:      enabled

Oct  1 19:13:15 Tower logger: /etc/rc.d/rc.hotplug start (exiting script)

Oct  1 19:13:15 Tower emhttp[1006]: UnRaid Management Utility version 3.0-beta4

Oct  1 19:13:15 Tower emhttp[1006]: Copyright © 2005-2006, Lime Technology, LL

C

Oct  1 19:13:15 Tower emhttp[1006]: shcmd (1): rmmod md-mod >>/var/log/go 2>&1

Oct  1 19:13:15 Tower ifplugd(eth0)[1013]: ifplugd 0.28 initializing.

Oct  1 19:13:15 Tower ifplugd(eth0)[1013]: Using interface eth0/00:13:20:BE:0C:F

8 with driver <sk98lin> (version: 8.35.2.3 (02))

Oct  1 19:13:15 Tower ifplugd(eth0)[1013]: Using detection mode: SIOCETHTOOL

Oct  1 19:13:15 Tower ifplugd(eth0)[1013]: Initialization complete, link beat de

tected.

Oct  1 19:13:15 Tower emhttp[1006]: shcmd (2): modprobe md-mod super=/boot/confi

g/super.dat slots=8,16,8,32 >>/var/log/go 2>&1

Oct  1 19:13:16 Tower kernel: md: unraid driver 0.90.1

Oct  1 19:13:16 Tower kernel: md: sizeof(mdp_super_t) = 4096

Oct  1 19:13:16 Tower kernel: md: measuring xor speed

Oct  1 19:13:16 Tower kernel:    8regs    :  2878.400 MB/sec

Oct  1 19:13:16 Tower kernel:    32regs    :  1853.600 MB/sec

Oct  1 19:13:16 Tower kernel:    pIII_sse  :  4362.800 MB/sec

Oct  1 19:13:16 Tower kernel:    pII_mmx  :  2718.000 MB/sec

Oct  1 19:13:16 Tower kernel:    p5_mmx    :  2741.200 MB/sec

Oct  1 19:13:16 Tower kernel: md: using function: pIII_sse (4362.800 MB/sec)

Oct  1 19:13:16 Tower kernel: md: superblock -> /boot/config/super.dat

Oct  1 19:13:16 Tower kernel: md: slot 0 device -> sdb [8,16]

Oct  1 19:13:16 Tower kernel: md: slot 1 device -> sdc [8,32]

Oct  1 19:13:16 Tower kernel: md: slot 2 device -> ? [0,0]

Oct  1 19:13:16 Tower kernel: md: slot 3 device -> ? [0,0]

Oct  1 19:13:16 Tower kernel: md: slot 4 device -> ? [0,0]

Oct  1 19:13:16 Tower kernel: md: slot 5 device -> ? [0,0]

Oct  1 19:13:16 Tower kernel: md: slot 6 device -> ? [0,0]

Oct  1 19:13:16 Tower kernel: md: slot 7 device -> ? [0,0]

Oct  1 19:13:16 Tower kernel: md: slot 8 device -> ? [0,0]

Oct  1 19:13:16 Tower kernel: md: slot 9 device -> ? [0,0]

Oct  1 19:13:16 Tower kernel: md: slot 10 device -> ? [0,0]

Oct  1 19:13:16 Tower kernel: md: slot 11 device -> ? [0,0]

Oct  1 19:13:16 Tower ifplugd(eth0)[1013]: Executing '/etc/ifplugd/ifplugd.actio

n eth0 up'.

Oct  1 19:13:16 Tower kernel: md: reading superblock from /boot/config/super.dat

Oct  1 19:13:16 Tower kernel: md: superblock events: 8

Oct  1 19:13:16 Tower kernel: md: import sdb ST3500630AS      3QG02QV4 offset: 6

3 size: 488386552

Oct  1 19:13:16 Tower kernel: md0: wrong

Oct  1 19:13:16 Tower emhttp[1006]: Device inventory:

Oct  1 19:13:16 Tower emhttp[1006]: /dev/scsi/sdh1-1c0i0l0 (sdb1) SATA:ST3500630

AS/3QG02QV4

Oct  1 19:13:16 Tower emhttp[1006]: /dev/scsi/sdh1-1c0i1l0 (sdc1) SATA:ST3500630

AS/3QG02GPW

Oct  1 19:13:16 Tower kernel: md: import sdc ST3500630AS      3QG02GPW offset: 6

3 size: 488386552

Oct  1 19:13:16 Tower kernel: md1: wrong

Oct  1 19:13:16 Tower emhttp[1006]: shcmd (3): rmmod md-mod >>/var/log/go 2>&1

Oct  1 19:13:16 Tower kernel: md: unraid driver removed.

Oct  1 19:13:16 Tower emhttp[1006]: shcmd (4): modprobe md-mod super=/boot/confi

g/super.dat slots=8,32,8,16,0,0 >>/var/log/go 2>&1

Oct  1 19:13:16 Tower ifplugd(eth0)[1013]: Program executed successfully.

Oct  1 19:13:16 Tower kernel: md: unraid driver 0.90.1

Oct  1 19:13:16 Tower kernel: md: sizeof(mdp_super_t) = 4096

Oct  1 19:13:16 Tower kernel: md: measuring xor speed

Oct  1 19:13:16 Tower kernel:    8regs    :  2856.800 MB/sec

Oct  1 19:13:16 Tower kernel:    32regs    :  1855.200 MB/sec

Oct  1 19:13:16 Tower kernel:    pIII_sse  :  4362.800 MB/sec

Oct  1 19:13:16 Tower kernel:    pII_mmx  :  2717.600 MB/sec

Oct  1 19:13:16 Tower kernel:    p5_mmx    :  2741.600 MB/sec

Oct  1 19:13:16 Tower kernel: md: using function: pIII_sse (4362.800 MB/sec)

Oct  1 19:13:16 Tower kernel: md: superblock -> /boot/config/super.dat

Oct  1 19:13:16 Tower kernel: md: slot 0 device -> sdc [8,32]

Oct  1 19:13:16 Tower kernel: md: slot 1 device -> sdb [8,16]

Oct  1 19:13:16 Tower kernel: md: slot 2 device -> ? [0,0]

Oct  1 19:13:16 Tower kernel: md: slot 3 device -> ? [0,0]

Oct  1 19:13:16 Tower kernel: md: slot 4 device -> ? [0,0]

Oct  1 19:13:16 Tower kernel: md: slot 5 device -> ? [0,0]

Oct  1 19:13:16 Tower kernel: md: slot 6 device -> ? [0,0]

Oct  1 19:13:16 Tower kernel: md: slot 7 device -> ? [0,0]

Oct  1 19:13:16 Tower kernel: md: slot 8 device -> ? [0,0]

Oct  1 19:13:16 Tower kernel: md: slot 9 device -> ? [0,0]

Oct  1 19:13:16 Tower kernel: md: slot 10 device -> ? [0,0]

Oct  1 19:13:16 Tower kernel: md: slot 11 device -> ? [0,0]

Oct  1 19:13:16 Tower kernel: md: reading superblock from /boot/config/super.dat

Oct  1 19:13:16 Tower kernel: md: superblock events: 8

Oct  1 19:13:16 Tower kernel: md: import sdc ST3500630AS      3QG02GPW offset: 6

3 size: 488386552

Oct  1 19:13:16 Tower kernel: md: import sdb ST3500630AS      3QG02QV4 offset: 6

3 size: 488386552

Oct  1 19:13:16 Tower emhttp[1006]: shcmd (5): killall -w smbd nmbd

Oct  1 19:13:16 Tower nmbd[1000]: [2006/10/01 19:13:16, 0] nmbd/nmbd.c:terminate

(56)

Oct  1 19:13:16 Tower nmbd[1000]:  Got SIGTERM: going down...

Oct  1 19:13:18 Tower emhttp[1006]: shcmd (6): /usr/sbin/nmbd -D

Oct  1 19:13:18 Tower emhttp[1006]: shcmd (7): /usr/sbin/smbd -D

Oct  1 19:13:18 Tower emhttp[1058]: driver cmd: start STOPPED

Oct  1 19:13:18 Tower kernel: mdcmd (2): start

Oct  1 19:13:18 Tower kernel: md: reading superblock from /boot/config/super.dat

Oct  1 19:13:18 Tower kernel: md: superblock events: 8

Oct  1 19:13:18 Tower kernel: md: import sdc ST3500630AS      3QG02GPW offset: 6

3 size: 488386552

Oct  1 19:13:18 Tower kernel: md: import sdb ST3500630AS      3QG02QV4 offset: 6

3 size: 488386552

Oct  1 19:13:18 Tower kernel: unraid: allocated 2186kB for md0

Oct  1 19:13:18 Tower kernel: md1: running, size: 488386552 blocks

Oct  1 19:13:18 Tower emhttp[1058]: driver cmd: check

Oct  1 19:13:18 Tower kernel: mdcmd (4): check

Oct  1 19:13:18 Tower kernel: md: recovery thread got woken up ...

Oct  1 19:13:18 Tower kernel: md: recovery thread checking parity...

Oct  1 19:13:18 Tower kernel: md: writing superblock to /boot/config/super.dat

Oct  1 19:13:18 Tower emhttp[1063]: shcmd (8): mount -t reiserfs -o noatime,nodi

ratime /dev/md1 /mnt/disk1

Oct  1 19:13:18 Tower kernel: md: using 256k window, over a total of 488386552 b

locks.

Oct  1 19:13:18 Tower kernel: reiserfs: found format "3.6" with standard journal

Oct  1 19:13:41 Tower kernel: reiserfs: checking transaction log (device md(9,1)

) ...

Oct  1 19:13:41 Tower kernel: for (md(9,1))

Oct  1 19:13:42 Tower kernel: reiserfs: replayed 3 transactions in 1 seconds

Oct  1 19:13:42 Tower kernel: md(9,1):Using r5 hash to sort names

Oct  1 19:13:42 Tower emhttp[1063]: remount: /dev/md1

Oct  1 19:13:42 Tower kernel: md(9,1):can't shrink filesystem on-line

Oct  1 19:13:42 Tower emhttp[1058]: shcmd (8): killall -w smbd nmbd

Oct  1 19:13:42 Tower nmbd[1054]: [2006/10/01 19:13:42, 0] nmbd/nmbd.c:terminate

(56)

Oct  1 19:13:42 Tower nmbd[1054]:  Got SIGTERM: going down...

Oct  1 19:13:44 Tower emhttp[1058]: shcmd (9): /usr/sbin/nmbd -D

Oct  1 19:13:44 Tower emhttp[1058]: shcmd (10): /usr/sbin/smbd -D

root@Tower:~#

 

==============================================================

 

BTW I have not plugged in a keboard or a mouse in the unraid server, as I don't have a screen connected to it....

Link to comment

I started copying the remaining dvds to the tower. Transfer speed hits a max of 10mB/sec on a Gigabit switch... should't it be faster?

I went to the maintenance page and I noticed that parity check is under way, with an estimated finish of 807,7 minutes, at a speed of 9.320 KB/sec.

Same problem as other reported? Slow parity check? I am only trying to fill up a 500 GB drive, 85 GB free....

Link to comment

You are right, parity speed is now ~56.000 with half an hour left to run. Shouldn't my transfer speed be much higher than 16 mB/sec?

 

Sustained "sequential" write to an unRAID share theoretical maximum transfer rate is going to be 1/2 the maximum transfer rate of the target disk.  For example, the raw transfer rate of the typical 7200 rpm hard drive is around 60 MB/sec on the outer cylinders, dropping close to 30 MB/sec on the inner cylinders.  The best you can write to this drive via unRAID share would be 30 MB/sec on the outer cylinders & 15 MB/sec on the inner cylinders.  [This is because each write is really a read-modify-write in order to keep parity updated.  That is, each write is really read followed by a write.]

 

The current Actual transfer rate to an unRAID share varies between around 50-80% of maximum.  This is due to several factors:

a) driver write-throttling (to permit glitch-free read back)

b) file system layout - all the blocks of a "sequential" file are not necessarily completely sequential on disk

c) other system activity

 

Hence your value of 16 MB/sec is reasonable.

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.