04-07-2010
restore data after system crash
Hi all,
I have a server running HP-UX 11i V1 (11.11).
We had a problem with the system disk which cannot boot and the recovery with the CD failed too.
the only solution was to re-install the system on a new disk.
The problem now is to get access to the data which are on other disks, not damaged.
These disks were managed by LVM.
My question is : how can I do to get back my data. I try to restore the volume groups with sam but it is not enough.
Could anybody help me or give me the reference of a HP book explaining how to do ?
Thanks in advance.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello All
We are using Tru64 Unix V4.0D on a Digital Alpha 1200 machine, which by coincidence, crashed last night! Completely out of the Blue!!! After rebooting the system and recovering the databases everything seemed to work ok. It is however, discomforting not to know how or why the system... (2 Replies)
Discussion started by: Ivo
2 Replies
2. Filesystems, Disks and Memory
I need some expert help, and would appreciate any feedback on the following problem:
After power outage the machine didn't allow the login. When we checked it , it looked like both disks were completely empty. Luckily, we have a backup machine, and we can restore the disks.
Has anybody seen... (3 Replies)
Discussion started by: DGoubine
3 Replies
3. HP-UX
Hi,
First of all, thanks for your help. I have downloaded freeBSD to study unix
I'm here again 'cause my HP-UX 10.x has "broken". It raise this error:
----------------------------------------------------
Diagnostic System warning:
= 0x1f005000 is POWERFAILED The diagnostic logging... (1 Reply)
Discussion started by: efrenba
1 Replies
4. UNIX for Dummies Questions & Answers
helo,
suppose u have well build in product system which is build in linux o.s. now due to reason system automatically become crash(software crash),then how do u handle such crash. which is better way to handle such crash.
amit (0 Replies)
Discussion started by: amitpansuria
0 Replies
5. AIX
Hello everyone
I have a partition with the TL 5300-06-01-0000 and try to update to this TL 5300-09-03-0918 but suddenly the update dont work more. I get in to the HMC and I see this code error 888 102 700 0C5
I try to restart my partition but doesnt work.
Theres someone who has this... (9 Replies)
Discussion started by: lo-lp-kl
9 Replies
6. Programming
hello all,
I have developed a server application in C for ulinux kernel 2.6.It works very fine; creating a socket, binding it to a port, listening for incoming sockets and accepting them ,all finish without any error.
But there is a problem regarding application crash.After an intentionally... (1 Reply)
Discussion started by: Sedighzadeh
1 Replies
7. UNIX for Dummies Questions & Answers
Hi all,
First and foremost I would like to mention I am pretty new to Linux.
I have some experience in Windows systems administration but nothing professionally.
Expect some real newbie questions.
For a small company I am trying to install a server so a development environment can be... (1 Reply)
Discussion started by: Crazy Harry
1 Replies
8. AIX
Hello,
Few days ago I created both mksysb and savevg archives of rootvg.
How can I restore this rootvg now because the AIX crashed during some software tests. There is no way to start from hdisk0 because most of the system files are deleted (this includes libc.a).
I tough it will be trivial... (6 Replies)
Discussion started by: +Yan
6 Replies
9. AIX
Hello All,
I am trying to clone an entire AIX virtual machine to a new virtual machine including all partitions and OS.Can anyone help me on the procedure to follow? I am not really sure on how it can be done.Thanks in advance.
Please use CODE tags for sample input, sample output, and for code... (4 Replies)
Discussion started by: gull05
4 Replies
BAD144(8) System Manager's Manual BAD144(8)
NAME
bad144 - read/write DEC standard 144 bad sector information
SYNOPSIS
bad144 disktype disk [ sno [ bad ... ] ]
DESCRIPTION
Bad144 can be used to inspect the information stored on a disk that is used by the disk drivers to implement bad sector forwarding. The
format of the information is specified by DEC standard 144, as follows.
The bad sector information is located in the first 5 even numbered sectors of the last track of the disk pack. There are five identical
copies of the information, described by the dkbad structure. Only the first of these copies is used.
Replacement sectors are allocated starting with the first sector before the bad sector information and working backwards towards the begin-
ning of the disk. A maximum of 126 bad sectors can be supported. The position of the bad sector in the bad sector table determines which
replacement sector it corresponds to.
The bad sector information and replacement sectors are conventionally only accessible through the ``h'' file system partition of the disk.
If that partition is used for a file system, the user is responsible for making sure that it does not overlap the bad sector information or
any replacement sectors.
The bad sector structure is as follows:
struct dkbad {
long bt_csn; /* cartridge serial number */
u_short bt_mbz; /* unused; should be 0 */
u_short bt_flag; /* -1 => alignment cartridge */
struct bt_bad {
u_short bt_cyl; /* cylinder number of bad sector */
u_short bt_trksec; /* track and sector number */
} bt_bad[MAXBAD];
};
Unused slots in the bt_bad array are filled with all bits set, a putatively illegal value. MAXBAD (in <sys/dkbad.h>) may be tuned locally
to reduce the space required to hold the bad-sector file in memory. It may not be greater than 126, which uses the whole disk sector. Bad
sectors past MAXBAD may be included by the formatter, but replacement sectors will not be used until MAXBAD is increased.
Bad144 is invoked by giving a device type (e.g. rk07, rm03, rm05, etc.), and a device name (e.g. hk0, hp1, etc.). It reads the first sec-
tor of the last track of the corresponding disk and prints out the bad sector information. It may also be invoked giving a serial number
for the pack and a list of bad sectors, and will then write the supplied information onto the same location. Note, however, that bad144
does not arrange for the specified sectors to be marked bad in this case. This option should only be used to restore known bad sector
information which was destroyed.
New bad sectors can be added by running the standard DEC formatter in section ``bad.''
SEE ALSO
badsect(8)
BUGS
Not all drivers support bad-sector forwarding on the PDP-11.
It should be possible to both format disks on-line under UNIX and to change the bad sector information, marking new bad sectors, without
running a standalone program.
The bootstrap drivers used to boot the system do not understand bad sectors or handle ECC errors. This means that none of these errors can
occur when reading the file /unix to boot. Sector 0 of the disk drive and the file /boot in the root file system of that drive must also
not have any of these errors in it.
The drivers that write a system core image on disk after a crash do not handle errors; thus the crash dump area must be free of errors and
bad sectors.
3rd Berkeley Distribution BAD144(8)