Re: degraded RAID array on squeeze
Hi Milos,
Milos Negovanovic wrote:
root@micro ~ # blkid
Edited the following....
/dev/sda3: UUID="9bca8a2b-2283-9bed-c8fe-9f89b0860cb2" LABEL="micro:2" TYPE="linux_raid_member"
/dev/sdb3: LABEL="home" UUID="4030e91a-c6fa-4640-81eb-654e2ad8c180" TYPE="ext4"
root@micro ~ # mdadm --detail --scan
ARRAY /dev/md/2 metadata=1.2 name=micro:2
UUID=9bca8a2b:22839bed:c8fe9f89:b0860cb2
Hmmm this line looks suspicious:
/dev/sdb3: LABEL="home" UUID="4030e91a-c6fa-4640-81eb-654e2ad8c180" TYPE="ext4"
Yes, very suspicious.
How about the output of:
df -Tah
Where is blkid getting its info from? fdisk sees /dev/sdb3 as linux RAID
partition.
I expect blkid gets its details from /dev file system area and partprobe
will update entries there for new or changed disks / partitions.
If /dev/sdb3 is not actually your /home file system [or used otherwise],
then I would be deleting the partition, re-adding it as expected, then
do partprobe and blkid again to check it looks happy. Then hopefully
you can add /dev/sdb3 back into the md2 RAID1 device successfully.
If the disk is failing as it appears from the smartctl message ... then
I also concur that you should look at replacing the disk ASAP.
--
Kind Regards
AndrewM
Andrew McGlashan
Broadband Solutions now including VoIP
Reply to: