Topic: RAID issue - need help recovering degraded array

[CharlieBrady]

So I ask again, can you query the drive serial number on SME?

The question is really "can linux query the drive serial number"? Yes - use the sdparm command (SATA and SCSI)  or hdparm command (ATA). Note however that sdparm is not installed by default. You can find  a suitable RPM here:

http://dries.ulyssis.org/rpm/packages/sdparm/info.html

[mike_mattos]

Charly, #  sdparm didn't work ( not found error ) on either of my SME testers,  6 OR 7, and I wasn't sure which Red Hat?  version?  to download.

As you said, hdparm won't work on SME6 scsi ata

However. on SME7 , VOILA!  Thx

Now if only it would automatically decode the RAID virtual drive!
You wouldn't happen to know if SMART is working on SME, would you?
( As in, will I get an email for a SMART error BEFORE the raid crashes?)

# hdparm -I /dev/sda1

/dev/sda1:

ATA device, with non-removable media
        Model Number:       WDC WD800JD-22MSA1
        Serial Number:      WD-WMAM9Z678073
        Firmware Revision:  10.01E01
Standards:
        Supported: 7 6 5 4
        Likely used: 7
Configuration:
        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:   16514064
        LBA    user addressable sectors:  156301488
        LBA48  user addressable sectors:  156301488
        device size with M = 1024*1024:       76319 MBytes
        device size with M = 1000*1000:       80026 MBytes (80 GB)
Capabilities:
        LBA, IORDY(can be disabled)
        Queue depth: 32
        Standby timer values: spec'd by Standard, with device specific minimum
        R/W multiple sector transfer: Max = 16  Current = 16
        Recommended acoustic management value: 128, current value: 254
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4
             Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
        Enabled Supported:
           *    NOP cmd
           *    READ BUFFER cmd
           *    WRITE BUFFER cmd
           *    Host Protected Area feature set
           *    Look-ahead
           *    Write cache
           *    Power Management feature set
           *    SMART feature set
           *    FLUSH CACHE EXT command
           *    Mandatory FLUSH CACHE command
           *    Device Configuration Overlay feature set
           *    48-bit Address feature set
                Automatic Acoustic Management feature set
                SET MAX security extension
           *    DOWNLOAD MICROCODE cmd
           *    General Purpose Logging feature set
           *    SMART self-test
           *    SMART error logging
Checksum: correct

[Boris]

ldkeen & jahlewis

>  I'm trying to work out why you have 3 raid devices instead of 2.
> Are you running version 7.0?

Assuming sme7 (as posted in sme7 forum), then it looks like the server was updated from sme6.x. The 3 partition format has been retained as the upgrade process did not convert it.
It will NOT be possible to simply remove & replace a drive and have the system automatically rebuild the array using the admin console menu. This will only work for new sme7 installs (or new sme7 installs plus restore from 6.x) where there are 2 partitions.

You will have to manually rebuild the array, search the forums as there have been a few good posts recently on this topic.

I just run into exactly the same problem while upgrading from 6.0.1 to SME7.

Any suggestions on rebuilding the RAID?

[kruhm]

Hi Boris,

I had to do a fresh install then use the copyfromdisk command. Allow 2 hrs downtime.

[Boris]

That's what I figured will be my best bet as well.
Fortunately this server is not critical for operations and doesn't have vital data. Easy to reinstall (now to version 7.1)

Thanks.
Boris.