NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Thu Apr 18, 2024 7:06 pm

View unanswered posts | View active topics


Board index » v2.x NASLite Products » NASLite-2

All times are UTC - 5 hours [ DST ]



Post new topic Reply to topic  Page 1 of 2
  [ 16 posts ]  Go to page 1, 2  Next
  Previous topic | Next topic 
Author Message
NomadOfNorad
PostPosted: Sun Sep 04, 2011 3:28 am 
Offline

Joined: Tue Jul 05, 2005 9:50 pm
Posts: 46
Location: Jacksonville, Florida
The power went out briefly tonight, and when I subsequently clicked the shortcut to my naslite partition (on my Win7 desktop), I got the error Windows cannot access \\NASLITE-2\Disk-0. I checked the web interface, and the interface itself comes up without issue, but Disk-0 does not show on the web interface. No icon on the page to click to go to the status on it, nothing. I tried rebooting the NAS from telnet, and nothing changed.

This is with NASLite-2 v2.64 11-2010

The drive can't be dead because the NAS boots from another partition on it.

I am not sure where to take it from here. oO

System Message Log follows:

Code:
    Sep 4 06:47:13 [3] klogd started: BusyBox v1.12.1 (2009-11-19 21:21:30 UTC)
    Sep 4 06:47:13 [3] Linux version 2.6.30.3.CORE3 (root@DevBox) (gcc version 4.1.2 (SE 4.1.2 p1.0.2)) #1 Wed Jul 14 01:02:59 UTC 2010
    Sep 4 06:47:13 [2] KERNEL supported cpus:
    Sep 4 06:47:13 [2] Intel GenuineIntel
    Sep 4 06:47:13 [2] AMD AuthenticAMD
    Sep 4 06:47:13 [2] NSC Geode by NSC
    Sep 4 06:47:13 [2] Cyrix CyrixInstead
    Sep 4 06:47:13 [2] Centaur CentaurHauls
    Sep 4 06:47:13 [2] Transmeta GenuineTMx86
    Sep 4 06:47:13 [2] Transmeta TransmetaCPU
    Sep 4 06:47:13 [2] UMC UMC UMC UMC
    Sep 4 06:47:13 [2] BIOS-provided physical RAM map:
    Sep 4 06:47:13 [2] BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
    Sep 4 06:47:13 [2] BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
    Sep 4 06:47:13 [2] BIOS-e820: 00000000000e7000 - 0000000000100000 (reserved)
    Sep 4 06:47:13 [2] BIOS-e820: 0000000000100000 - 00000000040fd800 (usable)
    Sep 4 06:47:13 [2] BIOS-e820: 00000000040fd800 - 00000000040ff800 (ACPI data)
    Sep 4 06:47:13 [2] BIOS-e820: 00000000040ff800 - 00000000040ffc00 (ACPI NVS)
    Sep 4 06:47:13 [2] BIOS-e820: 00000000040ffc00 - 0000000008000000 (usable)
    Sep 4 06:47:13 [2] BIOS-e820: 00000000fffe7000 - 0000000100000000 (reserved)
    Sep 4 06:47:13 [2] DMI 2.1 present.
    Sep 4 06:47:13 [2] last_pfn = 0x8000 max_arch_pfn = 0x100000
    Sep 4 06:47:13 [2] init_memory_mapping: 0000000000000000-0000000008000000
    Sep 4 06:47:13 [1] 0000000000 - 0000400000 page 4k
    Sep 4 06:47:13 [1] 0000400000 - 0008000000 page 2M
    Sep 4 06:47:13 [1] kernel direct mapping tables up to 8000000 @ 7000-b000
    Sep 4 06:47:13 [2] RAMDISK: 03a32000 - 040fc453
    Sep 4 06:47:13 [4] ACPI: RSDP 000f6b30 00014 (v00 PTLTD )
    Sep 4 06:47:13 [4] ACPI: RSDT 040fdb05 00028 (v01 PTLTD RSDT 00000000 PTL 01000000)
    Sep 4 06:47:13 [4] ACPI: FACP 040ff78c 00074 (v01 INTEL WS440BX 00000000 PTL 000F4240)
    Sep 4 06:47:13 [4] ACPI: DSDT 040fdb2d 01C5F (v02 Intel WS44BX 00000000 MSFT 01000000)
    Sep 4 06:47:13 [4] ACPI: FACS 040ffbc0 00040
    Sep 4 06:47:13 [3] 0MB HIGHMEM available.
    Sep 4 06:47:13 [3] 128MB LOWMEM available.
    Sep 4 06:47:13 [2] mapped low ram: 0 - 08000000
    Sep 4 06:47:13 [2] low ram: 0 - 08000000
    Sep 4 06:47:13 [2] node 0 low ram: 00000000 - 08000000
    Sep 4 06:47:13 [2] node 0 bootmap 00001000 - 00002000
    Sep 4 06:47:13 [2] (6 early reservations) ==> bootmem [0000000000 - 0008000000]
    Sep 4 06:47:13 [2] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
    Sep 4 06:47:13 [2] #1 [0000100000 - 000039b83c] TEXT DATA BSS ==> [0000100000 - 000039b83c]
    Sep 4 06:47:13 [2] #2 [0003a32000 - 00040fc453] RAMDISK ==> [0003a32000 - 00040fc453]
    Sep 4 06:47:13 [2] #3 [000009f000 - 0000100000] BIOS reserved ==> [000009f000 - 0000100000]
    Sep 4 06:47:13 [2] #4 [000039c000 - 000039e0e4] BRK ==> [000039c000 - 000039e0e4]
    Sep 4 06:47:13 [2] #5 [0000001000 - 0000002000] BOOTMAP ==> [0000001000 - 0000002000]
    Sep 4 06:47:13 [4] Zone PFN ranges:
    Sep 4 06:47:13 [4] DMA 0x00000000 -> 0x00001000
    Sep 4 06:47:13 [4] Normal 0x00001000 -> 0x00008000
    Sep 4 06:47:13 [4] HighMem 0x00008000 -> 0x00008000
    Sep 4 06:47:13 [4] Movable zone start PFN for each node
    Sep 4 06:47:13 [4] early_node_map[3] active PFN ranges
    Sep 4 06:47:13 [4] 0: 0x00000000 -> 0x0000009f
    Sep 4 06:47:13 [4] 0: 0x00000100 -> 0x000040fd
    Sep 4 06:47:13 [4] 0: 0x00004100 -> 0x00008000
    Sep 4 06:47:13 [1] On node 0 totalpages: 32668
    Sep 4 06:47:13 [1] free_area_init_node: node 0, pgdat c031d560, node_mem_map c1000000
    Sep 4 06:47:13 [1] DMA zone: 32 pages used for memmap
    Sep 4 06:47:13 [1] DMA zone: 0 pages reserved
    Sep 4 06:47:13 [1] DMA zone: 3967 pages, LIFO batch:0
    Sep 4 06:47:13 [1] Normal zone: 224 pages used for memmap
    Sep 4 06:47:13 [1] Normal zone: 28445 pages, LIFO batch:7
    Sep 4 06:47:13 [2] Using APIC driver default
    Sep 4 06:47:13 [2] ACPI: PM-Timer IO Port: 0x8008
    Sep 4 06:47:13 [2] Local APIC disabled by BIOS -- you can enable it with "lapic"
    Sep 4 06:47:13 [1] nr_irqs_gsi: 16
    Sep 4 06:47:13 [2] Allocating PCI resources starting at 10000000 (gap: 8000000:f7fe7000)
    Sep 4 06:47:13 [4] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32412
    Sep 4 06:47:13 [3] Kernel command line: rw root=/dev/ram0 initrd=NASLite.02 quiet BOOT_IMAGE=NASLite.01
    Sep 4 06:47:13 [2] Enabling fast FPU save and restore. done.
    Sep 4 06:47:13 [2] Initializing CPU#0
    Sep 4 06:47:13 [2] NR_IRQS:288
    Sep 4 06:47:13 [4] PID hash table entries: 512 (order: 9, 2048 bytes)
    Sep 4 06:47:13 [4] Fast TSC calibration using PIT
    Sep 4 06:47:13 [4] Detected 447.672 MHz processor.
    Sep 4 06:47:13 [4] Console: colour VGA+ 80x25
    Sep 4 06:47:13 [2] console [tty0] enabled
    Sep 4 06:47:13 [2] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
    Sep 4 06:47:13 [2] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
    Sep 4 06:47:13 [2] Initializing HighMem for node 0 (00000000:00000000)
    Sep 4 06:47:13 [2] Memory: 119728k/131072k available (1523k kernel code, 10780k reserved, 667k data, 208k init, 0k highmem)
    Sep 4 06:47:13 [2] virtual kernel memory layout:
    Sep 4 06:47:13 [2] fixmap : 0xfffa9000 - 0xfffff000 ( 344 kB)
    Sep 4 06:47:13 [2] pkmap : 0xff800000 - 0xffc00000 (4096 kB)
    Sep 4 06:47:13 [2] vmalloc : 0xc8800000 - 0xff7fe000 ( 879 MB)
    Sep 4 06:47:13 [2] lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
    Sep 4 06:47:13 [2] .init : 0xc0326000 - 0xc035a000 ( 208 kB)
    Sep 4 06:47:13 [2] .data : 0xc027cfdb - 0xc0323e14 ( 66
    Sep 4 06:47:13 [2] 7 kB)
    Sep 4 06:47:13 [2] .text : 0xc0100000 - 0xc027cfdb (1523 kB)
    Sep 4 06:47:13 [2] Checking if this processor honours the WP bit even in supervisor mode.Ok.
    Sep 4 06:47:13 [2] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
    Sep 4 06:47:13 [2] Calibrating delay loop (skipped), value calculated using timer frequency 895.34 BogoMIPS (lpj=1790688)
    Sep 4 06:47:13 [4] Mount-cache hash table entries: 512
    Sep 4 06:47:13 [2] CPU: L1 I cache: 16K, L1 D cache: 16K
    Sep 4 06:47:13 [2] CPU: L2 cache: 512K
    Sep 4 06:47:13 [4] CPU: Intel Pentium II (Deschutes) stepping 02
    Sep 4 06:47:13 [2] Checking 'hlt' instruction. OK.
    Sep 4 06:47:13 [2] ACPI: Core revision 20090320
    Sep 4 06:47:13 [4] ACPI: setting ELCR to 0200 (from 0a00)
    Sep 4 06:47:13 [2] net_namespace: 296 bytes
    Sep 4 06:47:13 [2] NET: Registered protocol family 16
    Sep 4 06:47:13 [2] ACPI: bus type pci registered
    Sep 4 06:47:13 [2] PCI: PCI BIOS revision 2.10 entry at 0xfd983, last bus=1
    Sep 4 06:47:13 [2] PCI: Using configuration type 1 for base access
    Sep 4 06:47:13 [4] bio: create slab at 0
    Sep 4 06:47:13 [1] ACPI: EC: Look up EC in DSDT
    Sep 4 06:47:13 [2] ACPI: Interpreter enabled
    Sep 4 06:47:13 [2] ACPI: (supports S0 S5)
    Sep 4 06:47:13 [2] ACPI: Using PIC for interrupt routing
    Sep 4 06:47:13 [2] ACPI: Power Resource [PFAN] (off)
    Sep 4 06:47:13 [2] ACPI: No dock devices found.
    Sep 4 06:47:13 [2] ACPI: PCI Root Bridge [PCI0] (0000:00)
    Sep 4 06:47:13 [1] pci 0000:00:00.0: reg 10 32bit mmio: [0xf8000000-0xfbffffff]
    Sep 4 06:47:13 [1] pci 0000:00:07.1: reg 20 io port: [0x1460-0x146f]
    Sep 4 06:47:13 [1] pci 0000:00:07.2: reg 20 io port: [0x1440-0x145f]
    Sep 4 06:47:13 [4] * Found PM-Timer Bug on the chipset. Due to workarounds for a bug,
    Sep 4 06:47:13 [4] * this clock source is slow. Consider trying other clock sources
    Sep 4 06:47:13 [2] pci 0000:00:07.3: quirk: region 8000-803f claimed by PIIX4 ACPI
    Sep 4 06:47:13 [2] pci 0000:00:07.3: quirk: region 7000-700f claimed by PIIX4 SMB
    Sep 4 06:47:13 [1] pci 0000:00:0c.0: reg 10 io port: [0x1400-0x143f]
    Sep 4 06:47:13 [1] pci 0000:00:0c.0: supports D2
    Sep 4 06:47:13 [2] pci 0000:00:0c.0: PME# supported from D0 D2 D3hot
    Sep 4 06:47:13 [2] pci 0000:00:0c.0: PME# disabled
    Sep 4 06:47:13 [1] pci 0000:00:0e.0: reg 10 io port: [0x1000-0x10ff]
    Sep 4 06:47:13 [1] pci 0000:00:0e.0: reg 14 32bit mmio: [0xf4000000-0xf40000ff]
    Sep 4 06:47:13 [1] pci 0000:00:0e.0: supports D1 D2
    Sep 4 06:47:13 [2] pci 0000:00:0e.0: PME# supported from D1 D2 D3hot
    Sep 4 06:47:13 [2] pci 0000:00:0e.0: PME# disabled
    Sep 4 06:47:13 [1] pci 0000:00:10.0: reg 10 io port: [0x1490-0x1497]
    Sep 4 06:47:13 [1] pci 0000:00:10.0: reg 14 io port: [0x1484-0x1487]
    Sep 4 06:47:13 [1] pci 0000:00:10.0: reg 18 io port: [0x1488-0x148f]
    Sep 4 06:47:13 [1] pci 0000:00:10.0: reg 1c io port: [0x1480-0x1483]
    Sep 4 06:47:13 [1] pci 0000:00:10.0: reg 20 io port: [0x1470-0x147f]
    Sep 4 06:47:13 [1] pci 0000:00:10.0: reg 24 32bit mmio: [0xf4000400-0xf40005ff]
    Sep 4 06:47:13 [1] pci 0000:00:10.0: reg 30 32bit mmio: [0x000000-0x07ffff]
    Sep 4 06:47:13 [1] pci 0000:00:10.0: supports D1 D2
    Sep 4 06:47:13 [1] pci 0000:01:00.0: reg 10 32bit mmio: [0xf5000000-0xf5ffffff]
    Sep 4 06:47:13 [1] pci 0000:01:00.0: reg 14 io port: [0x9000-0x90ff]
    Sep 4 06:47:13 [1] pci 0000:01:00.0: reg 18 32bit mmio: [0xf4100000-0xf4100fff]
    Sep 4 06:47:13 [1] pci 0000:01:00.0: reg 30 32bit mmio: [0x000000-0x01ffff]
    Sep 4 06:47:13 [1] pci 0000:00:01.0: bridge io port: [0x9000-0x9fff]
    Sep 4 06:47:13 [1] pci 0000:00:01.0: bridge 32bit mmio: [0xf4100000-0xf5ffffff]
    Sep 4 06:47:13 [1] pci_bus 0000:00: on NUMA node 0
    Sep 4 06:47:13 [1] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    Sep 4 06:47:13 [2] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
    Sep 4 06:47:13 [2] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 10 *11 12)
    Sep 4 06:47:13 [2] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
    Sep 4 06:47:13 [2] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 *9 10 11 12)
    Sep 4 06:47:13 [2] PCI: Using ACPI for IRQ routing
    Sep 4 06:47:13 [4] Expanded resource reserved due to conflict with Adapter ROM
    Sep 4 06:47:13 [1]
    Sep 4 06:47:13 [1] printing PIC contents
    Sep 4 06:47:13 [1] . PIC IMR: fdfa
    Sep 4 06:47:13 [1] . PIC IRR: 0800
    Sep 4 06:47:13 [1] . PIC ISR: 0000
    Sep 4 06:47:13 [1] . PIC ELCR: 0200
    Sep 4 06:47:13 [4]
    Sep 4 06:47:13 [1] printing local APIC contents on CPU#0/0:
    Sep 4 06:47:13 [2] . APIC ID: 00000000 (0)
    Sep 4 06:47:13 [2] . APIC VERSION: 00000000
    Sep 4 06:47:13 [1] . APIC TASKPRI: 00000000 (00)
    Sep 4 06:47:13 [1] . APIC RRR: 00000000
    Sep 4 06:47:13 [1] . APIC LDR: 00000000
    Sep 4 06:47:13 [1] . APIC DFR: 00000000
    Sep 4 06:47:13 [1] . APIC SPIV: 00000000
    Sep 4 06:47:13 [1] . APIC ISR field:
    Sep 4 06:47:13 [1] 0123456789abcdef0123456789abcdef
    Sep 4 06:47:13 [1] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [1] . APIC TMR field:
    Sep 4 06:47:13 [1] 0123456789abcdef0123456789abcdef
    Sep 4 06:47:13 [1] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 0000000
    Sep 4 06:47:13 [2] 0000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [1] . APIC IRR field:
    Sep 4 06:47:13 [1] 0123456789abcdef0123456789abcdef
    Sep 4 06:47:13 [1] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [4] 00000000000000000000000000000000
    Sep 4 06:47:13 [1] . APIC ICR: 00000000
    Sep 4 06:47:13 [1] . APIC ICR2: 00000000
    Sep 4 06:47:13 [1] . APIC LVTT: 00000000
    Sep 4 06:47:13 [1] . APIC LVT0: 00000000
    Sep 4 06:47:13 [1] . APIC LVT1: 00000000
    Sep 4 06:47:13 [1] . APIC TMICT: 00000000
    Sep 4 06:47:13 [1] . APIC TMCCT: 00000000
    Sep 4 06:47:13 [1] . APIC TDCR: 00000000
    Sep 4 06:47:13 [4]
    Sep 4 06:47:13 [1] number of MP IRQ sources: 0.
    Sep 4 06:47:13 [2] testing the IO APIC.
    Sep 4 06:47:13 [1] IRQ to pin mappings:
    Sep 4 06:47:13 [2] done.
    Sep 4 06:47:13 [2] pnp: PnP ACPI init
    Sep 4 06:47:13 [2] ACPI: bus type pnp registered
    Sep 4 06:47:13 [2] pnp: PnP ACPI: found 12 devices
    Sep 4 06:47:13 [2] ACPI: ACPI bus type pnp unregistered
    Sep 4 06:47:13 [2] system 00:01: ioport range 0x7000-0x700f has been reserved
    Sep 4 06:47:13 [2] system 00:01: ioport range 0x8000-0x803f has been reserved
    Sep 4 06:47:13 [2] pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
    Sep 4 06:47:13 [2] pci 0000:00:01.0: IO window: 0x9000-0x9fff
    Sep 4 06:47:13 [2] pci 0000:00:01.0: MEM window: 0xf4100000-0xf5ffffff
    Sep 4 06:47:13 [2] pci 0000:00:01.0: PREFETCH window: 0x00000010000000-0x000000100fffff
    Sep 4 06:47:13 [1] pci_bus 0000:00: resource 0 io: [0x00-0xffff]
    Sep 4 06:47:13 [1] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
    Sep 4 06:47:13 [1] pci_bus 0000:01: resource 0 io: [0x9000-0x9fff]
    Sep 4 06:47:13 [1] pci_bus 0000:01: resource 1 mem: [0xf4100000-0xf5ffffff]
    Sep 4 06:47:13 [1] pci_bus 0000:01: resource 2 pref mem [0x10000000-0x100fffff]
    Sep 4 06:47:13 [2] NET: Registered protocol family 2
    Sep 4 06:47:13 [2] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
    Sep 4 06:47:13 [2] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
    Sep 4 06:47:13 [2] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
    Sep 4 06:47:13 [2] TCP: Hash tables configured (established 4096 bind 4096)
    Sep 4 06:47:13 [2] TCP reno registered
    Sep 4 06:47:13 [2] NET: Registered protocol family 1
    Sep 4 06:47:13 [2] Trying to unpack rootfs image as initramfs.
    Sep 4 06:47:13 [2] rootfs image is not initramfs (junk in compressed archive); looks like an initrd
    Sep 4 06:47:13 [2] Freeing initrd memory: 6953k freed
    Sep 4 06:47:13 [2] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
    Sep 4 06:47:13 [2] msgmni has been set to 247
    Sep 4 06:47:13 [2] io scheduler noop registered (default)
    Sep 4 06:47:13 [2] pci 0000:00:00.0: Limiting direct PCI/PCI transfers
    Sep 4 06:47:13 [1] pci 0000:01:00.0: Boot video device
    Sep 4 06:47:13 [2] brd: module loaded
    Sep 4 06:47:13 [2] loop: module loaded
    Sep 4 06:47:13 [2] PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:MICE] at 0x60,0x64 irq 1,12
    Sep 4 06:47:13 [2] serio: i8042 KBD port at 0x60,0x64 irq 1
    Sep 4 06:47:13 [2] mice: PS/2 mouse device common for all mice
    Sep 4 06:47:13 [2] cpuidle: using governor ladder
    Sep 4 06:47:13 [2] TCP cubic registered
    Sep 4 06:47:13 [2] RPC: Registered udp transport module.
    Sep 4 06:47:13 [2] RPC: Registered tcp transport module.
    Sep 4 06:47:13 [2] Using IPI Shortcut mode
    Sep 4 06:47:13 [3] RAMDISK: CORE3 root image found at block 0
    Sep 4 06:47:13 [4] EXT2-fs warning: checktime reached, running e2fsck is recommended
    Sep 4 06:47:13 [4] VFS: Mounted root (ext2 filesystem) on device 1:0.
    Sep 4 06:47:13 [2] Freeing unused kernel memory: 208k freed
    Sep 4 06:47:15 [2] Floppy drive(s): fd0 is 1.44M
    Sep 4 06:47:15 [2] FDC 0 is a post-1991 82077
    Sep 4 06:47:16 [2] rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
    Sep 4 06:47:16 [2] rtc0: alarms up to one month, y3k, 114 bytes nvram
    Sep 4 06:47:17 [2] input: PC Speaker as /devices/platform/pcspkr/input/input0
    Sep 4 06:47:17 [2] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
    Sep 4 06:47:17 [2] ACPI: Power Button [PWRF]
    Sep 4 06:47:18 [4] Marking TSC unstable due to TSC halts in idle
    Sep 4 06:47:18 [2] ACPI: CPU0 (power states: C1[C1] C2[C2])
    Sep 4 06:47:18 [2] processor ACPI_CPU:00: registered as cooling_device0
    Sep 4 06:47:18 [2] fan PNP0C0B:00: registered as cooling_device1
    Sep 4 06:47:18 [2] ACPI: Fan [FAN1] (off)
    Sep 4 06:47:18 [2] Uniform Multi-Platform E-IDE driver
    Sep 4 06:47:18 [2] piix 0000:00:07.1: IDE controller (0x8086:0x7111 rev 0x01)
    Sep 4 06:47:18 [2] piix 0000:00:07.1: IDE port disabled
    Sep 4 06:47:18 [2] piix 0000:00:07.1: not 100% native mode: will probe irqs later
    Sep 4 06:47:18 [2] ide0: BM-DMA at 0x1468-0x146f
    Sep 4 06:47:18 [1] Probing IDE interface ide0.
    Sep 4 06:47:19 [2] hda: MATSHITADVD-ROM SR-8582, ATAPI CD/DVD-ROM drive
    Sep 4 06:47:19 [1] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
    Sep 4 06:47:19 [2] hda: MWDMA2 mode selected
    Sep 4 06:47:19 [2] ide0 at 0x170-0x177,0x376 on irq 15
    Sep 4 06:47:19 [3] SCSI subsystem initialized
    Sep 4 06:47:19 [1] libata version 3.00 loaded.
    Sep 4 06:47:20 [2] usbcore: registered new interface driver usbfs
    Sep 4 06:47:20 [2] usbcore: registered new interface driver hub
    Sep 4 06:47:20 [2] usbcore: registered new device driver usb
    Sep 4 06:47:20 [2] uhci_hcd: USB Universal Host Controller Interface driver
    Sep 4 06:47:20 [4] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 9
    Sep 4 06:47:20 [1] PCI: setting IRQ 9 as level-triggered
    Sep 4 06:47:20 [2] uhci_hcd 0000:00:07.2: PCI INT D -> Link[LNKD] -> GSI 9 (level, low) -> IRQ 9
    Sep 4 06:47:20 [2] uhci_hcd 0000:00:07.2: UHCI Host Controller
    Sep 4 06:47:20 [2] uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
    Sep 4 06:47:20 [2] uhci_hcd 0000:00:07.2: irq 9, io base 0x00001440
    Sep 4 06:47:20 [2] usb usb1: configuration #1 chosen from 1 choice
    Sep 4 06:47:20 [2] hub 1-0:1.0: USB hub found
    Sep 4 06:47:20 [2] hub 1-0:1.0: 2 ports detected
    Sep 4 06:47:20 [2] 8139too Fast Ethernet driver 0.9.28
    Sep 4 06:47:20 [4] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
    Sep 4 06:47:20 [1] PCI: setting IRQ 11 as level-triggered
    Sep 4 06:47:20 [2] 8139too 0000:00:0e.0: PCI INT A -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11
    Sep 4 06:47:20 [2] eth0: RealTek RTL8139 at 0x1000, 00:0d:88:2d:3a:b4, IRQ 11
    Sep 4 06:47:20 [1] eth0: Identified 8139 chip type 'RTL-8100B/8139D'
    Sep 4 06:47:20 [1] sata_sil 0000:00:10.0: version 2.4
    Sep 4 06:47:20 [2] sata_sil 0000:00:10.0: PCI INT A -> Link[LNKD] -> GSI 9 (level, low) -> IRQ 9
    Sep 4 06:47:20 [2] scsi0 : sata_sil
    Sep 4 06:47:20 [2] scsi1 : sata_sil
    Sep 4 06:47:20 [2] ata1: SATA max UDMA/100 mmio m512@0xf4000400 tf 0xf4000480 irq 9
    Sep 4 06:47:20 [2] ata2: SATA max UDMA/100 mmio m512@0xf4000400 tf 0xf40004c0 irq 9
    Sep 4 06:47:20 [2] ata1: SATA link down (SStatus 0 SControl 310)
    Sep 4 06:47:21 [2] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    Sep 4 06:47:21 [2] ata2.00: ATA-8: ST31000520AS, CC32, max UDMA/133
    Sep 4 06:47:21 [2] ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    Sep 4 06:47:21 [2] ata2.00: configured for UDMA/100
    Sep 4 06:47:21 [3] scsi 1:0:0:0: Direct-Access ATA ST31000520AS CC32 PQ: 0 ANSI: 5
    Sep 4 06:47:22 [2] ide-cd driver 5.00
    Sep 4 06:47:22 [2] ide-cd: hda: ATAPI 24X DVD-ROM drive, 512kB Cache
    Sep 4 06:47:22 [2] Uniform CD-ROM driver Revision: 3.20
    Sep 4 06:47:23 [4] Driver 'sd' needs updating - please use bus_type methods
    Sep 4 06:47:23 [3] sd 1:0:0:0: [sda] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB)
    Sep 4 06:47:23 [3] sd 1:0:0:0: [sda] Write Protect is off
    Sep 4 06:47:23 [1] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
    Sep 4 06:47:23 [3] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Sep 4 06:47:23 [2] sda:
    Sep 4 06:47:23 [2] sda1 sda2
    Sep 4 06:47:23 [3] sd 1:0:0:0: [sda] Attached SCSI disk
    Sep 4 06:47:56 [2] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1


Top
 Profile  
 
tony a
PostPosted: Sun Sep 04, 2011 4:02 am 
Offline

Joined: Sun May 27, 2007 5:38 pm
Posts: 517
Location: gods own country
let it do a disc check - than can take a while depending on drive size - my 1 terabyte can take over an hour - and thats with 1gig of memory - which is the next problem - how much memory have you got it the box - Naslite will work with minimum until it comes to disc checking when it may not complete

so add some memory if you only have a small amount in the box
Top
 Profile  
 
NomadOfNorad
PostPosted: Sun Sep 04, 2011 1:38 pm 
Offline

Joined: Tue Jul 05, 2005 9:50 pm
Posts: 46
Location: Jacksonville, Florida
Okay, I went to telnet, and under DISK-0 CONFIGURATION MENU invoked 5 - Check Disk-0 Filesystem, and it immediately came back:

e2fsck 1.40.4 (31-Dec-2007)
Pass 1: Checking inodes, blocks, and sizes
Error allocating icount link information: Memory allocation failed
e2fsck: aborted
Top
 Profile  
 
tony a
PostPosted: Sun Sep 04, 2011 1:42 pm 
Offline

Joined: Sun May 27, 2007 5:38 pm
Posts: 517
Location: gods own country
came back as in ok - or just saw it and then failed - if the latter i would be looking at memory - amount and is some faulty - boot up with a linex distro - that may well tell you more

EDIT - misread your post - so it failed - then try the memory and/or boot into linux and see what that says
Top
 Profile  
 
NomadOfNorad
PostPosted: Sun Sep 04, 2011 3:49 pm 
Offline

Joined: Tue Jul 05, 2005 9:50 pm
Posts: 46
Location: Jacksonville, Florida
Are there other things I can do from the NASLITE system to check things, tho?

addendum: anyway, I'm not that experienced with Linux, tho I do have some Linux live CDs. Ubuntu and Xubuntu and such, for instance. What should I run on one of those?
Top
 Profile  
 
dougal1957
PostPosted: Mon Sep 05, 2011 2:56 am 
Offline

Joined: Fri Dec 18, 2009 10:08 am
Posts: 129
Location: Sheffield UK
NomadOfNorad wrote:
Okay, I went to telnet, and under DISK-0 CONFIGURATION MENU invoked 5 - Check Disk-0 Filesystem, and it immediately came back:

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


That is the sort of message that you get when you have issufficient memory in the box try adding some more and try again.

it wont stop the box booting but it will refuse to mount a partition that it cannot fsck (I had the same 3 days ago).

Doug
Top
 Profile  
 
tony a
PostPosted: Mon Sep 05, 2011 3:46 am 
Offline

Joined: Sun May 27, 2007 5:38 pm
Posts: 517
Location: gods own country
totally agree with post above

linux would let you look at disc - it may let you run e2fsck - but it will certainly let you see if disc is ok and if files are there

but the 1st step is get more memory and let Naslite do what it is asking - that will most likely sort everything out
Top
 Profile  
 
dougal1957
PostPosted: Tue Sep 06, 2011 3:19 am 
Offline

Joined: Fri Dec 18, 2009 10:08 am
Posts: 129
Location: Sheffield UK
dougal1957 wrote:
NomadOfNorad wrote:
Okay, I went to telnet, and under DISK-0 CONFIGURATION MENU invoked 5 - Check Disk-0 Filesystem, and it immediately came back:

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


That is the sort of message that you get when you have issufficient memory in the box try adding some more and try again.

it wont stop the box booting but it will refuse to mount a partition that it cannot fsck (I had the same 3 days ago).

Doug


Having looked again at the logs I would say it is definately a lack of memory issue as far as I can see you only have 128Mb of ram in that box and a 1Tb Hard drive.

I would try and increase the Ram to at least 1Gb (although 512 Mb may be enough) I have had problems with 2Gb in my box but it is running a 16TB Raid array.

HTH Doug

p.s. Please report back.
Top
 Profile  
 
NomadOfNorad
PostPosted: Thu Sep 22, 2011 4:49 pm 
Offline

Joined: Tue Jul 05, 2005 9:50 pm
Posts: 46
Location: Jacksonville, Florida
Sorry I've not gotten back to this in so long, I just kept putting off dealing with this for ages because I knew I was going to have to take my machine apart to fix this... after moving a bunch of other stuff out of the way to get at the machine first.

I'm not sure I can even PUT more ram in this machine, it is an older-than-dirt Gateway G6-450, a Pentium II. If I were to GET more ram to put in it, I'd probably have to special order it for more than it's worth.

I tried pulling the drive out and accessing it on another machine, via an IDE/SATA-to-USB adapter... and for some reason couldn't get the SATA drive to be recognized by the adapter. The sata-drive-is-live light light never comes on on the adapter, even though I'm pretty sure I have it all connected right. I've now mounted the drive back into the Gateway machine and restarted it, and it boots into NASlite as before from that drive... but as before the partition with the data on it never mounts.

I then booted the machine on a DamnSmallLinux 1.1 livecd (which takes a lot less ram than other Linux versions) and which I'd used to repair (e2fsck) the drive contents when I was using two smaller drives and the old launches-from-floppy version of naslite... but I can't figure out which drive path to go to since it's obviously different on the new settup. It's been awhile since I set the current system up, but IIRC I'm using sata through a PCI sata card, whereas before I was using two IDE hard drives. Or maybe I'm using an IDE-to-SATA adaptor, I don't remember.

What path should I be using for this? Before, I would typically do something like this from the shell:

Code:
e2fsck -t /dev/hdb1

Bear in mind, I am a complete novice when it comes to Linux.
Top
 Profile  
 
georg
PostPosted: Thu Sep 22, 2011 7:46 pm 
Offline

Joined: Sat Nov 19, 2005 6:39 pm
Posts: 633
Location: California
Try the "fdisk -l" (lowercase "L") command (need to be root) ... it should list the attached devices, and from that info you should be able to tell the proper device to use.
Top
 Profile  
 
NomadOfNorad
PostPosted: Thu Sep 22, 2011 9:59 pm 
Offline

Joined: Tue Jul 05, 2005 9:50 pm
Posts: 46
Location: Jacksonville, Florida
Okay, I open XTerminal, set it to root via by typing "sudo su" (which I learned to do from Dillo: Getting Started With DSL), I then type "fdisk -l" and absolutely nothing comes up. Am I missing something?

Is there another way of bringing up a list of all devices?

Anyway, does anyone know what the most likely path to disk 0 is? I know that on my old settup, the floppy-launched one, I had disk 1 and disk 2, and those were accessed as /dev/hba1 and /dev/hdb1 respectively, but I have no clue what the path would be now with disk 0 on Naslite 2, but I'm guessing that there's a path that Naslite 2 always uses for Disk 0, for Disk 1, and so on. (I only have Disk 0.) Basically, I need to go into shell and type:

Code:
e2fsck -t /dev/[whatevertheheckitis]

...but I need to know what to place in the [whatevertheheckitis]
Top
 Profile  
 
georg
PostPosted: Fri Sep 23, 2011 12:13 am 
Offline

Joined: Sat Nov 19, 2005 6:39 pm
Posts: 633
Location: California
Ok ... I am not a Linux expert ... but I think the following might make a difference. Rather than typing "sudo su" add a (space separated) dash to the end of it. In other words, type "sudo su -" and try again.

(Either way worked on my Ubuntu system; but the two methods behaved just a little differently.)
Top
 Profile  
 
NomadOfNorad
PostPosted: Fri Sep 23, 2011 12:27 am 
Offline

Joined: Tue Jul 05, 2005 9:50 pm
Posts: 46
Location: Jacksonville, Florida
I open a fresh XTerminal, type "sudo su -" there, and I still get nothing at all when I type "fdisk -l" after that. Do I need to move to a specific directory before I "fdisk -l"?
Top
 Profile  
 
georg
PostPosted: Fri Sep 23, 2011 12:45 am 
Offline

Joined: Sat Nov 19, 2005 6:39 pm
Posts: 633
Location: California
No. That's all you should need.

try /dev/sda1 (and /dev/hda1).

If none of that works ... try a different LiveCD distribution (Knoppix or Ubuntu).

Update: I just tried a couple of old laptop IDE drives via a IDE/USB adapter. I noticed that one drive was "clicking". Moved it to a different PC, and worked ok there. Then tried a second drive on the first PC. Didn't work (same as your symptom). Moved the first drive back to the first PC, now it worked.

I have a feeling the first PC's USB port just barely manages to supply enough current to run the drive from the (otherwise not powered) adapter. If your adapter relies on power from USB for the drive this might be the problem. If powered separately, try a different USB port, preferably one directly off the back of the motherboard. And/or try a different PC.

2nd update: if "fdisk -l" does not see your drive then e2fsck is not going to work ... got to solve that problem first.
Top
 Profile  
 
NomadOfNorad
PostPosted: Fri Sep 23, 2011 2:45 am 
Offline

Joined: Tue Jul 05, 2005 9:50 pm
Posts: 46
Location: Jacksonville, Florida
The device I'm using is one of these, actually:

http://www.tigerdirect.com/applications ... atId=3770#

This is the first time I've ever used it with a SATA drive, tho. With IDE drives it works fine.

As for /dev/sda1 and /dev/hda1, when I invote "e2fsck -t /dev/sda1" they both give an error:

Code:
e2fsck 3.14-WIP (21-May-2003)
e2fsck: No such device or address while trying to open /dev/sda1
Possibly non-existent or swap device?


Code:
e2fsck 3.14-WIP (21-May-2003)
e2fsck: No such device or address while trying to open /dev/hda1
Possibly non-existent or swap device?


If I change it to /dev/sda0 I get:

Code:
e2fsck 3.14-WIP (21-May-2003)
e2fsck: No such device or address while trying to open /dev/sda0

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not a swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

I get the same error if I try that with /dev/hda0
Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 1 of 2
  [ 16 posts ]  Go to page 1, 2  Next

Board index » v2.x NASLite Products » NASLite-2

All times are UTC - 5 hours [ DST ]

Who is online

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