Re: degraded RAID array on squeeze
On Sat, Sep 24, 2011 at 08:30:06PM +1000, Andrew McGlashan wrote:
> 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
root@micro ~ # df -Tah
Filesystem Type Size Used Avail Use% Mounted on
/dev/md1 ext4 28G 587M 26G 3% /
tmpfs tmpfs 12G 8.0K 12G 1% /lib/init/rw
proc proc 0 0 0 - /proc
sysfs sysfs 0 0 0 - /sys
udev tmpfs 12G 180K 12G 1% /dev
tmpfs tmpfs 12G 0 12G 0% /dev/shm
devpts devpts 0 0 0 - /dev/pts
/dev/md2 ext4 1.4T 2.0G 1.3T 1% /var
none cgroup 0 0 0 - /cgroup
>
> >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.
Its not used as /home at all ... Ive tried deleting partition with
parted and re-creating it, setting the raid flag on it ... after
running partprobe and blkid, output is the same, also error when adding
it into RAID array is the same? Anyone know how to change the TYPE of
the partition as seen by the blkid? This is something installer has done
so there must be a way! :)
>
> 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.
Ill try to fix the RAID first, Ive seen crappy drives going into
temporary spasm and everything being OK after ;). I think my problem is
due to mdadm not seeing /dev/sdb3 as valid RAID partition, so Ill try to
fix that first.
Regards
--
Milos Negovanovic
milos.negovanovic@gmail.com
Reply to: