Hello all.

I'm using mixed unstable/experimental system.
$ uname -aLinux vmamonov 3.5.0-4.dmz.1-liquorix-amd64 #1 ZEN SMP PREEMPT Sun Sep 16 23:41:08 UTC 2012 x86_64 GNU/Linux

Some days ago I had updated grub2 packages to 2.00-7 version.*Now I have such situation:
# update-grubGRUB >= 2.00 has been unpacked but not yet configured.
grub-mkconfig will not work until the upgrade is complete.It should run later as part of configuring the new GRUB packages.
# grub-mkconfig -o /boot/grub/grub.cfgGRUB >= 2.00 has been unpacked but not yet configured.
grub-mkconfig will not work until the upgrade is complete.It should run later as part of configuring the new GRUB packages.
What must I do to resolve problem, except reverting grub2 to 1.99-23 from unstable?

--

Best regards,

Valery Mamonov.

On Thu, Sep 27, 2012 at 11:08 AM, Valery Mamonov
<valerymamonov@gmail.com> wrote:
>
> I'm using mixed unstable/experimental system.
>
> Some days ago I had updated grub2 packages to 2.00-7 version.
> Now I have such situation:
>
> # update-grub
> GRUB >= 2.00 has been unpacked but not yet configured.
> grub-mkconfig will not work until the upgrade is complete.
> It should run later as part of configuring the new GRUB packages.
>
> # grub-mkconfig -o /boot/grub/grub.cfg
> GRUB >= 2.00 has been unpacked but not yet configured.
> grub-mkconfig will not work until the upgrade is complete.
> It should run later as part of configuring the new GRUB packages.
>
> What must I do to resolve problem, except reverting grub2 to 1.99-23 from
> unstable?

Try dpkg's "--configure" or apt-get's "-f".


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/CAOdo=SwnL6F=YfD0O_m+tFo=8G8cZ1AbR8+ChN-N12ZzSn-MsQ@mail.gmail.com

2012/9/27 Tom H <tomh0665@gmail.com>

On Thu, Sep 27, 2012 at 11:08 AM, Valery Mamonov

<valerymamonov@gmail.com> wrote:

>

> I'm using mixed unstable/experimental system.

>

> Some days ago I had updated grub2 packages to 2.00-7 version.

> Now I have such situation:

>

> # update-grub

> GRUB >= 2.00 has been unpacked but not yet configured.

> grub-mkconfig will not work until the upgrade is complete.

> It should run later as part of configuring the new GRUB packages.

>

> # grub-mkconfig -o /boot/grub/grub.cfg

> GRUB >= 2.00 has been unpacked but not yet configured.

> grub-mkconfig will not work until the upgrade is complete.

> It should run later as part of configuring the new GRUB packages.

>

> What must I do to resolve problem, except reverting grub2 to 1.99-23 from

> unstable?



Try dpkg's "--configure" or apt-get's "-f".





--

To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org

with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: http://lists.debian.org/CAOdo=SwnL6F=YfD0O_m+tFo=8G8cZ1AbR8+ChN-N12ZzSn-MsQ@mail.gmail.com





No luck
# dpkg --configure -a# update-grubGRUB >= 2.00 has been unpacked but not yet configured.grub-mkconfig will not work until the upgrade is complete.
It should run later as part of configuring the new GRUB packages.
--

Best regards,

Valery Mamonov.

Am Donnerstag, 27. September 2012 schrieb Valery Mamonov:
> Hello all.

Hi Valery!

> I'm using mixed unstable/experimental system.
>
> $ uname -a
> Linux vmamonov 3.5.0-4.dmz.1-liquorix-amd64 #1 ZEN SMP PREEMPT Sun Sep
> 16 23:41:08 UTC 2012 x86_64 GNU/Linux

With a non-standard kernel. Thats no official Debian kernel.

> Some days ago I had updated grub2 packages to 2.00-7 version.
> Now I have such situation:
>
> # update-grub
> GRUB >= 2.00 has been unpacked but not yet configured.
> grub-mkconfig will not work until the upgrade is complete.
> It should run later as part of configuring the new GRUB packages.
>
> # grub-mkconfig -o /boot/grub/grub.cfg
> GRUB >= 2.00 has been unpacked but not yet configured.
> grub-mkconfig will not work until the upgrade is complete.
> It should run later as part of configuring the new GRUB packages.
>
> What must I do to resolve problem, except reverting grub2 to 1.99-23
> from unstable?

You install software from experimental. You even install a bootloader (!)
package from experimental. But you do not know how to configure a package
or do not know that above error message refers to configuring a package?

I recommend to learn package management basics before using *any* package
from experimental. Heck, I´d even stay away from unstable, before I knew a
bit more about package management. (Although unstable is IMHO quite tame
at the moment.)

What did you expect to gain from installing grub 2.00 anyway?

I omit answer to your question as Tom already gave it.

If you still have problems please post output of the dpkg / apt-get
command you tried.

Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201209272029.29067.Martin@lichtvoll.de">http://lists.debian.org/201209272029.29067.Martin@lichtvoll.de

Am Donnerstag, 27. September 2012 schrieb Valery Mamonov:
> 2012/9/27 Tom H <tomh0665@gmail.com>
>
> > On Thu, Sep 27, 2012 at 11:08 AM, Valery Mamonov
> >
> > <valerymamonov@gmail.com> wrote:
> > > I'm using mixed unstable/experimental system.
> > >
> > > Some days ago I had updated grub2 packages to 2.00-7 version.
> > > Now I have such situation:
> > >
> > > # update-grub
> > > GRUB >= 2.00 has been unpacked but not yet configured.
> > > grub-mkconfig will not work until the upgrade is complete.
> > > It should run later as part of configuring the new GRUB packages.
> > >
> > > # grub-mkconfig -o /boot/grub/grub.cfg
> > > GRUB >= 2.00 has been unpacked but not yet configured.
> > > grub-mkconfig will not work until the upgrade is complete.
> > > It should run later as part of configuring the new GRUB packages.
> > >
> > > What must I do to resolve problem, except reverting grub2 to
> > > 1.99-23 from unstable?
> >
> > Try dpkg's "--configure" or apt-get's "-f".
[…]
> No luck
>
> # dpkg --configure -a
> # update-grub
> GRUB >= 2.00 has been unpacked but not yet configured.
> grub-mkconfig will not work until the upgrade is complete.
> It should run later as part of configuring the new GRUB packages.

Works here:

merkaba:~> apt-get install -t experimental grub-pc
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Die folgenden zusätzlichen Pakete werden installiert:
grub-common grub-pc-bin grub2-common
[…]
grub-pc (2.00-7) wird eingerichtet ...
installation beendet. Keine Fehler aufgetreten.
grub.cfg wird erstellt …
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Linux-Abbild gefunden: /boot/vmlinuz-3.6.0-rc7-tp520
initrd-Abbild gefunden: /boot/initrd.img-3.6.0-rc7-tp520
[…]
Found memtest86+ image: /memtest86+.bin
Found memtest86+ multiboot image: /memtest86+_multiboot.bin
erledigt

merkaba:~> LANG=C update-grub
Generating grub.cfg ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-3.6.0-rc7-tp520
Found initrd image: /boot/initrd.img-3.6.0-rc7-tp520
Found linux image: /boot/vmlinuz-3.6.0-rc6-tp520
Found initrd image: /boot/initrd.img-3.6.0-rc6-tp520
Found linux image: /boot/vmlinuz-3.6.0-rc5-tp520
Found initrd image: /boot/initrd.img-3.6.0-rc5-tp520
Found linux image: /boot/vmlinuz-3.5.2-tp520
Found initrd image: /boot/initrd.img-3.5.2-tp520
Found linux image: /boot/vmlinuz-3.5-trunk-amd64
Found initrd image: /boot/initrd.img-3.5-trunk-amd64
Found linux image: /boot/vmlinuz-3.2.0-3-amd64
Found initrd image: /boot/initrd.img-3.2.0-3-amd64
Found memtest86+ image: /memtest86+.bin
Found memtest86+ multiboot image: /memtest86+_multiboot.bin
done


What does apt-cache policy?

merkaba:~> LANG=C apt-cache policy grub-pc
grub-pc:
Installed: 2.00-7
Candidate: 2.00-7
Version table:
*** 2.00-7 0
200 http://ftp.de.debian.org/debian/ experimental/main amd64
Packages
100 /var/lib/dpkg/status
1.99-23 0
500 http://ftp.de.debian.org/debian/ sid/main amd64 Packages


What does

merkaba:~> dpkg -s grub-pc | grep Status
Status: install ok installed

say on your system?


Does

dpkg-reconfigure grub-pc

work?


Why does your system have a non-standard kernel? Are any other non
standard package repositories active?


My recommendation from the other post still applies .

With some luck you should be able to downgrade to older grub-pc:

apt-get install grub-pc=1.99-23

or something like that. But that might not work in the current state your
grub-pc package is in.


Now, lets test whether this new grub2 boots . (GRML USB-Stick in reach.)

Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201209272040.03242.Martin@lichtvoll.de">http://lists.debian.org/201209272040.03242.Martin@lichtvoll.de

2012/9/27 Martin Steigerwald <Martin@lichtvoll.de>

Am Donnerstag, 27. September 2012 schrieb Valery Mamonov:

> Hello all.



Hi Valery!



> I'm using mixed unstable/experimental system.

>

> $ uname -a

> Linux vmamonov 3.5.0-4.dmz.1-liquorix-amd64 #1 ZEN SMP PREEMPT Sun Sep

> 16 23:41:08 UTC 2012 x86_64 GNU/Linux



With a non-standard kernel. Thats no official Debian kernel.



Yes, I know. Never experienced any problem with it.*

> Some days ago I had updated grub2 packages to 2.00-7 version.

> Now I have such situation:

>

> # update-grub

> GRUB >= 2.00 has been unpacked but not yet configured.

> grub-mkconfig will not work until the upgrade is complete.

> It should run later as part of configuring the new GRUB packages.

>

> # grub-mkconfig -o /boot/grub/grub.cfg

> GRUB >= 2.00 has been unpacked but not yet configured.

> grub-mkconfig will not work until the upgrade is complete.

> It should run later as part of configuring the new GRUB packages.

>

> What must I do to resolve problem, except reverting grub2 to 1.99-23

> from unstable?



You install software from experimental. You even install a bootloader (!)

package from experimental. But you do not know how to configure a package

or do not know that above error message refers to configuring a package?



I recommend to learn package management basics before using *any* package

from experimental. Heck, I´d even stay away from unstable, before I knew a

bit more about package management. (Although unstable is IMHO quite tame

at the moment.)



What did you expect to gain from installing grub 2.00 anyway?



I omit answer to your question as Tom already gave it.



If you still have problems please post output of the dpkg / apt-get

command you tried.



Thanks,

--

Martin 'Helios' Steigerwald - http://www.Lichtvoll.de

GPG: 03B0 0D6C 0040 0710 4AFA *B82F 991B EAAC A599 84C7





--

To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org

with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: http://lists.debian.org/201209272029.29067.Martin@lichtvoll.de




Well, I know about experimental repository and unstability of packages within it. *But my Debian system is working over 3 years, and i've decided all problems i've faced with. Usually I use google for this, but couldn't find anything about my issue, that's because i've decided to ask some help in debian-user.


--

Best regards,

Valery Mamonov.

2012/9/27 Martin Steigerwald <Martin@lichtvoll.de>

Am Donnerstag, 27. September 2012 schrieb Valery Mamonov:

> 2012/9/27 Tom H <tomh0665@gmail.com>

>

> > On Thu, Sep 27, 2012 at 11:08 AM, Valery Mamonov

> >

> > <valerymamonov@gmail.com> wrote:

> > > I'm using mixed unstable/experimental system.

> > >

> > > Some days ago I had updated grub2 packages to 2.00-7 version.

> > > Now I have such situation:

> > >

> > > # update-grub

> > > GRUB >= 2.00 has been unpacked but not yet configured.

> > > grub-mkconfig will not work until the upgrade is complete.

> > > It should run later as part of configuring the new GRUB packages.

> > >

> > > # grub-mkconfig -o /boot/grub/grub.cfg

> > > GRUB >= 2.00 has been unpacked but not yet configured.

> > > grub-mkconfig will not work until the upgrade is complete.

> > > It should run later as part of configuring the new GRUB packages.

> > >

> > > What must I do to resolve problem, except reverting grub2 to

> > > 1.99-23 from unstable?

> >

> > Try dpkg's "--configure" or apt-get's "-f".

[…]

> No luck

>

> # dpkg --configure -a

> # update-grub

> GRUB >= 2.00 has been unpacked but not yet configured.

> grub-mkconfig will not work until the upgrade is complete.

> It should run later as part of configuring the new GRUB packages.



Works here:



merkaba:~> apt-get install -t experimental grub-pc

Paketlisten werden gelesen... Fertig

Abhängigkeitsbaum wird aufgebaut.

Statusinformationen werden eingelesen.... Fertig

Die folgenden zusätzlichen Pakete werden installiert:

Â* grub-common grub-pc-bin grub2-common

[…]

grub-pc (2.00-7) wird eingerichtet ...

installation beendet. Keine Fehler aufgetreten.

grub.cfg wird erstellt …

Found background image: /usr/share/images/desktop-base/desktop-grub.png

Linux-Abbild gefunden: /boot/vmlinuz-3.6.0-rc7-tp520

initrd-Abbild gefunden: /boot/initrd.img-3.6.0-rc7-tp520

[…]

Found memtest86+ image: /memtest86+.bin

Found memtest86+ multiboot image: /memtest86+_multiboot.bin

erledigt



merkaba:~> LANG=C update-grub

Generating grub.cfg ...

Found background image: /usr/share/images/desktop-base/desktop-grub.png

Found linux image: /boot/vmlinuz-3.6.0-rc7-tp520

Found initrd image: /boot/initrd.img-3.6.0-rc7-tp520

Found linux image: /boot/vmlinuz-3.6.0-rc6-tp520

Found initrd image: /boot/initrd.img-3.6.0-rc6-tp520

Found linux image: /boot/vmlinuz-3.6.0-rc5-tp520

Found initrd image: /boot/initrd.img-3.6.0-rc5-tp520

Found linux image: /boot/vmlinuz-3.5.2-tp520

Found initrd image: /boot/initrd.img-3.5.2-tp520

Found linux image: /boot/vmlinuz-3.5-trunk-amd64

Found initrd image: /boot/initrd.img-3.5-trunk-amd64

Found linux image: /boot/vmlinuz-3.2.0-3-amd64

Found initrd image: /boot/initrd.img-3.2.0-3-amd64

Found memtest86+ image: /memtest86+.bin

Found memtest86+ multiboot image: /memtest86+_multiboot.bin

done




What does apt-cache policy?



merkaba:~> LANG=C apt-cache policy grub-pc

grub-pc:

Â* Installed: 2.00-7

Â* Candidate: 2.00-7

Â* Version table:

Â**** 2.00-7 0

Â* Â* Â* Â* 200 http://ftp.de.debian.org/debian/ experimental/main amd64

Packages

Â* Â* Â* Â* 100 /var/lib/dpkg/status

Â* Â* Â*1.99-23 0

Â* Â* Â* Â* 500 http://ftp.de.debian.org/debian/ sid/main amd64 Packages






----------------------------------------------------LANG=C apt-cache policy grub-pcgrub-pc:Â* Installed: 2.00-7Â* Candidate: 2.00-7
Â* Version table:Â**** 2.00-7 0Â* Â* Â* Â*1000 http://mirrors.kernel.org/debian/ experimental/main amd64 PackagesÂ* Â* Â* Â*1000 ftp://ftp.de.debian.org/debian/ experimental/main amd64 Packages
Â* Â* Â* Â*1000 http://mirror.yandex.ru/debian/ experimental/main amd64 PackagesÂ* Â* Â* Â* 100 /var/lib/dpkg/statusÂ* Â* Â*1.99-23 0Â* Â* Â* Â* 990 http://mirrors.kernel.org/debian/ unstable/main amd64 Packages
Â* Â* Â* Â* 990 http://mirror.yandex.ru/debian/ unstable/main amd64 PackagesÂ* Â* Â* Â* 800 http://mirror.yandex.ru/debian/ testing/main amd64 Packages
Â* Â* Â*1.98+20100804-14+squeeze1 0Â* Â* Â* Â* 500 ftp://ftp.de.debian.org/debian/ stable/main amd64 Packages



What does



merkaba:~> dpkg -s grub-pc | grep Status

Status: install ok installed


say on your system?





--------------------------------------dpkg -s grub-pc | grep StatusStatus: install ok installed--------------------------------------

Â*Â*Â*
Does



dpkg-reconfigure grub-pc



work?


LANG=C dpkg-reconfigure grub-pcInstallation finished. No error reported.GRUB >= 2.00 has been unpacked but not yet configured.grub-mkconfig will not work until the upgrade is complete.
It should run later as part of configuring the new GRUB packages.
Â*


Why does your system have a non-standard kernel? Are any other non

standard package repositories active?

Good question Quote from liquorix.net:Â*Liquorix is a distro kernel replacement built using the best configuration and kernel sources for desktop, multimedia, and gaming workloads.
Тhis kernel Â*works for а long time Â*and IÂ*never had any problems .Yes, I have some non-standard repos, but for specific applications, not for grub-pc.Â*Â*

My recommendation from the other post still applies .



With some luck you should be able to downgrade to older grub-pc:



apt-get install grub-pc=1.99-23



That's obvious and I'll try this, thanks.Â*

or something like that. But that might not work in the current state your

grub-pc package is in.





Now, lets test whether this new grub2 boots . (GRML USB-Stick in reach.)


It booted with version 2.00-4 at least.Â*Â*

Thanks,

--

Martin 'Helios' Steigerwald - http://www.Lichtvoll.de

GPG: 03B0 0D6C 0040 0710 4AFA Â*B82F 991B EAAC A599 84C7





--

To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org

with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: http://lists.debian.org/201209272040.03242.Martin@lichtvoll.de





--

Best regards,

Valery Mamonov.

Downgrading grub packages to 1.99-23 from unstable did the trick, as I thought.System boots and works fine.

--

Best regards,

Valery Mamonov.

Am Donnerstag, 27. September 2012 schrieb Valery Mamonov:
> Downgrading grub packages to 1.99-23 from unstable did the trick, as I
> thought.
> System boots and works fine.

Ok, good.

Would be interesting to know what the error was.

In case you spare any free time, I´d look in the shell script update-grub
or grub-mkconfig for the occurence of a part of the error message and look
whats going on there.

--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201209281326.33298.Martin@lichtvoll.de">http://lists.debian.org/201209281326.33298.Martin@lichtvoll.de

2012/9/28 Martin Steigerwald <Martin@lichtvoll.de>

Am Donnerstag, 27. September 2012 schrieb Valery Mamonov:

> Downgrading grub packages to 1.99-23 from unstable did the trick, as I

> thought.

> System boots and works fine.



Ok, good.



Would be interesting to know what the error was.



In case you spare any free time, I´d look in the shell script update-grub

or grub-mkconfig for the occurence of a part of the error message and look

whats going on there.



--

Martin 'Helios' Steigerwald - http://www.Lichtvoll.de

GPG: 03B0 0D6C 0040 0710 4AFA *B82F 991B EAAC A599 84C7





--

To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org

with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: http://lists.debian.org/201209281326.33298.Martin@lichtvoll.de




Thanks, I'll look in scripts.

--

Best regards,

Valery Mamonov.