NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Sun Nov 28, 2021 9:42 am

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 5 posts ] 
Author Message
PostPosted: Mon Mar 13, 2006 10:49 am 
Offline

Joined: Sun Dec 18, 2005 5:28 pm
Posts: 2
Every time I have a power failure, I loose the hard drives on one of my NASLite servers.

I am running two servers. Only one of them exhibits these symptoms.

When the server powers back up, it wont mount the drives and I have to re-configure the which means I loose all of the data on thoe drives. It doesn't seem to matter whether I am actively reading or writing data to or from the drives.

Is this to be expected? Any thoughts on what is going on? I have pasted some log files below if that will help. The server has 3 drives. Power failure on Saturday night resulted in loosing drives 1, 2 and drive 4 came back up find. I reconfigured drive 2 and it came back but all data was gone as expected. I have not reconfigured Drive-1 yet.

Disk-1 Initialization Messages

Checking for Disk-1
Found Disk-1 partition
Attempting to fix Disk-1 filesystem
Disk-1 filesystem is not mountable


--------------------------------------------------------------------------------
Disk-1 Hardware
WDC WD2500LB-55EDA0, ATA DISK drive
attached ide-disk driver.
host protected area => 1
488397168 sectors (250059 MB) w/2048KiB Cache, CHS=30401/255/63

NOTE: Disk-1 is installed and can be configured for use with NASLite-SMB.


_______________________________________________

[2006/03/13 07:28:58, 1] smbd/server.c:main(641)
smbd version 2.0.10 started.
Copyright Andrew Tridgell 1992-1998
[2006/03/13 07:29:39, 1] smbd/service.c:make_connection(550)
siebel-laptop1 (192.168.1.108) connect to service Disk-2 as user NAS-User (uid=98, gid=98) (pid 324)
[2006/03/13 07:29:41, 0] smbd/nttrans.c:call_nt_transact_ioctl(2516)
call_nt_transact_ioctl: Currently not implemented.

_______________________________________________________

Mar 13 07:29:02 Server03 syslog.info syslogd started: BusyBox v1.00-pre10 (2004.06.01-20:52+0000)
Mar 13 07:29:02 Server03 daemon.info init: Starting pid 294, console /dev/null: '/sbin/klogd'
Mar 13 07:29:02 Server03 syslog.notice klogd: klogd started: BusyBox v1.00-pre10 (2004.06.01-20:52+0000)
Mar 13 07:29:02 Server03 user.warn klogd: Linux version 2.4.26.NASLite (root@(none)) (gcc version 3.3.2) #10 Mon Jun 14 14:07:53 MDT 2004
Mar 13 07:29:02 Server03 user.info klogd: BIOS-provided physical RAM map:
Mar 13 07:29:02 Server03 user.warn klogd: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
Mar 13 07:29:02 Server03 user.warn klogd: BIOS-e820: 0000000000100000 - 0000000002000000 (usable)
Mar 13 07:29:02 Server03 user.warn klogd: BIOS-e820: 00000000fec00000 - 00000000fec00800 (reserved)
Mar 13 07:29:02 Server03 user.warn klogd: BIOS-e820: 00000000fee00000 - 00000000fee00400 (reserved)
Mar 13 07:29:02 Server03 user.warn klogd: BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved)
Mar 13 07:29:02 Server03 user.notice klogd: 32MB LOWMEM available.
Mar 13 07:29:02 Server03 user.warn klogd: On node 0 totalpages: 8192
Mar 13 07:29:02 Server03 user.warn klogd: zone(0): 4096 pages.
Mar 13 07:29:02 Server03 user.warn klogd: zone(1): 4096 pages.
Mar 13 07:29:02 Server03 user.warn klogd: zone(2): 0 pages.
Mar 13 07:29:02 Server03 user.info klogd: DMI not present.
Mar 13 07:29:02 Server03 user.warn klogd: Kernel command line:
Mar 13 07:29:02 Server03 user.info klogd: Initializing CPU#0
Mar 13 07:29:02 Server03 user.warn klogd: Detected 166.194 MHz processor.
Mar 13 07:29:02 Server03 user.warn klogd: Console: mono EGA+ 80x25
Mar 13 07:29:02 Server03 user.warn klogd: Calibrating delay loop... 331.77 BogoMIPS
Mar 13 07:29:02 Server03 user.info klogd: Memory: 30272k/32768k available (1044k kernel code, 2112k reserved, 281k data, 232k init, 0k highmem)
Mar 13 07:29:02 Server03 user.info klogd: Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
Mar 13 07:29:02 Server03 user.info klogd: Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
Mar 13 07:29:02 Server03 user.info klogd: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Mar 13 07:29:02 Server03 user.info klogd: Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Mar 13 07:29:02 Server03 user.warn klogd: Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
Mar 13 07:29:02 Server03 user.notice klogd: Intel Pentium with F0 0F bug - workaround enabled.
Mar 13 07:29:02 Server03 user.debug klogd: CPU: After generic, caps: 008001bf 00000000 00000000 00000000
Mar 13 07:29:02 Server03 user.debug klogd: CPU: Common caps: 008001bf 00000000 00000000 00000000
Mar 13 07:29:02 Server03 user.warn klogd: CPU: Intel Pentium MMX stepping 03
Mar 13 07:29:02 Server03 user.info klogd: Checking 'hlt' instruction... OK.
Mar 13 07:29:02 Server03 user.info klogd: Checking for popad bug... OK.
Mar 13 07:29:02 Server03 user.warn klogd: POSIX conformance testing by UNIFIX
Mar 13 07:29:02 Server03 user.info klogd: PCI: PCI BIOS revision 2.10 entry at 0xfce2e, last bus=1
Mar 13 07:29:02 Server03 user.info klogd: PCI: Using configuration type 1
Mar 13 07:29:02 Server03 user.info klogd: PCI: Probing PCI hardware
Mar 13 07:29:02 Server03 user.warn klogd: PCI: Probing PCI hardware (bus 00)
Mar 13 07:29:02 Server03 user.info klogd: Limiting direct PCI/PCI transfers.
Mar 13 07:29:02 Server03 user.info klogd: Activating ISA DMA hang workarounds.
Mar 13 07:29:02 Server03 user.info klogd: Linux NET4.0 for Linux 2.4
Mar 13 07:29:02 Server03 user.info klogd: Based upon Swansea University Computer Society NET3.039
Mar 13 07:29:02 Server03 user.warn klogd: Initializing RT netlink socket
Mar 13 07:29:02 Server03 user.warn klogd: Starting kswapd
Mar 13 07:29:02 Server03 user.info klogd: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
Mar 13 07:29:02 Server03 user.info klogd: devfs: boot_options: 0x1
Mar 13 07:29:02 Server03 user.warn klogd: pty: 256 Unix98 ptys configured
Mar 13 07:29:02 Server03 user.info klogd: Real Time Clock Driver v1.10f
Mar 13 07:29:02 Server03 user.warn klogd: keyboard: Timeout - AT keyboard not present?(ed)
Mar 13 07:29:02 Server03 user.warn klogd: keyboard: Timeout - AT keyboard not present?(f4)
Mar 13 07:29:02 Server03 user.info klogd: Floppy drive(s): fd0 is 1.44M
Mar 13 07:29:02 Server03 user.info klogd: FDC 0 is a National Semiconductor PC87306
Mar 13 07:29:02 Server03 user.warn klogd: RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Mar 13 07:29:02 Server03 user.info klogd: loop: loaded (max 8 devices)
Mar 13 07:29:02 Server03 user.info klogd: 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
Mar 13 07:29:02 Server03 user.warn klogd: FW Version=$Version$
Mar 13 07:29:02 Server03 user.info klogd: pcnet32.c:v1.28 02.20.2004 tsbogend@alpha.franken.de
Mar 13 07:29:02 Server03 user.info klogd: ThunderLAN driver v1.15
Mar 13 07:29:02 Server03 user.info klogd: TLAN: 0 devices installed, PCI: 0 EISA: 0
Mar 13 07:29:02 Server03 user.info klogd: dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
Mar 13 07:29:02 Server03 user.notice klogd: Intel(R) PRO/100 Network Driver - version 2.3.38-k1
Mar 13 07:29:02 Server03 user.notice klogd: Copyright (c) 2004 Intel Corporation
Mar 13 07:29:02 Server03 user.notice klogd:
Mar 13 07:29:02 Server03 user.debug klogd: e100: selftest OK.
Mar 13 07:29:02 Server03 user.notice klogd: e100: eth0: Intel(R) PRO/100 Network Connection
Mar 13 07:29:02 Server03 user.notice klogd: Hardware receive checksums enabled
Mar 13 07:29:02 Server03 user.notice klogd: cpu cycle saver enabled
Mar 13 07:29:02 Server03 user.notice klogd:
Mar 13 07:29:02 Server03 user.info klogd: forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.25.
Mar 13 07:29:02 Server03 user.info klogd: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
Mar 13 07:29:02 Server03 user.info klogd: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Mar 13 07:29:02 Server03 user.warn klogd: hda: WDC WD2500LB-55EDA0, ATA DISK drive
Mar 13 07:29:02 Server03 user.warn klogd: hdb: WDC WD2500LB-55EDA0, ATA DISK drive
Mar 13 07:29:02 Server03 user.warn klogd: hdc: NEC CD-ROM DRIVE:282, ATAPI CD/DVD-ROM drive
Mar 13 07:29:02 Server03 user.warn klogd: hdd: WDC WD400BB-00AUA1, ATA DISK drive
Mar 13 07:29:02 Server03 user.warn klogd: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Mar 13 07:29:02 Server03 user.warn klogd: ide1 at 0x170-0x177,0x376 on irq 15
Mar 13 07:29:02 Server03 user.warn klogd: hda: attached ide-disk driver.
Mar 13 07:29:02 Server03 user.warn klogd: hda: host protected area => 1
Mar 13 07:29:02 Server03 user.info klogd: hda: 488397168 sectors (250059 MB) w/2048KiB Cache, CHS=30401/255/63
Mar 13 07:29:02 Server03 user.warn klogd: hdb: attached ide-disk driver.
Mar 13 07:29:02 Server03 user.warn klogd: hdb: host protected area => 1
Mar 13 07:29:02 Server03 user.info klogd: hdb: 488397168 sectors (250059 MB) w/2048KiB Cache, CHS=30401/255/63
Mar 13 07:29:02 Server03 user.warn klogd: hdd: attached ide-disk driver.
Mar 13 07:29:02 Server03 user.warn klogd: hdd: host protected area => 1
Mar 13 07:29:02 Server03 user.info klogd: hdd: 78165360 sectors (40021 MB) w/2048KiB Cache, CHS=77545/16/63
Mar 13 07:29:02 Server03 user.info klogd: Partition check:
Mar 13 07:29:02 Server03 user.info klogd: /dev/ide/host0/bus0/target0/lun0: p1
Mar 13 07:29:02 Server03 user.info klogd: /dev/ide/host0/bus0/target1/lun0: p1
Mar 13 07:29:02 Server03 user.info klogd: /dev/ide/host1/bus0/target1/lun0: p1
Mar 13 07:29:02 Server03 user.info klogd: NET4: Linux TCP/IP 1.0 for NET4.0
Mar 13 07:29:02 Server03 user.info klogd: IP Protocols: ICMP, UDP, TCP
Mar 13 07:29:02 Server03 user.info klogd: IP: routing cache hash table of 512 buckets, 4Kbytes
Mar 13 07:29:02 Server03 user.info klogd: ind 4096)
Mar 13 07:29:02 Server03 user.info klogd: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Mar 13 07:29:02 Server03 user.notice klogd: RAMDISK: Compressed image found at block 803
Mar 13 07:29:02 Server03 user.warn klogd: EXT2-fs warning: checktime reached, running e2fsck is recommended
Mar 13 07:29:02 Server03 user.warn klogd: VFS: Mounted root (ext2 filesystem).
Mar 13 07:29:02 Server03 user.info klogd: Mounted devfs on /dev
Mar 13 07:29:02 Server03 user.info klogd: Freeing unused kernel memory: 232k freed
Mar 13 07:29:02 Server03 user.err klogd: e100: eth0 NIC Link is Up 100 Mbps Full duplex
Mar 13 07:29:02 Server03 user.notice klogd: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Mar 13 07:29:02 Server03 user.warn klogd: VM: killing process e2fsck
Mar 13 07:29:02 Server03 user.notice klogd: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Mar 13 07:29:02 Server03 user.warn klogd: VM: killing process e2fsck
Mar 13 07:29:29 Server03 auth.info login[295]: root login on `pts/0'
____________________________________________________


Top
 Profile  
 
 Post subject:
PostPosted: Mon Mar 13, 2006 6:18 pm 
Offline

Joined: Wed Jan 04, 2006 2:18 pm
Posts: 172
Location: North Carolina, USA
If this has happened multiple times you might consider investing in a UPS.

What happens is, as the power goes down it glitches the drive write heads which makes the drive write to some random sector and mess up the file system.

The normal shutdown will tell the drives to park the heads first so when the power goes off it isn't over a data area of the disk and no damage occurs. Some drive models will move the heads to the park position if no activity takes place for a while.

The other thing to try is just let NASLite run for an hour or so and see if the drives come back on line. The messages you show says it noticed the file system was messed up and it will try to fix it, but it can take a little while for a big disk. If it can't fix it you would get a message saying e2fsck failed. In that case you could try installing rlinux or some other recovery program on a windows machine to get most of your data back.

Did I mention getting a UPS :D


Top
 Profile  
 
 Post subject:
PostPosted: Mon Mar 13, 2006 7:48 pm 
Offline

Joined: Sun Dec 18, 2005 5:28 pm
Posts: 2
How long should I wait? They are 250G drives and a configure with the C option takes about 36-48 hours. Should I wait that long? or even longer? Is there any way to tell what the status is or what the progress is?

I was hoping the error logs would tell you there was a hardware issue. The strange thing is, one system never has a problem and the other system ALWAYS has a problem. The system that always has a problem is older and slower (PII 133 vs a 266). It also has much less memory (128M vs 512M).

I have been working on the electical system in the house over the past month and have accidently turned the power off 8-10 times. I have also just powered down the servers to see what would happen.

I would rather not invest in a UPS but I guess if it will save the data....


Top
 Profile  
 
 Post subject:
PostPosted: Thu Mar 23, 2006 1:05 pm 
Offline

Joined: Sat May 14, 2005 12:20 am
Posts: 52
I am running a small tower with 4x250G WD drives and had a lightning storm here and thought the same thing... almost mesed myself but I just walked away for a few hours and came back and it resurrected itself.

You have to remember its checking every little detail and doing that on a large scale.... well it just takes time. Its a bit of a hinderance but I would rather it be right than a bit faster and the data be corrupted.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Mar 24, 2006 4:17 am 
Offline

Joined: Fri Apr 29, 2005 8:01 am
Posts: 170
Location: Staffordshire UK
bmitchin wrote:
How long should I wait? They are 250G drives and a configure with the C option takes about 36-48 hours. Should I wait that long? or even longer? Is there any way to tell what the status is or what the progress is?

I was hoping the error logs would tell you there was a hardware issue. The strange thing is, one system never has a problem and the other system ALWAYS has a problem. The system that always has a problem is older and slower (PII 133 vs a 266). It also has much less memory (128M vs 512M).

I have been working on the electical system in the house over the past month and have accidently turned the power off 8-10 times. I have also just powered down the servers to see what would happen.

I would rather not invest in a UPS but I guess if it will save the data....


Something is wrong if its taking 48 hours to do the disk check, my old amd 300mhz NAS only took 3-4 hours to check a 400GB drive.
You can get a cheap easy to use basic UPS for about £30 so whats that about $50. I bought one from Maplins and if I wanted to I could run two NAS's off it. It's got to be worth the £30 just so you don't have to wait 2 days for your data :lol:

There is a script posted here http://www.serverelements.com/phpBB2/vi ... 6904e34d31
(well done Georg :wink: ) that would allow a Windows pc to run the script shutting down your NAS before it shuts itself down with the UPS software.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

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