Root password problem by passwd root

The password whas changed by typing :
%>passwd root
After this the system worked fine 3 days...
On first reboot i can NOT login like root...
Please help me...

Can you boot from the floopy disk,then mount the system,and change the file passwd...

Similar Messages

Root Password Problem

Hi ,
I am new to solaris . I installed the solaris 10 (beta 7) on P-111 machine. I start installation with Intractive installation but after 1 cd complition , OS reboots but no GUI. I tried 2-3 times.
After that i choose the option Jump start and installation completes. During the installation root password was not asked.
After installation ,when i login it just ask user not for password.
I can login in CDE session but not able in Java Desktop Environment.
Now I want to add user with the help of "Solaris management console" utility. But it ask for Root password.
Now please guide me how i can choose the Root password and how i can login in the Java desktop environment.
Regards
Gorayen

You can set your password with the passwd command

10.3 MYSQL Root Password problem..

We are running OSX Server 10.3.9 with the built in MYSQL. Somehow the root password for MYSQL that was set is not working and I am locked out with a 1045 error. I need to know how I go about resetting the ROOT password for MYSQL. as I mentioned, I am using the MYSQL that comes with 10.3.9. I have looked online but the tutorials for resetting the passwords do not work on my version...
Thanks...
-- Dave Hauss

I think by default Solaris uses CRYPT_DEFAULT=__unix__ which limits you to 8 characters.
in order to have more than 8 usable characters in your passwd, then you must use "md5"
CRYPT_DEFAULT=md5
this is located in : /etc/security/policy.conf
I think you may want to change the password length in /etc/default/passwd
PASSLENGTH= (default=6) change it to something of your liking.
be sure to do a little more research on the exact steps, but this is what you are loking for. im just going by memory here.

Root password problems

when using sudo command i can't remember my password how do i reset it ? what i would like to do is install apache on my desktop mac to enable me to use wordpress offline.

no this did not help.
I am the only user on my desktop so at loging i hit enter. but when in terminal using the sudo command it asks for root password which i cant remember.

Shaman doesn't ask for root password. But gets root privileges!!

As the title says:
Shaman is launched as a reguler user, never asks for root password, but still i able to install and uninstall packages.
Either something in my system is seriously fucked, or there is a major securiy problem with shaman.
Running openbox, installed shaman while running gnome, if that has anythiung to say. Sudo is not installed.
Output from running shaman in terminal:
[gert@flyktig ~]$ shaman
This process is currently running setuid or setgid.
GTK+ does not allow this therefore Qt cannot use the GTK+ integration.
Try launching your app using 'gksudo', 'kdesudo' or a similar tool.
See http://www.gtk.org/setuid.html for more information.
Translations are enabled.
Loading translations from "/usr/share/shaman/translations/"
Parsing "core"
Parser exited
Parsing "extra"
Parser exited
Parsing "community"
Parser exited
Parser exited
Log File should be: ""
"core" ---> "http://mirror.archlinux.no/core/os/i686"
"extra" ---> "http://mirror.archlinux.no/extra/os/i686"
"community" ---> "http://mirror.archlinux.no/community/os/i686"
Root privileges retired.
"/home/gert/.config/shaman/shaman.conf"
>>
>> Shaman 1.0.9
>> Compiled against Qt 4.4.1
>> Running with Qt 4.4.3
>>
>> Our website is @ http://shaman.iskrembilen.com/ , join in!!
>> You can also find a bugtracker in the website, please use it.
>>
>> Have you found a bug? Help us solving it faster! Please read
>> http://shaman.iskrembilen.com/trac/wiki/Debugging_Shaman
>> and please follow these steps to report bugs effectively!
>>
>> Starting Up Shaman...
User agent is: "shaman/1.0.9 (Linux i686) libalpm/3.1.1"
Shaman registered on the System Bus as ":1.51"
Service org.archlinux.shaman successfully exported on the System Bus.
--> UNSETENV HTTP_PROXY
--> UNSETENV FTP_PROXY
Populating Repo column
Log file is: /var/log/pacman.log
refinePkgView
The left TextBox is over, let's do the ComboBox
Show all packages
Remove Package
"Uninstall package: alunn"
"alunn"
"community"
Process Queue
Queue Dialog started
Queue signals connected
Starting Package Removal
Root Privileges granted.
Uid is: 1000
Received Event Callback
Alpm Thread Waiting.
Entering Queue Lock
Releasing Queue Lock
Alpm Thread awake.
Received Event Callback
Alpm Thread Waiting.
Entering Queue Lock
Releasing Queue Lock
Alpm Thread awake.
Received Event Callback
Alpm Thread Waiting.
Entering Queue Lock
No scriptlet for package alunn
Releasing Queue Lock
Alpm Thread awake.
Received Event Callback
Alpm Thread Waiting.
Entering Queue Lock
No scriptlet for package alunn
Releasing Queue Lock
Alpm Thread awake.
/sbin/ldconfig: Can't create temporary cache file /etc/ld.so.cache~: Ikke tilgang
Root privileges retired.
Transaction Completed Successfully
refinePkgView
refinePkgView
The left TextBox is over, let's do the ComboBox
Show all packages
[gert@flyktig ~]$

The point of this thread was that you don't need to enter the root password at all. Not the first time, not ever.
As far as I understand, it is supposed to work like this: When you first use shaman too install anything, it asks for the root password You can tick a "Do not ask me again"-box, so you don't have to enter the password again. If you tick the box and enter the password, shaman add the lines
[auth]
askforpwd=false
to the users shaman.conf-file (~./config/shaman/shaman.conf) The next time shaman is run, it checks the config file, and if the askforpwd value is set to false, it grants itself root privileges (with some nifty setuuid root-thingy, I imagine) This is not the problem - this is the feature.
The bug is this:
the fact that any user can add the lines
[auth]
askforpwd=false
to his own shaman.conf file, without ever entering the root password in shaman. The next time shaman is run, it checks the config file, and if the askforpwd value is set to false, it grants itself root privileges - even though the user has never entered the root password.
This works for any unprivileged user on the system.
If that is indeed a feature intended by any sane person, then I'm Mother Mary. And that can't be, seeing as I don't have breasts.

Root password problem in Solaris 10

Hi All,
Have anyone noticed this problem before?
I've set the password on Solaris for the root user as "rootroot123". However, I'm able to login with any password that starts with rootroot (i.e. rootroot*)...
My solaris version is:
SunOS mynode01 5.10 Generic_138888-03 sun4u sparc SUNW,Netra-240
Is there a bug report in Solaris regarding this or any way to solve it?
Thanx,
Mahmood

I think by default Solaris uses CRYPT_DEFAULT=__unix__ which limits you to 8 characters.
in order to have more than 8 usable characters in your passwd, then you must use "md5"
CRYPT_DEFAULT=md5
this is located in : /etc/security/policy.conf
I think you may want to change the password length in /etc/default/passwd
PASSLENGTH= (default=6) change it to something of your liking.
be sure to do a little more research on the exact steps, but this is what you are loking for. im just going by memory here.

Login as Root password problem (the changed password isn't working!)

I have enabled root user. I've changed my password for root user a couple of time and I am still not cable to login as root!! (username: root).
Any thoughts and help? thanks a lot! Alon.

Hello Stephen,
Change of password is not done via configtool. Configtool secure store just stores the current password which is taken by SDM during the deployment.
To change the password of the administrator user, you will need to enable SAP*. Please follow note Note 669848.
1. open the configtool: C:\usr\sap\<InstenceID>\JC<xx>\j2ee\configtool --> configtool.bat
ex: C:\usr\sap\J9E\JC09\j2ee\configtool ---> configtool
2. Activate the "super admin" and enter password(this is your choice) in configtool properties:
In Config tool: cluster-data>Global Server configuration>services--> com.sap.security.core.ume.service
find below ume properties and change values as i mentioned
ume.superadmin.activated=TRUE
ume.superadmin.password= < enter password>
3. Save the changes in configtool. click on Save button.
4. Stop the j2ee engine.
5. Start the j2ee engine.
6. Now you login to UME with username "SAP*" and password "what you entered in configtool"
7. After logging into UME Search for user "administrator" then unlock this user; or if you want to change password you can change it.
8. Goto config tool follow step 1:
9. Follow step2: and change ume property values as below:
ume.superadmin.activated=FALSE
ume.superadmin.password= (note: seta as default or blank)
10. Save the change setting in configtool.
11. Restart the j2ee engine ( Stop and Start).
12. Now login to user as "Administrator"; you will succussfully loging into ume;
Hope this helps.
Regards,
Snehal

Solaris 8, no root password, no login

During install I got a message like 'could not write /etc/passwd, is locked', I still continue the install, then after a while the install asks for the second software disk, this one is not recognized, so I skip it. Then after rebooting the system, it asks for a login and password, so I enter root en give my password. No way, it won't comply. So I try changing the /a/etc/passwd file (it seems to be the new environment), for instance by adding a line test::::: , so no password should be asked, this also does not work. Removing de root password from the passwd file does not work either. So, who can help me loggin in into the system without a root password, on a Linux machine this is no problem in stand-alone mode no password is asked. Booting with the b -s option gets you into the stand-alone or service mode. This is my last try, then I will throw Sun away......
PS. My system is fully recognized by the install software. No problem there.
Thanx....

Did you remove the 2nd entry in /etc/shadow file?
Each entry in the shadow file has the form:
username:password:lastchg:min:max:warn:inactive:expire:flag
Thanks
-Manish

Sun 7120 - problems with resetting root password?

We have just taken delivery of a Sun 7120 system, did the initial config today no problems, then came to log in to tweak it and it refused my root password. Logged on the serial console with the same password fine, logged out and now it won't let me back in, just says "login incorrect". Have reset the CLR PW jumper on the mainboard, and rebooted and it then comes up in the preboot system, but reports errors about the ILOM. After powering down and removing the jumper, the root password is still there!
Output on bootup attached below, can anyone help?
Cheers
Primary Bootstrap.
U-Boot 1.1.4
Custom AST2100 U-Boot 3.0 (Aug 17 2010 - 01:30:05) r58107
DRAM: 119 MB
Flash bank 0 at 10000000 has 32MB in 256 sectors (chipSize 1<<25, ratio 1, bufSz
1024).
Flash: 32 MB
VUART1 at port 0x03f8, SerIRQ[4] disabled
VUART2 at port 0x02f8, SerIRQ[3] disabled
Protecting U-Boot flash sectors; monitor_base=10040000.
board_findGpioNum(): ERROR, 'BIOS_TOP_BLOCK_LOCK' does not match any pin.
board_findGpioNum(): ERROR, 'SP_PECI_ENABLE' does not match any pin.
H/W: Lynxplus Service Processor; SOC: AST2100 Rev. 02 ('A3')
PWC_SP_Broken_OD = 0; ARM restart caused by: power-on
The host is OFF(S5) (hostWantsPwr=0, powerGood=0,
allowPwrOn=0|0, outOfReset=0, fatalError=0).
Reset straps=0x8c819180, def. H-PLL=264 MHz, CPU/AHB=2:1, boot CS0# normal spe
ed
PCI w/VGA noVBIOS; NOR 38ns/byte; DRAM clock is M-PLL: 264 MHz (DDR2-528)
DRAM: 128MB data - 8MB VGA, 32-bit noECC, 2 BA 10 CA, CL=4 BL=4 ap=1, 61440 us
refr
Board Revision - 8d
Date: 2011-01-19 (Wednesday) Time: 7:04:21
Reading FRUID...Valid CRC.
ethaddr=00:21:28:3D:BD:9A
eth1addr=00:21:28:3D:BD:9B
Net: MAC1 PHY not ready faradaynic#0, faradaynic#1
Enter Diagnostics Mode ['q'uick/'n'ormal(default)/e'x'tended(manufacturing mode)
] ..... 0
Diagnostics Mode - NORMAL
<DIAGS> Memory Data Bus Test ... PASSED
<DIAGS> Memory Address Bus Test ... PASSED
I2C Probe Test - Motherboard
Bus Device Address Result
=== ============================ ======= ======
2 Sys FRUID (U3003) 0xA0 PASSED
2 Power CPLD (U3301) 0x4E PASSED
2 CPU0 Fault LED's (U3001) 0x40 PASSED
2 CPU1 Fault LED's (U3002) 0x42 PASSED
2 PCA9555 (Misc) (U3005) 0x44 PASSED
2 DIMM IMAX (U3102) 0x12 PASSED
6 Bank Panel Led's (U2701) 0xC6 PASSED
6 DS1338(RTC) ( U803) 0xD0 PASSED
6 Temp Sensor1(LM75) (U3011) 0x90 PASSED
6 Temp Sensor2(LM75) (U3012) 0x92 PASSED
6 Temp Sensor3(LM75) (U3010) 0x94 PASSED
I2C Probe Test - Chassis(2U HYDE24)
PDB Board
Bus Device Address Result
=== ============================ ======= ======
1 PCA9548 Mux (U0202) 0xE0 PASSED
1 PDB FRUID (U0203) 0xAA PASSED
1 MAX7313 (U0201) 0x40 PASSED
1 MAX7315 (U1001) 0x46 PASSED
Power Supply 0
BUS Port DEVICE Address Result
=== ==== ==================== ======= ======
1 0 PS 0 FRUID ( - ) 0xAC PASSED
1 0 PS 0 CTRL ( - ) 0x7C PASSED
Power Supply 1
BUS Port DEVICE Address Result
=== ==== ==================== ======= ======
1 1 PS 1 FRUID ( - ) 0xAC PASSED
1 1 PS 1 CTRL ( - ) 0x7C PASSED
Unified Fan Module
BUS Port DEVICE Address Result
=== ==== ==================== ======= ======
1 2 FT 0 FRUID (U0203) 0xAC PASSED
1 2 FT 0 MAX7313 (U0201) 0x42 PASSED
1 2 FT 0 ADT7462 (U0202) 0xB8 PASSED
1 3 FT 1 MAX7313 (U0501) 0x42 PASSED
1 3 FT 1 ADT7462 (U0502) 0xB8 PASSED
24 Disk Backplane
BUS Port DEVICE Address Result
=== ==== ==================== ======= ======
1 4 BP MAX7313 ( U8) 0x44 PASSED
1 4 BP FRUID ( U6) 0xAC PASSED
LSI Daughter Card
BUS Port DEVICE Address Result
=== ==== ==================== ======= ======
1 4 EXP FRUID ( U07) 0xA0 PASSED
1 4 EXP Tmp Sens ( U04) 0x98 PASSED
1 4 EXP PCA9538 ( U10) 0xE6 PASSED
1 4 EXP EMP570 ( U05) 0x50 PASSED
Connector Board
BUS Port DEVICE Address Result
=== ==== ==================== ======= ======
1 4 CONN FRUID ( U05) 0xA2 PASSED
<DIAGS> PHY #0 R/W Test ... PASSED
<DIAGS> PHY #0 Link Status ... FAILED
MAC1 PHY not ready <DIAGS> ETHERNET PHY #0, Internal Loopback Test ... RX error
status = 0xB00905C0
FAILED
No data received
<DIAGS> USB 1.1 Test ... PASSED
<DIAGS>Access to BIOS Flash ... PASSED
<DIAGS> Testing PowerCPLD version ... PASSED
checking for abnormal reboots: 0:0.
abnormal reboot found -- too long, ignore
Booting linux in 3 seconds...
Un-Protect Flash Bank # 1
flctrl: Recovery U-Boot (r58107) at 0x10040000 is valid (min. r51654).
flctrl: Current U-Boot is not the main one.
bootpkg: Not safe to boot ILOM (stat=1). Check Preboot "vers" command,
then reload ILOM ("net flash") as needed.
ILOM Pre-boot Menu
Type "h" and [Enter] for a list of commands, or "?" [Enter] for
command-line key bindings. Type "h cmd" for summary of 'cmd' command.
Idle time-out is disabled. Set 'bootretry' to enable it.
This is Recovery U-Boot. Use "vers all" to check flash images.
Preboot> vers all
Main ILOM image at 0x100a0000:
Service Processor Firmware
Version = 3.0.9.27, for SP type 52
Date ='Tue Aug 17 01:54:07 EDT 2010', Build ='r58107'
Name ='sysbios'
uboot @0a0000 OK, kernel @102000 OK, root @20d684 OK,
sysbios @c9b6c4 OK, pwrseq @d51aa2 OK, pbsw @d6096c OK
coredump @1500000 8192 KiB, persist @1d00000 2048 KiB, params @1f00000 1024
KiB
Recovery firmware and data:
Normal U-Boot at 0x100a0000:
Date ='Aug 17 2010', Build ='r58107'
uboot @0a0000 OK
Recovery U-Boot at 0x10040000:
Date ='Aug 17 2010', Build ='r58107'
uboot @040000 OK
Primary Bootstrap build: r52205
Permanent environment: not found

I don't think it is. The jumper you saw is likely the ILOM jumper. The ILOM is different than the BUI(OS) password so they can be reset/changed independently.

Problem resetting mysql root password

I have install 5.5.20 from mysql from the TAR file. that install was done from an admin user by the name of mysql. Using the mysql user, I have reached a point where I am unable to reset the root password. I have tried both method of resetting the password with no success. Here is what I did. (path omitted for brevity, but used in the commands)
shell>mysqld_safe --skip-grant-tables
shell>mysql
mysql>UPDATE mysql.user SET Password=PASSWORD('newPass')
-> WHERE User='root';
mysqlQuery OK, 0 rows affected (0.05 sec)
Rows matched: 0 Changed: 0 Warnings: 0
shell> mysqld_safe
shell> mysql -u root -p
Enter password:
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
created an init file that had ths
--------contents of minit-------
UPDATE mysql.user SET Password=PASSWORD("newPass") WHERE User='root';
FLUSH PRIVILEGES;
------------eof--------------
mysqld_safe --init-file=minit
killed mysqld
mysqld_safe
mysql -u root -p
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
By the way, I closely monitored the .err file and nothing unusual or pacular showed up there.
Anyone see what I did wrong? Anyone have other suggestions?

I have install 5.5.20 from mysql from the TAR file. that install was done from an admin user by the name of mysql. Using the mysql user, I have reached a point where I am unable to reset the root password. I have tried both method of resetting the password with no success. Here is what I did. (path omitted for brevity, but used in the commands)
shell>mysqld_safe --skip-grant-tables
shell>mysql
mysql>UPDATE mysql.user SET Password=PASSWORD('newPass')
-> WHERE User='root';
mysqlQuery OK, 0 rows affected (0.05 sec)
Rows matched: 0 Changed: 0 Warnings: 0
shell> mysqld_safe
shell> mysql -u root -p
Enter password:
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
created an init file that had ths
--------contents of minit-------
UPDATE mysql.user SET Password=PASSWORD("newPass") WHERE User='root';
FLUSH PRIVILEGES;
------------eof--------------
mysqld_safe --init-file=minit
killed mysqld
mysqld_safe
mysql -u root -p
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
By the way, I closely monitored the .err file and nothing unusual or pacular showed up there.
Anyone see what I did wrong? Anyone have other suggestions?

Reset lost root password and now have read only filesystem

Hello,
I have recently had to reset a locked root password by booting from cdrom, mounting the first boot disk, editing the shadow file to remove root's password and rebooting the system.
The system has booted OK but, I now have a read only filesystem - everything in / cannot be edited, passwd doesnt work etc.
df -k shows the root (/) filesystem has been mounted on the physical disk I edited:
Filesystem kbytes used avail capacity Mounted on
/pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a 10085836 185862 9799116 2% /
but in the vfstab it still references the disksuite metadevice:
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
/dev/md/dsk/d30 /dev/md/rdsk/d30 / ufs 1 no -
So, can I simply boot from CDROM again, amend the vfstab to be /dev/dsk/c0t0d0s0 (instead of /dev/md/dsk/d03) and reboot?
Any help with this is appreciated!
Thanks,
Emma

df -k should have shown root mounted on md0
e.g. on my machine
# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d0 8260691 4366317 3811768 54% /
what does /etc/system show for rootdev?
# grep rootdev /etc/system
* rootdev: Set the root device. This should be a fully
* rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
rootdev:/pseudo/md@0:0,0,blk
Remember if this is a mirrored drive, when you boot from CD you may need to mount both sides of the mirror and make changes on both sides- otherwise the replication may not goes as expected.
Actually, I have run into problems with the modifying one side of a mirror this way. In the past Sun tech support would recommend that I break the mirror and then rebuild it once the system is up and running. So in your case you may want to boot from CD, mount the 1st disk slice, edit /etc/vfstab AND /etc/system, boot into the OS and use the various meta commands to delete and rebuild the mirror- or at least maybe to drop and reattach the 2nd 1/2 of the mirror.

Lost root password Can't get in to reset.........Ultra 5/10 Solaris

Just bought an Ultra 5 Sun desktop at the thrift store. This thing is brand new and was still in the box. Fired it up and come to find, it has never even been configured so I did so myself. I entered a User name and then followed that with setting up a new password for the first time. The system reboots on it's own and goes to a point asking for my Name and then password. Only problem is the password will not even type into the bar that requests it. Do I need to reset it and if so how?

Hi, boot with single user mode using cmd boot cdrom -s,then use passwd cmd to change root password.if it doesn't work.mount your root slice as /a,then edit /etc/shadow file and delete root passwd entry.I hope this tip fix your problem. : )

Lost root password

Hi mac community,
I´m a newcomer to Mac (and Linux) and I´ve had a problem related to root password.
I accidentally entered a password for root on my mac and I can´t remember it. I asked friends that work under linux for help, but they weren´t able to solve me the problem.
We´ve tried to start up the computer from the installation CD´s to delete the '*' symbol at /etc/passwd file but we failed. We either can´t do it once we are in user account. We can´t access root by any mean...
Can you help me before I set fire to my computer? ... ...
Thanks a lot.

Hello sailbillo:
Welcome to Apple discussions
To save your local fire department an emergency run, read this knowledge base article:
http://docs.info.apple.com/article.html?artnum=106156
Toward the bottom you will find the steps for resetting an administrator password.
This article has more information about the root user:
http://docs.info.apple.com/article.html?artnum=106290
Barry

Root password

I may have erased my root password now I try to install but it does not work. after mounting /dev/dsk/c0d0t0s0 /mnt I do cd /mnt. then I type the terminal and do vi. but it said that the terminal is unknown and also I can access shadow to delete the password. what do i do wrong? If somoene know the step please let me know.
Thanks

Hi there,
I do not know how you lost your root passwd but the following is are the steps to recover the root passwd if you have wrongfully
change the shell for the root. I am sure you can use the same steps for your purpose.
Question:
Some root users like to manually change the shell of account root. The most possible mistake is to simply change the default shell "/sbin/sh" to "/sbin/ksh". Thereafter, you will fail to log on the root because of the error of "No shell".
To fix the problem, the only way is to change root shell from /sbin/ksh to /usr/bin/ksh in /etc/passwd. Since the /etc/passwd is owned by root and you can not log on as root any more, so how to solve the problem ?
The problem is caused because the user does not know there are no other shells but Bourne Shell in /sbin. Therefore the system can not find /sbin/ksh and you fail to log on the root because of "No shell".
/sbin/sh is a hard copy under root (/) file system to make the system usable even before the file system /usr is mounted. It is very useful for system maintenance.
Below is the solution for Solaris Sparc/Intel platform respectively.
Caution: This solution can be also used to break into a system to alter security sensitive files, only authority persons can use it. Any damage caused is under your own responsibility.
For Solaris Intel platform:
1. Note down the root file system, e.g., /dev/dsk/c0t0d0s0
2. Insert installation CD
3. Reboot the system
4. Press ESC at the Press ESCape to interrupt autoboot in 5 seconds prompt.
5. Press the F2 key (F2_Continue) at the Solaris Device Configuration Assistant
screen.
6. Press the F2 key (F2_Continue) at the Identified Devices screen.
7. Select the CD-ROM drive as the boot device from the Boot Solaris screen,then press the F2 key (F2_Continue).
8. Type b -s at the Select the type of installation: prompt.
9. Mount the root file system to /a. E.g.,
# mount /dev/dsk/c0t0d0s0 /a
10. Modify /etc/passwd to correct the mistake by
vi /a/etc/passwd, then change /sbin/ksh to /usr/bin/ksh in root entity
11. Unmount the /a directory and reboot the system.

Root password changed

Hi.. the root password of my server is changed without anybody's knowlegde.
I'm now not able to login to this server. however i'm able to login to the sc> prompt.
Is there any way to reset the root password from sc> prompt ?
what would be the best way to recover the root password?
Regards
Nirvana

You should be able to get to ok prompt after sending a break from the sc> prompt.
Your zones should not be impacted except to be shutdown when the system is shutdown.
Find out who changed the root password and why so that you can prevent
this problem in the future.
You have a couple of recovery options:
1. Boot failsafe mode to either boot from a BE with a known, good root password or reset
the unknown root password by copying and pasting a known, good root password
into the /etc/shadow file. You can't reset the root passwd by using the passwd
command from failsafe mode. At least, I couldn't.
ok boot -F failsafe
You are prompted to mount the BE.
# export TERM
# vi /a/etc/shadow
# reboot
2. Boot this system from media or from the network, import the root pool and mount
the BE (if this a ZFS BE) and carefully remove the unknown root password entry
in the shadow file.
ok boot net -s
# zpool import -R /a rpool
# zfs mount rpool/ROOT/s10BE
# TERM=vt100
# export TERM
# vi /a/etc/shadow
3. Whether you boot failsafe (#1) or boot from media (#2), you should be
able to log back into the CONSOLE as root and reset the root password if you weren't
able to paste in a known, good password.
# passwd -r files root

Root password problem by passwd root

Similar Messages

Maybe you are looking for