Veritas Volume Manager 3.2 can't boot!!

ilwxfe

有谁碰过Veritas Volume Manager上面的这个问题么？
１。vxvm:vxconfigd: WARNING: Detaching plex rootvol-01 from volume rootvol
vxvm:vxconfigd: ERROR: System boot disk does not have a valid rootvol plex
２。WARNING: Cannot load drv/rootnex
Can't load the root filesystem
分别是一台主机上的两个RAID1硬盘。
在google,docs.sun.com找了很久，给出的修复结果是：
Try to boot from one of the named disks using the associated boot command
that is listed in the message.
和ok setenv use-nvramrc? true
第一种试了，得出的是第二个结果２。WARNING: Cannot load drv/rootnex
Can't load the root filesystem
用ok setenv use-nvramrc? true　设置，问题依旧。。。。。
不求别的，就想问一下类似问题有没有人碰到过。。

[ 本帖最后由 ilwxfe 于 2006-4-27 16:49 编辑 ]

nus

盘坏了？
一个坏了，尝试从另外一边引导；
两个都坏了，重新安装吧；

盘没有坏，解封装，OS正常后再重新封装。

建议申请现场服务。

ilwxfe

解封装也要在正常启动vxvm呀，boot cdrom -s进入系统能启动vxvm吗？

老邱

下面是VERITAS的Notes。找一下VERITAS support，问题应该不难解决的。

vxvm:vxconfigd: Error: System boot disk does not have a valid rootvol plex.
Details:

This issue is documented in the release notes but there is another case that can produce the same message even if upgrade_start has not been used. This error may be encountered if the root disk is a dynamic multipathing (DMP) device and a reconfiguration reboot is in progress.

Text from release notes:

For a system on which the root file system is contained on a mirrored volume, the upgrade_start script may choose a mirror on a disk other than the normal boot disk to perform the upgrade. If this occurs, the reboot, after running upgrade_finish, may initially fail, claiming that the mirror on the boot disk is stale:

vxvm:vxconfigd: Error: System boot disk does not have a valid rootvol plex.
Please boot from one of the following disks:
Disk: *diskname* Device: *device*
...
vxvm:vxconfigd: Error: System startup failed
The system is down.

The system should be booted from one of the disks named. If, in the eeprom option, use-nvramrc? is set to true, the system can be booted by specifying vex-diskname. (See Chapter 1 in the VERITAS Volume Manager Administrator's Reference Guide for details on booting when boot plexes are stale.).

Alternate cause:

There is another way to encounter this error. If the root disk is a DMP device and a reconfiguration reboot is in progress, this error may occur. It results when the controller number that DMP uses to publish the device changes during the re-configuration.  If the problem occurs, it can be recognized by the fact that the suggested boot device will be the next DMP path no matter which one is used. Booting from path A shows path B as the suggested path. Booting from path B shows path A as the suggested path.

To recover, make a copy of the /etc/system and /etc/vfstab files. Manually unencapsulate the boot volumes by pointing the root, usr, var, and swap entries in the /etc/vfstab to the original partitions and commenting out the two root lines in /etc/system by placing an '*' before them:

* rootdev:/pseudo/vxio:0.0
* set vxio:vol_rootdev_is_volume=1

This will allow the reconfiguration reboot to complete.

Re-encapsulate the root disks by restoring the vfstab and /etc/system files and perform a non-reconfiguration reboot.

ilwxfe

现在我在备份数据，然后再解封装。。看运气吧。谢谢各位了