NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Mon May 05, 2025 2:36 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 3 of 5
  [ 68 posts ]  Go to page Previous  1, 2, 3, 4, 5  Next
  Previous topic | Next topic 
Author Message
willsy
 Post subject:
PostPosted: Tue Nov 20, 2007 6:34 pm 
Offline

Joined: Mon Apr 17, 2006 12:55 pm
Posts: 143
Location: Newcastle
Had a look at the log file. Looks like the on-board NIC and the Raid card are sharing IRQ 10.
Could be the problem, however it doesn't cause any problems with the CF/IDE adaptor.
Top
 Profile  
 
willsy
 Post subject:
PostPosted: Sat Nov 24, 2007 5:08 pm 
Offline

Joined: Mon Apr 17, 2006 12:55 pm
Posts: 143
Location: Newcastle
Quote:
however it doesn't cause any problems with the CF/IDE adaptor.

Spoke too soon. I had just copied a load of recorded TV programmes across when it stopped responding on on the network. When i looked at the console it was showing a load of disk errors and when i rebooted it got the same errors as with the Transcend unit. I've disabled the onboard NIC and fitted a Netgear one i had lying around. I had to unplug the Megaraid adaptor to get it to boot at all. It allocated a different IRQ (11) but stupidly i re-enabled ESCD which then again shared IRQ 10. It's busy checking and repairing the file system with some 'SOME DATA MAY BE LOST' errors. Luckily i hadn't started using it as my main system.
I can't understand why it needs to share an IRQ as i have everything i don't need (LPT, serial, usb, secondary IDE etc) turned off.
Looks like a bit more work getting it set up and lots of testing.
Top
 Profile  
 
willsy
 Post subject:
PostPosted: Sun Nov 25, 2007 1:59 pm 
Offline

Joined: Mon Apr 17, 2006 12:55 pm
Posts: 143
Location: Newcastle
Don't know if anybody can give me a bit of help.
I can't get the system to stop sharing an IRQ (usually IRQ10)with the Megaraid card and either the onboard NIC or one in a PCI slot. I've tried the following:-
1. Removed Raid card and with onboard NIC enabled, set IRQ10 to reserved - Allocates IRQ 12 to onboard NIC.
2. Refit Raid card and reset IRQ to PCI device - reverts to IRQ 10 for both devices.
3. As above but leaving IRQ10 reserved - both devices allocated IRQ12
4. Fit NIC in a PCI slot, disable onboard NIC - Both IRQ10
5. As 4 but re-enable onboard NIC - onboard given IRQ12, PCI NIC and Raid card IRQ10
I've tried to remember to reset ESCD when applicable, and am unable to allocate IRQ's individually. There is only one PCI-X slot and 2 PCI slots, and i've tried the NIC in both.

Any suggestions would be appreciated.
Top
 Profile  
 
dimension
 Post subject:
PostPosted: Sun Nov 25, 2007 3:07 pm 
Offline

Joined: Tue Aug 10, 2004 1:50 pm
Posts: 604
Location: Texas, USA
BIOS can be strange at times. In some cases I've found that disabling PNP in the BIOS allows for correct IRQ reallocation. You have to make sure all the unneeded stuff is disabled tho. In some cases I even kill USB support. USB can be an IRQ pig, so on HDD it too can be disabled.
Top
 Profile  
 
willsy
 Post subject:
PostPosted: Sun Nov 25, 2007 3:25 pm 
Offline

Joined: Mon Apr 17, 2006 12:55 pm
Posts: 143
Location: Newcastle
i've got everything i can disabled apart from the Primary IDE channel. TBH i'm thinkng about junking (selling on ebay) the board & CPU and getting a different one, however the choice is a bit limited on boards with PCI-X.
Top
 Profile  
 
willsy
 Post subject:
PostPosted: Sun Nov 25, 2007 7:45 pm 
Offline

Joined: Mon Apr 17, 2006 12:55 pm
Posts: 143
Location: Newcastle
Got Eth0 (PCI Nic) on IRQ10, onboard Nic (enabled but not being used) at IRQ12, and the RAID card at IRQ12. I've had to format the RAID volume - too many errors, and was just looping on the find and fix errors option.
I might go into the BIOS and disable the onboard NIC and see what happens.
Both Nics are the same Realtek chipset. Is there any mileage in trying a decent quality (e.g. Intel) one just in case it's the Nic causing the problem?
Top
 Profile  
 
NickC
 Post subject:
PostPosted: Mon Nov 26, 2007 8:53 am 
Offline

Joined: Fri Jan 12, 2007 4:27 am
Posts: 577
Location: Scotland
I make it a point to switch everything that I'm not using off in BIOS. It took a few permutations to get my ASUS M2N32 WS PRO to shutdown without crashing with a kernel panic due to IRQ conflict.
Top
 Profile  
 
willsy
 Post subject:
PostPosted: Mon Nov 26, 2007 4:42 pm 
Offline

Joined: Mon Apr 17, 2006 12:55 pm
Posts: 143
Location: Newcastle
I was just about to give up, or even worse considered getting a copy of Windows Home Server :wink:. when I gave it one last few goes and would you Adam & Eve it - server log showed separate IRQ's for the PCI Nic and Raid card. Worse thing is i can't remember the sequence i did it in.
Now i'm scared to try the Transcend flash drive.
Now for a few days testing

Thanks for all the help and suggestions
Top
 Profile  
 
PieterB
 Post subject:
PostPosted: Fri Nov 30, 2007 12:23 pm 
Offline

Joined: Sat Mar 03, 2007 6:25 pm
Posts: 294
Location: Delft NL / Brooklyn NY
As mentioned elsewhere: no problems whatsoever.

MoBo: Intel D915PSYL
Processor: Socket 775 P4 630
Memory: 2x 512 Kingston Value RAM KVR400X64C3A/512
Graphics: Asus EN6200LE TC256/TD graphic adapter
HDD: Transcend IDE flash 32Mb voor NasLite 2 HDD
SATA RAID controller: 3ware 8006-2LP 2-port SATA RAID
Harddisk: 2x Seagate 500Mb Barracuda 7200/10
Box: Antec NSK4400 incl 380W voeding
DVD: Samsung SH-D163B DVD drive SATA
Floppy: generic No Brand
Top
 Profile  
 
willsy
 Post subject:
PostPosted: Sun Dec 23, 2007 7:24 am 
Offline

Joined: Mon Apr 17, 2006 12:55 pm
Posts: 143
Location: Newcastle
Just had another major filesystem error . I had been running the system for a few weeks and all seemed stable, so last night i decided to do the changeover. Everything was fine - watched about 4 hours of recorded tv, then the music video i was watching froze (coincedentally at about the same time as i shut the old server down).

I've listed my syslog below. I'm just about ready to abandon this setup unless someone can point out the problem. Could the stripe size on my raid setup be causing any problems?

Quote:
Dec 22 08:46:38 user.notice kernel: klogd started: BusyBox v1.01 (2007.03.15-22:03+0000)
Dec 22 08:46:38 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
Dec 22 08:46:38 user.info kernel: BIOS-provided physical RAM map:
Dec 22 08:46:38 user.warn kernel: BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
Dec 22 08:46:38 user.warn kernel: BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
Dec 22 08:46:38 user.warn kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Dec 22 08:46:38 user.warn kernel: BIOS-e820: 0000000000100000 - 000000001dff0000 (usable)
Dec 22 08:46:38 user.warn kernel: BIOS-e820: 000000001dff0000 - 000000001dff3000 (ACPI NVS)
Dec 22 08:46:38 user.warn kernel: BIOS-e820: 000000001dff3000 - 000000001e000000 (ACPI data)
Dec 22 08:46:38 user.warn kernel: BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
Dec 22 08:46:38 user.notice kernel: 0MB HIGHMEM available.
Dec 22 08:46:38 user.notice kernel: 479MB LOWMEM available.
Dec 22 08:46:38 user.warn kernel: On node 0 totalpages: 122864
Dec 22 08:46:38 user.warn kernel: zone(0): 4096 pages.
Dec 22 08:46:38 user.warn kernel: zone(1): 118768 pages.
Dec 22 08:46:38 user.warn kernel: zone(2): 0 pages.
Dec 22 08:46:38 user.info kernel: ACPI: RSDP (v000 IntelR ) @ 0x000f8e90
Dec 22 08:46:38 user.info kernel: ACPI: RSDT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1dff3040
Dec 22 08:46:38 user.info kernel: ACPI: FADT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1dff30c0
Dec 22 08:46:38 user.info kernel: ACPI: DSDT (v001 INTELR AWRDACPI 0x00001000 MSFT 0x0100000e) @ 0x00000000
Dec 22 08:46:38 user.warn kernel: Kernel command line: rw root=/dev/ram0 initrd=NASLite.02 quiet BOOT_IMAGE=naslite.01
Dec 22 08:46:38 user.info kernel: Initializing CPU#0
Dec 22 08:46:38 user.warn kernel: Detected 1703.901 MHz processor.
Dec 22 08:46:38 user.warn kernel: Console: colour VGA+ 80x25
Dec 22 08:46:38 user.warn kernel: Calibrating delay loop. 3394.76 BogoMIPS
Dec 22 08:46:38 user.info kernel: Memory: 479664k/491456k available (2214k kernel code, 11404k reserved, 642k data, 540k init, 0k highmem)
Dec 22 08:46:38 user.info kernel: Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Dec 22 08:46:38 user.info kernel: Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
Dec 22 08:46:38 user.info kernel: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Dec 22 08:46:38 user.info kernel: Buffer cache hash table entries: 32768 (order: 5, 131072 bytes)
Dec 22 08:46:38 user.warn kernel: Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
Dec 22 08:46:38 user.info kernel: CPU: L1 I cache: 32K, L1 D cache: 32K
Dec 22 08:46:38 user.debug kernel: CPU: After generic, caps: afe9fbbf 00000000 00000000 00000000
Dec 22 08:46:38 user.debug kernel: CPU: Common caps: afe9fbbf 00000000 00000000 00000000
Dec 22 08:46:38 user.warn kernel: CPU: Intel(R) Pentium(R) M processor 1.70GHz stepping 06
Dec 22 08:46:38 user.info kernel: Enabling fast FPU save and restore. done.
Dec 22 08:46:38 user.info kernel: Enabling unmasked SIMD FPU exception support. done.
Dec 22 08:46:38 user.info kernel: Checking 'hlt' instruction. OK.
Dec 22 08:46:38 user.warn kernel: ACPI: IRQ9 SCI: Edge set to Level Trigger.
Dec 22 08:46:38 user.warn kernel: POSIX conformance testing by UNIFIX
Dec 22 08:46:38 user.warn kernel: mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
Dec 22 08:46:38 user.warn kernel: mtrr: detected mtrr type: Intel
Dec 22 08:46:38 user.info kernel: ACPI: Subsystem revision 20040326
Dec 22 08:46:38 user.info kernel: PCI: PCI BIOS revision 2.10 entry at 0xfae80, last bus=3
Dec 22 08:46:38 user.info kernel: PCI: Using configuration type 1
Dec 22 08:46:38 user.info kernel: ACPI: Interpreter enabled
Dec 22 08:46:38 user.info kernel: ACPI: Using PIC for interrupt routing
Dec 22 08:46:38 user.info kernel: ACPI: System [ACPI] (supports S0 S1 S4 S5)
Dec 22 08:46:38 user.info kernel: ACPI: PCI Root Bridge [PCI0] (00:00)
Dec 22 08:46:38 user.warn kernel: PCI: Probing PCI hardware (bus 00)
Dec 22 08:46:38 user.info kernel: PCI: Ignoring BAR0-3 of IDE controller 00:1f.1
Dec 22 08:46:38 user.warn kernel: Transparent bridge - PCI device 8086:244e
Dec 22 08:46:38 user.debug kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Dec 22 08:46:38 user.debug kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
Dec 22 08:46:38 user.debug kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HRB_._PRT]
Dec 22 08:46:38 user.warn kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 7 9 10 11 12 14 15)
Dec 22 08:46:38 user.warn kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 *4 5 7 9 10 11 12 14 15)
Dec 22 08:46:38 user.warn kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
Dec 22 08:46:38 user.warn kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 7 9 10 11 12 14 15)
Dec 22 08:46:38 user.warn kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
Dec 22 08:46:38 user.warn kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 9 10 11 *12 14 15)
Dec 22 08:46:38 user.warn kernel: ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
Dec 22 08:46:38 user.warn kernel: ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 *7 9 10 11 12 14 15)
Dec 22 08:46:38 user.info kernel: PCI: Probing PCI hardware
Dec 22 08:46:38 user.warn kernel: ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 5
Dec 22 08:46:38 user.warn kernel: ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
Dec 22 08:46:38 user.warn kernel: ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 4
Dec 22 08:46:38 user.warn kernel: ACPI: PCI Interrupt Link [LNK0] enabled at IRQ 10
Dec 22 08:46:38 user.warn kernel: ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 12
Dec 22 08:46:38 user.warn kernel: ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 7
Dec 22 08:46:38 user.info kernel: PCI: Using ACPI for IRQ routing
Dec 22 08:46:38 user.info kernel: Linux NET4.0 for Linux 2.4
Dec 22 08:46:38 user.info kernel: Based upon Swansea University Computer Society NET3.039
Dec 22 08:46:38 user.warn kernel: Initializing RT netlink socket
Dec 22 08:46:38 user.warn kernel: Starting kswapd
Dec 22 08:46:38 user.info kernel: Journalled Block Device driver loaded
Dec 22 08:46:38 user.info kernel: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
Dec 22 08:46:38 user.info kernel: devfs: boot_options: 0x1
Dec 22 08:46:38 user.info kernel: nfsd (copyright (C) 1996 okir@monad.swb.de).
Dec 22 08:46:38 user.info kernel: ACPI: Power Button (FF) [PWRF]
Dec 22 08:46:38 user.info kernel: ACPI: Fan [FAN] (on)
Dec 22 08:46:38 user.info kernel: ACPI: Processor [CPU0] (supports C1, 2 throttling states)
Dec 22 08:46:38 user.info kernel: ACPI: Thermal Zone [THRM] (23 C)
Dec 22 08:46:38 user.warn kernel: pty: 256 Unix98 ptys configured
Dec 22 08:46:38 user.info kernel: Real Time Clock Driver v1.10f
Dec 22 08:46:38 user.warn kernel: floppy0: no floppy controllers found
Dec 22 08:46:38 user.warn kernel: RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
Dec 22 08:46:38 user.info kernel: loop: loaded (max 8 devices)
Dec 22 08:46:38 user.info kernel: Intel(R) PRO/1000 Network Driver - version 7.3.20-k4
Dec 22 08:46:38 user.info kernel: Copyright (c) 1999-2006 Intel Corporation.
Dec 22 08:46:38 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
Dec 22 08:46:38 user.warn kernel: FW Version=$Version$
Dec 22 08:46:38 user.info kernel: pcnet32.c:v1.30h 06.24.2004 tsbogend@alpha.franken.de
Dec 22 08:46:38 user.info kernel: ThunderLAN driver v1.15
Dec 22 08:46:38 user.info kernel: TLAN: 0 devices installed, PCI: 0 EISA: 0
Dec 22 08:46:38 user.info kernel: dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
Dec 22 08:46:38 user.info kernel: ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
Dec 22 08:46:38 user.warn kernel: sk98lin: No adapter found.
Dec 22 08:46:38 user.info kernel: forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.50.
Dec 22 08:46:38 user.info kernel: r8169 Gigabit Ethernet driver 1.2 loaded
Dec 22 08:46:38 user.debug kernel: eth0: Identified chip type is 'RTL8169s/8110s'.
Dec 22 08:46:38 user.info kernel: eth0: RTL8169 at 0xde808000, 00:0f:b5:fb:40:a6, IRQ 12
Dec 22 08:46:38 user.info kernel: eth0: Auto-negotiation Enabled.
Dec 22 08:46:38 user.info kernel: eth0: 100Mbps Full-duplex operation.
Dec 22 08:46:38 user.info kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
Dec 22 08:46:38 user.info kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Dec 22 08:46:38 user.info kernel: ICH5: IDE controller at PCI slot 00:1f.1
Dec 22 08:46:38 user.info kernel: ICH5: chipset revision 2
Dec 22 08:46:38 user.info kernel: ICH5: not 100% native mode: will probe irqs later
Dec 22 08:46:38 user.info kernel: ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, hdb:pio
Dec 22 08:46:38 user.warn kernel: hda: CF CARD 1GB, ATA DISK drive
Dec 22 08:46:38 user.warn kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Dec 22 08:46:38 user.warn kernel: hda: attached ide-disk driver.
Dec 22 08:46:38 user.info kernel: hda: 1981728 sectors (1015 MB) w/1KiB Cache, CHS=983/32/63, DMA
Dec 22 08:46:38 user.info kernel: Partition check:
Dec 22 08:46:38 user.info kernel: /dev/ide/host0/bus0/target0/lun0:<4>hda: dma_timer_expiry: dma status == 0x21
Dec 22 08:46:38 user.err kernel: hda: error waiting for DMA
Dec 22 08:46:38 user.warn kernel: hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 22 08:46:38 user.warn kernel:
Dec 22 08:46:38 user.warn kernel: p1 p2
Dec 22 08:46:38 user.info kernel: SCSI subsystem driver Revision: 1.00
Dec 22 08:46:38 user.info kernel: Loading Adaptec I2O RAID: Version 2.4 Build 5
Dec 22 08:46:38 user.info kernel: Detecting Adaptec I2O RAID controllers.
Dec 22 08:46:38 user.info kernel: Red Hat/Adaptec aacraid driver (1.1-3 Aug 12 2007 09:05:44)
Dec 22 08:46:38 user.warn kernel: scsi: Detection failed (no card)
Dec 22 08:46:38 user.notice kernel: megaraid: v2.10.10.1 (Release Date: Thu Jan 27 16:19:44 EDT 2005)
Dec 22 08:46:38 user.notice kernel: megaraid: found 0x1000:0x0409:bus 2:slot 14:func 0
Dec 22 08:46:38 user.notice kernel: scsi1:Found MegaRAID controller at 0xde80c000, IRQ:10
Dec 22 08:46:38 user.notice kernel: megaraid: [813J:H430] detected 1 logical drives.
Dec 22 08:46:38 user.notice kernel: megaraid: supports extended CDBs.
Dec 22 08:46:38 user.info kernel: megaraid: channel[0] is raid.
Dec 22 08:46:38 user.info kernel: scsi1 : LSI Logic MegaRAID 813J 254 commands 16 targs 4 chans 7 luns
Dec 22 08:46:38 user.notice kernel: scsi1: scanning scsi channel 0 for logical drives.
Dec 22 08:46:38 user.warn kernel: Vendor: MegaRAID Model: LD 0 RAID5 1907G Rev: 813J
Dec 22 08:46:38 user.warn kernel: Type: Direct-Access ANSI SCSI revision: 02
Dec 22 08:46:38 user.notice kernel: scsi1: scanning scsi channel 1 for logical drives.
Dec 22 08:46:38 user.notice kernel: scsi1: scanning scsi channel 2 for logical drives.
Dec 22 08:46:38 user.notice kernel: scsi1: scanning scsi channel 3 for logical drives.
Dec 22 08:46:38 user.notice kernel: scsi1: scanning scsi channel 4 [P0] for physical devices.
Dec 22 08:46:38 user.warn kernel: GDT-HA: Storage RAID Controller Driver. Version: 3.04
Dec 22 08:46:38 user.warn kernel: GDT-HA: Found 0 PCI Storage RAID Controllers
Dec 22 08:46:38 user.warn kernel: 3ware Storage Controller device driver for Linux v1.02.00.037.
Dec 22 08:46:38 user.warn kernel: 3w-xxxx: No cards found.
Dec 22 08:46:38 user.debug kernel: libata version 1.20 loaded.
Dec 22 08:46:38 user.warn kernel: Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
Dec 22 08:46:38 user.warn kernel: SCSI device sda: 3906248704 512-byte hdwr sectors (1999999 MB)
Dec 22 08:46:38 user.info kernel: /dev/scsi/host1/bus0/target0/lun0: p1
Dec 22 08:46:38 user.info kernel: ohci1394: $Rev: 1045 $ Ben Collins
Dec 22 08:46:38 user.info kernel: ohci1394_0: OHCI-1394 1.1 (PCI): IRQ=[7] MMIO=[e8320000-e83207ff] Max Packet=[2048]
Dec 22 08:46:38 user.info kernel: raw1394: /dev/raw1394 device initialized
Dec 22 08:46:38 user.info kernel: sbp2: $Rev: 1074 $ Ben Collins
Dec 22 08:46:38 user.err kernel: ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
Dec 22 08:46:38 user.info kernel: usb.c: registered new driver usbdevfs
Dec 22 08:46:38 user.info kernel: usb.c: registered new driver hub
Dec 22 08:46:38 user.info kernel: host/uhci.c: USB Universal Host Controller Interface driver v1.1
Dec 22 08:46:38 user.info kernel: usb.c: registered new driver usbkbd
Dec 22 08:46:38 user.info kernel: usbkbd.c: :USB HID Boot Protocol keyboard driver
Dec 22 08:46:38 user.info kernel: Initializing USB Mass Storage driver.
Dec 22 08:46:38 user.info kernel: usb.c: registered new driver usb-storage
Dec 22 08:46:38 user.info kernel: USB Mass Storage support registered.
Dec 22 08:46:38 user.info kernel: .0
Dec 22 08:46:38 user.info kernel: IP Protocols: ICMP, UDP, TCP
Dec 22 08:46:38 user.info kernel: IP: routing cache hash table of 4096 buckets, 32Kbytes
Dec 22 08:46:38 user.info kernel: TCP: Hash tables configured (established 32768 bind 65536)
Dec 22 08:46:38 user.info kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Dec 22 08:46:38 user.notice kernel: RAMDISK: NASLite file system found at block 0
Dec 22 08:46:38 user.warn kernel: <7>ieee1394: Host added: ID:BUS[0-00:1023] GUID[0001291000046c01]
Dec 22 08:46:38 user.warn kernel: <6>Freeing initrd memory: 1962k freed
Dec 22 08:46:38 user.warn kernel: VFS: Mounted root (ext2 filesystem).
Dec 22 08:46:38 user.info kernel: Mounted devfs on /dev
Dec 22 08:46:38 user.info kernel: Freeing unused kernel memory: 540k freed
Dec 22 08:46:38 user.warn kernel: hda: dma_timer_expiry: dma status == 0x21
Dec 22 08:46:38 user.err kernel: hda: error waiting for DMA
Dec 22 08:46:38 user.warn kernel: hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 22 08:46:38 user.warn kernel:
Dec 22 08:46:38 user.warn kernel: hda: dma_timer_expiry: dma status == 0x21
Dec 22 08:46:38 user.err kernel: hda: error waiting for DMA
Dec 22 08:46:38 user.warn kernel: hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 22 08:46:38 user.warn kernel:
Dec 22 08:46:38 user.warn kernel: hda: dma_timer_expiry: dma status == 0x21
Dec 22 08:46:38 user.err kernel: hda: error waiting for DMA
Dec 22 08:46:38 user.warn kernel: hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 22 08:46:38 user.warn kernel:
Dec 22 08:46:38 user.info kernel: kjournald starting. Commit interval 5 seconds
Dec 22 08:46:38 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal
Dec 22 08:46:38 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
Dec 22 23:38:10 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:40:10 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:41:01 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #32769: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:41:03 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #32769: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:42:03 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:42:34 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:42:34 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:44:56 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:45:36 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:45:36 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:45:37 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:45:59 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:46:05 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:46:06 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:46:07 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:47:45 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:47:45 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:47:54 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:47:54 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:49:28 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:49:50 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:51:38 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:52:09 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:52:09 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:53:02 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:54:25 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:54:29 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:54:29 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:57:48 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:57:48 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 22 23:57:53 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 23 00:03:36 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 23 00:03:36 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 23 00:06:27 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 23 00:06:27 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 23 00:31:33 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 23 00:31:33 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 23 00:31:34 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 23 00:31:39 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 23 00:32:13 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 23 00:32:13 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 23 00:32:15 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 23 00:46:24 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 23 00:46:24 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 23 00:46:26 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 23 01:16:34 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 23 01:16:34 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 23 01:17:55 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 23 01:17:56 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Dec 23 01:18:02 user.crit kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0


Top
 Profile  
 
dimension
 Post subject:
PostPosted: Mon Dec 24, 2007 11:12 am 
Offline

Joined: Tue Aug 10, 2004 1:50 pm
Posts: 604
Location: Texas, USA
willsy,

You are having all kinds of problems according to your logs willsy. The kernel is complaining about your ide drive as well as the raid. You need to track that down man. Are you using the right cables for the drives. Make sure your ide drives have ata133 rated cables and the sata drives are set to sata and not sata2. The power still may be a cause but my money is on cables.

you may have to reset the bios to defaults and then go back and shut things down again. That sometime works as does turning PnP off. Make sure you do a cold reboot after changing the settings.

Just guessing here. You'll have to experiment.
Top
 Profile  
 
willsy
 Post subject:
PostPosted: Mon Dec 24, 2007 12:55 pm 
Offline

Joined: Mon Apr 17, 2006 12:55 pm
Posts: 143
Location: Newcastle
I'm booting from a CF card ATM, think i might try a 2.5" hard drive i have.
I need to look at the motherboard manual to see if it supports SATA2, would this make a difference as the drives are connected to a RAID card?
Looks like a bit more work before i can trust this setup. Ah well!!
Top
 Profile  
 
willsy
 Post subject:
PostPosted: Fri Dec 28, 2007 7:15 pm 
Offline

Joined: Mon Apr 17, 2006 12:55 pm
Posts: 143
Location: Newcastle
Think it might be a conflict with the raid card and the mainboard. Can't tell for sure as i've tried a spare card which won't even get to the bios setup. just waiting for a reply on the actual condition of the spare card. I'll not be too happy if i've been sold a couple of duds.

Edit
Finally got it working - one of the BIOS settings from the previous attempt was causing it to hang. Thought i'd set everything back. Now to try and solve the IRQ sharing again.
Top
 Profile  
 
willsy
 Post subject:
PostPosted: Wed Jan 02, 2008 5:13 pm 
Offline

Joined: Mon Apr 17, 2006 12:55 pm
Posts: 143
Location: Newcastle
Now testing my rebuilt setup - ditched the CF card, tried the Transcend module but kept getting a kernel panic error (might be the power cable supplied with the module (similar to PieterB's problem) so am now running a 2.5" laptop drive as a boot drive (mainly to save on power as i'm worried about overloading the power supply), spare RAID card, and changed to some different memory sticks just to be sure that wasn't causing the problem. Just testing now - i'll stress it a bit more this time to make sure before switching over.
Fingers crossed!!
Top
 Profile  
 
PieterB
 Post subject: Re: New setup
PostPosted: Tue Jan 15, 2008 12:44 pm 
Offline

Joined: Sat Mar 03, 2007 6:25 pm
Posts: 294
Location: Delft NL / Brooklyn NY
willsy wrote:
(might be the power cable supplied with the module (similar to PieterB's problem)


I think I never explained why my Transcend module didn't work properly. Of course there was the power cable, but basically the whole problem arose because I bended one of the 40 pins in the IDE connector. That was kinda stupid.

I just returned from a three week visit to the US, and 'worked' from there through MS Remote Desktop with files stored on the NASLite box. Three weeks uptime, no hickups.

Still very pleased with my NAS box.
Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 3 of 5
  [ 68 posts ]  Go to page Previous  1, 2, 3, 4, 5  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 25 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:  
Powered by phpBB® Forum Software © phpBB Group