> 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 wrote:
>
>
>
> On 5/28/21 12:58, Gokan Atmaca wrote:
> >> Is your '/etc/crypttab' file properly populat
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 wrote:
>>
>> On 5/28/2021 8:31 PM, Gokan Atmaca wrote:
>>> Additionally I found something like the following in the dmesg
On Fri, 28 May 2021 21:10:03 +0200
john doe 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 alr
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:
> 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 wrote:
>
> On 5/28/2021 8:58 PM, Gokan Atmaca wrote:
> >> Is your '/etc/crypttab' file properly populated?
> >
> > There is no encrypted volume.
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
> Is your '/etc/crypttab' file properly populated?
There is no encrypted volume.
On Fri, May 28, 2021 at 9:37 PM john doe 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
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 :06:00.0: unknown chip XID 641
[Fri May 28 14:14:22 2021] device-mapper: tabl
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 :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
[Fr
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 Namelv-st0
VG Namevg2t
LV UUIDJOfIdw-8uhQ-OvsF-4Sdp-LMDm-NEVv-UMjFD
10 matches
Mail list logo