|
Size: 341
Comment:
|
Size: 1570
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
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 == Console == |
|
| Line 5: | Line 13: |
| 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. | To access Krunk's console, log in to mire and type |
| Line 7: | Line 15: |
| Root password is the same as the KVM (at the moment). | {{{ 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). You might need two tildes if you're on an ssh connection. == 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. The machine will reboot, and 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. |
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). You might need two tildes if you're on an ssh connection.
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. The machine will reboot, and 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.