January 24, 201511 yr I haven't really touched anything on my server in a long time...it was probably running for at least half a year without any intervention. Lately, I wanted to see if I could get Plex running on it and since I was still on 4.7 I decided I would try upgrading to 5.0.6. It seemed to work fine, however after doing the first parity check it looks like there are 840 errors. It says parity is valid though. Should I be worried? Anything for me to do or check? One other thing is that on my windows 7, it seems like I cannot get access to any of my shares. It will always give me access denied, but from my ATV2, the shares still seem to work fine. Any ideas? Thanks
January 24, 201511 yr Have you been doing regular parity checks? If not then maybe you accumulated a lot of parity errors. Have you been shutting down unRAID without stopping the array first? That could be a reason for parity errors. Have you run New Permissions like it said in the upgrade instructions? That might be why you can't access your shares.
January 24, 201511 yr Author Thanks for the reply. There were no parity errors before as the were regular parity checks done prior to the upgrade. Last one that was done prior was 21 days ago, so perhaps there were parity errors during this time, but I doubt it. I don't shut down without stopping the array first, but before I ran the upgrade, it appeared that when I shut down the array, it was hanging, so I did had to shut down without knowing if the array was completely stopped or not. Could have caused the errors I suppose. In that case, what options do I have for correction? For the permissions....damn, I totally forgot about that. I noticed that part before signing off for the night and completely forgot before writing this post. I will try that, and it should work fine. Thanks.
January 24, 201511 yr Author Wait....I think I am reading this wrong. Parity status shows: Last checked on Fri Jan 23 23:42:37 2015 EST, finding 0 errors. But for my parity drive, it shows: Temp. Size Free Reads Writes Errors parity WDC_WD20EARS-00MVWB0_WD-WCAZA8054351 (sdg) 1953514552 23°C 2 TB - 26192839 1041484 840 So I am not sure what those 840 errors are representing.
January 24, 201511 yr Wait....I think I am reading this wrong. Parity status shows: Last checked on Fri Jan 23 23:42:37 2015 EST, finding 0 errors. But for my parity drive, it shows: Temp. Size Free Reads Writes Errors parity WDC_WD20EARS-00MVWB0_WD-WCAZA8054351 (sdg) 1953514552 23°C 2 TB - 26192839 1041484 840 So I am not sure what those 840 errors are representing. Post a smart report for your parity drive. Those are read errors that apparently accepted a subsequent write without an error. Your hard drive could be failing.
January 25, 201511 yr Author smartctl -a -d ata /dev/sdg smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WCAZA8054351 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sat Jan 24 23:38:31 2015 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (40260) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 171 169 021 Pre-fail Always - 6408 4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 2361 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 059 059 000 Old_age Always - 30125 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 36 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 8 193 Load_Cycle_Count 0x0032 193 193 000 Old_age Always - 22200 194 Temperature_Celsius 0x0022 127 117 000 Old_age Always - 23 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 10 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 27 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 196 196 000 Old_age Offline - 1209 SMART Error Log Version: 1 ATA Error Count: 13 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 13 occurred at disk power-on lifetime: 30027 hours (1251 days + 3 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 68 a8 f1 e6 Error: UNC 8 sectors at LBA = 0x06f1a868 = 116500584 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 68 a8 f1 e6 08 35d+14:33:51.753 READ DMA c8 00 08 38 5c e2 e6 08 35d+14:33:51.721 READ DMA Error 12 occurred at disk power-on lifetime: 29912 hours (1246 days + 8 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 68 48 d4 ee Error: UNC 8 sectors at LBA = 0x0ed44868 = 248793192 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 68 48 d4 ee 08 30d+19:16:43.915 READ DMA ef 10 02 00 00 00 a0 08 30d+19:16:43.915 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 30d+19:16:43.912 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 30d+19:16:43.911 SET FEATURES [set transfer mode] Error 11 occurred at disk power-on lifetime: 29912 hours (1246 days + 8 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 68 48 d4 ee Error: UNC 8 sectors at LBA = 0x0ed44868 = 248793192 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 68 48 d4 ee 08 30d+19:16:41.206 READ DMA ef 10 02 00 00 00 a0 08 30d+19:16:41.206 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 30d+19:16:41.203 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 30d+19:16:41.202 SET FEATURES [set transfer mode] Error 10 occurred at disk power-on lifetime: 29912 hours (1246 days + 8 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 68 48 d4 ee Error: UNC 8 sectors at LBA = 0x0ed44868 = 248793192 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 68 48 d4 ee 08 30d+19:16:38.497 READ DMA ef 10 02 00 00 00 a0 08 30d+19:16:38.497 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 30d+19:16:38.494 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 30d+19:16:38.493 SET FEATURES [set transfer mode] Error 9 occurred at disk power-on lifetime: 29912 hours (1246 days + 8 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 68 48 d4 ee Error: UNC 8 sectors at LBA = 0x0ed44868 = 248793192 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 68 48 d4 ee 08 30d+19:16:35.788 READ DMA ef 10 02 00 00 00 a0 08 30d+19:16:35.788 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 30d+19:16:35.784 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 30d+19:16:35.784 SET FEATURES [set transfer mode] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 90% 30116 218471296 SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.
January 25, 201511 yr It doesn't look healthy. It's possible that you just have some limited bad spots starting to show up, or a marginal power supply issue, but it's more likely that you caught the drive at the beginning of failure. If it were me I'd get smart reports on the rest of the drives, just to make sure you don't have multiple drives with issues. Assuming the parity drive is the only marginal drive, it would be a great time to start planning for the future with a 4TB or larger parity drive replacement, and once the array is healthy again you can preclear the old parity drive for a couple cycles to see if the problems stabilize or get worse. I'm betting the drive is a goner, but it may be ok as long as you can get the current pending sector to go back to zero and stay that way, and get the offline uncorrectable and reallocated sector count number to stop growing.
January 25, 201511 yr Author This is great! Thanks very much for the help. Should I just be running the short tests? I didn't even know about these tests, but I will run them now to see what results I get. I am attaching the Smart Test for the other drives. They seemed to all be completed without errors, but you mentioned about pending sector and on SDB I see 66 in pending (if I am reading that correctly). My question is, do I have any issues with the other drives? sdb.txt sdc.txt sdf.txt sdd.txt
January 25, 201511 yr Author I am also attaching a screen capture of the Smart View of the drives. I tried to attach it to the previous post, but I could not include additional attachments for some reason.
January 25, 201511 yr Do you have current backups? If not, I'd back everything up now before doing any drive replacements with the array. You have 2 drives with pending sectors, which may prevent a successful rebuild. It's not a guaranteed fail, but it doesn't give me the warm and fuzzies. Ideally drive problems should be dealt with as soon as they come up, because unraid requires perfect reads from all but 1 drive to rebuild that failed drive. Currently the stock GUI doesn't emphasize drive health enough, but that is changing in the 6 beta versions. The smart report screen from myMain in unmenu is a very good place to keep up with drive health right now, as your screenshot shows.
January 25, 201511 yr Author I'm open to all suggestions. So what you are saying is that 2 drives are potentially falling? The parity plus 1 other? I currently do not run any backups and I honestly wouldn't even know how to back up this data. I basically set up this unraid server added some plugins and was essentially hands off the last 3 years. Looking for advice on how to proceed. You mentioned buying a 4tb to replace the parity. I can certainly do that but not sure what to do with the existing parity drive or the other problematic one. Thanks
January 25, 201511 yr Author Thanks dgaschk, however I am lost with some of this stuff. I was hoping for a more step 1, step 2, etc, kind of like this post: http://lime-technology.com/forum/index.php?topic=4068.msg91731#msg91731 I guess I am hoping for some magic too. Doing another parity check right now, and the drive errors are increasing.
January 25, 201511 yr Since you haven't gotten a reply, I will tell you what I would do it. (First, you will be buying two disks to replace these disks. So be looking around and evaluting what you need and can afford. If you will be needing more storage capacity in the future this would be an excellent time to get two 3 to 6TB drives.) Now for the procedure: 1- On the 'Main' page of unRAID's webGUI, double click on disk 2. 2- Under the SMB properties, make 'Export' 'Yes' and 'Security' 'Public' 3- On your windows machine, double click on Network and select your server by name. 4- Open 'Disk 2' and copy all the files off that disk. (You may have some failures-- data loss-- if both Disk 2 and your parity drive have issues in the same respective blocks.) If you don't have room off the server, you could try to copy some data from disk 2 to other disks on your server. With your parity drive in its current state, I would not really recommend doing this accept under extreme circumstances! Another option would be to be to simply preclear both disks and install them without attempting to recover any data from Disk 2 while it is still in the array. Install a utility (I am aware of two that will do this) which will read your disk 2 in your windows. You can then copy the files back to the server. Using this option will guarantee that you lose data!
January 25, 201511 yr Author Thanks Frank1940. A few questions. 1. After copying the files off of Disk 2, what should I do with that drive? Does it get tossed? Or can it be used again? 2. You said I need 2 more drives....is that replacing Disk 2 and Parity? What happens with both of the current drives? Again....are they garbage? 3. Once I copy off the files from Disk 2 (no, I don't have any room, but I may pick and choose what I keep from that disk as I do not need it all), then what happens? Do I mount both new drives, assign 1 to parity, and the other as a partition, then copy back those files? Thanks again!
January 26, 201511 yr Thanks Frank1940. A few questions. 1. After copying the files off of Disk 2, what should I do with that drive? Does it get tossed? Or can it be used again? You might try like a triple cycle of preclear script on both disks and see if the number of errors stabilize. If they do then depends on your tolerance for risk of losing data. I personally like to err on the side of caution! 2. You said I need 2 more drives....is that replacing Disk 2 and Parity? What happens with both of the current drives? Again....are they garbage? You are going to be replacing both the parity and disk 2 at this point. The odds are not fifty-fifty that either of the two drives can be used reused. The simplest way to find out if a drive is garage is to try to run three cycles of the preclear script and see if the number of errors (and the type of errors) remains constant after the first cycle. (The last disk I had fail would not even start the preclear script!) Basically, you are attempting to figure out if the disk is failing very quickly or if it still has a few months of usable service left in it. (Realize that all hard drives WILL fail. The trick is to figuring out when!) 3. Once I copy off the files from Disk 2 (no, I don't have any room, but I may pick and choose what I keep from that disk as I do not need it all), then what happens? Do I mount both new drives, assign 1 to parity, and the other as a partition, then copy back those files? One thing, you can do is to format one of the new disks in your windows machine. Now copy the files from disk 2 onto that disk. Preclear the second new disk. When that is done, remove the current parity drive from the server. NOTE: your server will be without parity protection at this point forward until your new parity drive is installed and parity is rebult. Install the preclear drive as disk 2 in the server. Assign it as a data disk. Now copy the data back from the windows computer to this new disk 2. Once, you have everything copied back, remove that new drive from your windows machine and preclear it. Then assign that drive as the parity drive and allow it to rebuild parity. You are not going to get this done in the next two hours. A single preclear cycle takes about 24 hours for 3TB drive. The first thing to do is to get those new drives ordered. Then decide on which course of action you are going to use. PS---- I, personally, would not write to the server until after I had recovered as much data as possible from disk 2. If your parity drive goes belly up, you guarantee a data loss from disk 2!
January 26, 201511 yr Author Wow....this is awesome, and exactly what I needed. I think I understand this a bit more now. So, currently looking for new drives. Could these be used? http://www.ncix.com/detail/wd-elements-4tb-desktop-external-bb-103285-1356.htm?affiliate_id=58025&click_id=1183544611 Sounds like they could be removed from their enclosures. They have the WD40EZRX in them.
January 26, 201511 yr Wow....this is awesome, and exactly what I needed. I think I understand this a bit more now. So, currently looking for new drives. Could these be used? http://www.ncix.com/detail/wd-elements-4tb-desktop-external-bb-103285-1356.htm?affiliate_id=58025&click_id=1183544611 Sounds like they could be removed from their enclosures. They have the WD40EZRX in them. Have you done due due diligence on this drive to see what other people experience is in removing and using these drives. If you do get them, be sure and test the drives in their housing to make sure they work. (Removing the drive usually voids the warranty!) Since it has an USB 3.0 interface, you would get transfer speeds faster than the data transmission over your network. That would mean that you won't have to pull that drive out of its enclosure until the data is back onto the server.
January 26, 201511 yr I'd spend a few extra $$ and get NAS-rated drives -- either WD Reds or the HGST units. http://www.newegg.com/Product/Product.aspx?Item=N82E16822145912 http://www.newegg.com/Product/Product.aspx?Item=N82E16822236599 The WD Reds run a bit cooler, but the HGST are a bit faster. Both have excellent reliability records. As for the replacement process ... I basically agree with what's been outlined, but would do one thing a bit different ... (1) First, as Frank suggested, copy everything from disk 2 to another location -- if you need additional space for that, buy yet-another drive (an external unit is fine) and attach it to your PC, then copy the data to it. (2) Replace your parity drive with one of the new 4TB drives you will be buying, and let the system rebuild parity; then do a parity check to confirm it's okay. If all seems well at this point; just replace your failing disk 2 with the other new 4TB drive, and let the system do a rebuild on that. If this goes well, you should have all of your data intact ... but just to be absolutely certain you may want to run a file comparison utility of the rebuilt disk #2 with the data you saved in #1. (3) Finally, you should consider how you're going to backup your data. UnRAID is NOT a replacement for having backups of data you don't want to lose. You only have 7TB of array space, so a pair of 4TB external drives is clearly enough to backup all of your data with room to spare -- and you could than add your other 2TB drives to your pool of backup drives as you eventually replace them with higher capacity drives.
January 26, 201511 yr Author Thank you to you both. I will now be on the hunt for 2 drives in the next week or so. I can refrain from writing to the server until this is resolved. I'll probably have a few more questions when I get started on this, but I should be good for now.
June 25, 201511 yr Author So....after 5 months, I finally purchased a few drives. I am trying to pre-clear one of the drives, and running into an issue. Pre-Clear unRAID Disk /dev/sdb ################################################################## 1.15 Device Model: TOSHIBA DT01ACA300 Serial Number: 255BRYBGS Firmware Version: MX6OABB0 User Capacity: 3,000,592,982,016 bytes Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Disk /dev/sdb doesn't contain a valid partition table ######################################################################## invoked as ./preclear_disk.sh /dev/sdb ######################################################################## (MBR 4k-aligned set. Partition will start on sector 64 for disks <= 2.2TB and se ctor 1 for disks > 2.2TB) Are you absolutely sure you want to clear this drive? (Answer Yes to continue. Capital 'Y', lower case 'es'): Y Clearing will NOT be performed root@Tower:/boot# Any idea why it would say "Clearing will NOT be performed"? In the log, it says "Tower kernel: sdb: unknown partition table"
June 25, 201511 yr So....after 5 months, I finally purchased a few drives. I am trying to pre-clear one of the drives, and running into an issue. Pre-Clear unRAID Disk /dev/sdb ################################################################## 1.15 Device Model: TOSHIBA DT01ACA300 Serial Number: 255BRYBGS Firmware Version: MX6OABB0 User Capacity: 3,000,592,982,016 bytes Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Disk /dev/sdb doesn't contain a valid partition table ######################################################################## invoked as ./preclear_disk.sh /dev/sdb ######################################################################## (MBR 4k-aligned set. Partition will start on sector 64 for disks <= 2.2TB and se ctor 1 for disks > 2.2TB) Are you absolutely sure you want to clear this drive? (Answer Yes to continue. Capital 'Y', lower case 'es'): Y Clearing will NOT be performed root@Tower:/boot# Any idea why it would say "Clearing will NOT be performed"? In the log, it says "Tower kernel: sdb: unknown partition table" Because you did not type the full word 'Yes' to start the preclear.
June 25, 201511 yr Author I was just about to come back and delete my idiotic post, but you beat me to it. Yep....just figured that out. For some reason, I kept reading Y for yes.
June 26, 201511 yr Author One thing, you can do is to format one of the new disks in your windows machine. Now copy the files from disk 2 onto that disk. Preclear the second new disk. When that is done, remove the current parity drive from the server. NOTE: your server will be without parity protection at this point forward until your new parity drive is installed and parity is rebult. Install the preclear drive as disk 2 in the server. Assign it as a data disk. Now copy the data back from the windows computer to this new disk 2. Once, you have everything copied back, remove that new drive from your windows machine and preclear it. Then assign that drive as the parity drive and allow it to rebuild parity. You are not going to get this done in the next two hours. A single preclear cycle takes about 24 hours for 3TB drive. The first thing to do is to get those new drives ordered. Then decide on which course of action you are going to use. PS---- I, personally, would not write to the server until after I had recovered as much data as possible from disk 2. If your parity drive goes belly up, you guarantee a data loss from disk 2! One question. If I have removed the current parity and the array is stopped, how can I see the new data drive in order to copy the files back?
June 26, 201511 yr One thing, you can do is to format one of the new disks in your windows machine. Now copy the files from disk 2 onto that disk. Preclear the second new disk. When that is done, remove the current parity drive from the server. NOTE: your server will be without parity protection at this point forward until your new parity drive is installed and parity is rebult. Install the preclear drive as disk 2 in the server. Assign it as a data disk. Now copy the data back from the windows computer to this new disk 2. Once, you have everything copied back, remove that new drive from your windows machine and preclear it. Then assign that drive as the parity drive and allow it to rebuild parity. You are not going to get this done in the next two hours. A single preclear cycle takes about 24 hours for 3TB drive. The first thing to do is to get those new drives ordered. Then decide on which course of action you are going to use. PS---- I, personally, would not write to the server until after I had recovered as much data as possible from disk 2. If your parity drive goes belly up, you guarantee a data loss from disk 2! One question. If I have removed the current parity and the array is stopped, how can I see the new data drive in order to copy the files back? With the array stopped and shut the server down Remove Disk 2. (I assume that you have removed the parity disk.) Be sure you know the serial number of the new disk. Start the server. Assign assign the new disk as Disk 2 (verifying what you did by the serial number). Start the array. The array will now be unprotected. Copy the Data back to Disk 2. Now preclear that new Windows Disk that you backed the data onto. Set it as the new parity disk. Start the array and parity will then be built onto that disk. (You could skip the preclear since you did exercise that disk with the copy operations but I would always recommend preclearing any disk before adding it to the server. That way you have tested the entire surface of the disk.)
Archived
This topic is now archived and is closed to further replies.