Re: LVM raid0

[Gokan Atmaca <linux.gokan@gmail.com>]

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
> ⠈⠳⣄⠀⠀⠀⠀