| 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 |
Hello ,
I have a problem . At a customer's place the LSM volume in a particular
diskgroup cannot start up during system reboot. This diskgroup consists of
10 logical volumes , only 9 volumes can start automatically except for
one. I have to manually start up this particular one.
Does anyone know why this particular one has to be started up manually
?
Any suggestion to correct the problem will be very much appreciated .
Best Regards,
lip
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 750.1 | need more info | NETRIX::"[email protected]" | Thu Feb 06 1997 08:39 | 5 | |
What version are you running? What does 'volinfo -p' and 'volprint -l' show after it fails to startup? [Posted by WWW Notes gateway] | |||||
| 750.2 | MSAM00::YOKEYAN | Fri Feb 07 1997 03:34 | 10 | ||
The customer site is running Digital Unix 3.2C . I did not issue the '
volinfo -p ' and 'volprint -l '. It has been happening everytime , the
customer reboot the system. I will get the 'volinfo -p ' and 'volprint -l'
when the customer reboot the system.
Thank you.
Best Regards,
lip
| |||||
| 750.3 | Volume was in DISABLED state after system reboot | MSAM00::YOKEYAN | Mon Feb 24 1997 05:32 | 23 | |
The volume that cannot startup automatically during reboot is in
DISABLED state.
#volprint -Aht
....
dg rtx_g01 833508890.3328.BINA2.maxisnet.com.my
.....
v vol102 fsgen DISABLED ACTIVE 39590858 SELECT -
p1 p1-02 vol102 DISABLED ACTIVE 12327882 CONCAT - RW
sd rz4106-01 p1-02 0 0 25133556 rz4106 rz4106
What can cause the volume to go into DISABLED state after system reboot
?
Any help and suggestion will be very much appreciated.
Thank You.
Best Regards,
lip
| |||||