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

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

LVM raid0

Started byGokan Atmaca <linux.gokan@gmail.com>
First post2021-05-28 20:30 +0200
Last post2021-05-28 21:50 +0200
Articles 10 — 5 participants

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

Contents

  LVM raid0 Gokan Atmaca <linux.gokan@gmail.com> - 2021-05-28 20:30 +0200
    Re: LVM raid0 john doe <johndoe65534@mail.com> - 2021-05-28 20:40 +0200
      Re: LVM raid0 Gokan Atmaca <linux.gokan@gmail.com> - 2021-05-28 21:00 +0200
        Re: LVM raid0 Gokan Atmaca <linux.gokan@gmail.com> - 2021-05-28 21:20 +0200
        Re: LVM raid0 john doe <johndoe65534@mail.com> - 2021-05-28 21:20 +0200
          Re: LVM raid0 Charles Curley <charlescurley@charlescurley.com> - 2021-05-28 22:50 +0200
        Re: LVM raid0 Tom Dial <tddial@comcast.net> - 2021-05-29 22:10 +0200
          Re: LVM raid0 Gokan Atmaca <linux.gokan@gmail.com> - 2021-05-31 11:30 +0200
    Re: LVM raid0 Gokan Atmaca <linux.gokan@gmail.com> - 2021-05-28 20:40 +0200
      Re: LVM raid0 Reco <recoverym4n@enotuniq.net> - 2021-05-28 21:50 +0200

#235621 — LVM raid0

FromGokan Atmaca <linux.gokan@gmail.com>
Date2021-05-28 20:30 +0200
SubjectLVM raid0
Message-ID<CjPp8-7Xl-7@gated-at.bofh.it>
Hello

I did LVM raid 0. But when reboot the disks come as "inherit".
What would be the reason ?

lvdisplay
  --- Logical volume ---
  LV Path                /dev/vg2t/lv-st0
  LV Name                lv-st0
  VG Name                vg2t
  LV UUID                JOfIdw-8uhQ-OvsF-4Sdp-LMDm-NEVv-UMjFDW
  LV Write Access        read/write
  LV Creation host, time ob, 2021-05-28 10:46:49 -0400
  LV Status              NOT available
  LV Size                1.81 TiB
  Current LE             474482
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto

  --- Logical volume ---
  LV Path                /dev/vg2t/lv_storage14t
  LV Name                lv_storage14t
  VG Name                vg2t
  LV UUID                jHbg36-GKU0-Mked-PbMd-Vnio-IPbE-lpGWD4
  LV Write Access        read/write
  LV Creation host, time ob 2021-05-28 13:41:04 -0400
  LV Status              NOT available
  LV Size                14.50 TiB
  Current LE             3801088
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto


Thanls.




-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀

[toc] | [next] | [standalone]

#235622

Fromjohn doe <johndoe65534@mail.com>
Date2021-05-28 20:40 +0200
Message-ID<CjPyO-80x-11@gated-at.bofh.it>
In reply to#235621
On 5/28/2021 8:31 PM, Gokan Atmaca wrote:
> Additionally I found something like the following in the dmesg logs.
>
> [Fri May 28 14:14:19 2021] x86/cpu: VMX (outside TXT) disabled by BIOS
> [Fri May 28 14:14:20 2021] r8169 0000:06:00.0: unknown chip XID 641
> [Fri May 28 14:14:22 2021] device-mapper: table: 253:2: raid: Failed
> to run raid array
> [Fri May 28 14:14:22 2021] device-mapper: table: 253:2: raid: Failed
> to run raid array
> [Fri May 28 14:15:25 2021] hdaudio hdaudioC0D2: Unable to bind the codec
>
> On Fri, May 28, 2021 at 9:27 PM Gokan Atmaca <linux.gokan@gmail.com> wrote:
>>
>> Hello
>>
>> I did LVM raid 0. But when reboot the disks come as "inherit".
>> What would be the reason ?
>>
>> lvdisplay
>>    --- Logical volume ---
>>    LV Path                /dev/vg2t/lv-st0
>>    LV Name                lv-st0
>>    VG Name                vg2t
>>    LV UUID                JOfIdw-8uhQ-OvsF-4Sdp-LMDm-NEVv-UMjFDW
>>    LV Write Access        read/write
>>    LV Creation host, time ob, 2021-05-28 10:46:49 -0400
>>    LV Status              NOT available
>>    LV Size                1.81 TiB
>>    Current LE             474482
>>    Segments               1
>>    Allocation             inherit
>>    Read ahead sectors     auto
>>
>>    --- Logical volume ---
>>    LV Path                /dev/vg2t/lv_storage14t
>>    LV Name                lv_storage14t
>>    VG Name                vg2t
>>    LV UUID                jHbg36-GKU0-Mked-PbMd-Vnio-IPbE-lpGWD4
>>    LV Write Access        read/write
>>    LV Creation host, time ob 2021-05-28 13:41:04 -0400
>>    LV Status              NOT available
>>    LV Size                14.50 TiB
>>    Current LE             3801088
>>    Segments               1
>>    Allocation             inherit
>>    Read ahead sectors     auto
>>
>>
>> Thanls.
>>
>>
>>
>>
>> --
>> ⢀⣴⠾⠻⢶⣦⠀
>> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
>> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
>> ⠈⠳⣄⠀⠀⠀⠀
>

Is your '/etc/crypttab' file properly populated?

--
John Doe

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

#235625

FromGokan Atmaca <linux.gokan@gmail.com>
Date2021-05-28 21:00 +0200
Message-ID<CjPSa-874-1@gated-at.bofh.it>
In reply to#235622
> Is your '/etc/crypttab' file properly populated?

There is no encrypted volume.


On Fri, May 28, 2021 at 9:37 PM john doe <johndoe65534@mail.com> wrote:
>
> On 5/28/2021 8:31 PM, Gokan Atmaca wrote:
> > Additionally I found something like the following in the dmesg logs.
> >
> > [Fri May 28 14:14:19 2021] x86/cpu: VMX (outside TXT) disabled by BIOS
> > [Fri May 28 14:14:20 2021] r8169 0000:06:00.0: unknown chip XID 641
> > [Fri May 28 14:14:22 2021] device-mapper: table: 253:2: raid: Failed
> > to run raid array
> > [Fri May 28 14:14:22 2021] device-mapper: table: 253:2: raid: Failed
> > to run raid array
> > [Fri May 28 14:15:25 2021] hdaudio hdaudioC0D2: Unable to bind the codec
> >
> > On Fri, May 28, 2021 at 9:27 PM Gokan Atmaca <linux.gokan@gmail.com> wrote:
> >>
> >> Hello
> >>
> >> I did LVM raid 0. But when reboot the disks come as "inherit".
> >> What would be the reason ?
> >>
> >> lvdisplay
> >>    --- Logical volume ---
> >>    LV Path                /dev/vg2t/lv-st0
> >>    LV Name                lv-st0
> >>    VG Name                vg2t
> >>    LV UUID                JOfIdw-8uhQ-OvsF-4Sdp-LMDm-NEVv-UMjFDW
> >>    LV Write Access        read/write
> >>    LV Creation host, time ob, 2021-05-28 10:46:49 -0400
> >>    LV Status              NOT available
> >>    LV Size                1.81 TiB
> >>    Current LE             474482
> >>    Segments               1
> >>    Allocation             inherit
> >>    Read ahead sectors     auto
> >>
> >>    --- Logical volume ---
> >>    LV Path                /dev/vg2t/lv_storage14t
> >>    LV Name                lv_storage14t
> >>    VG Name                vg2t
> >>    LV UUID                jHbg36-GKU0-Mked-PbMd-Vnio-IPbE-lpGWD4
> >>    LV Write Access        read/write
> >>    LV Creation host, time ob 2021-05-28 13:41:04 -0400
> >>    LV Status              NOT available
> >>    LV Size                14.50 TiB
> >>    Current LE             3801088
> >>    Segments               1
> >>    Allocation             inherit
> >>    Read ahead sectors     auto
> >>
> >>
> >> Thanls.
> >>
> >>
> >>
> >>
> >> --
> >> ⢀⣴⠾⠻⢶⣦⠀
> >> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> >> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
> >> ⠈⠳⣄⠀⠀⠀⠀
> >
>
> Is your '/etc/crypttab' file properly populated?
>
> --
> John Doe
>

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

#235630

FromGokan Atmaca <linux.gokan@gmail.com>
Date2021-05-28 21:20 +0200
Message-ID<CjQbx-8sW-25@gated-at.bofh.it>
In reply to#235625
> That file (1) needs to be  populated for it to work at boot! :)

thanks, i didn't know. I will check it. :)

On Fri, May 28, 2021 at 10:10 PM john doe <johndoe65534@mail.com> wrote:
>
> On 5/28/2021 8:58 PM, Gokan Atmaca wrote:
> >> Is your '/etc/crypttab' file properly populated?
> >
> > There is no encrypted volume.
> >
>
> That file (1) needs to be  populated for it to work at boot! :)
>
>
> 1)
> https://wiki.archlinux.org/title/Dm-crypt/System_configuration#Mounting_at_boot_time
>
> --
> John Doe
>

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

#235632

Fromjohn doe <johndoe65534@mail.com>
Date2021-05-28 21:20 +0200
Message-ID<CjQbx-8sW-23@gated-at.bofh.it>
In reply to#235625
On 5/28/2021 8:58 PM, Gokan Atmaca wrote:
>> Is your '/etc/crypttab' file properly populated?
>
> There is no encrypted volume.
>

That file (1) needs to be  populated for it to work at boot! :)


1)
https://wiki.archlinux.org/title/Dm-crypt/System_configuration#Mounting_at_boot_time

--
John Doe

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

#235634

FromCharles Curley <charlescurley@charlescurley.com>
Date2021-05-28 22:50 +0200
Message-ID<CjRAC-JG-11@gated-at.bofh.it>
In reply to#235632
On Fri, 28 May 2021 21:10:03 +0200
john doe <johndoe65534@mail.com> wrote:

> On 5/28/2021 8:58 PM, Gokan Atmaca wrote:
> >> Is your '/etc/crypttab' file properly populated?  
> >
> > There is no encrypted volume.
> >  
> 
> That file (1) needs to be  populated for it to work at boot! :)

No, not if (as M. Atmaca has already stated) there is no encrypted
portion of the system.


> 
> 
> 1)
> https://wiki.archlinux.org/title/Dm-crypt/System_configuration#Mounting_at_boot_time

This article is on DM-crypt, which should be irrelevant to the OP's
situation.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

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

#235660

FromTom Dial <tddial@comcast.net>
Date2021-05-29 22:10 +0200
Message-ID<Ckdrs-5A0-5@gated-at.bofh.it>
In reply to#235625

On 5/28/21 12:58, Gokan Atmaca wrote:
>> Is your '/etc/crypttab' file properly populated?
> 
> There is no encrypted volume.
> 
> 
> On Fri, May 28, 2021 at 9:37 PM john doe <johndoe65534@mail.com> wrote:
>>
>> On 5/28/2021 8:31 PM, Gokan Atmaca wrote:
>>> Additionally I found something like the following in the dmesg logs.
>>>
>>> [Fri May 28 14:14:19 2021] x86/cpu: VMX (outside TXT) disabled by BIOS
>>> [Fri May 28 14:14:20 2021] r8169 0000:06:00.0: unknown chip XID 641
>>> [Fri May 28 14:14:22 2021] device-mapper: table: 253:2: raid: Failed
>>> to run raid array
>>> [Fri May 28 14:14:22 2021] device-mapper: table: 253:2: raid: Failed
>>> to run raid array
>>> [Fri May 28 14:15:25 2021] hdaudio hdaudioC0D2: Unable to bind the codec
>>>
>>> On Fri, May 28, 2021 at 9:27 PM Gokan Atmaca <linux.gokan@gmail.com> wrote:
>>>>
>>>> Hello
>>>>
>>>> I did LVM raid 0. But when reboot the disks come as "inherit".
>>>> What would be the reason ?
>>>>
>>>> lvdisplay
>>>>    --- Logical volume ---
>>>>    LV Path                /dev/vg2t/lv-st0
>>>>    LV Name                lv-st0
>>>>    VG Name                vg2t
>>>>    LV UUID                JOfIdw-8uhQ-OvsF-4Sdp-LMDm-NEVv-UMjFDW
>>>>    LV Write Access        read/write
>>>>    LV Creation host, time ob, 2021-05-28 10:46:49 -0400
>>>>    LV Status              NOT available
>>>>    LV Size                1.81 TiB
>>>>    Current LE             474482
>>>>    Segments               1
>>>>    Allocation             inherit
>>>>    Read ahead sectors     auto
>>>>
>>>>    --- Logical volume ---
>>>>    LV Path                /dev/vg2t/lv_storage14t
>>>>    LV Name                lv_storage14t
>>>>    VG Name                vg2t
>>>>    LV UUID                jHbg36-GKU0-Mked-PbMd-Vnio-IPbE-lpGWD4
>>>>    LV Write Access        read/write
>>>>    LV Creation host, time ob 2021-05-28 13:41:04 -0400
>>>>    LV Status              NOT available
>>>>    LV Size                14.50 TiB
>>>>    Current LE             3801088
>>>>    Segments               1
>>>>    Allocation             inherit
>>>>    Read ahead sectors     auto

Allocation	inherit is the default (inherited from the volume group) if
you did not specify an allocation rule in the lvcreate command that
created the volume group. Based on my experience and existing volume
groups, it also is the default for vgcreate command if nothing else is
specified.

The above also shows "LV Status NOT available". That likely indicates
that the volume group was not activated at boot. That would prevent use
of the logical volumes for anything and probably explain the device
mapper messages shown above.

As Reco suggested in a later reply, it would be helpful to see the
output of both vgdisplay -v and pvdisplay.

It also might be helpful if you could show the exact commands you used
originally to set up the RAID environment.

I realize that may be impossible, but wonder if you defined a raid0
device on top of the LVM logical volumes using external raid management
software. My understanding is that while that might be possible, the
usual way to create raid under LVM is to specify it by type when
creating the logical volume. In this case, for (partly made up) example:

vgcreate vg2t /dev/sda /dev/sdb
lvcreate --type raid0 -name lv-stg --size 16700GiB vg2t

This would result in one logical volume, /dev/vg2t/, split between the
two physical volumes (assumed here to be /dev/sda and /dev/sdb but maybe
different on your system), with total storage of about 16.3 TiB. I guess
that allocation would be first from /dev/sda and, when that is
exhausted, /dev/sdb. Other allocation rules could be specified in the
vgcreate command (and inherited by the logical volume) or the lvcreate
command. With the very different sized disks involved, it is not clear
that would be useful.

Regards,
Tom Dial

>>>>
>>>>
>>>> Thanls.
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> ⢀⣴⠾⠻⢶⣦⠀
>>>> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
>>>> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
>>>> ⠈⠳⣄⠀⠀⠀⠀
>>>
>>
>> Is your '/etc/crypttab' file properly populated?
>>
>> --
>> John Doe
>>

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

#235728

FromGokan Atmaca <linux.gokan@gmail.com>
Date2021-05-31 11:30 +0200
Message-ID<CkMpb-19R-1@gated-at.bofh.it>
In reply to#235660
> vgcreate vg2t /dev/sda /dev/sdb
> lvcreate --type raid0 -name lv-stg --size 16700GiB vg2t


I solved the problem by manually activating it initially.

On Sat, May 29, 2021 at 10:41 PM Tom Dial <tddial@comcast.net> wrote:
>
>
>
> On 5/28/21 12:58, Gokan Atmaca wrote:
> >> Is your '/etc/crypttab' file properly populated?
> >
> > There is no encrypted volume.
> >
> >
> > On Fri, May 28, 2021 at 9:37 PM john doe <johndoe65534@mail.com> wrote:
> >>
> >> On 5/28/2021 8:31 PM, Gokan Atmaca wrote:
> >>> Additionally I found something like the following in the dmesg logs.
> >>>
> >>> [Fri May 28 14:14:19 2021] x86/cpu: VMX (outside TXT) disabled by BIOS
> >>> [Fri May 28 14:14:20 2021] r8169 0000:06:00.0: unknown chip XID 641
> >>> [Fri May 28 14:14:22 2021] device-mapper: table: 253:2: raid: Failed
> >>> to run raid array
> >>> [Fri May 28 14:14:22 2021] device-mapper: table: 253:2: raid: Failed
> >>> to run raid array
> >>> [Fri May 28 14:15:25 2021] hdaudio hdaudioC0D2: Unable to bind the codec
> >>>
> >>> On Fri, May 28, 2021 at 9:27 PM Gokan Atmaca <linux.gokan@gmail.com> wrote:
> >>>>
> >>>> Hello
> >>>>
> >>>> I did LVM raid 0. But when reboot the disks come as "inherit".
> >>>> What would be the reason ?
> >>>>
> >>>> lvdisplay
> >>>>    --- Logical volume ---
> >>>>    LV Path                /dev/vg2t/lv-st0
> >>>>    LV Name                lv-st0
> >>>>    VG Name                vg2t
> >>>>    LV UUID                JOfIdw-8uhQ-OvsF-4Sdp-LMDm-NEVv-UMjFDW
> >>>>    LV Write Access        read/write
> >>>>    LV Creation host, time ob, 2021-05-28 10:46:49 -0400
> >>>>    LV Status              NOT available
> >>>>    LV Size                1.81 TiB
> >>>>    Current LE             474482
> >>>>    Segments               1
> >>>>    Allocation             inherit
> >>>>    Read ahead sectors     auto
> >>>>
> >>>>    --- Logical volume ---
> >>>>    LV Path                /dev/vg2t/lv_storage14t
> >>>>    LV Name                lv_storage14t
> >>>>    VG Name                vg2t
> >>>>    LV UUID                jHbg36-GKU0-Mked-PbMd-Vnio-IPbE-lpGWD4
> >>>>    LV Write Access        read/write
> >>>>    LV Creation host, time ob 2021-05-28 13:41:04 -0400
> >>>>    LV Status              NOT available
> >>>>    LV Size                14.50 TiB
> >>>>    Current LE             3801088
> >>>>    Segments               1
> >>>>    Allocation             inherit
> >>>>    Read ahead sectors     auto
>
> Allocation      inherit is the default (inherited from the volume group) if
> you did not specify an allocation rule in the lvcreate command that
> created the volume group. Based on my experience and existing volume
> groups, it also is the default for vgcreate command if nothing else is
> specified.
>
> The above also shows "LV Status NOT available". That likely indicates
> that the volume group was not activated at boot. That would prevent use
> of the logical volumes for anything and probably explain the device
> mapper messages shown above.
>
> As Reco suggested in a later reply, it would be helpful to see the
> output of both vgdisplay -v and pvdisplay.
>
> It also might be helpful if you could show the exact commands you used
> originally to set up the RAID environment.
>
> I realize that may be impossible, but wonder if you defined a raid0
> device on top of the LVM logical volumes using external raid management
> software. My understanding is that while that might be possible, the
> usual way to create raid under LVM is to specify it by type when
> creating the logical volume. In this case, for (partly made up) example:
>
> vgcreate vg2t /dev/sda /dev/sdb
> lvcreate --type raid0 -name lv-stg --size 16700GiB vg2t
>
> This would result in one logical volume, /dev/vg2t/, split between the
> two physical volumes (assumed here to be /dev/sda and /dev/sdb but maybe
> different on your system), with total storage of about 16.3 TiB. I guess
> that allocation would be first from /dev/sda and, when that is
> exhausted, /dev/sdb. Other allocation rules could be specified in the
> vgcreate command (and inherited by the logical volume) or the lvcreate
> command. With the very different sized disks involved, it is not clear
> that would be useful.
>
> Regards,
> Tom Dial
>
> >>>>
> >>>>
> >>>> Thanls.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> ⢀⣴⠾⠻⢶⣦⠀
> >>>> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> >>>> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
> >>>> ⠈⠳⣄⠀⠀⠀⠀
> >>>
> >>
> >> Is your '/etc/crypttab' file properly populated?
> >>
> >> --
> >> John Doe
> >>

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

#235626

FromGokan Atmaca <linux.gokan@gmail.com>
Date2021-05-28 20:40 +0200
Message-ID<CjPyO-80x-3@gated-at.bofh.it>
In reply to#235621
Additionally I found something like the following in the dmesg logs.

[Fri May 28 14:14:19 2021] x86/cpu: VMX (outside TXT) disabled by BIOS
[Fri May 28 14:14:20 2021] r8169 0000:06:00.0: unknown chip XID 641
[Fri May 28 14:14:22 2021] device-mapper: table: 253:2: raid: Failed
to run raid array
[Fri May 28 14:14:22 2021] device-mapper: table: 253:2: raid: Failed
to run raid array
[Fri May 28 14:15:25 2021] hdaudio hdaudioC0D2: Unable to bind the codec

On Fri, May 28, 2021 at 9:27 PM Gokan Atmaca <linux.gokan@gmail.com> wrote:
>
> Hello
>
> I did LVM raid 0. But when reboot the disks come as "inherit".
> What would be the reason ?
>
> lvdisplay
>   --- Logical volume ---
>   LV Path                /dev/vg2t/lv-st0
>   LV Name                lv-st0
>   VG Name                vg2t
>   LV UUID                JOfIdw-8uhQ-OvsF-4Sdp-LMDm-NEVv-UMjFDW
>   LV Write Access        read/write
>   LV Creation host, time ob, 2021-05-28 10:46:49 -0400
>   LV Status              NOT available
>   LV Size                1.81 TiB
>   Current LE             474482
>   Segments               1
>   Allocation             inherit
>   Read ahead sectors     auto
>
>   --- Logical volume ---
>   LV Path                /dev/vg2t/lv_storage14t
>   LV Name                lv_storage14t
>   VG Name                vg2t
>   LV UUID                jHbg36-GKU0-Mked-PbMd-Vnio-IPbE-lpGWD4
>   LV Write Access        read/write
>   LV Creation host, time ob 2021-05-28 13:41:04 -0400
>   LV Status              NOT available
>   LV Size                14.50 TiB
>   Current LE             3801088
>   Segments               1
>   Allocation             inherit
>   Read ahead sectors     auto
>
>
> Thanls.
>
>
>
>
> --
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
> ⠈⠳⣄⠀⠀⠀⠀

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

#235629

FromReco <recoverym4n@enotuniq.net>
Date2021-05-28 21:50 +0200
Message-ID<CjQEx-b2-1@gated-at.bofh.it>
In reply to#235626
	Hi.

On Fri, May 28, 2021 at 09:31:06PM +0300, Gokan Atmaca wrote:
> Additionally I found something like the following in the dmesg logs.
> 
...
> [Fri May 28 14:14:22 2021] device-mapper: table: 253:2: raid: Failed
> to run raid array
> [Fri May 28 14:14:22 2021] device-mapper: table: 253:2: raid: Failed
> to run raid array

Chances are your initrd lacks dm-raid kernel module. Try adding it to
/etc/initramfs-tools/modules and rebuild your initrd.
Everything else in this dmesg does not relate to the problem.


> > What would be the reason ?

pvdisplay and vgdisplay would be nice.
And "lsmod | grep ^dm" while we're at it.


Oh, and please disgregard that crypttab advice. crypttab is only good
for something if you're using dm-crypt, and most likely you're not.

Reco

[toc] | [prev] | [standalone]

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

csiph-web