NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Sun May 31, 2020 2:38 am

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 6 posts ] 
Author Message
PostPosted: Thu Aug 24, 2006 4:14 pm 
Offline

Joined: Mon Mar 20, 2006 6:14 pm
Posts: 8
I've been running a NAS server quite happily for months, until the cpu fan died recently and apparently took the cpu with it. I've replaced both, but when I reboot, the system 'hangs' at the 'Disk 1 - Found partition' message. It's been that way for less than an hour, but no messsages.

1) Is it running an fsck or something without telling me?
2) I can't telnet to it, or hit it from my browser. Is that a problem or is it not going to be available untit the filesystems are mounted?


Top
 Profile  
 
 Post subject:
PostPosted: Thu Aug 24, 2006 4:34 pm 
Offline

Joined: Sun Jul 09, 2006 10:26 am
Posts: 427
often this is mistaken as a hang. its checking the filesystem and depending on the size of the disks can take a while.

usually you can hear some disk activity, or lights flashing.


Top
 Profile  
 
 Post subject:
PostPosted: Thu Aug 24, 2006 6:34 pm 
Offline

Joined: Mon Mar 20, 2006 6:14 pm
Posts: 8
gaiden wrote:
often this is mistaken as a hang. its checking the filesystem and depending on the size of the disks can take a while.

usually you can hear some disk activity, or lights flashing.


not hearing anything, but should I be able to view the logs to see where it stands? Is the network up?


Top
 Profile  
 
 Post subject:
PostPosted: Fri Aug 25, 2006 11:20 am 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
IDE is CPU-driven and as such can get messy in the event of a processor failure. The good thing is that on reboot, the OS is clean and should perform as expected.

With a 200G drive, time can vary a lot based on number of files, CPU speed and available RAM, however the 16 hours you are describing (in email) is excessive. If the HD LED is on, then the system is still checking, or perhaps stuck checking. It is also possible that the board logic is damaged as well, but that is less likely.

One thing you can do is boot a live distro (Knopix, Slax, Ubuntu, etc.) and check the drives manually. That will give you the feedback you are looking for. NASLite is incapable of launching services until the drives are properly mounted and the services properly configured per the available storage resources.

Hope that helps.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Aug 25, 2006 11:41 am 
Offline

Joined: Mon Mar 20, 2006 6:14 pm
Posts: 8
Tony wrote:
IDE is CPU-driven and as such can get messy in the event of a processor failure. The good thing is that on reboot, the OS is clean and should perform as expected.

With a 200G drive, time can vary a lot based on number of files, CPU speed and available RAM, however the 16 hours you are describing (in email) is excessive. If the HD LED is on, then the system is still checking, or perhaps stuck checking. It is also possible that the board logic is damaged as well, but that is less likely.

One thing you can do is boot a live distro (Knopix, Slax, Ubuntu, etc.) and check the drives manually. That will give you the feedback you are looking for. NASLite is incapable of launching services until the drives are properly mounted and the services properly configured per the available storage resources.

Hope that helps.


Tony,

Thanks. That helps a lot - knew I could count on you. Does your last sentence answer the question about telnet not being available? In other words, are the logs not reachable until the filesystems are mounted?

I just got a copy of RIPLinux - I'll try that and see.


Top
 Profile  
 
 Post subject:
PostPosted: Thu Sep 07, 2006 9:26 pm 
Offline

Joined: Mon Mar 20, 2006 6:14 pm
Posts: 8
foxtrot wrote:
Tony wrote:
IDE is CPU-driven and as such can get messy in the event of a processor failure. The good thing is that on reboot, the OS is clean and should perform as expected.

With a 200G drive, time can vary a lot based on number of files, CPU speed and available RAM, however the 16 hours you are describing (in email) is excessive. If the HD LED is on, then the system is still checking, or perhaps stuck checking. It is also possible that the board logic is damaged as well, but that is less likely.

One thing you can do is boot a live distro (Knopix, Slax, Ubuntu, etc.) and check the drives manually. That will give you the feedback you are looking for. NASLite is incapable of launching services until the drives are properly mounted and the services properly configured per the available storage resources.

Hope that helps.


Tony,

Thanks. That helps a lot - knew I could count on you. Does your last sentence answer the question about telnet not being available? In other words, are the logs not reachable until the filesystems are mounted?

I just got a copy of RIPLinux - I'll try that and see.


UPDATE - turned out the IDE channel was hosed and would only support 1 drive. Never seen that before. Swapped out the MB for a slower one that really should have been my choice from the start and all is well.

No drive errors - e2fsck ran great and fast under RIPLinux - highly recommend it.


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

All times are UTC - 5 hours [ DST ]


Who is online

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