July 31, 201213 yr I had a drive having some read errors, I was anxious to try the new WD RED series so I decided to replace the 2TB WD EARS with a 3TB RED. I precleared the 3TF RED thoroughly (3 passes, no errors), removed the 2TB and assigned the RED to the same slot. PArity rebuilded the 3TB and array was functioning fine. I then started to preclear the 2TB EARS using the following chain of commands: cd /boot screen ./preclear_disk.sh -M 3 -c 3 /dev/sd? preclear started at 16:38 and was running fine. At 17:52 I got an Array fault message (did not notice until 20 minutes later). The parity drive redballed. At 18:10 preclear reported finish of pre-read and start of zeroing At 18:10 preclear also gave me a PASS on cycle 1of3 of the preclear. Now ofcourse preclear could never have been finished. I am attaching the preclear reports. The parity drive is a few months old and had no smart errors before so I figured a possible issue with cabling (I was changing the sata cabling of the new RED drive just before), I however did not find anything "loose".. I restarted the array, array did not restart but was still stopped, I had to re-assign the parity drive and unraid reported the parity drive was a new drive, I had to click parity sync and it is now rebuilding parity. Two things: - Why is unraid now forcing a parity sync ? It keeps my array unprotected for something like 24 hours, should it not have found the drive to be ready to be used (especially if a cable was loose or something) - The preclear thing is also weird, especially because both things happened at the same time as the parity drive redball, could there be some kind of conflict going on ? Note: I know preclear is not part of the main package but since I also have the parity sync thing I thought it opportuun to post in this area. Attributes for the parity drive: ID# ATTRIBUTE NAME FLAG VALUE WORST THRESH TYPE UPDATED FAILED RAW VALUE 1 Raw Read Error Rate 0x000b 100 100 016 Pre-fail Always Never 0 2 Throughput Performance 0x0005 134 134 054 Pre-fail Offline Never 112 3 Spin Up Time 0x0007 127 127 024 Pre-fail Always Never 549 (Average 550) 4 Start Stop Count 0x0012 100 100 000 Old age Always Never 550 5 Reallocated Sector Ct 0x0033 100 100 005 Pre-fail Always Never 0 7 Seek Error Rate 0x000b 100 100 067 Pre-fail Always Never 0 8 Seek Time Performance 0x0005 132 132 020 Pre-fail Offline Never 32 9 Power On Hours 0x0012 100 100 000 Old age Always Never 2472 10 Spin Retry Count 0x0013 100 100 060 Pre-fail Always Never 0 12 Power Cycle Count 0x0032 100 100 000 Old age Always Never 20 192 Power-Off Retract Count 0x0032 100 100 000 Old age Always Never 550 193 Load Cycle Count 0x0012 100 100 000 Old age Always Never 550 194 Temperature Celsius 0x0002 146 146 000 Old age Always Never 41 (Min/Max 22/43) 196 Reallocated Event Count 0x0032 100 100 000 Old age Always Never 0 197 Current Pending Sector 0x0022 100 100 000 Old age Always Never 0 198 Offline Uncorrectable 0x0008 100 100 000 Old age Offline Never 0 199 UDMA CRC Error Count 0x000a 200 200 000 Old age Always Never 0 Herewith the output of the array not started mail: This message is a status update for unRAID Tower ----------------------------------------------------------------- Server Name: Tower IP: 192.168.1.14 Status: unRaid array not started. Status: The unRaid array needs attention. One or more disks are disabled or invalid. Date: Tue Jul 31 18:46:27 CEST 2012 Disk Temperature Status ----------------------------------------------------------------- Parity Disk [sdk]: 41C (DiskId: Hitachi_HDS5C3030ALA630_MJ1311YNG60RUA) Disk 1 [sdi]: 34C (DiskId: WDC_WD20EARS-00J2GB0_WD-WCAYY0285356) Disk 2 [sdd]: 35C (DiskId: WDC_WD20EADS-22R6B0_WD-WCAVY1682497) Disk 3 [sdc]: 33C (DiskId: WDC_WD20EARS-00MVWB0_WD-WMAZA3233512) Disk 4 [sdg]: Not-Reported (DiskId: WDC_WD20EARS-60MVWB0_WD-WCAZA8452751) Disk 5 [sdh]: Not-Reported (DiskId: WDC_WD20EARS-60MVWB0_WD-WCAZA8452711) Disk 6 [sdf]: 33C (DiskId: WDC_WD20EARS-00MVWB0_WD-WCAZA4913598) Disk 7 [sdl]: 40C (DiskId: WDC_WD20EARX-00PASB0_WD-WCAZAD290617) Disk 8 [sda]: 36C (DiskId: WDC_WD30EFRX-68AX9N0_WD-WMC1T0076253) Disk SMART Health Status ----------------------------------------------------------------- Parity Disk PASSED (DiskId: Hitachi_HDS5C3030ALA630_MJ1311YNG60RUA) Disk 1 PASSED (DiskId: WDC_WD20EARS-00J2GB0_WD-WCAYY0285356) Disk 2 PASSED (DiskId: WDC_WD20EADS-22R6B0_WD-WCAVY1682497) Disk 3 PASSED (DiskId: WDC_WD20EARS-00MVWB0_WD-WMAZA3233512) Disk 4 PASSED (DiskId: WDC_WD20EARS-60MVWB0_WD-WCAZA8452751) Disk 5 PASSED (DiskId: WDC_WD20EARS-60MVWB0_WD-WCAZA8452711) Disk 6 PASSED (DiskId: WDC_WD20EARS-00MVWB0_WD-WCAZA4913598) Disk 7 PASSED (DiskId: WDC_WD20EARX-00PASB0_WD-WCAZAD290617) Disk 8 PASSED (DiskId: WDC_WD30EFRX-68AX9N0_WD-WMC1T0076253) Output of /proc/mdcmd: ----------------------------------------------------------------- sbName=/boot/config/super.dat sbVersion=2.1.3 sbCreated=1329766103 sbUpdated=1343752018 sbEvents=156 sbState=1 sbNumDisks=9 sbSynced=0 sbSyncErrs=0 mdVersion=2.1.4 mdState=RECON_DISK mdNumProtected=9 mdNumDisabled=1 mdDisabledDisk=0 mdNumInvalid=1 mdInvalidDisk=0 mdNumMissing=0 mdMissingDisk=0 mdNumNew=0 mdResync=0 mdResyncCorr=0 mdResyncPos=0 mdResyncDt=0 mdResyncDb=0 diskNumber.0=0 diskName.0= diskSize.0=0 diskState.0=4 diskId.0=Hitachi_HDS5C3030ALA630_MJ1311YNG60RUA rdevNumber.0=0 rdevStatus.0=DISK_DSBL_NEW rdevName.0=sdk rdevSize.0=2930266532 rdevId.0=Hitachi_HDS5C3030ALA630_MJ1311YNG60RUA rdevNumErrors.0=0 rdevLastIO.0=1343753176 rdevSpinupGroup.0=0 diskNumber.1=1 diskName.1=md1 diskSize.1=1953514552 diskState.1=7 diskId.1=WDC_WD20EARS-00J2GB0_WD-WCAYY0285356 rdevNumber.1=1 rdevStatus.1=DISK_OK rdevName.1=sdi rdevSize.1=1953514552 rdevId.1=WDC_WD20EARS-00J2GB0_WD-WCAYY0285356 rdevNumErrors.1=0 rdevLastIO.1=1343753176 rdevSpinupGroup.1=0 diskNumber.2=2 diskName.2=md2 diskSize.2=1953514552 diskState.2=7 diskId.2=WDC_WD20EADS-22R6B0_WD-WCAVY1682497 rdevNumber.2=2 rdevStatus.2=DISK_OK rdevName.2=sdd rdevSize.2=1953514552 rdevId.2=WDC_WD20EADS-22R6B0_WD-WCAVY1682497 rdevNumErrors.2=0 rdevLastIO.2=1343753176 rdevSpinupGroup.2=0 diskNumber.3=3 diskName.3=md3 diskSize.3=1953514552 diskState.3=7 diskId.3=WDC_WD20EARS-00MVWB0_WD-WMAZA3233512 rdevNumber.3=3 rdevStatus.3=DISK_OK rdevName.3=sdc rdevSize.3=1953514552 rdevId.3=WDC_WD20EARS-00MVWB0_WD-WMAZA3233512 rdevNumErrors.3=0 rdevLastIO.3=1343753176 rdevSpinupGroup.3=0 diskNumber.4=4 diskName.4=md4 diskSize.4=1953514552 diskState.4=7 diskId.4=WDC_WD20EARS-60MVWB0_WD-WCAZA8452751 rdevNumber.4=4 rdevStatus.4=DISK_OK rdevName.4=sdg rdevSize.4=1953514552 rdevId.4=WDC_WD20EARS-60MVWB0_WD-WCAZA8452751 rdevNumErrors.4=0 rdevLastIO.4=1343753176 rdevSpinupGroup.4=0 diskNumber.5=5 diskName.5=md5 diskSize.5=1953514552 diskState.5=7 diskId.5=WDC_WD20EARS-60MVWB0_WD-WCAZA8452711 rdevNumber.5=5 rdevStatus.5=DISK_OK rdevName.5=sdh rdevSize.5=1953514552 rdevId.5=WDC_WD20EARS-60MVWB0_WD-WCAZA8452711 rdevNumErrors.5=0 rdevLastIO.5=1343753176 rdevSpinupGroup.5=0 diskNumber.6=6 diskName.6=md6 diskSize.6=1953514552 diskState.6=7 diskId.6=WDC_WD20EARS-00MVWB0_WD-WCAZA4913598 rdevNumber.6=6 rdevStatus.6=DISK_OK rdevName.6=sdf rdevSize.6=1953514552 rdevId.6=WDC_WD20EARS-00MVWB0_WD-WCAZA4913598 rdevNumErrors.6=0 rdevLastIO.6=1343753176 rdevSpinupGroup.6=0 diskNumber.7=7 diskName.7=md7 diskSize.7=1953514552 diskState.7=7 diskId.7=WDC_WD20EARX-00PASB0_WD-WCAZAD290617 rdevNumber.7=7 rdevStatus.7=DISK_OK rdevName.7=sdl rdevSize.7=1953514552 rdevId.7=WDC_WD20EARX-00PASB0_WD-WCAZAD290617 rdevNumErrors.7=0 rdevLastIO.7=1343753176 rdevSpinupGroup.7=0 diskNumber.8=8 diskName.8=md8 diskSize.8=2930266532 diskState.8=7 diskId.8=WDC_WD30EFRX-68AX9N0_WD-WMC1T0076253 rdevNumber.8=8 rdevStatus.8=DISK_OK rdevName.8=sda rdevSize.8=2930266532 rdevId.8=WDC_WD30EFRX-68AX9N0_WD-WMC1T0076253 rdevNumErrors.8=0 rdevLastIO.8=1343753176 rdevSpinupGroup.8=0 diskNumber.9=9 diskName.9= diskSize.9=0 diskState.9=0 diskId.9=_ rdevNumber.9=9 rdevStatus.9=DISK_NP rdevName.9= rdevSize.9=0 rdevId.9= rdevNumErrors.9=0 rdevLastIO.9=0 rdevSpinupGroup.9=0 diskNumber.10=10 diskName.10= diskSize.10=0 diskState.10=0 diskId.10=_ rdevNumber.10=10 rdevStatus.10=DISK_NP rdevName.10= rdevSize.10=0 rdevId.10= rdevNumErrors.10=0 rdevLastIO.10=0 rdevSpinupGroup.10=0 diskNumber.11=11 diskName.11= diskSize.11=0 diskState.11=0 diskId.11=_ rdevNumber.11=11 rdevStatus.11=DISK_NP rdevName.11= rdevSize.11=0 rdevId.11= rdevNumErrors.11=0 rdevLastIO.11=0 rdevSpinupGroup.11=0 diskNumber.12=12 diskName.12= diskSize.12=0 diskState.12=0 diskId.12=_ rdevNumber.12=12 rdevStatus.12=DISK_NP rdevName.12= rdevSize.12=0 rdevId.12= rdevNumErrors.12=0 rdevLastIO.12=0 rdevSpinupGroup.12=0 diskNumber.13=13 diskName.13= diskSize.13=0 diskState.13=0 diskId.13=_ rdevNumber.13=13 rdevStatus.13=DISK_NP rdevName.13= rdevSize.13=0 rdevId.13= rdevNumErrors.13=0 rdevLastIO.13=0 rdevSpinupGroup.13=0 diskNumber.14=14 diskName.14= diskSize.14=0 diskState.14=0 diskId.14=_ rdevNumber.14=14 rdevStatus.14=DISK_NP rdevName.14= rdevSize.14=0 rdevId.14= rdevNumErrors.14=0 rdevLastIO.14=0 rdevSpinupGroup.14=0 diskNumber.15=15 diskName.15= diskSize.15=0 diskState.15=0 diskId.15=_ rdevNumber.15=15 rdevStatus.15=DISK_NP rdevName.15= rdevSize.15=0 rdevId.15= rdevNumErrors.15=0 rdevLastIO.15=0 rdevSpinupGroup.15=0 diskNumber.16=16 diskName.16= diskSize.16=0 diskState.16=0 diskId.16=_ rdevNumber.16=16 rdevStatus.16=DISK_NP rdevName.16= rdevSize.16=0 rdevId.16= rdevNumErrors.16=0 rdevLastIO.16=0 rdevSpinupGroup.16=0 diskNumber.17=17 diskName.17= diskSize.17=0 diskState.17=0 diskId.17=_ rdevNumber.17=17 rdevStatus.17=DISK_NP rdevName.17= rdevSize.17=0 rdevId.17= rdevNumErrors.17=0 rdevLastIO.17=0 rdevSpinupGroup.17=0 diskNumber.18=18 diskName.18= diskSize.18=0 diskState.18=0 diskId.18=_ rdevNumber.18=18 rdevStatus.18=DISK_NP rdevName.18= rdevSize.18=0 rdevId.18= rdevNumErrors.18=0 rdevLastIO.18=0 rdevSpinupGroup.18=0 diskNumber.19=19 diskName.19= diskSize.19=0 diskState.19=0 diskId.19=_ rdevNumber.19=19 rdevStatus.19=DISK_NP rdevName.19= rdevSize.19=0 rdevId.19= rdevNumErrors.19=0 rdevLastIO.19=0 rdevSpinupGroup.19=0 diskNumber.20=20 diskName.20= diskSize.20=0 diskState.20=0 diskId.20=_ rdevNumber.20=20 rdevStatus.20=DISK_NP rdevName.20= rdevSize.20=0 rdevId.20= rdevNumErrors.20=0 rdevLastIO.20=0 rdevSpinupGroup.20=0 diskNumber.21=21 diskName.21= diskSize.21=0 diskState.21=0 diskId.21= rdevNumber.21=21 rdevStatus.21=DISK_NP rdevName.21= rdevSize.21=0 rdevId.21= rdevNumErrors.21=0 rdevLastIO.21=0 rdevSpinupGroup.21=0 diskNumber.22=22 diskName.22= diskSize.22=0 diskState.22=0 diskId.22= rdevNumber.22=22 rdevStatus.22=DISK_NP rdevName.22= rdevSize.22=0 rdevId.22= rdevNumErrors.22=0 rdevLastIO.22=0 rdevSpinupGroup.22=0 diskNumber.23=23 diskName.23= diskSize.23=0 diskState.23=0 diskId.23= rdevNumber.23=23 rdevStatus.23=DISK_NP rdevName.23= rdevSize.23=0 rdevId.23= rdevNumErrors.23=0 rdevLastIO.23=0 rdevSpinupGroup.23=0 At the moment parity sync is commencing without errors and I am not going to touch the preclear, at least till it has finished, then I will retest if someone feels that might be worthwhile. preclear_start__WD-WCAVY0959650_2012-07-31.txt preclear_finish__WD-WCAVY0959650_2012-07-31.txt preclear_rpt__WD-WCAVY0959650_2012-07-31.txt syslog.txt
July 31, 201213 yr cd /boot screen ./preclear_disk.sh -M 3 -c 3 /dev/sd? I'm certainly no expert, but I have to assume that's a transcription error, right? You didn't specify the drive to preclear... Unless a "?" is a wildcard character to preclear any drive that has not yet been? It sure would suck if that was short hand to say "PreClear all my drives"!
July 31, 201213 yr Author That is transcription, I copied and pasted from my command reminder pages. i precleared the correct drive. A drive part of the array will nor preclear also (safety mechanism) Sent from my iPad using Tapatalk HD
July 31, 201213 yr That is transcription, I copied and pasted from my command reminder pages. i precleared the correct drive. A drive part of the array will nor preclear also (safety mechanism) Sent from my iPad using Tapatalk HD Well, you got lucky. The "bash" shell will expand that wild-card "?" to /dev/sda /dev/sdb /dev/sdc /dev/sde (every drive in the box) The preclear script uses the first one in the list. (It does not error if extra arguments are supplied... although I suppose I can add that test to prevent a gross error some day by another mis-imformed user) To prove it, at the command line type: echo /dev/sd? and see what prints. Joe L.
August 1, 201213 yr Author Nope did not get lucky... I did not start the command with the wildcard (did some unix in the way-long-ago), I started it with the correct drive name. I only copied the command from a file i keep (attached) in which I store commands to use in various cirumstances. Any comments on the situation from anyone ? resync of parity is now half way done with no errors on the drive, smart also is ok so nothing physically would appear to be wrong with the drive.. Unraid_stuff.txt
August 3, 201213 yr Author Parity rebuild has finished and my array is back up and running without issues. I however do not dare trying that preclear again.. I'll get the disk out and have it go through a few testing cycles from my windows box first.
Archived
This topic is now archived and is closed to further replies.