sunhux
asked on
recover Solaris x86 root password in vCenter
Have a couple of Solaris x86 running in VMWare/vCenter that after the sysadmin
left, the root password was not handed over.
How do we recover the root password? I can't recall in Sparc what's the keystroke
to send to the Sparc to get into recovery mode
left, the root password was not handed over.
How do we recover the root password? I can't recall in Sparc what's the keystroke
to send to the Sparc to get into recovery mode
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ideally I don't have to build a boot server; actually UNIX admin colleagues left (without handing over password) & we're shorthanded.
For mounting the root / filesystem, is the steps as below?
Please select a device to be mounted (q for none) [?,??,q]: 1
mounting /dev/dsk/c0t0d0s0 on /a
starting shell.
For mounting the root / filesystem, is the steps as below?
Please select a device to be mounted (q for none) [?,??,q]: 1
mounting /dev/dsk/c0t0d0s0 on /a
starting shell.
https://unix.stackexchange.com/questions/422455/disable-annoying-solaris-reboot-key-binding
Try Win r
It should be official policy that root passwords must be in escrow or shared somewhere that the company has access. It should also be grounds for lawsuit if they leave without divulging a password. If the admin left on good terms, ask for the password.
Try Win r
It should be official policy that root passwords must be in escrow or shared somewhere that the company has access. It should also be grounds for lawsuit if they leave without divulging a password. If the admin left on good terms, ask for the password.
ASKER
Win-r key & Ctrl-r doesn't work on on the vCenter (ie doesn't seem to be equiv to Stop-A).
The 1st chap who left was not the one who created that VM while the 2nd chap had been ignoring
email requests for the last couple of weeks of his stay with the organization. He's not responding
to calls/whatsapp. Recovery is of lesser work/complications than lawsuit
The 1st chap who left was not the one who created that VM while the 2nd chap had been ignoring
email requests for the last couple of weeks of his stay with the organization. He's not responding
to calls/whatsapp. Recovery is of lesser work/complications than lawsuit
ASKER
Found:
http://www.unixguide.net/sun/x86faq/7.10.shtml
Q: What is the equivalent of STOP-A for Solaris Intel?
>I don't think so, because Stop-A allow you to go into open boot prom of
>the SUN and on a x86 it's a different thing (BIOS)
Unlike Solaris on Sparc (where STOP-A gets you the OpenBoot prompt),
there is no PROM firmware to drop into on x86.
You can boot your system under kadb and then use a similar keystroke to
drop into kadb and obtain debugging information.
To boot under kadb, type eeprom boot-file=kadb and then:
• Prior to Solaris 8, type CTRL-ALT-d to jump into kadb
• On Solaris 8 or later, type F1-a to jump into kadb <==
•At the Solaris Intel Boot Assistant prompt type "b kadb"
You can then type, for example:
$<systemdump
to force your system to panic and generate a crash dump (the equivalent of
"sync" at the ok prompt on SPARC).
The Device Configuration Assistant (DCA)
portion of the Intel boot process can be interrupted by hitting
escape (when prompted). This (I feel) is the Intel version of the
Boot Prom Monitor. Of course, all the commands cannot be equated
apples to apples because of the hardware differences!
For SPARC only:
If your console is a terminal, you can type "shift-break" or "ctrl-break"
or "ctrl-\" (ctrl-backslash)
or "<enter>" followd by "~" and "ctrl-break" on Solaris Sparc,
but this, too, is not available for Solaris Intel.
http://www.unixguide.net/sun/x86faq/7.10.shtml
Q: What is the equivalent of STOP-A for Solaris Intel?
>I don't think so, because Stop-A allow you to go into open boot prom of
>the SUN and on a x86 it's a different thing (BIOS)
Unlike Solaris on Sparc (where STOP-A gets you the OpenBoot prompt),
there is no PROM firmware to drop into on x86.
You can boot your system under kadb and then use a similar keystroke to
drop into kadb and obtain debugging information.
To boot under kadb, type eeprom boot-file=kadb and then:
• Prior to Solaris 8, type CTRL-ALT-d to jump into kadb
• On Solaris 8 or later, type F1-a to jump into kadb <==
•At the Solaris Intel Boot Assistant prompt type "b kadb"
You can then type, for example:
$<systemdump
to force your system to panic and generate a crash dump (the equivalent of
"sync" at the ok prompt on SPARC).
The Device Configuration Assistant (DCA)
portion of the Intel boot process can be interrupted by hitting
escape (when prompted). This (I feel) is the Intel version of the
Boot Prom Monitor. Of course, all the commands cannot be equated
apples to apples because of the hardware differences!
For SPARC only:
If your console is a terminal, you can type "shift-break" or "ctrl-break"
or "ctrl-\" (ctrl-backslash)
or "<enter>" followd by "~" and "ctrl-break" on Solaris Sparc,
but this, too, is not available for Solaris Intel.
ASKER
Seems like someone in the 1st link can't get the right key sequence.
>On x86 based systems, boot the system in the Solaris failsafe archive.
What's the exact command to enter at the OBP prompt to boot up from failsafe archive?
I suppose I can upload in iso format a Solaris boot CDROM : where do I get one to convert to ISO format?