NASLite Network Attached Storage

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

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 12 posts ] 
Author Message
PostPosted: Thu Dec 15, 2005 7:24 pm 
Offline

Joined: Wed Nov 30, 2005 10:55 pm
Posts: 7
Hi,

I'm running NAS from floppy in SMB configuration. I have (2) 40Gb hard disks and everything has been running fine. Today I had to shutdown the box and I shut it down properly (logged in and issues shutdown). Now when I've booted - it doesn't boot all the way up.

I see some errors regarding partition and during boot it gets hung at flow control regarding ethernet connection (which should work fine). Does anyone have any suggestions how to:

1. Fully boot up?
2. check the hard disks?

While I can't telnet in - I can get to webserver and only see info directory.

El


Top
 Profile  
 
 Post subject:
PostPosted: Thu Dec 15, 2005 7:43 pm 
Offline

Joined: Wed Nov 30, 2005 10:55 pm
Posts: 7
Hi Again,

Update - it finally booted all the way up. I looked through the syslog (from web server) and saw the following:

# Dec 15 13:23:59 dlcat-pc1912 user.info klogd: hdd:end_request: I/O error, dev 16:40 (hdd), sector 0
# Dec 15 13:23:59 dlcat-pc1912 user.warn klogd: end_request: I/O error, dev 16:40 (hdd), sector 2
# Dec 15 13:23:59 dlcat-pc1912 user.warn klogd: end_request: I/O error, dev 16:40 (hdd), sector 4
# Dec 15 13:23:59 dlcat-pc1912 user.warn klogd: end_request: I/O error, dev 16:40 (hdd), sector 6
# Dec 15 13:23:59 dlcat-pc1912 user.warn klogd: end_request: I/O error, dev 16:40 (hdd), sector 0
# Dec 15 13:23:59 dlcat-pc1912 user.warn klogd: end_request: I/O error, dev 16:40 (hdd), sector 2
# Dec 15 13:23:59 dlcat-pc1912 user.warn klogd: end_request: I/O error, dev 16:40 (hdd), sector 4
# Dec 15 13:23:59 dlcat-pc1912 user.warn klogd: end_request: I/O error, dev 16:40 (hdd), sector 6
# Dec 15 13:23:59 dlcat-pc1912 user.warn klogd: unable to read partition table
# Dec 15 13:23:59 dlcat-pc1912 user.info klogd: NET4: Linux TCP/IP 1.0 for NET4.0
# Dec 15 13:23:59 dlcat-pc1912 user.info klogd: IP Protocols: ICMP, UDP, TCP
# Dec 15 13:23:59 dlcat-pc1912 user.info klogd: IP: routing cache hash table of 8192 buckets, 64Kbytes
# Dec 15 13:23:59 dlcat-pc1912 user.info klogd: TCP: Hash tables configured (established 262144 bind 65536)
# Dec 15 13:23:59 dlcat-pc1912 user.info klogd: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
# Dec 15 13:23:59 dlcat-pc1912 user.notice klogd: RAMDISK: Compressed image found at block 803
# Dec 15 13:23:59 dlcat-pc1912 user.warn klogd: EXT2-fs warning: checktime reached, running e2fsck is recommended
# Dec 15 13:23:59 dlcat-pc1912 user.warn klogd: VFS: Mounted root (ext2 filesystem).
# Dec 15 13:23:59 dlcat-pc1912 user.info klogd: Mounted devfs on /dev
# Dec 15 13:23:59 dlcat-pc1912 user.info klogd: Freeing unused kernel memory: 232k freed
# Dec 15 13:23:59 dlcat-pc1912 user.info klogd: b44: eth0: Link is down.
# Dec 15 13:23:59 dlcat-pc1912 user.info klogd: b44: eth0: Link is up at 100 Mbps, full duplex.
# Dec 15 13:23:59 dlcat-pc1912 user.info klogd: b44: eth0: Flow control is off for TX and off for RX.
# Dec 15 13:30:27 dlcat-pc1912 auth.info login[596]: root login on `pts/0'


I'm a newbie to nas - can someone advise (or refer me to doc or url) that will show me how to run e2fsck.

The only way I see of doing this is going through the menu system (when logged in):
Option 4 (configure disks)
Choosing 1 C (for checking disk 1)

If I do the above - will that wipe the disks?
Thanks,

El


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 16, 2005 5:40 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
The above looks like a bad drive. I bet it's a pretty old and tired one that you had on the shelf somewhere ;-)

You can reformat it as you describe, but it will probably not last long. I'd be careful when committing data to it. Make sure you have a good backup strategy.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Dec 16, 2005 7:48 pm 
Offline

Joined: Wed Nov 30, 2005 10:55 pm
Posts: 7
Hi Tony,

Thank you for your help.

Can you help a newbie understand a couple of things:

1. How can you tell it's a bad drive when compared to an improper shutdown? (so what do you look at log-wise)

2. How do I run e2fsck? There's no command line option from menu system of the NAS.

El


Top
 Profile  
 
 Post subject: running e2fsck
PostPosted: Sat Dec 31, 2005 3:24 pm 
Offline

Joined: Thu Dec 29, 2005 9:49 pm
Posts: 14
Location: Brockville, ON
You'll need to download some type of Linux utility floppy or CD and run e2fsck from the command line.

e.g. http://www.sysresccd.org/

Then: e2fsck -v /dev/hda1

to run e2fsck on /dev/hda1 in verbose mode.

Rick D.


Top
 Profile  
 
 Post subject: Re: running e2fsck
PostPosted: Sun Jan 01, 2006 2:38 am 
Offline

Joined: Wed Nov 30, 2005 10:55 pm
Posts: 7
Hi Rick,

rdeschene wrote:
You'll need to download some type of Linux utility floppy or CD and run e2fsck from the command line.

e.g. http://www.sysresccd.org/

Then: e2fsck -v /dev/hda1

to run e2fsck on /dev/hda1 in verbose mode.

Rick D.


Thanks so much for your help. I was starting to give up on this thread. Being told that the disk is bad doesn't help me learn to diagnose NAS errors (per other post).

El


Top
 Profile  
 
 Post subject:
PostPosted: Sun Jan 01, 2006 11:01 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
Quote:
# Dec 15 13:23:59 dlcat-pc1912 user.warn klogd: end_request: I/O error, dev 16:40 (hdd), sector 2
# Dec 15 13:23:59 dlcat-pc1912 user.warn klogd: end_request: I/O error, dev 16:40 (hdd), sector 4
# Dec 15 13:23:59 dlcat-pc1912 user.warn klogd: end_request: I/O error, dev 16:40 (hdd), sector 6
# Dec 15 13:23:59 dlcat-pc1912 user.warn klogd: end_request: I/O error, dev 16:40 (hdd), sector 0
# Dec 15 13:23:59 dlcat-pc1912 user.warn klogd: end_request: I/O error, dev 16:40 (hdd), sector 2
# Dec 15 13:23:59 dlcat-pc1912 user.warn klogd: end_request: I/O error, dev 16:40 (hdd), sector 4
# Dec 15 13:23:59 dlcat-pc1912 user.warn klogd: end_request: I/O error, dev 16:40 (hdd), sector 6


I/O problems are hardware or driver related, so if other disks work fine on that controller/cable, then the only problem can be the disk causing the I/O error.


Top
 Profile  
 
 Post subject:
PostPosted: Mon Jan 02, 2006 4:03 am 
Offline

Joined: Wed Nov 30, 2005 10:55 pm
Posts: 7
Hello Tony,

Tony wrote:
Quote:
# Dec 15 13:23:59 dlcat-pc1912 user.warn klogd: end_request: I/O error, dev 16:40 (hdd), sector 2
# Dec 15 13:23:59 dlcat-pc1912 user.warn klogd: end_request: I/O error, dev 16:40 (hdd), sector 6


I/O problems are hardware or driver related, so if other disks work fine on that controller/cable, then the only problem can be the disk causing the I/O error.


Thank you for your repsone as perviously mentioned. Rick D. however helped answer my reply to your original response (the one that has "Can you help a newbie understand a couple of things...").

Thanks,

El


Top
 Profile  
 
PostPosted: Wed Jan 25, 2006 10:55 pm 
Offline

Joined: Thu Dec 29, 2005 9:49 pm
Posts: 14
Location: Brockville, ON
My apologies to Robbie Burns (if he's who I'm paraphrasing).

I just re-learned a really simple thing, I THINK. I'm not sure, because I've been trying to properly diagnose a potentially defective harddrive (HD) or HD controller in an NAS (boot floppy, FTP and HTTP) box and I'm only at day 2-3 of the process.

The last two times I lost power (i.e. improper shutdown) to the NAS box, the NAS initialization sequence would basically just "hang" at the "Detected Disk-1" stage. I gave it 4-6hours to proceed, but saw no harddrive activity during this period.

The first time, I was able to get this 120GB drive and its data back using a bootable cdrom (as described in an earlier post on this thread) and e2fsck. I THOUGHT that maybe I hadn't allowed enough time for NAS to complet te lost block test -- NAS never outputs this to screen, to it's hard to tell what's going on.

The second time, however, I spent many many manhours with mkfs and e2fsck to no avail and ended up reformatting the drive and doing a bad block check (see man mkfs and e2fsck respectively).

Subsequent to that, the BIOS would just hang when it tried to auto-detect the HD (I just had the BIOS set to AUTO since I installed this NAS box) during the boot sequence.

POSSIBLE CORRECTION ?
- well, I'm not sure I have any faulty hardware at all: HD or HD controller !

- replaced the CMOS battery (it's about 8yrs old) for good measure based on one of the Troubleshooting Guides at the Maxtor site.
- based on Maxtor's site, I also tried disconnecting my 120GB HD (IDE cable and power), rebooting and setting the Primary Master (the 120GB's position) drive to None, save settings, shutdown, reconnnect 120GB and reboot and do not re-enter BIOS setup.
- the above is the part I relearned - although this same box had booted with this same drive before about 10 times, fundamentally its BIOS is so old it maybe doesn't know what to make of a 120GB IDE HD.
:oops:
Why it hadn't consistently failed at this BIOS auto-detect HD stage I don't know, but I've seen erratic behaviour in PCs before.

- since I've made this change in the BIOS even if I literally pull the plug on this running NAS box for 0.5 - 7hours, when I plug it back in and reboot it is available for use within about 15 mins.
- also, when I remotely look at files or telnet on the NAS box it happens as fast as a local operation. There use to be a 1-2 sec. delay before you'd get a reaction. This makes me wonder if I wasn't keeping things busy by having the BIOS set improperly in the first place, and NAS and the hardware were sortof working in spite of this.

Rick D.
Brockville, Canada


Top
 Profile  
 
 Post subject:
PostPosted: Thu Jan 26, 2006 9:58 am 
rdeschene,

In the manual it recommends that you set hard disks to not installed or none.

Eden


Top
  
 
 Post subject: edeng
PostPosted: Thu Jan 26, 2006 1:49 pm 
Offline

Joined: Thu Dec 29, 2005 9:49 pm
Posts: 14
Location: Brockville, ON
Your quite right, that is what the manual says - I just re-read the copy I had.

Looking over my notes I'm not sure how I had the BIOS set (i.e. AUTO or NONE ?) when I did the installation 8 months ago. :?

Quite possibly when the computer lost power it defaulted back to AUTO (had the old CMOS battery at that point) and THAT was the root cause of the problems I began to have after that. At any rate, I've been trying to force the thing to crash -- pulling the power plug during write operations, etc. and so far it's just bouncing back like a champ.

At any rate, just a couple of items (check BIOS settings, replace CMOS battery) that will hopefully help others in their troubleshooting.

Thanks,
Rick D.


Top
 Profile  
 
 Post subject:
PostPosted: Thu Jan 26, 2006 2:03 pm 
rdeschene,

Your braver then I powering off while it performs a write operation. could end in tears..

good luck

eden


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

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: Google [Bot] 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