June 19, 200917 yr Thank you for the help in advance. I booted in 4.3.3 just fine. Visited Forums and realized new version. Copied onto flash bzimage and bzroot per readme. Now system hangs on bzroot dots, looks like it is about to start the server, since the dots cross most of the screen.... Reverted back to 4.3.3 and have no boot issues. Started a new parity since console said the parity was now no longer valid. Ran syslog steps.. Attaching log Light_syslog.txt Sorry, don't have a log from before the restore or able to provide 4.5 beta since it locks before the server is completely online. MSI P43 Neo3 Celeron Thanks
June 19, 200917 yr One of the possibilities whenever the boot stops while the dots are being displayed is a corrupted installation, perhaps from a bad download, or from a corrupted flash drive. The fact that the super.dat file seems to have been deleted when you reloaded v4.3.3 may also indicate file system corruption, unless you accidentally deleted it when you installed either the old or new release. You might test your flash drive in a Windows station with ScanDisk (check disk), then download again, and extract and install bzroot, bzimage, and memtest again to the flash. You may also want to read over the relevant tips in the bottom section of the USB Flash Drive Preparation page. It's possible that you need to redo your flash drive with a newer syslinux.exe. By the way, it's probably too late now, but you could have used the Trust My Array procedure to quickly bring your array back up, without having to rebuild the parity info. How many lines of dots do you see before it hangs?
June 19, 200917 yr Author Thank you Robj for the very prompt reply. Great news/ update. I just finished re-doing my lexar flash... from scratch. Copied the whole 4.5 beta6 and boooted without a problem... re-configured name of server from "tower" to "light" and assigned the devices as before. Currently running a new parity. I expect to be fully up and running after the parity completes. FYi, I did delete the super.dat file you mentioned, but only after the initial file copy of bizimage and bizroot to upgrade had failed. I have no idea why my system did not like the jump from 4.3.3 to 4.5, but now all is good. I basicaly started from scratch. The data should be fine, just the hours to do a parity. A good idea since the server has been off for 4 months while I traveled. Thanks again for the very prompt and spot on troubleshooting. Bernard
June 19, 200917 yr Author Hello I have an additional question based on the system log. This is my first time reading one, so just to be safe.... Log is split in 2 parts. Disk4 reports errors: Does the log indicate that these are "cable" errors or a possible indication of HD failure? Is there anything else in the log out of the ordinary? Thanks for the expert assistance. B
June 19, 200917 yr Part2 of syslog Can you get a smartctl report on that failing drive? smartctl -a -d ata /dev/sdd The first error seems to be a "media error" everything after that seems consistent with the inability to read data from the drive. un 19 02:33:41 Light kernel: ata4.00: configured for UDMA/133 Jun 19 02:33:41 Light kernel: ata4: EH complete Jun 19 02:33:43 Light kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jun 19 02:33:43 Light kernel: ata4.00: irq_stat 0x40000001 Jun 19 02:33:43 Light kernel: ata4.00: cmd 25/00:00:e7:8b:e2/00:04:1c:00:00/e0 tag 0 dma 524288 in Jun 19 02:33:43 Light kernel: res 51/40:00:f5:8b:e2/00:00:1c:00:00/e0 Emask 0x9 (media error) Jun 19 02:33:43 Light kernel: ata4.00: status: { DRDY ERR } Jun 19 02:33:43 Light kernel: ata4.00: error: { UNC } My best guess will be a bad drive, but I'd first want to see a smartctl report on the drive before discounting the cable... It is just that with a serial cable to the drive, if the cable is bad, drive communication and timeout errors are more likely if it is recognized by the BIOS at all. Also, the UNC (uncorrectable) error is described as being frequently due to bad sectors on the disk in the ATA Wiki http://ata.wiki.kernel.org/index.php/Libata_error_messages Uncorrectable error - often due to bad sectors on the disk Joe L.
June 20, 200917 yr Author Thanks Joe Here is the log you requested... root@Light:~# smartctl -a -d ata /dev/sdd 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: MAXTOR STM3500630AS Serial Number: 9QG3S5AG Firmware Version: 3.AAE User Capacity: 500,106,780,160 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Fri Jun 19 20:12:28 2009 GMT+5 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: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 430) 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: ( 163) minutes. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 118 089 006 Pre-fail Always - 0 3 Spin_Up_Time 0x0003 093 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 505 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 5 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 31315979 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1022 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 548 187 Reported_Uncorrect 0x0032 074 074 000 Old_age Always - 26 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 075 062 045 Old_age Always - 25 (Lifetime Min/Max 25/25) 194 Temperature_Celsius 0x0022 025 040 000 Old_age Always - 25 (0 20 0 0) 195 Hardware_ECC_Recovered 0x001a 074 060 000 Old_age Always - 10 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 2 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 2 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 76 (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 76 occurred at disk power-on lifetime: 1015 hours (42 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 00 54 9f e2 e0 Error: UNC at LBA = 0x00e29f54 = 14851924 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 e7 9c e2 e0 00 03:02:01.936 READ DMA EXT 27 00 00 00 00 00 e0 00 03:02:01.936 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 03:02:01.878 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 03:02:01.877 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 03:01:59.825 READ NATIVE MAX ADDRESS EXT Error 75 occurred at disk power-on lifetime: 1015 hours (42 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 00 54 9f e2 e0 Error: UNC at LBA = 0x00e29f54 = 14851924 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 e7 9c e2 e0 00 03:01:57.538 READ DMA EXT 27 00 00 00 00 00 e0 00 03:01:55.486 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 03:01:55.429 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 03:01:55.428 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 03:01:59.825 READ NATIVE MAX ADDRESS EXT Error 74 occurred at disk power-on lifetime: 1015 hours (42 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 00 54 9f e2 e0 Error: UNC at LBA = 0x00e29f54 = 14851924 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 e7 9c e2 e0 00 03:01:57.538 READ DMA EXT 27 00 00 00 00 00 e0 00 03:01:55.486 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 03:01:55.429 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 03:01:55.428 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 03:01:55.428 READ NATIVE MAX ADDRESS EXT Error 73 occurred at disk power-on lifetime: 1015 hours (42 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 00 54 9f e2 e0 Error: UNC at LBA = 0x00e29f54 = 14851924 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 e7 9c e2 e0 00 03:01:51.090 READ DMA EXT 27 00 00 00 00 00 e0 00 03:01:55.486 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 03:01:55.429 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 03:01:55.428 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 03:01:55.428 READ NATIVE MAX ADDRESS EXT Error 72 occurred at disk power-on lifetime: 1015 hours (42 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 00 54 9f e2 e0 Error: UNC at LBA = 0x00e29f54 = 14851924 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 e7 9c e2 e0 00 03:01:51.090 READ DMA EXT 27 00 00 00 00 00 e0 00 03:01:51.089 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 03:01:51.089 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 03:01:51.031 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 03:01:51.031 READ NATIVE MAX ADDRESS EXT SMART Self-test log structure revision number 1 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.
June 20, 200917 yr You have some bad sectors on this drive, rather tightly clustered around the 240GB point I believe. It's not completely clear from the SMART report (especially when you compare with the syslog) exactly how many are bad, and some may still be recoverable, because they are marked "Pending". I would run a SMART long test on the drive, see the bottom of the Obtaining a SMART report section. You will want to run this command, and it will take awhile: smartctl -d ata -tlong /dev/sdd Once the drive has finished the test (perhaps run it overnight), then obtain another SMART report, and we can compare it with the earlier one.
June 20, 200917 yr Author Thanks RobJ Ran your requested command smartctl -d ata -tlong /dev/sdd followed today by the smart log.... smartctl -a -d ata /dev/sdd Result: === START OF INFORMATION SECTION === Device Model: MAXTOR STM3500630AS Serial Number: 9QG3S5AG Firmware Version: 3.AAE User Capacity: 500,106,780,160 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sat Jun 20 10:26:19 2009 GMT+5 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: ( 430) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off supp ort. 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: ( 163) minutes. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_ FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 118 089 006 Pre-fail Always - 0 3 Spin_Up_Time 0x0003 093 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 507 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 5 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 31316276 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1031 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 549 187 Reported_Uncorrect 0x0032 074 074 000 Old_age Always - 26 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 065 062 045 Old_age Always - 35 (Lifetime Min/Max 29/35) 194 Temperature_Celsius 0x0022 035 040 000 Old_age Always - 35 (0 20 0 0) 195 Hardware_ECC_Recovered 0x001a 074 060 000 Old_age Always - 48896 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 2 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 2 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 76 (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 76 occurred at disk power-on lifetime: 1015 hours (42 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 00 54 9f e2 e0 Error: UNC at LBA = 0x00e29f54 = 14851924 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 e7 9c e2 e0 00 03:02:01.936 READ DMA EXT 27 00 00 00 00 00 e0 00 03:02:01.936 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 03:02:01.878 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 03:02:01.877 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 03:01:59.825 READ NATIVE MAX ADDRESS EXT Error 75 occurred at disk power-on lifetime: 1015 hours (42 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 00 54 9f e2 e0 Error: UNC at LBA = 0x00e29f54 = 14851924 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 e7 9c e2 e0 00 03:01:57.538 READ DMA EXT 27 00 00 00 00 00 e0 00 03:01:55.486 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 03:01:55.429 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 03:01:55.428 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 03:01:59.825 READ NATIVE MAX ADDRESS EXT Error 74 occurred at disk power-on lifetime: 1015 hours (42 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 00 54 9f e2 e0 Error: UNC at LBA = 0x00e29f54 = 14851924 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 e7 9c e2 e0 00 03:01:57.538 READ DMA EXT 27 00 00 00 00 00 e0 00 03:01:55.486 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 03:01:55.429 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 03:01:55.428 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 03:01:55.428 READ NATIVE MAX ADDRESS EXT Error 73 occurred at disk power-on lifetime: 1015 hours (42 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 00 54 9f e2 e0 Error: UNC at LBA = 0x00e29f54 = 14851924 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 e7 9c e2 e0 00 03:01:51.090 READ DMA EXT 27 00 00 00 00 00 e0 00 03:01:55.486 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 03:01:55.429 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 03:01:55.428 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 03:01:55.428 READ NATIVE MAX ADDRESS EXT Error 72 occurred at disk power-on lifetime: 1015 hours (42 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 00 54 9f e2 e0 Error: UNC at LBA = 0x00e29f54 = 14851924 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 e7 9c e2 e0 00 03:01:51.090 READ DMA EXT 27 00 00 00 00 00 e0 00 03:01:51.089 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 03:01:51.089 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 03:01:51.031 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 03:01:51.031 READ NATIVE MAX ADDRESS EXT SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA _of_first_error # 1 Extended offline Completed: read failure 90% 1022 484 613972 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.
June 20, 200917 yr Result is a little frustrating! It did not finish the test, failed at 90%. At first, I thought this must be another of those early failures often reported in the PreClear thread, but found that this was not a host abort, but a "read failure", and the sector it stopped at was one of those in the range listed in the syslog as bad sectors. That is not good. Perhaps because it did not finish the full test, it did not fully update the SMART parameters or deal with the 'Current Pending'. It did not change the drive health status to Fail, but I don't know if that is because the test did not finish, or it did not think the read failure is serious enough. Run the SMART short test, replace -tlong with -tshort, and let's see what it says on the report after that. It only takes a few minutes, I think. Apart from the abort when it hit one of the bad sectors, there do not appear to be any new problems reported. After the short test, this may be a good time to run the read-only version of the Parity check, to force a read of all sectors, but not corrupt the parity info. JoeL has some instructions somewhere, but I can't remember where. Needs to be added to the Wiki.
July 2, 200917 yr Author Update: I will run the suggestions after the 4th of July. Going to be on the road for another 2 weeks. Probably will RMA the drive to Maxtor as soon as possible once all is confirmed. Thanks again for the assistance. Have a great 4th if in the US. B.
Archived
This topic is now archived and is closed to further replies.