From: Sander <sander@humilis.net>
To: CACook@quantum-sci.com
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Cannot Deinstall a Debian Package
Date: Fri, 6 May 2011 15:21:58 +0200 [thread overview]
Message-ID: <20110506132158.GA20200@attic.humilis.net> (raw)
In-Reply-To: <201105060558.00314.CACook@quantum-sci.com>
CACook@quantum-sci.com wrote (ao):
> On Friday 6 May, 2011 05:20:28 Sander wrote:
> > Can you post the error?
> Do you want to continue [Y/n]?
> Setting up linux-image-2.6.38-2-amd64 (2.6.38-3) ...
> /usr/sbin/grub-probe: error: cannot stat `/dev/root'.
> run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
> Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.38-2-amd64.postinst line 801, <STDIN> line 7.
> dpkg: error processing linux-image-2.6.38-2-amd64 (--configure):
> subprocess installed post-installation script returned error exit status 9
> configured to not write apport reports
> Setting up grub-pc (1.99~rc1-13) ...
> grub-probe: error: cannot stat `/dev/root'.
> Installation finished. No error reported.
> /usr/sbin/grub-probe: error: cannot stat `/dev/root'.
Can you try:
dpkg -i /var/cache/apt/archives/grub-pc_1.99~rc1-13_amd64.deb
apt-get dist-upgrade
If that (second step) doesn't work:
echo "true" > /var/lib/dpkg/info/grub-installer.postinst
apt-get dist-upgrade
grub-install /dev/sda
update-grub
Sander
--
Humilis IT Services and Solutions
http://www.humilis.net
next prev parent reply other threads:[~2011-05-06 13:21 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 19:27 Cannot Deinstall a Debian Package CACook
2011-05-03 21:26 ` Fajar A. Nugraha
2011-05-03 22:20 ` CACook
2011-05-03 23:02 ` Chuck Burns
2011-05-04 0:12 ` CACook
2011-05-04 0:25 ` Chuck Burns
2011-05-04 1:20 ` Chris Samuel
2011-05-04 2:44 ` Fajar A. Nugraha
2011-05-04 9:51 ` Sander
2011-05-05 14:49 ` CACook
2011-05-05 18:09 ` CACook
2011-05-05 19:09 ` cwillu
2011-05-05 19:28 ` cwillu
2011-05-05 19:50 ` CACook
2011-05-05 19:55 ` Chris Mason
2011-05-05 20:32 ` CACook
2011-05-05 20:40 ` cwillu
2011-05-05 21:40 ` CACook
2011-05-05 21:48 ` cwillu
2011-05-05 22:33 ` CACook
2011-05-05 23:06 ` Miguel Garrido
2011-05-06 3:53 ` Helmut Hullen
2011-05-06 6:49 ` Sander
2011-05-05 20:31 ` cwillu
2011-05-05 20:57 ` CACook
2011-05-05 20:59 ` Lars Wirzenius
2011-05-05 21:48 ` CACook
2011-05-05 21:50 ` cwillu
2011-05-05 21:11 ` cwillu
2011-05-06 6:43 ` Sander
2011-05-06 6:33 ` Sander
2011-05-06 12:09 ` CACook
2011-05-06 12:20 ` Sander
2011-05-06 12:57 ` CACook
2011-05-06 13:21 ` Sander [this message]
2011-05-06 13:56 ` CACook
2011-05-06 14:17 ` Sander
2011-05-06 14:53 ` CACook
2011-05-06 14:58 ` Sander
2011-05-06 15:15 ` CACook
2011-05-06 17:09 ` CACook
2011-05-06 20:04 ` CACook
2011-05-06 20:16 ` Tomasz Torcz
2011-05-06 20:56 ` CACook
2011-05-06 21:23 ` Peter Stuge
2011-05-06 20:40 ` Sander
2011-05-06 20:51 ` Peter Stuge
2011-05-06 21:20 ` CACook
2011-05-06 21:28 ` Peter Stuge
2011-05-06 21:32 ` Hugo Mills
2011-05-06 22:17 ` David G Beausang
2011-05-07 1:51 ` C Anthony Risinger
2011-05-07 2:05 ` C Anthony Risinger
[not found] ` <201105062008.26159.CACook@quantum-sci.com>
2011-05-07 6:21 ` C Anthony Risinger
2011-05-07 7:03 ` Helmut Hullen
2011-05-06 13:30 ` Helmut Hullen
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=20110506132158.GA20200@attic.humilis.net \
--to=sander@humilis.net \
--cc=CACook@quantum-sci.com \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).