I have Sun Fire V440. Boot disks are mirrored. system crashed and it's not coming up. Error message is
Boot disks are mirrored and other disks are ZFS configuration. Please help.
Got an curious issue.
I applied 109147-39 to, oh 15 or so various systems all running Jumpstarted Solaris 8. When I hit the first two V440s, they both failed with Return code 139. All non shell commands segfaulted from then on.
The patch modified mainly the linker libraries and commands.
... (2 Replies)
Hello,
I hope you can help me. I am new to Sun servers and we have a Sun Fire v440 server in which one power supply failed, we are waiting for new one. But now our server is shutting down constantly. Is there any setting with which we can prevent this behaviour? (1 Reply)
Hi all - I have an issue with our (way old) single processor SunFire 280R, running Solaris 9.0.4.
It won't boot even after multiple power cycles. There was a power outage last week end in the computer room, so this might have to do.
In normal boot mode, the screen shows a single line :
... (5 Replies)
First of all it's shut down 60 second after power on and write on console :
SC Alert: Correct SCC not replaced - shutting managed system down!
This is cured by moving out battery from ALOM card.
Now server start to loop during the testing.
That's on the console:
>@(#) Sun Fire V440,Netra... (14 Replies)
Hello,
I am seeing error messages in V440 (OS = solaris 8). I have copied here :
The system does not reboot constantly and it is up for last 67 days. One more interesting thing I found, I see errors start appearing at 4:52AM last until 6am and again start at 16:52am on same day..
I... (5 Replies)
Hi,
I was asked to connect a KVM screen to a Sun Fire V440 last night so I connected it up but no joy and nothing on the KVM screen. I was told that a reboot may fix the problem so connected to the ALOM and rebooted. On the plus side, the KVM screen now works but I lost the ALOM connection.
... (0 Replies)
Hi:
I bougth an used Sun Fire v440, and It have a firmware password. When I turn on the server, it ask for firmware password. (I don 't know what is the correct password). I can access to SC, but when I want to access to OBP, Firmware Password appears again. I remove the battery for two hours,... (1 Reply)
Dear Team,
I need some expert advice to my problem.
We have a Sun Fire v440 in our customer Place. Server is working fine and no hardware deviations are found except one problem that processors generating too much heat. I have verified and found that the room temperature was 26-27 degree.... (5 Replies)
Hi,
I have a SUN Fire V440 server running Solaris 8. One of the 4 disks do not appear when issued the format command. The "ready to remove" LED is not on either.
Metastat command warns that this disk "Needs maintenace". Can I just shutdown and power off the machine and then insert an... (5 Replies)
Hi,
I have a Sun Fire V440 server that fails to boot up correctly. A lot of services are not started and the sytems acts really slow to commands. During boot I can see the following Error:
WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1):
SCSI transport failed: reason 'reset': retrying... (15 Replies)
Discussion started by: oliwei
15 Replies
LEARN ABOUT HPUX
vgchgid
vgchgid(1M)vgchgid(1M)NAME
vgchgid - modify the Volume Group ID (VGID) on a given set of physical devices
SYNOPSIS
PhysicalVolumePath [PhysicalVolumePath] ...
DESCRIPTION
The command is designed to change the LVM Volume Group ID (VGID) on a supplied set of disks. will work with any type of storage, but it is
primarily targeted at disk arrays that are able to create "snapshots" or "clones" of mirrored LUNs. accepts a set of raw physical devices
and ensures that they all belong to the same volume group, before altering the VGID (see section).
The same VGID is set on all the disks and it should be noted that in cases of multi-PV volume groups, all the physical volumes should be
supplied in a single invocation of the command.
Options
recognizes the following options and arguments:
PhysicalVolumePath The raw devices path name of a physical volume.
Background
Some storage subsystems have a feature which allows a user to split off a set of mirror copies of physical storage (termed or just as LVM
splits off logical volumes with the command. As the result of the "split," the split-off devices will have the same VGID as the original
disks. is needed to modify the VGID on the BCV devices. Once the VGID has been altered, the BCV disks can be imported into a new volume
group by using
WARNINGS
Once the VGID has been changed, the original VGID is lost until a disk device is re-mirrored with the original devices. If is used on a
subset of disk devices (for example, two out of four disk devices), the two groups of disk devices would not be able to be imported into
the same volume group since they have different VGIDs on them. The solution is to re-mirror all four of the disk devices and re-run on all
four BCV devices at the same time, and then use to import them into the same new volume group.
If a disk is newly added to an existing volume group and no subsequent LVM operations has been performed to alter the structures (in other
words, operations which perform an automated vgcfgbackup(1M)); then it is possible a subsequent will fail. It will report that the disk
does not belong to the volume group. This may be overcome by performing a structure changing operation on the volume group (for example,
using
It is the system administrator's responsibility to make sure that the devices provided in the command line are all Business Copy volumes of
the existing standard physical volumes and are in the ready state and writable. Mixing the standard and BC volumes in the same volume
group can cause data corruption.
RETURN VALUE
returns the following values:
0 VGID was modified with no error
1 VGID was not modified
EXAMPLES
An example showing how might be used:
1. The system administrator uses the following commands to create the Business Continuity (BCV or BC) copy:
1) For EMC Symmetrix disks, the commands are and
2) For XP disk array, the commands are and
Three BCV disks are created.
2. Change the VGID on the BCV disks.
3. Make a new volume group using the BCV disks.
This step can be skipped as the group file will be created automatically. If the file is manually created it will have different major
and minor numbers (see lvm(7)).
4. Import the BCV disks into the new volume group.
5. Activate the new volume group.
6. Backup the new volume group's LVM data structure.
7. Mount the associated logical volumes.
SEE ALSO vgimport(1M), vgscan(1M), vgcfgbackup(1M).
vgchgid(1M)