welcome: please sign in

The following 173 words could not be found in the dictionary of 7 words (including 7 LocalSpellingWords) and are highlighted below:
7b05436df66934a3   access   after   already   Also   an   and   any   are   asynchronously   At   attention   back   bad   be   being   big   boot   Both   bugs   but   case   com   command   connected   connection   Console   console   couple   cu   D1   debian   desired   dev   disks   dist   drive   each   echo   ed   Enter   eth0   eth1   example   exit   first   For   for   get   give   go   google   group   groups   has   hash   have   html   http   if   If   In   in   info   installing   is   it   its   Just   keep   kernel   key   krunk   Krunk   later   line   linux   Linux   log   lom   machine   mark   marked   may   message   messages   might   mind   Mire   mire   msg   must   necessary   need   not   Note   November   ok   on   openafs   order   org   our   over   part1   part3   partition   partitions   patient   period   physical   pipermail   port   Port   powercycle   poweroff   poweron   press   printed   proc   prompt   put   quickly   re   reboot   respond   result   return   returned   S0   screen   second   seconds   sequence   serial   show   signals   small   so   state   sticker   stop   stuck   subsequently   sudo   swap   sys   system   that   The   the   then   This   this   tilde   tildes   to   To   together   told   tty   twice   two   type   unresponsive   use   used   We   when   will   www   You   you  

Clear message


Note when installing debian : http://groups.google.com/group/linux.debian.bugs.dist/msg/7b05436df66934a3

Linux's "eth0" is the physical "Port B" (I put a sticker over it marked eth0). "eth1" is "Port A". Just keep this in mind.

Both disks have a small partition (part1) and a big partition (part3). The big partitions are RAID1'ed together; the small partition on the first drive is boot, the second drive is swap.

Also: http://www.openafs.org/pipermail/openafs-info/2006-November/024356.html

1. Console

Mire's ttyS0 is connected to krunk's LOM port.

To access Krunk's console, log in to mire and type

sudo cu -s 9600 -l /dev/ttyS0

This will give you access to Krunk's console. We have told Krunk not to respond to BREAK signals on the serial line (echo 0 > /proc/sys/kernel/stop-a), so in order to get its attention when it is stuck you must use the LOM attention sequence #. (return, hash mark, period). This will give you the lom> prompt; type console to go back to Krunk's console.

To exit cu, type ~. (return, tilde, period, return). You might need two tildes if you're on an SSH connection to Mire (and not Mire's console).

2. LOM

If the system is in a bad state and the console is unresponsive, you need to use LOM to powercycle the machine.

Enter the LOM prompt (#.), then type the desired command. I used poweroff and then poweron (Note that after each command, the prompt will return quickly, but any messages may be printed to the console later, asynchronously. For example, the poweroff command will result in the poweroff message being printed to the screen a couple seconds after the prompt has already returned, so be patient).

In any case, on reboot, the machine will show prompt "ok".

At the prompt, it is necessary to type in "boot" and subsequently press Enter key twice for the machine to boot our OS.

KrunkInfoz (last edited 2011-04-22 23:09:22 by ClintonEbadi)