On Mon, Aug 22, 2011 at 7:54 PM, Ben Hutchings wrote:
> On Mon, Aug 22, 2011 at 07:44:35PM +0100, Luke Kenneth Casson Leighton wrote:
>> On Mon, Aug 22, 2011 at 7:35 PM, Ben Hutchings wrote:
>> > On Mon, Aug 22, 2011 at 06:56:16PM +0100, Luke Kenneth Casson Leighton
>> > wrote:
>> >> Valentijn,
On Mon, Aug 22, 2011 at 8:02 PM, Ben Hutchings wrote:
> On Mon, Aug 22, 2011 at 07:55:28PM +0100, Luke Kenneth Casson Leighton wrote:
>> On Mon, Aug 22, 2011 at 7:42 PM, Luke Kenneth Casson Leighton
>> wrote:
>> > On Mon, Aug 22, 2011 at 7:21 PM, Valentijn Scholten
>> > wrote:
>> >> Hello Luke,
On Mon, Aug 22, 2011 at 06:56:16PM +0100, Luke Kenneth Casson Leighton wrote:
> Valentijn, this is very important:
>
> please can you keep and make available the initrd that was generated
> by initramfs-tools?
[...]
There isn't one. That is the problem. I don't believe this has
anything to do w
On Mon, Aug 22, 2011 at 07:55:28PM +0100, Luke Kenneth Casson Leighton wrote:
> On Mon, Aug 22, 2011 at 7:42 PM, Luke Kenneth Casson Leighton
> wrote:
> > On Mon, Aug 22, 2011 at 7:21 PM, Valentijn Scholten
> > wrote:
> >> Hello Luke,
> >> Thanks for jumping in.
> >> I only have a /boot/initrd.im
On Mon, Aug 22, 2011 at 7:35 PM, Ben Hutchings wrote:
> On Mon, Aug 22, 2011 at 06:56:16PM +0100, Luke Kenneth Casson Leighton wrote:
>> Valentijn, this is very important:
>>
>> please can you keep and make available the initrd that was generated
>> by initramfs-tools?
> [...]
>
> There isn't one.
On Mon, Aug 22, 2011 at 7:42 PM, Luke Kenneth Casson Leighton
wrote:
> On Mon, Aug 22, 2011 at 7:21 PM, Valentijn Scholten
> wrote:
>> Hello Luke,
>> Thanks for jumping in.
>> I only have a /boot/initrd.img-2.6.32-5-amd64 at the moment.
>> This is the one probably generated (reinstalled) after I
On Mon, Aug 22, 2011 at 07:44:35PM +0100, Luke Kenneth Casson Leighton wrote:
> On Mon, Aug 22, 2011 at 7:35 PM, Ben Hutchings wrote:
> > On Mon, Aug 22, 2011 at 06:56:16PM +0100, Luke Kenneth Casson Leighton
> > wrote:
> >> Valentijn, this is very important:
> >>
> >> please can you keep and mak
On Mon, Aug 22, 2011 at 7:21 PM, Valentijn Scholten
wrote:
> Hello Luke,
> Thanks for jumping in.
> I only have a /boot/initrd.img-2.6.32-5-amd64 at the moment.
> This is the one probably generated (reinstalled) after I reinstalled Squeeze
> on top of the existing problematic install.
ah. _drat
;
initramfs-to...@packages.debian.org
Subject: Re: Bug#636123: linux-image-2.6.39-2-amd64: root filesystem (LVM)
not recognised
Valentijn, this is very important:
please can you keep and make available the initrd that was generated
by initramfs-tools?
the file is going to be /boot/init
Valentijn, this is very important:
please can you keep and make available the initrd that was generated
by initramfs-tools?
the file is going to be /boot/initrd.img-2.6.38-2-{insert_arch_name}
DO NOT attempt to "recover" the system right away (unless you take a
backup of /boot/initrg.img-2.6.38-
Hi Valentin,
Valentijn Scholten wrote:
> [Subject: Bug#636123: similar issue with 2.6.39.2 from backports]
Please keep in mind that these appear as emails in a crowded inbox, so
the subject line can be a good place to put valuable context.
[...]
> I was running a Debian Squeeze with 2.6.38.2 fr
Your message dated Sat, 6 Aug 2011 22:23:04 +0200
with message-id <20110806202304.gb15...@elie.gateway.2wire.net>
and subject line Re: linux-image-2.6.39 not booting due to older package (not
in list of dependencies!)
has caused the Debian Bug report #636123,
regarding linux-image-2.6.39-2
Your message dated Tue, 02 Aug 2011 11:43:28 +0100
with message-id <1312281808.2591.58.camel@deadeye>
and subject line Re: Bug#636123: "fixed" the problem: broken/missing dependency
has caused the Debian Bug report #636123,
regarding linux-image-2.6.39-2-amd64: root filesystem (LVM
Package: linux-2.6
Version: 2.6.39-3
Severity: important
relevant section of /etc/fstab file:
# /etc/fstab: static file system information.
#
#
proc/proc procdefaults0 0
/dev/mapper/pc-root / ext3errors=remount-ro 0 1
14 matches
Mail list logo
