Subject: Finally, success (WAS Re: Mandrake install troubles with DAC960 RAID controller...)
From: Joshua J.Kugler (isd@as.uaf.edu)
Date: Mon Jan 07 2002 - 21:32:43 AKST
civileme, et al -
This update is late, the server was up and running last Thursday night (1/3).
So, I was finally able to get through the install by using the second disk,
which booted with a 2.2.x kernel. This kernel was able to correctly
initialize the DAC960. During the install, I was able to select the 2.4.x
kernel, and it didn't complain, and set up lilo correctly. I rebooted,
compiled 2.4.17, and away we went. Thanks for the tips!
Now, for the complaints, suggestions. :)
I realize strcmp("install", "upgrade") != 0, but it would be nice if the
install routine would look for existing configuration info. I was prepared,
so I had written down pertinant info, but it would be nice if install looked
for an existing /etc, and gleaned partition information, IP addresses, DNS
servers, etc. It would make the install go that much more smoothly.
I noticed during package selection that aspell would not install without the
GB (Great Britain) dictionaries (depended on them), even if US dictionaries
were selected. Why?
What is the difference between bash and bash1? The importance on bash1 says
"maybe." Why two? It just seems a bit confusing to users, as there is
nothing in the description to differentiate them.
kdeutils depends on efax? Really? Why can't I install kdeutils without
installing efax? This is a server, after all.
There still needs to be some tweaking done on the startup configuration in
the install program. I'm sorry, I didn't write everything down, but I know
there were several services I selected to start at boot that didn't get
included in /etc/rc.d/rc3.d/. I had to symlink them manually.
Another problem: Today, I discovered my server was not responding at all.
No ping, no ssh, nothing. Went to the server closet and was going to login,
but there was nothing on the console. Keyboard wouldn't respond. Num lock
wouldn't toggle, etc. Ctrl-Alt-Del wouldn't work. Had to hit reset on the
box (not something I like to do on a Linux box, much less a server). When it
came up, I looked through all the logs, and nothing looked amiss (other than
no entries after 12:40AM today). Does this ring a bell, or do I need to
start trouble shooting on my own? After bringing the server back up,
fsck'ing the partitions, and restarting everything, it was fine. We'll see
if it happens again.
Thanks again for all your help. It is much appreciated.
j----- k-----
-- Joshua Kugler, Information Services Director Associated Students of the University of Alaska Fairbanks isd@asuaf.org, 907-474-7601
This archive was generated by hypermail 2a23 : Mon Jan 07 2002 - 21:36:59 AKST