syslog part 2:

Apr 23 08:40:02 unraid kernel: io scheduler noop registered (default)
Apr 23 08:40:02 unraid kernel: io scheduler anticipatory registered
Apr 23 08:40:02 unraid kernel: io scheduler deadline registered
Apr 23 08:40:02 unraid kernel: io scheduler cfq registered
Apr 23 08:40:02 unraid kernel: Boot video device is 0000:00:02.0
Apr 23 08:40:02 unraid kernel: PCI: Setting latency timer of device 0000:00:1c.0 to 64
Apr 23 08:40:02 unraid kernel: assign_interrupt_mode Found MSI capability
Apr 23 08:40:02 unraid kernel: Allocate Port Service[0000:00:1c.0:pcie00]
Apr 23 08:40:02 unraid kernel: Allocate Port Service[0000:00:1c.0:pcie02]
Apr 23 08:40:02 unraid kernel: input: Power Button (FF) as /devices/virtual/input/input0
Apr 23 08:40:02 unraid kernel: ACPI: Power Button (FF) [PWRF]
Apr 23 08:40:02 unraid kernel: input: Power Button (CM) as /devices/virtual/input/input1
Apr 23 08:40:02 unraid kernel: ACPI: Power Button (CM) [PWRB]
Apr 23 08:40:02 unraid kernel: ACPI: Processor [CPU0] (supports 2 throttling states)
Apr 23 08:40:02 unraid kernel: Real Time Clock Driver v1.12ac
Apr 23 08:40:02 unraid kernel: intel_rng: FWH not detected
Apr 23 08:40:02 unraid kernel: Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds).
Apr 23 08:40:02 unraid kernel: Hangcheck: Using get_cycles().
Apr 23 08:40:02 unraid kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 1 ports, IRQ sharing disabled
Apr 23 08:40:02 unraid kernel: floppy0: no floppy controllers found
Apr 23 08:40:02 unraid kernel: loop: module loaded
Apr 23 08:40:02 unraid kernel: Driver 'sd' needs updating - please use bus_type methods
Apr 23 08:40:02 unraid kernel: ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
Apr 23 08:40:02 unraid kernel: USB Universal Host Controller Interface driver v3.0
Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 17
Apr 23 08:40:02 unraid kernel: PCI: Setting latency timer of device 0000:00:1d.0 to 64
Apr 23 08:40:02 unraid kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
Apr 23 08:40:02 unraid kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
Apr 23 08:40:02 unraid kernel: uhci_hcd 0000:00:1d.0: irq 17, io base 0x0000b000
Apr 23 08:40:02 unraid kernel: usb usb1: configuration #1 chosen from 1 choice
Apr 23 08:40:02 unraid kernel: hub 1-0:1.0: USB hub found
Apr 23 08:40:02 unraid kernel: hub 1-0:1.0: 2 ports detected
Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt 0000:00:1d.1[b] -> GSI 19 (level, low) -> IRQ 18
Apr 23 08:40:02 unraid kernel: PCI: Setting latency timer of device 0000:00:1d.1 to 64
Apr 23 08:40:02 unraid kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
Apr 23 08:40:02 unraid kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
Apr 23 08:40:02 unraid kernel: uhci_hcd 0000:00:1d.1: irq 18, io base 0x0000b400
Apr 23 08:40:02 unraid kernel: usb usb2: configuration #1 chosen from 1 choice
Apr 23 08:40:02 unraid kernel: hub 2-0:1.0: USB hub found
Apr 23 08:40:02 unraid kernel: hub 2-0:1.0: 2 ports detected
Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 19
Apr 23 08:40:02 unraid kernel: PCI: Setting latency timer of device 0000:00:1d.2 to 64
Apr 23 08:40:02 unraid kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
Apr 23 08:40:02 unraid kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
Apr 23 08:40:02 unraid kernel: uhci_hcd 0000:00:1d.2: irq 19, io base 0x0000b800
Apr 23 08:40:02 unraid kernel: usb usb3: configuration #1 chosen from 1 choice
Apr 23 08:40:02 unraid kernel: hub 3-0:1.0: USB hub found
Apr 23 08:40:02 unraid kernel: hub 3-0:1.0: 2 ports detected
Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 16
Apr 23 08:40:02 unraid kernel: PCI: Setting latency timer of device 0000:00:1d.3 to 64
Apr 23 08:40:02 unraid kernel: uhci_hcd 0000:00:1d.3: UHCI Host Controller
Apr 23 08:40:02 unraid kernel: uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
Apr 23 08:40:02 unraid kernel: uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000bc00
Apr 23 08:40:02 unraid kernel: usb usb4: configuration #1 chosen from 1 choice
Apr 23 08:40:02 unraid kernel: hub 4-0:1.0: USB hub found
Apr 23 08:40:02 unraid kernel: hub 4-0:1.0: 2 ports detected
Apr 23 08:40:02 unraid kernel: Initializing USB Mass Storage driver...
Apr 23 08:40:02 unraid kernel: usb 4-1: new full speed USB device using uhci_hcd and address 2
Apr 23 08:40:02 unraid kernel: usb 4-1: configuration #1 chosen from 1 choice
Apr 23 08:40:02 unraid kernel: scsi0 : SCSI emulation for USB Mass Storage devices
Apr 23 08:40:02 unraid kernel: usbcore: registered new interface driver usb-storage
Apr 23 08:40:02 unraid kernel: USB Mass Storage support registered.
Apr 23 08:40:02 unraid kernel: usb-storage: device found at 2
Apr 23 08:40:02 unraid kernel: usb-storage: waiting for device to settle before scanning
Apr 23 08:40:02 unraid kernel: PNP: No PS/2 controller found. Probing ports directly.
Apr 23 08:40:02 unraid kernel: Failed to disable AUX port, but continuing anyway... Is this a SiS?
Apr 23 08:40:02 unraid kernel: If AUX port is really absent please use the 'i8042.noaux' option.
Apr 23 08:40:02 unraid kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Apr 23 08:40:02 unraid kernel: mice: PS/2 mouse device common for all mice
Apr 23 08:40:02 unraid kernel: usbcore: registered new interface driver usbhid
Apr 23 08:40:02 unraid kernel: drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
Apr 23 08:40:02 unraid kernel: TCP cubic registered
Apr 23 08:40:02 unraid kernel: NET: Registered protocol family 1
Apr 23 08:40:02 unraid kernel: NET: Registered protocol family 17
Apr 23 08:40:02 unraid kernel: RPC: Registered udp transport module.
Apr 23 08:40:02 unraid kernel: RPC: Registered tcp transport module.
Apr 23 08:40:02 unraid kernel: Using IPI Shortcut mode
Apr 23 08:40:02 unraid kernel: Freeing unused kernel memory: 176k freed
Apr 23 08:40:02 unraid kernel: Intel(R) PRO/1000 Network Driver - version 7.6.15.4-NAPI
Apr 23 08:40:02 unraid kernel: Copyright (c) 1999-2008 Intel Corporation.
Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Apr 23 08:40:02 unraid kernel: PCI: Setting latency timer of device 0000:01:00.0 to 64
Apr 23 08:40:02 unraid kernel: e1000: 0000:01:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1) 00:15:17:51:7d:fa
Apr 23 08:40:02 unraid kernel: e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
Apr 23 08:40:02 unraid kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Apr 23 08:40:02 unraid kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Apr 23 08:40:02 unraid kernel: ICH7: IDE controller (0x8086:0x27df rev 0x01) at  PCI slot 0000:00:1f.1
Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 19
Apr 23 08:40:02 unraid kernel: ICH7: not 100%% native mode: will probe irqs later
Apr 23 08:40:02 unraid kernel:     ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:pio
Apr 23 08:40:02 unraid kernel:     ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pioApr 23 08:40:02 unraid kernel: Probing IDE interface ide0...
Apr 23 08:40:02 unraid kernel: libata version 3.00 loaded.
Apr 23 08:40:02 unraid kernel: hda: MAXTOR STM3500630A, ATA DISK drive
Apr 23 08:40:02 unraid kernel: hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
Apr 23 08:40:02 unraid kernel: hda: UDMA/100 mode selected
Apr 23 08:40:02 unraid kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Apr 23 08:40:02 unraid kernel: Probing IDE interface ide1...
Apr 23 08:40:02 unraid kernel: PDC20269: IDE controller (0x105a:0x4d69 rev 0x02) at  PCI slot 0000:02:00.0
Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 20 (level, low) -> IRQ 20
Apr 23 08:40:02 unraid kernel: PDC20269: PLL input clock is 16725 kHz
Apr 23 08:40:02 unraid kernel: PDC20269: 100%% native mode on irq 20
Apr 23 08:40:02 unraid kernel:     ide2: BM-DMA at 0x9000-0x9007, BIOS settings: hde:pio, hdf:pio
Apr 23 08:40:02 unraid kernel:     ide3: BM-DMA at 0x9008-0x900f, BIOS settings: hdg:pio, hdh:pio
Apr 23 08:40:02 unraid kernel: Probing IDE interface ide2...
Apr 23 08:40:02 unraid kernel: hdf: Maxtor 6Y250P0, ATA DISK drive
Apr 23 08:40:02 unraid kernel: hdf: host max PIO4 wanted PIO255(auto-tune) selected PIO4
Apr 23 08:40:02 unraid kernel: hdf: UDMA/133 mode selected
Apr 23 08:40:02 unraid kernel: ide2 at 0x8000-0x8007,0x8402 on irq 20
Apr 23 08:40:02 unraid kernel: Probing IDE interface ide3...
Apr 23 08:40:02 unraid kernel: hdh: Maxtor 6B300R0, ATA DISK drive
Apr 23 08:40:02 unraid kernel: hdh: host max PIO4 wanted PIO255(auto-tune) selected PIO4
Apr 23 08:40:02 unraid kernel: hdh: UDMA/133 mode selected
Apr 23 08:40:02 unraid kernel: ide3 at 0x8800-0x8807,0x8c02 on irq 20
Apr 23 08:40:02 unraid kernel: PDC20269: IDE controller (0x105a:0x4d69 rev 0x02) at  PCI slot 0000:02:01.0
Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 19 (level, low) -> IRQ 18
Apr 23 08:40:02 unraid kernel: PDC20269: PLL input clock is 16710 kHz
Apr 23 08:40:02 unraid kernel: PDC20269: 100%% native mode on irq 18
Apr 23 08:40:02 unraid kernel:     ide4: BM-DMA at 0xa400-0xa407, BIOS settings: hdi:pio, hdj:pio
Apr 23 08:40:02 unraid kernel:     ide5: BM-DMA at 0xa408-0xa40f, BIOS settings: hdk:pio, hdl:pio
Apr 23 08:40:02 unraid kernel: Probing IDE interface ide4...
Apr 23 08:40:02 unraid kernel: scsi 0:0:0:0: Direct-Access     Sony     Storage Media    0100 PQ: 0 ANSI: 0 CCS
Apr 23 08:40:02 unraid kernel: sd 0:0:0:0: [sda] 1014784 512-byte hardware sectors (520 MB)
Apr 23 08:40:02 unraid kernel: sd 0:0:0:0: [sda] Write Protect is off
Apr 23 08:40:02 unraid kernel: sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
Apr 23 08:40:02 unraid kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Apr 23 08:40:02 unraid kernel: sd 0:0:0:0: [sda] 1014784 512-byte hardware sectors (520 MB)
Apr 23 08:40:02 unraid kernel: sd 0:0:0:0: [sda] Write Protect is off
Apr 23 08:40:02 unraid kernel: sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
Apr 23 08:40:02 unraid kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Apr 23 08:40:02 unraid kernel:  sda: sda1
Apr 23 08:40:02 unraid kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk
Apr 23 08:40:02 unraid kernel: usb-storage: device scan complete
Apr 23 08:40:02 unraid kernel: Probing IDE interface ide5...
Apr 23 08:40:02 unraid kernel: hdk: Maxtor 7Y250P0, ATA DISK drive
Apr 23 08:40:02 unraid kernel: hdk: host max PIO4 wanted PIO255(auto-tune) selected PIO4
Apr 23 08:40:02 unraid kernel: hdk: UDMA/133 mode selected
Apr 23 08:40:02 unraid kernel: ide5 at 0x9c00-0x9c07,0xa002 on irq 18
Apr 23 08:40:02 unraid kernel: ata_piix 0000:00:1f.2: version 2.12
Apr 23 08:40:02 unraid kernel: ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt 0000:00:1f.2[b] -> GSI 19 (level, low) -> IRQ 18
Apr 23 08:40:02 unraid kernel: PCI: Setting latency timer of device 0000:00:1f.2 to 64
Apr 23 08:40:02 unraid kernel: scsi1 : ata_piix
Apr 23 08:40:02 unraid kernel: scsi2 : ata_piix
Apr 23 08:40:02 unraid kernel: ata1: SATA max UDMA/133 cmd 0xd400 ctl 0xd800 bmdma 0xe400 irq 18
Apr 23 08:40:02 unraid kernel: ata2: SATA max UDMA/133 cmd 0xdc00 ctl 0xe000 bmdma 0xe408 irq 18
Apr 23 08:40:02 unraid kernel: hda: max request size: 512KiB
Apr 23 08:40:02 unraid kernel: hda: Host Protected Area detected.
Apr 23 08:40:02 unraid kernel: ^Icurrent capacity is 976771055 sectors (500106 MB)
Apr 23 08:40:02 unraid kernel: ^Inative  capacity is 976773168 sectors (500107 MB)
Apr 23 08:40:02 unraid kernel: hda: Host Protected Area disabled.
Apr 23 08:40:02 unraid kernel: hda: 976773168 sectors (500107 MB) w/16384KiB Cache, CHS=60801/255/63
Apr 23 08:40:02 unraid kernel: hda: cache flushes supported
Apr 23 08:40:02 unraid kernel:  hda:<6>ata1.00: HPA detected: current 976771055, native 976773168
Apr 23 08:40:02 unraid kernel: ata1.00: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7
Apr 23 08:40:02 unraid kernel: ata1.00: 976771055 sectors, multi 16: LBA48 NCQ (depth 0/32)
Apr 23 08:40:02 unraid kernel: ata1.01: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7
Apr 23 08:40:02 unraid kernel: ata1.01: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
Apr 23 08:40:02 unraid kernel:  hda1
Apr 23 08:40:02 unraid kernel: hdf: max request size: 512KiB
Apr 23 08:40:02 unraid kernel: hdf: 490234752 sectors (251000 MB) w/7936KiB Cache, CHS=30515/255/63
Apr 23 08:40:02 unraid kernel: hdf: cache flushes supported
Apr 23 08:40:02 unraid kernel:  hdf: hdf1
Apr 23 08:40:02 unraid kernel: ata1.00: configured for UDMA/133
Apr 23 08:40:02 unraid kernel: hdh: max request size: 512KiB
Apr 23 08:40:02 unraid kernel: hdh: 586114704 sectors (300090 MB) w/16384KiB Cache, CHS=36483/255/63
Apr 23 08:40:02 unraid kernel: hdh: cache flushes supported
Apr 23 08:40:02 unraid kernel:  hdh:<6>ata1.01: configured for UDMA/133
Apr 23 08:40:02 unraid kernel:  hdh1
Apr 23 08:40:02 unraid kernel: hdk: max request size: 512KiB
Apr 23 08:40:02 unraid kernel: hdk: 490234752 sectors (251000 MB) w/7936KiB Cache, CHS=30515/255/63
Apr 23 08:40:02 unraid kernel: hdk: cache flushes supported

syslog final part:[code]Apr 23 08:40:02 unraid kernel:  hdk: hdk1
Apr 23 08:40:02 unraid kernel: ata2.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133
Apr 23 08:40:02 unraid kernel: ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
Apr 23 08:40:02 unraid kernel: ata2.00: configured for UDMA/133
Apr 23 08:40:02 unraid kernel: scsi 1:0:0:0: Direct-Access     ATA      SAMSUNG HD501LJ  CR10 PQ: 0 ANSI: 5
Apr 23 08:40:02 unraid kernel: sd 1:0:0:0: [sdb] 976771055 512-byte hardware sectors (500107 MB)
Apr 23 08:40:02 unraid kernel: sd 1:0:0:0: [sdb] Write Protect is off
Apr 23 08:40:02 unraid kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Apr 23 08:40:02 unraid kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 23 08:40:02 unraid kernel: sd 1:0:0:0: [sdb] 976771055 512-byte hardware sectors (500107 MB)
Apr 23 08:40:02 unraid kernel: sd 1:0:0:0: [sdb] Write Protect is off
Apr 23 08:40:02 unraid kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Apr 23 08:40:02 unraid kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 23 08:40:02 unraid kernel:  sdb: sdb1
Apr 23 08:40:02 unraid kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Apr 23 08:40:02 unraid kernel: scsi 1:0:1:0: Direct-Access     ATA      SAMSUNG HD501LJ  CR10 PQ: 0 ANSI: 5
Apr 23 08:40:02 unraid kernel: sd 1:0:1:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
Apr 23 08:40:02 unraid kernel: sd 1:0:1:0: [sdc] Write Protect is off
Apr 23 08:40:02 unraid kernel: sd 1:0:1:0: [sdc] Mode Sense: 00 3a 00 00
Apr 23 08:40:02 unraid kernel: sd 1:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 23 08:40:02 unraid kernel: sd 1:0:1:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
Apr 23 08:40:02 unraid kernel: sd 1:0:1:0: [sdc] Write Protect is off
Apr 23 08:40:02 unraid kernel: sd 1:0:1:0: [sdc] Mode Sense: 00 3a 00 00
Apr 23 08:40:02 unraid kernel: sd 1:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 23 08:40:02 unraid kernel:  sdc: sdc1
Apr 23 08:40:02 unraid kernel: sd 1:0:1:0: [sdc] Attached SCSI disk
Apr 23 08:40:02 unraid kernel: scsi 2:0:0:0: Direct-Access     ATA      ST3500630AS      3.AA PQ: 0 ANSI: 5
Apr 23 08:40:02 unraid kernel: sd 2:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB)
Apr 23 08:40:02 unraid kernel: sd 2:0:0:0: [sdd] Write Protect is off
Apr 23 08:40:02 unraid kernel: sd 2:0:0:0: [sdd] Mode Sense: 00 3a 00 00
Apr 23 08:40:02 unraid kernel: sd 2:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 23 08:40:02 unraid kernel: sd 2:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB)
Apr 23 08:40:02 unraid kernel: sd 2:0:0:0: [sdd] Write Protect is off
Apr 23 08:40:02 unraid kernel: sd 2:0:0:0: [sdd] Mode Sense: 00 3a 00 00
Apr 23 08:40:02 unraid kernel: sd 2:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 23 08:40:02 unraid kernel:  sdd: sdd1
Apr 23 08:40:02 unraid kernel: sd 2:0:0:0: [sdd] Attached SCSI disk
Apr 23 08:40:04 unraid logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig lo 127.0.0.1
Apr 23 08:40:04 unraid logger: /etc/rc.d/rc.inet1:  /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
Apr 23 08:40:04 unraid logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig eth0 192.168.100.201 broadcast 192.168.100.255 netmask 255.255.255.0
Apr 23 08:40:04 unraid logger: /etc/rc.d/rc.inet1:  /sbin/route add default gw 192.168.100.1 metric 1
Apr 23 08:40:04 unraid ifplugd(eth0)[1452]: ifplugd 0.28 initializing.
Apr 23 08:40:04 unraid ifplugd(eth0)[1452]: Using interface eth0/00:15:17:51:7D:FA with driver <e1000> (version: 7.6.15.4-NAPI)
Apr 23 08:40:04 unraid ifplugd(eth0)[1452]: Using detection mode: SIOCETHTOOL
Apr 23 08:40:04 unraid ifplugd(eth0)[1452]: Initialization complete, link beat not detected.
Apr 23 08:40:04 unraid kernel: fuse init (API version 7.9)
Apr 23 08:40:05 unraid emhttp: unRAID System Management Utility version 4.3-beta6
Apr 23 08:40:05 unraid emhttp: Copyright (C) 2005-2008, Lime Technology, LLC
Apr 23 08:40:05 unraid emhttp: Pro key detected, registered to: Mike Morbeto
Apr 23 08:40:05 unraid emhttp: Device inventory:
Apr 23 08:40:05 unraid emhttp: pci-0000:00:1f.2-scsi-1:0:0:0 (sdd) ata-ST3500630AS_9QG41ZM2
Apr 23 08:40:05 unraid emhttp: pci-0000:00:1f.2-scsi-0:0:1:0 (sdc) ata-SAMSUNG_HD501LJ_S0MUJ1DP301846
Apr 23 08:40:05 unraid emhttp: pci-0000:00:1f.2-scsi-0:0:0:0 (sdb) ata-SAMSUNG_HD501LJ_S0MUJ1DP301847
Apr 23 08:40:05 unraid emhttp: pci-0000:00:1f.1-ide-0:0 (hda) ata-MAXTOR_STM3500630A_5QG06KKG
Apr 23 08:40:05 unraid emhttp: pci-0000:02:01.0-ide-0:0 (hdk) ata-Maxtor_7Y250P0_Y62B2DJE
Apr 23 08:40:05 unraid emhttp: pci-0000:02:00.0-ide-0:1 (hdf) ata-Maxtor_6Y250P0_Y62HYJZE
Apr 23 08:40:05 unraid emhttp: pci-0000:02:00.0-ide-1:1 (hdh) ata-Maxtor_6B300R0_B60EQK0H
Apr 23 08:40:05 unraid emhttp: shcmd (1): rmmod md-mod >>/var/log/go 2>&1
Apr 23 08:40:05 unraid emhttp: shcmd: shcmd (1): exit status: 1
Apr 23 08:40:05 unraid emhttp: shcmd (2): modprobe md-mod super=/boot/config/super.dat slots=8,32,3,0,8,16,33,64,34,64,8,48,57,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 >>/var/log/go 2>&1
Apr 23 08:40:05 unraid kernel: md: unRAID driver 0.94.0 installed
Apr 23 08:40:05 unraid kernel: md: xor using function: pIII_sse (1211.600 MB/sec)
Apr 23 08:40:05 unraid emhttp: shcmd (3): /usr/sbin/hdparm -S242 /dev/sdc >/dev/null
Apr 23 08:40:05 unraid emhttp: shcmd (4): /usr/sbin/hdparm -S242 /dev/hda >/dev/null
Apr 23 08:40:05 unraid emhttp: shcmd (5): /usr/sbin/hdparm -S242 /dev/sdb >/dev/null
Apr 23 08:40:05 unraid emhttp: shcmd (6): /usr/sbin/hdparm -S242 /dev/hdf >/dev/null
Apr 23 08:40:06 unraid emhttp: shcmd (7): /usr/sbin/hdparm -S242 /dev/hdh >/dev/null
Apr 23 08:40:06 unraid emhttp: shcmd (: /usr/sbin/hdparm -S242 /dev/sdd >/dev/null
Apr 23 08:40:06 unraid emhttp: shcmd (9): /usr/sbin/hdparm -S242 /dev/hdk >/dev/null
Apr 23 08:40:06 unraid emhttp: shcmd (10): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root
Apr 23 08:40:06 unraid emhttp: shcmd (11): echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root
Apr 23 08:40:06 unraid emhttp: shcmd (12): echo '40 3 * * * /usr/local/sbin/mover | logger 2>&1' >>/var/spool/cron/crontabs/root
Apr 23 08:40:06 unraid emhttp: shcmd (13): crontab /var/spool/cron/crontabs/root
Apr 23 08:40:06 unraid emhttp: shcmd (14): killall -w smbd nmbd
Apr 23 08:40:07 unraid kernel: e1000: eth0: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Apr 23 08:40:07 unraid emhttp: shcmd (15): /usr/sbin/nmbd -D
Apr 23 08:40:07 unraid emhttp: shcmd (16): /usr/sbin/smbd -D
Apr 23 08:40:07 unraid kernel: mdcmd (3): start
Apr 23 08:40:07 unraid kernel: unraid: allocated 15222kB
Apr 23 08:40:07 unraid kernel: md1: running, size: 488386552 blocks
Apr 23 08:40:07 unraid kernel: md2: running, size: 488385496 blocks
Apr 23 08:40:07 unraid kernel: md3: running, size: 245117344 blocks
Apr 23 08:40:07 unraid kernel: md4: running, size: 293057320 blocks
Apr 23 08:40:07 unraid kernel: md5: running, size: 488386552 blocks
Apr 23 08:40:07 unraid kernel: md6: running, size: 245117344 blocks
Apr 23 08:40:07 unraid ifplugd(eth0)[1452]: Link beat detected.
Apr 23 08:40:07 unraid kernel: mdcmd (5): check
Apr 23 08:40:07 unraid kernel: md: recovery thread got woken up ...
Apr 23 08:40:07 unraid emhttp: shcmd (17): udevsettle
Apr 23 08:40:07 unraid emhttp: shcmd (18): mkdir -m 700 /mnt/disk1
Apr 23 08:40:07 unraid kernel: md: recovery thread has nothing to resync
Apr 23 08:40:07 unraid emhttp: shcmd (18): mkdir -m 700 /mnt/disk2
Apr 23 08:40:08 unraid emhttp: shcmd (19): mount -t reiserfs -o noatime,nodiratime /dev/md1 /mnt/disk1  >/dev/null 2>&1
Apr 23 08:40:08 unraid emhttp: shcmd (18): mkdir -m 700 /mnt/disk3
Apr 23 08:40:08 unraid emhttp: shcmd (19): mount -t reiserfs -o noatime,nodiratime /dev/md2 /mnt/disk2  >/dev/null 2>&1
Apr 23 08:40:08 unraid emhttp: shcmd (18): mkdir -m 700 /mnt/disk4
Apr 23 08:40:08 unraid emhttp: shcmd (19): mount -t reiserfs -o noatime,nodiratime /dev/md3 /mnt/disk3  >/dev/null 2>&1
Apr 23 08:40:08 unraid kernel: ReiserFS: md1: found reiserfs format "3.6" with standard journal
Apr 23 08:40:08 unraid kernel: ReiserFS: md1: using ordered data mode
Apr 23 08:40:08 unraid emhttp: shcmd (18): mkdir -m 700 /mnt/disk5
Apr 23 08:40:08 unraid emhttp: shcmd (19): mount -t reiserfs -o noatime,nodiratime /dev/md4 /mnt/disk4  >/dev/null 2>&1
Apr 23 08:40:08 unraid kernel: ReiserFS: md1: journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Apr 23 08:40:08 unraid kernel: ReiserFS: md1: checking transaction log (md1)
Apr 23 08:40:08 unraid emhttp: shcmd (18): mkdir -m 700 /mnt/disk6
Apr 23 08:40:08 unraid emhttp: shcmd (19): mount -t reiserfs -o noatime,nodiratime /dev/md5 /mnt/disk5  >/dev/null 2>&1
Apr 23 08:40:08 unraid kernel: ReiserFS: md2: found reiserfs format "3.6" with standard journal
Apr 23 08:40:08 unraid kernel: ReiserFS: md2: using ordered data mode
Apr 23 08:40:08 unraid kernel: ReiserFS: md3: found reiserfs format "3.6" with standard journal
Apr 23 08:40:08 unraid kernel: ReiserFS: md3: using ordered data mode
Apr 23 08:40:08 unraid emhttp: shcmd (19): mount -t reiserfs -o noatime,nodiratime /dev/md6 /mnt/disk6  >/dev/null 2>&1
Apr 23 08:40:08 unraid kernel: ReiserFS: md2: journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Apr 23 08:40:08 unraid kernel: ReiserFS: md2: checking transaction log (md2)
Apr 23 08:40:08 unraid kernel: ReiserFS: md3: journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Apr 23 08:40:08 unraid kernel: ReiserFS: md3: checking transaction log (md3)
Apr 23 08:40:08 unraid kernel: ReiserFS: md4: found reiserfs format "3.6" with standard journal
Apr 23 08:40:08 unraid kernel: ReiserFS: md4: using ordered data mode
Apr 23 08:40:08 unraid kernel: ReiserFS: md5: found reiserfs format "3.6" with standard journal
Apr 23 08:40:08 unraid kernel: ReiserFS: md5: using ordered data mode
Apr 23 08:40:08 unraid kernel: ReiserFS: md6: found reiserfs format "3.6" with standard journal
Apr 23 08:40:08 unraid kernel: ReiserFS: md6: using ordered data mode
Apr 23 08:40:08 unraid kernel: ReiserFS: md4: journal params: device md4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Apr 23 08:40:08 unraid kernel: ReiserFS: md4: checking transaction log (md4)
Apr 23 08:40:08 unraid kernel: ReiserFS: md5: journal params: device md5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Apr 23 08:40:08 unraid kernel: ReiserFS: md5: checking transaction log (md5)
Apr 23 08:40:08 unraid kernel: ReiserFS: md2: Using r5 hash to sort names
Apr 23 08:40:08 unraid kernel: ReiserFS: md3: Using r5 hash to sort names
Apr 23 08:40:08 unraid kernel: ReiserFS: md6: journal params: device md6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Apr 23 08:40:08 unraid kernel: ReiserFS: md6: checking transaction log (md6)
Apr 23 08:40:08 unraid kernel: ReiserFS: md1: Using r5 hash to sort names
Apr 23 08:40:08 unraid kernel: ReiserFS: md6: Using r5 hash to sort names
Apr 23 08:40:08 unraid kernel: ReiserFS: md4: Using r5 hash to sort names
Apr 23 08:40:08 unraid kernel: ReiserFS: md5: Using r5 hash to sort names
Apr 23 08:40:08 unraid kernel: can't shrink filesystem on-line
Apr 23 08:40:08 unraid last message repeated 5 times
Apr 23 08:40:08 unraid emhttp: shcmd (18): mkdir -m 700 /mnt/user
Apr 23 08:40:08 unraid emhttp: shcmd (19): /usr/local/sbin/shfs /mnt/user
Apr 23 08:40:09 unraid ifplugd(eth0)[1452]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Apr 23 08:40:09 unraid ifplugd(eth0)[1452]: Program executed successfully.
Apr 23 08:40:10 unraid shfs: duplicate object: /mnt/disk2/.DS_Store
Apr 23 08:40:10 unraid shfs: duplicate object: /mnt/disk3/.DS_Store
Apr 23 08:40:10 unraid shfs: duplicate object: /mnt/disk4/ehthumbs_vista.db
Apr 23 08:40:10 unraid shfs: duplicate object: /mnt/disk4/.DS_Store
Apr 23 08:40:10 unraid shfs: duplicate object: /mnt/disk5/.DS_Store
Apr 23 08:40:10 unraid shfs: duplicate object: /mnt/disk6/.DS_Store
Apr 23 08:40:10 unraid emhttp: shcmd (20): killall -HUP smbd
Apr 23 08:40:42 unraid in.telnetd[1606]: connect from 192.168.100.203 (192.168.100.203)
Apr 23 08:40:46 unraid login[1607]: ROOT LOGIN  on `pts/0' from `192.168.100.203'
Apr 23 09:48:41 unraid in.telnetd[1657]: connect from 192.168.100.203 (192.168.100.203)
Apr 23 09:48:49 unraid login[1658]: ROOT LOGIN  on `pts/0' from `192.168.100.203'
Apr 23 09:59:54 unraid in.telnetd[1676]: connect from 192.168.100.203 (192.168.100.203)
Apr 23 10:00:01 unraid login[1677]: ROOT LOGIN  on `pts/1' from `192.168.100.203'
Apr 23 10:06:12 unraid in.telnetd[1691]: connect from 192.168.100.203 (192.168.100.203)
Apr 23 10:06:50 unraid login[1692]: ROOT LOGIN  on `pts/1' from `192.168.100.203'

[/code]

Okay, ran the reiserfsck --rebuild-tree last night.

 

Looks like it fixed the problems.  Changes were made though, so I would check out the videos and folders mentioned, they could be corrupted, probably not, but possible.

 

The syslog looks fine, essentially identical to the previous, except that the connection is at gigabit speed.

 

Have you tried a different network card?  Also, what is the length of the cable that runs between floors, and what category of cable is it, and does it have the pre-made connectors?  Does it possibly run along side of power lines at some point?  Just reaching here, looking for suspects...

 

Hi Rob-

 

First I used the Gigabyte mobo's built in gig NIC. Worked fine for about a year. Then recently I started noticing these issues. I updated to 4.3 beta 6 from 4.2.whatever. I was having the issue before this however; hoped the upgrade might fix it. Thought it could be a problem on my main downloads/file transfer PC and not the unraid, but I also started getting drop offs where the shares would disappear during a file transfer on my Mac or another PC.

 

So then physical issues made sense. So I moved the unraid (and later even the PC) to a spot right next to the router and connected with fresh new cables. Still getting the problem. It happens even when in a telnet session. I can't even move my files off the unraid onto another storage location since it craps out mid-way through the file transfer.

 

Also, now that I'm using 4.3 I noticed something else. In the web control, under shares, there are a bunch listed that correspond to various folders on my unraid. I do not recall setting these up myself at all. I have one folder that's name is common across multiple drives (Movies, Shows, DVDs) on disk1, disk2, etc... I was always able to access this as one large 2TB share (for read-only, at least) but with the limitations on user shares pre 4.3, I hardly ever used it that way. I would just navigate to disk1, disk2, etc.. directly. So I knew there was a "share" set up for the Movies, Shows, and DVDs folders but I never set these others up. Now there are ones entered (seemingly by themselves) in the web interface for other folders I may have on one or another disk in the array, such as Backups, CD Audio, Convert to DVD, Lost+Found, etc... All show "high-water" allocation method and export read/write mode, with no included or excluded disks indicated. I never set any of these up manually. Could that have anything to do with these issues, should I delete them (how?), or what else could I look at?

OK, we need to see a syslog that includes your network issues, because none so far have had any network problems showing.  Force several network dropouts under different conditions, then capture a syslog and attach it (you can attach files using the Additional Options... link).  Also type ifconfig at a console or in a telnet box, after these network issues, and show us the results.

 

As to the shares, that sounds normal.  The User Share system is regenerated each time you boot, and looks for both User Shares you have set up, as well as ones always created from the top level folders on the data disks.

 

Network is dropping all the time- I'm not sure what to do to get it to show up in the log. For instance, it has crapped out again on several  700MB downloads I've been trying to save to disk4 of the array. It was doing this right up to when I got the last log. I just figured I'd check ifconfig now to see, then try some more transfers (from unraid to local disk, from local disk to unraid, downloads to unraid, etc..) again as well.

 

Well, went in to do the ifconfig, and here is the result:

unraid login: root
Linux 2.6.24.4-unRAID.
root@unraid:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:15:17:51:7D:FA
          inet addr:192.168.100.201  Bcast:192.168.100.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2231005 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5767690 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:863162301 (823.1 MiB)  TX bytes:4108318780 (3.8 GiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:40 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3080 (3.0 KiB)  TX bytes:3080 (3.0 KiB)

root@unraid:~#

Now, I know you said to create some new errors then check this, and interestingly enough, WHILE checking it, I got this (again:)

I'll check the log again now but these seem to not report there? If I restart the telnet session, or remap the network drive or My Network Place again it will reappear fine. Very frustrating.

 

Just tried to copy a file from E (local disk) to W(disk 4 mounted network drive), and got this error, which is a new one. BTW, I have tried both using the unraid from XP with mount network drive (assigning a letter to each one in the array), both logging in as my usual PC user name (or unchanged) and with the "sign in as a different user" option using root. I've also tried adding a network place and accessing the unraid drives that way too. I deleted my shares that were set to reconnect at login and rebuilt them just in case. I also tried the direct unc path (for instance, telling a program to download files to \\unraid\disk4\temp instead of via the mounted drive letter. None have fixed this. Out of curiosity, what is the preferred method, mapping (as root?) or network places?

 

and this is the most common error I get (also get this one when it craps out in the middle of a download) This time it just happened when I tried to double-click Disk4 on the My Network Places (\\UNRAID\Disk4) item:

and here is the latest syslog (attached)

By the way, in the ifconfig (forgive my ignorance), what does Bcast:192.168.100.255  refer to? I have network settings in the web config page set at:

IP: 192.168.100.201

Netmask: 255.255.255.0

Gateway: 192.168.100.1

 

Hmmm....  Your syslog shows no problems at all!!!  Neither does your ifconfig report.  So I can say that it appears there is nothing wrong with unRAID or its networking, since if it had lost the network, that would have appeared in the syslog.  We need to tackle this from the other end.

 

New idea:  I've discovered, and a few other uTorrent users have reported a similar problem, that my D-Link DI604 router resets itself every 20 minutes, when I try to setup a machine to share Open Office, AutoPatcher, Knoppix etc files using uTorrent.  When it resets, the connections are restored quickly in about 30 seconds, but my external IP has been changed, which wreaks havoc with trying to help others using a VNC tool.  As soon as I shutdown uTorrent, the router stays up with same IP for months at a time.  Is it possible that you are running a torrent server or some internet software that is rebooting or resetting the router?

 

By the way, in the ifconfig (forgive my ignorance), what does Bcast:192.168.100.255  refer to?

 

That is a normal broadcast address, simply means a station can send a packet to that IP and all of the stations on the 192.168.100.* subnet will receive it.

 

Out of curiosity, what is the preferred method, mapping (as root?) or network places?

 

Your choice, whatever is most convenient for you, or required by your applications.

 

By the way, in the ifconfig (forgive my ignorance), what does Bcast:192.168.100.255  refer to? I have network settings in the web config page set at:

IP: 192.168.100.201

Netmask: 255.255.255.0

Gateway: 192.168.100.1

 

See here: http://www.thelug.org/orig/papers/tl-ip-addressing.html

 

Basically, as RobJ said, the broadcast address is listened to by all machines on a subnet.

 

Joe L.

I am using a torrent program, uTorrent specifically. It is those downloads that keep crapping out the most when saving to the unraid. When I change the download path to a local disk (or even a remote disk on another machine with file sharing on and mounted on the PC running uT), they work fine and the downloads don't stop. When I have the download path as the unraid, it craps out like this. Of course it's not all uTorrent stuff however- simply doing telnet or file transfer in Windows Explorer or on a Mac with the unraid is also resulting in these errors I posted pics of. In fact, when that last batch of errors popped up and I did the screen grabs attached, I had shut down uTorrent prior to that as it kept getting errors anyway. I don't leave it up and running often, and it isn't on now nor was it when I got those errors earlier. However, I'm not ruling out the router since what you are seeing in the logs shows no errors. Let me ask- is there any log on the unraid that can show specific file activity? In otherwords, the copy, move or write commands the machines on the network are requesting, and the unraid response?

 

Do I need to go into my router and set up the UDP ports shown in the unraid web config? I don't recall having to do that before so I assumed it was okay.

 

I do recall updating my router firmware a month or two ago. It's a Belkin Pre-N but was acting up on Xbox Live with restricted NAT, and I read on DSLReports.com (among others) of success flashing it with specific Linksys firmware for the WRT54GX that was proved to work on the Belkin hardware as well, and (other than this unraid stuff), it has been very reliable since. Linksys firmware 1.02.15 is what I'm running. Are there router logs I might be able to access that might help diagnose this if we think it could be router-related?

By the way, not that it should make a difference, but I also run Anonymizer and PeerGuardian2 on that PC running uTorrent since the very though of open ports to the outside world is not my favorite idea. Not that I'm downloading anything that I don't own or is otherwise copyrighted, of course ;-)  The router updates DnyDNS.org with my IP so I can use a DNS to access my PCs from afar with VNC, and that is working fine. In fact all the cut and paste today posted is from machines I've gotten too from work via VNC.

From the department of longshots now:

First, whenever I have wierd network dropouts, the first thing I check is duplex settings. A switch/router and client with different or auto settings can be a pain.

1.Try setting the speed/duples settings manually on both and replicate your transfer test.

2. Set your IP addresses manually and replace router with switch or crossover networkcable.

 

Another thing came to mind, is your dhcp-renew timer very low ??. If yes raise it to a few days and try again.

/Rene

 

Well, I've been thinking about trying a new router anyway like to upgrade my WAP to final pre-N spec model and one w/ GigE network ports. So mabe that's this weekend's project, and a new router will magically remove the gremlin. Keep the ideas coming though, I'll check any and all suggested.

What is causing your issues may not be the same as what caused mine, but I thought I would mention the 2 things that helped me pin my network problems down.  They may or may not help you.  One is to log into your router, and check the router logs.  You may have to turn logging on.  I would find that they had only recent history, and I was able to determine by working back, exactly when the router had last re-started.  I checked often, and identified a pattern.  The other thing that helped was to check the uTorrent tab that shows network activity.  I don't remember what I did, but there is a way to show graphically the upload and download totals, and that was when I verified that every 20 minutes, all network activity would go to zero for a bit, and then slowly climb back up and plateau until the next 20 minute mark, and plunge to zero again.

 

What is causing your issues may not be the same as what caused mine, but I thought I would mention the 2 things that helped me pin my network problems down.  They may or may not help you.  One is to log into your router, and check the router logs.  You may have to turn logging on.  I would find that they had only recent history, and I was able to determine by working back, exactly when the router had last re-started.  I checked often, and identified a pattern.  The other thing that helped was to check the uTorrent tab that shows network activity.  I don't remember what I did, but there is a way to show graphically the upload and download totals, and that was when I verified that every 20 minutes, all network activity would go to zero for a bit, and then slowly climb back up and plateau until the next 20 minute mark, and plunge to zero again.

 

So uTorrent was/is actually rebooting your router somehow? What kind of router & firmware? I'll check my logs.

Technically, I can't say yet that uTorrent is rebooting my router, but that activity associated with uTorrent uploading is coincident with periodic router resets.

 

I am using an old D-Link DI-624 revC router with firmware v2.76, from 2006 but apparently the latest.

 

I"M A DUMBASS! I"M A DUMBASS! I"M A DUMBASS! I"M A DUMBASS! I"M A DUMBASS!

Okay, figured it out today. I went up to my office/spare room at home where I had an older PC, and my son asked me to bring up his game on it, so I touched the mouse and woke it up. Low and behold, there is a Windows message- conflicting IP! Dammit, I forgot about the PC and when I resurrected it for occasional use by my son, for some dumb reason I assigned it a static IP, just in case I ever needed to VNC into it. Yep, gave it the same one as the unraid. Case closed. Sorry. Set it for DHCP (or could have just picked another IP), and now the unraid isn't dropping off the network in the middle of transfers. Wow, amazing. Doh.

 

Still, I wonder why the loss/conflict that caused it to choke isn't in the logs?

Added this discussion to the networking FAQ (link back only), here.  Feel free to edit.  There are other good networking diagnostic threads that should also be added to this FAQ entry.