05-21-2012
The following should work wether the break-sequence is disabled or not:
- Take an identical system. Make sure you can boot/install it and install the OS to a new disk.
- Take out this disk and connect it to the system you want to revive as the first harddisk. You may have to disconnect your faulty disk and attach it differently to prevent the system to attempt booting from there. Boot the normally from this disk.
- Attach the original disk to the system, mount its file systems and make the necessary changes to make it bootable again.
- Shut down, remove the new disk and put the revived disk into its place again.
This generic approach works on virtually every OS i have encountered so far. If this doesn't work then please tell us why and what exact problem you encountered.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
While playing with my LINUX machine i accidently deleted a file name called /etc/passwd . Even though the system is booted am unable to get the login prompt. Is there any remedy for this problem.:( (5 Replies)
Discussion started by: cyno
5 Replies
2. Solaris
Hi Folks ,
Would be grateful if someone could help me out in one of the question that came to my mind . If the /etc/passwd file has been deleted and the system has been rebooted . Then i dont think that any user would be able to login and the system will be useless . Whats the best solution for... (5 Replies)
Discussion started by: gera_sachin125
5 Replies
3. UNIX for Dummies Questions & Answers
Thanks
AVKlinux (11 Replies)
Discussion started by: avklinux
11 Replies
4. Solaris
i wonder if there is a tool to read the /etc/passwd or /etc/shadow files in order to reset user accounts to the same one.
By moving (restore) all filessytem and data to another same Sun box, none of the users are able to logon to the new box which i didn't change nothing. But if i reset the user... (1 Reply)
Discussion started by: lamoul
1 Replies
5. UNIX for Advanced & Expert Users
I'm trying to make this work, and it half works. Accounts with password hashes matching the old crypt(3) algorithm work just fine:
JUpfW/w6jo6aw
But accounts with longer password hashes preceded by $1$, such as the following, do not work:
$1$iIcbppdP$HDyjJeVMGgJ.ovLsnjtTR.... (0 Replies)
Discussion started by: davidstvz
0 Replies
6. Solaris
Hi Folks,
I have Solaris 10, latest release.
We have passwd aging set in /etc/defalut/passwd.
I have an account that passwd should never expire. Acheived by emptying associated users shadow file entries for passwd aging.
When I reset the users passwd using passwd command, it re enables... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
7. Solaris
Hi , can anyone explain me the difference between /etc/shadow and /etc/default/passwd . As per my knowledge both the files are used for password aging and control parameters. (2 Replies)
Discussion started by: rogerben
2 Replies
8. UNIX for Advanced & Expert Users
hi, all
I just started on new box where I have to diff passwd working perfectly on the very same account/user. I see that shadow was added recently (I'm not a root in there), I see 'x' in passwd. Not sure how it should work, should I change old passwd for one defined in shadow? Or it's fine to... (20 Replies)
Discussion started by: trento17
20 Replies
9. UNIX for Dummies Questions & Answers
Hi
I was accessing our linux test server via putty and By mistake i deleted /etc/passwd file.....
It is allowing me to login..... So could anyone please help me out in this issue....
Please, it is urgent (6 Replies)
Discussion started by: rahul547
6 Replies
10. Solaris
Hi,
I have a Solaris 10 box where password aging is not functioning properly. Using the passwd command with the -l or -u options causes the lastchg field in the /etc/shadow file to be modified. Therefore, if a user's password is set to expire in 90 days and they are 1 day away, all they have... (4 Replies)
Discussion started by: cschar
4 Replies
LEARN ABOUT OSF1
volreattach
volreattach(8) System Manager's Manual volreattach(8)
NAME
volreattach - Reattaches disk drives that have once again become accessible
SYNOPSIS
/usr/sbin/volreattach [-rb] [accessname...]
/usr/sbin/volreattach -c accessname
OPTIONS
The volreattach utility has the following options: Calls the volrecover utility to attempt to recover stale plexes of any volumes on the
failed disk. Performs the reattach operation in the background. Checks whether a reattach is possible. No operation is performed, but the
name of the disk group and disk media name at which the disk can be reattached is displayed.
DESCRIPTION
The volreattach utility attempts to reattach disks using the same disk group and media names they had before detachment.
This operation may be necessary if a disk has a transient failure, or if some disk drivers are unloaded or unloadable when the Logical
Storage Manager is started, causing disks to enter the failed state.
If the problem is fixed, the volreattach command can be used to reattach the disks without plexes being flagged as stale, as long as the
reattach happens before any volumes on the disk are started.
The volreattach command is called from the voldiskadm menus as part of disk recovery.
The volreattach utility tries to find a disk with a disk group and disk ID matching that of the disk(s) being reattached. If the matching
disk is found, the reattach operation may still fail if the original cause (or some other cause) for the disk failure still exists.
EXIT CODES
A zero exit status is returned if it is possible to perform a reattach. Otherwise, non-zero is returned.
SEE ALSO
volintro(8), voldiskadm(8), volrecover(8)
volreattach(8)