NASLite Network Attached Storage

I have been running NASLite-M2 for about a month now with no problems until today. I shutdown my server when a storm was approaching to prevent any problems. Once the storm passed, I rebooted and drive-1 failed during the start-up. after trying again with the same results, I booted the machine with a puppy linux live cd and the drive worked in all respects with no loss of data. NASLite still cannot mount the drive. I am running the sever from IDE drive-0 and using a 1.5TB SATA on a PCI controller card for the storage. Any suggestions?

Here is the partial syslog:

Jun 19 03:29:52 [1] libata version 1.20 loaded.
Jun 19 03:29:52 [1] PCI(00:0f.0): version 0.9
Jun 19 03:29:52 [2] ata1: SATA max UDMA/100 cmd 0xC8804C80 ctl 0xC8804C8A bmdma 0xC8804C00 irq 10
Jun 19 03:29:52 [2] ata2: SATA max UDMA/100 cmd 0xC8804CC0 ctl 0xC8804CCA bmdma 0xC8804C08 irq 10
Jun 19 03:29:52 [2] ata3: SATA max UDMA/100 cmd 0xC8804E80 ctl 0xC8804E8A bmdma 0xC8804E00 irq 10
Jun 19 03:29:52 [2] ata4: SATA max UDMA/100 cmd 0xC8804EC0 ctl 0xC8804ECA bmdma 0xC8804E08 irq 10
Jun 19 03:29:52 [1] ata1: dev 0 cfg 49:2f00 82:346b 83:7501 84:4123 85:3469 86:b401 87:4123 88:407f
Jun 19 03:29:52 [2] ata1: dev 0 ATA-8, max UDMA/133, 2930277168 sectors: LBA48
Jun 19 03:29:52 [2] ata1: dev 0 configured for UDMA/100
Jun 19 03:29:52 [2] ata2: no device found (phy stat 00000000)
Jun 19 03:29:52 [2] ata3: no device found (phy stat 00000000)
Jun 19 03:29:52 [2] ata4: no device found (phy stat 00000000)
Jun 19 03:29:52 [2] scsi2 : sata_sil
Jun 19 03:29:52 [2] scsi3 : sata_sil
Jun 19 03:29:52 [2] scsi4 : sata_sil
Jun 19 03:29:52 [2] scsi5 : sata_sil
Jun 19 03:29:52 [4] Vendor: ATA Model: ST31500341AS Rev: SD17
Jun 19 03:29:52 [4] Type: Direct-Access ANSI SCSI revision: 05
Jun 19 03:29:52 [4] Attached scsi disk sda at scsi2, channel 0, id 0, lun 0
Jun 19 03:29:52 [4] SCSI device sda: 2930277168 512-byte hdwr sectors (1500302 MB)
Jun 19 03:29:52 [2] /dev/scsi/host2/bus0/target0/lun0: p1
Jun 19 03:29:52 [2] raw1394: /dev/raw1394 device initialized
Jun 19 03:29:52 [2] sbp2: $Rev: 1074 $ Ben Collins
Jun 19 03:29:52 [5] ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
Jun 19 03:29:52 [2] usb.c: registered new driver usbdevfs
Jun 19 03:29:52 [2] usb.c: registered new driver hub
Jun 19 03:29:52 [2] host/uhci.c: USB Universal Host Controller Interface driver v1.1
Jun 19 03:29:52 [2] host/uhci.c: USB UHCI at I/O 0xef40, IRQ 9
Jun 19 03:29:52 [2] usb.c: new USB bus registered, assigned bus number 1
Jun 19 03:29:52 [2] hub.c: USB hub found
Jun 19 03:29:52 [2] hub.c: 2 ports detected
Jun 19 03:29:52 [2] usb.c: registered new driver usbkbd
Jun 19 03:29:52 [2] usbkbd.c: :USB HID Boot Protocol keyboard driver
Jun 19 03:29:52 [2] Initializing USB Mass Storage driver.
Jun 19 03:29:52 [2] usb.c: registered new driver usb-storage
Jun 19 03:29:52 [2] USB Mass Storage support registered.
Jun 19 03:29:52 [2] NET4: Linux TCP/IP 1.0 for NET4.0
Jun 19 03:29:52 [2] IP Protocols: ICMP, UDP, TCP
Jun 19 03:29:52 [2] IP: routing cache hash table of 1024 buckets, 8Kbytes
Jun 19 03:29:52 [2] TCP: Hash tables configured (established 8192 bind 16384)
Jun 19 03:29:52 [2] NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Jun 19 03:29:52 [3] RAMDISK: NASLite file system found at block 0
Jun 19 03:29:52 [4] .<6>hub.c: new USB device 00:07.2-2, assigned address 2
Jun 19 03:29:52 [4] .<6>hub.c: USB hub found
Jun 19 03:29:52 [4] .<6>hub.c: 4 ports detected
Jun 19 03:29:52 [4] <6>hub.c: new USB device 00:07.2-2.1, assigned address 3
Jun 19 03:29:52 [4] <4>usb.c: USB device 3 (vend/prod 0x46d/0xc00e) is not claimed by any active driver.
Jun 19 03:29:52 [4] <6>hub.c: new USB device 00:07.2-2.2, assigned address 4
Jun 19 03:29:52 [4] <6>input0: Dell Dell USB Keyboard on usb1:4.0
Jun 19 03:29:52 [4] .<6>Freeing initrd memory: 4137k freed
Jun 19 03:29:52 [4] VFS: Mounted root (ext2 filesystem).
Jun 19 03:29:52 [2] Mounted devfs on /dev
Jun 19 03:29:52 [2] Freeing unused kernel memory: 560k freed
Jun 19 03:29:52 [4] hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Jun 19 03:29:52 [4] hda: drive_cmd: error=0x04 { DriveStatusError }
Jun 19 03:29:52 [3] __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Jun 19 03:29:52 [4] VM: killing process e2fsck

Likely the drive was unmounted in some way that ended with the OS marking the drive as inconsistent. Boot NL like normal and log into the terminal and select the drive to be checked and let it run. The drive should come up though this may take a while.

Mike

How much ram is in the machine? Looks like the e2fsck is dying, this would happen if there's insufficient ram to fsck the a large hard disk.

Thank you both for your replies,

The system would not complete the check via the storage menu until I increased the RAM; reporting "KILLED"
I only had 128Mb RAM, so I increased to 1GB. The start took quite a long time at the Disk-1 check but, once it finished, the drive is back on the system.


Thanks again,

Diverk

Ya, with big drives you'll need more than 128Megs to do the fsck.

Your back in business, thanks.

Wow that's good that Ralph know what it was by this data:



traslashin = not Enough ram to mount HDD.

-Raymond Day