> Could you please remove rc.log, reboot and post the fresh rc.log?

Done:

rc shutdown logging started at Sun Jun 21 14:40:55 2009

* Stopping local...
 [ ok ]
* Saving random seed...
 [ ok ]
* Deactivating swap devices...
 [ ok ]
* Unmounting network filesystems...
 [ ok ]
* Bringing down interface lo
*   Removing addresses
* Stopping gpm...
 [ ok ]
* Stopping syslog-ng...
 [ ok ]
  Reading all physical volumes.  This may take a while...
  Found volume group "vg" using metadata type lvm2
  5 logical volume(s) in volume group "vg" now active
mount: /dev/sda1 already mounted on /boot
mount: /dev/vg/usr already mounted on /usr
mount: /dev/vg/home already mounted on /home
mount: /dev/vg/opt already mounted on /opt
mount: /dev/vg/var already mounted on /var
mount: /dev/vg/tmp already mounted on /tmp
mount: shm already mounted on /dev/shm
mount: tmpfs already mounted on /tmp
nothing was mounted
* Stopping prebootmisc...
 [ ok ]
* Unmounting loopback devices
* Unmounting filesystems
*   Unmounting /var...
 [ ok ]
*   Unmounting /opt...
 [ ok ]
*   Unmounting /home...
 [ ok ]
*   Unmounting /usr...
 [ ok ]
*   Unmounting /tmp...
 [ ok ]
*   Unmounting /boot...
 [ ok ]
*   lvm uses addon code which is deprecated
*   and may not be available in the future.
* Shutting down the Logical Volume Manager
*   Shutting Down logical volume: /dev/vg/home ...
 [ ok ]
*   Shutting Down logical volume: /dev/vg/opt ...
 [ ok ]
*   Shutting Down logical volume: /dev/vg/tmp ...
 [ ok ]
*   Shutting Down logical volume: /dev/vg/usr ...
 [ ok ]
*   Shutting Down logical volume: /dev/vg/var ...
 [ ok ]
*   Shutting Down volume group: vg ...
 [ ok ]
* Finished Shutting down the Logical Volume Manager
* Stopping udevd...
 [ ok ]

rc shutdown logging stopped at Sun Jun 21 14:41:04 2009


rc boot logging started at Sun Jun 21 08:41:52 2009

* Setting system clock using the hardware clock [Local Time]...
 [ ok ]
* Autoloaded 0 module(s)
*   lvm uses addon code which is deprecated
*   and may not be available in the future.
* Setting up the Logical Volume Manager...
  Locking type 1 initialisation failed.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Volume group "vg" not found
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Volume group "vg" not found
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Volume group "vg" not found
* Failed to setup the LVM
 [ !! ]
* ERROR: lvm failed to start
*   device-mapper uses addon code which is deprecated
*   and may not be available in the future.
* Checking local filesystems ...
/dev/sda2: clean, 6837/65952 files, 41219/263424 blocks
/dev/sda1: clean, 37/12544 files, 9602/50148 blocks
fsck.ext2: No such file or directory while trying to open /dev/vg/usr
/dev/vg/usr:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

fsck.ext2: No such file or directory while trying to open /dev/vg/home
/dev/vg/home:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

fsck.ext2: No such file or directory while trying to open /dev/vg/opt
/dev/vg/opt:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

fsck.ext2: No such file or directory while trying to open /dev/vg/var
/dev/vg/var:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

fsck.ext2: No such file or directory while trying to open /dev/vg/tmp
/dev/vg/tmp:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

* Operational error
 [ !! ]
* Remounting root filesystem read/write...
 [ ok ]
* Updating /etc/mtab...
 [ ok ]
* Mounting local filesystems...
mount: special device /dev/vg/usr does not exist
mount: special device /dev/vg/home does not exist
mount: special device /dev/vg/opt does not exist
mount: special device /dev/vg/var does not exist
mount: special device /dev/vg/tmp does not exist
* Some local filesystem failed to mount
 [ !! ]
* Setting hostname to localhost...
 [ ok ]
* Configuring kernel parameters...
 [ ok ]
  Reading all physical volumes.  This may take a while...
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Volume group "vg" not found
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Volume group "vg" not found
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Volume group "vg" not found
mount: /dev/sda1 already mounted on /boot
mount: shm already mounted on /dev/shm
mount: tmpfs already mounted on /tmp
mount: special device /dev/vg/usr does not exist
mount: special device /dev/vg/home does not exist
mount: special device /dev/vg/opt does not exist
mount: special device /dev/vg/var does not exist
mount: special device /dev/vg/tmp does not exist
mkdir: cannot create directory `/var/log': File exists
* failed to create needed directory /var/log
 [ !! ]
* ERROR: bootmisc failed to start
* Setting terminal encoding [UTF-8]...
 [ ok ]
* Setting console font [default8x16]...
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
 [ !! ]
* ERROR: consolefont failed to start
* Loading key mappings [us]...
cannot open file windowkeys
* Error loading key mappings
 [ !! ]
* ERROR: keymaps failed to start
* Bringing up interface lo
*   127.0.0.1/8...
 [ ok ]
*   Adding routes
*     127.0.0.0/8 via 127.0.0.1...
 [ ok ]
* Activating swap devices...
 [ ok ]
* Initializing random number generator...
 [ ok ]

rc boot logging stopped at Sun Jun 21 14:41:54 2009


rc default logging started at Sun Jun 21 14:41:54 2009

*   lvm uses addon code which is deprecated
*   and may not be available in the future.
* Setting up the Logical Volume Manager...
 [ ok ]
  Reading all physical volumes.  This may take a while...
  Found volume group "vg" using metadata type lvm2
  5 logical volume(s) in volume group "vg" now active
mount: /dev/sda1 already mounted on /boot
mount: shm already mounted on /dev/shm
mount: tmpfs already mounted on /tmp
/dev/mapper/vg-usr on /usr type ext2 (rw,noatime)
/dev/mapper/vg-home on /home type ext2 (rw,noatime)
/dev/mapper/vg-opt on /opt type ext2 (rw,noatime)
/dev/mapper/vg-var on /var type ext2 (rw,noatime)
/dev/mapper/vg-tmp on /tmp type ext2 (rw,noatime)
* Creating user login records...
 [ ok ]
* Cleaning /var/run...
 [ ok ]
* Wiping /tmp directory...
 [ ok ]
* Setting console font [default8x16]...
 [ ok ]
* Starting syslog-ng...
 [ ok ]
* Starting gpm...
 [ ok ]
* Loading key mappings [us]...
 [ ok ]
* Setting keyboard mode [UTF-8]...
 [ ok ]
* Mounting network filesystems...
 [ ok ]
* Starting local...
 [ ok ]

rc default logging stopped at Sun Jun 21 14:41:57 2009


>
> BTW: Do you see messages like this:
>
> *   device-mapper uses addon code which is deprecated
> *   and may not be available in the future.

Yes

>
> Also: What are your versions of bl2 and openrc?

OpenRC 0.4.4, bl-2.0.1



> Did you compare the contents of those packages (esp. openrc) with the
> contents
> of your /etc/runlevels?

I assume you mean /usr/share/openrc/runlevels.

Under /usr/share/openrc/runlevels/boot there are definitely
differences: no device-mapper, no consolefont, no lvm, no root

Under /usr/share/openrc/runlevels/default: no gpm, syslog-ng

Under /usr/share/openrc/runlevels/sysinit: no udev.

No /usr/share/openrc/runlevels/single also no nonetwork

shutdown runlevels the same.


>
> It may also help to wipe /etc/runlevels and copy the contents of
> /usr/share/openrc/runlevels/ into it, then add symlinks for lvm,
> device-mapper
> and (if needed) dmcrypt to the boot runlevel again.

Don't understand. The links in /etc/runlevels and
/usr/share/openrc/runlevels are identical(except for the omissions
noted above) eg bootmisc -> /etc/init.d/bootmisc. Maybe if I add the
missing links to /usr/share/openrc/runlevels that'll fix things...I'll
try that in the meantime.

Thanks for the hints!

mw

Reply via email to