NASLite Network Attached Storage

After eagerly applying the 1.62 upgrade, I was able to finally have NL see my 5TB. I formatted it, put about 1TB worth of data on it, all the while getting great performance (about 80% of my 1Gb/s NIC).

I had 4x500 PATA's that I took offline once I determined the SATA RAID0 vol was going to work. Everything was still right as rain. I did two things that may or may not have anything to do with this problem. I reinstated one of the 500 PATA's, which kicked my DISK-0 SATA volume to DISK-1, and I had set the time from the default of whatever 2000 to the current day/time. Thinking the reinstating of the 500GB drive was the cause, I took it offline again, but of course that didn't help.

I've tried a thorough scan (that took almost 24 hours), and no problems. The file system is journaled (by default). Attached is the log:

System Message Log:

Feb 23 01:59:37 [3] klogd started: BusyBox v1.12.1 (2009-11-19 21:21:30 UTC)
Feb 23 01:59:37 [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
Feb 23 01:59:37 [2] KERNEL supported cpus:
Feb 23 01:59:37 [2] Intel GenuineIntel
Feb 23 01:59:37 [2] AMD AuthenticAMD
Feb 23 01:59:37 [2] NSC Geode by NSC
Feb 23 01:59:37 [2] Cyrix CyrixInstead
Feb 23 01:59:37 [2] Centaur CentaurHauls
Feb 23 01:59:37 [2] Transmeta GenuineTMx86
Feb 23 01:59:37 [2] Transmeta TransmetaCPU
Feb 23 01:59:37 [2] UMC UMC UMC UMC
Feb 23 01:59:37 [2] BIOS-provided physical RAM map:
Feb 23 01:59:37 [2] BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
Feb 23 01:59:37 [2] BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
Feb 23 01:59:37 [2] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Feb 23 01:59:37 [2] BIOS-e820: 0000000000100000 - 000000001fffc000 (usable)
Feb 23 01:59:37 [2] BIOS-e820: 000000001fffc000 - 000000001ffff000 (ACPI data)
Feb 23 01:59:37 [2] BIOS-e820: 000000001ffff000 - 0000000020000000 (ACPI NVS)
Feb 23 01:59:37 [2] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
Feb 23 01:59:37 [2] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
Feb 23 01:59:37 [2] BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
Feb 23 01:59:37 [2] DMI 2.3 present.
Feb 23 01:59:37 [2] last_pfn = 0x1fffc max_arch_pfn = 0x100000
Feb 23 01:59:37 [2] init_memory_mapping: 0000000000000000-000000001fffc000
Feb 23 01:59:37 [1] 0000000000 - 0000400000 page 4k
Feb 23 01:59:37 [1] 0000400000 - 001fc00000 page 2M
Feb 23 01:59:37 [1] 001fc00000 - 001fffc000 page 4k
Feb 23 01:59:37 [1] kernel direct mapping tables up to 1fffc000 @ 7000-c000
Feb 23 01:59:37 [2] RAMDISK: 0f75d000 - 0ffff80d
Feb 23 01:59:37 [4] ACPI: RSDP 000f6840 00014 (v00 ASUS )
Feb 23 01:59:37 [4] ACPI: RSDT 1fffc000 0002C (v01 ASUS P4S533 42302E31 MSFT 31313031)
Feb 23 01:59:37 [4] ACPI: FACP 1fffc100 00074 (v01 ASUS P4S533 42302E31 MSFT 31313031)
Feb 23 01:59:37 [4] ACPI: DSDT 1fffc180 0255F (v01 ASUS P4S533 00001000 MSFT 0100000B)
Feb 23 01:59:37 [4] ACPI: FACS 1ffff000 00040
Feb 23 01:59:37 [4] ACPI: BOOT 1fffc040 00028 (v01 ASUS P4S533 42302E31 MSFT 31313031)
Feb 23 01:59:37 [3] 0MB HIGHMEM available.
Feb 23 01:59:37 [3] 511MB LOWMEM available.
Feb 23 01:59:37 [2] mapped low ram: 0 - 1fffc000
Feb 23 01:59:37 [2] low ram: 0 - 1fffc000
Feb 23 01:59:37 [2] node 0 low ram: 00000000 - 1fffc000
Feb 23 01:59:37 [2] node 0 bootmap 00001000 - 00005000
Feb 23 01:59:37 [2] (7 early reservations) ==> bootmem [0000000000 - 001fffc000]
Feb 23 01:59:37 [2] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
Feb 23 01:59:37 [2] #1 [0000100000 - 000039b83c] TEXT DATA BSS ==> [0000100000 - 000039b83c]
Feb 23 01:59:37 [2] #2 [000f75d000 - 000ffff80d] RAMDISK ==> [000f75d000 - 000ffff80d]
Feb 23 01:59:37 [2] #3 [000009f400 - 0000100000] BIOS reserved ==> [000009f400 - 0000100000]
Feb 23 01:59:37 [2] #4 [000039c000 - 000039e14c] BRK ==> [000039c000 - 000039e14c]
Feb 23 01:59:37 [2] #5 [0000007000 - 0000008000] PGTABLE ==> [0000007000 - 0000008000]
Feb 23 01:59:37 [2] #6 [0000001000 - 0000005000] BOOTMAP ==> [0000001000 - 0000005000]
Feb 23 01:59:37 [4] Zone PFN ranges:
Feb 23 01:59:37 [4] DMA 0x00000000 -> 0x00001000
Feb 23 01:59:37 [4] Normal 0x00001000 -> 0x0001fffc
Feb 23 01:59:37 [4] HighMem 0x0001fffc -> 0x0001fffc
Feb 23 01:59:37 [4] Movable zone start PFN for each node
Feb 23 01:59:37 [4] early_node_map[2] active PFN ranges
Feb 23 01:59:37 [4] 0: 0x00000000 -> 0x0000009f
Feb 23 01:59:37 [4] 0: 0x00000100 -> 0x0001fffc
Feb 23 01:59:37 [1] On node 0 totalpages: 130971
Feb 23 01:59:37 [1] free_area_init_node: node 0, pgdat c031d560, node_mem_map c1000000
Feb 23 01:59:37 [1] DMA zone: 32 pages used for memmap
Feb 23 01:59:37 [1] DMA zone: 0 pages reserved
Feb 23 01:59:37 [1] DMA zone: 3967 pages, LIFO batch:0
Feb 23 01:59:37 [1] Normal zone: 992 pages used for memmap
Feb 23 01:59:37 [1] Normal zone: 125980 pages, LIFO batch:31
Feb 23 01:59:37 [2] Using APIC driver default
Feb 23 01:59:37 [2] ACPI: PM-Timer IO Port: 0xe408
Feb 23 01:59:37 [2] Found and enabled local APIC!
Feb 23 01:59:37 [1] nr_irqs_gsi: 16
Feb 23 01:59:37 [2] Allocating PCI resources starting at 30000000 (gap: 20000000:dec00000)
Feb 23 01:59:37 [4] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129947
Feb 23 01:59:37 [3] Kernel command line: root=/dev/ram0 rw
Feb 23 01:59:37 [2] Enabling fast FPU save and restore. done.
Feb 23 01:59:37 [2] Enabling unmasked SIMD FPU exception support. done.
Feb 23 01:59:37 [2] Initializing CPU#0
Feb 23 01:59:37 [2] NR_IRQS:288
Feb 23 01:59:37 [4] PID hash table entries: 2048 (order: 11, 8192 bytes)
Feb 23 01:59:37 [4] Fast TSC calibration using PIT
Feb 23 01:59:37 [4] Detected 1815.958 MHz processor.
Feb 23 01:59:37 [4] Console: colour VGA+ 80x25
Feb 23 01:59:37 [2] console [tty0] enabled
Feb 23 01:59:37 [2] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Feb 23 01:59:37 [2] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Feb 23 01:59:37 [2] Initializing HighMem for node 0 (00000000:00000000)
Feb 23 01:59:37 [2] Memory: 507508k/524272k available (1523k kernel code, 16036k reserved, 667k data, 208k init, 0k highmem)
Feb 23 01:59:37 [2] virtual kernel memory layout:
Feb 23 01:59:37 [2] fixmap : 0xfffa9000 - 0xfffff000 ( 344 kB)
Feb 23 01:59:37 [2] pkmap : 0xff800000 - 0xffc00000 (4096
Feb 23 01:59:37 [2] kB)
Feb 23 01:59:37 [2] vmalloc : 0xe07fc000 - 0xff7fe000 ( 496 MB)
Feb 23 01:59:37 [2] lowmem : 0xc0000000 - 0xdfffc000 ( 511 MB)
Feb 23 01:59:37 [2] .init : 0xc0326000 - 0xc035a000 ( 208 kB)
Feb 23 01:59:37 [2] .data : 0xc027cfdb - 0xc0323e14 ( 667 kB)
Feb 23 01:59:37 [2] .text : 0xc0100000 - 0xc027cfdb (1523 kB)
Feb 23 01:59:37 [2] Checking if this processor honours the WP bit even in supervisor mode.Ok.
Feb 23 01:59:37 [2] SLUB: Genslabs=13, HWalign=128, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Feb 23 01:59:37 [2] Calibrating delay loop (skipped), value calculated using timer frequency 3631.91 BogoMIPS (lpj=7263832)
Feb 23 01:59:37 [4] Mount-cache hash table entries: 512
Feb 23 01:59:37 [2] CPU: Trace cache: 12K uops, L1 D cache: 8K
Feb 23 01:59:37 [2] CPU: L2 cache: 512K
Feb 23 01:59:37 [4] CPU: Intel(R) Pentium(R) 4 CPU 1.80GHz stepping 04
Feb 23 01:59:37 [2] Checking 'hlt' instruction. OK.
Feb 23 01:59:37 [2] ACPI: Core revision 20090320
Feb 23 01:59:37 [4] ACPI: setting ELCR to 0200 (from 1e20)
Feb 23 01:59:37 [2] net_namespace: 296 bytes
Feb 23 01:59:37 [2] NET: Registered protocol family 16
Feb 23 01:59:37 [2] ACPI: bus type pci registered
Feb 23 01:59:37 [2] PCI: PCI BIOS revision 2.10 entry at 0xf1580, last bus=1
Feb 23 01:59:37 [2] PCI: Using configuration type 1 for base access
Feb 23 01:59:37 [4] bio: create slab at 0
Feb 23 01:59:37 [1] ACPI: EC: Look up EC in DSDT
Feb 23 01:59:37 [2] ACPI: Interpreter enabled
Feb 23 01:59:37 [2] ACPI: (supports S0 S5)
Feb 23 01:59:37 [2] ACPI: Using PIC for interrupt routing
Feb 23 01:59:37 [2] ACPI: No dock devices found.
Feb 23 01:59:37 [2] ACPI: PCI Root Bridge [PCI0] (0000:00)
Feb 23 01:59:37 [1] pci 0000:00:00.0: reg 10 32bit mmio: [0xe8000000-0xebffffff]
Feb 23 01:59:37 [2] pci 0000:00:02.0: Enabling SiS 96x SMBus
Feb 23 01:59:37 [1] pci 0000:00:02.1: reg 20 io port: [0xe600-0xe61f]
Feb 23 01:59:37 [1] pci 0000:00:02.5: reg 20 io port: [0xd800-0xd80f]
Feb 23 01:59:37 [1] pci 0000:00:09.0: reg 10 io port: [0xa800-0xa8ff]
Feb 23 01:59:37 [1] pci 0000:00:09.0: reg 14 64bit mmio: [0xe5000000-0xe50000ff]
Feb 23 01:59:37 [1] pci 0000:00:09.0: reg 1c 64bit mmio: [0xef000000-0xef7fffff]
Feb 23 01:59:37 [1] pci 0000:00:09.0: reg 30 32bit mmio: [0x000000-0x00ffff]
Feb 23 01:59:37 [1] pci 0000:00:09.0: supports D1 D2
Feb 23 01:59:37 [2] pci 0000:00:09.0: PME# supported from D0 D1 D2 D3hot
Feb 23 01:59:37 [2] pci 0000:00:09.0: PME# disabled
Feb 23 01:59:37 [1] pci 0000:00:0a.0: reg 10 32bit mmio: [0xe4800000-0xe4803fff]
Feb 23 01:59:37 [1] pci 0000:00:0a.0: reg 14 io port: [0xa400-0xa4ff]
Feb 23 01:59:37 [1] pci 0000:00:0a.0: reg 30 32bit mmio: [0x000000-0x01ffff]
Feb 23 01:59:37 [1] pci 0000:00:0a.0: supports D1 D2
Feb 23 01:59:37 [2] pci 0000:00:0a.0: PME# supported from D0 D1 D2 D3hot D3cold
Feb 23 01:59:37 [2] pci 0000:00:0a.0: PME# disabled
Feb 23 01:59:37 [1] pci 0000:00:0d.0: reg 10 32bit mmio: [0xe4000000-0xe4000fff]
Feb 23 01:59:37 [1] pci 0000:00:0d.0: supports D1 D2
Feb 23 01:59:37 [2] pci 0000:00:0d.0: PME# supported from D0 D1 D2 D3hot
Feb 23 01:59:37 [2] pci 0000:00:0d.0: PME# disabled
Feb 23 01:59:37 [1] pci 0000:00:0d.1: reg 10 32bit mmio: [0xe3800000-0xe3800fff]
Feb 23 01:59:37 [1] pci 0000:00:0d.1: supports D1 D2
Feb 23 01:59:37 [2] pci 0000:00:0d.1: PME# supported from D0 D1 D2 D3hot
Feb 23 01:59:37 [2] pci 0000:00:0d.1: PME# disabled
Feb 23 01:59:37 [1] pci 0000:00:0d.2: reg 10 32bit mmio: [0xe3000000-0xe30000ff]
Feb 23 01:59:37 [1] pci 0000:00:0d.2: supports D1 D2
Feb 23 01:59:37 [2] pci 0000:00:0d.2: PME# supported from D0 D1 D2 D3hot
Feb 23 01:59:37 [2] pci 0000:00:0d.2: PME# disabled
Feb 23 01:59:37 [1] pci 0000:01:00.0: reg 10 32bit mmio: [0xe7000000-0xe7ffffff]
Feb 23 01:59:37 [1] pci 0000:01:00.0: reg 14 32bit mmio: [0xf0000000-0xf7ffffff]
Feb 23 01:59:37 [1] pci 0000:01:00.0: reg 30 32bit mmio: [0xefff0000-0xefffffff]
Feb 23 01:59:37 [1] pci 0000:00:01.0: bridge 32bit mmio: [0xe7000000-0xe7ffffff]
Feb 23 01:59:37 [1] pci 0000:00:01.0: bridge 32bit mmio pref: [0xeff00000-0xfebfffff]
Feb 23 01:59:37 [1] pci_bus 0000:00: on NUMA node 0
Feb 23 01:59:37 [1] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Feb 23 01:59:37 [1] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
Feb 23 01:59:37 [2] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Feb 23 01:59:37 [2] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Feb 23 01:59:37 [2] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11 *12 14 15)
Feb 23 01:59:37 [2] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 10 11 12 14 15)
Feb 23 01:59:37 [2] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *9
Feb 23 01:59:37 [2] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Feb 23 01:59:37 [2] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Feb 23 01:59:37 [2] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *9
Feb 23 01:59:37 [2] PCI: Using ACPI for IRQ routing
Feb 23 01:59:37 [1]
Feb 23 01:59:37 [1] printing PIC contents
Feb 23 01:59:37 [1] . PIC IMR: fdfa
Feb 23 01:59:37 [1] . PIC IRR: 1c20
Feb 23 01:59:37 [1] . PIC ISR: 0000
Feb 23 01:59:37 [1] . PIC ELCR: 0200
Feb 23 01:59:37 [4]
Feb 23 01:59:37 [1] printing local APIC contents on CPU#0/0:
Feb 23 01:59:37 [2] . APIC ID: 00000000 (0)
Feb 23 01:59:37 [2] . APIC VERSION: 00050014
Feb 23 01:59:37 [1] . APIC TASKPRI: 00000000 (00)
Feb 23 01:59:37 [1] . APIC PROCPRI: 00000000
Feb 23 01:59:37 [1] . APIC LDR: 01000000
Feb 23 01:59:37 [1] . APIC DFR: ffffffff
Feb 23 01:59:37 [1] . APIC SPIV: 000001ff
Feb 23 01:59:37 [1] . APIC ISR field:
Feb 23 01:59:37 [1] 0123456789abcdef0123456789abcdef
Feb 23 01:59:37 [1] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [1] . APIC TMR field:
Feb 23 01:59:37 [1] 0123456789abcdef0123456789abcdef
Feb 23 01:59:37 [1] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [1] . APIC IRR field:
Feb 23 01:59:37 [1] 0123456789abcdef0123456789abcdef
Feb 23 01:59:37 [1] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000000000000000000000
Feb 23 01:59:37 [4] 00000000000000010000000000000000
Feb 23 01:59:37 [1] . APIC ESR: 00000000
Feb 23 01:59:37 [1] . APIC ICR: 00000000
Feb 23 01:59:37 [1] . APIC ICR2: 00000000
Feb 23 01:59:37 [1] . APIC LVTT: 000200ef
Feb 23 01:59:37 [1] . APIC LVTPC: 00010000
Feb 23 01:59:37 [1] . APIC LVT0: 00001700
Feb 23 01:59:37 [1] . APIC LVT1: 00000400
Feb 23 01:59:37 [1] . APIC LVTERR: 000000fe
Feb 23 01:59:37 [1] . APIC TMICT: 0000628a
Feb 23 01:59:37 [1] . APIC TMCCT: 00001f6d
Feb 23 01:59:37 [1] . APIC TDCR: 00000003
Feb 23 01:59:37 [4]
Feb 23 01:59:37 [1] number of MP IRQ sources: 0.
Feb 23 01:59:37 [2] testing the IO APIC.
Feb 23 01:59:37 [1] IRQ to pin mappings:
Feb 23 01:59:37 [2] done.
Feb 23 01:59:37 [2] pnp: PnP ACPI init
Feb 23 01:59:37 [2] ACPI: bus type pnp registered
Feb 23 01:59:37 [2] pnp: PnP ACPI: found 15 devices
Feb 23 01:59:37 [2] ACPI: ACPI bus type pnp unregistered
Feb 23 01:59:37 [2] system 00:00: iomem range 0x0-0x9ffff could not be reserved
Feb 23 01:59:37 [2] system 00:00: iomem range 0xf0000-0xfffff could not be reserved
Feb 23 01:59:37 [2] system 00:00: iomem range 0x100000-0x1fffffff could not be reserved
Feb 23 01:59:37 [2] system 00:00: iomem range 0xfec00000-0xfecfffff could not be reserved
Feb 23 01:59:37 [2] system 00:00: iomem range 0xfee00000-0xfeefffff could not be reserved
Feb 23 01:59:37 [2] system 00:02: ioport range 0xe400-0xe47f has been reserved
Feb 23 01:59:37 [2] system 00:02: ioport range 0xe480-0xe4ff has been reserved
Feb 23 01:59:37 [2] system 00:02: ioport range 0xe600-0xe61f has been reserved
Feb 23 01:59:37 [2] system 00:02: ioport range 0x480-0x48f has been reserved
Feb 23 01:59:37 [2] system 00:02: iomem range 0xffee0000-0xffefffff has been reserved
Feb 23 01:59:37 [2] system 00:03: iomem range 0xfffe0000-0xffffffff could not be reserved
Feb 23 01:59:37 [2] system 00:04: ioport range 0x4d0-0x4d1 has been reserved
Feb 23 01:59:37 [2] system 00:0e: ioport range 0x3f0-0x3f1 has been reserved
Feb 23 01:59:37 [2] pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
Feb 23 01:59:37 [2] pci 0000:00:01.0: IO window: disabled
Feb 23 01:59:37 [2] pci 0000:00:01.0: MEM window: 0xe7000000-0xe7ffffff
Feb 23 01:59:37 [2] pci 0000:00:01.0: PREFETCH window: 0x000000eff00000-0x000000febfffff
Feb 23 01:59:37 [1] pci 0000:00:01.0: setting latency timer to 64
Feb 23 01:59:37 [1] pci_bus 0000:00: resource 0 io: [0x00-0xffff]
Feb 23 01:59:37 [1] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
Feb 23 01:59:37 [1] pci_bus 0000:01: resource 1 mem: [0xe7000000-0xe7ffffff]
Feb 23 01:59:37 [1] pci_bus 0000:01: resource 2 pref mem [0xeff00000-0xfebfffff]
Feb 23 01:59:37 [2] NET: Registered protocol family 2
Feb 23 01:59:37 [2] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
Feb 23 01:59:37 [2] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
Feb 23 01:59:37 [2] TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
Feb 23 01:59:37 [2] TCP: Hash tables configured (established 16384 bind 16384)
Feb 23 01:59:37 [2] TCP reno registered
Feb 23 01:59:37 [2] NET: Registered protocol family 1
Feb 23 01:59:37 [2] Trying to unpack rootfs image as initramfs.
Feb 23 01:59:37 [2] rootfs image is not initramfs (junk in compressed archive); looks like an initrd
Feb 23 01:59:37 [2] Freeing initrd memory: 8842k freed
Feb 23 01:59:37 [2] Simple Boot Flag at 0x3a set to 0x80
Feb 23 01:59:37 [2] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Feb 23 01:59:37 [2] msgmni has been set to 1009
Feb 23 01:59:37 [2] io scheduler noop registered (default)
Feb 23 01:59:37 [1] pci 0000:01:00.0: Boot video device
Feb 23 01:59:37 [2] brd: module loaded
Feb 23 01:59:37 [2] loop: module loaded
Feb 23 01:59:37 [2] PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
Feb 23 01:59:37 [4] PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Feb 23 01:59:37 [2] serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 23 01:59:37 [2] mice: PS/2 mouse device common for all m
Feb 23 01:59:37 [2] ice
Feb 23 01:59:37 [2] cpuidle: using governor ladder
Feb 23 01:59:37 [2] TCP cubic registered
Feb 23 01:59:37 [2] RPC: Registered udp transport module.
Feb 23 01:59:37 [2] RPC: Registered tcp transport module.
Feb 23 01:59:37 [2] Using IPI Shortcut mode
Feb 23 01:59:37 [2] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
Feb 23 01:59:37 [3] RAMDISK: CORE3 root image found at block 0
Feb 23 01:59:37 [4] VFS: Mounted root (ext2 filesystem) on device 1:0.
Feb 23 01:59:37 [2] Freeing unused kernel memory: 208k freed
Feb 23 01:59:38 [2] Floppy drive(s): fd0 is 1.44M
Feb 23 01:59:38 [2] FDC 0 is a post-1991 82077
Feb 23 01:59:39 [2] rtc_cmos 00:06: RTC can wake from S4
Feb 23 01:59:39 [2] rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
Feb 23 01:59:39 [2] rtc0: alarms up to one month, 242 bytes nvram
Feb 23 01:59:40 [2] input: PC Speaker as /devices/platform/pcspkr/input/input1
Feb 23 01:59:40 [2] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
Feb 23 01:59:40 [2] ACPI: Power Button [PWRF]
Feb 23 01:59:40 [2] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3
Feb 23 01:59:40 [2] ACPI: Power Button [PWRB]
Feb 23 01:59:40 [5] ACPI: Invalid PBLK length [5]
Feb 23 01:59:40 [2] processor ACPI_CPU:00: registered as cooling_device0
Feb 23 01:59:40 [2] Uniform Multi-Platform E-IDE driver
Feb 23 01:59:40 [2] sis5513 0000:00:02.5: SiS 961 MuTIOL IDE UDMA100 controller
Feb 23 01:59:40 [2] sis5513 0000:00:02.5: IDE controller (0x1039:0x5513 rev 0xd0)
Feb 23 01:59:40 [2] sis5513 0000:00:02.5: not 100% native mode: will probe irqs later
Feb 23 01:59:40 [2] ide0: BM-DMA at 0xd800-0xd807
Feb 23 01:59:40 [2] ide1: BM-DMA at 0xd808-0xd80f
Feb 23 01:59:40 [1] Probing IDE interface ide0.
Feb 23 01:59:41 [1] Probing IDE interface ide1.
Feb 23 01:59:41 [2] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Feb 23 01:59:41 [2] ide1 at 0x170-0x177,0x376 on irq 15
Feb 23 01:59:41 [3] SCSI subsystem initialized
Feb 23 01:59:41 [1] libata version 3.00 loaded.
Feb 23 01:59:42 [4] 3ware 9000 Storage Controller device driver for Linux v2.26.02.012.
Feb 23 01:59:42 [4] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
Feb 23 01:59:42 [1] PCI: setting IRQ 10 as level-triggered
Feb 23 01:59:42 [2] 3w-9xxx 0000:00:09.0: PCI INT A -> Link[LNKB] -> GSI 10 (level, low) -> IRQ 10
Feb 23 01:59:44 [2] scsi0 : 3ware 9000 Storage Controller
Feb 23 01:59:44 [4] 3w-9xxx: scsi0: Found a 3ware 9000 Storage Controller at 0xe5000000, IRQ: 10.
Feb 23 01:59:44 [4] 3w-9xxx: scsi0: Firmware FE9X 2.08.00.009, BIOS BE9X 2.03.01.052, Ports: 12.
Feb 23 01:59:44 [3] scsi 0:0:0:0: Direct-Access AMCC 9500S-12 DISK 2.08 PQ: 0 ANSI: 3
Feb 23 01:59:44 [4] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 12
Feb 23 01:59:44 [1] PCI: setting IRQ 12 as level-triggered
Feb 23 01:59:44 [2] skge 0000:00:0a.0: PCI INT A -> Link[LNKC] -> GSI 12 (level, low) -> IRQ 12
Feb 23 01:59:44 [2] skge 1.13 addr 0xe4800000 irq 12 chip Yukon rev 1
Feb 23 01:59:44 [2] skge eth0: addr 00:13:46:82:d4:fd
Feb 23 01:59:44 [2] usbcore: registered new interface driver usbfs
Feb 23 01:59:44 [2] usbcore: registered new interface driver hub
Feb 23 01:59:44 [2] usbcore: registered new device driver usb
Feb 23 01:59:44 [2] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Feb 23 01:59:44 [2] ohci_hcd 0000:00:0d.0: PCI INT A -> Link[LNKB] -> GSI 10 (level, low) -> IRQ 10
Feb 23 01:59:44 [2] ohci_hcd 0000:00:0d.0: OHCI Host Controller
Feb 23 01:59:44 [2] ohci_hcd 0000:00:0d.0: new USB bus registered, assigned bus number 1
Feb 23 01:59:44 [2] ohci_hcd 0000:00:0d.0: irq 10, io mem 0xe4000000
Feb 23 01:59:45 [2] usb usb1: configuration #1 chosen from 1 choice
Feb 23 01:59:45 [2] hub 1-0:1.0: USB hub found
Feb 23 01:59:45 [2] hub 1-0:1.0: 3 ports detected
Feb 23 01:59:45 [2] ohci_hcd 0000:00:0d.1: PCI INT B -> Link[LNKC] -> GSI 12 (level, low) -> IRQ 12
Feb 23 01:59:45 [2] ohci_hcd 0000:00:0d.1: OHCI Host Controller
Feb 23 01:59:45 [2] ohci_hcd 0000:00:0d.1: new USB bus registered, assigned bus number 2
Feb 23 01:59:45 [2] ohci_hcd 0000:00:0d.1: irq 12, io mem 0xe3800000
Feb 23 01:59:45 [2] usb usb2: configuration #1 chosen from 1 choice
Feb 23 01:59:45 [2] hub 2-0:1.0: USB hub found
Feb 23 01:59:45 [2] hub 2-0:1.0: 2 ports detected
Feb 23 01:59:45 [2] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Feb 23 01:59:45 [4] Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after
Feb 23 01:59:45 [4] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
Feb 23 01:59:45 [1] PCI: setting IRQ 5 as level-triggered
Feb 23 01:59:45 [2] ehci_hcd 0000:00:0d.2: PCI INT C -> Link[LNKD] -> GSI 5 (level, low) -> IRQ 5
Feb 23 01:59:45 [2] ehci_hcd 0000:00:0d.2: EHCI Host Controller
Feb 23 01:59:45 [2] ehci_hcd 0000:00:0d.2: new USB bus registered, assigned bus number 3
Feb 23 01:59:45 [2] ehci_hcd 0000:00:0d.2: irq 5, io mem 0xe3000000
Feb 23 01:59:45 [2] ehci_hcd 0000:00:0d.2: USB 2.0 started, EHCI 0.95
Feb 23 01:59:45 [2] usb usb3: configuration #1 chosen from 1 choice
Feb 23 01:59:45 [2] hub 3-0:1.0: USB hub found
Feb 23 01:59:45 [2] hub 3-0:1.0: 5 ports detected
Feb 23 01:59:46 [2] usb 3-4: new high speed USB device using ehci_hcd and address 2
Feb 23 01:59:46 [2] usb 3-4: configuration #1 chosen from 1 choice
Feb 23 01:59:47 [4] Driver 'sd' needs updating - please use bus_type methods
Feb 23 01:59:47 [3] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
Feb 23 01:59:47 [3] sd 0:0:0:0: [sda] 9765519360 512-byte hardware sectors: (4.99 TB/4.54 TiB)
Feb 23 01:59:47 [3] sd 0:0:0:0: [sda] Write Protect is off
Feb 23 01:59:47 [1] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
Feb 23 01:59:47 [3] sd 0:0:0:0: [sda] Write cache: enabled, read cache: disabled, doesn't support DPO or FUA
Feb 23 01:59:47 [3] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
Feb 23 01:59:47 [2] sda:
Feb 23 01:59:47 [2] sda1
Feb 23 01:59:47 [3] sd 0:0:0:0: [sda] Attached SCSI disk
Feb 23 01:59:47 [2] Initializing USB Mass Storage driver.
Feb 23 01:59:47 [2] scsi1 : SCSI emulation for USB Mass Storage devices
Feb 23 01:59:47 [1] usb-storage: device found at 2
Feb 23 01:59:47 [1] usb-storage: waiting for device to settle before scanning
Feb 23 01:59:47 [2] usbcore: registered new interface driver usb-storage
Feb 23 01:59:47 [2] USB Mass Storage support registered.
Feb 23 01:59:52 [3] scsi 1:0:0:0: Direct-Access Generic STORAGE DEVICE 1033 PQ: 0 ANSI: 0
Feb 23 01:59:52 [1] usb-storage: device scan complete
Feb 23 01:59:52 [3] sd 1:0:0:0: [sdb] 1024000 512-byte hardware sectors: (524 MB/500 MiB)
Feb 23 01:59:52 [3] sd 1:0:0:0: [sdb] Write Protect is off
Feb 23 01:59:52 [1] sd 1:0:0:0: [sdb] Mode Sense: 00 00 00 00
Feb 23 01:59:52 [5] sd 1:0:0:0: [sdb] Assuming drive cache: write through
Feb 23 01:59:52 [5] sd 1:0:0:0: [sdb] Assuming drive cache: write through
Feb 23 01:59:52 [2] sdb:
Feb 23 01:59:52 [2] sdb1
Feb 23 01:59:52 [3] sd 1:0:0:0: [sdb] Attached SCSI removable disk
Feb 23 02:00:10 [2] skge eth0: enabling interface
Feb 23 02:00:12 [2] skge eth0: Link is up at 1000 Mbps, full duplex, flow control both

I can blow off the array and rebuild, but that will take me another 2-3 days, and I'm especially hesitant since I can't determine what the problem is. NL can definitely "see" it, it simply FAILS the array even though it can successfully do a thorough scan on it. Of course the volume is set to RW. It's just not getting mounted. Any ideas?

I ran option#5 in hopes to get *anything*, and thankfully I got an error - something to work with:

e2fsck 1.40.4 (31-Dec-2007)
Pass 1: Checking inodes, blocks, and sizes
Error allocating icount link information: Memory allocation failed
e2fsck: aborted

Research shows a possible explanation?

http://serverfault.com/questions/9218/r ... ilesystems

I am running 512MB RAM and 32-bit. What are my options? I can't set a swap file size. I'm going to try boosting RAM and report back.

Ugh. After MORE research it's apparent that I rebooted one too many times and NL decided to fsck the volume. Coupled with only 512MB RAM, e2fsck just doesn't have enough memory to disk check the entire array.

I don't really *CARE* if this array gets disk checked because the data I'm storing is fairly static and backed up to tape quarterly.

There are no configuration options for e2fsck to run with less or no checks.

I added another 512MB stick and at least it's been going for about 15 minutes now. I hope to hell it gets through this.

Help?!

After bringing my total RAM to 1GB and about 74 minutes later, it finally completed the disk check.

Feb 23 04:38:11 [2] skge eth0: Link is up at 1000 Mbps, full duplex, flow control both
Feb 23 05:52:10 [2] kjournald starting. Commit interval 5 seconds
Feb 23 05:52:10 [2] EXT3 FS on sda1, internal journal
Feb 23 05:52:10 [2] EXT3-fs: mounted filesystem with writeback data mode.
Feb 23 05:52:33 [2] Adding 1048568k swap on /export/Disk-0/_NL_SWAP/VRAM. Priority:-1 extents:265 across:1066236k

I'm assuming I'm safe here and that I can fill up this volume and that NL will not complain or take longer than 74 minutes.

Also, I am begging and pleading here. PLEASE add e2fsck configuration to maybe an Advanced Settings menu for NL so those that want to turn it off, can.

Thanks,

Jeff

Sounds like a really great idea! This way when someone turns off the FSK and the machine fails due to hardware during a write and the FS becomes corrupted you can overwrite those files that are the most important to you when you get it back up.

FSK is there for your data's protection and to keep the developers from hearing that the software corrupted their data for X reason.

Mike

we have been here before - there are those of us who do not run 24/7 who would like more options for e2fsck and others who see nothing wrong with it [like mike!]

one discussion was to have an option to have it run at power off - dont know what happened to that - again the arguments fell into 2 camps - for and against

but it is configurable for frequancy and number of reboots - not from within naslite but via a linux distro - have a search there are a number of threads explaining how to do it

Hence the "advanced" option so people who aren't using NL the way Mike is can have more options when it comes to the disk check. Hell, it can be an option hidden in an easter egg somewhere.

Thanks for the constructive post, Tony.

My post is simply to point out what WILL happen if you give people the option. 99.9% of people think that they are the target of the "Advanced" menu items. (my ass has overloaded my brain more than once and put me in this category.) When they make a mistake though, they spit the blame at the distro authors and bitch and complain like no ones business. (Not me on the after effects of my mistakes) I see it happen all the time and it doesn't have to be an appliance application or OS, or software. It can be incorrectly using a tool or a cup of coffee that's to hot.

Personally I say add it to the main menu. Let the user be able to turn off file system checking all together. BUT, when they come and complain that due to an inconsistent FS they lost their kids birth video, the pics of their wedding, or the video of the bull mastif plowing the chiwawa for three hours....well SOL.

Sorry for the rant but I deal with people that due stupid things in a fairly consistent manner. They make stupid choices even when they are informed about the ill effects that can and likely will result. They then expect others to help with the wiping of their asses.

If you consider my posting, nae useless ranting, as unhelpful then please by all means don't hesitate to put me on ignore. I tend to provide information of little or no use to most everyone and you are the special one I choose to shower with my EXTRA useless info. I would really feel horrible if you were to take anything that I say as having any point at all. I would feel worse yet should you be lead astray.

Sorry for wasting your time.

For others this issue has come up before and the lack of verboseness in the underlying FSCK has been rather disconcerting for most new to NASLite. The documentation needs to be updated to reflect that fact that the FSCK will fail if there is not enough memory. Tony and Ralph are only two people and I would expect that this will be rectified in the next iteration of the documentation.

Mike

I understand the dilemma here but am reluctant to remove fsck from the boot sequence since I'd consider it to be one of the most important tasks of the start-up sequence. The RAM to storage should be consistent and capable of handling fsck regardless of how valuable the data may be. That is a hardware sizing issue and should be addressed as z0ner did by adding the additional 512M. If the filesystem is in fact degraded, the lack of RAM should and does render the affected volume unusable since the server would be incapable of resolving the defects. The goal of the design is to preserve the integrity of the data no matter what its value may be.

In practice, one can share out a 16T volume using NASLite-2 running on a machine with 128M of RAM. That would be a BAD practice since the server will be unable to perform necessary filesystem maintenance. Allowing one to overwrite the default behavior of that server will most certainly destroy the stored data over time.

However, the cause of the fsck that z0ner had problems with has nothing to do with corrupt data and was strictly a preventive step. I agree that we can go away with the number of reboots altogether and allow the 180-day interval to take over. If that is an agreeable option, we'll implement it in the next release. Any comments on that are welcome so please pros, cons?

The fsck at boot time however is not going away if the goal is to present a clean filesystem. Checking at shutdown as discussed a few months ago is not feasible. A power-outage will render that ineffective. Can't have that

As a default, 180-day-interval sounds good. ( I won't restart the prior discussion regarding trade-offs etc. )

How hard would it be to allow user to specify a custom interval (90 days, 30 days, 360 days, 28 days, etc) -- just like the "Status Update" interval ? ( Of course ... that could cause problems ... if the user changes the default from 180 to (for example) 90 days, the entire system needs to be rebooted and each disk would have to have the new interval applied to it ... with or without resetting the "counter" ... )

**OR**, (for data integrity paranoid users), I would like to specify a custom interval for each Disk-X separately ... with this feature I could accomplish an overlapping of fsck -- which would minimize the impact on startup time, as only ONE disk gets checked (if you shutdown regularly). (Example: use 28-day-interval for all disks, but change each disk to 28-day at the beginning of a different day or week (like Sunday). So if you have 4 disks, one disk will be checked each Sunday. Many other user-customizable scenarios are possible this way.) In this case only the affected disk (with a change to the interval) should have its "counter" reset and no "Save Config" or reboot should be required (otherwise the other disks may be affected and ruin the strategy).

The latest releases of 2 and M2 automatically set the interval to 180 days.

Which makes perfect sense why I needed a fsck on a 3-day old volume: I changed the default Y2000 date to today's date, well in excess of the 180-day disk check period.

I'm an options junkie, so IMHO I would like it to be completely configurable. However, I understand if that isn't in Tony and Ralph's ultimate vision of NASLite - even though I really can't see the harm in adding an extra level of complexity for power administrators.

I was initially worried that even 3GB of RAM (limit on mobo) wouldn't fix it and the sheer hours I put in to this project would have been wasted. Even though it takes over an hour, I can certainly live with it every 180 days.

And Mike, thanks for taking the time to explain your opinion. I initially dismissed your post as troll-ish, confused because I've seen some of the excellent advice that you give. In my web development I too have ultimate control over what the user is allowed to do, but I have added advanced options and with only a few exceptions most stay away. People need to be responsible for the choices that they make. You will not be added to my ignore list anytime soon

Likely you and I are very much alike, we want total control. We are also willing to accept the consequences of the mistakes we can make due to that control. Peeved though I may have been at your response I still would have helped you in the future. Glad you didn't take my rant the wrong way.

Mike

Trust me, I understand exactly where you are, but this happens to be the one particular option that can cause a whole lot of trouble for an ignorant newbie or a forgetful/lazy pro.

Consider the following:

The only time you'll experience delay due to filesystem check is once-in-a-while at boot. If your machine is on 24/7 then you'll not have to worry about it much other than at maintenance time when the machine is taken down. Arguably, an appropriate time for filesystem maintenance.

If on the other hand you power the machine off and on daily, and are spinning 5T of RAID, you are not only asking for trouble but potentially causing it. In that case the filesystem check is not only appropriate but necessary to keep you from unintentionally trashing your data. Regardless of whether you value that data or not.

fsck is like insurance and seatbelts. It is always too expensive or constraining until you have an accident and are VERY happy to have them...

Computers and hard drives do breakdown and data is very important.

Number of boots before fsck can be modified using a live CD for "pros" that want to "bypass" the fsck but should not be included in NL which is used mainly by people that built them, throw them in a lost place and let it run all the time and may "forget" risks about HDD failure.

I boot NL every week and I hate it (too) when NL starts a fsck just when I need the computer rapidly but I'm most happy to know that my professional data is under strict control and security.

Just my 5 cents