NASLite Network Attached Storage

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

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 4 posts ] 
Author Message
PostPosted: Wed Dec 14, 2005 2:26 pm 
Offline

Joined: Thu Sep 22, 2005 3:43 am
Posts: 3
My power went out last night - and so did my nas. I powered it back up this morning and now I only see 2 of my disks (out of 3). When I look from telnet the 3rd disk is there and is ready to be formatted. When I look from http - "Disk-3 is installed and can be configured for use with NASLite-SMBG."

Here is what it says on the disk-3 page:
Disk-3 Initialization Messages

1. Checking for Disk-3
2. Disk-3 is not available

Disk-3 Hardware

* Maxtor 6B160P0, ATA DISK drive
* attached ide-disk driver.
* host protected area => 1
* 320173056 sectors (163929 MB) w/8192KiB Cache, CHS=19929/255/63, UDMA(33)

NOTE: Disk-3 is installed and can be configured for use with NASLite-SMBG.



==========================

Here is my server system log:

Server System Log

* Dec 14 10:11:39 NAS syslog.info syslogd started: BusyBox v1.00-pre10 (2004.06.01-20:52+0000)
* Dec 14 10:11:39 NAS daemon.info init: Starting pid 288, console /dev/null: '/sbin/klogd'
* Dec 14 10:11:39 NAS syslog.notice klogd: klogd started: BusyBox v1.00-pre10 (2004.06.01-20:52+0000)
* Dec 14 10:11:39 NAS user.warn klogd: Linux version 2.4.26.NASLite (root@ServerElements.com) (gcc version 3.3.2) #23 Tue Oct 5 11:47:14 MDT 2004
* Dec 14 10:11:39 NAS user.info klogd: BIOS-provided physical RAM map:
* Dec 14 10:11:39 NAS user.warn klogd: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
* Dec 14 10:11:39 NAS user.warn klogd: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
* Dec 14 10:11:39 NAS user.warn klogd: BIOS-e820: 0000000000100000 - 000000000a000000 (usable)
* Dec 14 10:11:39 NAS user.warn klogd: BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
* Dec 14 10:11:39 NAS user.notice klogd: 160MB LOWMEM available.
* Dec 14 10:11:39 NAS user.warn klogd: On node 0 totalpages: 40960
* Dec 14 10:11:39 NAS user.warn klogd: zone(0): 4096 pages.
* Dec 14 10:11:39 NAS user.warn klogd: zone(1): 36864 pages.
* Dec 14 10:11:39 NAS user.warn klogd: zone(2): 0 pages.
* Dec 14 10:11:39 NAS user.warn klogd: Kernel command line:
* Dec 14 10:11:39 NAS user.info klogd: Initializing CPU#0
* Dec 14 10:11:39 NAS user.warn klogd: Detected 498.479 MHz processor.
* Dec 14 10:11:39 NAS user.warn klogd: Console: colour VGA+ 80x25
* Dec 14 10:11:39 NAS user.warn klogd: Calibrating delay loop... 992.87 BogoMIPS
* Dec 14 10:11:39 NAS user.info klogd: Memory: 159836k/163840k available (1085k kernel code, 3620k reserved, 230k data, 336k init, 0k highmem)
* Dec 14 10:11:39 NAS user.info klogd: Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
* Dec 14 10:11:39 NAS user.info klogd: Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
* Dec 14 10:11:39 NAS user.info klogd: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
* Dec 14 10:11:39 NAS user.info klogd: Buffer cache hash table entries: 8192 (order: 3, 32768 bytes)
* Dec 14 10:11:39 NAS user.warn klogd: Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
* Dec 14 10:11:39 NAS user.info klogd: CPU: L1 I cache: 16K, L1 D cache: 16K
* Dec 14 10:11:39 NAS user.info klogd: CPU: L2 cache: 512K
* Dec 14 10:11:39 NAS user.debug klogd: CPU: After generic, caps: 0383f9ff 00000000 00000000 00000000
* Dec 14 10:11:39 NAS user.debug klogd: CPU: Common caps: 0383f9ff 00000000 00000000 00000000
* Dec 14 10:11:39 NAS user.warn klogd: CPU: Intel Pentium III (Katmai) stepping 03
* Dec 14 10:11:39 NAS user.info klogd: Enabling fast FPU save and restore... done.
* Dec 14 10:11:39 NAS user.info klogd: Enabling unmasked SIMD FPU exception support... done.
* Dec 14 10:11:39 NAS user.info klogd: Checking 'hlt' instruction... OK.
* Dec 14 10:11:39 NAS user.info klogd: Checking for popad bug... OK.
* Dec 14 10:11:39 NAS user.warn klogd: POSIX conformance testing by UNIFIX
* Dec 14 10:11:39 NAS user.info klogd: PCI: PCI BIOS revision 2.10 entry at 0xfcaee, last bus=1
* Dec 14 10:11:39 NAS user.info klogd: PCI: Using configuration type 1
* Dec 14 10:11:39 NAS user.info klogd: PCI: Probing PCI hardware
* Dec 14 10:11:39 NAS user.warn klogd: PCI: Probing PCI hardware (bus 00)
* Dec 14 10:11:39 NAS user.info klogd: PCI: Using IRQ router PIIX/ICH [8086/7110] at 00:07.0
* Dec 14 10:11:39 NAS user.info klogd: Limiting direct PCI/PCI transfers.
* Dec 14 10:11:39 NAS user.info klogd: Linux NET4.0 for Linux 2.4
* Dec 14 10:11:39 NAS user.info klogd: Based upon Swansea University Computer Society NET3.039
* Dec 14 10:11:39 NAS user.warn klogd: Initializing RT netlink socket
* Dec 14 10:11:39 NAS user.warn klogd: Starting kswapd
* Dec 14 10:11:39 NAS user.info klogd: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
* Dec 14 10:11:39 NAS user.info klogd: devfs: boot_options: 0x1
* Dec 14 10:11:39 NAS user.warn klogd: pty: 256 Unix98 ptys configured
* Dec 14 10:11:39 NAS user.info klogd: Real Time Clock Driver v1.10f
* Dec 14 10:11:39 NAS user.info klogd: Floppy drive(s): fd0 is 1.44M
* Dec 14 10:11:39 NAS user.info klogd: FDC 0 is a National Semiconductor PC87306
* Dec 14 10:11:39 NAS user.warn klogd: RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
* Dec 14 10:11:39 NAS user.info klogd: loop: loaded (max 8 devices)
* Dec 14 10:11:39 NAS user.info klogd: Intel(R) PRO/1000 Network Driver - version 5.2.30.1-k1
* Dec 14 10:11:39 NAS user.info klogd: Copyright (c) 1999-2004 Intel Corporation.
* Dec 14 10:11:39 NAS user.info klogd: ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
* Dec 14 10:11:39 NAS user.warn klogd: sk98lin: No adapter found.
* Dec 14 10:11:39 NAS user.info klogd: r8169 Gigabit Ethernet driver 1.2 loaded
* Dec 14 10:11:39 NAS user.info klogd: PCI: Found IRQ 10 for device 00:0d.0
* Dec 14 10:11:39 NAS user.info klogd: PCI: Sharing IRQ 10 with 01:00.0
* Dec 14 10:11:39 NAS user.debug klogd: r8169: PCI device 00:0d.0: unknown chip version, assuming RTL-8169
* Dec 14 10:11:39 NAS user.debug klogd: r8169: PCI device 00:0d.0: TxConfig = 0x4000000
* Dec 14 10:11:39 NAS user.debug klogd: eth0: Identified chip type is 'RTL-8169'.
* Dec 14 10:11:39 NAS user.info klogd: eth0: RealTek RTL8169 Gigabit Ethernet at 0xca800400, 00:40:f4:cb:84:c3, IRQ 10
* Dec 14 10:11:39 NAS user.info klogd: eth0: Auto-negotiation Enabled.
* Dec 14 10:11:39 NAS user.info klogd: eth0: 1000Mbps Full-duplex operation.
* Dec 14 10:11:39 NAS user.info klogd: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
* Dec 14 10:11:39 NAS user.info klogd: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
* Dec 14 10:11:39 NAS user.info klogd: PIIX4: IDE controller at PCI slot 00:07.1
* Dec 14 10:11:39 NAS user.info klogd: PIIX4: chipset revision 1
* Dec 14 10:11:39 NAS user.info klogd: PIIX4: not 100% native mode: will probe irqs later
* Dec 14 10:11:39 NAS user.info klogd: ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
* Dec 14 10:11:39 NAS user.info klogd: ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio
* Dec 14 10:11:39 NAS user.warn klogd: hda: Maxtor 6Y120P0, ATA DISK drive
* Dec 14 10:11:39 NAS user.warn klogd: hdb: ST3160023A, ATA DISK drive
* Dec 14 10:11:39 NAS user.warn klogd: blk: queue c02c4420, I/O limit 4095Mb (mask 0xffffffff)
* Dec 14 10:11:39 NAS user.warn klogd: blk: queue c02c455c, I/O limit 4095Mb (mask 0xffffffff)
* Dec 14 10:11:39 NAS user.warn klogd: hdc: Maxtor 6B160P0, ATA DISK drive
* Dec 14 10:11:39 NAS user.warn klogd: blk: queue c02c4874, I/O limit 4095Mb (mask 0xffffffff)
* Dec 14 10:11:39 NAS user.warn klogd: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
* Dec 14 10:11:39 NAS user.warn klogd: ide1 at 0x170-0x177,0x376 on irq 15
* Dec 14 10:11:39 NAS user.warn klogd: hda: attached ide-disk driver.
* Dec 14 10:11:39 NAS user.warn klogd: hda: host protected area => 1
* Dec 14 10:11:39 NAS user.info klogd: hda: 240121728 sectors (122942 MB) w/7936KiB Cache, CHS=14946/255/63, UDMA(33)
* Dec 14 10:11:39 NAS user.warn klogd: hdb: attached ide-disk driver.
* Dec 14 10:11:39 NAS user.warn klogd: hdb: host protected area => 1
* Dec 14 10:11:39 NAS user.info klogd: hdb: 312581808 sectors (160042 MB) w/8192KiB Cache, CHS=19457/255/63, UDMA(33)
* Dec 14 10:11:39 NAS user.warn klogd: hdc: attached ide-disk driver.
* Dec 14 10:11:39 NAS user.warn klogd: 1
* Dec 14 10:11:39 NAS user.info klogd: hdc: 320173056 sectors (163929 MB) w/8192KiB Cache, CHS=19929/255/63, UDMA(33)
* Dec 14 10:11:39 NAS user.info klogd: Partition check:
* Dec 14 10:11:39 NAS user.info klogd: /dev/ide/host0/bus0/target0/lun0: p1
* Dec 14 10:11:39 NAS user.info klogd: /dev/ide/host0/bus0/target1/lun0: p1
* Dec 14 10:11:39 NAS user.info klogd: /dev/ide/host0/bus1/target0/lun0: unknown partition table
* Dec 14 10:11:39 NAS user.info klogd: NET4: Linux TCP/IP 1.0 for NET4.0
* Dec 14 10:11:39 NAS user.info klogd: IP Protocols: ICMP, UDP, TCP
* Dec 14 10:11:39 NAS user.info klogd: IP: routing cache hash table of 1024 buckets, 8Kbytes
* Dec 14 10:11:39 NAS user.info klogd: TCP: Hash tables configured (established 16384 bind 32768)
* Dec 14 10:11:39 NAS user.info klogd: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
* Dec 14 10:11:39 NAS user.notice klogd: RAMDISK: Compressed image found at block 798
* Dec 14 10:11:39 NAS user.warn klogd: EXT2-fs warning: checktime reached, running e2fsck is recommended
* Dec 14 10:11:39 NAS user.warn klogd: VFS: Mounted root (ext2 filesystem).
* Dec 14 10:11:39 NAS user.info klogd: Mounted devfs on /dev
* Dec 14 10:11:39 NAS user.info klogd: Freeing unused kernel memory: 336k freed

Any help here would be greatly appreciated.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Dec 14, 2005 3:29 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
On rare occasion, an IDE disk may be damaged in the event of a power failure. This is especially true if the power outage is not clean where power just goes out, but rather long with a brownout period during which the machine can get damaged. In your case, the disk appears to be ok except, according to the log you provided, the partition table appears to be damaged.

You may be able to recover the content in full by running fdisk. Do not make any changes to the partition table and just enter w to write the tables back to the disk.

Do that in Linux and not windows or DOS. Any live CD should do, Knoppix probably being the most popular.

If this does not correct the partition table flaw, then there is a possibility of data loss. Data recovery tools will be necessary for extraction.


Last edited by Tony on Wed Dec 14, 2005 3:33 pm, edited 1 time in total.

Top
 Profile  
 
 Post subject:
PostPosted: Wed Dec 14, 2005 3:31 pm 
Offline

Joined: Thu Sep 22, 2005 3:43 am
Posts: 3
Thank you Tony.

Would you mind giving me the exact command - as I am not very familiar with Linux.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Dec 14, 2005 3:39 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
Disk-3 is your secondary master. At the shell prompt just run "fdisk /dev/hdc". Use the "w" option to write the partition table back to the drive.

You can also use "cfdisk /dev/hdc" which will provide you with a full-screen curses display, but fdisk is probably safer.

If you have questions about fdisk usege, "man fdisk" will give you a good start.

hope that helps.


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

All times are UTC - 5 hours [ DST ]


Who is online

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