NASLite Network Attached Storage

Hi,

I've decided to upgrade my hardware and I've moved my Naslite USB on a new PC.

Naslite boots from a CF and the Array is composed by 6 320GB SATA Disks connected to an LSILogic MegaRaid 150-6.

The new PC has other 2 MegaRaid 150-4.

The data resided on the 6 disk connected to the 150-6 in a RAID5 config

While Physically moving the disks, the SATA connector on number 4 got broken, everything should be fine due to the RAID 5.

I've connected the disks in the new hardware in the same chain as before but the Array fails.

On the array there is something like 1.2TB of data and I do not know hot to recover from this disastrous situation.

The Array is fine, I've already run the checkdisk also with the repair option but NasLite doesn't want to bring the data back.

this is what I get from the SysLog:

System Message Log:

* Apr 7 05:50:23 syslog.info syslogd started: BusyBox v1.01 (2006.02.26-22:07+0000)
* Apr 7 05:50:23 daemon.info init: ^MStarting pid 1571, console /dev/null: '/sbin/klogd'
* Apr 7 05:50:23 user.notice kernel: klogd started: BusyBox v1.01 (2006.02.26-22:07+0000)
* Apr 7 05:50:23 user.warn kernel: Linux version 2.4.33.NASLite (root@TZT) (gcc version 3.3.6) #1 Tue Aug 15 01:08:13 UTC 2006
* Apr 7 05:50:23 user.info kernel: BIOS-provided physical RAM map:
* Apr 7 05:50:23 user.warn kernel: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
* Apr 7 05:50:23 user.warn kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
* Apr 7 05:50:23 user.warn kernel: BIOS-e820: 0000000000100000 - 000000003ffec000 (usable)
* Apr 7 05:50:23 user.warn kernel: BIOS-e820: 000000003ffec000 - 000000003ffef000 (ACPI data)
* Apr 7 05:50:23 user.warn kernel: BIOS-e820: 000000003ffef000 - 000000003ffff000 (reserved)
* Apr 7 05:50:23 user.warn kernel: BIOS-e820: 000000003ffff000 - 0000000040000000 (ACPI NVS)
* Apr 7 05:50:23 user.warn kernel: BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
* Apr 7 05:50:23 user.warn kernel: BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
* Apr 7 05:50:23 user.warn kernel: BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
* Apr 7 05:50:23 user.warn kernel: Warning only 896MB will be used.
* Apr 7 05:50:23 user.warn kernel: Use a HIGHMEM enabled kernel.
* Apr 7 05:50:23 user.notice kernel: 896MB LOWMEM available.
* Apr 7 05:50:23 user.warn kernel: On node 0 totalpages: 229376
* Apr 7 05:50:23 user.warn kernel: zone(0): 4096 pages.
* Apr 7 05:50:23 user.warn kernel: zone(1): 225280 pages.
* Apr 7 05:50:23 user.warn kernel: zone(2): 0 pages.
* Apr 7 05:50:23 user.notice kernel: ASUS P4B266 detected: force use of acpi=ht
* Apr 7 05:50:23 user.info kernel: ACPI: RSDP (v000 ASUS ) @ 0x000f7720
* Apr 7 05:50:23 user.info kernel: ACPI: RSDT (v001 ASUS P4B266 0x42302e31 MSFT 0x31313031) @ 0x3ffec000
* Apr 7 05:50:23 user.info kernel: ACPI: FADT (v001 ASUS P4B266 0x42302e31 MSFT 0x31313031) @ 0x3ffec100
* Apr 7 05:50:23 user.info kernel: ACPI: BOOT (v001 ASUS P4B266 0x42302e31 MSFT 0x31313031) @ 0x3ffec040
* Apr 7 05:50:23 user.info kernel: ACPI: MADT (v001 ASUS P4B266 0x42302e31 MSFT 0x31313031) @ 0x3ffec080
* Apr 7 05:50:23 user.info kernel: ACPI: DSDT (v001 ASUS P4B266 0x00001000 MSFT 0x0100000b) @ 0x00000000
* Apr 7 05:50:23 user.warn kernel: Kernel command line: rw root=/dev/ram0 initrd=NASLite.02 quiet BOOT_IMAGE=naslite.01
* Apr 7 05:50:23 user.info kernel: Initializing CPU#0
* Apr 7 05:50:23 user.warn kernel: Detected 2017.985 MHz processor.
* Apr 7 05:50:23 user.warn kernel: Console: colour VGA+ 80x25
* Apr 7 05:50:23 user.warn kernel: Calibrating delay loop. 4023.91 BogoMIPS
* Apr 7 05:50:23 user.info kernel: Memory: 901896k/917504k available (2198k kernel code, 15224k reserved, 734k data, 536k init, 0k highmem)
* Apr 7 05:50:23 user.info kernel: Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
* Apr 7 05:50:23 user.info kernel: Inode cache hash table entries: 65536 (order: 7, 524288 bytes)
* Apr 7 05:50:23 user.info kernel: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
* Apr 7 05:50:23 user.info kernel: Buffer cache hash table entries: 65536 (order: 6, 262144 bytes)
* Apr 7 05:50:23 user.warn kernel: Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
* Apr 7 05:50:23 user.info kernel: CPU: Trace cache: 12K uops, L1 D cache: 8K
* Apr 7 05:50:23 user.info kernel: CPU: L2 cache: 512K
* Apr 7 05:50:23 user.debug kernel: CPU: After generic, caps: 3febfbff 00000000 00000000 00000000
* Apr 7 05:50:23 user.debug kernel: CPU: Common caps: 3febfbff 00000000 00000000 00000000
* Apr 7 05:50:23 user.warn kernel: CPU: Intel(R) Pentium(R) 4 CPU 2.00GHz stepping 04
* Apr 7 05:50:23 user.info kernel: Enabling fast FPU save and restore. done.
* Apr 7 05:50:23 user.info kernel: Enabling unmasked SIMD FPU exception support. done.
* Apr 7 05:50:23 user.info kernel: Checking 'hlt' instruction. OK.
* Apr 7 05:50:23 user.info kernel: Checking for popad bug. OK.
* Apr 7 05:50:23 user.warn kernel: POSIX conformance testing by UNIFIX
* Apr 7 05:50:23 user.info kernel: ACPI: Subsystem revision 20040326
* Apr 7 05:50:23 user.info kernel: ACPI: Interpreter disabled.
* Apr 7 05:50:23 user.info kernel: PCI: PCI BIOS revision 2.10 entry at 0xf1090, last bus=2
* Apr 7 05:50:23 user.info kernel: PCI: Using configuration type 1
* Apr 7 05:50:23 user.info kernel: PCI: Probing PCI hardware
* Apr 7 05:50:23 user.warn kernel: PCI: Probing PCI hardware (bus 00)
* Apr 7 05:50:23 user.info kernel: PCI: Enabled i801 SMBus device
* Apr 7 05:50:23 user.warn kernel: Transparent bridge - PCI device 8086:244e
* Apr 7 05:50:23 user.info kernel: PCI: Using IRQ router PIIX/ICH [8086/2440] at 00:1f.0
* Apr 7 05:50:23 user.info kernel: Linux NET4.0 for Linux 2.4
* Apr 7 05:50:23 user.info kernel: Based upon Swansea University Computer Society NET3.039
* Apr 7 05:50:23 user.warn kernel: Initializing RT netlink socket
* Apr 7 05:50:23 user.warn kernel: Starting kswapd
* Apr 7 05:50:23 user.info kernel: Journalled Block Device driver loaded
* Apr 7 05:50:23 user.info kernel: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
* Apr 7 05:50:23 user.info kernel: devfs: boot_options: 0x1
* Apr 7 05:50:23 user.info kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
* Apr 7 05:50:23 user.warn kernel: pty: 256 Unix98 ptys configured
* Apr 7 05:50:23 user.info kernel: Real Time Clock Driver v1.10f
* Apr 7 05:50:23 user.warn kernel: floppy0: no floppy controllers found
* Apr 7 05:50:23 user.warn kernel: RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
* Apr 7 05:50:23 user.info kernel: loop: loaded (max 8 devices)
* Apr 7 05:50:23 user.info kernel: Intel(R) PRO/1000 Network Driver - version 5.7.6-k1
* Apr 7 05:50:23 user.info kernel: Copyright (c) 1999-2004 Intel Corporation.
* Apr 7 05:50:23 user.info kernel: PCI: Found IRQ 7 for device 02:09.0
* Apr 7 05:50:23 user.info kernel: PCI: Sharing IRQ 7 with 02:03.0
* Apr 7 05:50:23 user.info kernel: PCI: Sharing IRQ 7 with 02:0d.0
* Apr 7 05:50:23 user.info kernel: e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
* Apr 7 05:50:23 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
* Apr 7 05:50:23 user.warn kernel: FW Version=$Version$
* Apr 7 05:50:23 user.info kernel: pcnet32.c:v1.30h 06.24.2004 tsbogend@alpha.franken.de
* Apr 7 05:50:23 user.info kernel: ThunderLAN driver v1.15
* Apr 7 05:50:23 user.info kernel: TLAN: 0 devices installed, PCI: 0 EISA: 0
* Apr 7 05:50:23 user.info kernel: dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
* Apr 7 05:50:23 user.info kernel: ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
* Apr 7 05:50:23 user.emerg kernel: 4>sk98lin: No adapter found.
* Apr 7 05:50:23 user.info kernel: forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.50.
* Apr 7 05:50:23 user.info kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
* Apr 7 05:50:23 user.info kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
* Apr 7 05:50:23 user.info kernel: ICH2: IDE controller at PCI slot 00:1f.1
* Apr 7 05:50:23 user.info kernel: ICH2: chipset revision 5
* Apr 7 05:50:23 user.info kernel: ICH2: not 100% native mode: will probe irqs later
* Apr 7 05:50:23 user.info kernel: ide0: BM-DMA at 0xb800-0xb807, BIOS settings: hda:DMA, hdb:pio
* Apr 7 05:50:23 user.info kernel: ide1: BM-DMA at 0xb808-0xb80f, BIOS settings: hdc:pio, hdd:pio
* Apr 7 05:50:23 user.warn kernel: hda: KINGSTON, ATA DISK drive
* Apr 7 05:50:23 user.warn kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
* Apr 7 05:50:23 user.warn kernel: hda: attached ide-disk driver.
* Apr 7 05:50:23 user.info kernel: hda: 1014048 sectors (519 MB) w/1KiB Cache, CHS=1980/16/32, DMA
* Apr 7 05:50:23 user.info kernel: Partition check:
* Apr 7 05:50:23 user.info kernel: /dev/ide/host0/bus0/target0/lun0: p1
* Apr 7 05:50:23 user.info kernel: SCSI subsystem driver Revision: 1.00
* Apr 7 05:50:23 user.info kernel: Loading Adaptec I2O RAID: Version 2.4 Build 5
* Apr 7 05:50:23 user.info kernel: Detecting Adaptec I2O RAID controllers.
* Apr 7 05:50:23 user.info kernel: Red Hat/Adaptec aacraid driver (1.1-3 Aug 15 2006 01:22:52)
* Apr 7 05:50:23 user.warn kernel: scsi: Detection failed (no card)
* Apr 7 05:50:23 user.notice kernel: megaraid: v2.10.10.1 (Release Date: Thu Jan 27 16:19:44 EDT 2005)
* Apr 7 05:50:23 user.info kernel: PCI: Found IRQ 3 for device 02:0c.0
* Apr 7 05:50:23 user.notice kernel: megaraid: found 0x1000:0x1960:bus 2:slot 12:func 0
* Apr 7 05:50:23 user.notice kernel: scsi1:Found MegaRAID controller at 0xf8823000, IRQ:3
* Apr 7 05:50:23 user.notice kernel: megaraid: [713^:G121] detected 1 logical drives.
* Apr 7 05:50:23 user.notice kernel: megaraid: supports extended CDBs.
* Apr 7 05:50:23 user.info kernel: megaraid: channel[0] is raid.
* Apr 7 05:50:23 user.info kernel: PCI: Found IRQ 7 for device 02:0d.0
* Apr 7 05:50:23 user.info kernel: PCI: Sharing IRQ 7 with 02:03.0
* Apr 7 05:50:23 user.info kernel: PCI: Sharing IRQ 7 with 02:09.0
* Apr 7 05:50:23 user.notice kernel: megaraid: found 0x1000:0x1960:bus 2:slot 13:func 0
* Apr 7 05:50:23 user.notice kernel: scsi2:Found MegaRAID controller at 0xf8825000, IRQ:7
* Apr 7 05:50:23 user.notice kernel: megaraid: [713R:G121] detected 1 logical drives.
* Apr 7 05:50:23 user.notice kernel: megaraid: supports extended CDBs.
* Apr 7 05:50:23 user.info kernel: megaraid: channel[0] is raid.
* Apr 7 05:50:23 user.info kernel: PCI: Found IRQ 10 for device 02:0e.0
* Apr 7 05:50:23 user.notice kernel: megaraid: found 0x1000:0x1960:bus 2:slot 14:func 0
* Apr 7 05:50:23 user.notice kernel: scsi3:Found MegaRAID controller at 0xf8827000, IRQ:10
* Apr 7 05:50:23 user.notice kernel: megaraid: [713R:G121] detected 1 logical drives.
* Apr 7 05:50:23 user.notice kernel: megaraid: supports extended CDBs.
* Apr 7 05:50:23 user.info kernel: megaraid: channel[0] is raid.
* Apr 7 05:50:23 user.notice kernel: megaraid: no BIOS enabled.
* Apr 7 05:50:23 user.info kernel: scsi1 : LSI Logic MegaRAID 713^ 254 commands 16 targs 4 chans 7 luns
* Apr 7 05:50:23 user.info kernel: scsi2 : LSI Logic MegaRAID 713R 254 commands 16 targs 4 chans 7 luns
* Apr 7 05:50:23 user.info kernel: scsi3 : LSI Logic MegaRAID 713R 254 commands 16 targs 4 chans 7 luns
* Apr 7 05:50:23 user.notice kernel: scsi1: scanning scsi channel 0 for logical drives.
* Apr 7 05:50:23 user.warn kernel: Vendor: MegaRAID Model: LD 0 RAID5 1526G Rev: 713^
* Apr 7 05:50:23 user.warn kernel: Type: Direct-Access ANSI SCSI revision: 02
* Apr 7 05:50:23 user.notice kernel: scsi1: scanning scsi channel 1 for logical drives.
* Apr 7 05:50:23 user.notice kernel: scsi1: scanning scsi channel 2 for logical drives.
* Apr 7 05:50:23 user.notice kernel: scsi1: scanning scsi channel 3 for logical drives.
* Apr 7 05:50:23 user.notice kernel: scsi1: scanning scsi channel 4 [P0] for physical devices.
* Apr 7 05:50:23 user.notice kernel: scsi2: scanning scsi channel 0 for logical drives.
* Apr 7 05:50:23 user.warn kernel: Vendor: MegaRAID Model: LD 0 RAID5 610G Rev: 713R
* Apr 7 05:50:23 user.warn kernel: Type: Direct-Access ANSI SCSI revision: 02
* Apr 7 05:50:23 user.notice kernel: scsi2: scanning scsi channel 1 for logical drives.
* Apr 7 05:50:23 user.notice kernel: scsi2: scanning scsi channel 2 for logical drives.
* Apr 7 05:50:23 user.notice kernel: scsi2: scanning scsi channel 3 for logical drives.
* Apr 7 05:50:23 user.notice kernel: scsi2: scanning scsi channel 4 [P0] for physical devices.
* Apr 7 05:50:23 user.notice kernel: scsi3: scanning scsi channel 0 for logical drives.
* Apr 7 05:50:23 user.warn kernel: Vendor: MegaRAID Model: LD 0 RAID5 915G Rev: 713R
* Apr 7 05:50:23 user.warn kernel: Type: Direct-Access ANSI SCSI revision: 02
* Apr 7 05:50:23 user.notice kernel: scsi3: scanning scsi channel 1 for logical drives.
* Apr 7 05:50:23 user.notice kernel: scsi3: scanning scsi channel 2 for logical drives.
* Apr 7 05:50:23 user.notice kernel: scsi3: scanning scsi channel 3 for logical drives.
* Apr 7 05:50:23 user.notice kernel: scsi3: scanning scsi channel 4 [P0] for physical devices.
* Apr 7 05:50:23 user.warn kernel: GDT-HA: Storage RAID Controller Driver. Version: 3.04
* Apr 7 05:50:23 user.warn kernel: GDT-HA: Found 0 PCI Storage RAID Controllers
* Apr 7 05:50:23 user.warn kernel: 3ware Storage Controller device driver for Linux v1.02.00.037.
* Apr 7 05:50:23 user.warn kernel: 3w-xxxx: No cards found.
* Apr 7 05:50:23 user.debug kernel: libata version 1.20 loaded.
* Apr 7 05:50:23 user.warn kernel: Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
* Apr 7 05:50:23 user.warn kernel: Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0
* Apr 7 05:50:23 user.warn kernel: Attached scsi disk sdc at scsi3, channel 0, id 0, lun 0
* Apr 7 05:50:23 user.warn kernel: SCSI device sda: 3125667840 512-byte hdwr sectors (1600342 MB)
* Apr 7 05:50:23 user.info kernel: /dev/scsi/host1/bus0/target0/lun0: p1
* Apr 7 05:50:23 user.warn kernel: SCSI device sdb: 1250267136 512-byte hdwr sectors (640137 MB)
* Apr 7 05:50:23 user.info kernel: /dev/scsi/host2/bus0/target0/lun0: unknown partition table
* Apr 7 05:50:23 user.warn kernel: tors (960205 MB)
* Apr 7 05:50:23 user.info kernel: /dev/scsi/host3/bus0/target0/lun0: unknown partition table
* Apr 7 05:50:23 user.info kernel: raw1394: /dev/raw1394 device initialized
* Apr 7 05:50:23 user.info kernel: sbp2: $Rev: 1074 $ Ben Collins
* Apr 7 05:50:23 user.err kernel: ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
* Apr 7 05:50:23 user.info kernel: usb.c: registered new driver usbdevfs
* Apr 7 05:50:23 user.info kernel: usb.c: registered new driver hub
* Apr 7 05:50:23 user.info kernel: host/uhci.c: USB Universal Host Controller Interface driver v1.1
* Apr 7 05:50:23 user.info kernel: PCI: Found IRQ 12 for device 00:1f.2
* Apr 7 05:50:23 user.debug kernel: PCI: Setting latency timer of device 00:1f.2 to 64
* Apr 7 05:50:23 user.info kernel: host/uhci.c: USB UHCI at I/O 0xb400, IRQ 12
* Apr 7 05:50:23 user.info kernel: usb.c: new USB bus registered, assigned bus number 1
* Apr 7 05:50:23 user.info kernel: hub.c: USB hub found
* Apr 7 05:50:23 user.info kernel: hub.c: 2 ports detected
* Apr 7 05:50:23 user.info kernel: PCI: Found IRQ 5 for device 00:1f.4
* Apr 7 05:50:23 user.debug kernel: PCI: Setting latency timer of device 00:1f.4 to 64
* Apr 7 05:50:23 user.info kernel: host/uhci.c: USB UHCI at I/O 0xb000, IRQ 5
* Apr 7 05:50:23 user.info kernel: usb.c: new USB bus registered, assigned bus number 2
* Apr 7 05:50:23 user.info kernel: hub.c: USB hub found
* Apr 7 05:50:23 user.info kernel: hub.c: 2 ports detected
* Apr 7 05:50:23 user.info kernel: Initializing USB Mass Storage driver.
* Apr 7 05:50:23 user.info kernel: usb.c: registered new driver usb-storage
* Apr 7 05:50:23 user.info kernel: USB Mass Storage support registered.
* Apr 7 05:50:23 user.info kernel: NET4: Linux TCP/IP 1.0 for NET4.0
* Apr 7 05:50:23 user.info kernel: IP Protocols: ICMP, UDP, TCP
* Apr 7 05:50:23 user.info kernel: IP: routing cache hash table of 8192 buckets, 64Kbytes
* Apr 7 05:50:23 user.info kernel: TCP: Hash tables configured (established 262144 bind 65536)
* Apr 7 05:50:23 user.info kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
* Apr 7 05:50:23 user.notice kernel: RAMDISK: NASLite file system found at block 0
* Apr 7 05:50:23 user.warn kernel: <6>Freeing initrd memory: 1601k freed
* Apr 7 05:50:23 user.warn kernel: EXT2-fs warning: checktime reached, running e2fsck is recommended
* Apr 7 05:50:23 user.warn kernel: VFS: Mounted root (ext2 filesystem).
* Apr 7 05:50:23 user.info kernel: Mounted devfs on /dev
* Apr 7 05:50:23 user.info kernel: Freeing unused kernel memory: 536k freed
* Apr 7 05:50:23 user.info kernel: e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
* Apr 7 05:50:38 auth.info login[1569]: root login on `vc/1'

Please help.

Thanks.

MB

I assume that you have maintained the same order of the disks while moving them to the new box.

From what you say, I understand that disk no 4 is now dead because of the broken connector. In theory, the raid card should see a disk missing and mark the array as degraded but still operational.

From your log it seems that NASlite finds all 3 raid cards and reports one logical drive for each. This means that your other 2 raid cards also have a raid arrays. Is this correct?

You are not clear on how you have deduced that the array is gone.
Is it because it is not available through NASlite?
It could be that Naslite is doing a disk check before mounting it which could take hours.....

Have you tried the megaraid BIOS util during BIOS post to see what it says?

Correct, but I've also discovered that is not needed. The LSI MegaRaid is able to address the correct disks address in the chain even if they are connected to different ports.




Correct, I'm assuming nothing has happened to the data contained in the array.



Correct, the Nas Box has 3 LSI MegaRaid 150-X controllers:

First: 150-6, is the one with problematic array
Second and Third: 2x MegaRaid 150-4



When NasLite boots up shows the disk in a Fail State and does not mount it




I've run the check in NasLite, it gives a lot of errors (is too fast to read what it says) but completes in a couple of minutes.




Initially it said that there was a configuration mismatch, so I've copied the Array Config from the Disks to the Controller NVRam. The Controllers saws the array as operational.

Right now I'm checking the consistency of the array through the MegaRaid Util. In something more than 10h he has checked 25% of the array.

Any guess?

Thanks and Happy Easter.

MB

I was away or the easter weekend.

How did the consistency check go?

The consistency checks showed millions of errors.

I've tried to fix them with Knoppix without any luck. I've also bought a tool to recover from Ext2-3 and he was able to recover just some tens of file out of thousands.

I'm assuming everything is lost now and I'm a little bit disappointed by the support I've received from the forum.

Next steps will be:

1) Implement a backup policy on DVD-Rom
2) Reconsider the strength of NasLite in case of problems. The server I'm running now can manage Windows2K-2K3 as a file server, I need to decide if is worth to switch to that platform.

Just to recap, I did not understood what happened and why the problems have occurred. Assuming the hardware is fine, all the disks and Controllers was just 5 months old and Top of the Line for this kind of applications, I still need to understand if the system is reliable at least in terms of recovering the data.

I need to be honest since the problem, the server was running as a beauty, what worries me is the level of support I've received when something went wrong. basically was inexistent.

Thanks.

MB

Hello mbmobile,



I’m sure that folks here will agree that we have been more than diligent in supporting NASLite problems or issues that have been brought forth. NASLite is a software product, so our efforts are always directed towards improving the OS itself. It should not be our responsibility to coach people on how to properly configure and administer their hardware. That is the reason we maintain this forum.

Looking at your log above, how many things do you see sharing IRQ7?

Thanks Tony,

this is the kind of support I was looking three weeks ago.

MB

Based on the 3 RAID cards setup that you have, I assumed that you are experienced enough to figure it out. In hindsight, I probably should have said something. I think that you are trying to do too much with too few IRQs. Disable all unnecessary devices in the BIOS and make sure that the drive controllers and the NIC in particular have dedicated IRQs. That has been discussed to death on this very forum.

As far as the RAID goes, regardless of what the card capabilities may be, it is not only a good practice but is often necessary to mount the drives in the same order and port position as in the original installation. Further, it is good practice to bring the arrays up one by one in order to keep variables to a minimum. I’m not sure what path you took during the rebuild, but I am guessing you repopulated the new machine in full and let it go hopping all things come up as with the previous setup.

What I would have done is keep the other RAID cards out and concentrate on bringing the machine back to the original order prior to adding additional hardware.

All that aside, I’d like to point out that the problem you are experiencing has nothing to do with NASlite. If the hardware is properly set and configured, then NASLite will be more than capable of performing it’s duties. Perhaps your “what worries me is the level of support” comment should be directed towards LSI or your board manufacturer. That would have been more appropriate don’t you think?

Anyway, I’ll be happy to assist you in resolving your problem as time permits.

Thanks Tony,

The "recovery"has been performed with only one RAID Controller and with the disks in the same order as before.

The log I have sent was after the system was in place, at 5:00am, and I didn't have the will to remove everything.

The recovery tests was performed the days after with absolutely no luck.

As I said I'm "accepting" the fact all the data has been lost. The only thing I'd like to understand, in order to avoid or fix the problem in the future, is to understand what has been happened and why the FileSystem has been totally compromised after moving the disks. As I said the disks were in the same order as before.

When I've run the fsck from Knoppix millions of errors was displayed, millions. and my question is why.

I'm not considering me a Unix expert but I'm looking for someone else had the same experience, even outside NasLite.

Thanks.

MB