Topic: DegradedArray event - Notifications

[davidpfox]

Hi All ....... I had my first raid controller issue across the weekend where I received approx 3 separate email notifications 5min apart. From what I read through doco, I would of expected to receive a "Everything is now ok" email if the raid controller resolved itself, but also why am I not still receiving the notifications? Does it only get 'tripped' when it gets to that part of the HDD?

Thanks

[Stefano]

hi

do you really have a raid controller? or are you using SME's sw raid?

please post the result of

Code: [Select]

cat /proc/mdstat

thank you

[davidpfox]

SME SW

[Stefano]

and the output?

[davidpfox]

lol ..... sorry ....

Personalities : [raid1]
md2 : active raid1 sdb2[1]
      156183808 blocks [2/1] [_U]
     
md1 : active raid1 sda1[0] sdb1[1]
      104320 blocks [2/2] [UU]
     
unused devices: <none>

and the output?

[Stefano]

your sdda disk is gone... change it asap

[davidpfox]

your sdda disk is gone... change it asap

Hi Stefano ...... are you able to give me a '101' lesson on all sdda, mdda etc. that are used or should be used?

[Stefano]

mmmhh... first of alll it's 'sda', my bad

what you ask is a bit complex, so you should learn something about linux hd's naming rules (search with google)

then you should read this wiki page..

if you need to identify your sda disk (assuming you have 2 identical hds), you can recover s/n with

Code: [Select]

smartctl -i /dev/sda
smartctl -i /dev/sdb

hth

[davidpfox]

I am just reviewing that wiki article now - thanks for the heads up.

So I can see that sdb is the troublesome drive, and form this wiki article it tells me to go ahead with a 'smartctl -i /dev/sdb' command. When I do this I get a 'Smartctl: please specify device type with the -d option'.

Looks like I need to get to know smartctl a bit more.

Thanks again for your help!!

[sekt]

try this link http://wiki.contribs.org/Raid

[Stefano]

So I can see that sdb is the troublesome drive,

biiiiiiip.. wrong guess.. your faulty hd is sda

and form this wiki article it tells me to go ahead with a 'smartctl -i /dev/sdb' command. When I do this I get a 'Smartctl: please specify device type with the -d option'.

strange.. could you please describe a little your hw?
- what kind of hd are you using?
- mb?
- chipset/controller?

please take the time to make a backup of your data..

[davidpfox]

Thanks Stefano ..... I will be onsite with this client tomorrow (9 hours from now) so will be able to get some specs then - unless you know of anything I can use to pull this information from command-line etc.?

I was about to reply to all posts after some digging around - see below

*********

After doing a lot of reading of documentation and others experiences, I ended up executing 'mdadm --add /dev/md2 /dev/sda2'. The rebuild looks pretty good as I can now run 'cat /proc/mdstat':

Personalities : [raid1]
md2 : active raid1 sda2[0] sdb2[1]
      156183808 blocks [2/2] [UU]
     
md1 : active raid1 sda1[0] sdb1[1]
      104320 blocks [2/2] [UU]
     
unused devices: <none>

Also, when I access Server Console and check 'Manage disk redundancy', I see that all is in working order.

So it looks like the rebuild was successfull and my sda2 is back online. Should I be looking at my sdb drive for errors?

[Stefano]

ok.. so your raid arrays are ok..

I would check /var/log/messages for errors to discover why sda was thrown out of the array..

about CLI commands to investigate your hw configuration:
- lspci (eventually with -v flag)
- dmidecode

HTH

[davidpfox]

ok.. so your raid arrays are ok..

I would check /var/log/messages for errors to discover why sda was thrown out of the array..

Feel like reviewing these with me?

Oct 17 09:58:26 sme-server kernel: SCSI device sda: 312579695 512-byte hdwr sectors (160041 MB)
Oct 17 09:58:26 sme-server kernel: SCSI device sda: drive cache: write back
Oct 17 09:58:26 sme-server kernel: SCSI device sda: 312579695 512-byte hdwr sectors (160041 MB)
Oct 17 09:58:26 sme-server kernel: SCSI device sda: drive cache: write back
Oct 17 09:58:26 sme-server kernel:  sda: sda1 sda2
Oct 17 09:58:26 sme-server kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Oct 17 09:58:26 sme-server kernel: md: bind<sda1>
Oct 17 09:58:26 sme-server kernel: md: bind<sda2>
Oct 17 09:58:26 sme-server kernel: md: kicking non-fresh sda2 from array!
Oct 17 09:58:26 sme-server kernel: md: unbind<sda2>
Oct 17 09:58:26 sme-server kernel: md: export_rdev(sda2)
Oct 17 09:58:27 sme-server kernel: md: could not bd_claim sda1.
Oct 17 09:58:27 sme-server kernel: md: could not bd_claim sda2.
Oct 17 09:58:27 sme-server kernel: md: considering sda2 ...
Oct 17 09:58:27 sme-server kernel: md:  adding sda2 ...
Oct 17 09:58:27 sme-server kernel: md: md2 already running, cannot run sda2
Oct 17 09:58:27 sme-server kernel: md: export_rdev(sda2)

about CLI commands to investigate your hw configuration:
- lspci (eventually with -v flag)
- dmidecode

lspci
00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)
00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) SATA IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
02:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)

I did not include output from dmidecode as this is quite lengthy ..... 

[piran]

Water under the bridge I know but it may have been your
sdb (not sda) that was the more likely one to be suspect?
http://wiki.contribs.org/Raid#Resynchronising_a_Failed_RAID

Code: [Select]

(wiki extract)
md2 : active raid1 hdb2[1]        <-- missing partition   
     1048704 blocks [2/1] [_U]    <-- failed


Personalities : [raid1]
md2 : active raid1 sdb2[1]             <-- missing partition 
      156183808 blocks [2/1] [_U]    <-- failed
     
md1 : active raid1 sda1[0] sdb1[1]
      104320 blocks [2/2] [UU]