776 (Ready for Recovery) and 785 (Parity initial. in progress) on two logical drives

[indira_sa]

Hi,

We have : Smart Array P600 Controller

In RAID 5 configuration, one disk had malfunction - ADU predicted that disk will fail, so we replaced that disk.

Rebuld was started ok, and reached 90%, but after that when we returned to ACU we have two errors:

776

(Ready for Recovery) Logical Drive 3 (2.0 TB, RAID 5) is queued for rebuilding.

785

Background parity initialization is currently queued or in progress on Logical Drive 2 (5.0 GB, RAID 5). If background parity initialization is queued, it will start when I/O is performed on the drive. When background parity initialization completes, the performance of the logical drive will improve.

Situations with drives are:

Logical drive 3 (2 TB, RAID 5):

Status

Ready for Rebuild

Rebuild Percentage Complete

0%

Drive Number

3

Drive Unique ID

600508B1001038373320202020200008

Size

2097151 MB

Fault Tolerance

RAID 5

Heads

255

Sectors/Track

32

Cylinders

65535

Strip Size

64 KB

Full Stripe Size

320 KB

Array Accelerator

Enabled

Parity Initialization Status

Initialization Completed

Disk Name

\\.\PhysicalDrive2

Logical drive 2 (5 GB, RAID 5)

Status

OK

Drive Number

2

Drive Unique ID

600508B1001038373320202020200007

Size

5119 MB

Fault Tolerance

RAID 5

Heads

255

Sectors/Track

32

Cylinders

1285

Strip Size

64 KB

Full Stripe Size

320 KB

Array Accelerator

Enabled

Parity Initialization Status

In Progress

Disk Name

\\.\PhysicalDrive1

Disk Partition Information

Partition Number: 1, Size: 5.0 GB, Mount Point: Unknown

In ADU log – there is no information about aborted buidling, but only   I see „read error“

Logical Drive 3:

     Drive Status:           Ready for recovery

     Blocks to Rebuild:     0

     Blocks Re-mapped:      

     Spare Status Flags:     0x00

     Spare to Replaced Map: See Big Spare to Replace Map:

     Media Was Exchanged:   No

     Cache Failure:         No

     Expand Failure:         0x00

     Unit Flags:             0x01 (Read Error)

     Big Remap Count:       Bus ID Count ID Count ID Count ID Count ID Count

                             1     2 002fh

     Big Drive Failure Map:     0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000

     Big Replacement Drive Map: 0x0008 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000

     Big Active Spare Map:     0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000

     Big Spare to Replace Map: No spares have replaced any drives

     Big Spare Marked OK Map:   0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000

I found information that restart may be help for rebuild to start, but Partiy initialization is in progress, so I don't what to do … To speed up initialization ? Or just wait ??

best regards and thak you for your time,

Indira

[lfeldman1]

It looks like the array has failed due to a read error durring rebuild and now has inconsistent parity(2 drives with outdated parity and 3 with a newer set.

It's unclear what exactly happened but any attempt at a rebuild at this point will cause data corruption and overwritting at this point.

If you have a validated, up to date back up, you're best bet is to replace the drive with the read error, set up a new RAID volume and retore from backup.

If you don't have a validated, up to date backup and the data is valuable, then you'll need to contact a proffessional data recovery lab.

Example: www.raiddatarecovery.com

[indira_sa]

I don't see any errors on physical disks. All disks "look" ok.  Server is running ok, all data and all partitions are availiable and working ok.  A little slower, but everything looks ok. Only in ACU I have one information 785 and warning  776 ...

5 disks in RAID 5. -> 4 logical disks.  And I have problem with 2. and 3. logical drive.

2. logical drive is for party, and 3. logical drive is my "Data partition".

If I setup new RAID 5, I have to format server, becouse I have only one RAID 5 on 6 disks  for hole server.....

As you see in table belove 3. logical drive is my partition E:\ on server...

Logical Drive Status: Ready for Rebuild

Rebuild Percentage Complete: 0%

Drive Number 3

Drive Unique ID 600508B1001038373320202020200008

Size 2097151 MB

Fault Tolerance RAID 5

Heads 255

Sectors/Track 32

Cylinders 65535

Strip Size 64 KB

Full Stripe Size 320 KB

Array Accelerator Enabled

Parity Initialization Status Initialization Completed

Disk Name \\.\PhysicalDrive2

Disk Partition Information Partition Number: 1, Size: 2.0 TB, Mount Point: E:\

[indira_sa]

hi, pls any info/suggestins ? 

is it ok, to try restart  or remove/add disk which we replaced. I think that may be something is not ok with the disk which is replaced.

I send ACU log..

thank you for your time,

Indira

[indira_sa]

just to share info... may be it could be usefull to smb.

We shut down server, turn off power supply. Wait 10-15', check disks in meantime  (take it out, and trun it back). Everything was ok.

after that turn on server, "f2" - start automatic recovery   (there was info that las automatic rec. was not successfull).

REbuild started ok, server was started ok and rebuild finished ok.  :)

The thing that I changed before shut down server is that realocate some jobs from that server to another (just to reduce load on server)....

best regards,

Indira

[indira_sa]

sorry, previously reply was not correct  : "F1" is for Automatic Reocvery and that was the option we choosed.

best regards,

Indira