degraded RAID array on squeeze

Hi all, one of my servers has experienced degradation in one of its RAID arrays: root@micro ~ # cat /proc/mdstat Personalities : [raid1] md2 : active raid1 sda3[0] 1424121720 blocks super 1.2 [2/1] [U_] md1 : active raid1 sda2[0] sdb2[1] 29295544 blocks super 1.2 [2/2] [UU]

Re: degraded RAID array on squeeze

also sprach Milos Negovanovic milos.negovano...@gmail.com [2011.09.24.1034 +0200]: one of my servers has experienced degradation in one of its RAID arrays: What happened? root@micro ~ # mdadm --add /dev/md2 /dev/sdb3 mdadm: add new device failed for /dev/sdb3 as 2: Invalid argument Does

Re: degraded RAID array on squeeze

Hi Milos, Milos Negovanovic wrote: root@micro ~ # mdadm --add /dev/md2 /dev/sdb3 mdadm: add new device failed for /dev/sdb3 as 2: Invalid argument Try like this instead: mdadm /dev/md2 --add /dev/sdb3 -- Kind Regards AndrewM Andrew McGlashan -- To UNSUBSCRIBE, email to

Re: degraded RAID array on squeeze

On Sat, Sep 24, 2011 at 07:09:57PM +1000, Andrew McGlashan wrote: Hi Milos, Milos Negovanovic wrote: root@micro ~ # mdadm --add /dev/md2 /dev/sdb3 mdadm: add new device failed for /dev/sdb3 as 2: Invalid argument Try like this instead: mdadm /dev/md2 --add /dev/sdb3 root@micro ~ #

Re: degraded RAID array on squeeze

also sprach Andrew McGlashan andrew.mcglas...@affinityvision.com.au [2011.09.24.1109 +0200]: root@micro ~ # mdadm --add /dev/md2 /dev/sdb3 Try like this instead: mdadm /dev/md2 --add /dev/sdb3 That's the same to mdadm. -- martin | http://madduck.net/ | http://two.sentenc.es/ i never go

Re: degraded RAID array on squeeze

On Sat, Sep 24, 2011 at 10:50:17AM +0200, martin f krafft wrote: also sprach Milos Negovanovic milos.negovano...@gmail.com [2011.09.24.1034 +0200]: one of my servers has experienced degradation in one of its RAID arrays: What happened? I was in the middle of system update via aptitude

Re: degraded RAID array on squeeze

Hi, Milos Negovanovic wrote: On Sat, Sep 24, 2011 at 07:09:57PM +1000, Andrew McGlashan wrote: Hi Milos, Milos Negovanovic wrote: root@micro ~ # mdadm --add /dev/md2 /dev/sdb3 mdadm: add new device failed for /dev/sdb3 as 2: Invalid argument Try like this instead: mdadm /dev/md2 --add

Re: degraded RAID array on squeeze

On Sat, Sep 24, 2011 at 10:30:01AM +0100, Milos Negovanovic wrote: On Sat, Sep 24, 2011 at 10:50:17AM +0200, martin f krafft wrote: also sprach Milos Negovanovic milos.negovano...@gmail.com [2011.09.24.1034 +0200]: one of my servers has experienced degradation in one of its RAID arrays:

Re: degraded RAID array on squeeze

also sprach Milos Negovanovic milos.negovano...@gmail.com [2011.09.24.1130 +0200]: I was in the middle of system update via aptitude last week, and it started giving me strange errors that it cant access /dev/sdb3 ... I suspect these were errors from underlaying RAID array. At about the same

Re: degraded RAID array on squeeze

On Sat, Sep 24, 2011 at 07:33:23PM +1000, Andrew McGlashan wrote: Hi, Milos Negovanovic wrote: On Sat, Sep 24, 2011 at 07:09:57PM +1000, Andrew McGlashan wrote: Hi Milos, Milos Negovanovic wrote: root@micro ~ # mdadm --add /dev/md2 /dev/sdb3 mdadm: add new device failed for /dev/sdb3 as

Re: degraded RAID array on squeeze

also sprach Milos Negovanovic milos.negovano...@gmail.com [2011.09.24.1134 +0200]: For details see host's SYSLOG (default: /var/log/syslog). And? Please try to provide all relevant information up front. It takes a lot of effort of others if we have to pull all information out of your nose. --

Re: degraded RAID array on squeeze

also sprach Milos Negovanovic milos.negovano...@gmail.com [2011.09.24.1143 +0200]: Hmmm this line looks suspicious: /dev/sdb3: LABEL=home UUID=4030e91a-c6fa-4640-81eb-654e2ad8c180 TYPE=ext4 Where is blkid getting its info from? fdisk sees /dev/sdb3 as linux RAID partition. From the

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

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

Re: degraded RAID array on squeeze

also sprach Milos Negovanovic milos.negovano...@gmail.com [2011.09.24.1305 +0200]: 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

Re: degraded RAID array on squeeze

On Sat, Sep 24, 2011 at 7:05 AM, Milos Negovanovic milos.negovano...@gmail.com wrote: On Sat, Sep 24, 2011 at 08:30:06PM +1000, Andrew McGlashan wrote: Milos Negovanovic wrote: Where is blkid getting its info from? fdisk sees /dev/sdb3 as linux RAID partition. I expect blkid gets its

Re: degraded RAID array on squeeze

On Sat, Sep 24, 2011 at 01:46:21PM +0200, martin f krafft wrote: also sprach Milos Negovanovic milos.negovano...@gmail.com [2011.09.24.1305 +0200]: 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.

Re: degraded RAID array on squeeze

Milos Negovanovic wrote: Ive dd-ed /dev/sdb3 and that did the trick! I was able to re-add the partition to RAID array. Great, but keep an eye on that disk. I would definitely be wanting to ensure it's integrity ... at the very least make sure you have good backups. I'm sure you know that