NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Fri Mar 29, 2024 7:55 am

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 15 posts ] 
Author Message
PostPosted: Thu Feb 25, 2010 4:51 pm 
Offline

Joined: Wed Oct 28, 2009 2:03 pm
Posts: 10
Hi All,

I am testing a NASLite-M2 x64 v1.62 server before it going live, I have a 3ware 9500s-4lp Hardware raid card.
3 x 500gb drive setup as raid5 1 logical volume 936gb. After setting up an formatting the volume and putting some data
on it I thought I would test the Check raid alert 2x700hz beeps followed by 5x300hz beeps by pulling the data and power lead on one of the disks. The degradation is detected and displayed in server log:-

Feb 25 19:16:46 [4] 3w-9xxx: scsi0: AEN: ERROR (0x04:0x0002): Degraded unit:unit=0, port=1

But no alarm.
My pc speaker is working fine as when naslite boots and shuts down I here the beeps.
Full server log below.

Any Ideas Guys??

Many Thanks




Feb 25 19:11:00 [3] klogd started: BusyBox v1.12.1 (2009-11-19 21:21:30 UTC)
Feb 25 19:11:00 [3] Linux version 2.6.30.3-64-CORE3 (root@DevBox) (gcc version 4.3.3 (GCC) ) #1 SMP Thu Jan 28 13:28:52 EST 2010
Feb 25 19:11:00 [2] Command line: rw root=/dev/ram0 initrd=NASLite.02 quiet BOOT_IMAGE=NASLite.01
Feb 25 19:11:00 [2] KERNEL supported cpus:
Feb 25 19:11:00 [2] Intel GenuineIntel
Feb 25 19:11:00 [2] AMD AuthenticAMD
Feb 25 19:11:00 [2] Centaur CentaurHauls
Feb 25 19:11:00 [2] BIOS-provided physical RAM map:
Feb 25 19:11:00 [2] BIOS-e820: 0000000000000000 - 000000000009e000 (usable)
Feb 25 19:11:00 [2] BIOS-e820: 000000000009e000 - 00000000000a0000 (reserved)
Feb 25 19:11:00 [2] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Feb 25 19:11:00 [2] BIOS-e820: 0000000000100000 - 00000000bffef800 (usable)
Feb 25 19:11:00 [2] BIOS-e820: 00000000bffef800 - 00000000bfff0000 (reserved)
Feb 25 19:11:00 [2] BIOS-e820: 00000000bfff0000 - 00000000bfff3000 (ACPI NVS)
Feb 25 19:11:00 [2] BIOS-e820: 00000000bfff3000 - 00000000c0000000 (ACPI data)
Feb 25 19:11:00 [2] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
Feb 25 19:11:00 [2] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
Feb 25 19:11:00 [2] DMI 2.4 present.
Feb 25 19:11:00 [3] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
Feb 25 19:11:00 [1] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
Feb 25 19:11:00 [2] last_pfn = 0xbffef max_arch_pfn = 0x100000000
Feb 25 19:11:00 [2] init_memory_mapping: 0000000000000000-00000000bffef000
Feb 25 19:11:00 [1] 0000000000 - 00bfe00000 page 2M
Feb 25 19:11:00 [1] 00bfe00000 - 00bffef000 page 4k
Feb 25 19:11:00 [1] kernel direct mapping tables up to bffef000 @ 10000-15000
Feb 25 19:11:00 [2] RAMDISK: 7f744000 - 7fffec71
Feb 25 19:11:00 [4] ACPI: RSDP 00000000000f76a0 00014 (v00 IntelR)
Feb 25 19:11:00 [4] ACPI: RSDT 00000000bfff3040 00038 (v01 IntelR AWRDACPI 42302E31 AWRD 00000000)
Feb 25 19:11:00 [4] ACPI: FACP 00000000bfff30c0 00074 (v01 IntelR AWRDACPI 42302E31 AWRD 00000000)
Feb 25 19:11:00 [4] ACPI: DSDT 00000000bfff3180 04B50 (v01 INTELR AWRDACPI 00001000 MSFT 0100000E)
Feb 25 19:11:00 [4] ACPI: FACS 00000000bfff0000 00040
Feb 25 19:11:00 [4] ACPI: MCFG 00000000bfff7e40 0003C (v01 IntelR AWRDACPI 42302E31 AWRD 00000000)
Feb 25 19:11:00 [4] ACPI: APIC 00000000bfff7d40 00084 (v01 IntelR AWRDACPI 42302E31 AWRD 00000000)
Feb 25 19:11:00 [4] ACPI: SSDT 00000000bfff7ec0 0015C (v01 PmRef Cpu0Ist 00003000 INTL 20040311)
Feb 25 19:11:00 [4] ACPI: SSDT 00000000bfff8350 002F1 (v01 PmRef CpuPm 00003000 INTL 20040311)
Feb 25 19:11:00 [1] ACPI: Local APIC address 0xfee00000
Feb 25 19:11:00 [2] (7 early reservations) ==> bootmem [0000000000 - 00bffef000]
Feb 25 19:11:00 [2] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
Feb 25 19:11:00 [2] #1 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000]
Feb 25 19:11:00 [2] #2 [0000200000 - 000057dc8c] TEXT DATA BSS ==> [0000200000 - 000057dc8c]
Feb 25 19:11:00 [2] #3 [007f744000 - 007fffec71] RAMDISK ==> [007f744000 - 007fffec71]
Feb 25 19:11:00 [2] #4 [000009e000 - 0000100000] BIOS reserved ==> [000009e000 - 0000100000]
Feb 25 19:11:00 [2] #5 [000057e000 - 000057e08a] BRK ==> [000057e000 - 000057e08a]
Feb 25 19:11:00 [2] #6 [0000010000 - 0000013000] PGTABLE ==> [0000010000 - 0000013000]
Feb 25 19:11:00 [2] found SMP MP-table at [ffff8800000f37d0] f37d0
Feb 25 19:11:00 [1] [ffffe20000000000-ffffe200029fffff] PMD -> [ffff880001200000-ffff880003bfffff] on node 0
Feb 25 19:11:00 [4] Zone PFN ranges:
Feb 25 19:11:00 [4] DMA 0x00000010 -> 0x00001000
Feb 25 19:11:00 [4] DMA32 0x00001000 -> 0x00100000
Feb 25 19:11:00 [4] Normal 0x00100000 -> 0x00100000
Feb 25 19:11:00 [4] Movable zone start PFN for each node
Feb 25 19:11:00 [4] early_node_map[2] active PFN ranges
Feb 25 19:11:00 [4] 0: 0x00000010 -> 0x0000009e
Feb 25 19:11:00 [4] 0: 0x00000100 -> 0x000bffef
Feb 25 19:11:00 [1] On node 0 totalpages: 786301
Feb 25 19:11:00 [1] DMA zone: 56 pages used for memmap
Feb 25 19:11:00 [1] DMA zone: 997 pages reserved
Feb 25 19:11:00 [1] DMA zone: 2929 pages, LIFO batch:0
Feb 25 19:11:00 [1] DMA32 zone: 10696 pages used for memmap
Feb 25 19:11:00 [1] DMA32 zone: 771623 pages, LIFO batch:31
Feb 25 19:11:00 [2] ACPI: PM-Timer IO Port: 0x408
Feb 25 19:11:00 [1] ACPI: Local APIC address 0xfee00000
Feb 25 19:11:00 [2] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Feb 25 19:11:00 [2] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Feb 25 19:11:00 [2] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
Feb 25 19:11:00 [2] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
Feb 25 19:11:00 [2] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Feb 25 19:11:00 [2] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Feb 25 19:11:00 [2] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Feb 25 19:11:00 [2] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Feb 25 19:11:00 [2] ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
Feb 25 19:11:00 [2] IOAPIC[0]: apic_id 4, version 0, address 0xfec00000, GSI 0-23
Feb 25 19:11:00 [2] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 25 19:11:00 [2] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 25 19:11:00 [1] ACPI: IRQ0 us
Feb 25 19:11:00 [2] ed by override.
Feb 25 19:11:00 [1] ACPI: IRQ2 used by override.
Feb 25 19:11:00 [1] ACPI: IRQ9 used by override.
Feb 25 19:11:00 [2] Using ACPI (MADT) for SMP configuration information
Feb 25 19:11:00 [2] SMP: Allowing 4 CPUs, 2 hotplug CPUs
Feb 25 19:11:00 [1] nr_irqs_gsi: 24
Feb 25 19:11:00 [2] Allocating PCI resources starting at c2000000 (gap: c0000000:20000000)
Feb 25 19:11:00 [2] NR_CPUS:4 nr_cpumask_bits:4 nr_cpu_ids:4 nr_node_ids:1
Feb 25 19:11:00 [2] PERCPU: Embedded 24 pages at ffff88000101c000, static data 68896 bytes
Feb 25 19:11:00 [4] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 774552
Feb 25 19:11:00 [3] Kernel command line: rw root=/dev/ram0 initrd=NASLite.02 quiet BOOT_IMAGE=NASLite.01
Feb 25 19:11:00 [2] Initializing CPU#0
Feb 25 19:11:00 [2] NR_IRQS:384
Feb 25 19:11:00 [4] PID hash table entries: 4096 (order: 12, 32768 bytes)
Feb 25 19:11:00 [4] Fast TSC calibration using PIT
Feb 25 19:11:00 [4] Detected 1861.874 MHz processor.
Feb 25 19:11:00 [4] Console: colour VGA+ 80x25
Feb 25 19:11:00 [2] console [tty0] enabled
Feb 25 19:11:00 [2] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Feb 25 19:11:00 [2] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Feb 25 19:11:00 [2] Checking aperture.
Feb 25 19:11:00 [2] No AGP bridge found
Feb 25 19:11:00 [2] Memory: 3082288k/3145660k available (2004k kernel code, 456k absent, 62232k reserved, 846k data, 324k init)
Feb 25 19:11:00 [2] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Feb 25 19:11:00 [2] Calibrating delay loop (skipped), value calculated using timer frequency 3723.74 BogoMIPS (lpj=7447496)
Feb 25 19:11:00 [4] Mount-cache hash table entries: 256
Feb 25 19:11:00 [2] CPU: L1 I cache: 32K, L1 D cache: 32K
Feb 25 19:11:00 [2] CPU: L2 cache: 2048K
Feb 25 19:11:00 [2] CPU: Physical Processor ID: 0
Feb 25 19:11:00 [2] CPU: Processor Core ID: 0
Feb 25 19:11:00 [2] using mwait in idle threads.
Feb 25 19:11:00 [2] Freeing SMP alternatives: 23k freed
Feb 25 19:11:00 [2] ACPI: Core revision 20090320
Feb 25 19:11:00 [2] Setting APIC routing to flat
Feb 25 19:11:00 [2] CPU0: Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz stepping 06
Feb 25 19:11:00 [2] Booting processor 1 APIC 0x1 ip 0x6000
Feb 25 19:11:00 [2] Initializing CPU#1
Feb 25 19:11:00 [2] Calibrating delay using timer specific routine 3724.29 BogoMIPS (lpj=7448596)
Feb 25 19:11:00 [2] CPU: L1 I cache: 32K, L1 D cache: 32K
Feb 25 19:11:00 [2] CPU: L2 cache: 2048K
Feb 25 19:11:00 [2] CPU: Physical Processor ID: 0
Feb 25 19:11:00 [2] CPU: Processor Core ID: 1
Feb 25 19:11:00 [2] CPU1: Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz stepping 06
Feb 25 19:11:00 [2] checking TSC synchronization [CPU#0 -> CPU#1]: passed.
Feb 25 19:11:00 [2] Brought up 2 CPUs
Feb 25 19:11:00 [2] Total of 2 processors activated (7448.04 BogoMIPS).
Feb 25 19:11:00 [2] net_namespace: 560 bytes
Feb 25 19:11:00 [2] NET: Registered protocol family 16
Feb 25 19:11:00 [2] ACPI: bus type pci registered
Feb 25 19:11:00 [2] PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory Controller Hub with MMCONFIG support.
Feb 25 19:11:00 [3] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
Feb 25 19:11:00 [3] PCI: MCFG area at e0000000 reserved in E820
Feb 25 19:11:00 [2] PCI: Using MMCONFIG at e0000000 - efffffff
Feb 25 19:11:00 [2] PCI: Using configuration type 1 for base access
Feb 25 19:11:00 [4] bio: create slab at 0
Feb 25 19:11:00 [1] ACPI: EC: Look up EC in DSDT
Feb 25 19:11:00 [2] ACPI: Interpreter enabled
Feb 25 19:11:00 [2] ACPI: (supports S0 S5)
Feb 25 19:11:00 [2] ACPI: Using IOAPIC for interrupt routing
Feb 25 19:11:00 [2] ACPI: No dock devices found.
Feb 25 19:11:00 [2] ACPI: PCI Root Bridge [PCI0] (0000:00)
Feb 25 19:11:00 [2] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Feb 25 19:11:00 [2] pci 0000:00:01.0: PME# disabled
Feb 25 19:11:00 [2] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Feb 25 19:11:00 [2] pci 0000:00:1c.0: PME# disabled
Feb 25 19:11:00 [1] pci 0000:00:1d.0: reg 20 io port: [0xff00-0xff1f]
Feb 25 19:11:00 [1] pci 0000:00:1d.1: reg 20 io port: [0xfe00-0xfe1f]
Feb 25 19:11:00 [1] pci 0000:00:1d.2: reg 20 io port: [0xfd00-0xfd1f]
Feb 25 19:11:00 [1] pci 0000:00:1d.3: reg 20 io port: [0xfc00-0xfc1f]
Feb 25 19:11:00 [1] pci 0000:00:1d.7: reg 10 32bit mmio: [0xfdfff000-0xfdfff3ff]
Feb 25 19:11:00 [2] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
Feb 25 19:11:00 [2] pci 0000:00:1d.7: PME# disabled
Feb 25 19:11:00 [1] pci 0000:00:1f.1: reg 10 io port: [0x00-0x07]
Feb 25 19:11:00 [1] pci 0000:00:1f.1: reg 14 io port: [0x00-0x03]
Feb 25 19:11:00 [1] pci 0000:00:1f.1: reg 18 io port: [0x00-0x07]
Feb 25 19:11:00 [1] pci 0000:00:1f.1: reg 1c io port: [0x00-0x03]
Feb 25 19:11:00 [1] pci 0000:00:1f.1: reg 20 io port: [0xf900-0xf90f]
Feb 25 19:11:00 [1] pci 0000:00:1f.2: reg 10 io port: [0xf800-0xf807]
Feb 25 19:11:00 [1] pci 0000:00:1f.2: reg 14 io port: [0xf700-0xf703]
Feb 25 19:11:00 [1] pci 0000:00:1f.2: reg 18 io port: [0xf600-0xf607]
Feb 25 19:11:00 [1] pci 0000:00:1f.2: reg 1c io port: [0xf500-0xf503]
Feb 25 19:11:00 [1] pci 0000:00:1f.2: reg 20 io port: [0xf400-0xf40f]
Feb 25 19:11:00 [1] pci 0000:00:1f.2: reg 24 32bit mmio: [0xfdffc000-0xfdffc3ff]
Feb 25 19:11:00 [2] pci 0000:00:1f.2: PME# supported from D3hot
Feb 25 19:11:00 [2] pci 0000:00:1f.2: PME# disabled
Feb 25 19:11:00 [1] pci 0000:00:1f.3: reg 20 io port: [0x500-0x51f]
Feb 25 19:11:00 [1] pci 0000:01:00.0: reg 10 64bit mmio: [0xd0000000-0xdfffffff]
Feb 25 19:11:00 [1] pci
Feb 25 19:11:00 [2] 0000:01:00.0: reg 18 64bit mmio: [0xfddf0000-0xfddfffff]
Feb 25 19:11:00 [1] pci 0000:01:00.0: reg 20 io port: [0xce00-0xceff]
Feb 25 19:11:00 [1] pci 0000:01:00.0: reg 30 32bit mmio: [0x000000-0x01ffff]
Feb 25 19:11:00 [1] pci 0000:01:00.0: supports D1 D2
Feb 25 19:11:00 [1] pci 0000:01:00.1: reg 10 64bit mmio: [0xfdde0000-0xfddeffff]
Feb 25 19:11:00 [1] pci 0000:01:00.1: supports D1 D2
Feb 25 19:11:00 [1] pci 0000:00:01.0: bridge io port: [0xc000-0xcfff]
Feb 25 19:11:00 [1] pci 0000:00:01.0: bridge 32bit mmio: [0xfdd00000-0xfddfffff]
Feb 25 19:11:00 [1] pci 0000:00:01.0: bridge 64bit mmio pref: [0xd0000000-0xdfffffff]
Feb 25 19:11:00 [1] pci 0000:02:00.0: reg 10 32bit mmio: [0xfdbe0000-0xfdbfffff]
Feb 25 19:11:00 [1] pci 0000:02:00.0: reg 14 32bit mmio: [0xfd400000-0xfd7fffff]
Feb 25 19:11:00 [1] pci 0000:02:00.0: reg 18 io port: [0xbf00-0xbf1f]
Feb 25 19:11:00 [2] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
Feb 25 19:11:00 [2] pci 0000:02:00.0: PME# disabled
Feb 25 19:11:00 [1] pci 0000:00:1c.0: bridge io port: [0xb000-0xbfff]
Feb 25 19:11:00 [1] pci 0000:00:1c.0: bridge 32bit mmio: [0xfd400000-0xfdbfffff]
Feb 25 19:11:00 [1] pci 0000:00:1c.0: bridge 64bit mmio pref: [0xfde00000-0xfdefffff]
Feb 25 19:11:00 [1] pci 0000:03:02.0: reg 10 32bit mmio: [0xfdca0000-0xfdcbffff]
Feb 25 19:11:00 [1] pci 0000:03:02.0: reg 14 32bit mmio: [0xfdcc0000-0xfdcdffff]
Feb 25 19:11:00 [1] pci 0000:03:02.0: reg 18 io port: [0xdf00-0xdf3f]
Feb 25 19:11:00 [1] pci 0000:03:02.0: reg 30 32bit mmio: [0x000000-0x01ffff]
Feb 25 19:11:00 [2] pci 0000:03:02.0: PME# supported from D0 D3hot D3cold
Feb 25 19:11:00 [2] pci 0000:03:02.0: PME# disabled
Feb 25 19:11:00 [1] pci 0000:03:03.0: reg 10 io port: [0xdc00-0xdcff]
Feb 25 19:11:00 [1] pci 0000:03:03.0: reg 14 64bit mmio: [0xfdcff000-0xfdcff0ff]
Feb 25 19:11:00 [1] pci 0000:03:03.0: reg 1c 64bit mmio: [0xfc800000-0xfcffffff]
Feb 25 19:11:00 [1] pci 0000:03:03.0: reg 30 32bit mmio: [0x000000-0x00ffff]
Feb 25 19:11:00 [1] pci 0000:03:03.0: supports D1 D2
Feb 25 19:11:00 [2] pci 0000:03:03.0: PME# supported from D0 D1 D2 D3hot
Feb 25 19:11:00 [2] pci 0000:03:03.0: PME# disabled
Feb 25 19:11:00 [2] pci 0000:00:1e.0: transparent bridge
Feb 25 19:11:00 [1] pci 0000:00:1e.0: bridge io port: [0xd000-0xdfff]
Feb 25 19:11:00 [1] pci 0000:00:1e.0: bridge 32bit mmio: [0xfdc00000-0xfdcfffff]
Feb 25 19:11:00 [1] pci 0000:00:1e.0: bridge 64bit mmio pref: [0xfc800000-0xfcffffff]
Feb 25 19:11:00 [1] pci_bus 0000:00: on NUMA node 0
Feb 25 19:11:00 [1] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Feb 25 19:11:00 [1] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT]
Feb 25 19:11:00 [1] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
Feb 25 19:11:00 [2] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 *10 11 12 14 15)
Feb 25 19:11:00 [2] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 10 11 *12 14 15)
Feb 25 19:11:00 [2] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 *7 9 10 11 12 14 15)
Feb 25 19:11:00 [2] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 11 12 14 *15)
Feb 25 19:11:00 [2] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 10 *11 12 14 15)
Feb 25 19:11:00 [2] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
Feb 25 19:11:00 [2] ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
Feb 25 19:11:00 [2] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 *5 7 9 10 11 12 14 15)
Feb 25 19:11:00 [2] PCI: Using ACPI for IRQ routing
Feb 25 19:11:00 [1]
Feb 25 19:11:00 [1] printing PIC contents
Feb 25 19:11:00 [1] . PIC IMR: ffff
Feb 25 19:11:00 [1] . PIC IRR: 1ca1
Feb 25 19:11:00 [1] . PIC ISR: 0000
Feb 25 19:11:00 [1] . PIC ELCR: 9ca0
Feb 25 19:11:00 [4]
Feb 25 19:11:00 [1] printing local APIC contents on CPU#0/0:
Feb 25 19:11:00 [2] . APIC ID: 00000000 (0)
Feb 25 19:11:00 [2] . APIC VERSION: 00050014
Feb 25 19:11:00 [1] . APIC TASKPRI: 00000000 (00)
Feb 25 19:11:00 [1] . APIC PROCPRI: 00000000
Feb 25 19:11:00 [1] . APIC LDR: 01000000
Feb 25 19:11:00 [1] . APIC DFR: ffffffff
Feb 25 19:11:00 [1] . APIC SPIV: 000001ff
Feb 25 19:11:00 [1] . APIC ISR field:
Feb 25 19:11:00 [1] 0123456789abcdef0123456789abcdef
Feb 25 19:11:00 [1] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [1] . APIC TMR field:
Feb 25 19:11:00 [1] 0123456789abcdef0123456789abcdef
Feb 25 19:11:00 [1] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [1] . APIC IRR field:
Feb 25 19:11:00 [1] 0123456789abcdef0123456789abcdef
Feb 25 19:11:00 [1] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 0000000000000000000000
Feb 25 19:11:00 [2] 0000000000
Feb 25 19:11:00 [1] . APIC ESR: 00000000
Feb 25 19:11:00 [1] . APIC ICR: 000008fb
Feb 25 19:11:00 [1] . APIC ICR2: 02000000
Feb 25 19:11:00 [1] . APIC LVTT: 000200ef
Feb 25 19:11:00 [1] . APIC LVTPC: 00010000
Feb 25 19:11:00 [1] . APIC LVT0: 00010700
Feb 25 19:11:00 [1] . APIC LVT1: 00000400
Feb 25 19:11:00 [1] . APIC LVTERR: 000000fe
Feb 25 19:11:00 [1] . APIC TMICT: 000103c8
Feb 25 19:11:00 [1] . APIC TMCCT: 0000eee8
Feb 25 19:11:00 [1] . APIC TDCR: 00000003
Feb 25 19:11:00 [4]
Feb 25 19:11:00 [4]
Feb 25 19:11:00 [1] printing local APIC contents on CPU#1/1:
Feb 25 19:11:00 [2] . APIC ID: 01000000 (1)
Feb 25 19:11:00 [2] . APIC VERSION: 00050014
Feb 25 19:11:00 [1] . APIC TASKPRI: 00000000 (00)
Feb 25 19:11:00 [1] . APIC PROCPRI: 00000000
Feb 25 19:11:00 [1] . APIC LDR: 02000000
Feb 25 19:11:00 [1] . APIC DFR: ffffffff
Feb 25 19:11:00 [1] . APIC SPIV: 000001ff
Feb 25 19:11:00 [1] . APIC ISR field:
Feb 25 19:11:00 [1] 0123456789abcdef0123456789abcdef
Feb 25 19:11:00 [1] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [1] . APIC TMR field:
Feb 25 19:11:00 [1] 0123456789abcdef0123456789abcdef
Feb 25 19:11:00 [1] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [1] . APIC IRR field:
Feb 25 19:11:00 [1] 0123456789abcdef0123456789abcdef
Feb 25 19:11:00 [1] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [4] 00000000000000000000000000000000
Feb 25 19:11:00 [1] . APIC ESR: 00000000
Feb 25 19:11:00 [1] . APIC ICR: 00000000
Feb 25 19:11:00 [1] . APIC ICR2: 00000000
Feb 25 19:11:00 [1] . APIC LVTT: 000200ef
Feb 25 19:11:00 [1] . APIC LVTPC: 00010000
Feb 25 19:11:00 [1] . APIC LVT0: 00010700
Feb 25 19:11:00 [1] . APIC LVT1: 00010400
Feb 25 19:11:00 [1] . APIC LVTERR: 000000fe
Feb 25 19:11:00 [1] . APIC TMICT: 000103c8
Feb 25 19:11:00 [1] . APIC TMCCT: 0000e2ff
Feb 25 19:11:00 [1] . APIC TDCR: 00000003
Feb 25 19:11:00 [4]
Feb 25 19:11:00 [1] number of MP IRQ sources: 15.
Feb 25 19:11:00 [1] number of IO-APIC #4 registers: 24.
Feb 25 19:11:00 [2] testing the IO APIC.
Feb 25 19:11:00 [4]
Feb 25 19:11:00 [1] IO APIC #4
Feb 25 19:11:00 [1] register #00: 00000000
Feb 25 19:11:00 [1] . : physical APIC id: 00
Feb 25 19:11:00 [1] . : Delivery Type: 0
Feb 25 19:11:00 [1] . : LTS : 0
Feb 25 19:11:00 [1] register #01: 00170020
Feb 25 19:11:00 [1] . : max redirection entries: 0017
Feb 25 19:11:00 [1] . : PRQ implemented: 0
Feb 25 19:11:00 [1] . : IO APIC version: 0020
Feb 25 19:11:00 [1] IRQ redirection table:
Feb 25 19:11:00 [1] NR Dst Mask Trig IRR Pol Stat Dmod Deli Vect:
Feb 25 19:11:00 [1] 00 000 1 0 0 0 0 0 0 00
Feb 25 19:11:00 [1] 01 003 0 0 0 0 0 1 1 31
Feb 25 19:11:00 [1] 02 003 0 0 0 0 0 1 1 30
Feb 25 19:11:00 [1] 03 003 0 0 0 0 0 1 1 33
Feb 25 19:11:00 [1] 04 003 0 0 0 0 0 1 1 34
Feb 25 19:11:00 [1] 05 003 0 0 0 0 0 1 1 35
Feb 25 19:11:00 [1] 06 003 0 0 0 0 0 1 1 36
Feb 25 19:11:00 [1] 07 003 0 0 0 0 0 1 1 37
Feb 25 19:11:00 [1] 08 003 0 0 0 0 0 1 1 38
Feb 25 19:11:00 [1] 09 003 0 1 0 0 0 1 1 39
Feb 25 19:11:00 [1] 0a 003 0 0 0 0 0 1 1 3A
Feb 25 19:11:00 [1] 0b 003 0 0 0 0 0 1 1 3B
Feb 25 19:11:00 [1] 0c 003 0 0 0 0 0 1 1 3C
Feb 25 19:11:00 [1] 0d 003 0 0 0 0 0 1 1 3D
Feb 25 19:11:00 [1] 0e 003 0 0 0 0 0 1 1 3E
Feb 25 19:11:00 [1] 0f 003 0 0 0 0 0 1 1 3F
Feb 25 19:11:00 [1] 10 000 1 0 0 0 0 0 0 00
Feb 25 19:11:00 [1] 11 000 1 0 0 0 0 0 0 00
Feb 25 19:11:00 [1] 12 000 1 0 0 0 0 0 0 00
Feb 25 19:11:00 [1] 13 000 1 0 0 0 0 0 0 00
Feb 25 19:11:00 [1] 14 000 1 0 0 0 0 0 0 00
Feb 25 19:11:00 [1] 15 000 1 0 0 0 0 0 0 00
Feb 25 19:11:00 [1] 16 000 1 0 0 0 0 0 0 00
Feb 25 19:11:00 [1] 17 000 1 0 0 0 0 0 0 00
Feb 25 19:11:00 [1] IRQ to pin mappings:
Feb 25 19:11:00 [1] IRQ0 -> 0:2
Feb 25 19:11:00 [1] IRQ1 -> 0:1
Feb 25 19:11:00 [1] IRQ3 -> 0:3
Feb 25 19:11:00 [1] IRQ4 -> 0:4
Feb 25 19:11:00 [1] IRQ5 -> 0:5
Feb 25 19:11:00 [1] IRQ6 -> 0:6
Feb 25 19:11:00 [1] IRQ7 -> 0:7
Feb 25 19:11:00 [1] IRQ8 -> 0:8
Feb 25 19:11:00 [1] IRQ9 -> 0:9
Feb 25 19:11:00 [1] IRQ10 -> 0:10
Feb 25 19:11:00 [1] IRQ11 -> 0:11
Feb 25 19:11:00 [1] IRQ12 -> 0:12
Feb 25 19:11:00 [1] IRQ13 -> 0:13
Feb 25 19:11:00 [1] IRQ14 -> 0:14
Feb 25 19:11:00 [1] IRQ15 -> 0:15
Feb 25 19:11:00 [2] done.
Feb 25 19:11:00 [2] pnp: PnP ACPI init
Feb 25 19:11:00 [2] ACPI: bus type pnp registered
Feb 25 19:11:00 [2] pnp: PnP ACPI: found 11 devices
Feb 25 19:11:00 [2] ACPI: ACPI bus type pnp unregistered
Feb 25 19:11:00 [2] system 00:01: ioport range 0x4d0-0x4d1 has been reserved
Feb 25 19:11:00 [2] system 00:01: ioport range 0x290-0x29f
Feb 25 19:11:00 [2] has been reserved
Feb 25 19:11:00 [2] system 00:01: ioport range 0x800-0x87f has been reserved
Feb 25 19:11:00 [2] system 00:01: ioport range 0x880-0x88f has been reserved
Feb 25 19:11:00 [2] system 00:07: ioport range 0x400-0x4bf has been reserved
Feb 25 19:11:00 [2] system 00:09: iomem range 0xe0000000-0xefffffff has been reserved
Feb 25 19:11:00 [2] system 00:0a: iomem range 0xda800-0xdbfff has been reserved
Feb 25 19:11:00 [2] system 00:0a: iomem range 0xf0000-0xf7fff could not be reserved
Feb 25 19:11:00 [2] system 00:0a: iomem range 0xf8000-0xfbfff could not be reserved
Feb 25 19:11:00 [2] system 00:0a: iomem range 0xfc000-0xfffff could not be reserved
Feb 25 19:11:00 [2] system 00:0a: iomem range 0xbfff0000-0xbfffffff could not be reserved
Feb 25 19:11:00 [2] system 00:0a: iomem range 0x0-0x9ffff could not be reserved
Feb 25 19:11:00 [2] system 00:0a: iomem range 0x100000-0xbffeffff could not be reserved
Feb 25 19:11:00 [2] system 00:0a: iomem range 0xfec00000-0xfec00fff has been reserved
Feb 25 19:11:00 [2] system 00:0a: iomem range 0xfed13000-0xfed1dfff has been reserved
Feb 25 19:11:00 [2] system 00:0a: iomem range 0xfed20000-0xfed8ffff has been reserved
Feb 25 19:11:00 [2] system 00:0a: iomem range 0xfee00000-0xfee00fff has been reserved
Feb 25 19:11:00 [2] system 00:0a: iomem range 0xffb00000-0xffb7ffff has been reserved
Feb 25 19:11:00 [2] system 00:0a: iomem range 0xfff00000-0xffffffff has been reserved
Feb 25 19:11:00 [2] system 00:0a: iomem range 0xe0000-0xeffff has been reserved
Feb 25 19:11:00 [2] pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
Feb 25 19:11:00 [2] pci 0000:00:01.0: IO window: 0xc000-0xcfff
Feb 25 19:11:00 [2] pci 0000:00:01.0: MEM window: 0xfdd00000-0xfddfffff
Feb 25 19:11:00 [2] pci 0000:00:01.0: PREFETCH window: 0x000000d0000000-0x000000dfffffff
Feb 25 19:11:00 [2] pci 0000:00:1c.0: PCI bridge, secondary bus 0000:02
Feb 25 19:11:00 [2] pci 0000:00:1c.0: IO window: 0xb000-0xbfff
Feb 25 19:11:00 [2] pci 0000:00:1c.0: MEM window: 0xfd400000-0xfdbfffff
Feb 25 19:11:00 [2] pci 0000:00:1c.0: PREFETCH window: 0x000000fde00000-0x000000fdefffff
Feb 25 19:11:00 [2] pci 0000:00:1e.0: PCI bridge, secondary bus 0000:03
Feb 25 19:11:00 [2] pci 0000:00:1e.0: IO window: 0xd000-0xdfff
Feb 25 19:11:00 [2] pci 0000:00:1e.0: MEM window: 0xfdc00000-0xfdcfffff
Feb 25 19:11:00 [2] pci 0000:00:1e.0: PREFETCH window: 0x000000fc800000-0x000000fcffffff
Feb 25 19:11:00 [2] pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Feb 25 19:11:00 [1] pci 0000:00:01.0: setting latency timer to 64
Feb 25 19:11:00 [2] pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Feb 25 19:11:00 [1] pci 0000:00:1c.0: setting latency timer to 64
Feb 25 19:11:00 [1] pci 0000:00:1e.0: setting latency timer to 64
Feb 25 19:11:00 [1] pci_bus 0000:00: resource 0 io: [0x00-0xffff]
Feb 25 19:11:00 [1] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffffffffffff]
Feb 25 19:11:00 [1] pci_bus 0000:01: resource 0 io: [0xc000-0xcfff]
Feb 25 19:11:00 [1] pci_bus 0000:01: resource 1 mem: [0xfdd00000-0xfddfffff]
Feb 25 19:11:00 [1] pci_bus 0000:01: resource 2 pref mem [0xd0000000-0xdfffffff]
Feb 25 19:11:00 [1] pci_bus 0000:02: resource 0 io: [0xb000-0xbfff]
Feb 25 19:11:00 [1] pci_bus 0000:02: resource 1 mem: [0xfd400000-0xfdbfffff]
Feb 25 19:11:00 [1] pci_bus 0000:02: resource 2 pref mem [0xfde00000-0xfdefffff]
Feb 25 19:11:00 [1] pci_bus 0000:03: resource 0 io: [0xd000-0xdfff]
Feb 25 19:11:00 [1] pci_bus 0000:03: resource 1 mem: [0xfdc00000-0xfdcfffff]
Feb 25 19:11:00 [1] pci_bus 0000:03: resource 2 pref mem [0xfc800000-0xfcffffff]
Feb 25 19:11:00 [1] pci_bus 0000:03: resource 3 io: [0x00-0xffff]
Feb 25 19:11:00 [1] pci_bus 0000:03: resource 4 mem: [0x000000-0xffffffffffffffff]
Feb 25 19:11:00 [2] NET: Registered protocol family 2
Feb 25 19:11:00 [2] IP route cache hash table entries: 131072 (order: 8, 1048576 bytes)
Feb 25 19:11:00 [2] TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
Feb 25 19:11:00 [2] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Feb 25 19:11:00 [2] TCP: Hash tables configured (established 262144 bind 65536)
Feb 25 19:11:00 [2] TCP reno registered
Feb 25 19:11:00 [2] NET: Registered protocol family 1
Feb 25 19:11:00 [2] Trying to unpack rootfs image as initramfs.
Feb 25 19:11:00 [2] rootfs image is not initramfs (junk in compressed archive); looks like an initrd
Feb 25 19:11:00 [2] Freeing initrd memory: 8939k freed
Feb 25 19:11:00 [2] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Feb 25 19:11:00 [2] msgmni has been set to 6038
Feb 25 19:11:00 [2] io scheduler noop registered (default)
Feb 25 19:11:00 [1] pci 0000:01:00.0: Boot video device
Feb 25 19:11:00 [1] pcieport-driver 0000:00:01.0: setting latency timer to 64
Feb 25 19:11:00 [1] pcieport-driver 0000:00:1c.0: setting latency timer to 64
Feb 25 19:11:00 [2] Linux agpgart interface v0.103
Feb 25 19:11:00 [2] brd: module loaded
Feb 25 19:11:00 [2] loop: module loaded
Feb 25 19:11:00 [2] PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
Feb 25 19:11:00 [4] PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Feb 25 19:11:00 [2] serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 25 19:11:00 [2] mice: PS/2 mouse device commo
Feb 25 19:11:00 [2] n for all mice
Feb 25 19:11:00 [2] cpuidle: using governor ladder
Feb 25 19:11:00 [2] TCP cubic registered
Feb 25 19:11:00 [2] RPC: Registered udp transport module.
Feb 25 19:11:00 [2] RPC: Registered tcp transport module.
Feb 25 19:11:00 [2] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
Feb 25 19:11:00 [3] RAMDISK: CORE3 root image found at block 0
Feb 25 19:11:00 [4] VFS: Mounted root (ext2 filesystem) on device 1:0.
Feb 25 19:11:00 [2] Freeing unused kernel memory: 324k freed
Feb 25 19:11:04 [4] floppy0: no floppy controllers found
Feb 25 19:11:05 [2] rtc_cmos 00:03: RTC can wake from S4
Feb 25 19:11:05 [2] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
Feb 25 19:11:05 [2] rtc0: alarms up to one month, 242 bytes nvram
Feb 25 19:11:06 [2] input: PC Speaker as /devices/platform/pcspkr/input/input1
Feb 25 19:11:06 [2] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
Feb 25 19:11:06 [2] ACPI: Power Button [PWRF]
Feb 25 19:11:06 [2] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3
Feb 25 19:11:06 [2] ACPI: Power Button [PWRB]
Feb 25 19:11:06 [2] processor ACPI_CPU:00: registered as cooling_device0
Feb 25 19:11:06 [4] ACPI: SSDT 00000000bfff82c0 00087 (v01 PmRef Cpu1Ist 00003000 INTL 20040311)
Feb 25 19:11:06 [2] processor ACPI_CPU:01: registered as cooling_device1
Feb 25 19:11:06 [2] thermal LNXTHERM:01: registered as thermal_zone0
Feb 25 19:11:06 [2] ACPI: Thermal Zone [THRM] (37 C)
Feb 25 19:11:06 [2] fan PNP0C0B:00: registered as cooling_device2
Feb 25 19:11:06 [2] ACPI: Fan [FAN] (on)
Feb 25 19:11:06 [2] e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.4-k4
Feb 25 19:11:06 [2] e1000e: Copyright (c) 1999-2008 Intel Corporation.
Feb 25 19:11:06 [2] e1000e 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Feb 25 19:11:06 [1] e1000e 0000:02:00.0: setting latency timer to 64
Feb 25 19:11:06 [5] 0000:02:00.0: 0000:02:00.0: Failed to initialize MSI interrupts. Falling back to legacy interrupts.
Feb 25 19:11:06 [2] 0000:02:00.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:16:ec:e4:ee:90
Feb 25 19:11:06 [2] 0000:02:00.0: eth0: Intel(R) PRO/1000 Network Connection
Feb 25 19:11:06 [2] 0000:02:00.0: eth0: MAC: 2, PHY: 2, PBA No: ffffff-0ff
Feb 25 19:11:06 [2] usbcore: registered new interface driver usbfs
Feb 25 19:11:06 [2] usbcore: registered new interface driver hub
Feb 25 19:11:06 [2] usbcore: registered new device driver usb
Feb 25 19:11:06 [2] uhci_hcd: USB Universal Host Controller Interface driver
Feb 25 19:11:06 [2] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
Feb 25 19:11:06 [1] uhci_hcd 0000:00:1d.0: setting latency timer to 64
Feb 25 19:11:06 [2] uhci_hcd 0000:00:1d.0: UHCI Host Controller
Feb 25 19:11:06 [2] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
Feb 25 19:11:06 [2] uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000ff00
Feb 25 19:11:06 [2] usb usb1: configuration #1 chosen from 1 choice
Feb 25 19:11:06 [2] hub 1-0:1.0: USB hub found
Feb 25 19:11:06 [2] hub 1-0:1.0: 2 ports detected
Feb 25 19:11:06 [2] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
Feb 25 19:11:06 [1] uhci_hcd 0000:00:1d.1: setting latency timer to 64
Feb 25 19:11:06 [2] uhci_hcd 0000:00:1d.1: UHCI Host Controller
Feb 25 19:11:06 [2] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
Feb 25 19:11:06 [2] uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000fe00
Feb 25 19:11:06 [2] usb usb2: configuration #1 chosen from 1 choice
Feb 25 19:11:06 [2] hub 2-0:1.0: USB hub found
Feb 25 19:11:06 [2] hub 2-0:1.0: 2 ports detected
Feb 25 19:11:06 [2] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
Feb 25 19:11:06 [1] uhci_hcd 0000:00:1d.2: setting latency timer to 64
Feb 25 19:11:06 [2] uhci_hcd 0000:00:1d.2: UHCI Host Controller
Feb 25 19:11:06 [2] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
Feb 25 19:11:06 [2] uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000fd00
Feb 25 19:11:06 [2] usb usb3: configuration #1 chosen from 1 choice
Feb 25 19:11:06 [2] hub 3-0:1.0: USB hub found
Feb 25 19:11:06 [2] hub 3-0:1.0: 2 ports detected
Feb 25 19:11:06 [2] uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 16 (level, low) -> IRQ 16
Feb 25 19:11:06 [1] uhci_hcd 0000:00:1d.3: setting latency timer to 64
Feb 25 19:11:06 [2] uhci_hcd 0000:00:1d.3: UHCI Host Controller
Feb 25 19:11:06 [2] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
Feb 25 19:11:06 [2] uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000fc00
Feb 25 19:11:06 [2] usb usb4: configuration #1 chosen from 1 choice
Feb 25 19:11:06 [2] hub 4-0:1.0: USB hub found
Feb 25 19:11:06 [2] hub 4-0:1.0: 2 ports detected
Feb 25 19:11:06 [2] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Feb 25 19:11:06 [4] Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after
Feb 25 19:11:06 [2] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
Feb 25 19:11:06 [1] ehci_hcd 0000:00:1d.7: setting latency timer to 64
Feb 25 19:11:06 [2] ehci_hcd 0000:00:1d.7: EHCI Host Controller
Feb 25 19:11:06 [2] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5
Feb 25 19:11:06 [1] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
Feb 25 19:11:06 [2] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfdfff000
Feb 25 19:11:06 [2] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
Feb 25 19:11:06 [2] usb usb5: configuration #1 chosen from 1 choice
Feb 25 19:11:06 [2] hub 5-0:1.0: USB hub found
Feb 25 19:11:06 [2] hub 5-0:1.0: 8 ports detected
Feb 25 19:11:06 [2] Intel(R) PRO/1000 Network Driver - version 7.3.21-k3-NAPI
Feb 25 19:11:06 [2] Copyright (c) 1999-2006 Intel Corporation.
Feb 25 19:11:06 [2] e1000 0000:03:02.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
Feb 25 19:11:06 [2] e1000: 0000:03:02.0: e1000_probe: (PCI:33MHz:32-bit) 00:1b:21:19:4d:0b
Feb 25 19:11:06 [2] e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
Feb 25 19:11:06 [3] SCSI subsystem initialized
Feb 25 19:11:06 [4] 3ware 9000 Storage Controller device driver for Linux v2.26.02.012.
Feb 25 19:11:06 [2] 3w-9xxx 0000:03:03.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
Feb 25 19:11:07 [2] usb 5-5: new high speed USB device using ehci_hcd and address 2
Feb 25 19:11:07 [2] usb 5-5: configuration #1 chosen from 1 choice
Feb 25 19:11:07 [2] usb 5-8: new high speed USB device using ehci_hcd and address 3
Feb 25 19:11:07 [2] usb 5-8: configuration #1 chosen from 1 choice
Feb 25 19:11:08 [4] 3w-9xxx: scsi0: AEN: INFO (0x04:0x0053): Battery capacity test is overdue:.
Feb 25 19:11:08 [2] scsi0 : 3ware 9000 Storage Controller
Feb 25 19:11:08 [4] 3w-9xxx: scsi0: Found a 3ware 9000 Storage Controller at 0xfdcff000, IRQ: 20.
Feb 25 19:11:08 [4] 3w-9xxx: scsi0: Firmware FE9X 2.08.00.009, BIOS BE9X 2.03.01.052, Ports: 4.
Feb 25 19:11:08 [3] scsi 0:0:0:0: Direct-Access AMCC 9500S-4LP DISK 2.08 PQ: 0 ANSI: 3
Feb 25 19:11:08 [2] Uniform Multi-Platform E-IDE driver
Feb 25 19:11:08 [2] piix 0000:00:1f.1: IDE controller (0x8086:0x27df rev 0x01)
Feb 25 19:11:08 [2] PIIX_IDE 0000:00:1f.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Feb 25 19:11:08 [2] piix 0000:00:1f.1: IDE port disabled
Feb 25 19:11:08 [2] piix 0000:00:1f.1: not 100% native mode: will probe irqs later
Feb 25 19:11:08 [2] ide0: BM-DMA at 0xf900-0xf907
Feb 25 19:11:08 [1] Probing IDE interface ide0.
Feb 25 19:11:09 [2] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Feb 25 19:11:09 [1] libata version 3.00 loaded.
Feb 25 19:11:09 [1] ata_piix 0000:00:1f.2: version 2.13
Feb 25 19:11:09 [2] ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
Feb 25 19:11:09 [2] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
Feb 25 19:11:09 [1] ata_piix 0000:00:1f.2: setting latency timer to 64
Feb 25 19:11:09 [2] scsi1 : ata_piix
Feb 25 19:11:09 [2] scsi2 : ata_piix
Feb 25 19:11:09 [2] ata1: SATA max UDMA/133 cmd 0xf800 ctl 0xf700 bmdma 0xf400 irq 19
Feb 25 19:11:09 [2] ata2: SATA max UDMA/133 cmd 0xf600 ctl 0xf500 bmdma 0xf408 irq 19
Feb 25 19:11:10 [2] Initializing USB Mass Storage driver.
Feb 25 19:11:10 [2] scsi3 : SCSI emulation for USB Mass Storage devices
Feb 25 19:11:10 [1] usb-storage: device found at 2
Feb 25 19:11:10 [1] usb-storage: waiting for device to settle before scanning
Feb 25 19:11:10 [2] scsi4 : SCSI emulation for USB Mass Storage devices
Feb 25 19:11:10 [1] usb-storage: device found at 3
Feb 25 19:11:10 [1] usb-storage: waiting for device to settle before scanning
Feb 25 19:11:10 [2] usbcore: registered new interface driver usb-storage
Feb 25 19:11:10 [2] USB Mass Storage support registered.
Feb 25 19:11:10 [4] Driver 'sd' needs updating - please use bus_type methods
Feb 25 19:11:10 [3] sd 0:0:0:0: [sda] 1953083392 512-byte hardware sectors: (999 GB/931 GiB)
Feb 25 19:11:10 [3] sd 0:0:0:0: [sda] Write Protect is off
Feb 25 19:11:10 [1] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
Feb 25 19:11:10 [3] sd 0:0:0:0: [sda] Write cache: enabled, read cache: disabled, doesn't support DPO or FUA
Feb 25 19:11:10 [2] sda:
Feb 25 19:11:11 [2] sda1
Feb 25 19:11:11 [3] sd 0:0:0:0: [sda] Attached SCSI disk
Feb 25 19:11:15 [3] scsi 3:0:0:0: Direct-Access SanDisk U3 Titanium 3.27 PQ: 0 ANSI: 2
Feb 25 19:11:15 [3] scsi 4:0:0:0: Direct-Access Generic USB SD Reader 1.00 PQ: 0 ANSI: 0
Feb 25 19:11:15 [3] scsi 3:0:0:1: CD-ROM SanDisk U3 Titanium 3.27 PQ: 0 ANSI: 2
Feb 25 19:11:15 [3] scsi 4:0:0:1: Direct-Access Generic USB CF Reader 1.01 PQ: 0 ANSI: 0
Feb 25 19:11:15 [3] sd 3:0:0:0: [sdb] 4001422 512-byte hardware sectors: (2.04 GB/1.90 GiB)
Feb 25 19:11:15 [3] sd 3:0:0:0: [sdb] Write Protect is off
Feb 25 19:11:15 [1] sd 3:0:0:0: [sdb] Mode Sense: 03 00 00 00
Feb 25 19:11:15 [5] sd 3:0:0:0: [sdb] Assuming drive cache: write through
Feb 25 19:11:15 [1] usb-storage: device scan complete
Feb 25 19:11:15 [3] scsi 4:0:0:2: Direct-Access Generic USB SM Reader 1.02 PQ: 0 ANSI: 0
Feb 25 19:11:15 [3] sd 4:0:0:0: [sdc] Attached SCSI removable disk
Feb 25 19:11:15 [5] sd 3:0:0:0: [sdb] Assuming drive cache: write through
Feb 25 19:11:15 [2] sdb: sdb1
Feb 25 19:11:15 [3] scsi 4:0:0:3: Direct-Access Generic USB MS Reader 1.03 PQ: 0 ANSI: 0
Feb 25 19:11:15 [3] sd 4:0:0:1: [sdd] Attached SCSI removable disk
Feb 25 19:11:15 [1] usb-storage: device scan complete
Feb 25 19:11:15 [3] sd 4:0:0:2: [sde] Attached SCSI removable disk
Feb 25 19:11:15 [3] sd 3:0:0:0: [sdb] Attached SCSI removable disk
Feb 25 19:11:15 [3] sd 4:0:0:3: [sdf] Attached SCSI removable disk
Feb 25 19:11:18 [4] Driver 'sr' needs updating - please use bus_type methods
Feb 25 19:11:18 [4] sr0: scsi3-mmc drive: 8x/40x writer xa/form2 cdda tray
Feb 25 19:11:18 [2] Uniform CD-ROM driver Revision: 3.20
Feb 25 19:11:18 [1] sr 3:0:0:1: Attached scsi CD-ROM sr0
Feb 25 19:11:41 [2] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Feb 25 19:11:52 [2] kjournald starting. Commit interval 5 seconds
Feb 25 19:11:52 [2] EXT3 FS on sda1, internal journal
Feb 25 19:11:52 [2] EXT3-fs: mounted filesystem with writeback data mode.
Feb 25 19:12:35 [2] Adding 1048568k swap on /export/Disk-0/_NL_SWAP/VRAM. Priority:-1 extents:265 across:1066236k
Feb 25 19:16:46 [4] 3w-9xxx: scsi0: AEN: ERROR (0x04:0x0002): Degraded unit:unit=0, port=1.


Top
 Profile  
 
PostPosted: Sat Feb 27, 2010 3:24 am 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:01 pm
Posts: 801
Location: ServerElements
I need to look into this, we have provisions in NASLite to detect degraded arrays, that 3ware card has thrown alot of different things at us, that no other card does.


Top
 Profile  
 
PostPosted: Thu Jul 08, 2010 9:54 am 
Offline

Joined: Sun Mar 01, 2009 12:19 pm
Posts: 54
Roy,
I assume the degradation message only presents in the log after a boot?

It would be great to have NASLite detect a degraded array. Have you heard of any progress on adding this functionality?

Thanks,
John


Top
 Profile  
 
PostPosted: Thu Jul 08, 2010 12:58 pm 
Offline

Joined: Wed Oct 28, 2009 2:03 pm
Posts: 10
Hi John,

No I tested the raid degredation when the naslite server was running not on boot, I disconnected the drive power and naslite picked up there was a problem with the array shortly afterwards. It showed up in the syslog but there should be an audible alarm as well but that's not working.

I received a message from Tony on may 10th below.

"Hi Roy,

We are about to release a fix to the beta testers dressing the alarm, some driver issues, network stats and other minor tweaks. So, very soon.

SANLite is currently in development. We'll announce when ready for testing.

Thanks for your patience.

Tony Tonchev (Server Elements) "

So hopefully not long :-)

Roy.


Top
 Profile  
 
PostPosted: Tue Sep 21, 2010 6:17 am 
Offline

Joined: Wed Jul 19, 2006 9:16 am
Posts: 82
Location: Leicester, UK
Now that the alarm issue has been fixed in the latest release, how will I know if soemthing is wrong? Presumably it's an audible alarm, but when will it be sounded and for how long? If the alarm goes off while the NAS is running will the alarm sound continuously or is it designed to mute after a certain time? Will there be some indication via the web-page interface?

Thanks.


Top
 Profile  
 
PostPosted: Fri Sep 24, 2010 5:53 am 
Offline

Joined: Wed Oct 28, 2009 2:03 pm
Posts: 10
When the system is running and a failure occurs in a raid array ( I don't think it detects in a non raid setup eg single drives) naslite will detect the problem, after
a little while an alarm (a series of beeps) will sound and continuously pause and alarm until looked at.

A problem I did find though is because I don't keep my system on continuously I thought I would just check to see if naslite would pick
up a degraded array from power on (basically I unplugged a drive from a working array before powering up), the 3ware card obviously
picked up the problem and displaying that my raid 5 array was degraded after a pause continued to boot up to naslite.

I checked naslite syslog and it shows a meessage about the degraded array but the alarm didn't go off. I store my headerless nas system in a
cupboard and boot it up when needed so if a drive didn't start up on boot up and the array was degraded I would have no way of knowing
unless I kee looking in the system log.

I love the idea of naslite I think it's great but I can't take the risk with my data.

I have my nas running on Debian Etch with 3ware 3dm2 software that will email me of any issues with the 3ware 9500-s card with samba and rsync
for file sharing and backup slowly adding others , twonky media server and subsonic for music(both excellent).


Top
 Profile  
 
PostPosted: Fri Sep 24, 2010 7:31 am 
Offline

Joined: Sun Apr 02, 2006 9:05 pm
Posts: 1688
Location: Up State NY in the USA!!!!
roy wrote:
...I love the idea of naslite I think it's great but I can't take the risk with my data....


Well, that is exactly what you are doing by cycling the system off and on all the time. The spin down and spin up are the main ware on drive heads and platters. Also the thermal cycling is hard on components as well. Putting it in a cupboard, unless it has very good ventilation, is far from optimal as well.

Also, RAID5 systems should be backed up regularly as they are far less reliable the more drives you add. They only bring a basic level of fault redundancy to the table and are only a start to a comprehensive data safety regimen.

Good luck with that, I suspect that you are going to need it.

Mike


Top
 Profile  
 
PostPosted: Fri Sep 24, 2010 12:22 pm 
Offline

Joined: Wed Oct 28, 2009 2:03 pm
Posts: 10
Wo Wo Wo Wo,

I was simply answering a question about the raid degradation alarm and my experiences with naslite raid degredation alarm on 3ware 9500s raid card. I have spent quite a bit of time testing naslite and the 3ware card. I'm just posting my findings.

How often I cycle my system is besides the point. It is possible to have your system on 24/7 but if you experience a power
failure and your system comes back up automatically with a failed disk there is a chance you are not going to know about it. If another disk fails that could be the end of your data!!!

My Raid 5 array is reasonably large with temporary files as well as my important data. All my important data is backed up
to a raid 1 array on the same 3ware card and system. Yes My system is in a closet to cut out all noise but it is quite a large closet and the case I use gives more than adequate cooling.

thanks

Roy.


Top
 Profile  
 
PostPosted: Fri Sep 24, 2010 12:51 pm 
Offline

Joined: Sun Apr 02, 2006 9:05 pm
Posts: 1688
Location: Up State NY in the USA!!!!
Not getting on you, just pointing out the issues you are introducing with your practice.

As far as the power cycling being beside the point, I think you miss it entirely. It is hard on drives and especially the electronics. Thermal cycling is more of a killer as the scale of components shrinks. I have drives in service that have been running for more than 7 years. There are less than a few dozen power cycles on them. SMART still looks good on them all.

Thanks for the info. I hope that Tony and Ralph use it to good effect in future releases of the appliance OS.

Mike


Top
 Profile  
 
PostPosted: Fri Sep 24, 2010 1:54 pm 
Offline

Joined: Wed Oct 28, 2009 2:03 pm
Posts: 10
Yes I agree about constant power cycling and respect that you are very knowledgeable in the IT field but I was only replying to my experience to the question asked.

I do upgrade my hard drives on quite a regular basis, probably annually as bigger and better drives becomes available.

I do a quite a lot of testing scenarios of hardware/software nas/sans using sas/scsi/sata disks
available to make improvements and keep licensing costs down for the company where I work.

But as you know when something is not working or broken you need notification.

My current setup I can lose my entire Raid 5 disks and a Raid 1 disk and still get at my important data or lose a raid 1 and raid 5 disk and still get at my data and be informed.

Respect :-)

Roy.


Top
 Profile  
 
PostPosted: Fri Sep 24, 2010 2:42 pm 
Offline

Joined: Sun Apr 02, 2006 9:05 pm
Posts: 1688
Location: Up State NY in the USA!!!!
Glad to see I am not the only one that uses the terms SAS, SCSI, as well as SATA. I have a FC-AL array I am building. 64 drives of 147GB and 10K RPM. Should be a bit fast. Also have an array that will hold 16 SATA drives for backup of the 64 drive array. I am not that big a fan of most of the RAID cards. I prefer to use an appliance for the heavy lifting so all I present are LUNs to the NAS.

Mike


Top
 Profile  
 
PostPosted: Fri Sep 24, 2010 3:59 pm 
Offline

Joined: Wed Oct 28, 2009 2:03 pm
Posts: 10
Yes well times that x 2 and that's what I'm working on ;-)


Top
 Profile  
 
PostPosted: Fri Sep 24, 2010 4:29 pm 
Offline

Joined: Wed Oct 28, 2009 2:03 pm
Posts: 10
Can I also comment 64 drives of 147GB is off the wall, you must be quite close with the array
and constantly texting each other :-)


Top
 Profile  
 
PostPosted: Fri Sep 24, 2010 5:37 pm 
Offline

Joined: Sun Apr 02, 2006 9:05 pm
Posts: 1688
Location: Up State NY in the USA!!!!
You may surely comment. There are a few hot spares there......LOL But FC-AL enterprise class drives (as well as SAS and SCSI) are far more reliable than the run of the mill consumer stuff. I see far fewer failures than one would think. Eventually the main home/gaming computers will boot from the array via fibre to the controller. Dedicated 2Gb link should move right along.

The unit I have is a DataDirect S2A8000 with 12GB of cache. Just moved so I have yet to get it all in the new rack and setup. Got other fish to fry right now. I will be migrating to a SATA based system over time though as extra chassis come on Ebay.

Mike


Top
 Profile  
 
PostPosted: Mon Jul 04, 2011 5:31 am 
Offline

Joined: Wed Jul 19, 2006 9:16 am
Posts: 82
Location: Leicester, UK
Some time ago I posed the following question:

Quote:
Now that the alarm issue has been fixed in the latest release, how will I know if soemthing is wrong? Presumably it's an audible alarm, but when will it be sounded and for how long? If the alarm goes off while the NAS is running will the alarm sound continuously or is it designed to mute after a certain time? Will there be some indication via the web-page interface?


Although this issue is supposed to now be fixed, I'm not so sure. Yesterday, an alarm went off while I was sitting at my computer. It sounded just the once, and an entry was created at that time in the log to say that one of the units on one RAID port was degraded. Had I not been there at the time, I would never have heard the alarm. I rarely (if ever) inspect the logs, so how, otherwise, would I have known that I'd lost a disk?

Raymond


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 15 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 25 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group