Your message dated Mon, 11 Jan 2016 05:26:57 +0000
with message-id <[email protected]>
and subject line Bug#808289: Removed package(s) from unstable
has caused the Debian Bug report #711630,
regarding upstart: Installing upstart results in hang at boot (relates to LVM?)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
711630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711630
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: upstart
Version: 1.6.1-1
Severity: important

Dear Maintainer,

   * What led up to the situation?
        Installed upstart, replacing sysvinit, then rebooted
   * What was the outcome of this action?
        Boot hung after fsck of /root, /boot and /home
   * What outcome did you expect instead?
        Boot as far as a console login at least
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
        Recovered by using init=/bin/bash on kernel cmdline, and manually
        ran sysv startup scripts, to the point where I could run apt-get again
        to restore sysvinit

The boot process stopped after fsck, leaving no console access, and an
essentially unusable system.

By comparing the failed startup with the manual startup from /bin/bash, it
appears that the upstart-driven startup is not enabling LVM early enough, so
that mountall does not complete mounting the LVM-hosted partitions, and then
nothing else happens.

/etc/fstab: (with the noauto,user mounts removed)
# /etc/fstab: static file system information.
#
# <file system>                 <mount point>   <type>  <options>       <dump>  
<pass>
proc                            /proc           proc    defaults        0       0
UUID=f5ebf199-5396-4b0c-a3e5-f35833e99473       /       ext3    
errors=remount-ro 0     1
UUID=92f30fdb-364b-4978-8918-e820ba9c8570       /boot   ext3    defaults        
0       2
UUID=5d778b04-aef3-47ec-965d-b6ccbd6da7fa       /home   ext3    defaults        
0       2
UUID=9791c6cc-84b6-4f47-a613-1ddb1af14a8c       none    swap    sw              
0       0
UUID=E4C010C1C0109BBC           /mnt/windows/e  ntfs    user,exec,utf8  0       0
/dev/disk_group/usrlocal        /usr/local      ext3    defaults        0       
2
/dev/disk_group/music           /mnt/music      ext3    user            0       
2

So, something needs to either run the /etc/init.d/lvm2 script, or in some other
way enable the LVM-managed volumes before mountall can complete. I don't really
know what that should be - is it lvm2, udev (based on rules supplied by lvm2),
mountall itself, or something else?

Or is there something wrong/old with my config?

I'm very happy to provide more information, as I'd very much like to try
upstart.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.6.2 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages upstart depends on:
ii  ifupdown        0.7.43
ii  initscripts     2.88dsf-41
ii  libc6           2.17-3
ii  libdbus-1-3     1.6.10-1
ii  libjson0        0.10-1.2
ii  libnih-dbus1    1.0.3-4.1+b1
ii  libnih1         1.0.3-4.1+b1
ii  libselinux1     2.1.13-2
ii  libudev0        175-7.2
ii  mountall        2.48
ii  sysv-rc         2.88dsf-41
ii  sysvinit-utils  2.88dsf-41
ii  udev            175-7.2

upstart recommends no packages.

Versions of packages upstart suggests:
pn  bash-completion  <none>
ii  graphviz         2.26.3-14
ii  python           2.7.3-5

--- End Message ---
--- Begin Message ---
Version: 1.11-5+rm

Dear submitter,

as the package upstart has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/808289

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to