Title: | LSM |
Moderator: | SMURF::SHIDERLY |
Created: | Mon Jan 17 1994 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 803 |
Total number of notes: | 2852 |
Hi all, I'm trying to mirror a system disk under DU 3.2g. I've followed the procedure from note 452.1 as below: 1)volinstall 2)volsetup rz9 3)volencap rz8 4)reboot 5)voldctl add disk rz8 6)voldctl rm disk rz9 7)voldg rmdisk rz9 8)voldisk rm rz9 9)disklabel -re rz9 10)volrootmir rz9 11)voldctl add disk rz9 12)voladvdomencap usr_domain 13)cd /etc/vol/reconfig.d/domain.d/usr_domain.d/command 14) vi rz8g.sh -> replace -U gen by -U fsgen 15) cd / ; init 0 It runs thru without errors, but if I try to boot the system with rz8 removed, I get the following error: "lsm:vold:Error:enable failed:Error in disk group configuration copies No valid disk found containing disk group;transactions are disabled lsm:vold:FATAL Error:Rootdg cannot be imported during boot" Have I missed something? I looks like rz9 doesn't contain lsm disk group configuration. How can I fix the problem? Thanks in advance, Greg.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
775.1 | Again the bug!! See 767.1 | BACHUS::DEVOS | Manu Devos DEC/SI Brussels 856-7539 | Thu Mar 27 1997 07:04 | 1 |
775.2 | Urgent assistance required with root mirroring | AUSSIE::CARMODY | Wed Apr 02 1997 20:13 | 3 | |
Thanks Manu, that fixed the problem. Greg. P.S. Is there a patch for this bug? or is it fixed in DU4.0. | |||||
775.3 | No official patch yet ... | BACHUS::DEVOS | Manu Devos DEC/SI Brussels 856-7539 | Thu Apr 03 1997 10:03 | 19 |
Hi, You can try my own temporary fix described in note 596.1 for V3.2D/E/F/G. But, think that the bug is acting at the time you mirror your system disk, and the patch is not removing the consequence of the bug. I mean this: if you cannot boot from your second disk created some months ago, because you used the buggy vol-reconfig, and if you patch vol-reconfig today, the second disk is still unbootable. You should manually removed the mirror, remove all LSM reference to the second disk, apply the patch and then mirror your system disk again. I think V4.0 is not suffering of this problem. But again, upgrading to V4.x will not solve your problem, you should repeat the encap/mirror process. Regards, Manu. |