July 23, 201015 yr I have been having random crashes whenever I try to load data onto my "disk1" for a period of time. Around 5-10mins. Now, I have replacing disk1 with another similar drive but the crashing still goes on. This random crashing doesn't seem to happen if I'm loading the data onto disk2 or disk3 as I was able to fill up disk3 completely without a system crash. Seemed like it is only happening to disk1. The crashing became more often when there is around 80GB of space left on disk1. All of the HDDs are WD aaks, but I don't think it is having any compatibility issue. As these crashes aren't 100% random, they only happen when constant stream of data is being loaded onto the disk. Parity checks also can be run 100% without issues and spin up/downs are fine as well. These are the list of things I have tried. replace disk1 with another HDD using another SATA port and another SATA cable memtest - no error tail -f /var/log/syslog - nothing comes up when the system began crashing. I get a kernel panic screen (the kernel panics are usually swapper tainted) updated unraid to 4.5.6 and my hardware AMD a64 3000 DFI lanparty nf3-250gb 1.5GB of ram onboard Gb nic pci video card pci sata card and my configuration The parity drive is connected to the mobo's sata port The data drives are connected to the pci sata card All drives are WD aaks Possible things I may try. replace the pci video card replace the mobo/cpu setup - don't really want to Right now I have move the disk1 onto disk4 and the parity is being written. So just wanna know if anybody have any idea regard this. note- The data drives temperature is running at 42-44C when the parity-sync is being run.
July 23, 201015 yr Author Jul 23 00:15:19 FS1 syslogd 1.4.1: restart. Jul 23 00:15:19 FS1 kernel: klogd 1.4.1, log source = /proc/kmsg started. Jul 23 00:15:19 FS1 kernel: Linux version 2.6.32.9-unRAID (root@Develop) (gcc version 4.2.3) #5 SMP Wed Jun 16 20:45:26 MDT 2010 Jul 23 00:15:19 FS1 kernel: KERNEL supported cpus: Jul 23 00:15:19 FS1 kernel: Intel GenuineIntel Jul 23 00:15:19 FS1 kernel: AMD AuthenticAMD Jul 23 00:15:19 FS1 kernel: NSC Geode by NSC Jul 23 00:15:19 FS1 kernel: Cyrix CyrixInstead Jul 23 00:15:19 FS1 kernel: Centaur CentaurHauls Jul 23 00:15:19 FS1 kernel: Transmeta GenuineTMx86 Jul 23 00:15:19 FS1 kernel: Transmeta TransmetaCPU Jul 23 00:15:19 FS1 kernel: UMC UMC UMC UMC Jul 23 00:15:19 FS1 kernel: BIOS-provided physical RAM map: Jul 23 00:15:19 FS1 kernel: BIOS-e820: 0000000000000000 - 000000000009d400 (usable) Jul 23 00:15:19 FS1 kernel: BIOS-e820: 000000000009d400 - 00000000000a0000 (reserved) Jul 23 00:15:19 FS1 kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) Jul 23 00:15:19 FS1 kernel: BIOS-e820: 0000000000100000 - 000000005fff0000 (usable) Jul 23 00:15:19 FS1 kernel: BIOS-e820: 000000005fff0000 - 000000005fff3000 (ACPI NVS) Jul 23 00:15:19 FS1 kernel: BIOS-e820: 000000005fff3000 - 0000000060000000 (ACPI data) Jul 23 00:15:19 FS1 kernel: BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) Jul 23 00:15:19 FS1 kernel: BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved) Jul 23 00:15:19 FS1 kernel: BIOS-e820: 00000000fefffc00 - 00000000ff000000 (reserved) Jul 23 00:15:19 FS1 kernel: BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved) Jul 23 00:15:19 FS1 kernel: DMI 2.2 present. Jul 23 00:15:19 FS1 kernel: Phoenix BIOS detected: BIOS may corrupt low RAM, working around it. Jul 23 00:15:19 FS1 kernel: e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) Jul 23 00:15:19 FS1 kernel: last_pfn = 0x5fff0 max_arch_pfn = 0x1000000 Jul 23 00:15:19 FS1 kernel: MTRR default type: uncachable Jul 23 00:15:19 FS1 kernel: MTRR fixed ranges enabled: Jul 23 00:15:19 FS1 kernel: 00000-9FFFF write-back Jul 23 00:15:19 FS1 kernel: A0000-BFFFF uncachable Jul 23 00:15:19 FS1 kernel: C0000-C7FFF write-protect Jul 23 00:15:19 FS1 kernel: C8000-FFFFF uncachable Jul 23 00:15:19 FS1 kernel: MTRR variable ranges enabled: Jul 23 00:15:19 FS1 kernel: 0 base 0000000000 mask FFC0000000 write-back Jul 23 00:15:19 FS1 kernel: 1 base 0040000000 mask FFE0000000 write-back Jul 23 00:15:19 FS1 kernel: 2 base 00E0000000 mask FFF8000000 write-combining Jul 23 00:15:19 FS1 kernel: 3 disabled Jul 23 00:15:19 FS1 kernel: 4 disabled Jul 23 00:15:19 FS1 kernel: 5 disabled Jul 23 00:15:19 FS1 kernel: 6 disabled Jul 23 00:15:19 FS1 kernel: 7 disabled Jul 23 00:15:19 FS1 kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 Jul 23 00:15:19 FS1 kernel: initial memory mapped : 0 - 01800000 Jul 23 00:15:19 FS1 kernel: init_memory_mapping: 0000000000000000-00000000379fe000 Jul 23 00:15:19 FS1 kernel: NX (Execute Disable) protection: active Jul 23 00:15:19 FS1 kernel: 0000000000 - 0000200000 page 4k Jul 23 00:15:19 FS1 kernel: 0000200000 - 0037800000 page 2M Jul 23 00:15:19 FS1 kernel: 0037800000 - 00379fe000 page 4k Jul 23 00:15:19 FS1 kernel: kernel direct mapping tables up to 379fe000 @ 10000-16000 Jul 23 00:15:19 FS1 kernel: RAMDISK: 5cbbb000 - 5ffef09a Jul 23 00:15:19 FS1 kernel: Allocated new RAMDISK: 0148f000 - 048c309a Jul 23 00:15:19 FS1 kernel: Move RAMDISK from 000000005cbbb000 - 000000005ffef099 to 0148f000 - 048c3099 Jul 23 00:15:19 FS1 kernel: ACPI: RSDP 000f7b00 00014 (v00 Nvidia) Jul 23 00:15:19 FS1 kernel: ACPI: RSDT 5fff3040 00028 (v01 Nvidia AWRDACPI 42302E31 AWRD 00000000) Jul 23 00:15:19 FS1 kernel: ACPI: FACP 5fff30c0 00074 (v01 Nvidia AWRDACPI 42302E31 AWRD 00000000) Jul 23 00:15:19 FS1 kernel: ACPI: DSDT 5fff3180 04A08 (v01 NVIDIA AWRDACPI 00001000 MSFT 0100000E) Jul 23 00:15:19 FS1 kernel: ACPI: FACS 5fff0000 00040 Jul 23 00:15:19 FS1 kernel: 645MB HIGHMEM available. Jul 23 00:15:19 FS1 kernel: 889MB LOWMEM available. Jul 23 00:15:19 FS1 kernel: mapped low ram: 0 - 379fe000 Jul 23 00:15:19 FS1 kernel: low ram: 0 - 379fe000 Jul 23 00:15:19 FS1 kernel: node 0 low ram: 00000000 - 379fe000 Jul 23 00:15:19 FS1 kernel: node 0 bootmap 00012000 - 00018f40 Jul 23 00:15:19 FS1 kernel: (9 early reservations) ==> bootmem [0000000000 - 00379fe000] Jul 23 00:15:19 FS1 kernel: #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] Jul 23 00:15:19 FS1 kernel: #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000] Jul 23 00:15:19 FS1 kernel: #2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000] Jul 23 00:15:19 FS1 kernel: #3 [0001000000 - 0001481c4c] TEXT DATA BSS ==> [0001000000 - 0001481c4c] Jul 23 00:15:19 FS1 kernel: #4 [000009d400 - 0000100000] BIOS reserved ==> [000009d400 - 0000100000] Jul 23 00:15:19 FS1 kernel: #5 [0001482000 - 000148e088] BRK ==> [0001482000 - 000148e088] Jul 23 00:15:19 FS1 kernel: #6 [0000010000 - 0000012000] PGTABLE ==> [0000010000 - 0000012000] Jul 23 00:15:19 FS1 kernel: #7 [000148f000 - 00048c309a] NEW RAMDISK ==> [000148f000 - 00048c309a] Jul 23 00:15:19 FS1 kernel: #8 [0000012000 - 0000019000] BOOTMAP ==> [0000012000 - 0000019000] Jul 23 00:15:19 FS1 kernel: Zone PFN ranges: Jul 23 00:15:19 FS1 kernel: DMA 0x00000010 -> 0x00001000 Jul 23 00:15:19 FS1 kernel: Normal 0x00001000 -> 0x000379fe Jul 23 00:15:19 FS1 kernel: HighMem 0x000379fe -> 0x0005fff0 Jul 23 00:15:19 FS1 kernel: Movable zone start PFN for each node Jul 23 00:15:19 FS1 kernel: early_node_map[2] active PFN ranges Jul 23 00:15:19 FS1 kernel: 0: 0x00000010 -> 0x0000009d Jul 23 00:15:19 FS1 kernel: 0: 0x00000100 -> 0x0005fff0 Jul 23 00:15:19 FS1 kernel: On node 0 totalpages: 393085 Jul 23 00:15:19 FS1 kernel: free_area_init_node: node 0, pgdat c13f0fc0, node_mem_map c48c5200 Jul 23 00:15:19 FS1 kernel: DMA zone: 32 pages used for memmap Jul 23 00:15:19 FS1 kernel: DMA zone: 0 pages reserved Jul 23 00:15:19 FS1 kernel: DMA zone: 3949 pages, LIFO batch:0 Jul 23 00:15:19 FS1 kernel: Normal zone: 1748 pages used for memmap Jul 23 00:15:19 FS1 kernel: Normal zone: 221994 pages, LIFO batch:31 Jul 23 00:15:19 FS1 kernel: HighMem zone: 1292 pages used for memmap Jul 23 00:15:19 FS1 kernel: HighMem zone: 164070 pages, LIFO batch:31 Jul 23 00:15:19 FS1 kernel: Using APIC driver default Jul 23 00:15:19 FS1 kernel: Nvidia board detected. Ignoring ACPI timer override. Jul 23 00:15:19 FS1 kernel: If you got timer trouble try acpi_use_timer_override Jul 23 00:15:19 FS1 kernel: ACPI: PM-Timer IO Port: 0x4008 Jul 23 00:15:19 FS1 kernel: SMP: Allowing 1 CPUs, 0 hotplug CPUs Jul 23 00:15:19 FS1 kernel: Found and enabled local APIC! Jul 23 00:15:19 FS1 kernel: nr_irqs_gsi: 16 Jul 23 00:15:19 FS1 kernel: Allocating PCI resources starting at 60000000 (gap: 60000000:9ec00000) Jul 23 00:15:19 FS1 kernel: NR_CPUS:4 nr_cpumask_bits:4 nr_cpu_ids:1 nr_node_ids:1 Jul 23 00:15:19 FS1 kernel: PERCPU: Embedded 11 pages/cpu @c5600000 s22232 r0 d22824 u2097152 Jul 23 00:15:19 FS1 kernel: pcpu-alloc: s22232 r0 d22824 u2097152 alloc=1*2097152 Jul 23 00:15:19 FS1 kernel: pcpu-alloc: [0] 0 Jul 23 00:15:19 FS1 kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 390013 Jul 23 00:15:19 FS1 kernel: Kernel command line: initrd=bzroot BOOT_IMAGE=bzimage Jul 23 00:15:19 FS1 kernel: PID hash table entries: 4096 (order: 2, 16384 bytes) Jul 23 00:15:19 FS1 kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Jul 23 00:15:19 FS1 kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Jul 23 00:15:19 FS1 kernel: Enabling fast FPU save and restore... done. Jul 23 00:15:19 FS1 kernel: Enabling unmasked SIMD FPU exception support... done. Jul 23 00:15:19 FS1 kernel: Initializing CPU#0 Jul 23 00:15:19 FS1 kernel: Initializing HighMem for node 0 (000379fe:0005fff0) Jul 23 00:15:19 FS1 kernel: Memory: 1500120k/1572800k available (2692k kernel code, 71312k reserved, 1359k data, 312k init, 661448k highmem) Jul 23 00:15:19 FS1 kernel: virtual kernel memory layout: Jul 23 00:15:19 FS1 kernel: fixmap : 0xfff6b000 - 0xfffff000 ( 592 kB) Jul 23 00:15:19 FS1 kernel: pkmap : 0xffa00000 - 0xffc00000 (2048 kB) Jul 23 00:15:19 FS1 kernel: vmalloc : 0xf81fe000 - 0xff9fe000 ( 120 MB) Jul 23 00:15:19 FS1 kernel: lowmem : 0xc0000000 - 0xf79fe000 ( 889 MB) Jul 23 00:15:19 FS1 kernel: .init : 0xc13f5000 - 0xc1443000 ( 312 kB) Jul 23 00:15:19 FS1 kernel: .data : 0xc12a12ac - 0xc13f4eec (1359 kB) Jul 23 00:15:19 FS1 kernel: .text : 0xc1000000 - 0xc12a12ac (2692 kB) Jul 23 00:15:19 FS1 kernel: Checking if this processor honours the WP bit even in supervisor mode...Ok. Jul 23 00:15:19 FS1 kernel: SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 Jul 23 00:15:19 FS1 kernel: Hierarchical RCU implementation. Jul 23 00:15:19 FS1 kernel: NR_IRQS:384 Jul 23 00:15:19 FS1 kernel: spurious 8259A interrupt: IRQ7. Jul 23 00:15:19 FS1 kernel: Console: colour VGA+ 80x25 Jul 23 00:15:19 FS1 kernel: console [tty0] enabled Jul 23 00:15:19 FS1 kernel: Fast TSC calibration using PIT Jul 23 00:15:19 FS1 kernel: Detected 2009.551 MHz processor. Jul 23 00:15:19 FS1 kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 4019.10 BogoMIPS (lpj=20095510) Jul 23 00:15:19 FS1 kernel: Mount-cache hash table entries: 512 Jul 23 00:15:19 FS1 kernel: CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) Jul 23 00:15:19 FS1 kernel: CPU: L2 Cache: 512K (64 bytes/line) Jul 23 00:15:19 FS1 kernel: mce: CPU supports 5 MCE banks Jul 23 00:15:19 FS1 kernel: Checking 'hlt' instruction... OK. Jul 23 00:15:19 FS1 kernel: SMP alternatives: switching to UP code Jul 23 00:15:19 FS1 kernel: Freeing SMP alternatives: 14k freed Jul 23 00:15:19 FS1 kernel: ACPI: Core revision 20090903 Jul 23 00:15:19 FS1 kernel: ACPI: setting ELCR to 0200 (from 0c20) Jul 23 00:15:19 FS1 kernel: weird, boot CPU (#0) not listed by the BIOS. Jul 23 00:15:19 FS1 kernel: SMP motherboard not detected. Jul 23 00:15:19 FS1 kernel: SMP disabled Jul 23 00:15:19 FS1 kernel: Brought up 1 CPUs Jul 23 00:15:19 FS1 kernel: Total of 1 processors activated (4019.10 BogoMIPS). Jul 23 00:15:19 FS1 kernel: NET: Registered protocol family 16 Jul 23 00:15:19 FS1 kernel: ACPI: bus type pci registered Jul 23 00:15:19 FS1 kernel: PCI: PCI BIOS revision 2.10 entry at 0xfa660, last bus=2 Jul 23 00:15:19 FS1 kernel: PCI: Using configuration type 1 for base access Jul 23 00:15:19 FS1 kernel: bio: create slab at 0 Jul 23 00:15:19 FS1 kernel: ACPI: EC: Look up EC in DSDT Jul 23 00:15:19 FS1 kernel: ACPI Warning: Package List length (0x6) larger than NumElements count (0x3), truncated Jul 23 00:15:19 FS1 kernel: (20090903/dsobject-515) Jul 23 00:15:19 FS1 kernel: ACPI: Interpreter enabled Jul 23 00:15:19 FS1 kernel: ACPI: (supports S0 S1 S5) Jul 23 00:15:19 FS1 kernel: ACPI: Using PIC for interrupt routing Jul 23 00:15:19 FS1 kernel: ACPI: Power Resource [iSAV] (on) Jul 23 00:15:19 FS1 kernel: ACPI: No dock devices found. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Root Bridge [PCI0] (0000:00) Jul 23 00:15:19 FS1 kernel: pci 0000:00:00.0: reg 10 32bit mmio pref: [0xe0000000-0xe7ffffff] Jul 23 00:15:19 FS1 kernel: pci 0000:00:01.1: reg 10 io port: [0xe100-0xe11f] Jul 23 00:15:19 FS1 kernel: pci 0000:00:01.1: reg 20 io port: [0x4c00-0x4c3f] Jul 23 00:15:19 FS1 kernel: pci 0000:00:01.1: reg 24 io port: [0x4c40-0x4c7f] Jul 23 00:15:19 FS1 kernel: pci 0000:00:01.1: PME# supported from D3hot D3cold Jul 23 00:15:19 FS1 kernel: pci 0000:00:01.1: PME# disabled Jul 23 00:15:19 FS1 kernel: pci 0000:00:02.0: reg 10 32bit mmio: [0xea003000-0xea003fff] Jul 23 00:15:19 FS1 kernel: pci 0000:00:02.0: supports D1 D2 Jul 23 00:15:19 FS1 kernel: pci 0000:00:02.0: PME# supported from D0 D1 D2 D3hot D3cold Jul 23 00:15:19 FS1 kernel: pci 0000:00:02.0: PME# disabled Jul 23 00:15:19 FS1 kernel: pci 0000:00:02.1: reg 10 32bit mmio: [0xea004000-0xea004fff] Jul 23 00:15:19 FS1 kernel: pci 0000:00:02.1: supports D1 D2 Jul 23 00:15:19 FS1 kernel: pci 0000:00:02.1: PME# supported from D0 D1 D2 D3hot D3cold Jul 23 00:15:19 FS1 kernel: pci 0000:00:02.1: PME# disabled Jul 23 00:15:19 FS1 kernel: pci 0000:00:02.2: reg 10 32bit mmio: [0xea000000-0xea0000ff] Jul 23 00:15:19 FS1 kernel: pci 0000:00:02.2: supports D1 D2 Jul 23 00:15:19 FS1 kernel: pci 0000:00:02.2: PME# supported from D0 D1 D2 D3hot D3cold Jul 23 00:15:19 FS1 kernel: pci 0000:00:02.2: PME# disabled Jul 23 00:15:19 FS1 kernel: pci 0000:00:05.0: reg 10 32bit mmio: [0xea001000-0xea001fff] Jul 23 00:15:19 FS1 kernel: pci 0000:00:05.0: reg 14 io port: [0xd200-0xd207] Jul 23 00:15:19 FS1 kernel: pci 0000:00:05.0: supports D1 D2 Jul 23 00:15:19 FS1 kernel: pci 0000:00:05.0: PME# supported from D0 D1 D2 D3hot D3cold Jul 23 00:15:19 FS1 kernel: pci 0000:00:05.0: PME# disabled Jul 23 00:15:19 FS1 kernel: pci 0000:00:08.0: reg 20 io port: [0xf000-0xf00f] Jul 23 00:15:19 FS1 kernel: pci 0000:00:09.0: reg 10 io port: [0x9e0-0x9e7] Jul 23 00:15:19 FS1 kernel: pci 0000:00:09.0: reg 14 io port: [0xbe0-0xbe3] Jul 23 00:15:19 FS1 kernel: pci 0000:00:09.0: reg 18 io port: [0x960-0x967] Jul 23 00:15:19 FS1 kernel: pci 0000:00:09.0: reg 1c io port: [0xb60-0xb63] Jul 23 00:15:19 FS1 kernel: pci 0000:00:09.0: reg 20 io port: [0xd900-0xd90f] Jul 23 00:15:19 FS1 kernel: pci 0000:00:09.0: reg 24 io port: [0xda00-0xda7f] Jul 23 00:15:19 FS1 kernel: pci 0000:00:0a.0: reg 10 io port: [0x9f0-0x9f7] Jul 23 00:15:19 FS1 kernel: pci 0000:00:0a.0: reg 14 io port: [0xbf0-0xbf3] Jul 23 00:15:19 FS1 kernel: pci 0000:00:0a.0: reg 18 io port: [0x970-0x977] Jul 23 00:15:19 FS1 kernel: pci 0000:00:0a.0: reg 1c io port: [0xb70-0xb73] Jul 23 00:15:19 FS1 kernel: pci 0000:00:0a.0: reg 20 io port: [0xdf00-0xdf0f] Jul 23 00:15:19 FS1 kernel: pci 0000:00:0a.0: reg 24 io port: [0xe000-0xe07f] Jul 23 00:15:19 FS1 kernel: pci 0000:02:07.0: reg 10 32bit mmio pref: [0xe9000000-0xe9ffffff] Jul 23 00:15:19 FS1 kernel: pci 0000:02:07.0: reg 30 32bit mmio pref: [0x000000-0x007fff] Jul 23 00:15:19 FS1 kernel: pci 0000:02:09.0: reg 10 io port: [0xc100-0xc107] Jul 23 00:15:19 FS1 kernel: pci 0000:02:09.0: reg 14 io port: [0xc200-0xc203] Jul 23 00:15:19 FS1 kernel: pci 0000:02:09.0: reg 18 io port: [0xc300-0xc307] Jul 23 00:15:19 FS1 kernel: pci 0000:02:09.0: reg 1c io port: [0xc400-0xc403] Jul 23 00:15:19 FS1 kernel: pci 0000:02:09.0: reg 20 io port: [0xc500-0xc50f] Jul 23 00:15:19 FS1 kernel: pci 0000:02:09.0: reg 24 32bit mmio: [0xe8080000-0xe80803ff] Jul 23 00:15:19 FS1 kernel: pci 0000:02:09.0: reg 30 32bit mmio pref: [0x000000-0x07ffff] Jul 23 00:15:19 FS1 kernel: pci 0000:02:09.0: supports D1 D2 Jul 23 00:15:19 FS1 kernel: pci 0000:00:0e.0: bridge io port: [0xc000-0xcfff] Jul 23 00:15:19 FS1 kernel: pci 0000:00:0e.0: bridge 32bit mmio: [0xe8000000-0xe8ffffff] Jul 23 00:15:19 FS1 kernel: pci 0000:00:0e.0: bridge 32bit mmio pref: [0xe9000000-0xe9ffffff] Jul 23 00:15:19 FS1 kernel: pci_bus 0000:00: on NUMA node 0 Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT] Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT] Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 *5 6 7 10 11 12 14 15) Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 5 6 7 *10 11 12 14 15) Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 *5 6 7 10 11 12 14 15) Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 *5 6 7 10 11 12 14 15) Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 6 7 10 *11 12 14 15)
July 23, 201015 yr Author Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LAPU] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 5 6 7 10 *11 12 14 15) Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 *5 6 7 10 11 12 14 15) Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LFIR] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [L3CM] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LSID] (IRQs 3 4 5 6 7 10 *11 12 14 15) Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LFID] (IRQs 3 4 5 6 7 *10 11 12 14 15) Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [APC1] (IRQs *16), disabled. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [APC2] (IRQs *17) Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [APC3] (IRQs *18), disabled. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [APC4] (IRQs *19) Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22) *0 Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22) *0 Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22) *0 Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [APCI] (IRQs 20 21 22) *0, disabled. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22) *0, disabled. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22) *0, disabled. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [APCS] (IRQs *23) Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22) *0 Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22) *0, disabled. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [AP3C] (IRQs 20 21 22) *0, disabled. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22) *0, disabled. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [APSI] (IRQs 20 21 22) *0, disabled. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [APSJ] (IRQs 20 21 22) *0, disabled. Jul 23 00:15:19 FS1 kernel: vgaarb: device added: PCI:0000:02:07.0,decodes=io+mem,owns=io+mem,locks=none Jul 23 00:15:19 FS1 kernel: vgaarb: loaded Jul 23 00:15:19 FS1 kernel: SCSI subsystem initialized Jul 23 00:15:19 FS1 kernel: libata version 3.00 loaded. Jul 23 00:15:19 FS1 kernel: usbcore: registered new interface driver usbfs Jul 23 00:15:19 FS1 kernel: usbcore: registered new interface driver hub Jul 23 00:15:19 FS1 kernel: usbcore: registered new device driver usb Jul 23 00:15:19 FS1 kernel: PCI: Using ACPI for IRQ routing Jul 23 00:15:19 FS1 kernel: Switching to clocksource tsc Jul 23 00:15:19 FS1 kernel: pnp: PnP ACPI init Jul 23 00:15:19 FS1 kernel: ACPI: bus type pnp registered Jul 23 00:15:19 FS1 kernel: pnp: PnP ACPI: found 13 devices Jul 23 00:15:19 FS1 kernel: ACPI: ACPI bus type pnp unregistered Jul 23 00:15:19 FS1 kernel: system 00:00: ioport range 0x4000-0x407f has been reserved Jul 23 00:15:19 FS1 kernel: system 00:00: ioport range 0x4080-0x40ff has been reserved Jul 23 00:15:19 FS1 kernel: system 00:00: ioport range 0x4400-0x447f has been reserved Jul 23 00:15:19 FS1 kernel: system 00:00: ioport range 0x4480-0x44ff has been reserved Jul 23 00:15:19 FS1 kernel: system 00:00: ioport range 0x4800-0x487f has been reserved Jul 23 00:15:19 FS1 kernel: system 00:00: ioport range 0x4880-0x48ff has been reserved Jul 23 00:15:19 FS1 kernel: system 00:01: iomem range 0xf0000-0xf3fff could not be reserved Jul 23 00:15:19 FS1 kernel: system 00:01: iomem range 0xf4000-0xf7fff could not be reserved Jul 23 00:15:19 FS1 kernel: system 00:01: iomem range 0xf8000-0xfbfff could not be reserved Jul 23 00:15:19 FS1 kernel: system 00:01: iomem range 0xfc000-0xfffff could not be reserved Jul 23 00:15:19 FS1 kernel: system 00:01: iomem range 0x5fff0000-0x5fffffff could not be reserved Jul 23 00:15:19 FS1 kernel: system 00:01: iomem range 0xffff0000-0xffffffff has been reserved Jul 23 00:15:19 FS1 kernel: system 00:01: iomem range 0x0-0x9ffff could not be reserved Jul 23 00:15:19 FS1 kernel: system 00:01: iomem range 0x100000-0x5ffeffff could not be reserved Jul 23 00:15:19 FS1 kernel: system 00:01: iomem range 0xfec00000-0xfec00fff has been reserved Jul 23 00:15:19 FS1 kernel: system 00:01: iomem range 0xfee00000-0xfeefffff has been reserved Jul 23 00:15:19 FS1 kernel: system 00:01: iomem range 0xfefff000-0xfeffffff could not be reserved Jul 23 00:15:19 FS1 kernel: system 00:01: iomem range 0xfff80000-0xfff80fff has been reserved Jul 23 00:15:19 FS1 kernel: system 00:01: iomem range 0xfff90000-0xfffbffff has been reserved Jul 23 00:15:19 FS1 kernel: system 00:01: iomem range 0xfffed000-0xfffeffff has been reserved Jul 23 00:15:19 FS1 kernel: system 00:03: ioport range 0x4d0-0x4d1 has been reserved Jul 23 00:15:19 FS1 kernel: system 00:03: ioport range 0x800-0x805 has been reserved Jul 23 00:15:19 FS1 kernel: pci 0000:00:0b.0: PCI bridge, secondary bus 0000:01 Jul 23 00:15:19 FS1 kernel: pci 0000:00:0b.0: IO window: disabled Jul 23 00:15:19 FS1 kernel: pci 0000:00:0b.0: MEM window: disabled Jul 23 00:15:19 FS1 kernel: pci 0000:00:0b.0: PREFETCH window: disabled Jul 23 00:15:19 FS1 kernel: pci 0000:00:0e.0: PCI bridge, secondary bus 0000:02 Jul 23 00:15:19 FS1 kernel: pci 0000:00:0e.0: IO window: 0xc000-0xcfff Jul 23 00:15:19 FS1 kernel: pci 0000:00:0e.0: MEM window: 0xe8000000-0xe8ffffff Jul 23 00:15:19 FS1 kernel: pci 0000:00:0e.0: PREFETCH window: 0xe9000000-0xe9ffffff Jul 23 00:15:19 FS1 kernel: pci 0000:00:0e.0: setting latency timer to 64 Jul 23 00:15:19 FS1 kernel: pci_bus 0000:00: resource 0 io: [0x00-0xffff] Jul 23 00:15:19 FS1 kernel: pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffffffffffff] Jul 23 00:15:19 FS1 kernel: pci_bus 0000:02: resource 0 io: [0xc000-0xcfff] Jul 23 00:15:19 FS1 kernel: pci_bus 0000:02: resource 1 mem: [0xe8000000-0xe8ffffff] Jul 23 00:15:19 FS1 kernel: pci_bus 0000:02: resource 2 pref mem [0xe9000000-0xe9ffffff] Jul 23 00:15:19 FS1 kernel: NET: Registered protocol family 2 Jul 23 00:15:19 FS1 kernel: IP route cache hash table entries: 32768 (order: 5, 131072 bytes) Jul 23 00:15:19 FS1 kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes) Jul 23 00:15:19 FS1 kernel: TCP bind hash table entries: 65536 (order: 7, 524288 bytes) Jul 23 00:15:19 FS1 kernel: TCP: Hash tables configured (established 131072 bind 65536) Jul 23 00:15:19 FS1 kernel: TCP reno registered Jul 23 00:15:19 FS1 kernel: NET: Registered protocol family 1 Jul 23 00:15:19 FS1 kernel: RPC: Registered udp transport module. Jul 23 00:15:19 FS1 kernel: RPC: Registered tcp transport module. Jul 23 00:15:19 FS1 kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Jul 23 00:15:19 FS1 kernel: pci 0000:02:07.0: Boot video device Jul 23 00:15:19 FS1 kernel: Unpacking initramfs... Jul 23 00:15:19 FS1 kernel: Freeing initrd memory: 53456k freed Jul 23 00:15:19 FS1 kernel: highmem bounce pool size: 64 pages Jul 23 00:15:19 FS1 kernel: Installing knfsd (copyright © 1996 [email protected]). Jul 23 00:15:19 FS1 kernel: Slow work thread pool: Starting up Jul 23 00:15:19 FS1 kernel: Slow work thread pool: Ready Jul 23 00:15:19 FS1 kernel: fuse init (API version 7.13) Jul 23 00:15:19 FS1 kernel: msgmni has been set to 1744 Jul 23 00:15:19 FS1 kernel: io scheduler noop registered (default) Jul 23 00:15:19 FS1 kernel: io scheduler anticipatory registered Jul 23 00:15:19 FS1 kernel: io scheduler deadline registered Jul 23 00:15:19 FS1 kernel: io scheduler cfq registered Jul 23 00:15:19 FS1 kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0 Jul 23 00:15:19 FS1 kernel: ACPI: Power Button [PWRB] Jul 23 00:15:19 FS1 kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 Jul 23 00:15:19 FS1 kernel: ACPI: Power Button [PWRF] Jul 23 00:15:19 FS1 kernel: fan PNP0C0B:00: registered as cooling_device0 Jul 23 00:15:19 FS1 kernel: ACPI: Fan [FAN] (on) Jul 23 00:15:19 FS1 kernel: processor LNXCPU:00: registered as cooling_device1 Jul 23 00:15:19 FS1 kernel: thermal LNXTHERM:01: registered as thermal_zone0 Jul 23 00:15:19 FS1 kernel: ACPI: Thermal Zone [THRM] (40 C) Jul 23 00:15:19 FS1 kernel: lp: driver loaded but no devices found Jul 23 00:15:19 FS1 kernel: Real Time Clock Driver v1.12b Jul 23 00:15:19 FS1 kernel: Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds). Jul 23 00:15:19 FS1 kernel: Hangcheck: Using get_cycles(). Jul 23 00:15:19 FS1 kernel: Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled Jul 23 00:15:19 FS1 kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A Jul 23 00:15:19 FS1 kernel: 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A Jul 23 00:15:19 FS1 kernel: parport_pc 00:0b: reported by Plug and Play ACPI Jul 23 00:15:19 FS1 kernel: parport0: PC-style at 0x378, irq 7 [PCSPP(,...)] Jul 23 00:15:19 FS1 kernel: lp0: using parport0 (interrupt-driven). Jul 23 00:15:19 FS1 kernel: FDC 0 is a post-1991 82077 Jul 23 00:15:19 FS1 kernel: loop: module loaded Jul 23 00:15:19 FS1 kernel: Uniform Multi-Platform E-IDE driver Jul 23 00:15:19 FS1 kernel: e100: Intel® PRO/100 Network Driver, 3.5.24-k2-NAPI Jul 23 00:15:19 FS1 kernel: e100: Copyright© 1999-2006 Intel Corporation Jul 23 00:15:19 FS1 kernel: Broadcom NetXtreme II CNIC Driver cnic v2.0.1 (Oct 01, 2009) Jul 23 00:15:19 FS1 kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LUB2] enabled at IRQ 5 Jul 23 00:15:19 FS1 kernel: PCI: setting IRQ 5 as level-triggered Jul 23 00:15:19 FS1 kernel: ehci_hcd 0000:00:02.2: PCI INT C -> Link[LUB2] -> GSI 5 (level, low) -> IRQ 5 Jul 23 00:15:19 FS1 kernel: ehci_hcd 0000:00:02.2: setting latency timer to 64 Jul 23 00:15:19 FS1 kernel: ehci_hcd 0000:00:02.2: EHCI Host Controller Jul 23 00:15:19 FS1 kernel: ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1 Jul 23 00:15:19 FS1 kernel: ehci_hcd 0000:00:02.2: debug port 1 Jul 23 00:15:19 FS1 kernel: ehci_hcd 0000:00:02.2: cache line size of 64 is not supported Jul 23 00:15:19 FS1 kernel: ehci_hcd 0000:00:02.2: irq 5, io mem 0xea000000 Jul 23 00:15:19 FS1 kernel: ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00 Jul 23 00:15:19 FS1 kernel: usb usb1: configuration #1 chosen from 1 choice Jul 23 00:15:19 FS1 kernel: hub 1-0:1.0: USB hub found Jul 23 00:15:19 FS1 kernel: hub 1-0:1.0: 8 ports detected Jul 23 00:15:19 FS1 kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LUBA] enabled at IRQ 5 Jul 23 00:15:19 FS1 kernel: ohci_hcd 0000:00:02.0: PCI INT A -> Link[LUBA] -> GSI 5 (level, low) -> IRQ 5 Jul 23 00:15:19 FS1 kernel: ohci_hcd 0000:00:02.0: setting latency timer to 64 Jul 23 00:15:19 FS1 kernel: ohci_hcd 0000:00:02.0: OHCI Host Controller Jul 23 00:15:19 FS1 kernel: ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2 Jul 23 00:15:19 FS1 kernel: ohci_hcd 0000:00:02.0: irq 5, io mem 0xea003000 Jul 23 00:15:19 FS1 kernel: usb usb2: configuration #1 chosen from 1 choice Jul 23 00:15:19 FS1 kernel: hub 2-0:1.0: USB hub found Jul 23 00:15:19 FS1 kernel: hub 2-0:1.0: 4 ports detected Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LUBB] enabled at IRQ 5 Jul 23 00:15:19 FS1 kernel: ohci_hcd 0000:00:02.1: PCI INT B -> Link[LUBB] -> GSI 5 (level, low) -> IRQ 5 Jul 23 00:15:19 FS1 kernel: ohci_hcd 0000:00:02.1: setting latency timer to 64 Jul 23 00:15:19 FS1 kernel: ohci_hcd 0000:00:02.1: OHCI Host Controller Jul 23 00:15:19 FS1 kernel: ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 3 Jul 23 00:15:19 FS1 kernel: ohci_hcd 0000:00:02.1: irq 5, io mem 0xea004000 Jul 23 00:15:19 FS1 kernel: usb usb3: configuration #1 chosen from 1 choice Jul 23 00:15:19 FS1 kernel: hub 3-0:1.0: USB hub found Jul 23 00:15:19 FS1 kernel: hub 3-0:1.0: 4 ports detected Jul 23 00:15:19 FS1 kernel: uhci_hcd: USB Universal Host Controller Interface driver Jul 23 00:15:19 FS1 kernel: usbcore: registered new interface driver usblp Jul 23 00:15:19 FS1 kernel: Initializing USB Mass Storage driver... Jul 23 00:15:19 FS1 kernel: usbcore: registered new interface driver usb-storage Jul 23 00:15:19 FS1 kernel: USB Mass Storage support registered. Jul 23 00:15:19 FS1 kernel: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1 Jul 23 00:15:19 FS1 kernel: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp Jul 23 00:15:19 FS1 kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 Jul 23 00:15:19 FS1 kernel: mice: PS/2 mouse device common for all mice Jul 23 00:15:19 FS1 kernel: input: PC Speaker as /devices/platform/pcspkr/input/input2 Jul 23 00:15:19 FS1 kernel: it87: Found IT8712F chip at 0x290, revision 6 Jul 23 00:15:19 FS1 kernel: ACPI: I/O resource it87 [0x295-0x296] conflicts with ACPI region IP__ [0x295-0x296] Jul 23 00:15:19 FS1 kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Jul 23 00:15:19 FS1 kernel: cpuidle: using governor ladder Jul 23 00:15:19 FS1 kernel: usbcore: registered new interface driver hiddev Jul 23 00:15:19 FS1 kernel: usbcore: registered new interface driver usbhid Jul 23 00:15:19 FS1 kernel: usbhid: v2.6:USB HID core driver Jul 23 00:15:19 FS1 kernel: TCP cubic registered Jul 23 00:15:19 FS1 kernel: NET: Registered protocol family 17 Jul 23 00:15:19 FS1 kernel: Using IPI No-Shortcut mode Jul 23 00:15:19 FS1 kernel: Freeing unused kernel memory: 312k freed Jul 23 00:15:19 FS1 kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 Jul 23 00:15:19 FS1 kernel: usb 1-2: new high speed USB device using ehci_hcd and address 2 Jul 23 00:15:19 FS1 kernel: usb 1-2: configuration #1 chosen from 1 choice Jul 23 00:15:19 FS1 kernel: scsi0 : SCSI emulation for USB Mass Storage devices Jul 23 00:15:19 FS1 kernel: usb-storage: device found at 2 Jul 23 00:15:19 FS1 kernel: usb-storage: waiting for device to settle before scanning Jul 23 00:15:19 FS1 kernel: forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64. Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 11 Jul 23 00:15:19 FS1 kernel: PCI: setting IRQ 11 as level-triggered Jul 23 00:15:19 FS1 kernel: forcedeth 0000:00:05.0: PCI INT A -> Link[LMAC] -> GSI 11 (level, low) -> IRQ 11 Jul 23 00:15:19 FS1 kernel: forcedeth 0000:00:05.0: setting latency timer to 64 Jul 23 00:15:19 FS1 kernel: nv_probe: set workaround bit for reversed mac addr Jul 23 00:15:19 FS1 kernel: forcedeth 0000:00:05.0: ifname eth0, PHY OUI 0x5043 @ 1, addr 00:01:29:fa:14:10 Jul 23 00:15:19 FS1 kernel: forcedeth 0000:00:05.0: csum timirq gbit lnktim desc-v2 Jul 23 00:15:19 FS1 kernel: amd74xx 0000:00:08.0: UDMA133 controller Jul 23 00:15:19 FS1 kernel: amd74xx 0000:00:08.0: IDE controller (0x10de:0x00e5 rev 0xa2) Jul 23 00:15:19 FS1 kernel: AMD_IDE 0000:00:08.0: power state changed by ACPI to D0 Jul 23 00:15:19 FS1 kernel: amd74xx 0000:00:08.0: not 100%% native mode: will probe irqs later Jul 23 00:15:19 FS1 kernel: ide0: BM-DMA at 0xf000-0xf007 Jul 23 00:15:19 FS1 kernel: ide1: BM-DMA at 0xf008-0xf00f Jul 23 00:15:19 FS1 kernel: Probing IDE interface ide0... Jul 23 00:15:19 FS1 kernel: Probing IDE interface ide1... Jul 23 00:15:19 FS1 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Jul 23 00:15:19 FS1 kernel: ide1 at 0x170-0x177,0x376 on irq 15 Jul 23 00:15:19 FS1 kernel: sata_nv 0000:00:09.0: version 3.5 Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LSID] enabled at IRQ 11 Jul 23 00:15:19 FS1 kernel: sata_nv 0000:00:09.0: PCI INT A -> Link[LSID] -> GSI 11 (level, low) -> IRQ 11 Jul 23 00:15:19 FS1 kernel: sata_nv 0000:00:09.0: setting latency timer to 64 Jul 23 00:15:19 FS1 kernel: scsi1 : sata_nv Jul 23 00:15:19 FS1 kernel: scsi2 : sata_nv Jul 23 00:15:19 FS1 kernel: ata1: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xd900 irq 11 Jul 23 00:15:19 FS1 kernel: ata2: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xd908 irq 11 Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LFID] enabled at IRQ 10 Jul 23 00:15:19 FS1 kernel: PCI: setting IRQ 10 as level-triggered
July 23, 201015 yr Author Jul 23 00:15:19 FS1 kernel: sata_nv 0000:00:0a.0: PCI INT A -> Link[LFID] -> GSI 10 (level, low) -> IRQ 10 Jul 23 00:15:19 FS1 kernel: sata_nv 0000:00:0a.0: setting latency timer to 64 Jul 23 00:15:19 FS1 kernel: scsi3 : sata_nv Jul 23 00:15:19 FS1 kernel: scsi4 : sata_nv Jul 23 00:15:19 FS1 kernel: ata3: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xdf00 irq 10 Jul 23 00:15:19 FS1 kernel: ata4: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xdf08 irq 10 Jul 23 00:15:19 FS1 kernel: ata3: SATA link down (SStatus 0 SControl 300) Jul 23 00:15:19 FS1 kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Jul 23 00:15:19 FS1 kernel: ata1.00: ATA-8: WDC WD6400AAKS-65A7B2, 01.03B01, max UDMA/133 Jul 23 00:15:19 FS1 kernel: ata1.00: 1250263728 sectors, multi 1: LBA48 NCQ (depth 0/32) Jul 23 00:15:19 FS1 kernel: ata1.00: configured for UDMA/133 Jul 23 00:15:19 FS1 kernel: scsi 1:0:0:0: Direct-Access ATA WDC WD6400AAKS-6 01.0 PQ: 0 ANSI: 5 Jul 23 00:15:19 FS1 kernel: sd 1:0:0:0: [sda] 1250263728 512-byte logical blocks: (640 GB/596 GiB) Jul 23 00:15:19 FS1 kernel: sd 1:0:0:0: [sda] Write Protect is off Jul 23 00:15:19 FS1 kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 Jul 23 00:15:19 FS1 kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 23 00:15:19 FS1 kernel: sda: sda1 Jul 23 00:15:19 FS1 kernel: sd 1:0:0:0: [sda] Attached SCSI disk Jul 23 00:15:19 FS1 kernel: ata2: SATA link down (SStatus 0 SControl 300) Jul 23 00:15:19 FS1 kernel: ata4: SATA link down (SStatus 0 SControl 300) Jul 23 00:15:19 FS1 kernel: sata_sil 0000:02:09.0: version 2.4 Jul 23 00:15:19 FS1 kernel: ACPI: PCI Interrupt Link [LNK2] enabled at IRQ 5 Jul 23 00:15:19 FS1 kernel: sata_sil 0000:02:09.0: PCI INT A -> Link[LNK2] -> GSI 5 (level, low) -> IRQ 5 Jul 23 00:15:19 FS1 kernel: sata_sil 0000:02:09.0: Applying R_ERR on DMA activate FIS errata fix Jul 23 00:15:19 FS1 kernel: scsi5 : sata_sil Jul 23 00:15:19 FS1 kernel: scsi6 : sata_sil Jul 23 00:15:19 FS1 kernel: scsi7 : sata_sil Jul 23 00:15:19 FS1 kernel: scsi8 : sata_sil Jul 23 00:15:19 FS1 kernel: ata5: SATA max UDMA/100 mmio m1024@0xe8080000 tf 0xe8080080 irq 5 Jul 23 00:15:19 FS1 kernel: ata6: SATA max UDMA/100 mmio m1024@0xe8080000 tf 0xe80800c0 irq 5 Jul 23 00:15:19 FS1 kernel: ata7: SATA max UDMA/100 mmio m1024@0xe8080000 tf 0xe8080280 irq 5 Jul 23 00:15:19 FS1 kernel: ata8: SATA max UDMA/100 mmio m1024@0xe8080000 tf 0xe80802c0 irq 5 Jul 23 00:15:19 FS1 kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jul 23 00:15:19 FS1 kernel: ata5.00: ATA-8: WDC WD6400AAKS-22A7B0, 01.03B01, max UDMA/133 Jul 23 00:15:19 FS1 kernel: ata5.00: 1250263728 sectors, multi 16: LBA48 NCQ (depth 0/32) Jul 23 00:15:19 FS1 kernel: ata5.00: configured for UDMA/100 Jul 23 00:15:19 FS1 kernel: scsi 5:0:0:0: Direct-Access ATA WDC WD6400AAKS-2 01.0 PQ: 0 ANSI: 5 Jul 23 00:15:19 FS1 kernel: sd 5:0:0:0: [sdb] 1250263728 512-byte logical blocks: (640 GB/596 GiB) Jul 23 00:15:19 FS1 kernel: sd 5:0:0:0: [sdb] Write Protect is off Jul 23 00:15:19 FS1 kernel: sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jul 23 00:15:19 FS1 kernel: sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 23 00:15:19 FS1 kernel: sdb: sdb1 Jul 23 00:15:19 FS1 kernel: sd 5:0:0:0: [sdb] Attached SCSI disk Jul 23 00:15:19 FS1 kernel: ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jul 23 00:15:19 FS1 kernel: ata6.00: ATA-8: WDC WD6400AAKS-65A7B2, 01.03B01, max UDMA/133 Jul 23 00:15:19 FS1 kernel: ata6.00: 1250263728 sectors, multi 16: LBA48 NCQ (depth 0/32) Jul 23 00:15:19 FS1 kernel: ata6.00: configured for UDMA/100 Jul 23 00:15:19 FS1 kernel: scsi 6:0:0:0: Direct-Access ATA WDC WD6400AAKS-6 01.0 PQ: 0 ANSI: 5 Jul 23 00:15:19 FS1 kernel: sd 6:0:0:0: [sdc] 1250263728 512-byte logical blocks: (640 GB/596 GiB) Jul 23 00:15:19 FS1 kernel: sd 6:0:0:0: [sdc] Write Protect is off Jul 23 00:15:19 FS1 kernel: sd 6:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Jul 23 00:15:19 FS1 kernel: sd 6:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 23 00:15:19 FS1 kernel: sdc: sdc1 Jul 23 00:15:19 FS1 kernel: sd 6:0:0:0: [sdc] Attached SCSI disk Jul 23 00:15:19 FS1 kernel: ata7: SATA link down (SStatus 0 SControl 310) Jul 23 00:15:19 FS1 kernel: ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jul 23 00:15:19 FS1 kernel: ata8.00: ATA-8: WDC WD6400AAKS-22A7B2, 01.03B01, max UDMA/133 Jul 23 00:15:19 FS1 kernel: ata8.00: 1250263728 sectors, multi 16: LBA48 NCQ (depth 0/32) Jul 23 00:15:19 FS1 kernel: ata8.00: configured for UDMA/100 Jul 23 00:15:19 FS1 kernel: scsi 8:0:0:0: Direct-Access ATA WDC WD6400AAKS-2 01.0 PQ: 0 ANSI: 5 Jul 23 00:15:19 FS1 kernel: sd 8:0:0:0: [sdd] 1250263728 512-byte logical blocks: (640 GB/596 GiB) Jul 23 00:15:19 FS1 kernel: sd 8:0:0:0: [sdd] Write Protect is off Jul 23 00:15:19 FS1 kernel: sd 8:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Jul 23 00:15:19 FS1 kernel: sd 8:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 23 00:15:19 FS1 kernel: sdd: sdd1 Jul 23 00:15:19 FS1 kernel: sd 8:0:0:0: [sdd] Attached SCSI disk Jul 23 00:15:19 FS1 kernel: scsi 0:0:0:0: Direct-Access CBM Flash Disk 5.00 PQ: 0 ANSI: 2 Jul 23 00:15:19 FS1 kernel: sd 0:0:0:0: [sde] 2035712 512-byte logical blocks: (1.04 GB/994 MiB) Jul 23 00:15:19 FS1 kernel: sd 0:0:0:0: [sde] Write Protect is off Jul 23 00:15:19 FS1 kernel: sd 0:0:0:0: [sde] Mode Sense: 0b 00 00 08 Jul 23 00:15:19 FS1 kernel: sd 0:0:0:0: [sde] Assuming drive cache: write through Jul 23 00:15:19 FS1 kernel: usb-storage: device scan complete Jul 23 00:15:19 FS1 kernel: sd 0:0:0:0: [sde] Assuming drive cache: write through Jul 23 00:15:19 FS1 kernel: sde: sde1 Jul 23 00:15:19 FS1 kernel: sd 0:0:0:0: [sde] Assuming drive cache: write through Jul 23 00:15:19 FS1 kernel: sd 0:0:0:0: [sde] Attached SCSI removable disk Jul 23 00:15:19 FS1 logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Jul 23 00:15:19 FS1 logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo Jul 23 00:15:19 FS1 ifplugd(eth0)[1264]: ifplugd 0.28 initializing. Jul 23 00:15:19 FS1 ifplugd(eth0)[1264]: Using interface eth0/00:01:29:FA:14:10 with driver (version: 0.64) Jul 23 00:15:19 FS1 ifplugd(eth0)[1264]: Using detection mode: SIOCETHTOOL Jul 23 00:15:19 FS1 ifplugd(eth0)[1264]: Initialization complete, link beat detected. Jul 23 00:15:19 FS1 ifplugd(eth0)[1264]: Executing '/etc/ifplugd/ifplugd.action eth0 up'. Jul 23 00:15:19 FS1 logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 hw ether 00:01:29:FA:14:10 Jul 23 00:15:19 FS1 logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 10.0.0.8 broadcast 10.0.0.255 netmask 255.255.255.0 Jul 23 00:15:19 FS1 logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 10.0.0.1 metric 1 Jul 23 00:15:19 FS1 ntpd[1303]: ntpd [email protected] Wed Jan 14 23:46:25 UTC 2009 (1) Jul 23 00:15:19 FS1 ifplugd(eth0)[1264]: client: Starting NTP daemon: /usr/sbin/ntpd -g Jul 23 00:15:19 FS1 ntpd[1304]: precision = 1.000 usec Jul 23 00:15:19 FS1 ntpd[1304]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Jul 23 00:15:19 FS1 ntpd[1304]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled Jul 23 00:15:19 FS1 ntpd[1304]: Listening on interface #1 lo, 127.0.0.1#123 Enabled Jul 23 00:15:19 FS1 ntpd[1304]: Listening on interface #2 eth0, 10.0.0.8#123 Enabled Jul 23 00:15:19 FS1 ntpd[1304]: kernel time sync status 0040 Jul 23 00:15:19 FS1 ifplugd(eth0)[1264]: Program executed successfully. Jul 23 00:15:19 FS1 rpc.statd[1318]: Version 1.1.4 Starting Jul 23 00:15:19 FS1 emhttp: unRAID System Management Utility version 4.5.6 Jul 23 00:15:19 FS1 emhttp: Copyright © 2005-2010, Lime Technology, LLC Jul 23 00:15:19 FS1 unmenu-status: Starting unmenu web-server Jul 23 00:15:19 FS1 emhttp: Pro key detected, GUID: 1E3D-6025-1422-4103246A1D03 Jul 23 00:15:19 FS1 emhttp: shcmd (1): udevadm settle Jul 23 00:15:19 FS1 emhttp: Device inventory: Jul 23 00:15:19 FS1 emhttp: pci-0000:00:09.0-scsi-0:0:0:0 host1 (sda) WDC_WD6400AAKS-65A7B2_WD-WCASYA413861 Jul 23 00:15:19 FS1 emhttp: pci-0000:02:09.0-scsi-0:0:0:0 host5 (sdb) WDC_WD6400AAKS-22A7B0_WD-WMASY4653206 Jul 23 00:15:19 FS1 emhttp: pci-0000:02:09.0-scsi-1:0:0:0 host6 (sdc) WDC_WD6400AAKS-65A7B2_WD-WCASYA411677 Jul 23 00:15:19 FS1 emhttp: pci-0000:02:09.0-scsi-3:0:0:0 host8 (sdd) WDC_WD6400AAKS-22A7B2_WD-WCASYA156940 Jul 23 00:15:19 FS1 emhttp: restart_md_driver: stat pci-0000:02:09.0-scsi-2:0:0:0: No such file or directory Jul 23 00:15:19 FS1 emhttp: shcmd (2): modprobe -rw md-mod 2>&1 | logger Jul 23 00:15:19 FS1 emhttp: shcmd (3): modprobe md-mod super=/boot/config/super.dat slots=8,0,8,16,8,32,8,48,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 2>&1 | logger Jul 23 00:15:19 FS1 kernel: xor: automatically using best checksumming function: pIII_sse Jul 23 00:15:19 FS1 kernel: pIII_sse : 6168.400 MB/sec Jul 23 00:15:19 FS1 kernel: xor: using function: pIII_sse (6168.400 MB/sec) Jul 23 00:15:19 FS1 emhttp: Spinning up all drives... Jul 23 00:15:19 FS1 kernel: md: unRAID driver 0.95.4 installed Jul 23 00:15:19 FS1 kernel: md: import disk0: [8,0] (sda) WDC WD6400AAKS-6 WD-WCASYA413861 offset: 63 size: 625131832 Jul 23 00:15:19 FS1 kernel: md: import disk1: [8,16] (sdb) WDC WD6400AAKS-2 WD-WMASY4653206 offset: 63 size: 625131832 Jul 23 00:15:19 FS1 kernel: md: import disk2: [8,32] (sdc) WDC WD6400AAKS-6 WD-WCASYA411677 offset: 63 size: 625131832 Jul 23 00:15:19 FS1 kernel: md: import disk3: [8,48] (sdd) WDC WD6400AAKS-2 WD-WCASYA156940 offset: 63 size: 625131832 Jul 23 00:15:19 FS1 kernel: md: disk4 missing Jul 23 00:15:19 FS1 kernel: mdcmd (2): set md_num_stripes 1280 Jul 23 00:15:19 FS1 kernel: mdcmd (3): set md_write_limit 768 Jul 23 00:15:19 FS1 kernel: mdcmd (4): set md_sync_window 288 Jul 23 00:15:19 FS1 kernel: mdcmd (5): set spinup_group 0 0 Jul 23 00:15:19 FS1 kernel: mdcmd (6): set spinup_group 1 0 Jul 23 00:15:19 FS1 kernel: mdcmd (7): set spinup_group 2 0 Jul 23 00:15:19 FS1 kernel: mdcmd (: set spinup_group 3 0 Jul 23 00:15:19 FS1 kernel: mdcmd (9): spinup 0 Jul 23 00:15:19 FS1 kernel: mdcmd (10): spinup 1 Jul 23 00:15:19 FS1 kernel: mdcmd (11): spinup 2 Jul 23 00:15:19 FS1 kernel: mdcmd (12): spinup 3 Jul 23 00:15:19 FS1 emhttp: stale configuration Jul 23 00:15:19 FS1 emhttp: shcmd (4): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Jul 23 00:15:19 FS1 emhttp: _shcmd: shcmd (4): exit status: 1 Jul 23 00:15:19 FS1 emhttp: shcmd (5): cp /etc/exports- /etc/exports Jul 23 00:15:19 FS1 emhttp: shcmd (6): killall -HUP smbd Jul 23 00:15:19 FS1 emhttp: shcmd (7): /etc/rc.d/rc.nfsd restart | logger Jul 23 00:15:20 FS1 emhttp: shcmd (7): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root Jul 23 00:15:20 FS1 emhttp: shcmd (: echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root Jul 23 00:15:20 FS1 emhttp: shcmd (9): echo '40 3 * * * /usr/local/sbin/mover 2>&1 | logger' >>/var/spool/cron/crontabs/root Jul 23 00:15:20 FS1 emhttp: shcmd (10): crontab /var/spool/cron/crontabs/root Jul 23 00:15:28 FS1 ntpd[1304]: synchronized to 174.143.207.151, stratum 3 Jul 23 00:21:45 FS1 emhttp: shcmd (12): modprobe -rw md-mod 2>&1 | logger Jul 23 00:21:45 FS1 emhttp: shcmd (13): modprobe md-mod super=/boot/config/super.dat slots=8,0,8,16,8,32,8,48,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 2>&1 | logger Jul 23 00:21:45 FS1 kernel: md: unRAID driver removed Jul 23 00:21:45 FS1 kernel: xor: automatically using best checksumming function: pIII_sse Jul 23 00:21:45 FS1 kernel: pIII_sse : 6162.400 MB/sec Jul 23 00:21:45 FS1 kernel: xor: using function: pIII_sse (6162.400 MB/sec) Jul 23 00:21:45 FS1 kernel: md: unRAID driver 0.95.4 installed Jul 23 00:21:45 FS1 kernel: md: import disk0: [8,0] (sda) WDC WD6400AAKS-6 WD-WCASYA413861 offset: 63 size: 625131832 Jul 23 00:21:45 FS1 kernel: md: import disk1: [8,16] (sdb) WDC WD6400AAKS-2 WD-WMASY4653206 offset: 63 size: 625131832 Jul 23 00:21:45 FS1 kernel: md: import disk2: [8,32] (sdc) WDC WD6400AAKS-6 WD-WCASYA411677 offset: 63 size: 625131832 Jul 23 00:21:45 FS1 kernel: md: import disk3: [8,48] (sdd) WDC WD6400AAKS-2 WD-WCASYA156940 offset: 63 size: 625131832 Jul 23 00:21:45 FS1 kernel: md: disk4 missing Jul 23 00:21:45 FS1 kernel: mdcmd (2): set md_num_stripes 1280 Jul 23 00:21:45 FS1 kernel: mdcmd (3): set md_write_limit 768 Jul 23 00:21:45 FS1 kernel: mdcmd (4): set md_sync_window 288 Jul 23 00:21:45 FS1 kernel: mdcmd (5): set spinup_group 0 0 Jul 23 00:21:45 FS1 kernel: mdcmd (6): set spinup_group 1 0 Jul 23 00:21:45 FS1 kernel: mdcmd (7): set spinup_group 2 0 Jul 23 00:21:45 FS1 kernel: mdcmd (: set spinup_group 3 0 Jul 23 00:22:08 FS1 in.telnetd[1636]: connect from 10.0.0.157 (10.0.0.157) Jul 23 00:22:11 FS1 login[1637]: ROOT LOGIN on `pts/0' from `10.0.0.157' Jul 23 00:25:11 FS1 emhttp: shcmd (14): modprobe -rw md-mod 2>&1 | logger Jul 23 00:25:11 FS1 emhttp: shcmd (15): modprobe md-mod super=/boot/config/super.dat slots=8,0,8,16,8,32,8,48,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 2>&1 | logger Jul 23 00:25:11 FS1 kernel: md: unRAID driver removed Jul 23 00:25:11 FS1 kernel: xor: automatically using best checksumming function: pIII_sse Jul 23 00:25:11 FS1 kernel: pIII_sse : 6162.400 MB/sec Jul 23 00:25:11 FS1 kernel: xor: using function: pIII_sse (6162.400 MB/sec) Jul 23 00:25:11 FS1 kernel: md: unRAID driver 0.95.4 installed Jul 23 00:25:11 FS1 kernel: read_file: error 2 opening /boot/config/super.dat Jul 23 00:25:11 FS1 kernel: md: could not read superblock from /boot/config/super.dat Jul 23 00:25:11 FS1 kernel: md: initializing superblock Jul 23 00:25:11 FS1 kernel: md: import disk0: [8,0] (sda) WDC WD6400AAKS-6 WD-WCASYA413861 offset: 63 size: 625131832 Jul 23 00:25:11 FS1 kernel: md: disk0 new disk Jul 23 00:25:11 FS1 kernel: md: import disk1: [8,16] (sdb) WDC WD6400AAKS-2 WD-WMASY4653206 offset: 63 size: 625131832 Jul 23 00:25:11 FS1 kernel: md: disk1 new disk Jul 23 00:25:11 FS1 kernel: md: import disk2: [8,32] (sdc) WDC WD6400AAKS-6 WD-WCASYA411677 offset: 63 size: 625131832 Jul 23 00:25:11 FS1 kernel: md: disk2 new disk Jul 23 00:25:11 FS1 kernel: md: import disk3: [8,48] (sdd) WDC WD6400AAKS-2 WD-WCASYA156940 offset: 63 size: 625131832 Jul 23 00:25:11 FS1 kernel: md: disk3 new disk Jul 23 00:25:11 FS1 kernel: mdcmd (2): set md_num_stripes 1280 Jul 23 00:25:11 FS1 kernel: mdcmd (3): set md_write_limit 768 Jul 23 00:25:11 FS1 kernel: mdcmd (4): set md_sync_window 288 Jul 23 00:25:11 FS1 kernel: mdcmd (5): set spinup_group 0 0 Jul 23 00:25:11 FS1 kernel: mdcmd (6): set spinup_group 1 0 Jul 23 00:25:11 FS1 kernel: mdcmd (7): set spinup_group 2 0 Jul 23 00:25:11 FS1 kernel: mdcmd (: set spinup_group 3 0 Jul 23 00:25:22 FS1 emhttp: shcmd (16): /usr/local/sbin/set_ncq sda 1 >/dev/null Jul 23 00:25:22 FS1 emhttp: shcmd (17): /usr/local/sbin/set_ncq sdb 1 >/dev/null Jul 23 00:25:22 FS1 emhttp: shcmd (18): /usr/local/sbin/set_ncq sdc 1 >/dev/null Jul 23 00:25:22 FS1 emhttp: shcmd (19): /usr/local/sbin/set_ncq sdd 1 >/dev/null Jul 23 00:25:22 FS1 emhttp: writing mbr on disk 1 (/dev/sdb) Jul 23 00:25:22 FS1 emhttp: re-reading /dev/sdb partition table Jul 23 00:25:22 FS1 kernel: sdb: sdb1 Jul 23 00:25:23 FS1 kernel: mdcmd (12): start NEW_ARRAY Jul 23 00:25:23 FS1 kernel: unraid: allocating 23480K for 1280 stripes (4 disks) Jul 23 00:25:23 FS1 kernel: md1: running, size: 625131832 blocks Jul 23 00:25:23 FS1 kernel: md2: running, size: 625131832 blocks Jul 23 00:25:23 FS1 kernel: md3: running, size: 625131832 blocks Jul 23 00:25:24 FS1 emhttp: shcmd (20): udevadm settle Jul 23 00:25:24 FS1 emhttp: shcmd (21): mkdir /mnt/disk3 Jul 23 00:25:24 FS1 emhttp: shcmd (21): mkdir /mnt/disk2 Jul 23 00:25:24 FS1 emhttp: shcmd (21): mkdir /mnt/disk1 Jul 23 00:25:24 FS1 emhttp: shcmd (22): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md3 /mnt/disk3 2>&1 | logger Jul 23 00:25:24 FS1 emhttp: shcmd (23): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md2 /mnt/disk2 2>&1 | logger Jul 23 00:25:24 FS1 kernel: mdcmd (14): check Jul 23 00:25:24 FS1 kernel: md: recovery thread woken up ... Jul 23 00:25:24 FS1 kernel: md: recovery thread syncing parity disk ... Jul 23 00:25:24 FS1 kernel: md: using 1152k window, over a total of 625131832 blocks. Jul 23 00:25:24 FS1 emhttp: shcmd (24): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1 2>&1 | logger Jul 23 00:25:24 FS1 kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal Jul 23 00:25:24 FS1 kernel: REISERFS (device md1): using ordered data mode Jul 23 00:25:24 FS1 kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal Jul 23 00:25:24 FS1 kernel: REISERFS (device md3): using ordered data mode Jul 23 00:25:24 FS1 kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal Jul 23 00:25:24 FS1 kernel: REISERFS (device md2): using ordered data mode Jul 23 00:25:24 FS1 kernel: REISERFS (device 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 Jul 23 00:25:24 FS1 kernel: REISERFS (device md3): checking transaction log (md3) Jul 23 00:25:24 FS1 kernel: REISERFS (device 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 Jul 23 00:25:24 FS1 kernel: REISERFS (device md2): checking transaction log (md2) Jul 23 00:25:24 FS1 kernel: REISERFS (device 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 Jul 23 00:25:24 FS1 kernel: REISERFS (device md1): checking transaction log (md1) Jul 23 00:25:56 FS1 kernel: REISERFS (device md3): replayed 51 transactions in 32 seconds Jul 23 00:25:56 FS1 kernel: REISERFS (device md3): Using r5 hash to sort names Jul 23 00:27:25 FS1 kernel: REISERFS (device md2): replayed 231 transactions in 121 seconds Jul 23 00:27:25 FS1 kernel: REISERFS (device md2): Using r5 hash to sort names Jul 23 00:27:28 FS1 kernel: REISERFS (device md1): replayed 252 transactions in 124 seconds Jul 23 00:27:28 FS1 kernel: REISERFS (device md1): Using r5 hash to sort names Jul 23 00:27:29 FS1 emhttp: shcmd (27): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Jul 23 00:27:29 FS1 emhttp: shcmd (28): cp /etc/exports- /etc/exports Jul 23 00:27:29 FS1 emhttp: shcmd (29): mkdir /mnt/user Jul 23 00:27:29 FS1 emhttp: shcmd (30): /usr/local/sbin/shfs /mnt/user -o noatime,big_writes,allow_other,default_permissions Jul 23 00:27:30 FS1 emhttp: shcmd (31): killall -HUP smbd Jul 23 00:27:30 FS1 emhttp: shcmd (32): /etc/rc.d/rc.nfsd restart | logger
July 23, 201015 yr What does an overnight Memtest say? How long did you let memtest run when you say it said no errors?
July 23, 201015 yr Author What does an overnight Memtest say? How long did you let memtest run when you say it said no errors? I just let it run for few hours, didn't run overnight. But anyways.. this is rather interesting. switched disk1 to disk4 and did some file copy testing using both cp and samba simultaneous. And the server had yet to crash. Perhaps there is some bug with unraid ?
July 23, 201015 yr Perhaps there is some bug with unraid ? No, if there was some bug in unRAID everyone would be complaining about the issue. There is something weird with your setup that was/is causing problems.
July 23, 201015 yr Author Perhaps there is some bug with unraid ? No, if there was some bug in unRAID everyone would be complaining about the issue. There is something weird with your setup that was/is causing problems. Was able to fill the disk4 without crashing. So something definitely not right with unraid. Nothing else was changed other than the disk number. Unless something else suggest otherwise. I'm gonna say this is a bug.
July 23, 201015 yr I just let it run for few hours, didn't run overnight. But anyways.. this is rather interesting. switched disk1 to disk4 and did some file copy testing using both cp and samba simultaneous. And the server had yet to crash. When you say you switched disk 1 to disk 4 what exactly did you do?. Did you just unassign it on the devices page and then assign it to the disk 4 slot? Was able to fill the disk4 without crashing. So something definitely not right with unraid. Nothing else was changed other than the disk number. Unless something else suggest otherwise. I'm gonna say this is a bug. I did notice that you are using an nf3 board. There are known data corruption issues with the nforce board from version 4 on back. I can say with quite a bit of confidence that this is NOT an unRAID bug. It would have been complained about over and over and over again if it existed. If i had to guess at a cause i would point to the SATA controller you have the drives hooked up to and possibly an intermittent/weak connection. Are you using locking SATA cables? Why are some drives hook to the onboard SATA and others not? Another syslog may help to find something (just copy to a text file and upload it here).
July 23, 201015 yr Author When you say you switched disk 1 to disk 4 what exactly did you do?. Did you just unassign it on the devices page and then assign it to the disk 4 slot? I rebuilt the array with initconfig and assigned the hdd that was at disk1 to disk4. I did notice that you are using an nf3 board. There are known data corruption issues with the nforce board from version 4 on back. I can say with quite a bit of confidence that this is NOT an unRAID bug. It would have been complained about over and over and over again if it existed. If i had to guess at a cause i would point to the SATA controller you have the drives hooked up to and possibly an intermittent/weak connection. Are you using locking SATA cables? Why are some drives hook to the onboard SATA and others not? Another syslog may help to find something (just copy to a text file and upload it here). You can point and say there is a hardware issue with my hardware if you want. The bottom line is I have tried two different harddrives, in two different slots on the same sata card with two different cable. Yet, the results are the same when they are in the disk1 slot. Now that I have switched the same hdd using the same cable in the same slot that was crashing the server earlier to disk4 slot, and the server instantly become stable? The only thing in my original syslog that looked suspicous is this. Jul 23 00:25:11 FS1 kernel: md: unRAID driver 0.95.4 installed Jul 23 00:25:11 FS1 kernel: read_file: error 2 opening /boot/config/super.dat Jul 23 00:25:11 FS1 kernel: md: could not read superblock from /boot/config/super.dat Jul 23 00:25:11 FS1 kernel: md: initializing superblock Whether this could cause unraid to crash when data is being written to disk1 slot... That's up to the dev to investigate. Again, this only happens to disk1 slot. Disk2,3,4 are completely fine. P.S. - Just because something that isn't complained over and over, it doesn't mean it is not a bug or could be a bug. Even if I'm the only person in the world that experience this problem. It is still a bug. You are making it sound like unraid is 100% perfect and it doesn't contain any bugs.
July 23, 201015 yr When you type "initconfig" the unRAID software renames config/super.dat to config/super.old Therefore, when you subsequently start the array is is expected the config/super.dat is unable to be read (it does not exist) The errors in the syslog are expected at that point. When the config/super.dat file is missing the unRAID software then re-creates a new config/super.dat file based on the currently assigned and working disks. The super.dat file holds the model/serial number of each of your disks, the sizes of them, their status, and the current parity status. When you type initiconfig and subsequently start the array, after it then re-creates super.dat, it will then have a full parity calc initiated. It, when complete, will write the successful parity completion status to the config/super.dat file. I'll repeat what prostuff1 had said. It is likely you have a hardware issue. It might have caused file-system corruption on one of your disks. I have seen a corrupt file-system crash a server. You might try checking each of your disk as described in the wiki here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems It is possible in writing and re-writing the files to your disks the corruption fixed itself (perhaps you deleted the file with the corruption) Also, if you are using an early Nforce chipset based MB, you will not be the first to discover they cause random errors when used with multiple disks. (translation... they cause "hair-loss" because you'll be pulling out your hair trying to find the cause of random errors) You'll know, because you get random parity errors at times. I strongly suggest you run multiple parity checks in NOCORRECT mode by typing: /root/mdcmd check NOCORRECT Otherwise, a read of bad data from a data disk will result in having parity updated to match the incorrect value read. The NOCORRECT option will detect the errors, but not overwrite parity with bad data. Good luck. Keep an eye out for an alternate motherboard, at least consider a swap at some point... It may save you from having a hair-style like mine. Joe L.
July 23, 201015 yr Author When you type "initconfig" the unRAID software renames config/super.dat to config/super.old Therefore, when you subsequently start the array is is expected the config/super.dat is unable to be read (it does not exist) the unRAID software then re-creates a new config/super.dat file based on the currently assigned and working disks. The super.dat file holds the model/serial number of each of your disks, the sizes of them, their status, and the current parity status. when you type initiconfig to force the re-creation of super.dat, you will then have a full parity calc initiated when you next start the array. It, when complete, will write the successful parity completion status to the config/super.dat file. I'll repeat what the other user had said. It is likely you have a hardware issue. It might have been caused file-system corruption on one of your disks. I have seen a corrupt file-system crash a server. You might try checking each of them as described in the wiki here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems Also, if you are using an early Nforce chipset based MB, you will not be the first to discover they cause random errors when used with multiple disks. (translation... they cause "hair-loss" because you'll be pulling out your hair trying to find the cause of random errors) Good luck. Keep an eye out for an alternate motherboard, at least consider a swap at some point... It may save you from having a hair-style like mine. Joe L. No, that syslog is before I ran initconfig and reassigned disk1 to disk4. You failed to see the bottom line. Same harddrives with same MBR, FS, data on it and it is not crashing the server... If it's really my hardware, then regardless of the disk slot swap. I will still be getting crashes when moving data over, but ever since the disk slot swap, no more crashing
July 23, 201015 yr No, that syslog is before I ran initconfig and reassigned disk1 to disk4. We understand that, but running initconfig did in fact tell unRAID to forget everything it knew about your setup and start as if it were new. You failed to see the bottom line. Same harddrives with same MBR, FS, data on it and it is not crashing the server... The same FS might in fact be the problem. Run a FS check on your system to see if it pops anything up. If it's really my hardware, then regardless of the disk slot swap. I will still be getting crashes when moving data over, but ever since the disk slot swap, no more crashing Yup, and that is the reason harware issues are so hard to find and fix. What you did may have solved the problem you were seeing but it in no way fixed the problem. It may have masked it... but that is probably all it did. Run the FS check, the memtest, and try moving all the disks to the MB controller and off the card (if you can). The more parts of the system you can remove/isolate the better chance you have of finding the problem.
July 23, 201015 yr Author Yup, and that is the reason harware issues are so hard to find and fix. What you did may have solved the problem you were seeing but it in no way fixed the problem. It may have masked it... but that is probably all it did. Run the FS check, the memtest, and try moving all the disks to the MB controller and off the card (if you can). The more parts of the system you can remove/isolate the better chance you have of finding the problem. I've just done two tests to fill the same hdd that was causing the issue. Still didn't crash. Like I said before, the hdd's were left at the same state as before the slot arrangement. So if it was really a FS issue, the problem will be apparent. Why would I need to move my hdds to the mb controller? Jeesus... I really don't understand this "unraid doesn't have bugs" mentality from you guys. First one guy said the mobo's chipset is known for its problems. Now you are saying the sata card could be causing issues. But hey... I did one logical (software) arrangement and the problem went away instantly. So I just rebooted the server and currently doing my 3rd fill test. If its an hardware issue, something is bound to happen soon... Attached a new syslog after reboot for those who are interested. unraid.txt
July 23, 201015 yr I've just done two tests to fill the same hdd that was causing the issue. Still didn't crash. Like I said before, the hdd's were left at the same state as before the slot arrangement. So if it was really a FS issue, the problem will be apparent. Now, if you could move that disk back to slot one it would be an interesting test. Why would I need to move my hdds to the mb controller? Jeesus... I really don't understand this "unraid doesn't have bugs" mentality from you guys. It's not that unRAID does not have bugs, we know it does, but what you are describing and the "fix" that you preformed makes no sense what so ever. A disk in one slot is no different then a disk in another slot. First one guy said the mobo's chipset is known for its problems. Now you are saying the sata card could be causing issues. But hey... I did one logical (software) arrangement and the problem went away instantly. Your "logical (software) arrangement" makes no sense what so ever. The initconfig command may fixed your problem. So I just rebooted the server and currently doing my 3rd fill test. If its an hardware issue, something is bound to happen soon... Attached a new syslog after reboot for those who are interested. It would have been nice to have the syslog before you rebooted the server.
July 23, 201015 yr Author Now, if you could move that disk back to slot one it would be an interesting test. Not interested in wasting another day on this matter tbh... Already wasted the last 3 days on this. Maybe when I decide to add another disk to the array. It's not that unRAID does not have bugs, we know it does, but what you are describing and the "fix" that you preformed makes no sense what so ever. A disk in one slot is no different then a disk in another slot. It may not make sense to you but it definitely make sense to me (IF there is a bug). Your idea of moving the hdd's to the mobo slots to test make no sense whatsoever to me... Vise versa Your "logical (software) arrangement" makes no sense what so ever. The initconfig command may fixed your problem. So if initconfig fixed the problem, isn't that suggesting it is something on the software side and not hardware ? It would have been nice to have the syslog before you rebooted the server. That is the syslog before the reboot in the first post.
July 23, 201015 yr So if initconfig fixed the problem, isn't that suggesting it is something on the software side and not hardware ? The problem stems from the fact that you could not write/read the super.dat file. The initconfig command creates a new one, as mentioned earlier by JoeL. Since a new super.dat was created by running initconfig and you can now write to it you "fixed" your problem. NOW, the only reason for the super.dat file to not be readable is because of a HARDWARE problem. Your flash drive may have developed a bad spot and caused the problem, i do not know. This problem has acutally happened once to me but i keep regular backups of my flash drive and was able to stop the array, replace the super.dat file, and start up no problem. You could always pull the flash drive out quick and run checkdisk on it from a windows machine.
July 23, 201015 yr Author So if initconfig fixed the problem, isn't that suggesting it is something on the software side and not hardware ? The problem stems from the fact that you could not write/read the super.dat file. The initconfig command creates a new one, as mentioned earlier by JoeL. Since a new super.dat was created by running initconfig and you can now write to it you "fixed" your problem. NOW, the only reason for the super.dat file to not be readable is because of a HARDWARE problem. Your flash drive may have developed a bad spot and caused the problem, i do not know. This problem has acutally happened once to me but i keep regular backups of my flash drive and was able to stop the array, replace the super.dat file, and start up no problem. You could always pull the flash drive out quick and run checkdisk on it from a windows machine. HAHAHA please stop. It is not a hardware problem. First it is my chipset, next is the sata card now it is my flash drive. What's next? My video card ? CPU ? I've never seen somebody that blindly defend a problem like you guys. I guess you can keep blaming my HARDWARE as long as nobody else run into this bug.
July 24, 201015 yr HAHAHA please stop. It is not a hardware problem. First it is my chipset, next is the sata card now it is my flash drive. What's next? My video card ? CPU ? I've never seen somebody that blindly defend a problem like you guys. I guess you can keep blaming my HARDWARE as long as nobody else run into this bug. Consider this ... How many people are using unRAID? How many of those have a disk1 in their configuration? How many people are experiencing (reporting?) this problem with disk1? What is the significant difference between the two groups of users (those with the problem - just you?, and those without the problem - several thousand)? Reading this thread has just made me realise why I had a problem, many years ago, with a Win2k system - I was using an Epox mobo with NVidia chipset. I battled this for many months, with random crashes that I could never tie down. I tried swapping various pieces of the hardware, even replacing the mobo with an identical unit, but the problems continued. However, since the day I rebuilt the system around an ASUS mobo (with a later NVidia chipset), it has been problem free!
July 24, 201015 yr I've had nothing but trouble with Nvidia chipsets under Win2K and WinXP. It wouldn't surprised me some of the issues also carry over to Linux. I've also never seen one so adamant that their entire and complete set of hardware is flawless. If you keep that attitude up, you're likely to never receive help in the future and be bound to troubleshoot things yourself.
Archived
This topic is now archived and is closed to further replies.