We had an X1 we wanted to do a network-boot install on, which was ignoring the break command from the LOM during power-up. We could not interrupt the boot process before the existing OS hung.To get the system out of this state:In the diagnostics mode the X1 is hyper-sensitive to the break command; once the hardware has finished initializing you can use the normal #. and break sequences to drop to the ok prompt and do what you will with the system.Warning: Don't be fooled by the ok PROM prompt after the bootmode forth command; the X1 has not initialized all (any?) of its hardware, so attempts to boot from this ok prompt will fail with a Fast MMU Data Miss error.
lom> poweroff lom> bootmode forth lom> poweron [...] ok setenv diag-switch? true ok reset-all
Sometimes that didn't work
OK, presuming you've already set up your Jumpstart back end, there's a different way of accomplishing the same thing:lom> poweroff
lom> bootmode forth
lom> poweron
ok setenv boot-device net
ok reset-all
- When the installer starts up, quit out of it to the installer-os prompt
#.
lom> break
ok setenv boot-device disk
ok boot net - install
no comments |
post comment
Virtual Dave Megaplex:
Home Page- This wiki's start page
- Send Feedback To Dave
Logged in Users: (0)
Recently Changed
Check Internet Service Database Match- Device-Local Certificate Expired
- CLI Policy Lookup
- DH Selection For IPsec VPNs
- Scan For Newly Added Disk
- nmap
- Seconds Since Epoch to Local Time
- Link Monitor
- DH group to OAKLEY_GROUP table
- Fire Eater
- start
- FortiClient Error Codes
- dhparams Generation
- SSL Certificate Bundles
- ufw
- Grow A LVM Partition
- Creating Users
- whoami
- list databases
- 2023
- 2022
- 2019
- 2018
- 2017
- 2011
- 2010
- 2008
- 2001
- 2000
- 1999
Editing: snipsnap-help, Image Macro(Et auditum est, et idcirco ego nunc simulare)
This is a collection of techical information, much of it learned the hard way. Consider it a lab book or a /info directory. I doubt much of it will be of use to anyone else.