On Sun, 2020-05-24 at 21:14 +0800, Ed Greshko wrote:
On 2020-05-24 19:37, Patrick O'Callaghan wrote:
> Still getting the hang of md. I had it working for several days (2
> disks in RAID1 config) but after a system update and reboot, it
> suddenly shows no data:
>
> ]# lsblk
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
> [...]
> sdd 8:48 0 931.5G 0 disk
> └─md127 9:127 0 931.4G 0 raid1
> └─md127p1 259:0 0 931.4G 0 part
> sde 8:64 0 931.5G 0 disk
> └─md127 9:127 0 931.4G 0 raid1
> └─md127p1 259:0 0 931.4G 0 part
FWIW, I just created a RAID1 on a VM in the "standard" way and I see....
[egreshko@f31k ~]$ sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 50G 0 disk
└─md0 9:0 0 50G 0 raid1
sdb 8:16 0 50G 0 disk
└─md0 9:0 0 50G 0 raid1
sr0 11:0 1 1024M 0 rom
vda 252:0 0 30G 0 disk
├─vda1 252:1 0 1G 0 part /boot
└─vda2 252:2 0 29G 0 part
├─fedora_f31k-root 253:0 0 27G 0 lvm /
└─fedora_f31k-swap 253:1 0 2.1G 0 lvm [SWAP]
and it seems a bit more "sane" than your configuration.
Yours is using LVM, which I wanted to avoid. That may be the root of
the issue (though I've no idea why).
poc