October 18, 201411 yr Yesterday my v5 server showed 4 errors on a drive, so i started a parity check as stated in the wiki. This morning, about 10 hours later, it should be finished, so i checked but the webgui is not responding. Also i can not start unmenu. I can see other plugins still working (sabnzbd, slimserver, sickbeard) and i can also use telnet. I tried to manually umount and stop the array but umnout /mnt/md1 says the disk is busy... so i can not stop. Does that mean the parity check is still running? How can i find out if it is? Is there a way to restart the gui? Will that also restart umenu?
October 18, 201411 yr Author I am very worried... syslog also showed read errors on disk2? Why am i suddenly getting read errors? the syslog is showing these sorts of messages for the last 10 hours, does that mean it is still doing the parity check? 8 10:30:03 UNRAID kernel: cdb[0]=0x88: 88 00 00 00 00 00 6b ae 3a f0 00 00 04 00 00 00 Oct 18 10:30:03 UNRAID kernel: scsi target1:0:6: handle(0x000f), sas_address(0x4433221106000000), phy(6) Oct 18 10:30:03 UNRAID kernel: scsi target1:0:6: enclosure_logical_id(0x500605b0033c0a20), slot(5) Oct 18 10:30:03 UNRAID kernel: sd 1:0:6:0: task abort: SUCCESS scmd(e6489480) Oct 18 10:30:34 UNRAID kernel: sd 1:0:6:0: attempting task abort! scmd(e6489480) Oct 18 10:30:34 UNRAID kernel: sd 1:0:6:0: [sdj] CDB: Oct 18 10:30:34 UNRAID kernel: cdb[0]=0x88: 88 00 00 00 00 00 6b ae 3a f0 00 00 04 00 00 00 Oct 18 10:30:34 UNRAID kernel: scsi target1:0:6: handle(0x000f), sas_address(0x4433221106000000), phy(6) Oct 18 10:30:34 UNRAID kernel: scsi target1:0:6: enclosure_logical_id(0x500605b0033c0a20), slot(5) Oct 18 10:30:34 UNRAID kernel: sd 1:0:6:0: task abort: SUCCESS scmd(e6489480) Oct 18 10:31:05 UNRAID kernel: sd 1:0:6:0: attempting task abort! scmd(e6489480) Oct 18 10:31:05 UNRAID kernel: sd 1:0:6:0: [sdj] CDB: Oct 18 10:31:05 UNRAID kernel: cdb[0]=0x88: 88 00 00 00 00 00 6b ae 3a f0 00 00 04 00 00 00 Oct 18 10:31:05 UNRAID kernel: scsi target1:0:6: handle(0x000f), sas_address(0x4433221106000000), phy(6) Oct 18 10:31:05 UNRAID kernel: scsi target1:0:6: enclosure_logical_id(0x500605b0033c0a20), slot(5) Oct 18 10:31:05 UNRAID kernel: sd 1:0:6:0: task abort: SUCCESS scmd(e6489480) Oct 18 10:31:36 UNRAID kernel: sd 1:0:6:0: attempting task abort! scmd(e6489480) Oct 18 10:31:36 UNRAID kernel: sd 1:0:6:0: [sdj] CDB: Oct 18 10:31:36 UNRAID kernel: cdb[0]=0x88: 88 00 00 00 00 00 6b ae 3a f0 00 00 04 00 00 00 Oct 18 10:31:36 UNRAID kernel: scsi target1:0:6: handle(0x000f), sas_address(0x4433221106000000), phy(6) Oct 18 10:31:36 UNRAID kernel: scsi target1:0:6: enclosure_logical_id(0x500605b0033c0a20), slot(5) Oct 18 10:31:36 UNRAID kernel: sd 1:0:6:0: task abort: SUCCESS scmd(e6489480) Please help... syslog.zip
October 18, 201411 yr It could be a loose connection to disk2 or a failing disk. If your sure the parity check should be finished or even if not I would reboot your server. You can't do much without the webgui. I would run the powerdown -r command from command to reboot and have a look at what is going on. You really need to upgrade to 5.05 as well. If it is only a parity check then a reboot shouldn't affect the array.
October 18, 201411 yr Author Thanks... i've used powerdown to shut down the machine. During shutdown i noticed a SMART report stating 'disk failure within 24 hours'.... When it was down gave it a good cleaning (lots of dust...) and re-plugged all disks and cables. Now i have rebooted, and the gui does not show any errors...like nothing happened. Looking at the smart status reports from unmenu, i see reallocated sector counts on disk 2 and 6. Disk 2 has failed smart: smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Hitachi/HGST Deskstar 7K4000 Device Model: Hitachi HDS724040ALE640 Serial Number: PK2311PAG4JRMM LU WWN Device Id: 5 000cca 22bc21049 Firmware Version: MJAOA3B0 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sat Oct 18 12:55:27 2014 CEST 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: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. 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 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 082 082 054 Pre-fail Offline - 1112 3 Spin_Up_Time 0x0007 125 125 024 Pre-fail Always - 620 (Average 618) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 1501 5 Reallocated_Sector_Ct 0x0033 001 001 005 Pre-fail Always FAILING_NOW 1995 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 114 114 020 Pre-fail Offline - 37 9 Power_On_Hours 0x0012 098 098 000 Old_age Always - 19830 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 58 192 Power-Off_Retract_Count 0x0032 099 099 000 Old_age Always - 1505 193 Load_Cycle_Count 0x0012 099 099 000 Old_age Always - 1505 194 Temperature_Celsius 0x0002 150 150 000 Old_age Always - 40 (Min/Max 24/54) 196 Reallocated_Event_Count 0x0032 001 001 000 Old_age Always - 4987 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 Disk 6 has passed but also has reallocted buffer count of 916. All other disks have PASSED. So... what to do now? Should i replace disk 2 and do a rebuild? What about disk 6?
October 18, 201411 yr Author Anyone who can point me in the right direction? What should i do, remove disk2 and replace it with a new one and rebuild? But... since disk6 has read errors as well, won't that become a problem during rebuild? I've just got me a new 4TB WD Red just in case.
October 18, 201411 yr Author I don't wanna be impatient but i really need some help/guidance/assurance. What should i do? Anyone? Am i posting in the wrong section maybe?
October 19, 201411 yr Author At this moment i can not even copy data from disk2 anymore, it is extremely slow, and the webgui shows errors are generated when i do. So there is no way to copy stuff from it, i have to replace disk2 and rebuild it from parity i guess. Disk6 i can still copy data from, i have enough room on the array to move it's content and do a poor man's backup. If needed, disk6 could be omitted. So if there is a way to remove disk6 before i rebuild disk2, so disk6 won't be a hazard? Anyway, smart report for Disk 6. Numbers for reallocated sector and reallocated count and pending sector are stable since at least yesterday, and i've been copying and deleting data from it since then. Statistics for /dev/sdg Hitachi_HDS724040ALE640_PK2311PAG421XT smartctl -a /dev/sdg smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Hitachi/HGST Deskstar 7K4000 Device Model: Hitachi HDS724040ALE640 Serial Number: PK2311PAG421XT LU WWN Device Id: 5 000cca 22bc1d939 Firmware Version: MJAOA3B0 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sun Oct 19 09:32:25 2014 CEST 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: ( 38) The self-test routine was interrupted by the host with a hard or soft reset. Total time to complete Offline data collection: ( 24) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 558) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control 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 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 137 137 054 Pre-fail Offline - 79 3 Spin_Up_Time 0x0007 121 121 024 Pre-fail Always - 637 (Average 638) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 1203 5 Reallocated_Sector_Ct 0x0033 057 057 005 Pre-fail Always - 923 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 112 112 020 Pre-fail Offline - 38 9 Power_On_Hours 0x0012 098 098 000 Old_age Always - 18113 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 20 192 Power-Off_Retract_Count 0x0032 099 099 000 Old_age Always - 1206 193 Load_Cycle_Count 0x0012 099 099 000 Old_age Always - 1206 194 Temperature_Celsius 0x0002 181 181 000 Old_age Always - 33 (Min/Max 23/54) 196 Reallocated_Event_Count 0x0032 001 001 000 Old_age Always - 1959 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 56 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 4 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 4 occurred at disk power-on lifetime: 18079 hours (753 days + 7 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 40 00 40 04 Error: UNC at LBA = 0x04400040 = 71303232 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 08 00 40 00 40 40 00 1d+09:01:58.443 READ FPDMA QUEUED 60 08 00 70 b1 31 40 00 1d+09:01:58.425 READ FPDMA QUEUED 60 08 00 60 f0 c8 40 00 1d+09:01:58.405 READ FPDMA QUEUED 60 08 00 58 00 94 40 00 1d+09:01:58.384 READ FPDMA QUEUED e5 00 00 00 00 00 00 00 1d+09:00:12.211 CHECK POWER MODE Error 3 occurred at disk power-on lifetime: 18079 hours (753 days + 7 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 50 00 54 0d Error: UNC at LBA = 0x0d540050 = 223608912 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 08 00 50 00 54 40 00 1d+08:53:38.552 READ FPDMA QUEUED 60 08 00 58 00 f0 40 00 1d+08:53:38.552 READ FPDMA QUEUED 60 08 00 68 00 f0 40 00 1d+08:53:38.551 READ FPDMA QUEUED 60 08 00 60 00 f0 40 00 1d+08:53:38.542 READ FPDMA QUEUED 60 08 00 e8 32 60 40 00 1d+08:53:38.528 READ FPDMA QUEUED Error 2 occurred at disk power-on lifetime: 18079 hours (753 days + 7 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 e8 80 3f 0b Error: UNC at LBA = 0x0b3f80e8 = 188711144 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 08 00 e8 80 3f 40 00 1d+08:49:26.244 READ FPDMA QUEUED 60 08 00 00 c4 b3 40 00 1d+08:49:26.234 READ FPDMA QUEUED 60 08 00 78 e6 0e 40 00 1d+08:49:26.234 READ FPDMA QUEUED 60 08 00 80 e6 0e 40 00 1d+08:49:26.224 READ FPDMA QUEUED 60 08 00 38 c3 91 40 00 1d+08:49:26.210 READ FPDMA QUEUED Error 1 occurred at disk power-on lifetime: 18079 hours (753 days + 7 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 58 00 d4 0a Error: UNC at LBA = 0x0ad40058 = 181665880 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 08 00 58 00 d4 40 00 1d+08:49:22.182 READ FPDMA QUEUED 60 08 00 30 77 5e 40 00 1d+08:49:22.182 READ FPDMA QUEUED 60 08 00 48 77 5e 40 00 1d+08:49:22.161 READ FPDMA QUEUED 60 08 00 60 c9 98 40 00 1d+08:49:22.141 READ FPDMA QUEUED 60 08 00 48 53 d7 40 00 1d+08:49:22.127 READ FPDMA QUEUED SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Interrupted (host reset) 60% 18098 - 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.
October 19, 201411 yr You cannot remove any disks if you want to be able to rebuild disk2 from parity. If you have a spare drive available then I would do this ASAP before something else goes wrong. Since you have another drive possibly playing up it is possible the rebuild will not be perfect (i.e. some files corrupt/missing) but at least you will have recovered what you can. As you say you have copied data off the other suspect drive (disk6), then once you have rebuilt disk2, you could do a 'new config' and re-assign the drives omitting disk6. The 'new config' will destroy the current parity (which is why you need to rebuild disk2 first) but should then leave you with a known working set of drives albeit without parity at this point.. After doing the new config you will have to do a parity sync to create a new valid parity, and after that you should run a parity check to validate it. Once you have the current disk6 out of the array you can put the drive through a few pre-clear cycles to see if it is really failing and needs replacing or not. Disk2 should not be re-used as in my experience any drive that fails SMART is in imminent total failure (unfortunately the converse is not true). If it is still under warranty the fact that it is failing SMART is more than enough reason to ask for a replacement.
October 19, 201411 yr Clearly you need to rebuild disk2. Hopefully you have backups of your data -- if not, you'll just have to run the risk of losing all of disk2's data until the rebuild completes because, as you've noted you may have a 2nd failing drive as well. If the disk2 rebuild completes okay, I'd then do the same with disk6, so you have both of your troublesome disks out of the array.
October 19, 201411 yr Disk2 should not be re-used as in my experience any drive that fails SMART is in imminent total failure ... Absolutely agree. If a disk fails SMART, do NOT use it - period. Time for the trash can or (if under warranty) an RMA.
October 19, 201411 yr Author OK, loud and clear, thanks! I do not have a full backup, so i take the risk of losing all of disk2 data, i am aware of that. I guess i'll have to run the preclear script on the replacement for disk2 first? That will take a day or 2 as well
October 19, 201411 yr I guess i'll have to run the preclear script on the replacement for disk2 first? That will take a day or 2 as well I'd turn off your server and not use it until you have the new disk tested and are ready for the rebuild. A pre-clear isn't absolutely necessary (it's just one way of testing the disk) ... but you should at least confirm the new disk is okay. To minimize downtime, I'd just run the WD Data Lifeguard tests -- Quick, Extended, then a full write zeroes, and then repeat the Quick and Extended -- on a convenient PC. Connect the drive directly to a SATA port ... that's FAR faster than using a USB caddy.
October 19, 201411 yr Author I don't have a esata cable... so i will test the new wd red using a usb docking station. In the mean time i am still copying some stuff from disk6 as much as i can, just to be sure. After that is done, and the new WD red is ok & ready, i will replace disk2 and start the rebuild as stated in the wiki. Thanks so far guys!
October 19, 201411 yr Author I've downloaded the wd diagnostics, but the extended test and the full zero write will take about 70 hours each... over usb. So if i have to do both tests twice, i'll be litterally busy for the next 3 weeks... I think i better put the wd red in the unraid machine and do a preclear from there... that will take a day and a half, for one run. If i don't want to use the unraid server's storage while preclearing, can i just leave it or should i stop the array while preclearing?
October 19, 201411 yr Actually you don't need to do two of the extended WD tests. Just do a Quick test; then a full Write Zeroes; and then the Extended test. However, if you do these over USB, they do indeed take a LONG time. If you do them from a SATA port, they're MUCH quicker -- actually a good bit quicker than a pre-clear. Does your PC not have any spare SATA ports? You don't have to actually put the drive in the machine -- just attach a SATA cable to it, plug it in a spare port; and plug in a SATA power cable. But if you prefer to use the UnRAID machine, that's fine. I wouldn't do anything with the array, however => it's okay to Start it (or not), but don't USE it. No need to take any chances with more use of the two failing drives until you get this resolved.
October 19, 201411 yr Author I don't have a pc, only a mac mini, and a windows laptop. The laptop has a eSata port, but i don't have a cable for it...
October 19, 201411 yr ... i don't have a cable for it... Easy (and cheap) to fix [ http://www.monoprice.com/Product?c_id=102&cp_id=10226&cs_id=1022603&p_id=8792&seq=1&format=2 ] ... but clearly by the time it arrives you could just test with a USB dock (or do a pre-clear).
October 19, 201411 yr Author I hurried to the local pc shop yesterday to get the 4TB WD red... i could have picked up a cable there
October 19, 201411 yr I hurried to the local pc shop yesterday to get the 4TB WD red... i could have picked up a cable there In any event, you should pick up a cable when convenient (or just order one). It's definitely something you should have so you can attach drives to the laptop when needed.
October 20, 201411 yr Author I will pick one up later this week, i'm gonna get a 2nd WD red for disk6 as well. If the rebuild succeeds that is. Preclearing is in its final stage, post read, 40%. Probably gonna start the rebuild next morning (it's now 18:45 here in NL) How long will a rebuild take? About the same time as a preclear cycle?
October 20, 201411 yr A rebuild should take roughly the same amount of time as a parity check. Not nearly as long as a preclear.
October 20, 201411 yr Author Ok, so a rebuild will take about 9 to 10 hours, that's a lot better I just found out the 4TB WD red disk is 52 bytes 'larger' then the parity and other (HGST) 4TB disks... the HGST/Hitachi's are 3907018532 bytes, the WD is 3907018584 bytes... will this become a problem for the rebuild?
October 20, 201411 yr Ok, so a rebuild will take about 9 to 10 hours, that's a lot better I just found out the 4TB WD red disk is 52 bytes 'larger' then the parity and other (HGST) 4TB disks... the HGST/Hitachi's are 3907018532 bytes, the WD is 3907018584 bytes... will this become a problem for the rebuild? Yes, definitely. UnRAID won't allow it, as the parity drive must be >= all other drives in the system. There are two ways to resolve this ... (1) Use the "parity swap-disable" feature; which allows you to replace a failing drive with the parity drive while at the same time upgrading parity to a larger drive. This process is outlined in the Wiki. Basically the system will first copy the old parity drive to the new one; then do the rebuild. (2) Attach your WD Red to your laptop (using the eSATA cable you're going to buy); and use the SetMax feature in the free HDat2 utility [ http://www.hdat2.com/ ] to make it the same size as the current parity drive. The drive can then be used for a rebuild without the need to change your parity drive.
October 20, 201411 yr ... Here's a copy of the Wiki page that outlines the swap-disable process: You must replace a failed disk with a disk which is as big or bigger than the original and not bigger than the parity disk. If the replacement disk is larger than your parity disk, then the system permits a special configuration change called swap-disable. For swap-disable, you use your existing parity disk to replace the failed disk, and you install your new big disk as the parity disk: 1. Stop the array. 2. Power down the unit. 3. Replace the parity hard disk with a new bigger one. 4. Replace the failed hard disk with you old parity disk. 5. Power up the unit. 6. Start the array. When you start the array, the system will first copy the parity information to the new parity disk, and then reconstruct the contents of the failed disk. Note, however, that there have been a few instances where folks say this hasn't worked correctly in v5. I've not done it myself, so I don't really know => but the "Safe" way to do this is to do one step at a time ... i.e. do the rebuild of the failing disk; and THEN upgrade parity to a larger drive. Personally, I'd use HDat2 to make the disk "okay" for a rebuild; then, with your next WD Red, upgrade parity to that drive (or perhaps even spring for a 6TB unit for parity) ... and then you won't have issues with future rebuilds.
Archived
This topic is now archived and is closed to further replies.