If you do not run blkid
as root, it cannot actually read any information on the devices and thus must rely on the cache.
Always run blkid
as root if anything about the disks has changed.
Hehe six months later... but I'll try to answer nonetheless.
mdadm --examine --scan
shows you the several RAIDs' uuids which should be consistent with mdadm.conf
For each RAID, all the partitions that make the RAID share this same uuid.
blkid
gives you the filesystem uuids which should be consistent with fstab
So blkid
should show you something like:
/dev/sda3: UUID="dfdcd9c4-2438-1dd7-25ff-b77a9bc2784c" TYPE="linux_raid_member"
/dev/sdb3: UUID="dfdcd9c4-2438-1dd7-25ff-b77a9bc2784c" TYPE="linux_raid_member"
/dev/md2: UUID="73315a4d-2885-45ed-88e9-00c66d449115" TYPE="ext4"
where /dev/sd[ab]3
's uuid is the RAID uuid
You could try to recreate the RAID.
Is /dev/sda3
part of a RAID? (You can check that with mdadm --examine /dev/sda3
)
If it is, then you can do something similar to this:
mdadm --create /dev/md[x] --assume-clean --level=<raidLevel> --verbose --raid-devices=<numberOfDevices> /dev/sd[x]3
Best Answer
You first create the RAID5 device and then use the UUID of it in your mdadm.conf, not the UUID for a filesystem:
So I have a
mdadm.conf
of