Post Error 1729-background Parity Initialization Not Yet Complete

Things Small and Medium Business Service Providers All Solutions Services Advise, Transform and Manage Financing and Flexible Capacity IT Support Services background parity initialization is currently queued Education and Training Services All Services Products Integrated Systems what is parity initialization Composable Systems Converged Systems Hyper Converged Systems Blade Systems Infrastructure Management Software Application Lifecycle parity initialization status initialization failed Management Application Delivery Management Big Data Analytics DevOps Enterprise Security Hybrid and Private Cloud Information Governance Information Management IT Service Management Operations Management Server

Parity Initialization Method

Management Software as a Service (SaaS) Software-Defined Data Center Storage Management All Software Servers Rack Servers Tower Servers Blade Servers Density Optimized Mission Critical Servers Servers for Cloud Server Management All Servers Storage All-flash and Hybrid Storage Midrange and Enterprise Storage Entry Storage Systems Data Availability, Protection and hp smart array p410i code 785 Retention Software Defined Storage Management and Orchestration Storage Networking All Storage Networking Switches Routers Access Points and Controllers Wireless LAN Campus and Branch Networking Data Center Networking Wide Area Network Software Defined Networking Network Functions Virtualization Network Management All Networking About UsSupportClearType to search2086159Solutions Transform to a Hybrid Infrastructure Protect Your Digital Enterprise Empower the Data-Driven Organization Enable Workplace Productivity Cloud Security Big Data Mobility Infrastructure Internet of Things Small and Medium Business Service Providers All Solutions Services Advise, Transform and Manage Financing and Flexible Capacity IT Support Services Education and Training Services All Services Products Integrated Systems Composable Systems Converged Systems Hyper Converged Systems Blade Systems Infrastructure Management Software Application Lifecycle Management Application Delivery Management Big Data Analytics DevOps Enterprise Security Hybrid and Private Cloud Information Governance Information Management IT Service Management Operations Management Server Management Software as a Service (SaaS) Software-Define

Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us surface scan analysis priority Learn more about Stack Overflow the company Business Learn more about hiring developers or

The 'data Array 1' Parity Initialization Status Is 'failed'.

posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and

Raid Parity Initialization

answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up https://community.hpe.com/t5/Network-Attached-Storage-NAS/Logical-Drive-with-Background-parity-error-on-HP-storage-server/td-p/2363071 and rise to the top Slow parity initialization of RAID-5 array on HP Smart Array P411 controller up vote 4 down vote favorite 1 On 29th October 2011, I built a RAID-5 array using 4 x 146.8GB Seagate SAS ST3146855SS drives running at 15k connected to a PowerEdge R515 with HP Smart Array P411 controller running Windows 2008 (so nothing particularly unusual). I know that parity initialisation of http://serverfault.com/questions/331581/slow-parity-initialization-of-raid-5-array-on-hp-smart-array-p411-controller a RAID-5 array can take some time but it's still running after 2.5 weeks which seems a little unusual. I'd previously built another array on the same controller using 4 x 2TB SATA-2 drives and that did take a while to complete but a) I'm sure it was less than 2.5 weeks, b) that array was ~12 times bigger and c) during initialization, the percentrage slowly increased each day. At the moment, the status display for this new 2nd array simply says "Parity Initialization Status: In Progress" and it's said that since the start. It's this lack of change on the status that worries me the most - feels like it's not actually doing anything. Do you think something has gone wrong or am I being unpatient and for some reason, the status not increasing is normal? I kind of expected a much smaller array on faster drives (15k SAS versus 7.5k SATA-2) to build in a few days. This is our primary SAN running StarWind so my "have a play" options are very limited. This 2nd array is currently in use for one small virtual disk so I could shut the target machine down, move the virtual disk to another drive a

complete on cluster-shared volumes, the following warning messages are displayed: Array Configuration Utility (ACU) Popup Warning Message Background parity initialization is currently queued or in http://thewon.tistory.com/4 progress on Compaq RA4000/4100 Controller in RAID Array BOX7 on the following logical drives: Logical Drive x This is a normal operation that is necessary to initialize logical drives http://www.tek-tips.com/viewthread.cfm?qid=1432480 that have a fault tolerance with parity. If background parity initialization is queued, it will start when I/O is performed on the drives. When background parity initialization completes, the parity initialization performance of the logical drives will improve. ACU (XE) Controller Status Message Background parity initialization is currently queued or in progress on logical drive X ( RAID 5 in array B). 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 background parity initialization improve. When background parity initialization does not complete on other (non-cluster-shared) volumes, the following warning messages are displayed along with above warning messages. POST Error Messages 1729-Slot X Drive Array - Disk Consistency Initialization In Progress RAID 4/5 performance may be lower until Auto Reliability Monitoring has completed Automatic Background Parity Consistency Initialization OR 1729 - Slot x Drive Array - Disk performance Optimization Scan In Progress- RAID 4/5/ADG performance may be higher after completion. System Event Log Message Source: Server Agents Type: Warning Event Id: 1123 message Description: "Warning: Compaq System Information Agent: Compaq Health: POST Errors Detected. One or more POST errors detected during server setup [SNMP Trap: 6027 in CPQHLTH.MIB]." Background parity initialization is a normal operation that is necessary to initialize logical drives that have a fault tolerance with parity. If background parity initialization is queued, it will start when I/O is performed on the drives. When background parity initialization completes, the performance of the logical drives will improve. HP Smart Array Controllers allow parity initialization for RAID 4,

FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. HP (Compaq) Disk & RAID solutions Forum at Tek-Tips HomeForumsServer RackStorage: Disk, RAID and NAS/SANHP (Compaq) Disk & RAID solutions Forum Parity Initialization thread866-1432480 Forum Search FAQs Links MVPs Parity Initialization Parity Initialization no1youno (TechnicalUser) (OP) 5 Dec 07 05:22 Hi allI am currently setting up my Proliant ML370 server with a RAID1 & RAID5.Logical Drive 2 is setup with RAID2 and apparently has a background Parity Inialization in progress. I understand that this may take several hours to complete?However I would assume that I would still see the drive in Windows Explorer, but I don't, I only see see drive C:Is this right? Do I need to wait until the Parity Inialization is completed before I see Drive D:Cheers RE: Parity Initialization cajuntank (IS/IT--Management) 5 Dec 07 12:07 Your not going to see the drive in Windows Explorer since you haven't told Windows OS what to do with it yet. Go to disk management and it should be there as a drive ready to partition and format. If it does not show up as a drive at all under disk management, then make sure all firmware and HP software is current.If still and issue post back what generation ML370 it is and what array controller model? RE: Parity Initialization no1youno (TechnicalUser) (OP) 5 Dec 07 21:07 Thanks cajuntank. I ended up using Paragon Partition Manager and did it that way.By the way, the Logical Drive 2 (RAID5) is setuo with 3x 18Gb drives, however the Logical Drive is only showing a total of around 34Gb. What has happened to the other 18Gb?I thought RAID5 combined all the physical drives?Cheers