public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: LarryT <gparted@gmail.com>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] problem with /dev mounted ...
Date: Sat, 17 Feb 2007 22:11:19 +0100	[thread overview]
Message-ID: <45D76F77.8060503@gmail.com> (raw)

Hi all,
I have a problem since last pportage update of my gentoo.
when i run the stage1 and 2 to build my livecd i get an error about /dev 
which is still mounted. I can reboot or umount -fl the device, but the 
problem comes back.
What may i try, please ?

Thx,
Larry

Here is one of the output i get :
GParted mainfiles # nice catalyst -a -f gparted-stage1.spec && nice 
catalyst -a -f gparted-stage2.spec ; sync
Gentoo Catalyst, version 2.0.2
Copyright 2003-2006 The Gentoo Foundation
Distributed under the GNU General Public License version 2

Using default Catalyst configuration file, /etc/catalyst/catalyst.conf
Setting sharedir to config file value "/usr/lib/catalyst"
Setting snapshot_cache to default value "/var/tmp/catalyst/snapshot_cache"
Setting hash_function to default value "crc32"
Setting storedir to config file value "/var/tmp/catalyst"
Setting portdir to default value "/usr/portage"
Setting distdir to config file value "/usr/portage/distfiles"
Setting options to config file value "pkgcache kerncache"
Kernel cache support enabled.
Package cache support enabled.
Envscript support enabled.
Using target: livecd-stage1
Building natively for x86
Source path set to 
/var/tmp/catalyst/builds/default/stage3-i686-2006.tbl.tar.bz2
portage_overlay directories are set to: 
"/mnt/gparted/gparted-001/portage-overlay"
Location of the package cache is 
/var/tmp/catalyst/packages/default/livecd-stage1-i686-0.3.X/
Location of the kerncache is 
/var/tmp/catalyst/kerncache/default/livecd-stage1-i686-0.3.X/
Checking for processes running in chroot and killing them.
umount: /mnt/gparted/catalyst/tmp/default/livecd-stage1-i686-0.3.X/dev: 
device is busy
umount: /mnt/gparted/catalyst/tmp/default/livecd-stage1-i686-0.3.X/dev: 
device is busy
/dev is still mounted; performing auto-bind-umount... !!! catalyst: 
First attempt to unmount: 
/var/tmp/catalyst/tmp/default/livecd-stage1-i686-0.3.X//dev failed.
!!! catalyst: Killing any pids still running in the chroot
Checking for processes running in chroot and killing them.
umount: /mnt/gparted/catalyst/tmp/default/livecd-stage1-i686-0.3.X/dev: 
device is busy
umount: /mnt/gparted/catalyst/tmp/default/livecd-stage1-i686-0.3.X/dev: 
device is busy
!!! catalyst: Couldn't umount bind mount: 
/var/tmp/catalyst/tmp/default/livecd-stage1-i686-0.3.X//dev

!!! catalyst: Couldn't umount one or more bind-mounts; aborting for safety.


Traceback (most recent call last):
 File "modules/generic_stage_target.py", line 541, in mount_safety_check
   self.unbind()
 File "modules/generic_stage_target.py", line 831, in unbind
   raise CatalystError,"Couldn't umount one or more bind-mounts; 
aborting for safety."
CatalystError: <unprintable instance object>
None

!!! catalyst: Unable to auto-unbind /dev


Catalyst aborting....
GParted mainfiles #

-- 
gentoo-catalyst@gentoo.org mailing list



             reply	other threads:[~2007-02-17 21:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-17 21:11 LarryT [this message]
2007-02-18 11:16 ` [gentoo-catalyst] problem with /dev mounted "Andreas Rückert"
2007-02-18 14:04   ` LarryT
2007-02-19  1:12     ` Florent

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45D76F77.8060503@gmail.com \
    --to=gparted@gmail.com \
    --cc=gentoo-catalyst@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox