NASLite Network Attached Storage

Serious: The boot time of the NASLite box was similar to the boot time of the main Windows XP SP2 system. Less than 90 seconds. Suddenly, as of yesterday, with no changes made, boot time is about 5 minutes. There must be a reason.

Please help and explain. Thanks.

And now, this morning, everything is back to the usual fast boot. Still puzzled.

Apparently, nobody has any idea what is happining, or nobody seems to bother. The first assumption is alarming, the second reassuring. This reasoning as such will keep me in the dark.

I think you failed to post any real detailed information on the problem other than to say it took a long time. My guess based on the VERY LIMITED information you have provided is that there was an FS check being run and so you had to wait for the disk to be mounted for use. What caused the FSCK to be initiated is anyones guess, maybe just a botched shutdown. I can tell you that it will happen again in the future and you will have to wait for it to complete the check before it will mount the drives. This is a good thing as it is keeping your data in order and safe.

And while I am ranting, why are you booting the thing each day? It is hard on the hardware to be doing that, just leave it run.

There, that the reassurance you needed? In the future provide copies of your logs so we can see what the problem might be unless you just want to listen to the crickets in the forums.

Mike

Unfortunately without more info, I don't think anyone could help.

Posting the syslog is a good start

Thank you for responding. The filesystem check was also my guess, but why? I mean what triggers the check? Is this a routine, let's say after 5 times booting?

Anyway, just now I booted the NASLite box, again (after 4 days of 'normal' boot times) l-o-n-g, running smoothly afterwards. I collected the log a couple of minutes after the I-am-ready beeps.

I did not post a log because it seemed overkill, and the answer might have been easy without the log. But if Tony or someone else would look into this log, it will be very much appreciated.

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

And the filesystem log:

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: filetype sparse_super large_file
Filesystem state: not clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 61166016
Block count: 122093568
Reserved block count: 0
Free blocks: 100547820
Free inodes: 61146702
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 Mar 2 14:06:33 2008
Last write time: Sun Mar 2 14:11:22 2008
Mount count: 1
Maximum mount count: 39
Last checked: Sun Mar 2 14:06:33 2008
Check interval: 15552000 (6 months)
Next check after: Fri Aug 29 14:06:33 2008
Reserved blocks uid: 0 (user admin)
Reserved blocks gid: 0 (group admin)
First inode: 11
Inode size: 128

The lines: Indicate that your drive has just been checked and will require to be checked again after 38 more reboots, or six months...

Still, Nick, that does not explain why there are (probably) 2 filesystem checks within one week, or 5 reboots. Thank you though for taking the time to look at the data.

A filesystem check can be issued for many reasons and is not an event that will occur for all drives at the same time. It is possible that one disk got scanned , then a couple of days later the other got scanned. It is also possible that a file was open on a client when the machine was shut down. Although on shutdown NASLite explicitly flushes the buffers and syncs the drives, at times a filesystem fails to unmount cleanly and a check is issued on reboot.

Unless you are having hardware problems, I'd say you are experiencing normal operation and personally, I wouldn't worry much about the delay in boot. That's not to say I wouldn't keep an eye out for anomalies, but it does sound like your setup is running as it should.

Thank you for your comprehensive answer, Tony.

Before posing a question I consult the manual and search the forum -I noticed quite a few dead links. Maybe a FAQ would help you save time.

Quote:
"
And the filesystem log:

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: filetype sparse_super large_file
Filesystem state: not clean
Errors behavior: Continue
"
unquote

What about this line stating a Not Clean file system state?

NASLite-2 marks the drives as not clean during the boot process. If the server powers down incorrectly, i.e. power failure, the drive will still be marked as not clean. When the server powers down properly, the shutdown procedure marks the drive as clean. If the server boots and finds a drive marked as not clean it will be checked at boot.