Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #166043 > unrolled thread

Debian Testing. Can't boot after apt-get dist-upgrade (28 March 2016)

Started bySergei Petrunin <halfstrik@gmail.com>
First post2016-03-28 23:10 +0200
Last post2016-03-29 11:30 +0200
Articles 4 — 3 participants

Back to article view | Back to linux.debian.user


Contents

  Debian Testing. Can't boot after apt-get dist-upgrade (28 March 2016) Sergei Petrunin <halfstrik@gmail.com> - 2016-03-28 23:10 +0200
    Re: Debian Testing. Can't boot after apt-get dist-upgrade (28 March  2016) Matthew Moore <a91738246@gmail.com> - 2016-03-29 02:40 +0200
      Re: Debian Testing. Can't boot after apt-get dist-upgrade (28 March 2016) Sergei Petrunin <halfstrik@gmail.com> - 2016-03-29 09:40 +0200
        Re: Debian Testing. Can't boot after apt-get dist-upgrade (28 March 2016) Javi Barroso <javibarroso@gmail.com> - 2016-03-29 11:30 +0200

#166043 — Debian Testing. Can't boot after apt-get dist-upgrade (28 March 2016)

FromSergei Petrunin <halfstrik@gmail.com>
Date2016-03-28 23:10 +0200
SubjectDebian Testing. Can't boot after apt-get dist-upgrade (28 March 2016)
Message-ID<rhMAa-4dD-19@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Hello,

Just execute update commands:

sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

After that I no longer be able to boot on 4.4.0 kernel (I using it for some
time already), so I boot now from 4.3.0.

During the system boot I get the following message:

Begin: Running /scripts/local-block ... lvmetad is not active yet
sysinit
  Volume group "strog-vg" not found
  Cannot process volume group strog-vg
done.
 --- several times message like this ---
 --- and then ---
Give up waiting for root device. Common problems:
 - Boot args (cat /proc/cmdline)
  - Check rootdelay=
  - Check root=
- Missing modules
ALERT! /dev/mapper/strog--vg-root does not exist. Dropping to a shell

I'm using LVM, so I assume that you forget to include LVM support into last
kernel release (or related to kernel)
Here is the list of my recently updated packages related to Linux kernel:

2016-03-20 10:48:14 install linux-headers-4.4.0-1-common:amd64 <none>
4.4.6-1
2016-03-20 10:48:36 install linux-kbuild-4.4:amd64 <none> 4.4-4
2016-03-20 10:48:36 install linux-headers-4.4.0-1-amd64:amd64 <none> 4.4.6-1
2016-03-20 10:48:39 install linux-image-4.4.0-1-amd64:amd64 <none> 4.4.6-1

Thanks.

[toc] | [next] | [standalone]


#166047 — Re: Debian Testing. Can't boot after apt-get dist-upgrade (28 March 2016)

FromMatthew Moore <a91738246@gmail.com>
Date2016-03-29 02:40 +0200
SubjectRe: Debian Testing. Can't boot after apt-get dist-upgrade (28 March 2016)
Message-ID<rhPRo-6yl-7@gated-at.bofh.it>
In reply to#166043
On 2016-03-28 11:46:46 PM, Sergei Petrunin wrote:
>During the system boot I get the following message:
>
>Begin: Running /scripts/local-block ... lvmetad is not active yet
>sysinit
>  Volume group "strog-vg" not found
>  Cannot process volume group strog-vg
>done.
> --- several times message like this ---
> --- and then ---
>Give up waiting for root device. Common problems:
> - Boot args (cat /proc/cmdline)
>  - Check rootdelay=
>  - Check root=
>- Missing modules
>ALERT! /dev/mapper/strog--vg-root does not exist. Dropping to a shell

I just finished dealing with something similar. Paradoxically, using the
secondary boot menu (Advanced Options or similar) in Grub booted fine. I
ended up doing a install-grub followed by an update-grub once booted and
it seems to have resolved things.

Hope this helps,
MM

[toc] | [prev] | [next] | [standalone]


#166050

FromSergei Petrunin <halfstrik@gmail.com>
Date2016-03-29 09:40 +0200
Message-ID<rhWpP-2Nj-3@gated-at.bofh.it>
In reply to#166047

[Multipart message — attachments visible in raw view] — view raw

Thanks for response!

Unfortunately, I have to report that doing

sudo install-grub /dev/sda    #/dev/sda is by device for hard-drive with
lvm, may be I need some specific options here?
sudo upgrade-grub

do not cure boot for 4.4.0 kernel - same problem persists, still 4.3.0
kernel (in "Advanced GRUB menu") booting fine.
So I still assume the problem I's not in grub (config for both kernels
4.3.0 and 4.4.0 looks the same)

Can you please spot commands for GRUB that you are using (may be some
specific options other them mine), do you use LVM?

On Tue, Mar 29, 2016 at 3:32 AM, Matthew Moore <a91738246@gmail.com> wrote:

> On 2016-03-28 11:46:46 PM, Sergei Petrunin wrote:
>
>> During the system boot I get the following message:
>>
>> Begin: Running /scripts/local-block ... lvmetad is not active yet
>> sysinit
>>  Volume group "strog-vg" not found
>>  Cannot process volume group strog-vg
>> done.
>> --- several times message like this ---
>> --- and then ---
>> Give up waiting for root device. Common problems:
>> - Boot args (cat /proc/cmdline)
>>  - Check rootdelay=
>>  - Check root=
>> - Missing modules
>> ALERT! /dev/mapper/strog--vg-root does not exist. Dropping to a shell
>>
>
> I just finished dealing with something similar. Paradoxically, using the
> secondary boot menu (Advanced Options or similar) in Grub booted fine. I
> ended up doing a install-grub followed by an update-grub once booted and
> it seems to have resolved things.
>
> Hope this helps,
> MM
>

[toc] | [prev] | [next] | [standalone]


#166053

FromJavi Barroso <javibarroso@gmail.com>
Date2016-03-29 11:30 +0200
Message-ID<rhY8i-3VB-17@gated-at.bofh.it>
In reply to#166050
Hello,

El 29 de marzo de 2016 9:16:09 CEST, Sergei Petrunin <halfstrik@gmail.com> escribió:
>Thanks for response!
>
>Unfortunately, I have to report that doing
>
>sudo install-grub /dev/sda    #/dev/sda is by device for hard-drive
>with
>lvm, may be I need some specific options here?
>sudo upgrade-grub
>
>do not cure boot for 4.4.0 kernel - same problem persists, still 4.3.0
>kernel (in "Advanced GRUB menu") booting fine.
>So I still assume the problem I's not in grub (config for both kernels
>4.3.0 and 4.4.0 looks the same)
>
>Can you please spot commands for GRUB that you are using (may be some
>specific options other them mine), do you use LVM?
>
>On Tue, Mar 29, 2016 at 3:32 AM, Matthew Moore <a91738246@gmail.com>
>wrote:
>
>> On 2016-03-28 11:46:46 PM, Sergei Petrunin wrote:
>>
>>> During the system boot I get the following message:
>>>
>>> Begin: Running /scripts/local-block ... lvmetad is not active yet
>>> sysinit
>>>  Volume group "strog-vg" not found
>>>  Cannot process volume group strog-vg
>>> done.
>>> --- several times message like this ---
>>> --- and then ---
>>> Give up waiting for root device. Common problems:
>>> - Boot args (cat /proc/cmdline)
>>>  - Check rootdelay=
>>>  - Check root=
>>> - Missing modules
>>> ALERT! /dev/mapper/strog--vg-root does not exist. Dropping to a
>shell

Does vgchange -ay and then control-d start the System?

There was a similar problem on sid months ago

Regards

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web