FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 09-24-2011, 08:34 AM
Milos Negovanovic
 
Default 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]

md0 : active (auto-read-only) raid1 sda1[0] sdb1[1]
11716536 blocks super 1.2 [2/2] [UU]

unused devices: <none>


Following some online tutorials for RAID array recovery Iam trying to
re-insert /dev/sdb3 into /dev/md2:

root@micro ~ # mdadm --add /dev/md2 /dev/sdb3
mdadm: add new device failed for /dev/sdb3 as 2: Invalid argument

As you can see it fails to re-insert the component! Whats suspicious is
that /dev/sdb1 and /dev/sdb2 are just fine in other 2 RAID components,
so I don't think that the /dev/sdb drive has failed!

Any suggestions are welcome!

Regards
--
Milos Negovanovic
milos.negovanovic@gmail.com


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110924083424.GA2602@googlemail.com">http://lists.debian.org/20110924083424.GA2602@googlemail.com
 
Old 09-24-2011, 08:50 AM
martin f krafft
 
Default degraded RAID array on squeeze

also sprach Milos Negovanovic <milos.negovanovic@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 /dev/sdb3 exist?

> As you can see it fails to re-insert the component! Whats
> suspicious is that /dev/sdb1 and /dev/sdb2 are just fine in other
> 2 RAID components, so I don't think that the /dev/sdb drive has
> failed!

Sure, it could have partially failed. You need to know what happened
to be able to figure out what to do now.

--
.'`. martin f. krafft <madduck@d.o> Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduck http://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems

i wish this wish not to be granted!
-- achilles (hofstadter's geb)
 
Old 09-24-2011, 09:09 AM
Andrew McGlashan
 
Default 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 debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4E7D9E65.3030107@affinityvision.com.au">http://lists.debian.org/4E7D9E65.3030107@affinityvision.com.au
 
Old 09-24-2011, 09:23 AM
Milos Negovanovic
 
Default 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 ~ # mdadm /dev/md2 --add /dev/sdb3
mdadm: add new device failed for /dev/sdb3 as 2: Invalid argument

BTW I have tried all the variations of this command I could find online,
and all of them give me this error.

Regards
--
Milos Negovanovic
milos.negovanovic@gmail.com


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110924092340.GB2602@googlemail.com">http://lists.debian.org/20110924092340.GB2602@googlemail.com
 
Old 09-24-2011, 09:26 AM
martin f krafft
 
Default degraded RAID array on squeeze

also sprach Andrew McGlashan <andrew.mcglashan@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 without my dinner. no one ever does, except vegetarians
and people like that."
-- oscar wilde

spamtraps: madduck.bogus@madduck.net
 
Old 09-24-2011, 09:30 AM
Milos Negovanovic
 
Default degraded RAID array on squeeze

On Sat, Sep 24, 2011 at 10:50:17AM +0200, martin f krafft wrote:
> also sprach Milos Negovanovic <milos.negovanovic@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 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
time smartd sent me a mail stating that the ATA error count has jumped
from 0 to 800 or so.

>
> > root@micro ~ # mdadm --add /dev/md2 /dev/sdb3
> > mdadm: add new device failed for /dev/sdb3 as 2: Invalid argument
>
> Does /dev/sdb3 exist?

It exists.

root@micro ~ # cat /proc/partitions
major minor #blocks name

8 0 1465138584 sda
8 1 11717632 sda1
8 2 29296640 sda2
8 3 1424122880 sda3
8 16 1465138584 sdb
8 17 11717632 sdb1
8 18 29296640 sdb2
8 19 1424122880 sdb3
9 0 11716536 md0
9 1 29295544 md1
9 2 1424121720 md2

root@micro ~ # fdisk -l /dev/sdb

Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0002ea6d

Device Boot Start End Blocks Id System
/dev/sdb1 1 1459 11717632 fd Linux raid
autodetect
/dev/sdb2 * 1459 5107 29296640 fd Linux raid
autodetect
/dev/sdb3 5107 182402 1424122880 fd Linux raid
autodetect

root@micro ~ # ls -l /dev/sdb3
brw-rw---- 1 root disk 8, 19 Sep 24 09:21 /dev/sdb3

>
> > As you can see it fails to re-insert the component! Whats
> > suspicious is that /dev/sdb1 and /dev/sdb2 are just fine in other
> > 2 RAID components, so I don't think that the /dev/sdb drive has
> > failed!
>
> Sure, it could have partially failed. You need to know what happened
> to be able to figure out what to do now.

I am in dark regarding that, as I said I was in the middle of system
update when I saw first errors.

Regards
--
Milos Negovanovic
milos.negovanovic@gmail.com


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110924093000.GC2602@googlemail.com">http://lists.debian.org/20110924093000.GC2602@googlemail.com
 
Old 09-24-2011, 09:33 AM
Andrew McGlashan
 
Default 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 /dev/sdb3



root@micro ~ # mdadm /dev/md2 --add /dev/sdb3
mdadm: add new device failed for /dev/sdb3 as 2: Invalid argument

BTW I have tried all the variations of this command I could find online,
and all of them give me this error.


Okay, try the following and show us the output.

partprobe

blkid

mdadm --detail --scan


--
Kind Regards
AndrewM

Andrew McGlashan
Broadband Solutions now including VoIP


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4E7DA3E3.8050904@affinityvision.com.au">http://lists.debian.org/4E7DA3E3.8050904@affinityvision.com.au
 
Old 09-24-2011, 09:34 AM
Milos Negovanovic
 
Default 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.negovanovic@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 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
> time smartd sent me a mail stating that the ATA error count has jumped
> from 0 to 800 or so.

I managed to find that smartd email:

This email was generated by the smartd daemon running on:

host name: micro
DNS domain: milosn.net
NIS domain: (none)

The following warning/error was logged by the smartd daemon:

Device: /dev/sdb [SAT], ATA error count increased from 0 to 894

For details see host's SYSLOG (default: /var/log/syslog).

You can also use the smartctl utility for further investigation.
No additional email messages about this problem will be sent.

Regards
--
Milos Negovanovic
milos.negovanovic@gmail.com


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110924093451.GD2602@googlemail.com">http://lists.debian.org/20110924093451.GD2602@googlemail.com
 
Old 09-24-2011, 09:37 AM
martin f krafft
 
Default degraded RAID array on squeeze

also sprach Milos Negovanovic <milos.negovanovic@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
> time smartd sent me a mail stating that the ATA error count has jumped
> from 0 to 800 or so.

You need to give the exact errors. But it sounds like your disk is
about to die. I'd get a new one ASAP.

--
.'`. martin f. krafft <madduck@d.o> Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduck http://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems

"in the figure of the president, george w. bush, the incompetence,
stupidity, and sheer inhumanity that characterize so much of
america's money-mad corporate elite find their quintessentially
repulsive expression."
-- journalist, aftermath of katrina
 
Old 09-24-2011, 09:43 AM
Milos Negovanovic
 
Default 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 2: Invalid argument
> >>Try like this instead:
> >>
> >>mdadm /dev/md2 --add /dev/sdb3
> >>
> >
> >root@micro ~ # mdadm /dev/md2 --add /dev/sdb3
> >mdadm: add new device failed for /dev/sdb3 as 2: Invalid argument
> >
> >BTW I have tried all the variations of this command I could find online,
> >and all of them give me this error.
>
> Okay, try the following and show us the output.
>
> partprobe
>
> blkid
>
> mdadm --detail --scan
>

root@micro ~ # partprobe

root@micro ~ # blkid
/dev/sdb1: UUID="ea2de79b-ee83-1c72-35ee-44eb048206bc" LABEL="micro:0" TYPE="linux_raid_member"
/dev/sdb2: UUID="de73322a-76df-fa34-7b38-44b155266292" LABEL="micro:1" TYPE="linux_raid_member"
/dev/sda1: UUID="ea2de79b-ee83-1c72-35ee-44eb048206bc" LABEL="micro:0" TYPE="linux_raid_member"
/dev/sda2: UUID="de73322a-76df-fa34-7b38-44b155266292" LABEL="micro:1" TYPE="linux_raid_member"
/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"
/dev/md0: UUID="16453ab8-e70a-48f3-a435-649505897d2f" TYPE="swap"
/dev/md1: UUID="3810bb4b-12be-4e7a-9818-8503f90aa96f" TYPE="ext4"
/dev/md2: UUID="3c69773f-5595-4e29-9c8e-66bfbdfd4422" TYPE="ext4"

root@micro ~ # mdadm --detail --scan
ARRAY /dev/md/0 metadata=1.2 name=micro:0
UUID=ea2de79b:ee831c72:35ee44eb:048206bc
ARRAY /dev/md/1 metadata=1.2 name=micro:1
UUID=de73322a:76dffa34:7b3844b1:55266292
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"

Where is blkid getting its info from? fdisk sees /dev/sdb3 as linux RAID
partition.

Regards
--
Milos Negovanovic
milos.negovanovic@gmail.com


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110924094318.GE2602@googlemail.com">http://lists.debian.org/20110924094318.GE2602@googlemail.com
 

Thread Tools




All times are GMT. The time now is 06:20 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org