NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Thu Mar 28, 2024 2:15 pm

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 12 posts ] 
Author Message
 Post subject: Boot Log and System Log
PostPosted: Tue Jan 19, 2010 9:28 am 
Offline

Joined: Sun Mar 01, 2009 12:19 pm
Posts: 54
In NASLite-2 is there a way to look at system logs? It looks like the log displayed in the http GUI is just for boot messages.

I have no doubt this topic has been covered but I have not been able to find an answer in my searches.

Thank you,
John


Top
 Profile  
 
PostPosted: Tue Jan 19, 2010 9:58 am 
Offline

Joined: Sat Nov 19, 2005 6:39 pm
Posts: 633
Location: California
The log shown in the browser does keep track of more than boot log, but I am not sure how extensive the entries get. I have seen disk errors and network issues reported long after a boot. To test, disconnect/re-connect the network cable and check the log again.


Top
 Profile  
 
PostPosted: Tue Jan 19, 2010 11:29 am 
Offline

Joined: Sun Apr 02, 2006 9:05 pm
Posts: 1688
Location: Up State NY in the USA!!!!
Unplugging the NIC cable will show in the network log at the bottom of that page, not in the boot log.

Mike


Top
 Profile  
 
PostPosted: Tue Jan 19, 2010 11:49 am 
Offline

Joined: Sun Mar 01, 2009 12:19 pm
Posts: 54
Is there a real-time log that can be accessed?


Top
 Profile  
 
PostPosted: Tue Jan 19, 2010 5:54 pm 
Offline

Joined: Sat Nov 19, 2005 6:39 pm
Posts: 633
Location: California
The real-time log is in RAM ... and you can only access what the http browser pages provide. Those pages are updated per the interval you choose. And below please find a copy of my Syslog page which illustrates the LOST LINK error I talked about above (sorry, Mike).

I disconnected the cable twice. Once for only a few seconds. But the next update did not show the problem. Then, on a second attempt 4hrs20 minutes later, I tried again and left the cable disconnected across two of the 15 minute update intervals ... so it is sort of "real-time" ... but notice how after the second "problem" *BOTH* errors are reported.

Also note this is an older version (2.06) of NL2, rather than the current 2.6 (Core3). The new version may behave differently, but I suspect it would do the same.


Attachments:
Syslog_NIC_Error.jpg
Syslog_NIC_Error.jpg [ 520.24 KiB | Viewed 27063 times ]
Top
 Profile  
 
PostPosted: Tue Jan 19, 2010 5:58 pm 
Offline

Joined: Sat Nov 19, 2005 6:39 pm
Posts: 633
Location: California
P.S.: The current entry (after one more update) reports the link is back up (of course! ... else I would not have been able to get the above screen shot)

Quote:
Jan 20 00:54:35 user.info kernel: e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX


Top
 Profile  
 
PostPosted: Tue Jan 19, 2010 6:15 pm 
Offline

Joined: Sun Apr 02, 2006 9:05 pm
Posts: 1688
Location: Up State NY in the USA!!!!
Why are you sorry? I miss that, I was wrong, no big deal. I don't have all the answers here. :D

I also don't have any entries in my logs since the machine was reboot after system maintainence in November. Zero errors = zero log entries it would appear. I seldom if ever look at my logs.


This is my log at present:

* Nov 22 22:02:20 [3] klogd started: BusyBox v1.01 (2008.07.26-02:54+0000)
* Nov 22 22:02:20 [2] zing CPU#0
* Nov 22 22:02:20 [4] Detected 2000.002 MHz processor.
* Nov 22 22:02:20 [4] Console: colour VGA+ 80x25
* Nov 22 22:02:20 [4] Calibrating delay loop. 3984.58 BogoMIPS
* Nov 22 22:02:20 [2] Memory: 1027020k/1047808k available (2325k kernel code, 20400k reserved, 680k data, 556k init, 130304k highmem)
* Nov 22 22:02:20 [2] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
* Nov 22 22:02:20 [2] Inode cache hash table entries: 65536 (order: 7, 524288 bytes)
* Nov 22 22:02:20 [2] Mount cache hash table entries: 512 (order: 0, 4096 bytes)
* Nov 22 22:02:20 [2] Buffer cache hash table entries: 65536 (order: 6, 262144 bytes)
* Nov 22 22:02:20 [4] Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
* Nov 22 22:02:20 [2] CPU: Trace cache: 12K uops, L1 D cache: 8K
* Nov 22 22:02:20 [2] CPU: L2 cache: 512K
* Nov 22 22:02:20 [2] Intel machine check architecture supported.
* Nov 22 22:02:20 [2] Intel machine check reporting enabled on CPU#0.
* Nov 22 22:02:20 [1] CPU: After generic, caps: 3febfbff 00000000 00000000 00000000
* Nov 22 22:02:20 [1] CPU: Common caps: 3febfbff 00000000 00000000 00000000
* Nov 22 22:02:20 [4] CPU: Intel(R) Pentium(R) 4 CPU 2.00GHz stepping 04
* Nov 22 22:02:20 [2] Enabling fast FPU save and restore. done.
* Nov 22 22:02:20 [2] Enabling unmasked SIMD FPU exception support. done.
* Nov 22 22:02:20 [2] Checking 'hlt' instruction. OK.
* Nov 22 22:02:20 [4] POSIX conformance testing by UNIFIX
* Nov 22 22:02:20 [4] enabled ExtINT on CPU#0
* Nov 22 22:02:20 [4] ESR value before enabling vector: 00000000
* Nov 22 22:02:20 [4] ESR value after enabling vector: 00000000
* Nov 22 22:02:20 [4] ENABLING IO-APIC IRQs
* Nov 22 22:02:20 [1] init IO_APIC IRQs
* Nov 22 22:02:20 [1] IO-APIC (apicid-pin) 1-0, 1-16, 1-17, 1-18, 1-19, 1-20, 1-21, 1-22, 1-23 not connected.
* Nov 22 22:02:20 [2] TIMER: vector=0x31 pin1=2 pin2=-1
* Nov 22 22:02:20 [4] Using local APIC timer interrupts.
* Nov 22 22:02:20 [4] calibrating APIC timer .
* Nov 22 22:02:20 [4] . CPU clock speed is 1999.9882 MHz.
* Nov 22 22:02:20 [4] . host bus clock speed is 99.9992 MHz.
* Nov 22 22:02:20 [4] cpu: 0, clocks: 999992, slice: 499996
* Nov 22 22:02:20 [4] CPU0
* Nov 22 22:02:20 [4] mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
* Nov 22 22:02:20 [4] mtrr: detected mtrr type: Intel
* Nov 22 22:02:20 [2] ACPI: Subsystem revision 20040326
* Nov 22 22:02:20 [2] PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=2
* Nov 22 22:02:20 [2] PCI: Using configuration type 1
* Nov 22 22:02:20 [2] ACPI: Interpreter enabled
* Nov 22 22:02:20 [2] ACPI: Using IOAPIC for interrupt routing
* Nov 22 22:02:20 [2] ACPI: System [ACPI] (supports S0 S1 S4 S5)
* Nov 22 22:02:20 [2] ACPI: PCI Root Bridge [PCI0] (00:00)
* Nov 22 22:02:20 [4] PCI: Probing PCI hardware (bus 00)
* Nov 22 22:02:20 [2] PCI: Ignoring BAR0-3 of IDE controller 00:1f.1
* Nov 22 22:02:20 [4] Transparent bridge - PCI device 8086:244e
* Nov 22 22:02:20 [1] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
* Nov 22 22:02:20 [1] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
* Nov 22 22:02:20 [2] ACPI: Power Resource [URP1] (off)
* Nov 22 22:02:20 [2] ACPI: Power Resource [URP2] (off)
* Nov 22 22:02:20 [2] ACPI: Power Resource [FDDP] (off)
* Nov 22 22:02:20 [2] ACPI: Power Resource [LPTP] (off)
* Nov 22 22:02:20 [4] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 *11 12 14 15)
* Nov 22 22:02:20 [4] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 *7 9 10 11 12 14 15)
* Nov 22 22:02:20 [4] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 7 9 10 11 12 14 15)
* Nov 22 22:02:20 [4] ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 7 9 10 11 12 14 15)
* Nov 22 22:02:20 [4] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 *4 5 6 7 9 10 11 12 14 15)
* Nov 22 22:02:20 [4] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
* Nov 22 22:02:20 [4] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
* Nov 22 22:02:20 [4] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
* Nov 22 22:02:20 [2] PCI: Probing PCI hardware
* Nov 22 22:02:20 [1] 00:00:01[A] -> 1-16 -> IRQ 16 level low
* Nov 22 22:02:20 [1] 00:00:01[B] -> 1-17 -> IRQ 17 level low
* Nov 22 22:02:20 [1] 00:00:1d[B] -> 1-19 -> IRQ 19 level low
* Nov 22 22:02:20 [1] 00:00:1d[C] -> 1-18 -> IRQ 18 level low
* Nov 22 22:02:20 [1] 00:00:1d[D] -> 1-23 -> IRQ 23 level low
* Nov 22 22:02:20 [1] 00:02:08[A] -> 1-20 -> IRQ 20 level low
* Nov 22 22:02:20 [1] 00:02:00[A] -> 1-21 -> IRQ 21 level low
* Nov 22 22:02:20 [1] 00:02:00[B] -> 1-22 -> IRQ 22 level low
* Nov 22 22:02:20 [1] number of MP IRQ sources: 15.
* Nov 22 22:02:20 [1] number of IO-APIC #1 registers: 24.
* Nov 22 22:02:20 [2] testing the IO APIC.
* Nov 22 22:02:20 [4]
* Nov 22 22:02:20 [1] IO APIC #1
* Nov 22 22:02:20 [1] register #00: 01000000
* Nov 22 22:02:20 [1] . : physical APIC id: 01
* Nov 22 22:02:20 [1] . : Delivery Type: 0
* Nov 22 22:02:20 [1] . : LTS : 0
* Nov 22 22:02:20 [1] register #01: 00178020
* Nov 22 22:02:20 [1] . : max redirection entries: 0017
* Nov 22 22:02:20 [1] . : PRQ implemented: 1
* Nov 22 22:02:20 [1] . : IO APIC version: 0020
* Nov 22 22:02:20 [1] register #02: 00000000
* Nov 22 22:02:20 [1] . : arbitration: 00
* Nov 22 22:02:20 [1] register #03: 00000001
* Nov 22 22:02:20 [1] . : Boot DT : 1
* Nov 22 22:02:20 [1] IRQ redirection table:
* Nov 22 22:02:20 [1] NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
* Nov 22 22:02:20 [1] 00 000 00 1 0 0 0 0 0 2 00
* Nov 22 22:02:20 [1] 0 0 1 1 39
* Nov 22 22:02:20 [1] 02 001 01 0 0 0 0 0 1 1 31
* Nov 22 22:02:20 [1] 03 001 01 0 0 0 0 0 1 1 41
* Nov 22 22:02:20 [1] 04 001 01 0 0 0 0 0 1 1 49
* Nov 22 22:02:20 [1] 05 001 01 0 0 0 0 0 1 1 51
* Nov 22 22:02:20 [1] 06 001 01 0 0 0 0 0 1 1 59
* Nov 22 22:02:20 [1] 07 001 01 0 0 0 0 0 1 1 61
* Nov 22 22:02:20 [1] 08 001 01 0 0 0 0 0 1 1 69
* Nov 22 22:02:20 [1] 09 001 01 0 1 0 0 0 1 1 71
* Nov 22 22:02:20 [1] 0a 001 01 0 0 0 0 0 1 1 79
* Nov 22 22:02:20 [1] 0b 001 01 0 0 0 0 0 1 1 81
* Nov 22 22:02:20 [1] 0c 001 01 0 0 0 0 0 1 1 89
* Nov 22 22:02:20 [1] 0d 001 01 0 0 0 0 0 1 1 91
* Nov 22 22:02:20 [1] 0e 001 01 0 0 0 0 0 1 1 99
* Nov 22 22:02:20 [1] 0f 001 01 0 0 0 0 0 1 1 A1
* Nov 22 22:02:20 [1] 10 001 01 1 1 0 1 0 1 1 A9
* Nov 22 22:02:20 [1] 11 001 01 1 1 0 1 0 1 1 B1
* Nov 22 22:02:20 [1] 12 001 01 1 1 0 1 0 1 1 C1
* Nov 22 22:02:20 [1] 13 001 01 1 1 0 1 0 1 1 B9
* Nov 22 22:02:20 [1] 14 001 01 1 1 0 1 0 1 1 D1
* Nov 22 22:02:20 [1] 15 001 01 1 1 0 1 0 1 1 D9
* Nov 22 22:02:20 [1] 16 001 01 1 1 0 1 0 1 1 E1
* Nov 22 22:02:20 [1] 17 001 01 1 1 0 1 0 1 1 C9
* Nov 22 22:02:20 [1] IRQ to pin mappings:
* Nov 22 22:02:20 [1] IRQ0 -> 0:2
* Nov 22 22:02:20 [1] IRQ1 -> 0:1
* Nov 22 22:02:20 [1] IRQ3 -> 0:3
* Nov 22 22:02:20 [1] IRQ4 -> 0:4
* Nov 22 22:02:20 [1] IRQ5 -> 0:5
* Nov 22 22:02:20 [1] IRQ6 -> 0:6
* Nov 22 22:02:20 [1] IRQ7 -> 0:7
* Nov 22 22:02:20 [1] IRQ8 -> 0:8
* Nov 22 22:02:20 [1] IRQ9 -> 0:9
* Nov 22 22:02:20 [1] IRQ10 -> 0:10
* Nov 22 22:02:20 [1] IRQ11 -> 0:11
* Nov 22 22:02:20 [1] IRQ12 -> 0:12
* Nov 22 22:02:20 [1] IRQ13 -> 0:13
* Nov 22 22:02:20 [1] IRQ14 -> 0:14
* Nov 22 22:02:20 [1] IRQ15 -> 0:15
* Nov 22 22:02:20 [1] IRQ16 -> 0:16
* Nov 22 22:02:20 [1] IRQ17 -> 0:17
* Nov 22 22:02:20 [1] IRQ18 -> 0:18
* Nov 22 22:02:20 [1] IRQ19 -> 0:19
* Nov 22 22:02:20 [1] IRQ20 -> 0:20
* Nov 22 22:02:20 [1] IRQ21 -> 0:21
* Nov 22 22:02:20 [1] IRQ22 -> 0:22
* Nov 22 22:02:20 [1] IRQ23 -> 0:23
* Nov 22 22:02:20 [2] done.
* Nov 22 22:02:20 [2] PCI: Using ACPI for IRQ routing
* Nov 22 22:02:20 [2] Linux NET4.0 for Linux 2.4
* Nov 22 22:02:20 [2] Based upon Swansea University Computer Society NET3.039
* Nov 22 22:02:20 [4] Initializing RT netlink socket
* Nov 22 22:02:20 [4] Starting kswapd
* Nov 22 22:02:20 [4] allocated 32 pages and 32 bhs reserved for the highmem bounces
* Nov 22 22:02:20 [2] Journalled Block Device driver loaded
* Nov 22 22:02:20 [2] devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
* Nov 22 22:02:20 [2] devfs: boot_options: 0x1
* Nov 22 22:02:20 [2] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
* Nov 22 22:02:20 [2] ACPI: Power Button (FF) [PWRF]
* Nov 22 22:02:20 [2] ACPI: Sleep Button (CM) [SLPB]
* Nov 22 22:02:20 [2] ACPI: Processor [CPU1] (supports C1, 8 throttling states)
* Nov 22 22:02:20 [4] pty: 256 Unix98 ptys configured
* Nov 22 22:02:20 [2] Real Time Clock Driver v1.10f
* Nov 22 22:02:20 [4] keyboard: Timeout - AT keyboard not present?(ed)
* Nov 22 22:02:20 [4] keyboard: Timeout - AT keyboard not present?(f4)
* Nov 22 22:02:20 [4] floppy0: no floppy controllers found
* Nov 22 22:02:20 [4] RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
* Nov 22 22:02:20 [2] loop: loaded (max 8 devices)
* Nov 22 22:02:20 [2] Intel(R) PRO/1000 Network Driver - version 7.3.20-k4
* Nov 22 22:02:20 [2] Copyright (c) 1999-2006 Intel Corporation.
* Nov 22 22:02:20 [2] 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
* Nov 22 22:02:20 [4] FW Version=$Version$
* Nov 22 22:02:20 [2] pcnet32.c:v1.30h 06.24.2004 tsbogend@alpha.franken.de
* Nov 22 22:02:20 [2] ThunderLAN driver v1.15
* Nov 22 22:02:20 [2] TLAN: 0 devices installed, PCI: 0 EISA: 0
* Nov 22 22:02:20 [2] dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
* Nov 22 22:02:20 [4] acenic.c: v0.92 08/05/2002 Jes Sorensen, linux-acenic@SunSITE.dk
* Nov 22 22:02:20 [4] http://home.cern.ch/~jes/gige/acenic.html
* Nov 22 22:02:20 [2] eth0: 3Com 3C985 Gigabit Ethernet at 0xff9f8000, irq 17
* Nov 22 22:02:20 [2] Tigon I (Rev. 4), Firmware: 12.4.11, MAC: 00:60:08:21:54:f0
* Nov 22 22:02:20 [2] PCI cache line size set incorrectly (0 bytes) by BIOS/FW, correcting to 16
* Nov 22 22:02:20 [2] PCI bus width: 32 bits, speed: 33MHz, latency: 64 clks
* Nov 22 22:02:20 [2] eth0: Firmware up and running
* Nov 22 22:02:20 [2] ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
* Nov 22 22:02:20 [3] Intel(R) PRO/100 Network Driver - version 2.3.43-k1
* Nov 22 22:02:20 [3] Copyright (c) 2004 Intel Corporation
* Nov 22 22:02:20 [3]
* Nov 22 22:02:20 [1] e100: selftest OK.
* Nov 22 22:02:20 [4] eth0: Optical link UP (Full Duplex, Flow Control: RX)
* Nov 22 22:02:20 [3] e100: eth1: Intel(R) PRO/100 Network Connection
* Nov 22 22:02:20 [3] Hardware receive checksums enabled
* Nov 22 22:02:20 [3]
* Nov 22 22:02:20 [4] sk98lin: No adapter found.
* Nov 22 22:02:20 [2] forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.50.
* Nov 22 22:02:20 [2] Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
* Nov 22 22:02:20 [2] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
* Nov 22 22:02:20 [2] ICH4: IDE controller at PCI slot 00:1f.1
* Nov 22 22:02:20 [4] PCI: Enabling device 00:1f.1 (0005 -> 0007)
* Nov 22 22:02:20 [2] ICH4: chipset revision 1
* Nov 22 22:02:20 [2] ICH4: not 100% native mode: will probe irqs later
* Nov 22 22:02:20 [2] M-DMA at 0xffa0-0xffa7, BIOS settings: hda:pio, hdb:pio
* Nov 22 22:02:20 [2] SiI680: IDE controller at PCI slot 02:00.0
* Nov 22 22:02:20 [2] SiI680: chipset revision 2
* Nov 22 22:02:20 [2] SiI680: not 100% native mode: will probe irqs later
* Nov 22 22:02:20 [2] SiI680: BASE CLOCK == 133
* Nov 22 22:02:20 [2] ide1: MMIO-DMA , BIOS settings: hdc:pio, hdd:pio
* Nov 22 22:02:20 [2] ide2: MMIO-DMA , BIOS settings: hde:pio, hdf:pio
* Nov 22 22:02:20 [4] hda: SanDisk SDCFB-64, CFA DISK drive
* Nov 22 22:02:20 [4] hdc: ST3200822A, ATA DISK drive
* Nov 22 22:02:20 [4] hdd: ST3300831A, ATA DISK drive
* Nov 22 22:02:20 [4] hde: MAXTOR STM3500630A, ATA DISK drive
* Nov 22 22:02:20 [4] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
* Nov 22 22:02:20 [4] ide1 at 0xf8811c80-0xf8811c87,0xf8811c8a on irq 21
* Nov 22 22:02:20 [4] ide2 at 0xf8811cc0-0xf8811cc7,0xf8811cca on irq 21
* Nov 22 22:02:20 [4] hda: attached ide-disk driver.
* Nov 22 22:02:20 [2] hda: 125440 sectors (64 MB) w/1KiB Cache, CHS=490/8/32
* Nov 22 22:02:20 [4] hdc: attached ide-disk driver.
* Nov 22 22:02:20 [4] hdc: host protected area => 1
* Nov 22 22:02:20 [2] hdc: 390721968 sectors (200050 MB) w/8192KiB Cache, CHS=24321/255/63, UDMA(100)
* Nov 22 22:02:20 [4] hdd: attached ide-disk driver.
* Nov 22 22:02:20 [4] hdd: host protected area => 1
* Nov 22 22:02:20 [2] hdd: 586072368 sectors (300069 MB) w/8192KiB Cache, CHS=36481/255/63, UDMA(100)
* Nov 22 22:02:20 [4] hde: attached ide-disk driver.
* Nov 22 22:02:20 [4] hde: host protected area => 1
* Nov 22 22:02:20 [2] hde: 976773168 sectors (500108 MB) w/16384KiB Cache, CHS=60801/255/63, UDMA(100)
* Nov 22 22:02:20 [2] Partition check:
* Nov 22 22:02:20 [2] /dev/ide/host0/bus0/target0/lun0: p1 p2
* Nov 22 22:02:20 [2] /dev/ide/host1/bus0/target0/lun0: p1
* Nov 22 22:02:20 [2] /dev/ide/host1/bus0/target1/lun0: p1
* Nov 22 22:02:20 [2] /dev/ide/host1/bus1/target0/lun0: p1
* Nov 22 22:02:20 [2] SCSI subsystem driver Revision: 1.00
* Nov 22 22:02:20 [2] Loading Adaptec I2O RAID: Version 2.4 Build 5
* Nov 22 22:02:20 [2] Detecting Adaptec I2O RAID controllers.
* Nov 22 22:02:20 [2] Red Hat/Adaptec aacraid driver (1.1-3 Jul 16 2008 21:50:42)
* Nov 22 22:02:20 [4] scsi: Detection failed (no card)
* Nov 22 22:02:20 [3] megaraid: v2.10.10.1 (Release Date: Thu Jan 27 16:19:44 EDT 2005)
* Nov 22 22:02:20 [4] GDT-HA: Storage RAID Controller Driver. Version: 3.04
* Nov 22 22:02:20 [4] GDT-HA: Found 0 PCI Storage RAID Controllers
* Nov 22 22:02:20 [2] scsi1 : SCSI host adapter emulation for IDE ATAPI devices
* Nov 22 22:02:20 [4] 3ware Storage Controller device driver for Linux v1.02.00.037.
* Nov 22 22:02:20 [4] 3w-xxxx: No cards found.
* Nov 22 22:02:20 [1] libata version 1.20 loaded.
* Nov 22 22:02:20 [1] PCI(02:02.0): version 0.9
* Nov 22 22:02:20 [2] ata1: SATA max UDMA/100 cmd 0xF8815880 ctl 0xF881588A bmdma 0xF8815800 irq 18
* Nov 22 22:02:20 [2] ata2: SATA max UDMA/100 cmd 0xF88158C0 ctl 0xF88158CA bmdma 0xF8815808 irq 18
* Nov 22 22:02:20 [1] ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4123 85:3469 86:bc01 87:4123 88:407f
* Nov 22 22:02:20 [2] ata1: dev 0 ATA-8, max UDMA/133, 1465149168 sectors: LBA48
* Nov 22 22:02:20 [2] ata1: dev 0 configured for UDMA/100
* Nov 22 22:02:20 [2] ata2: no device found (phy stat 00000000)
* Nov 22 22:02:20 [2] scsi2 : sata_sil
* Nov 22 22:02:20 [2] scsi3 : sata_sil
* Nov 22 22:02:20 [4] Vendor: ATA Model: ST3750330AS Rev: SD15
* Nov 22 22:02:20 [4] Type: Direct-Access ANSI SCSI revision: 05
* Nov 22 22:02:20 [4] Attached scsi disk sda at scsi2, channel 0, id 0, lun 0
* Nov 22 22:02:20 [4] SCSI device sda: 1465149168 512-byte hdwr sectors (750156 MB)
* Nov 22 22:02:20 [2] /dev/scsi/host2/bus0/target0/lun0: p1
* Nov 22 22:02:20 [2] raw1394: /dev/raw1394 device initialized
* Nov 22 22:02:20 [2] sbp2: $Rev: 1074 $ Ben Collins
* Nov 22 22:02:20 [5] ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
* Nov 22 22:02:20 [2] usb.c: registered new driver usbdevfs
* Nov 22 22:02:20 [2] usb.c: registered new driver hub
* Nov 22 22:02:20 [1] PCI: Setting latency timer of device 00:1d.7 to 64
* Nov 22 22:02:20 [2] ehci_hcd 00:1d.7: PCI device 8086:24cd
* Nov 22 22:02:20 [2] ehci_hcd 00:1d.7: irq 23, pci mem f8817c00
* Nov 22 22:02:20 [2] usb.c: new USB bus registered, assigned bus number 1
* Nov 22 22:02:20 [2] ehci_hcd 00:1d.7: enabled 64bit PCI DMA
* Nov 22 22:02:20 [1] PCI: cache line size of 128 is not supported by device 00:1d.7
* Nov 22 22:02:20 [2] ehci_hcd 00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
* Nov 22 22:02:20 [2] hub.c: USB hub found
* Nov 22 22:02:20 [2] hub.c: 6 ports detected
* Nov 22 22:02:20 [2] host/uhci.c: USB Universal Host Controller Interface driver v1.1
* Nov 22 22:02:20 [1] PCI: Setting latency timer of device 00:1d.0 to 64
* Nov 22 22:02:20 [2] host/uhci.c: USB UHCI at I/O 0xe800, IRQ 16
* Nov 22 22:02:20 [2] usb.c: new USB bus registered, assigned bus number 2
* Nov 22 22:02:20 [2] hub.c: USB hub found
* Nov 22 22:02:20 [2] hub.c: 2 ports detected
* Nov 22 22:02:20 [1] PCI: Setting latency timer of device 00:1d.1 to 64
* Nov 22 22:02:20 [2] host/uhci.c: USB UHCI at I/O 0xe880, IRQ 19
* Nov 22 22:02:20 [2] usb.c: new USB bus registered, assigned bus number 3
* Nov 22 22:02:20 [2] hub.c: USB hub found
* Nov 22 22:02:20 [2] hub.c: 2 ports detected
* Nov 22 22:02:20 [1] PCI: Setting latency timer of device 00:1d.2 to 64
* Nov 22 22:02:20 [2] host/uhci.c: USB UHCI at I/O 0xec00, IRQ 18
* Nov 22 22:02:20 [2] usb.c: new USB bus registered, assigned bus number 4
* Nov 22 22:02:20 [2] hub.c: USB hub found
* Nov 22 22:02:20 [2] hub.c: 2 ports detected
* Nov 22 22:02:20 [2] registered new driver usbkbd
* Nov 22 22:02:20 [2] usbkbd.c: :USB HID Boot Protocol keyboard driver
* Nov 22 22:02:20 [2] Initializing USB Mass Storage driver.
* Nov 22 22:02:20 [2] usb.c: registered new driver usb-storage
* Nov 22 22:02:20 [2] USB Mass Storage support registered.
* Nov 22 22:02:20 [2] NET4: Linux TCP/IP 1.0 for NET4.0
* Nov 22 22:02:20 [2] IP Protocols: ICMP, UDP, TCP
* Nov 22 22:02:20 [2] IP: routing cache hash table of 8192 buckets, 64Kbytes
* Nov 22 22:02:20 [2] TCP: Hash tables configured (established 262144 bind 65536)
* Nov 22 22:02:20 [2] NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
* Nov 22 22:02:20 [3] RAMDISK: NASLite file system found at block 0
* Nov 22 22:02:20 [4] [truncated]
* Nov 22 22:02:20 [4] EXT2-fs warning: checktime reached, running e2fsck is recommended
* Nov 22 22:02:20 [4] VFS: Mounted root (ext2 filesystem).
* Nov 22 22:02:20 [2] Mounted devfs on /dev
* Nov 22 22:02:20 [2] Freeing unused kernel memory: 556k freed
* Nov 22 22:02:20 [2] /dev/ide/host0/bus0/target0/lun0: p1 p2
* Nov 22 22:02:20 [2] /dev/ide/host0/bus0/target0/lun0: p1 p2
* Nov 22 22:02:20 [2] /dev/ide/host0/bus0/target0/lun0: p1 p2
* Nov 22 22:02:20 [4] hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
* Nov 22 22:02:20 [4] hda: drive_cmd: error=0x04 { DriveStatusError }
* Nov 22 22:02:20 [2] /dev/ide/host0/bus0/target0/lun0: p1 p2
* Nov 22 22:02:20 [4] hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
* Nov 22 22:02:20 [4] hda: drive_cmd: error=0x04 { DriveStatusError }
* Nov 22 22:02:20 [2] /dev/ide/host0/bus0/target0/lun0: p1 p2
* Nov 22 22:02:20 [4] hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
* Nov 22 22:02:20 [4] hda: drive_cmd: error=0x04 { DriveStatusError }
* Nov 22 22:02:20 [2] /dev/ide/host0/bus0/target0/lun0: p1 p2
* Nov 22 22:02:20 [1] VFS: Disk change detected on device 03:00
* Nov 22 22:02:20 [2] /dev/ide/host0/bus0/target0/lun0: p1 p2
* Nov 22 22:02:20 [2] /dev/ide/host0/bus0/target0/lun0: p1 p2
* Nov 22 22:02:20 [2] /dev/ide/host0/bus0/target0/lun0: p1 p2
* Nov 22 22:02:20 [4] hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
* Nov 22 22:02:20 [4] hda: drive_cmd: error=0x04 { DriveStatusError }
* Nov 22 22:02:20 [2] /dev/ide/host0/bus0/target0/lun0: p1 p2
* Nov 22 22:02:20 [4] hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
* Nov 22 22:02:20 [4] hda: drive_cmd: error=0x04 { DriveStatusError }
* Nov 22 22:02:20 [2] /dev/ide/host0/bus0/target0/lun0: p1 p2
* Nov 22 22:02:20 [2] kjournald starting. Commit interval 5 seconds
* Nov 22 22:02:20 [2] EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,1), internal journal
* Nov 22 22:02:20 [2] EXT3-fs: mounted filesystem with ordered data mode.
* Nov 22 22:02:20 [2] kjournald starting. Commit interval 5 seconds
* Nov 22 22:02:20 [2] EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,65), internal journal
* Nov 22 22:02:20 [2] EXT3-fs: mounted filesystem with ordered data mode.
* Nov 22 22:02:20 [2] kjournald starting. Commit interval 5 seconds
* Nov 22 22:02:20 [2] EXT3 FS 2.4-0.9.19, 19 August 2002 on ide2(33,1), internal journal
* Nov 22 22:02:20 [2] EXT3-fs: mounted filesystem with ordered data mode.
* Nov 22 22:02:20 [2] kjournald starting. Commit interval 5 seconds
* Nov 22 22:02:20 [2] EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal
* Nov 22 22:02:20 [2] EXT3-fs: mounted filesystem with ordered data mode.

Mike


Top
 Profile  
 
PostPosted: Tue Jan 19, 2010 6:24 pm 
Offline

Joined: Sun Mar 01, 2009 12:19 pm
Posts: 54
georg wrote:
The real-time log is in RAM ... and you can only access what the http browser pages provide. Those pages are updated per the interval you choose.


Where do I choose the interval? Is it in the Telnet menu because I haven't seen it.

Thanks,
John


Top
 Profile  
 
PostPosted: Tue Jan 19, 2010 7:46 pm 
Offline

Joined: Sat Nov 19, 2005 6:39 pm
Posts: 633
Location: California
mikeiver1 wrote:
Why are you sorry? I miss that, I was wrong, no big deal. I don't have all the answers here. :D

I also don't have any entries in my logs since the machine was reboot after system maintainence in November. Zero errors = zero log entries it would appear. I seldom if ever look at my logs.

Mike

I felt "sorry" about having to correct your normally spot-on info :o

Are your "{ DriveReady SeekComplete Error }" and "{ DriveStatusError }" during boot any issue or concern ?


Top
 Profile  
 
PostPosted: Tue Jan 19, 2010 7:49 pm 
Offline

Joined: Sat Nov 19, 2005 6:39 pm
Posts: 633
Location: California
jgkurz wrote:
Where do I choose the interval? Is it in the Telnet menu because I haven't seen it.

Yes. It's in the "Services Configuration Menu" -- option 8 -- "Status Update" (version 2.06, but I don't think it's changed on newer NL versions).


Top
 Profile  
 
PostPosted: Tue Jan 19, 2010 8:11 pm 
Offline

Joined: Sun Apr 02, 2006 9:05 pm
Posts: 1688
Location: Up State NY in the USA!!!!
georg wrote:
...Are your "{ DriveReady SeekComplete Error }" and "{ DriveStatusError }" during boot any issue or concern ?


Not from what I can tell, all the data is still there and I have no issues. Likely just driver stuff in Linux bonking on boot.

Mike


Top
 Profile  
 
PostPosted: Thu Jul 08, 2010 2:11 pm 
Offline

Joined: Sun Mar 01, 2009 12:19 pm
Posts: 54
In the interest of tying out my original post I have been able to see updates to my log. I unplugged the Ethernet cable twice and this was the result with NASLite-M2 1.62 32bit. Looks good!


# Jun 6 08:16:03 [3] sd 1:0:0:0: [sdb] Attached SCSI removable disk
# Jun 6 08:16:21 [2] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
# Jun 6 08:16:33 [2] kjournald starting. Commit interval 5 seconds
# Jun 6 08:16:33 [2] EXT3 FS on sda1, internal journal
# Jun 6 08:16:33 [2] EXT3-fs: mounted filesystem with writeback data mode.
# Jun 8 12:13:50 [2] e1000: eth1 NIC Link is Down
# Jun 8 12:14:03 [2] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
# Jun 8 12:14:08 [2] e1000: eth1 NIC Link is Down
# Jun 8 12:14:10 [2] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX


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

All times are UTC - 5 hours [ DST ]


Who is online

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