NASLite Network Attached Storage

# Sep 23 14:54:05 user.warn kernel: EXT2-fs warning: checktime reached, running e2fsck is recommended

AND:

# Sep 25 01:02:40 user.debug kernel: hw tcp v4 csum failed
# Sep 25 01:02:40 user.debug kernel: hw tcp v4 csum failed
# Sep 25 01:02:40 user.debug kernel: hw tcp v4 csum failed
# Sep 25 01:02:40 user.debug kernel: hw tcp v4 csum failed
# Sep 26 15:57:07 user.debug kernel: hw tcp v4 csum failed
# Sep 26 15:57:07 user.debug kernel: hw tcp v4 csum failed
# Sep 26 15:57:07 user.debug kernel: hw tcp v4 csum failed
# Sep 26 15:57:07 user.debug kernel: hw tcp v4 csum failed
# Sep 26 15:57:07 user.debug kernel: hw tcp v4 csum failed
# Sep 26 15:57:07 user.debug kernel: hw tcp v4 csum failed
# Sep 26 15:57:07 user.debug kernel: hw tcp v4 csum failed
# Sep 26 15:57:07 user.debug kernel: hw tcp v4 csum failed
# Sep 26 15:57:07 user.debug kernel: hw tcp v4 csum failed
# Sep 26 15:57:07 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:24:55 user.warn kernel: NET: 5 messages suppressed.
# Sep 26 16:24:55 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:24:55 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:24:55 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:24:55 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:24:55 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:24:55 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:24:55 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:24:55 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:24:55 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:24:55 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:34:16 user.warn kernel: NET: 11 messages suppressed.
# Sep 26 16:34:16 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:34:16 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:34:16 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:34:16 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:34:16 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:34:16 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:34:16 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:34:16 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:34:16 user.debug kernel: hw tcp v4 csum failed
# Sep 26 16:34:16 user.debug kernel: hw tcp v4 csum failed


PieterB

Tony or Ralph should be able to tell you but it looks to me like you are having issues with the NIC.

Mike

Just rebooted NASLite; alarming lines vanished, except for the one in red -action required?

System Message Log:

* Sep 27 13:52:18 user.notice kernel: klogd started: BusyBox v1.01 (2007.03.15-22:03+0000)
* Sep 27 13:52:18 user.warn kernel: Linux version 2.4.35.NASLite (root@tzt) (gcc version 3.4.6) #2 Sun Aug 12 09:03:16 EDT 2007
* Sep 27 13:52:18 user.info kernel: BIOS-provided physical RAM map:
* Sep 27 13:52:18 user.warn kernel: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
* Sep 27 13:52:18 user.warn kernel: BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
* Sep 27 13:52:18 user.warn kernel: BIOS-e820: 00000000000e6000 - 0000000000100000 (reserved)
* Sep 27 13:52:18 user.warn kernel: BIOS-e820: 0000000000100000 - 000000003fe2fc00 (usable)
* Sep 27 13:52:18 user.warn kernel: BIOS-e820: 000000003fe2fc00 - 000000003fe3ecb3 (ACPI NVS)
* Sep 27 13:52:18 user.warn kernel: BIOS-e820: 000000003ff2fc00 - 000000003ff30000 (ACPI NVS)
* Sep 27 13:52:18 user.warn kernel: BIOS-e820: 000000003ff30000 - 000000003ff40000 (ACPI data)
* Sep 27 13:52:18 user.warn kernel: BIOS-e820: 000000003ff40000 - 000000003fff0000 (ACPI NVS)
* Sep 27 13:52:18 user.warn kernel: BIOS-e820: 000000003fff0000 - 0000000040000000 (reserved)
* Sep 27 13:52:18 user.warn kernel: BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
* Sep 27 13:52:18 user.warn kernel: BIOS-e820: 00000000fed13000 - 00000000fed1a000 (reserved)
* Sep 27 13:52:18 user.warn kernel: BIOS-e820: 00000000fed1c000 - 00000000feda0000 (reserved)
* Sep 27 13:52:18 user.notice kernel: 126MB HIGHMEM available.
* Sep 27 13:52:18 user.notice kernel: 896MB LOWMEM available.
* Sep 27 13:52:18 user.warn kernel: On node 0 totalpages: 261679
* Sep 27 13:52:18 user.warn kernel: zone(0): 4096 pages.
* Sep 27 13:52:18 user.warn kernel: zone(1): 225280 pages.
* Sep 27 13:52:18 user.warn kernel: zone(2): 32303 pages.
* Sep 27 13:52:18 user.info kernel: ACPI: RSDP (v000 ACPIAM ) @ 0x000f4ea0
* Sep 27 13:52:18 user.info kernel: ACPI: RSDT (v001 INTEL D915PSY 0x20050128 MSFT 0x00000097) @ 0x3ff30000
* Sep 27 13:52:18 user.info kernel: ACPI: FADT (v002 INTEL D915PSY 0x20050128 MSFT 0x00000097) @ 0x3ff30200
* Sep 27 13:52:18 user.info kernel: ACPI: MADT (v001 INTEL D915PSY 0x20050128 MSFT 0x00000097) @ 0x3ff30390
* Sep 27 13:52:18 user.info kernel: ACPI: MCFG (v001 INTEL D915PSY 0x20050128 MSFT 0x00000097) @ 0x3ff30400
* Sep 27 13:52:18 user.info kernel: ACPI: ASF! (v016 LEGEND I865PASF 0x00000001 INTL 0x02002026) @ 0x3ff35f90
* Sep 27 13:52:18 user.info kernel: ACPI: SSDT (v001 DpgPmm Cpu1Ist 0x00000010 INTL 0x02002026) @ 0x3ff36030
* Sep 27 13:52:18 user.info kernel: ACPI: SSDT (v001 DpgPmm Cpu2Ist 0x00000010 INTL 0x02002026) @ 0x3ff36440
* Sep 27 13:52:18 user.info kernel: ACPI: SSDT (v001 DpgPmm CpuPm 0x00000010 INTL 0x02002026) @ 0x3ff36850
* Sep 27 13:52:18 user.info kernel: ACPI: TCPA (v001 INTEL TBLOEMID 0x00000001 MSFT 0x00000097) @ 0x3ff36990
* Sep 27 13:52:18 user.info kernel: ACPI: WDDT (v001 INTEL OEMWDDT 0x00000001 INTL 0x02002026) @ 0x3ff369c4
* Sep 27 13:52:18 user.info kernel: ACPI: DSDT (v001 INTEL D915PSY 0x00000001 INTL 0x02002026) @ 0x00000000
* Sep 27 13:52:18 user.warn kernel: Kernel command line: rw root=/dev/ram0 initrd=NASLite.02 quiet BOOT_IMAGE=naslite.01
* Sep 27 13:52:18 user.info kernel: Initializing CPU#0
* Sep 27 13:52:18 user.warn kernel: Detected 3000.265 MHz processor.
* Sep 27 13:52:18 user.warn kernel: Console: colour VGA+ 80x25
* Sep 27 13:52:18 user.warn kernel: Calibrating delay loop. 5976.88 BogoMIPS
* Sep 27 13:52:18 user.info kernel: Memory: 1028396k/1046716k available (2214k kernel code, 17932k reserved, 642k data, 540k init, 129212k highmem)
* Sep 27 13:52:18 user.info kernel: Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
* Sep 27 13:52:18 user.info kernel: Inode cache hash table entries: 65536 (order: 7, 524288 bytes)
* Sep 27 13:52:18 user.info kernel: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
* Sep 27 13:52:18 user.info kernel: Buffer cache hash table entries: 65536 (order: 6, 262144 bytes)
* Sep 27 13:52:18 user.warn kernel: Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
* Sep 27 13:52:18 user.info kernel: CPU: Trace cache: 12K uops, L1 D cache: 16K
* Sep 27 13:52:18 user.debug kernel: CPU: After generic, caps: bfebfbff 20100000 00000000 00000000
* Sep 27 13:52:18 user.debug kernel: CPU: Common caps: bfebfbff 20100000 00000000 00000000
* Sep 27 13:52:18 user.warn kernel: CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 0a
* Sep 27 13:52:18 user.info kernel: Enabling fast FPU save and restore. done.
* Sep 27 13:52:18 user.info kernel: Enabling unmasked SIMD FPU exception support. done.
* Sep 27 13:52:18 user.info kernel: Checking 'hlt' instruction. OK.
* Sep 27 13:52:18 user.warn kernel: ACPI: IRQ9 SCI: Level Trigger.
* Sep 27 13:52:18 user.warn kernel: POSIX conformance testing by UNIFIX
* Sep 27 13:52:18 user.warn kernel: mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
* Sep 27 13:52:18 user.warn kernel: mtrr: detected mtrr type: Intel
* Sep 27 13:52:18 user.info kernel: ACPI: Subsystem revision 20040326
* Sep 27 13:52:18 user.info kernel: PCI: Using configuration type 1
* Sep 27 13:52:18 user.info kernel: ACPI: Interpreter enabled
* Sep 27 13:52:18 user.info kernel: ACPI: Using PIC for interrupt routing
* Sep 27 13:52:18 user.info kernel: ACPI: System [ACPI] (supports S0 S1 S4 S5)
* Sep 27 13:52:18 user.info kernel: ACPI: PCI Root Bridge [PCI0] (00:00)
* Sep 27 13:52:18 user.warn kernel: PCI: Probing PCI hardware (bus 00)
* Sep 27 13:52:18 user.info kernel: PCI: Ignoring BAR0-3 of IDE controller 00:1f.1
* Sep 27 13:52:18 user.warn kernel: Transparent bridge - PCI device 8086:244e
* Sep 27 13:52:18 user.debug kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
* Sep 27 13:52:18 user.debug kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEGP._PRT]
* Sep 27 13:52:18 user.debug kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P2._PRT]
* Sep 27 13:52:18 user.info kernel: ACPI: Power Resource [URP1] (off)
* Sep 27 13:52:18 user.info kernel: ACPI: Power Resource [FDDP] (off)
* Sep 27 13:52:18 user.info kernel: ACPI: Power Resource [LPTP] (off)
* Sep 27 13:52:18 user.info kernel: ACPI: Power Resource [URP2] (off)
* Sep 27 13:52:18 user.debug kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT]
* Sep 27 13:52:18 user.debug kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2._PRT]
* Sep 27 13:52:18 user.debug kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3._PRT]
* Sep 27 13:52:18 user.warn kernel: *11 12 14 15)
* Sep 27 13:52:18 user.warn kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
* Sep 27 13:52:18 user.warn kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
* Sep 27 13:52:18 user.warn kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
* Sep 27 13:52:18 user.warn kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
* Sep 27 13:52:18 user.warn kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
* Sep 27 13:52:18 user.warn kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs *3 4 5 6 7 9 10 11 12 14 15)
* Sep 27 13:52:18 user.warn kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
* Sep 27 13:52:18 user.info kernel: PCI: Probing PCI hardware
* Sep 27 13:52:18 user.warn kernel: ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
* Sep 27 13:52:18 user.warn kernel: ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
* Sep 27 13:52:18 user.warn kernel: ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
* Sep 27 13:52:18 user.warn kernel: ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
* Sep 27 13:52:18 user.warn kernel: ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 9
* Sep 27 13:52:18 user.warn kernel: ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 3
* Sep 27 13:52:18 user.warn kernel: ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 11
* Sep 27 13:52:18 user.info kernel: PCI: Using ACPI for IRQ routing
* Sep 27 13:52:18 user.info kernel: Linux NET4.0 for Linux 2.4
* Sep 27 13:52:18 user.info kernel: Based upon Swansea University Computer Society NET3.039
* Sep 27 13:52:18 user.warn kernel: Initializing RT netlink socket
* Sep 27 13:52:18 user.warn kernel: Starting kswapd
* Sep 27 13:52:18 user.warn kernel: allocated 32 pages and 32 bhs reserved for the highmem bounces
* Sep 27 13:52:18 user.info kernel: Journalled Block Device driver loaded
* Sep 27 13:52:18 user.info kernel: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
* Sep 27 13:52:18 user.info kernel: devfs: boot_options: 0x1
* Sep 27 13:52:18 user.info kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
* Sep 27 13:52:18 user.info kernel: ACPI: Power Button (FF) [PWRF]
* Sep 27 13:52:18 user.info kernel: ACPI: Processor [CPU1] (supports C1, 2 performance states, 8 throttling states)
* Sep 27 13:52:18 user.info kernel: ACPI: Processor [CPU2] (supports C1, 2 performance states, 8 throttling states)
* Sep 27 13:52:18 user.warn kernel: pty: 256 Unix98 ptys configured
* Sep 27 13:52:18 user.info kernel: Real Time Clock Driver v1.10f
* Sep 27 13:52:18 user.info kernel: Floppy drive(s): fd0 is 1.44M
* Sep 27 13:52:18 user.warn kernel: keyboard: Timeout - AT keyboard not present?(ed)
* Sep 27 13:52:18 user.warn kernel: keyboard: Timeout - AT keyboard not present?(f4)
* Sep 27 13:52:18 user.info kernel: FDC 0 is a post-1991 82077
* Sep 27 13:52:18 user.warn kernel: RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
* Sep 27 13:52:18 user.info kernel: loop: loaded (max 8 devices)
* Sep 27 13:52:18 user.info kernel: Intel(R) PRO/1000 Network Driver - version 7.3.20-k4
* Sep 27 13:52:18 user.info kernel: Copyright (c) 1999-2006 Intel Corporation.
* Sep 27 13:52:18 user.info kernel: dgrs: SW=$Id: dgrs.c,v 1.13 2000/06/06 04:07:00 rick Exp $ FW=Build 550 11/16/96 03:45:15
* Sep 27 13:52:18 user.warn kernel: FW Version=$Version$
* Sep 27 13:52:18 user.info kernel: pcnet32.c:v1.30h 06.24.2004 tsbogend@alpha.franken.de
* Sep 27 13:52:18 user.info kernel: ThunderLAN driver v1.15
* Sep 27 13:52:18 user.info kernel: TLAN: 0 devices installed, PCI: 0 EISA: 0
* Sep 27 13:52:18 user.info kernel: dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
* Sep 27 13:52:18 user.info kernel: ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
* Sep 27 13:52:18 user.notice kernel: Intel(R) PRO/100 Network Driver - version 2.3.43-k1
* Sep 27 13:52:18 user.notice kernel: Copyright (c) 2004 Intel Corporation
* Sep 27 13:52:18 user.notice kernel:
* Sep 27 13:52:18 user.debug kernel: e100: selftest OK.
* Sep 27 13:52:18 user.notice kernel: e100: eth0: Intel(R) PRO/100 Network Connection
* Sep 27 13:52:18 user.notice kernel: Hardware receive checksums enabled
* Sep 27 13:52:18 user.notice kernel:
* Sep 27 13:52:18 user.warn kernel: sk98lin: No adapter found.
* Sep 27 13:52:18 user.info kernel: forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.50.
* Sep 27 13:52:18 user.info kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
* Sep 27 13:52:18 user.info kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
* Sep 27 13:52:18 user.info kernel: ICH6: IDE controller at PCI slot 00:1f.1
* Sep 27 13:52:18 user.info kernel: ICH6: chipset revision 3
* Sep 27 13:52:18 user.info kernel: ICH6: not 100% native mode: will probe irqs later
* Sep 27 13:52:18 user.info kernel: ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:pio, hdb:pio
* Sep 27 13:52:18 user.info kernel: ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio
* Sep 27 13:52:18 user.warn kernel: hda: TRANSCEND 032M, ATA DISK drive
* Sep 27 13:52:18 user.warn kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
* Sep 27 13:52:18 user.warn kernel: hda: attached ide-disk driver.
* Sep 27 13:52:18 user.info kernel: hda: 63488 sectors (33 MB) w/2KiB Cache, CHS=496/4/32
* Sep 27 13:52:18 user.info kernel: Partition check:
* Sep 27 13:52:18 user.info kernel: /dev/ide/host0/bus0/target0/lun0: p1 p2
* Sep 27 13:52:18 user.info kernel: SCSI subsystem driver Revision: 1.00
* Sep 27 13:52:18 user.info kernel: Loading Adaptec I2O RAID: Version 2.4 Build 5
* Sep 27 13:52:18 user.info kernel: Detecting Adaptec I2O RAID controllers.
* Sep 27 13:52:18 user.info kernel: Red Hat/Adaptec aacraid driver (1.1-3 Aug 12 2007 09:05:44)
* Sep 27 13:52:18 user.warn kernel: scsi: Detection failed (no card)
* Sep 27 13:52:18 user.notice kernel: megaraid: v2.10.10.1 (Release Date: Thu Jan 27 16:19:44 EDT 2005)
* Sep 27 13:52:18 user.warn kernel: GDT-HA: Storage RAID Controller Driver. Version: 3.04
* Sep 27 13:52:18 user.warn kernel: GDT-HA: Found 0 PCI Storage RAID Controllers
* Sep 27 13:52:18 user.warn kernel: 3ware Storage Controller device driver for Linux v1.02.00.037.
* Sep 27 13:52:18 user.notice kernel: scsi1 : Found a 3ware Storage Controller at 0xbc00, IRQ: 3, P-chip: 1.3
* Sep 27 13:52:18 user.info kernel: scsi1 : 3ware Storage Controller
* Sep 27 13:52:18 user.warn kernel: Vendor: 3ware Model: Logical Disk 0 Rev: 1.0
* Sep 27 13:52:18 user.warn kernel: Type: Direct-Access ANSI SCSI revision: 00
* Sep 27 13:52:18 user.debug kernel:
* Sep 27 13:52:18 user.debug kernel: PCI(00:1f.2): version 1.05
* Sep 27 13:52:18 user.debug kernel: PCI: Setting latency timer of device 00:1f.2 to 64
* Sep 27 13:52:18 user.info kernel: ata1: SATA max UDMA/133 cmd 0xEC00 ctl 0xE802 bmdma 0xDC00 irq 10
* Sep 27 13:52:18 user.info kernel: ata2: SATA max UDMA/133 cmd 0xE400 ctl 0xE002 bmdma 0xDC08 irq 10
* Sep 27 13:52:18 user.debug kernel: ata1: dev 0 cfg 49:0f00 82:0210 83:4010 84:4000 85:0000 86:0000 87:4000 88:0407
* Sep 27 13:52:18 user.info kernel: ata1: dev 0 ATAPI, max UDMA/33
* Sep 27 13:52:18 user.debug kernel: ata1: dev 1 cfg 49:2f00 82:346b 83:7d01 84:4023 85:3469 86:3c01 87:4023 88:207f
* Sep 27 13:52:18 user.info kernel: ata1: dev 1 ATA-7, max UDMA/133, 976773168 sectors: LBA48
* Sep 27 13:52:18 user.info kernel: ata1: dev 0 configured for UDMA/33
* Sep 27 13:52:18 user.info kernel: ata1: dev 1 configured for UDMA/33
* Sep 27 13:52:18 user.warn kernel: ATA: abnormal status 0x7F on port 0xE407
* Sep 27 13:52:18 user.err kernel: ata2: disabling port
* Sep 27 13:52:18 user.info kernel: scsi2 : ata_piix
* Sep 27 13:52:18 user.info kernel: scsi3 : ata_piix
* Sep 27 13:52:18 user.warn kernel: Vendor: ATA Model: ST3500630AS Rev: 3.AA
* Sep 27 13:52:18 user.warn kernel: Type: Direct-Access ANSI SCSI revision: 05
* Sep 27 13:52:18 user.warn kernel: Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
* Sep 27 13:52:18 user.warn kernel: Attached scsi disk sdb at scsi2, channel 0, id 1, lun 0
* Sep 27 13:52:18 user.warn kernel: SCSI device sda: 976771120 512-byte hdwr sectors (500107 MB)
* Sep 27 13:52:18 user.info kernel: /dev/scsi/host1/bus0/target0/lun0: p1
* Sep 27 13:52:18 user.warn kernel: SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB)
* Sep 27 13:52:18 user.info kernel: /dev/scsi/host2/bus0/target1/lun0: p1
* Sep 27 13:52:18 user.info kernel: raw1394: /dev/raw1394 device initialized
* Sep 27 13:52:18 user.info kernel: sbp2: $Rev: 1074 $ Ben Collins
* Sep 27 13:52:18 user.err kernel: ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
* Sep 27 13:52:18 user.info kernel: usb.c: registered new driver usbdevfs
* Sep 27 13:52:18 user.info kernel: usb.c: registered new driver hub
* Sep 27 13:52:18 user.debug kernel: PCI: Setting latency timer of device 00:1d.7 to 64
* Sep 27 13:52:18 user.info kernel: ehci_hcd 00:1d.7: PCI device 8086:265c
* Sep 27 13:52:18 user.info kernel: ehci_hcd 00:1d.7: irq 9, pci mem f8815000
* Sep 27 13:52:18 user.info kernel: usb.c: new USB bus registered, assigned bus number 1
* Sep 27 13:52:18 user.info kernel: ehci_hcd 00:1d.7: enabled 64bit PCI DMA
* Sep 27 13:52:18 user.debug kernel: PCI: cache line size of 128 is not supported by device 00:1d.7
* Sep 27 13:52:18 user.info kernel: ehci_hcd 00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
* Sep 27 13:52:18 user.info kernel: hub.c: USB hub found
* Sep 27 13:52:18 user.info kernel: hub.c: 8 ports detected
* Sep 27 13:52:18 user.info kernel: host/uhci.c: USB Universal Host Controller Interface driver v1.1
* Sep 27 13:52:18 user.debug kernel: PCI: Setting latency timer of device 00:1d.0 to 64
* Sep 27 13:52:18 user.info kernel: host/uhci.c: USB UHCI at I/O 0xcc00, IRQ 9
* Sep 27 13:52:18 user.info kernel: usb.c: new USB bus registered, assigned bus number 2
* Sep 27 13:52:18 user.info kernel: hub.c: USB hub found
* Sep 27 13:52:18 user.info kernel: hub.c: 2 ports detected
* Sep 27 13:52:18 user.debug kernel: PCI: Setting latency timer of device 00:1d.1 to 64
* Sep 27 13:52:18 user.info kernel: host/uhci.c: USB UHCI at I/O 0xd000, IRQ 10
* Sep 27 13:52:18 user.info kernel: usb.c: new USB bus registered, assigned bus number 3
* Sep 27 13:52:18 user.info kernel: hub.c: USB hub found
* Sep 27 13:52:18 user.info kernel: hub.c: 2 ports detected
* Sep 27 13:52:18 user.debug kernel: PCI: Setting latency timer of device 00:1d.2 to 64
* Sep 27 13:52:18 user.info kernel: host/uhci.c: USB UHCI at I/O 0xd400, IRQ 5
* Sep 27 13:52:18 user.info kernel: usb.c: new USB bus registered, assigned bus number 4
* Sep 27 13:52:18 user.info kernel: hub.c: USB hub found
* Sep 27 13:52:18 user.info kernel: hub.c: 2 ports detected
* Sep 27 13:52:18 user.debug kernel: PCI: Setting latency timer of device 00:1d.3 to 64
* Sep 27 13:52:18 user.info kernel: host/uhci.c: USB UHCI at I/O 0xd800, IRQ 11
* Sep 27 13:52:18 user.info kernel: usb.c: new USB bus registered, assigned bus number 5
* Sep 27 13:52:18 user.info kernel: hub.c: USB hub found
* Sep 27 13:52:18 user.info kernel: hub.c: 2 ports detected
* Sep 27 13:52:18 user.info kernel: usb.c: registered new driver usbkbd
* Sep 27 13:52:18 user.info kernel: usbkbd.c: :USB HID Boot Protocol keyboard driver
* Sep 27 13:52:18 user.info kernel: Initializing USB Mass Storage driver.
* Sep 27 13:52:18 user.info kernel: usb.c: registered new driver usb-storage
* Sep 27 13:52:18 user.info kernel: USB Mass Storage support registered.
* Sep 27 13:52:18 user.info kernel: NET4: Linux TCP/IP 1.0 for NET4.0
* Sep 27 13:52:18 user.info kernel: IP Protocols: ICMP, UDP, TCP
* Sep 27 13:52:18 user.info kernel: IP: routing cache hash table of 8192 buckets, 64Kbytes
* Sep 27 13:52:18 user.info kernel: TCP: Hash tables configured (established 262144 bind 65536)
* Sep 27 13:52:18 user.info kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
* Sep 27 13:52:18 user.notice kernel: RAMDISK: NASLite file system found at block 0
* Sep 27 13:52:18 user.warn kernel: <6>Freeing initrd memory: 1962k freed
* Sep 27 13:52:18 user.warn kernel: EXT2-fs warning: checktime reached, running e2fsck is recommended
* Sep 27 13:52:18 user.warn kernel: esystem).
* Sep 27 13:52:18 user.info kernel: Mounted devfs on /dev
* Sep 27 13:52:18 user.info kernel: Freeing unused kernel memory: 540k freed
* Sep 27 13:52:18 user.err kernel: e100: eth0 NIC Link is Up 100 Mbps Full duplex
* Sep 27 13:52:18 user.info kernel: kjournald starting. Commit interval 5 seconds
* Sep 27 13:52:18 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal
* Sep 27 13:52:18 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
* Sep 27 13:52:18 user.info kernel: kjournald starting. Commit interval 5 seconds
* Sep 27 13:52:18 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,17), internal journal
* Sep 27 13:52:18 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.


NASLite-2 HDD v2.06 10-2007
Content updated every 1 min.
Last update Sun Sep 27 14:00:01 UTC 2009.

PieterB

No reason to be alarmed yet

Check SMART for the drive in question and if all looks good then you have nothing to worry about. Next, park the drive (--) using the admin menu, reboot and do a complete filesystem check and repair including checking for bad blocks. Let if complete the cycle, set the drive back to (RW), reboot and all will be back to normal.

Hope that helps.

Funny, that's just what I was going to say!

Mike

Thanks, It seems that S.M.A.R.T. is not available on the RAID-1 array on the 8006-2LP controller. I did a file system check on that array, and there were no bad blocks or other anomalies, it seems.
Still the last part of the syslog doesn't look good -again:

# Sep 27 13:52:18 user.warn kernel: EXT2-fs warning: checktime reached, running e2fsck is recommended
# Sep 27 13:52:18 user.warn kernel: esystem).
# Sep 27 13:52:18 user.info kernel: Mounted devfs on /dev
# Sep 27 13:52:18 user.info kernel: Freeing unused kernel memory: 540k freed
# Sep 27 13:52:18 user.err kernel: e100: eth0 NIC Link is Up 100 Mbps Full duplex
# Sep 27 13:52:18 user.info kernel: kjournald starting. Commit interval 5 seconds
# Sep 27 13:52:18 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal
# Sep 27 13:52:18 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
# Sep 27 13:52:18 user.info kernel: kjournald starting. Commit interval 5 seconds
# Sep 27 13:52:18 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,17), internal journal
# Sep 27 13:52:18 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
# Sep 27 14:39:33 user.debug kernel: hw tcp v4 csum failed
# Sep 27 14:39:33 user.debug kernel: hw tcp v4 csum failed
# Sep 27 14:39:33 user.debug kernel: hw tcp v4 csum failed
# Sep 27 14:39:33 user.debug kernel: hw tcp v4 csum failed
# Sep 27 14:39:33 user.debug kernel: hw tcp v4 csum failed
# Sep 27 14:39:33 user.debug kernel: hw tcp v4 csum failed
# Sep 27 14:39:33 user.debug kernel: hw tcp v4 csum failed
# Sep 27 14:39:33 user.debug kernel: hw tcp v4 csum failed
# Sep 27 14:39:33 user.debug kernel: hw tcp v4 csum failed
# Sep 27 14:39:33 user.debug kernel: hw tcp v4 csum failed
# Sep 27 14:42:03 user.warn kernel: NET: 28 messages suppressed.
# Sep 27 14:42:03 user.debug kernel: hw tcp v4 csum failed
# Sep 27 14:42:03 user.debug kernel: hw tcp v4 csum failed
# Sep 27 14:42:03 user.debug kernel: hw tcp v4 csum failed
# Sep 27 14:42:03 user.debug kernel: hw tcp v4 csum failed
# Sep 27 14:42:03 user.debug kernel: hw tcp v4 csum failed
# Sep 27 14:42:03 user.debug kernel: hw tcp v4 csum failed
# Sep 27 14:42:03 user.debug kernel: hw tcp v4 csum failed
# Sep 27 14:42:03 user.debug kernel: hw tcp v4 csum failed
# Sep 27 14:42:03 user.debug kernel: hw tcp v4 csum failed
# Sep 27 14:42:03 user.debug kernel: hw tcp v4 csum failed
# Sep 27 15:45:53 user.warn kernel: NET: 12 messages suppressed.
# Sep 27 15:45:53 user.debug kernel: hw tcp v4 csum failed
# Sep 27 15:45:53 user.debug kernel: hw tcp v4 csum failed
# Sep 27 15:45:53 user.debug kernel: hw tcp v4 csum failed
# Sep 27 15:45:53 user.debug kernel: hw tcp v4 csum failed
# Sep 27 15:45:53 user.debug kernel: hw tcp v4 csum failed
# Sep 27 15:45:53 user.debug kernel: hw tcp v4 csum failed
# Sep 27 15:45:53 user.debug kernel: hw tcp v4 csum failed
# Sep 27 15:45:53 user.debug kernel: hw tcp v4 csum failed
# Sep 27 15:45:53 user.debug kernel: hw tcp v4 csum failed
# Sep 27 15:45:53 user.debug kernel: hw tcp v4 csum failed

This is the Storage log:

Disk-1 Hardware Details:

MODEL: 3ware Logical Disk 0, v.1.0
INTERFACE: SCSI, HOST-1, BUS-0, TARGET-0, LUN-0

Filesystem Details:

tune2fs 1.27 (8-Mar-2002)
Filesystem volume name: NASLite-SE000160
Last mounted on:
Filesystem UUID: 6bf97d82-99e1-4628-8c24-66da3b2838e5
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal filetype needs_recovery sparse_super large_file
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 61166016
Block count: 122093568
Reserved block count: 0
Free blocks: 41818444
Free inodes: 61118109
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16416
Inode blocks per group: 513
Last mount time: Sun Sep 27 13:52:15 2009
Last write time: Sun Sep 27 19:13:02 2009
Mount count: 20
Maximum mount count: 39
Last checked: Mon May 25 23:08:21 2009
Check interval: 15552000 (6 months)
Next check after: Sat Nov 21 23:08:21 2009
Reserved blocks uid: 0 (user admin)
Reserved blocks gid: 0 (group admin)
First inode: 11
Inode size: 128
Journal UUID:
Journal inode: 8
Journal device: 0x0000
First orphan inode: 0

I have a spare, which is on a SATA connector of the mobo:

Disk-2 Hardware Details:

MODEL: ATA ST3500630AS, v.3.AA
INTERFACE: SCSI, HOST-2, BUS-0, TARGET-1, LUN-0

Filesystem Details:

tune2fs 1.27 (8-Mar-2002)
Filesystem volume name: NASLite-SE000160
Last mounted on:
Filesystem UUID: 9236a7a8-f136-4561-9088-b81d67e74f3a
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal filetype needs_recovery sparse_super large_file
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 61166016
Block count: 122093568
Reserved block count: 0
Free blocks: 42976980
Free inodes: 61118454
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16416
Inode blocks per group: 513
Last mount time: Sun Sep 27 13:52:15 2009
Last write time: Sun Sep 27 18:30:20 2009
Mount count: 7
Maximum mount count: 20
Last checked: Tue Jul 21 10:58:28 2009
Check interval: 15552000 (6 months)
Next check after: Sun Jan 17 10:58:28 2010
Reserved blocks uid: 0 (user admin)
Reserved blocks gid: 0 (group admin)
First inode: 11
Inode size: 128
Journal UUID:
Journal inode: 8
Journal device: 0x0000
First orphan inode: 0

Thanks for looking into these logs, guys

PieterB

The "debug kernel: hw tcp v4 csum failed" errors are network related and are usually caused by the interface receiving packets with bad checksums. Normally the only consequence is reduced network performance, but it can be annoying - especially when looking at the syslog. Causes can be the network interface, the cable, the switch or a specific port. I'd start by using a different cable and a different port on the switch.

All it took was readjusting the cable connector, it seems. Since I have upgraded the system with a second 3-Ware 8006-2LP controller, I haven't done the file check yet.

It's so funny that, with NASLite running so smoothly over a couple of years, you tend to forget the functionality of the admin menu. And how well it works.

PieterB