On Sat, Mar 7, 2015 at 5:23 PM, Chris Murphy wrote:
> The grub.cfg should have a boot parameter mduuid which makes mdadm in
I'm not sure if grub2-mkconfig will automatically detect and add
mduuid to grub.cfg. You can try it. If not then you could add the
entry to the extra boot params line in /e
/etc/fstab needs the UUID for the filesystem volume; so if you use
blkid, find the line with the filesystem type and label you used when
you created the file system, and use the uuid listed after UUID=
The grub.cfg should have a boot parameter mduuid which makes mdadm in
the initramfs aware that i
Thanks.
On Sat, Mar 7, 2015 at 4:26 PM, Miguel Medalha
wrote:
> Assuming your raid group is /dev/md127, you can run:
>
> ls -l /dev/disk/by-uuid
>
> or
>
> blkid /dev/md127
>
> and use the ID both will show for /dev/md127
>
> ___
> CentOS mailing lis
Assuming your raid group is /dev/md127, you can run:
ls -l /dev/disk/by-uuid
or
blkid /dev/md127
and use the ID both will show for /dev/md127
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
I'm confused about which UUID to use to identify a software RAID in fstab.
lsblk -fs shows:
md127p1 ext4c43af789-82aa-49e9-a8ed-acd52b1cdd58 /y
--- md127 ext4 39c20575-4257-4fd7-b5c8-8a15757e9e8e
--- sdb1 linux_r hostname:0
af77830e-8cfd-9012-62ce-e57105c3bf6c
5 matches
Mail list logo