More info: LSM won't start after 5.1 upgrade, illegal vminor enc ountered

From: McCracken, Denise (Denise.McCracken@misyshealthcare.com)
Date: Fri Jan 17 2003 - 03:38:33 EST

• Next message: kavithaj: "Reg. Password Check"
• Previous message: McCracken, Denise: "LSM won't start after 5.1 upgrade"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

        I ended up starting over with LSM, but I still have a serious
problem that is looking like a bug. I did a new volsetup, forced it to
create a new configuration and all was well...for a while.

        I encapsulated the root volumes and mirrored them, then set up
another dg and mirrored it. I restored a filesystem and rebooted the box,
twice, in fact, and all was well. After I applied patch kit 3, however, the
machine didn't come back up. At the console, there were some messages like
this:

illegal vminor encountered
filesystem had unexpected consistency
/dev/rvol/rootdg/usrvol (/usr)
/dev/vol/sqdg/sqvol (/sunquest)

        and the system came up in single-user mode.

        We tried booting the old kernel, booting the other side of the
mirror, and running lsmbstartup by hand, and all gave the same result. As I
had tested this on other machines, I can't understand what is going on here.
Because I set up LSM from scratch, I don't think I could have done anything
wrong.

Any ideas? If this could be a hardware problem, I would want to know that
too.

thanks

Denise McCracken
MiSys Healthcare Systems
Denise.McCracken@misyshealthcare.com
(520) 570-2521

• Next message: kavithaj: "Reg. Password Check"
• Previous message: McCracken, Denise: "LSM won't start after 5.1 upgrade"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:04 EDT