Hi:
I have the same error on dmesg "init: Failed to obtain startpar-bridge
instance: Unknown parameter: INSTANCE"
We have a server with a volume Group (VG) and two logical volumes (LV). About
two 11 days ago it worked fine and we could see information when we run "lvs
-a" or "vgs -a".
But if I
(not related to the issue, but to a hang just after this message
appears, for which people may be googling the startpar-bridge message)
I found this continually as the last suspicious event before hang on an arm64
with an old 14.04 nfsroot system.
After this it would always hang at "nfs: server
Appears in dmesg. System initialization completed without problems
(Ubuntu Utopic 14.10)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1295596
Title:
init: Failed to
** Changed in: upstart (Ubuntu)
Status: Expired = Confirmed
** Changed in: upstart (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
[Expired for upstart (Ubuntu) because there has been no activity for 60
days.]
** Changed in: upstart (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
5 matches
Mail list logo
