NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Fri Apr 19, 2024 9:17 am

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 26 posts ]  Go to page 1, 2  Next
Author Message
 Post subject: Abnormalities in Syslog
PostPosted: Thu May 06, 2010 1:14 am 
Offline

Joined: Sat Mar 03, 2007 6:25 pm
Posts: 294
Location: Delft NL / Brooklyn NY
Would you mind taking a look at this syslog? The APIC section seems weird, so is the end where there's a warning for the hda.

A few days ago the RAID array got corrupted, without a reason. Drives are OK, 3Ware 8006-2LP is functioning well.
Is there an issue with the motherboard, the processor?

NAS is on 24/7

Thanks a lot!

* May 6 07:51:03 [3] klogd started: BusyBox v1.12.1 (2009-11-19 21:21:30 UTC)
* May 6 07:51:03 [3] Linux version 2.6.30.3.CORE3 (root@DevBox) (gcc version 4.1.2 (SE 4.1.2 p1.0.2)) #1 Mon Jan 25 02:33:02 UTC 2010
* May 6 07:51:03 [2] KERNEL supported cpus:
* May 6 07:51:03 [2] Intel GenuineIntel
* May 6 07:51:03 [2] AMD AuthenticAMD
* May 6 07:51:03 [2] NSC Geode by NSC
* May 6 07:51:03 [2] Cyrix CyrixInstead
* May 6 07:51:03 [2] Centaur CentaurHauls
* May 6 07:51:03 [2] Transmeta GenuineTMx86
* May 6 07:51:03 [2] Transmeta TransmetaCPU
* May 6 07:51:03 [2] UMC UMC UMC UMC
* May 6 07:51:03 [2] BIOS-provided physical RAM map:
* May 6 07:51:03 [2] BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
* May 6 07:51:03 [2] BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
* May 6 07:51:03 [2] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
* May 6 07:51:03 [2] BIOS-e820: 0000000000100000 - 000000000fffc000 (usable)
* May 6 07:51:03 [2] BIOS-e820: 000000000fffc000 - 000000000ffff000 (ACPI data)
* May 6 07:51:03 [2] BIOS-e820: 000000000ffff000 - 0000000010000000 (ACPI NVS)
* May 6 07:51:03 [2] BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
* May 6 07:51:03 [2] DMI 2.3 present.
* May 6 07:51:03 [2] last_pfn = 0xfffc max_arch_pfn = 0x100000
* May 6 07:51:03 [2] init_memory_mapping: 0000000000000000-000000000fffc000
* May 6 07:51:03 [1] 0000000000 - 0000400000 page 4k
* May 6 07:51:03 [1] 0000400000 - 000fc00000 page 2M
* May 6 07:51:03 [1] 000fc00000 - 000fffc000 page 4k
* May 6 07:51:03 [1] kernel direct mapping tables up to fffc000 @ 7000-c000
* May 6 07:51:03 [2] RAMDISK: 0f91f000 - 0fffa0d2
* May 6 07:51:03 [4] ACPI: RSDP 000f6da0 00014 (v00 ASUS )
* May 6 07:51:03 [4] ACPI: RSDT 0fffc000 0002C (v01 ASUS CUV4X_C 30303031 MSFT 31313031)
* May 6 07:51:03 [4] ACPI: FACP 0fffc080 00074 (v01 ASUS CUV4X_C 30303031 MSFT 31313031)
* May 6 07:51:03 [4] ACPI: DSDT 0fffc100 0285A (v01 ASUS CUV4X_C 00001000 MSFT 0100000B)
* May 6 07:51:03 [4] ACPI: FACS 0ffff000 00040
* May 6 07:51:03 [4] ACPI: BOOT 0fffc040 00028 (v01 ASUS CUV4X_C 30303031 MSFT 31313031)
* May 6 07:51:03 [3] 0MB HIGHMEM available.
* May 6 07:51:03 [3] 255MB LOWMEM available.
* May 6 07:51:03 [2] mapped low ram: 0 - 0fffc000
* May 6 07:51:03 [2] low ram: 0 - 0fffc000
* May 6 07:51:03 [2] node 0 low ram: 00000000 - 0fffc000
* May 6 07:51:03 [2] node 0 bootmap 00001000 - 00003000
* May 6 07:51:03 [2] (7 early reservations) ==> bootmem [0000000000 - 000fffc000]
* May 6 07:51:03 [2] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
* May 6 07:51:03 [2] #1 [0000100000 - 000039b83c] TEXT DATA BSS ==> [0000100000 - 000039b83c]
* May 6 07:51:03 [2] #2 [000f91f000 - 000fffa0d2] RAMDISK ==> [000f91f000 - 000fffa0d2]
* May 6 07:51:03 [2] #3 [000009f400 - 0000100000] BIOS reserved ==> [000009f400 - 0000100000]
* May 6 07:51:03 [2] #4 [000039c000 - 000039e154] BRK ==> [000039c000 - 000039e154]
* May 6 07:51:03 [2] #5 [0000007000 - 0000008000] PGTABLE ==> [0000007000 - 0000008000]
* May 6 07:51:03 [2] #6 [0000001000 - 0000003000] BOOTMAP ==> [0000001000 - 0000003000]
* May 6 07:51:03 [4] Zone PFN ranges:
* May 6 07:51:03 [4] DMA 0x00000000 -> 0x00001000
* May 6 07:51:03 [4] Normal 0x00001000 -> 0x0000fffc
* May 6 07:51:03 [4] HighMem 0x0000fffc -> 0x0000fffc
* May 6 07:51:03 [4] Movable zone start PFN for each node
* May 6 07:51:03 [4] early_node_map[2] active PFN ranges
* May 6 07:51:03 [4] 0: 0x00000000 -> 0x0000009f
* May 6 07:51:03 [4] 0: 0x00000100 -> 0x0000fffc
* May 6 07:51:03 [1] On node 0 totalpages: 65435
* May 6 07:51:03 [1] free_area_init_node: node 0, pgdat c031d560, node_mem_map c1000000
* May 6 07:51:03 [1] DMA zone: 32 pages used for memmap
* May 6 07:51:03 [1] DMA zone: 0 pages reserved
* May 6 07:51:03 [1] DMA zone: 3967 pages, LIFO batch:0
* May 6 07:51:03 [1] Normal zone: 480 pages used for memmap
* May 6 07:51:03 [1] Normal zone: 60956 pages, LIFO batch:15
* May 6 07:51:03 [2] Using APIC driver default
* May 6 07:51:03 [2] ACPI: PM-Timer IO Port: 0xe408
* May 6 07:51:03 [2] Local APIC disabled by BIOS -- you can enable it with "lapic"
* May 6 07:51:03 [1] nr_irqs_gsi: 16
* May 6 07:51:03 [2] Allocating PCI resources starting at 20000000 (gap: 10000000:efff0000)
* May 6 07:51:03 [4] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 64923
* May 6 07:51:03 [3] Kernel command line: rw root=/dev/ram0 initrd=NASLite.02 quiet BOOT_IMAGE=NASLite.01
* May 6 07:51:03 [2] Enabling fast FPU save and restore. done.
* May 6 07:51:03 [2] Enabling unmasked SIMD FPU exception support. done.
* May 6 07:51:03 [2] Initializing CPU#0
* May 6 07:51:03 [2] NR_IRQS:288
* May 6 07:51:03 [4] PID hash table entries: 1024 (order: 10, 4096 bytes)
* May 6 07:51:03 [4] Fast TSC calibration using PIT
* May 6 07:51:03 [4] Detected 534.512 MHz processor.
* May 6 07:51:03 [4] Console: colour VGA+ 80x25
* May 6 07:51:03 [2] console [tty0] enabled
* May 6 07:51:03 [2] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
* May 6 07:51:03 [2] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
* May 6 07:51:03 [2] Initializing HighMem for node 0 (00000000:00000000)
* May 6 07:51:03 [2] Memory: 249588k/262128k available (1523k kernel code, 11976k reserved, 667k data, 208k init, 0k highmem)
* May 6 07:51:03 [2] virtual kernel memory layout:
* May 6 07:51:03 [2] fixmap : 0xfffa9000 - 0xfffff000 ( 344 kB)
* May 6 07:51:03 [2] pkmap : 0xff800000 - 0xffc00000 (4096 kB)
* May 6 07:51:03 [2] vmalloc : 0xd07fc000 - 0xff7fe000 ( 75
* May 6 07:51:03 [2] 2 MB)
* May 6 07:51:03 [2] lowmem : 0xc0000000 - 0xcfffc000 ( 255 MB)
* May 6 07:51:03 [2] .init : 0xc0326000 - 0xc035a000 ( 208 kB)
* May 6 07:51:03 [2] .data : 0xc027cfdb - 0xc0323e14 ( 667 kB)
* May 6 07:51:03 [2] .text : 0xc0100000 - 0xc027cfdb (1523 kB)
* May 6 07:51:03 [2] Checking if this processor honours the WP bit even in supervisor mode.Ok.
* May 6 07:51:03 [2] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
* May 6 07:51:03 [2] Calibrating delay loop (skipped), value calculated using timer frequency 1069.02 BogoMIPS (lpj=2138048)
* May 6 07:51:03 [4] Mount-cache hash table entries: 512
* May 6 07:51:03 [2] CPU: L1 I cache: 16K, L1 D cache: 16K
* May 6 07:51:03 [2] CPU: L2 cache: 128K
* May 6 07:51:03 [4] CPU: Intel Celeron (Coppermine) stepping 06
* May 6 07:51:03 [2] Checking 'hlt' instruction. OK.
* May 6 07:51:03 [2] ACPI: Core revision 20090320
* May 6 07:51:03 [4] ACPI: setting ELCR to 0200 (from 0c10)
* May 6 07:51:03 [2] net_namespace: 296 bytes
* May 6 07:51:03 [2] NET: Registered protocol family 16
* May 6 07:51:03 [2] ACPI: bus type pci registered
* May 6 07:51:03 [2] PCI: PCI BIOS revision 2.10 entry at 0xf0d10, last bus=1
* May 6 07:51:03 [2] PCI: Using configuration type 1 for base access
* May 6 07:51:03 [4] bio: create slab at 0
* May 6 07:51:03 [1] ACPI: EC: Look up EC in DSDT
* May 6 07:51:03 [2] ACPI: Interpreter enabled
* May 6 07:51:03 [2] ACPI: (supports S0 S5)
* May 6 07:51:03 [2] ACPI: Using PIC for interrupt routing
* May 6 07:51:03 [2] ACPI: No dock devices found.
* May 6 07:51:03 [2] ACPI: PCI Root Bridge [PCI0] (0000:00)
* May 6 07:51:03 [1] pci 0000:00:00.0: reg 10 32bit mmio: [0xfc000000-0xfdffffff]
* May 6 07:51:03 [1] pci 0000:00:01.0: supports D1
* May 6 07:51:03 [1] pci 0000:00:04.1: reg 20 io port: [0xb800-0xb80f]
* May 6 07:51:03 [1] pci 0000:00:04.2: reg 20 io port: [0xb400-0xb41f]
* May 6 07:51:03 [1] pci 0000:00:04.3: reg 20 io port: [0xb000-0xb01f]
* May 6 07:51:03 [2] pci 0000:00:04.4: quirk: region e400-e4ff claimed by vt82c586 ACPI
* May 6 07:51:03 [2] pci 0000:00:04.4: quirk: region e800-e80f claimed by vt82c686 SMB
* May 6 07:51:03 [1] pci 0000:00:07.0: reg 10 io port: [0xa800-0xa80f]
* May 6 07:51:03 [1] pci 0000:00:07.0: reg 14 32bit mmio: [0xde000000-0xde00000f]
* May 6 07:51:03 [1] pci 0000:00:07.0: reg 18 32bit mmio: [0xdd800000-0xddffffff]
* May 6 07:51:03 [1] pci 0000:00:07.0: reg 30 32bit mmio: [0x000000-0x00ffff]
* May 6 07:51:03 [1] pci 0000:00:07.0: supports D1
* May 6 07:51:03 [1] pci 0000:00:08.0: reg 10 io port: [0xa400-0xa4ff]
* May 6 07:51:03 [1] pci 0000:00:08.0: reg 14 32bit mmio: [0xdd000000-0xdd0000ff]
* May 6 07:51:03 [1] pci 0000:00:08.0: supports D1 D2
* May 6 07:51:03 [2] pci 0000:00:08.0: PME# supported from D1 D2 D3hot D3cold
* May 6 07:51:03 [2] pci 0000:00:08.0: PME# disabled
* May 6 07:51:03 [1] pci 0000:01:00.0: reg 10 32bit mmio: [0xf0000000-0xf7ffffff]
* May 6 07:51:03 [1] pci 0000:01:00.0: reg 14 io port: [0xd800-0xd8ff]
* May 6 07:51:03 [1] pci 0000:01:00.0: reg 18 32bit mmio: [0xdf000000-0xdf00ffff]
* May 6 07:51:03 [1] pci 0000:01:00.0: reg 30 32bit mmio: [0xeffe0000-0xefffffff]
* May 6 07:51:03 [1] pci 0000:01:00.0: supports D1 D2
* May 6 07:51:03 [1] pci 0000:01:00.1: reg 10 32bit mmio: [0xe0000000-0xe7ffffff]
* May 6 07:51:03 [1] pci 0000:01:00.1: reg 14 32bit mmio: [0xde800000-0xde80ffff]
* May 6 07:51:03 [1] pci 0000:01:00.1: supports D1 D2
* May 6 07:51:03 [1] pci 0000:00:01.0: bridge io port: [0xd000-0xdfff]
* May 6 07:51:03 [1] pci 0000:00:01.0: bridge 32bit mmio: [0xde800000-0xdfefffff]
* May 6 07:51:03 [1] pci 0000:00:01.0: bridge 32bit mmio pref: [0xe0000000-0xfbffffff]
* May 6 07:51:03 [1] pci_bus 0000:00: on NUMA node 0
* May 6 07:51:03 [1] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
* May 6 07:51:03 [1] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
* May 6 07:51:03 [2] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
* May 6 07:51:03 [2] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 *4 5 6 7 9 10 11 12 14 15)
* May 6 07:51:03 [2] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
* May 6 07:51:03 [2] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
* May 6 07:51:03 [2] PCI: Using ACPI for IRQ routing
* May 6 07:51:03 [1]
* May 6 07:51:03 [1] printing PIC contents
* May 6 07:51:03 [1] . PIC IMR: fdfa
* May 6 07:51:03 [1] . PIC IRR: 0000
* May 6 07:51:03 [1] . PIC ISR: 0000
* May 6 07:51:03 [1] . PIC ELCR: 0200
* May 6 07:51:03 [4]
* May 6 07:51:03 [1] printing local APIC contents on CPU#0/0:
* May 6 07:51:03 [2] . APIC ID: 00000000 (0)
* May 6 07:51:03 [2] . APIC VERSION: 00000000
* May 6 07:51:03 [1] . APIC TASKPRI: 00000000 (00)
* May 6 07:51:03 [1] . APIC RRR: 00000000
* May 6 07:51:03 [1] . APIC LDR: 00000000
* May 6 07:51:03 [1] . APIC DFR: 00000000
* May 6 07:51:03 [1] . APIC SPIV: 00000000
* May 6 07:51:03 [1] . APIC ISR field:
* May 6 07:51:03 [1] 0123456789abcdef0123456789abcdef
* May 6 07:51:03 [1] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [1] . APIC TMR field:
* May 6 07:51:03 [1] 0123456789abcdef0123456789abcdef
* May 6 07:51:03 [1] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [1] . APIC IRR field:
* May 6 07:51:03 [1] 0123456789abcdef0123456789abcdef
* May 6 07:51:03 [1] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [4] 00000000000000000000000000000000
* May 6 07:51:03 [1] . APIC ICR: 00000000
* May 6 07:51:03 [1] . APIC ICR2: 00000000
* May 6 07:51:03 [1] . APIC LVTT: 00000000
* May 6 07:51:03 [1] . APIC LVT0: 00000000
* May 6 07:51:03 [1] . APIC LVT1: 00000000
* May 6 07:51:03 [1] . APIC TMICT: 00000000
* May 6 07:51:03 [1] . APIC TMCCT: 00000000
* May 6 07:51:03 [1] . APIC TDCR: 00000000

* May 6 07:51:03 [4]
* May 6 07:51:03 [1] number of MP IRQ sources: 0.
* May 6 07:51:03 [2] testing the IO APIC.
* May 6 07:51:03 [1] IRQ to pin mappings:
* May 6 07:51:03 [2] done.
* May 6 07:51:03 [2] pnp: PnP ACPI init
* May 6 07:51:03 [2] ACPI: bus type pnp registered
* May 6 07:51:03 [4] pnp 00:03: io resource (0xe400-0xe47f) overlaps 0000:00:04.4 BAR 7 (0xe400-0xe4ff), disabling
* May 6 07:51:03 [2] pnp: PnP ACPI: found 10 devices
* May 6 07:51:03 [2] ACPI: ACPI bus type pnp unregistered
* May 6 07:51:03 [2] system 00:00: iomem range 0x0-0x9ffff could not be reserved
* May 6 07:51:03 [2] system 00:00: iomem range 0xf0000-0xfffff could not be reserved
* May 6 07:51:03 [2] system 00:00: iomem range 0x100000-0xfffffff could not be reserved
* May 6 07:51:03 [2] system 00:00: iomem range 0xfffe0000-0xffffffff could not be reserved
* May 6 07:51:03 [2] system 00:02: ioport range 0x3f0-0x3f1 has been reserved
* May 6 07:51:03 [2] system 00:02: ioport range 0x4d0-0x4d1 has been reserved
* May 6 07:51:03 [2] system 00:03: ioport range 0xe800-0xe80f has been reserved
* May 6 07:51:03 [2] pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
* May 6 07:51:03 [2] pci 0000:00:01.0: IO window: 0xd000-0xdfff
* May 6 07:51:03 [2] pci 0000:00:01.0: MEM window: 0xde800000-0xdfefffff
* May 6 07:51:03 [2] pci 0000:00:01.0: PREFETCH window: 0x000000e0000000-0x000000fbffffff
* May 6 07:51:03 [1] pci 0000:00:01.0: setting latency timer to 64
* May 6 07:51:03 [1] pci_bus 0000:00: resource 0 io: [0x00-0xffff]
* May 6 07:51:03 [1] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
* May 6 07:51:03 [1] pci_bus 0000:01: resource 0 io: [0xd000-0xdfff]
* May 6 07:51:03 [1] pci_bus 0000:01: resource 1 mem: [0xde800000-0xdfefffff]
* May 6 07:51:03 [1] pci_bus 0000:01: resource 2 pref mem [0xe0000000-0xfbffffff]
* May 6 07:51:03 [2] NET: Registered protocol family 2
* May 6 07:51:03 [2] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
* May 6 07:51:03 [2] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
* May 6 07:51:03 [2] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
* May 6 07:51:03 [2] TCP: Hash tables configured (established 8192 bind 8192)
* May 6 07:51:03 [2] TCP reno registered
* May 6 07:51:03 [2] NET: Registered protocol family 1
* May 6 07:51:03 [2] Trying to unpack rootfs image as initramfs.
* May 6 07:51:03 [2] rootfs image is not initramfs (junk in compressed archive); looks like an initrd
* May 6 07:51:03 [2] Freeing initrd memory: 7020k freed
* May 6 07:51:03 [2] Simple Boot Flag at 0x3a set to 0x1
* May 6 07:51:03 [2] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
* May 6 07:51:03 [2] msgmni has been set to 501
* May 6 07:51:03 [2] io scheduler noop registered (default)
* May 6 07:51:03 [2] pci 0000:00:01.0: disabling DAC on VIA PCI bridge
* May 6 07:51:03 [2] pci 0000:00:04.0: Disabling VIA external APIC routing
* May 6 07:51:03 [1] pci 0000:01:00.0: Boot video device
* May 6 07:51:03 [2] brd: module loaded
* May 6 07:51:03 [2] loop: module loaded
* May 6 07:51:03 [2] PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
* May 6 07:51:03 [4] PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
* May 6 07:51:03 [2] serio: i8042 KBD port at 0x60,0x64 irq 1
* May 6 07:51:03 [2] mice: PS/2 mouse device common for all mice
* May 6 07:51:03 [2] cpuidle: using governor ladder
* May 6 07:51:03 [2] TCP cubic registered
* May 6 07:51:03 [2] RPC: Registered udp transport module.
* May 6 07:51:03 [2] RPC: Registered tcp transport module.
* May 6 07:51:03 [2] Using IPI Shortcut mode
* May 6 07:51:03 [3] RAMDISK: CORE3 root image found at block 0
* May 6 07:51:03 [4] VFS: Mounted root (ext2 filesystem) on device 1:0.
* May 6 07:51:03 [2] Freeing unused kernel memory: 208k freed
* May 6 07:51:05 [2] Floppy drive(s): fd0 is 1.44M
* May 6 07:51:05 [2] FDC 0 is a post-1991 82077
* May 6 07:51:06 [2] rtc_cmos 00:05: RTC can wake from S4
* May 6 07:51:06 [2] rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
* May 6 07:51:06 [2] rtc0: alarms up to one year, 242 bytes nvram
* May 6 07:51:07 [2] input: PC Speaker as /devices/platform/pcspkr/input/input0
* May 6 07:51:07 [2] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
* May 6 07:51:07 [2] ACPI: Power Button [PWRF]
* May 6 07:51:07 [2] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2
* May 6 07:51:07 [2] ACPI: Power Button [PWRB]
* May 6 07:51:07 [4] Marking TSC unstable due to TSC halts in idle
* May 6 07:51:07 [2] ACPI: CPU0 (power states: C1[C1] C2[C2])
* May 6 07:51:07 [2] processor ACPI_CPU:00: registered as cooling_device0
* May 6 07:51:07 [2] ACPI: Processor [CPU0] (supports 16 throttling states)
* May 6 07:51:08 [2] Uniform Multi-Platform E-IDE driver
* May 6 07:51:08 [2] via82cxxx 0000:00:04.1: VIA vt82c686a (rev 22) IDE UDMA66
* May 6 07:51:08 [2] via82cxxx 0000:00:04.1: IDE controller (0x1106:0x0571 rev 0x10)
* May 6 07:51:08 [2] via82cxxx 0000:00:04.1: not 100% native mode: will probe irqs later
* May 6 07:51:08 [2] ide0: BM-DMA at 0xb800-0xb807
* May 6 07:51:08 [2] ide1: BM-DMA at 0xb808-0xb80f
* May 6 07:51:08 [1] Probing IDE interface ide0.
* May 6 07:51:08 [2] hda: TRANSCEND, CFA DISK drive
* May 6 07:51:09 [1] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO5
* May 6 07:51:09 [4] hda: host side 80-wire cable detection failed, limiting max speed to UDMA33
* May 6 07:51:09 [2] hda: UDMA/33 mode selected
* May 6 07:51:09 [1] Probing IDE interface ide1.
* May 6 07:51:09 [2] hdc: TSSTcorp CDDVDW SH-S222A, ATAPI CD/DVD-ROM drive
* May 6 07:51:10 [1] hdc: host max PIO5 wanted PIO255(auto-tune) selected PIO4
* May 6 07:51:10 [4] hdc: host side 80-wire cable detection failed, limiting max speed to UDMA33
* May 6 07:51:10 [2] hdc: UDMA/33 mode selected
* May 6 07:51:10 [2] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
* May 6 07:51:10 [2] ide1 at 0x170-0x177,0x376 on irq 15
* May 6 07:51:10 [3] SCSI subsystem initialized
* May 6 07:51:10 [1] libata version 3.00 loaded.
* May 6 07:51:10 [2] usbcore: registered new interface driver usbfs
* May 6 07:51:10 [2] usbcore: registered new interface driver hub
* May 6 07:51:10 [2] usbcore: registered new device driver usb
* May 6 07:51:11 [2] uhci_hcd: USB Universal Host Controller Interface driver
* May 6 07:51:11 [4] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
* May 6 07:51:11 [1] PCI: setting IRQ 11 as level-triggered
* May 6 07:51:11 [2] uhci_hcd 0000:00:04.2: PCI INT D -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
* May 6 07:51:11 [2] uhci_hcd 0000:00:04.2: UHCI Host Controller
* May 6 07:51:11 [2] uhci_hcd 0000:00:04.2: new USB bus registered, assigned bus number 1
* May 6 07:51:11 [2] uhci_hcd 0000:00:04.2: irq 11, io base 0x0000b400
* May 6 07:51:11 [2] usb usb1: configuration #1 chosen from 1 choice
* May 6 07:51:11 [2] hub 1-0:1.0: USB hub found
* May 6 07:51:11 [2] hub 1-0:1.0: 2 ports detected
* May 6 07:51:11 [2] uhci_hcd 0000:00:04.3: PCI INT D -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
* May 6 07:51:11 [2] uhci_hcd 0000:00:04.3: UHCI Host Controller
* May 6 07:51:11 [2] uhci_hcd 0000:00:04.3: new USB bus registered, assigned bus number 2
* May 6 07:51:11 [2] uhci_hcd 0000:00:04.3: irq 11, io base 0x0000b000
* May 6 07:51:11 [2] usb usb2: configuration #1 chosen from 1 choice
* May 6 07:51:11 [2] hub 2-0:1.0: USB hub found
* May 6 07:51:11 [2] hub 2-0:1.0: 2 ports detected
* May 6 07:51:11 [4] 3ware Storage Controller device driver for Linux v1.26.02.002.
* May 6 07:51:11 [4] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 4
* May 6 07:51:11 [1] PCI: setting IRQ 4 as level-triggered
* May 6 07:51:11 [2] 3w-xxxx 0000:00:07.0: PCI INT A -> Link[LNKB] -> GSI 4 (level, low) -> IRQ 4
* May 6 07:51:17 [2] scsi0 : 3ware Storage Controller
* May 6 07:51:17 [4] 3w-xxxx: scsi0: Found a 3ware Storage Controller at 0xa800, IRQ: 4.
* May 6 07:51:17 [3] scsi 0:0:0:0: Direct-Access 3ware Logical Disk 0 1.2 PQ: 0 ANSI: 0
* May 6 07:51:17 [2] 8139too Fast Ethernet driver 0.9.28
* May 6 07:51:17 [2] 8139too 0000:00:08.0: enabling device (0004 -> 0007)
* May 6 07:51:17 [4] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
* May 6 07:51:17 [1] PCI: setting IRQ 10 as level-triggered
* May 6 07:51:17 [2] 8139too 0000:00:08.0: PCI INT A -> Link[LNKA] -> GSI 10 (level, low) -> IRQ 10
* May 6 07:51:17 [2] eth0: RealTek RTL8139 at 0xa400, 00:10:a7:10:93:be, IRQ 10
* May 6 07:51:17 [1] eth0: Identified 8139 chip type 'RTL-8139C'
* May 6 07:51:17 [2] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
* May 6 07:51:19 [2] ide-gd driver 1.18
* May 6 07:51:19 [2] hda: max request size: 128KiB
* May 6 07:51:19 [2] hda: 249984 sectors (127 MB) w/1KiB Cache, CHS=248/16/63
* May 6 07:51:19 [2] hda: hda1 hda2
* May 6 07:51:19 [2] ide-cd driver 5.00
* May 6 07:51:19 [2] ide-cd: hdc: ATAPI 48X DVD-ROM DVD-R/RAM CD-R/RW drive, 2048kB Cache
* May 6 07:51:19 [2] Uniform CD-ROM driver Revision: 3.20
* May 6 07:51:19 [4] Driver 'sd' needs updating - please use bus_type methods
* May 6 07:51:19 [3] sd 0:0:0:0: [sda] 625140400 512-byte hardware sectors: (320 GB/298 GiB)
* May 6 07:51:19 [3] sd 0:0:0:0: [sda] Write Protect is off
* May 6 07:51:19 [1] sd 0:0:0:0: [sda] Mode Sense: 00 00 00 00
* May 6 07:51:19 [3] sd 0:0:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
* May 6 07:51:19 [2] sda: sda1
* May 6 07:51:19 [3] sd 0:0:0:0: [sda] Attached SCSI disk
* May 6 07:51:44 [2] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
* May 6 07:51:45 [5] hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
* May 6 07:51:45 [5] hda: task_no_data_intr: error=0x04 { DriveStatusError }
* May 6 07:51:45 [5] hda: possibly failed opcode: 0xb0

* May 6 07:51:47 [2] kjournald starting. Commit interval 5 seconds
* May 6 07:51:47 [2] EXT3 FS on sda1, internal journal
* May 6 07:51:47 [2] EXT3-fs: mounted filesystem with writeback data mode.


Top
 Profile  
 
PostPosted: Thu May 06, 2010 6:42 am 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
The error relates to an IDE drive so not sure how that affects the RAID? In that case it's most likely cable related.

In cases like that, when I'm not clear on the exact cause of a problem, I do the following:

1. Re-seat all connections - RAM, cables, plugs, etc. and clean if necessary.
2. Run memtest. That checks the RAM, CPU and other key components. Allow memtest to complete 3 or more passes before assuming all is well. Overnight is even better. Intermittent heat-related problems can often show up here.
3. Run OEM Disk diagnostics to verify drives, controller, cabling is in shape.
4. In NASLite admin, run check and repair with bad block testing for each individual drive. Bad block testing is irrelevant for a RAID array, so disable that for those.

Those are the 4 basic steps that can provide you with a pretty accurate indication of where your hardware stands. If you have any doubts about your machine, go through the above and if all is well, you can be assured you have a fit server.

Obviously, if a problem occurs during any of the test stages, I'd deal with it accordingly.

Hope that helps.


Top
 Profile  
 
PostPosted: Thu May 06, 2010 6:58 am 
Offline

Joined: Sat Mar 03, 2007 6:25 pm
Posts: 294
Location: Delft NL / Brooklyn NY
Tony wrote:
The error relates to an IDE drive


The only IDE drive in the computer is a Transcend 32 MB solid state module, directly mounted on the IDE connector. That's the boot drive, and booting goes flawless, it seems.

I'll take your suggestion to re-seat all connections.

Is this utility CD a good tool for the tests: http://www.ultimatebootcd.com/

Thanks for answering.


Top
 Profile  
 
PostPosted: Thu May 06, 2010 6:59 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
PieterB wrote:
The only IDE drive in the computer is a Transcend 32 MB solid state module...

In that case the error is benign and caused by lack of UDMA.

It may well be that the NASLite drivers don't like that card. If the disk checks are OK (yes, the Ultimate Boot CD should do fine), then I'd say the card may not be usable with NASLite. I use two VIA SATA controllers in one of my NL servers without an issue, so who knows. Hopefully your tests will turn something up.


Top
 Profile  
 
PostPosted: Thu May 06, 2010 8:55 pm 
Offline

Joined: Sat Mar 03, 2007 6:25 pm
Posts: 294
Location: Delft NL / Brooklyn NY
Tony wrote:
In that case the error is benign and caused by lack of UDMA. If the disk checks are OK (yes, the Ultimate Boot CD should do fine), then I'd say the card may not be usable with NASLite. Hopefully your tests will turn something up.


I think you're starting to confuse two issues: firstly there's a VIA Sata card, not functioning very well. I took that card out, and will test drive the villain in another setup. Secondly there's an issue with an IDE drive. The only IDE connected devices are a new CD drive, and the already mentioned Transcend Module.

The Transcend module has successfully been my boot drive for about 3 years in every NASLite box build. That should rule out a basic problem. Of course there could be a problem with this particular module.
Do I understand well that these lines:
Quote:
* May 6 07:51:45 [5] hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
* May 6 07:51:45 [5] hda: task_no_data_intr: error=0x04 { DriveStatusError }
* May 6 07:51:45 [5] hda: possibly failed opcode: 0xb0

indicate an IDE problem? And could that be the solid state boot drive?


Top
 Profile  
 
PostPosted: Thu May 06, 2010 9:12 pm 
Offline

Joined: Sat Mar 03, 2007 6:25 pm
Posts: 294
Location: Delft NL / Brooklyn NY
This is the end of the syslog of another 2.62 system with the same Transcend boot drive:

# May 7 03:54:08 [1] ata_piix 0000:00:1f.2: version 2.13
# May 7 03:54:08 [2] ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
# May 7 03:54:08 [2] ata_piix 0000:00:1f.2: MAP [ IDE IDE P1 P3 ]
# May 7 03:54:08 [1] ata_piix 0000:00:1f.2: setting latency timer to 64
# May 7 03:54:08 [2] scsi1 : ata_piix
# May 7 03:54:08 [2] scsi2 : ata_piix
# May 7 03:54:08 [2] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
# May 7 03:54:08 [2] ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
# May 7 03:54:09 [2] ata1.00: ATA-5: TRANSCEND, 2.0, max UDMA/66
# May 7 03:54:09 [2] ata1.00: 250368 sectors, multi 1: LBA
# May 7 03:54:09 [4] ata1.00: limited to UDMA/33 due to 40-wire cable
# May 7 03:54:09 [2] ata1.00: configured for UDMA/33
# May 7 03:54:09 [3] scsi 1:0:0:0: Direct-Access ATA TRANSCEND 2.0 PQ: 0 ANSI: 5
# May 7 03:54:09 [1] ata2.01: NODEV after polling detection
# May 7 03:54:09 [2] ata2.00: ATAPI: TSSTcorpDVD-ROM SH-D163B, SB03, max UDMA/33
# May 7 03:54:09 [2] ata2.00: configured for UDMA/33
# May 7 03:54:09 [3] scsi 2:0:0:0: CD-ROM TSSTcorp DVD-ROM SH-D163B SB03 PQ: 0 ANSI: 5
# May 7 03:54:09 [2] Uniform Multi-Platform E-IDE driver
# May 7 03:54:10 [4] Driver 'sd' needs updating - please use bus_type methods
# May 7 03:54:10 [3] sd 0:0:0:0: [sda] 1953103872 512-byte hardware sectors: (999 GB/931 GiB)
# May 7 03:54:10 [3] sd 0:0:0:0: [sda] Write Protect is off
# May 7 03:54:10 [1] sd 0:0:0:0: [sda] Mode Sense: 23 00 10 00
# May 7 03:54:10 [3] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
# May 7 03:54:10 [3] sd 0:0:1:0: [sdb] 1953103872 512-byte hardware sectors: (999 GB/931 GiB)
# May 7 03:54:10 [3] sd 0:0:1:0: [sdb] Write Protect is off
# May 7 03:54:10 [1] sd 0:0:1:0: [sdb] Mode Sense: 23 00 10 00
# May 7 03:54:10 [3] sd 0:0:2:0: [sdc] 1953103872 512-byte hardware sectors: (999 GB/931 GiB)
# May 7 03:54:10 [3] sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
# May 7 03:54:10 [3] sd 0:0:2:0: [sdc] Write Protect is off
# May 7 03:54:10 [1] sd 0:0:2:0: [sdc] Mode Sense: 23 00 10 00
# May 7 03:54:10 [3] sd 1:0:0:0: [sde] 250368 512-byte hardware sectors: (128 MB/122 MiB)
# May 7 03:54:10 [2] sda:<5>sd 1:0:0:0: [sde] Write Protect is off
# May 7 03:54:10 [1] sd 1:0:0:0: [sde] Mode Sense: 00 3a 00 00
# May 7 03:54:10 [3] sd 1:0:0:0: [sde] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
# May 7 03:54:10 [2] sde:<5>sd 0:0:3:0: [sdd] 1953103872 512-byte hardware sectors: (999 GB/931 GiB)
# May 7 03:54:10 [4] sde1
# May 7 03:54:10 [3] sd 0:0:2:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
# May 7 03:54:10 [3] sd 0:0:3:0: [sdd] Write Protect is off
# May 7 03:54:10 [1] sd 0:0:3:0: [sdd] Mode Sense: 23 00 10 00
# May 7 03:54:10 [2] sdb:<5>sd 0:0:3:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA
# May 7 03:54:10 [2] sdc:<6> sdd:
# May 7 03:54:10 [3] sd 1:0:0:0: [sde] Attached SCSI disk
# May 7 03:54:10 [4] sda1
# May 7 03:54:10 [3] sd 0:0:0:0: [sda] Attached SCSI disk
# May 7 03:54:10 [4] sdd1
# May 7 03:54:10 [4] sdc1
# May 7 03:54:10 [3] sd 0:0:3:0: [sdd] Attached SCSI disk
# May 7 03:54:10 [3] sd 0:0:2:0: [sdc] Attached SCSI disk
# May 7 03:54:10 [4] sdb1
# May 7 03:54:10 [3] sd 0:0:1:0: [sdb] Attached SCSI disk
# May 7 03:54:10 [4] Driver 'sr' needs updating - please use bus_type methods
# May 7 03:54:10 [4] sr0: scsi3-mmc drive: 4x/32x cd/rw xa/form2 cdda tray
# May 7 03:54:10 [2] Uniform CD-ROM driver Revision: 3.20
# May 7 03:54:10 [1] sr 2:0:0:0: Attached scsi CD-ROM sr0
# May 7 03:54:39 [2] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
# May 7 03:54:52 [2] kjournald starting. Commit interval 5 seconds
# May 7 03:54:52 [2] EXT3 FS on sda1, internal journal
# May 7 03:54:52 [2] EXT3-fs: mounted filesystem with writeback data mode.
# May 7 03:54:53 [2] kjournald starting. Commit interval 5 seconds
# May 7 03:54:53 [2] EXT3 FS on sdb1, internal journal
# May 7 03:54:53 [2] EXT3-fs: mounted filesystem with writeback data mode.
# May 7 03:54:53 [2] kjournald starting. Commit interval 5 seconds
# May 7 03:54:53 [2] EXT3 FS on sdc1, internal journal
# May 7 03:54:53 [2] EXT3-fs: mounted filesystem with writeback data mode.
# May 7 03:54:53 [2] kjournald starting. Commit interval 5 seconds
# May 7 03:54:53 [2] EXT3 FS on sdd1, internal journal
# May 7 03:54:53 [2] EXT3-fs: mounted filesystem with writeback data mode.

Is there a clue when you compare the two?

And, BTW, the problem started with a degraded RAID array. That could not be related to a faulty boot drive, could it?


Top
 Profile  
 
PostPosted: Fri May 07, 2010 6:12 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
No confusion here at all. 8)

The IDE drive you have is flash and does not support UDMA. The error simply indicates that the system drops down to PIO after failing to access the flash drive with UDMA enabled. You can probably take care of that in the BIOS by disabling UDMA for that IDE channel.

The rest of the issues are subject to your tests. I have no info to contribute on the degraded RAID or the performance of the VIA card.

What I can say with certainty is the particular hda errors are unrelated to the RAID and VIA card issues.


Top
 Profile  
 
PostPosted: Fri May 07, 2010 6:55 pm 
Offline

Joined: Sat Mar 03, 2007 6:25 pm
Posts: 294
Location: Delft NL / Brooklyn NY
Tony wrote:
What I can say with certainty is the particular hda errors are unrelated to the RAID and VIA card issues.


Thank you so much.

It has been said before, but it is so wonderful that you keep looking at the forum, and keep providing your answers.


Top
 Profile  
 
PostPosted: Sat May 08, 2010 9:00 am 
Offline

Joined: Sat Mar 03, 2007 6:25 pm
Posts: 294
Location: Delft NL / Brooklyn NY
I followed the advice to disable UDMA in the BIOS. But nothing changed. This is the endsection of the syslog where the Transcend device is discovered:

# May 8 08:42:26 [1] Probing IDE interface ide0.
# May 8 08:42:26 [2] hda: TRANSCEND, CFA DISK drive
# May 8 08:42:27 [1] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO5
# May 8 08:42:27 [4] hda: host side 80-wire cable detection failed, limiting max speed to UDMA33
# May 8 08:42:27 [2] hda: UDMA/33 mode selected

# May 8 08:42:27 [1] Probing IDE interface ide1.
# May 8 08:42:27 [2] hdc: TSSTcorp CDDVDW SH-S222A, ATAPI CD/DVD-ROM drive
# May 8 08:42:28 [1] hdc: host max PIO5 wanted PIO255(auto-tune) selected PIO4
# May 8 08:42:28 [4] hdc: host side 80-wire cable detection failed, limiting max speed to UDMA33
# May 8 08:42:28 [2] hdc: UDMA/33 mode selected
# May 8 08:42:28 [2] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
# May 8 08:42:28 [2] ide1 at 0x170-0x177,0x376 on irq 15
# May 8 08:42:28 [3] SCSI subsystem initialized
# May 8 08:42:28 [1] libata version 3.00 loaded.
# May 8 08:42:29 [2] usbcore: registered new interface driver usbfs
# May 8 08:42:29 [2] usbcore: registered new interface driver hub
# May 8 08:42:29 [2] usbcore: registered new device driver usb
# May 8 08:42:29 [2] uhci_hcd: USB Universal Host Controller Interface driver
# May 8 08:42:29 [4] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
# May 8 08:42:29 [1] PCI: setting IRQ 11 as level-triggered
# May 8 08:42:29 [2] uhci_hcd 0000:00:04.2: PCI INT D -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
# May 8 08:42:29 [2] uhci_hcd 0000:00:04.2: UHCI Host Controller
# May 8 08:42:29 [2] uhci_hcd 0000:00:04.2: new USB bus registered, assigned bus number 1
# May 8 08:42:29 [2] uhci_hcd 0000:00:04.2: irq 11, io base 0x0000b400
# May 8 08:42:29 [2] usb usb1: configuration #1 chosen from 1 choice
# May 8 08:42:29 [2] hub 1-0:1.0: USB hub found
# May 8 08:42:29 [2] hub 1-0:1.0: 2 ports detected
# May 8 08:42:29 [2] uhci_hcd 0000:00:04.3: PCI INT D -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
# May 8 08:42:29 [2] uhci_hcd 0000:00:04.3: UHCI Host Controller
# May 8 08:42:29 [2] uhci_hcd 0000:00:04.3: new USB bus registered, assigned bus number 2
# May 8 08:42:29 [2] uhci_hcd 0000:00:04.3: irq 11, io base 0x0000b000
# May 8 08:42:29 [2] usb usb2: configuration #1 chosen from 1 choice
# May 8 08:42:29 [2] hub 2-0:1.0: USB hub found
# May 8 08:42:29 [2] hub 2-0:1.0: 2 ports detected
# May 8 08:42:29 [4] 3ware Storage Controller device driver for Linux v1.26.02.002.
# May 8 08:42:29 [4] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 4
# May 8 08:42:29 [1] PCI: setting IRQ 4 as level-triggered
# May 8 08:42:29 [2] 3w-xxxx 0000:00:07.0: PCI INT A -> Link[LNKB] -> GSI 4 (level, low) -> IRQ 4
# May 8 08:42:35 [2] scsi0 : 3ware Storage Controller
# May 8 08:42:35 [4] 3w-xxxx: scsi0: Found a 3ware Storage Controller at 0xa800, IRQ: 4.
# May 8 08:42:35 [3] scsi 0:0:0:0: Direct-Access 3ware Logical Disk 0 1.2 PQ: 0 ANSI: 0
# May 8 08:42:35 [2] 8139too Fast Ethernet driver 0.9.28
# May 8 08:42:35 [2] 8139too 0000:00:08.0: enabling device (0004 -> 0007)
# May 8 08:42:35 [4] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
# May 8 08:42:35 [1] PCI: setting IRQ 10 as level-triggered
# May 8 08:42:35 [2] 8139too 0000:00:08.0: PCI INT A -> Link[LNKA] -> GSI 10 (level, low) -> IRQ 10
# May 8 08:42:35 [2] eth0: RealTek RTL8139 at 0xa400, 00:10:a7:10:93:be, IRQ 10
# May 8 08:42:35 [1] eth0: Identified 8139 chip type 'RTL-8139C'
# May 8 08:42:35 [2] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
# May 8 08:42:37 [2] ide-gd driver 1.18
# May 8 08:42:37 [2] hda: max request size: 128KiB
# May 8 08:42:37 [2] hda: 249984 sectors (127 MB) w/1KiB Cache, CHS=248/16/63
# May 8 08:42:37 [2] hda: hda1 hda2
# May 8 08:42:37 [2] ide-cd driver 5.00
# May 8 08:42:37 [2] ide-cd: hdc: ATAPI 48X DVD-ROM DVD-R/RAM CD-R/RW drive, 2048kB Cache
# May 8 08:42:37 [2] Uniform CD-ROM driver Revision: 3.20
# May 8 08:42:37 [4] Driver 'sd' needs updating - please use bus_type methods
# May 8 08:42:37 [3] sd 0:0:0:0: [sda] 625140400 512-byte hardware sectors: (320 GB/298 GiB)
# May 8 08:42:37 [3] sd 0:0:0:0: [sda] Write Protect is off
# May 8 08:42:37 [1] sd 0:0:0:0: [sda] Mode Sense: 00 00 00 00
# May 8 08:42:37 [3] sd 0:0:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
# May 8 08:42:37 [2] sda: sda1
# May 8 08:42:37 [3] sd 0:0:0:0: [sda] Attached SCSI disk
# May 8 08:43:02 [2] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
# May 8 08:43:04 [5] hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
# May 8 08:43:04 [5] hda: task_no_data_intr: error=0x04 { DriveStatusError }
# May 8 08:43:04 [5] hda: possibly failed opcode: 0xb0

# May 8 08:43:05 [2] kjournald starting. Commit interval 5 seconds
# May 8 08:43:05 [2] EXT3 FS on sda1, internal journal
# May 8 08:43:05 [2] EXT3-fs: mounted filesystem with writeback data mode.

Anybody out there have a guess? Should I -in stead of disabling UDMA- enable the lowest speed in the BIOS, for instance?


Top
 Profile  
 
PostPosted: Sat May 08, 2010 1:38 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:01 pm
Posts: 801
Location: ServerElements
Ignore it, it will always be in the syslog with a flash device, since it's doesn't support DMA.


Top
 Profile  
 
PostPosted: Sat May 08, 2010 2:47 pm 
Offline

Joined: Sat Mar 03, 2007 6:25 pm
Posts: 294
Location: Delft NL / Brooklyn NY
Ralph wrote:
Ignore it, it will always be in the syslog with a flash device, since it's doesn't support DMA.


Sorry Ralph, that's too easy. Here's the end section of my own test system, with the same Transcend device (http://www.transcendusa.com/Products/ModDetail.asp?ModNo=26&LangNo=0&Func1No=1&Func2No=159, no problems whatsoever:

# May 7 03:54:09 [2] ata1.00: ATA-5: TRANSCEND, 2.0, max UDMA/66
# May 7 03:54:09 [2] ata1.00: 250368 sectors, multi 1: LBA
# May 7 03:54:09 [4] ata1.00: limited to UDMA/33 due to 40-wire cable
# May 7 03:54:09 [2] ata1.00: configured for UDMA/33
# May 7 03:54:09 [3] scsi 1:0:0:0: Direct-Access ATA TRANSCEND 2.0 PQ: 0 ANSI: 5
# May 7 03:54:09 [1] ata2.01: NODEV after polling detection
# May 7 03:54:09 [2] ata2.00: ATAPI: TSSTcorpDVD-ROM SH-D163B, SB03, max UDMA/33
# May 7 03:54:09 [2] ata2.00: configured for UDMA/33
# May 7 03:54:09 [3] scsi 2:0:0:0: CD-ROM TSSTcorp DVD-ROM SH-D163B SB03 PQ: 0 ANSI: 5
# May 7 03:54:09 [2] Uniform Multi-Platform E-IDE driver
# May 7 03:54:10 [4] Driver 'sd' needs updating - please use bus_type methods
# May 7 03:54:10 [3] sd 0:0:0:0: [sda] 1953103872 512-byte hardware sectors: (999 GB/931 GiB)
# May 7 03:54:10 [3] sd 0:0:0:0: [sda] Write Protect is off
# May 7 03:54:10 [1] sd 0:0:0:0: [sda] Mode Sense: 23 00 10 00
# May 7 03:54:10 [3] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
# May 7 03:54:10 [3] sd 0:0:1:0: [sdb] 1953103872 512-byte hardware sectors: (999 GB/931 GiB)
# May 7 03:54:10 [3] sd 0:0:1:0: [sdb] Write Protect is off
# May 7 03:54:10 [1] sd 0:0:1:0: [sdb] Mode Sense: 23 00 10 00
# May 7 03:54:10 [3] sd 0:0:2:0: [sdc] 1953103872 512-byte hardware sectors: (999 GB/931 GiB)
# May 7 03:54:10 [3] sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
# May 7 03:54:10 [3] sd 0:0:2:0: [sdc] Write Protect is off
# May 7 03:54:10 [1] sd 0:0:2:0: [sdc] Mode Sense: 23 00 10 00
# May 7 03:54:10 [3] sd 1:0:0:0: [sde] 250368 512-byte hardware sectors: (128 MB/122 MiB)
# May 7 03:54:10 [2] sda:<5>sd 1:0:0:0: [sde] Write Protect is off
# May 7 03:54:10 [1] sd 1:0:0:0: [sde] Mode Sense: 00 3a 00 00
# May 7 03:54:10 [3] sd 1:0:0:0: [sde] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
# May 7 03:54:10 [2] sde:<5>sd 0:0:3:0: [sdd] 1953103872 512-byte hardware sectors: (999 GB/931 GiB)
# May 7 03:54:10 [4] sde1
# May 7 03:54:10 [3] sd 0:0:2:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
# May 7 03:54:10 [3] sd 0:0:3:0: [sdd] Write Protect is off
# May 7 03:54:10 [1] sd 0:0:3:0: [sdd] Mode Sense: 23 00 10 00
# May 7 03:54:10 [2] sdb:<5>sd 0:0:3:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA
# May 7 03:54:10 [2] sdc:<6> sdd:
# May 7 03:54:10 [3] sd 1:0:0:0: [sde] Attached SCSI disk
# May 7 03:54:10 [4] sda1
# May 7 03:54:10 [3] sd 0:0:0:0: [sda] Attached SCSI disk
# May 7 03:54:10 [4] sdd1
# May 7 03:54:10 [4] sdc1
# May 7 03:54:10 [3] sd 0:0:3:0: [sdd] Attached SCSI disk
# May 7 03:54:10 [3] sd 0:0:2:0: [sdc] Attached SCSI disk
# May 7 03:54:10 [4] sdb1
# May 7 03:54:10 [3] sd 0:0:1:0: [sdb] Attached SCSI disk
# May 7 03:54:10 [4] Driver 'sr' needs updating - please use bus_type methods
# May 7 03:54:10 [4] sr0: scsi3-mmc drive: 4x/32x cd/rw xa/form2 cdda tray
# May 7 03:54:10 [2] Uniform CD-ROM driver Revision: 3.20
# May 7 03:54:10 [1] sr 2:0:0:0: Attached scsi CD-ROM sr0
# May 7 03:54:39 [2] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
# May 7 03:54:52 [2] kjournald starting. Commit interval 5 seconds
# May 7 03:54:52 [2] EXT3 FS on sda1, internal journal
# May 7 03:54:52 [2] EXT3-fs: mounted filesystem with writeback data mode.
# May 7 03:54:53 [2] kjournald starting. Commit interval 5 seconds
# May 7 03:54:53 [2] EXT3 FS on sdb1, internal journal
# May 7 03:54:53 [2] EXT3-fs: mounted filesystem with writeback data mode.
# May 7 03:54:53 [2] kjournald starting. Commit interval 5 seconds
# May 7 03:54:53 [2] EXT3 FS on sdc1, internal journal
# May 7 03:54:53 [2] EXT3-fs: mounted filesystem with writeback data mode.
# May 7 03:54:53 [2] kjournald starting. Commit interval 5 seconds
# May 7 03:54:53 [2] EXT3 FS on sdd1, internal journal
# May 7 03:54:53 [2] EXT3-fs: mounted filesystem with writeback data mode.
# May 7 03:55:59 [4] 3w-9xxx: scsi0: AEN: INFO (0x04:0x0029): Verify started:unit=0.
# May 7 03:55:59 [4] 3w-9xxx: scsi0: AEN: INFO (0x04:0x0029): Verify started:unit=1.
# May 7 03:55:59 [4] 3w-9xxx: scsi0: AEN: INFO (0x04:0x0029): Verify started:unit=2.
# May 7 06:48:11 [4] 3w-9xxx: scsi0: AEN: INFO (0x04:0x002B): Verify completed:unit=2.
# May 7 06:48:12 [4] 3w-9xxx: scsi0: AEN: INFO (0x04:0x0029): Verify started:unit=3.
# May 7 07:26:55 [4] 3w-9xxx: scsi0: AEN: INFO (0x04:0x002B): Verify completed:unit=1.
# May 7 07:28:33 [4] 3w-9xxx: scsi0: AEN: INFO (0x04:0x002B): Verify completed:unit=0.
# May 7 09:38:57 [4] 3w-9xxx: scsi0: AEN: INFO (0x04:0x002B): Verify completed:unit=3.

Also my functional box (still on the previous version) does not have a problem with the Transcend drive:

# Apr 30 02:43:04 user.warn kernel: hda: TRANSCEND 032M, ATA DISK drive
# Apr 30 02:43:04 user.warn kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
# Apr 30 02:43:04 user.warn kernel: hda: attached ide-disk driver.
# Apr 30 02:43:04 user.info kernel: hda: 63488 sectors (33 MB) w/2KiB Cache, CHS=1024/255/63
# Apr 30 02:43:04 user.info kernel: Partition check:
# Apr 30 02:43:04 user.info kernel: /dev/ide/host0/bus0/target0/lun0: p1 p2
# Apr 30 02:43:04 user.info kernel: SCSI subsystem driver Revision: 1.00
# Apr 30 02:43:04 user.info kernel: Loading Adaptec I2O RAID: Version 2.4 Build 5
# Apr 30 02:43:04 user.info kernel: Detecting Adaptec I2O RAID controllers.
# Apr 30 02:43:04 user.info kernel: Red Hat/Adaptec aacraid driver (1.1-3 Aug 12 2007 09:05:44)
# Apr 30 02:43:04 user.warn kernel: scsi: Detection failed (no card)
# Apr 30 02:43:04 user.notice kernel: megaraid: v2.10.10.1 (Release Date: Thu Jan 27 16:19:44 EDT 2005)
# Apr 30 02:43:04 user.warn kernel: GDT-HA: Storage RAID Controller Driver. Version: 3.04
# Apr 30 02:43:04 user.warn kernel: GDT-HA: Found 0 PCI Storage RAID Controllers
# Apr 30 02:43:04 user.warn kernel: 3ware Storage Controller device driver for Linux v1.02.00.037.
# Apr 30 02:43:04 user.notice kernel: scsi1 : Found a 3ware Storage Controller at 0xbc00, IRQ: 3, P-chip: 1.3
# Apr 30 02:43:04 user.info kernel: scsi1 : 3ware Storage Controller
# Apr 30 02:43:04 user.warn kernel: Vendor: 3ware Model: Logical Disk 0 Rev: 1.0
# Apr 30 02:43:04 user.warn kernel: Type: Direct-Access ANSI SCSI revision: 00
# Apr 30 02:43:04 user.debug kernel: libata version 1.20 loaded.
# Apr 30 02:43:04 user.debug kernel: PCI(00:1f.2): version 1.05
# Apr 30 02:43:04 user.debug kernel: to 64
# Apr 30 02:43:04 user.info kernel: ata1: SATA max UDMA/133 cmd 0xEC00 ctl 0xE802 bmdma 0xDC00 irq 10
# Apr 30 02:43:04 user.info kernel: ata2: SATA max UDMA/133 cmd 0xE400 ctl 0xE002 bmdma 0xDC08 irq 10
# Apr 30 02:43:04 user.debug kernel: ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4023 85:3469 86:3c01 87:4023 88:207f
# Apr 30 02:43:04 user.info kernel: ata1: dev 0 ATA-7, max UDMA/133, 976773168 sectors: LBA48
# Apr 30 02:43:04 user.debug kernel: ata1: dev 1 cfg 49:0f00 82:0210 83:4010 84:4000 85:0000 86:0000 87:4000 88:0407
# Apr 30 02:43:04 user.info kernel: ata1: dev 1 ATAPI, max UDMA/33
# Apr 30 02:43:04 user.info kernel: ata1: dev 0 configured for UDMA/33
# Apr 30 02:43:04 user.info kernel: ata1: dev 1 configured for UDMA/33
# Apr 30 02:43:04 user.warn kernel: ATA: abnormal status 0x7F on port 0xE407
# Apr 30 02:43:04 user.err kernel: ata2: disabling port
# Apr 30 02:43:04 user.info kernel: scsi2 : ata_piix
# Apr 30 02:43:04 user.info kernel: scsi3 : ata_piix
# Apr 30 02:43:04 user.warn kernel: Vendor: ATA Model: ST3500630AS Rev: 3.AA
# Apr 30 02:43:04 user.warn kernel: Type: Direct-Access ANSI SCSI revision: 05
# Apr 30 02:43:04 user.warn kernel: Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
# Apr 30 02:43:04 user.warn kernel: Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0
# Apr 30 02:43:04 user.warn kernel: SCSI device sda: 976771120 512-byte hdwr sectors (500107 MB)
# Apr 30 02:43:04 user.info kernel: /dev/scsi/host1/bus0/target0/lun0: p1
# Apr 30 02:43:04 user.warn kernel: SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB)
# Apr 30 02:43:04 user.info kernel: /dev/scsi/host2/bus0/target0/lun0: p1
# Apr 30 02:43:04 user.info kernel: raw1394: /dev/raw1394 device initialized
# Apr 30 02:43:04 user.info kernel: sbp2: $Rev: 1074 $ Ben Collins
# Apr 30 02:43:04 user.err kernel: ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
# Apr 30 02:43:04 user.info kernel: usb.c: registered new driver usbdevfs
# Apr 30 02:43:04 user.info kernel: usb.c: registered new driver hub
# Apr 30 02:43:04 user.debug kernel: PCI: Setting latency timer of device 00:1d.7 to 64
# Apr 30 02:43:04 user.info kernel: ehci_hcd 00:1d.7: PCI device 8086:265c
# Apr 30 02:43:04 user.info kernel: ehci_hcd 00:1d.7: irq 9, pci mem f8834000
# Apr 30 02:43:04 user.info kernel: usb.c: new USB bus registered, assigned bus number 1
# Apr 30 02:43:04 user.info kernel: ehci_hcd 00:1d.7: enabled 64bit PCI DMA
# Apr 30 02:43:04 user.debug kernel: PCI: cache line size of 128 is not supported by device 00:1d.7
# Apr 30 02:43:04 user.info kernel: ehci_hcd 00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
# Apr 30 02:43:04 user.info kernel: hub.c: USB hub found
# Apr 30 02:43:04 user.info kernel: hub.c: 8 ports detected
# Apr 30 02:43:04 user.info kernel: host/uhci.c: USB Universal Host Controller Interface driver v1.1
# Apr 30 02:43:04 user.debug kernel: PCI: Setting latency timer of device 00:1d.0 to 64
# Apr 30 02:43:04 user.info kernel: host/uhci.c: USB UHCI at I/O 0xcc00, IRQ 9
# Apr 30 02:43:04 user.info kernel: usb.c: new USB bus registered, assigned bus number 2
# Apr 30 02:43:04 user.info kernel: hub.c: USB hub found
# Apr 30 02:43:04 user.info kernel: hub.c: 2 ports detected
# Apr 30 02:43:04 user.debug kernel: PCI: Setting latency timer of device 00:1d.1 to 64
# Apr 30 02:43:04 user.info kernel: host/uhci.c: USB UHCI at I/O 0xd000, IRQ 10
# Apr 30 02:43:04 user.info kernel: usb.c: new USB bus registered, assigned bus number 3
# Apr 30 02:43:04 user.info kernel: hub.c: USB hub found
# Apr 30 02:43:04 user.info kernel: hub.c: 2 ports detected
# Apr 30 02:43:04 user.debug kernel: PCI: Setting latency timer of device 00:1d.2 to 64
# Apr 30 02:43:04 user.info kernel: host/uhci.c: USB UHCI at I/O 0xd400, IRQ 5
# Apr 30 02:43:04 user.info kernel: usb.c: new USB bus registered, assigned bus number 4
# Apr 30 02:43:04 user.info kernel: hub.c: USB hub found
# Apr 30 02:43:04 user.info kernel: hub.c: 2 ports detected
# Apr 30 02:43:04 user.debug kernel: PCI: Setting latency timer of device 00:1d.3 to 64
# Apr 30 02:43:04 user.info kernel: host/uhci.c: USB UHCI at I/O 0xd800, IRQ 11
# Apr 30 02:43:04 user.info kernel: usb.c: new USB bus registered, assigned bus number 5
# Apr 30 02:43:04 user.info kernel: hub.c: USB hub found
# Apr 30 02:43:04 user.info kernel: hub.c: 2 ports detected
# Apr 30 02:43:04 user.info kernel: usb.c: registered new driver usbkbd
# Apr 30 02:43:04 user.info kernel: usbkbd.c: :USB HID Boot Protocol keyboard driver
# Apr 30 02:43:04 user.info kernel: Initializing USB Mass Storage driver.
# Apr 30 02:43:04 user.info kernel: usb.c: registered new driver usb-storage
# Apr 30 02:43:04 user.info kernel: USB Mass Storage support registered.
# Apr 30 02:43:04 user.info kernel: NET4: Linux TCP/IP 1.0 for NET4.0
# Apr 30 02:43:04 user.info kernel: IP Protocols: ICMP, UDP, TCP
# Apr 30 02:43:04 user.info kernel: IP: routing cache hash table of 8192 buckets, 64Kbytes
# Apr 30 02:43:04 user.info kernel: TCP: Hash tables configured (established 262144 bind 65536)
# Apr 30 02:43:04 user.info kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
# Apr 30 02:43:04 user.notice kernel: RAMDISK: NASLite file system found at block 0
# Apr 30 02:43:04 user.warn kernel: <6>Freeing initrd memory: 1962k freed
# Apr 30 02:43:04 user.warn kernel: EXT2-fs warning: checktime reached, running e2fsck is recommended
# Apr 30 02:43:04 user.warn kernel: VFS: Mounted root (ext2 filesystem).
# Apr 30 02:43:04 user.info kernel: Mounted devfs on /dev
# Apr 30 02:43:04 user.info kernel:
# Apr 30 02:43:04 user.info kernel: e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
# Apr 30 02:43:04 user.info kernel: kjournald starting. Commit interval 5 seconds
# Apr 30 02:43:04 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal
# Apr 30 02:43:04 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
# Apr 30 02:43:04 user.info kernel: kjournald starting. Commit interval 5 seconds
# Apr 30 02:43:04 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,17), internal journal
# Apr 30 02:43:04 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
# May 4 03:30:14 user.info kernel: e1000: eth0: e1000_watchdog: NIC Link is Down
# May 4 03:30:40 user.info kernel: e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

It's just puzzling me.


Top
 Profile  
 
PostPosted: Sat May 08, 2010 11:42 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:01 pm
Posts: 801
Location: ServerElements
Quote:
Sorry Ralph, that's too easy. Here's the end section of my own test system, with the same Transcend device (http://www.transcendusa.com/Products/Mo ... unc2No=159, no problems whatsoever:


So what changed?

And now I ask the question, if board/bios can't detect properly a boot device that has limited or no DMA support, how does that affect your running NL system?


Top
 Profile  
 
PostPosted: Mon May 10, 2010 3:25 am 
Offline

Joined: Sat Mar 03, 2007 6:25 pm
Posts: 294
Location: Delft NL / Brooklyn NY
OK, you have an old car, running absolutely perfect. All of a sudden, it dies. Your mechanic arrives, readjusts some parts, wiggles some cables and EUREKA! It runs again like before. Then you notice the red warning light on your dashboard. The manual instructs you to go straight to a garage. That's what you do, of course. You consult your kind & capable car mechanic again. He says: 'What's your problem? The car is running fine, ain't it? Just ignore the light. It's nothing"

I assure you, you keep looking at the light, and keep wondering: it wasn't there before....


Top
 Profile  
 
PostPosted: Mon May 10, 2010 12:54 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
Well, let me try to explain.

What you are seeing is the kernel doing its job. In some cases, where the BIOS properly sets the hardware, the kernel sees a PIO mode IDE device hence addresses it in those terms. If however the BIOS misrepresents the device and leads the kernel to think its addressing an IDE device capable of UDMA support, the kernel will proceed accordingly and fail issuing the error. It will then drop a notch and try addressing the device via PIO. That's why you see the error only once.

In the case of DOS/Windows, etc, the BIOS controls how the drives are addressed. In the case of Linux however, the kernel probes and handles the hardware based on it's capabilities and not necessarily by what the BIOS reports.

The DriveStatusError issued by the kernel is not new but has surely been there for that particular board. You can verify that by trying any version of NASLite including older versions.


Top
 Profile  
 
PostPosted: Mon May 10, 2010 1:09 pm 
Offline

Joined: Sat Mar 03, 2007 6:25 pm
Posts: 294
Location: Delft NL / Brooklyn NY
Tony wrote:
The DriveStatusError issued by the kernel is not new but has surely been there for that particular board. You can verify that by trying any version of NASLite including older versions.


Thank you for your comprehensive explanation. I do wonder if the previous version reported the same error. I don't recall seeing an error with the initial CORE3 on that machine.

I will have the computer second half of this week for testing, and will report my findings. Can I downgrade NL-2 the same way I upgrade (the 'i' option)?


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 26 posts ]  Go to page 1, 2  Next

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 75 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