Re: [leaf-user] Harddisk: Device... deceased :P

2004-07-21 Thread Jon Clausen
Welll...

To summarize;

I ended up compiling a 2.4.24 kernel in order to get the disk recognized.
Basically, once I got all the patches applied, the correct options selected,
modified linuxrc to mount the disk on /var/log at boot, and all that, it
worked out fine.

So I put the router in service.

Next day I tried ssh'ing into it. It accepted the password, but then the
connection would just hang. This got me worried.

Day after that I decided to go over there and check the box out. The rack
was pretty hot (insufficient ventilation) and the box itself was definitely
too hot.

It would still route, but dhcpd wouldn't hand out ip addresses. Since
there's no screen/keyboard available on location, my only real option was to
power off/on to see if that would at least let me log in.

Long story short;

Brought it home, hooked it up with monitor.

With disk disconnected it boots fine.

With disk connected, the box never completes is POST :(

Lesson learned:

IDE disks aren't meant for 24/7, and need to be kept cool. (DOH!)

So the question now is;

Apart from ensuring that the disk is kept cool, what can I do to minimize
'operating stress'?

That is, is it a good idea to have the disk spin down, considering that
shorewall.log will be written to more or less constantly (causing the disk
to spin up/down a lot)

Hmmm... Maybe I should just go with CF/DOM or something else, solid state,
and set up a server to move the logs to $whenever, accepting the fact that
chips get worn out aftesr so-and-so-many rewrites...

I find it sort of ironic, having spent much time in order to put the logs on
disk (so they would survive powercuts etc), that those same logs are now
lost because the disk died... :P

Oh well... Just thought I'd let everyone know that I got it working... 'till
it died.

/Jon

-- 
Just say know!


---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click

leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html


RE: [leaf-user] Harddisk: Device... deceased :P

2004-07-21 Thread Peter Mueller
 Hmmm... Maybe I should just go with CF/DOM or something else, 
 solid state,
 and set up a server to move the logs to $whenever, accepting 
 the fact that
 chips get worn out aftesr so-and-so-many rewrites...

Yes, this is what I would (have) done.  CF is badass, it boots so fast.

 I find it sort of ironic, having spent much time in order to 
 put the logs on
 disk (so they would survive powercuts etc), that those same 
 logs are now
 lost because the disk died... :P

Well why don't you set up a remote syslog server instead?

/etc/syslog.conf:
*.* @10.0.0.1

Then /etc/init.d/sysklogd restart.

On the remote server, you will need to allow firewall rules (if
necessary) and configure syslogd to accept remote logs.  This is done on
redhat via /etc/sysconfig/syslog:
SYSLOGD_OPTIONS=-m 0 -r
On other distributions you can probably modify the Sys-V script
directly.

P


---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21alloc_id040op=click

leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html