Bug#586660: 586660

[Ned Deily]

Seeing the same problem here. Perhaps the key is /boot being on a separate device with / on LVM volume?

# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/dm-0 16513960 3697920 11977184 24% /
tmpfs 126924 0 126924 0% /lib/init/rw
udev 121888 164 121724 1% /dev
tmpfs 126924 0 126924 0% /dev/shm
...
/dev/sda3 264443 48629 202159 20% /boot
# apt-show-versions | grep grub
grub/testing uptodate 0.97-61
grub-common/testing uptodate 1.98-1
grub-doc/testing uptodate 0.97-61
grub-legacy-doc/testing uptodate 0.97-61
grub-pc/testing uptodate 1.98-1
# update-grub
/usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).
# apt-get --reinstall install memtest86+
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
hwtools memtester kernel-patch-badram memtest86
The following packages will be upgraded:
memtest86+
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0B/152kB of archives.
After this operation, 4,096B of additional disk space will be used.
Reading changelogs... Done
Preconfiguring packages ...
Selecting previously deselected package memtest86+.
(Reading database ... 83347 files and directories currently installed.)
Preparing to replace memtest86+ 4.00-2.2 (using .../memtest86+_4.00-2.3_i386.deb) ...
Unpacking replacement memtest86+ ...
/usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).
dpkg: warning: subprocess old post-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
/usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).
dpkg: error processing /var/cache/apt/archives/memtest86+_4.00-2.3_i386.deb (--unpack):
subprocess new post-removal script returned error exit status 1
/usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).
dpkg: error while cleaning up:
subprocess new post-removal script returned error exit status 1
Processing triggers for man-db ...
Errors were encountered while processing:
/var/cache/apt/archives/memtest86+_4.00-2.3_i386.deb
[ Rootkit Hunter version 1.3.6 ]
File updated: searched for 164 files, found 139
E: Sub-process /usr/bin/dpkg returned an error code (1)

--
Ned Deily
n...@acm.org -- []

--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[Thiemo Nagel]

On 06/23/2010 02:52 AM, Ned Deily wrote:
> Seeing the same problem here. Perhaps the key is /boot being on a separate device with / on LVM volume?

Interesting! My setup is similar:

eee:/home/thiemo# df

Filesystem 1K-blocks Used Available Use% Mounted on

/dev/dm-0 150909088 131589756 11653572 92% /
tmpfs 512536 8 512528 1% /lib/init/rw
varrun 512536 224 512312 1% /var/run
varlock 512536 4 512532 1% /var/lock
udev 510616 232 510384 1% /dev
tmpfs 512536 0 512536 0% /dev/shm
/dev/sda6 964500 227156 688348 25% /boot
none 1048576 88 1048488 1% /tmp

Cheers!

Thiemo

[Colin Watson]

reassign 586660 grub-pc 1.98-1
forcemerge 550704 586660
thanks

On Wed, Jun 23, 2010 at 03:47:49AM +0200, Thiemo Nagel wrote:
> On 06/23/2010 02:52 AM, Ned Deily wrote:
>> Seeing the same problem here. Perhaps the key is /boot being on a separate device with / on LVM volume?
>
> Interesting! My setup is similar:
>
> eee:/home/thiemo# df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/dm-0 150909088 131589756 11653572 92% /

Then you're almost certainly running into #550704, which has bitten a
lot of people in testing. Unfortunately other problems have made it
difficult to get a version of grub2 that fixes this into testing in a
timely manner. In the meantime, I suggest upgrading to grub-common and
grub-pc from unstable.

If you want more detailed background, see my blog:

http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/debian/2010-06-04-hacking-on-grub2.html
http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/debian/2010-06-21-grub2-boot-problems.html

Regards,

--
Colin Watson [cjwa...@debian.org]

[Ned Deily]

On Jun 28, 2010, at 5:34 , Colin Watson wrote:
> On Wed, Jun 23, 2010 at 03:47:49AM +0200, Thiemo Nagel wrote:
>> On 06/23/2010 02:52 AM, Ned Deily wrote:
>>> Seeing the same problem here. Perhaps the key is /boot being on a separate device with / on LVM volume?

>> Interesting! My setup is similar: [...]

> Then you're almost certainly running into #550704, which has bitten a
> lot of people in testing. Unfortunately other problems have made it
> difficult to get a version of grub2 that fixes this into testing in a
> timely manner. In the meantime, I suggest upgrading to grub-common and
> grub-pc from unstable.

Upgrading to grub-{common,pc} 1.98+20100617-1 solves the problem for me. Thanks!.

--
Ned Deily
n...@acm.org -- []

[Thiemo Nagel]

On 06/28/2010 02:34 PM, Colin Watson wrote:
> Then you're almost certainly running into #550704, which has bitten a
> lot of people in testing. Unfortunately other problems have made it
> difficult to get a version of grub2 that fixes this into testing in a
> timely manner. In the meantime, I suggest upgrading to grub-common and
> grub-pc from unstable.

Thank you! Installing the sid packages has fixed the problem.

Cheers, Thiemo