We think we have ruined the image that comes with the SC or something but we were trying to install Debian Linux on this V240. On the OBP we typed ok boot new linux root=/dev/nfs nfsroot=10.1.3.1:/mnt/iso ip=10.1.3.11:10.1.3.1:10.1.3.254:255.255.255.0:SWITCH01
/mnt/iso is where we mounted the Debian ISO via lofiadm
10.1.3.11 is the IP we wanted to assign this machine
After it went through this, we got a lot of garbage on the screen. So we recycled power (Cold reboot) the machine and now this happens: ALOM BOOTMON v1.5.1 ALOM Build Release: 001 Reset register: e0000000 EHRS ESRS LLRS ALOM POST 1.0 Dual Port Memory Test, PASSED. TTY External - Internal Loopback Test TTY External - Internal Loopback Test, PASSED. TTYC - Internal Loopback Test TTYC - Internal Loopback Test, PASSED. TTYD - Internal Loopback Test TTYD - Internal Loopback Test, PASSED. Memory Data Lines Test Memory Data Lines Test, PASSED. Memory Address Lines Test Slide address bits to test open address lines Test for shorted address lines Memory Address Lines Test, PASSED. Memory Parity Test Memory Parity Test, PASSED. Boot Sector FLASH CRC Test Boot Sector FLASH CRC Test, PASSED. Return to Boot Monitor for Handshake ALOM POST 1.0 Status = 00007fff Returned from Boot Monitor and Handshake Clearing Memory Cells Memory Clean Complete Loading the runtime image... ¡¼å!ØÖ
+½ç+ Gûb î
+($+ Ø½ C0 ÑbCÏÀ¤èÜäC8Á8
Please help! We're actually not physically at the server and it's sitting 10,000 miles away. We have access to remote power boot and a serial access into the machine however.
Thank you in advance
Transworld Telecom Support
Edited by: 833239 on Feb 3, 2011 5:18 PM
Just FYI, This has been resolved
This was caused by a mismatch in the baud rates of the console server connected to the Serial port of the machine, where a colleague had changed
ttya-mode to 19200,8,n,1,- while the console server was still configured for 9600.
Please note that the speed / baud compatibility changes between steps during the boot process. That is, the baud required before the point of
Loading the runtime image...
showed all messages properly @ 9600
Right after that message, it was required we change it to 19200, to be able to see all messages
After getting into ALOM, and issuing a command like 'poweron', we got all garbage again, till we changed the baud back to 9600
and once booted into OBP, the baud needed to be changed back up to 19200.
Anyway, everything's been set back to 9600 to avoid this in the future.