Sponsored Content
Special Forums Cybersecurity lost root password using (SAM) trusted security Post 6669 by alwayslearningunix on Monday 10th of September 2001 05:26:29 AM
Old 09-10-2001
If you don't have a root session logged on I'm afraid it is a reboot into single user mode - interrupt the boot sequence when it asks you to, search for a boot path, boot from that path (should be obvious which disk to select - look at the SCSI addressing), say yes to interacting with the ISL, at the ISL prompt type : hpux -is, and let it boot into single user mode.

mount -a to mount all filesystems. cd into the /tcb/files/auth/r directory, cp the root file, then edit it and delete the line beginning ":u_pwd". You can then change root passwd in the normal manner.

NOTE - if root passwd has been locked out due to too many incorrect login attempts run "/usr/lbin/modprpw -k root" to unlock, then undergo the above procedure for deleting root tcb entry.

Hope this helps.

Regards.
alwayslearningunix
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Root Password Lost !!!

I've forgotten root password on one of Solaris machines, i searched in forumes to find a similar case but there's no proceudre here to reinintialize root password, cause most of related commands & even single user mode needs root password that i don't have. Any solution would be helpful. --rgrds,... (9 Replies)
Discussion started by: nikk
9 Replies

2. UNIX for Advanced & Expert Users

I lost my password root

Hello ... I lost my password root ! maybe someone can to help me to log in HP_UX, i started the server in " Singel - User" and i changed my password to new password and it`s not working .. what i must to do ??? (4 Replies)
Discussion started by: yanly
4 Replies

3. UNIX for Advanced & Expert Users

Lost Root Password

I have recently become the sys adm guy for our unix systems here for my shop. I have a pretty good understanding of the system, but there is just some stuff that I don't know. Right now one of those things is to recover the password for a unix system. I know that there is a way that you can use... (2 Replies)
Discussion started by: GlockCW
2 Replies

4. Answers to Frequently Asked Questions

Lost root password / Can't login as root

We have quite a few threads about this subject. I have collected some of them and arranged them by the OS which is primarily discussed in the thread. That is because the exact procedure depends on the OS involved. What's more, since you often need to interact with the boot process, the... (0 Replies)
Discussion started by: Perderabo
0 Replies

5. Linux

how to access root priveliges if root password is lost

wish to know how to access root password it root password is forgotten in linux (1 Reply)
Discussion started by: wojtyla
1 Replies

6. UNIX for Dummies Questions & Answers

Root Password Lost

I'm attempting to blank out the root user password on a machine that we have forgotten the password for. I have been using the advice posted on this site to boot from CDROM in single user mode, then mounting the root slice and editing the /etc/shadow file. Each time I save the shadow file and... (1 Reply)
Discussion started by: gonzotonka
1 Replies

7. UNIX for Advanced & Expert Users

Help with Lost Root Password

This is a common question im sure... I bought a RS/6000 Model 240. Aix 4.3.3 loaded. No root password was supplied to me, but I do have the install media (4 disks). I want to drop into maint mode. So I place the cd into the drive, restart the box ( by pressing the power button, since i do not have... (3 Replies)
Discussion started by: JoeJohnSmith
3 Replies

8. SCO

unixware 7.1.4 lost root password

I dont have the cds, what can i do? (2 Replies)
Discussion started by: sopapa
2 Replies

9. SCO

Lost root Password - OpenServer 6

Hi All, It seems that someone in my organization had changed the root password on a SCO Openserver 6 box. Apparently, there are no emergency boot disks. I think they were never created because there is no floppy drive on the machine. I've tried to use the Openserver 6 media installations... (2 Replies)
Discussion started by: gseyforth
2 Replies

10. Solaris

Lost Root Password on VXVM Encapsulated Root Disk

Hi All Hope it's okay to post on this sub-forum, couldn't find a better place I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies
SYSTEMD-FSTAB-GENERATOR(8)				      systemd-fstab-generator					SYSTEMD-FSTAB-GENERATOR(8)

NAME
systemd-fstab-generator - Unit generator for /etc/fstab SYNOPSIS
/lib/systemd/system-generators/systemd-fstab-generator DESCRIPTION
systemd-fstab-generator is a generator that translates /etc/fstab (see fstab(5) for details) into native systemd units early at boot and when configuration of the system manager is reloaded. This will instantiate mount and swap units as necessary. The passno field is treated like a simple boolean, and the ordering information is discarded. However, if the root file system is checked, it is checked before all the other file systems. See systemd.mount(5) and systemd.swap(5) for more information about special /etc/fstab mount options this generator understands. One special topic is handling of symbolic links. Historical init implementations supported symlinks in /etc/fstab. Because mount units will refuse mounts where the target is a symbolic link, this generator will resolve any symlinks as far as possible when processing /etc/fstab in order to enhance backwards compatibility. If a symlink target does not exist at the time that this generator runs, it is assumed that the symlink target is the final target of the mount. systemd-fstab-generator implements systemd.generator(7). KERNEL COMMAND LINE
systemd-fstab-generator understands the following kernel command line parameters: fstab=, rd.fstab= Takes a boolean argument. Defaults to "yes". If "no", causes the generator to ignore any mounts or swap devices configured in /etc/fstab. rd.fstab= is honored only by the initial RAM disk (initrd) while fstab= is honored by both the main system and the initrd. root= Takes the root filesystem to mount in the initrd. root= is honored by the initrd. rootfstype= Takes the root filesystem type that will be passed to the mount command. rootfstype= is honored by the initrd. rootflags= Takes the root filesystem mount options to use. rootflags= is honored by the initrd. mount.usr= Takes the /usr filesystem to be mounted by the initrd. If mount.usrfstype= or mount.usrflags= is set, then mount.usr= will default to the value set in root=. Otherwise, this parameter defaults to the /usr entry found in /etc/fstab on the root filesystem. mount.usr= is honored by the initrd. mount.usrfstype= Takes the /usr filesystem type that will be passed to the mount command. If mount.usr= or mount.usrflags= is set, then mount.usrfstype= will default to the value set in rootfstype=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrfstype= is honored by the initrd. mount.usrflags= Takes the /usr filesystem mount options to use. If mount.usr= or mount.usrfstype= is set, then mount.usrflags= will default to the value set in rootflags=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrflags= is honored by the initrd. systemd.volatile= Controls whether the system shall boot up in volatile mode. Takes a boolean argument or the special value state. If false (the default), this generator makes no changes to the mount tree and the system is booted up in normal mode. If true the generator ensures systemd-volatile-root.service(8) is run as part of the initial RAM disk ("initrd"). This service changes the mount table before transitioning to the host system, so that a volatile memory file system ("tmpfs") is used as root directory, with only /usr mounted into it from the configured root file system, in read-only mode. This way the system operates in fully stateless mode, with all configuration and state reset at boot and lost at shutdown, as /etc and /var will be served from the (initially unpopulated) volatile memory file system. If set to state the generator will leave the root directory mount point unaltered, however will mount a "tmpfs" file system to /var. In this mode the normal system configuration (i.e. the contents of "/etc") is in effect (and may be modified during system runtime), however the system state (i.e. the contents of "/var") is reset at boot and lost at shutdown. Note that in none of these modes the root directory, /etc, /var or any other resources stored in the root file system are physically removed. It's thus safe to boot a system that is normally operated in non-volatile mode temporarily into volatile mode, without losing data. Note that enabling this setting will only work correctly on operating systems that can boot up with only /usr mounted, and are able to automatically populate /etc, and also /var in case of "systemd.volatile=yes". SEE ALSO
systemd(1), fstab(5), systemd.mount(5), systemd.swap(5), systemd-cryptsetup-generator(8), kernel-command-line(7) systemd 237 SYSTEMD-FSTAB-GENERATOR(8)
All times are GMT -4. The time now is 07:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy