Sponsored Content
Full Discussion: HP-UX Disk crash?
Special Forums Hardware Filesystems, Disks and Memory HP-UX Disk crash? Post 302134463 by hoff on Friday 31st of August 2007 03:32:51 AM
Old 08-31-2007
Quote:
Originally Posted by Perderabo
hoff, the physical volume /dev/dsk/c5t6d0 was added to volume group vg01. Possibly other disks might have been added to vg01 as well. Then vg01 is carved up into logical volumes such as /dev/vg01/lvol4. And then file systems were created on the logical volumes. It is possible to ignore LVM and install a file system directly on a physical disk, but few people would do that and the OS installation procedure would make it rather hard to do. So, yes, you need to fsck /dev/vg01/lvol4 and lvol5.
Hi, thx for all help. I think I got a hang of it now and found out what disk that is malfunctioning.
I did an diskinfo on the specified disk /dev/rdsk/c5t6d0 and it shows size: 0 Kbytes, which seems quite odd. All other disks seems fine and gives the correct size.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Disk Crash

We have a Unix system with two hard drives. When we tried to access it this morning it had frozen, and when we rebooted it couldn't find one of the hard drives, and had quite a few bad data blocks on the other. Of course we fear the worst: that the drive is completely gone, but were not sure how... (1 Reply)
Discussion started by: Kgatliffe
1 Replies

2. Filesystems, Disks and Memory

System crash and Disk erasure !!!

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

HP-UX system crash help please!!!

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. Solaris

crash of my machine

I installed solaris 5.9 on a machine SunBlade100 512Mo of RAM and 18Go of hard disc, after the installation I have remark that the machine starts again after 10mn with 15 mn of walk, I downloaded and installed the last patchs on the machine but the poblème persists. someone can help me and tell me... (0 Replies)
Discussion started by: toufik
0 Replies

5. Solaris

crash dump

Can anyone of you help me in enabling crash dump on Solaris 5.5.1 (1 Reply)
Discussion started by: csreenivas
1 Replies

6. Solaris

crash dump

hi , i have machine that is crashed how i can enable core dump file & how can i find it ? :confused: (4 Replies)
Discussion started by: lid-j-one
4 Replies

7. Solaris

scconf crash: registering a Veritas local disk on Sun Cluster (localonly=true)

Hi all, I want to put a local disk on a Sun Cluster node but scconf command explodes :eek: My system: * two node cluster on two VMWare virtual machines * Solaris 10 SunOS 5.10 Generic_141415-05 i86pc i386 i86pc * Sun Cluster 3.2 u2 * Veritas Volume manager The situation... (2 Replies)
Discussion started by: gxmsgx
2 Replies

8. Solaris

crash dumps

I am supporting a server running Solaris 4.3.The server is not having ddicated system administrator and i am requred to do minor maintenance tasks.l From few days, The server is automatically crashing and i just reboot the server. I also do not see anything in /var/adm/messages that can give an... (1 Reply)
Discussion started by: asalman.qazi
1 Replies

9. SCO

Unixware Crash ...

Hi, I need help, one of our servers is down, and all data in that Server are critical: The Scenario: ------------- I have a computer with the next architecture: architecture=IA32 bus_types=PCI2.10,ISA,PnP1.0 hostname=xxx.xxx.xxx (the real name is hidden) hw_provider=Generic AT... (2 Replies)
Discussion started by: danilosevilla
2 Replies

10. Solaris

Boot disk crash with metadb config info

Hello all; We have a SunFire V240 with three disks that were part of a metadb. One of those disks, the boot disk, experienced a horrible death Monday night and we're now trying to recover from that. I know very little about metadb stuff, so please be gentle with me... I'm assuming... (3 Replies)
Discussion started by: Handon
3 Replies
vgcfgrestore(1M)														  vgcfgrestore(1M)

NAME
vgcfgrestore - display or restore LVM volume group configuration from backup file or kernel memory SYNOPSIS
vg_name vg_name old_pv_path] pv_path vg_conf_path vg_conf_path old_pv_path] pv_path pv_path Remarks cannot be performed if the volume group is activated in shared mode. cannot be performed on devices attached to activated volume groups. Prior to restoring a backup configuration to a disk, detach the physi- cal volume from the volume group using the command (see pvchange(1M)), or deactivate the volume group using the command (see vgchange(1M)). will refuse to restore a configuration to a physical volume with a block size different than the block size stored in the configuration backup file for that physical volume. DESCRIPTION
The command restores the LVM configuration data from a default option) or alternate option) configuration backup file, or from kernel mem- ory option), to the physical volume named by pv_path. Or, it displays the configuration data on standard output option). The configuration stored for one physical volume, old_pv_path, can be copied to another physical volume pv_path option). Options and Arguments recognizes the following options and arguments: pv_path The raw (character) device path name of a physical volume that is currently online. If the option is omitted, pv_path must specify a physical volume whose configuration is stored in the configura- tion backup file. Get configuration information from the alternate configuration backup file vg_conf_path. This option is applicable to input arguments belonging to volume groups version 1.0. Forcibly restore the LVM configuration data even if the physical volume has alternate block(s) allocated inside the user data area. This option should be used with extreme caution. User is advised to fix the problem because potential data corruption could occur. Get configuration information from LVM data structures in kernel memory. The volume group containing pv_path must be activated in order to use this option. List the configuration information saved in the specified configuration backup file. Get configuration information from the default configuration backup file: vg_name is the path name of the volume group. base_vg_name is the base name of vg_name. For example, if vg_name is specified as base_vg_name is Restore the configuration information saved for physical volume old_pv_path to physical volume pv_path. This option is useful when a physical volume's name has changed since the configuration backup file was created or updated. old_pv_path must be the path name of a physical volume whose configuration is stored in the configuration backup file. It needs not be currently online. pv_path must be the path name of a physical volume that is currently online. Its configuration needs not be stored in the configuration backup file. Forcibly restore the LVM configuration data even if there is a physical volume mismatch between the kernel and the configuration backup file with the volume group still active. This option should not be used unless the configuration file is absolutely valid and up-to-date. Restoring invalid configuration data can result in data corruption later. If there are alternate physical volume links configured in the system, the following message will appear when total number of physical volumes in the kernel does not match with the configuration backup file due to missing alternate physical volume links: Mismatch between the backup file and the running kernel: Kernel indicates X disks for /dev/vgname; /etc/lvm- conf/vgname indicates Y disks. Cannot proceed with the restoration. Deactivate the Volume Group and try again. In this case, the user is advised to deactivate the volume group first, then use the command to restore configu- ration data when the volume group is unavailable. But if the volume group has to stay available and the user is absolutely sure the configuration file is correct, this option will restore data from the configuration file when the volume group stays available. Provide additional information when invoked together with option. o Additional values displayed for each path: o Disk size in kilobytes o Starting block number (kb) of the user data. o The PVkey (see Note that paths with the same key are links to the same device. Additional values displayed for each volume group: o max_pv o max_pe o max_lv o vg_version o vg_size (only volume groups version 2.0 or higher, see vgcreate(1M)) RETURN VALUE
exits with one of the following values: Successful completion. Failure. Errors occurred during the restore operation. EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified or is null, it defaults to "C" (see lang(5)). If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)). EXAMPLES
Restore the LVM configuration information for the physical volume that was saved in the default file Force to restore the LVM configuration data when volume group is still active: Restore the LVM configuration information to physical volume using alternate configuration file List backup information saved in default configuration file Above command might display the following: Restore LVM configuration information stored for in default configuration file to physical volume Restore LVM configuration information to physical volume using LVM data structures in kernel memory. The volume group containing must be activated: AUTHOR
was developed by HP. SEE ALSO
pvchange(1M), vgcfgbackup(1M), vgchange(1M), intro(7), lvm(7). vgcfgrestore(1M)
All times are GMT -4. The time now is 03:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy