[prev in list] [next in list] [prev in thread] [next in thread] 

List:       debian-user
Subject:    Re: Debian Testing. Can't boot after apt-get dist-upgrade (28 March 2016)
From:       Javi Barroso <javibarroso () gmail ! com>
Date:       2016-03-29 9:28:00
Message-ID: 66B5593A-939D-4C02-9FD7-B0847CB9277B () gmail ! com
[Download RAW message or body]

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

[prev in list] [next in list] [prev in thread] [next in thread]