I had 3 1TB disks and was doing an upgrade to 3 2TB disks.
Over 2 days, I replaced a disk a night, letting it sync overnight.
Last night I replaced the final 1TB drive. Eight hours later the drive was synced. I chose to wait until the next night to reboot the NAS to do the expansion, knowing it would take several hours.
It had been working fine all day, but when I went to reboot using Raidar, I discovered this message:
Disk fail event occurred on SATA channel 3. If the failed disk is used in a RAID level 1, 5, or X-RAID volume, please note that volume is now unprotected, and an additional disk failure may render that volume dead.
I went ahead and rebooted but it never got past the Rebooting... message. So, I hotswapped the 3rd drive with the 1TB drive I had in there before. After a short while, I got this message:
Access to the disk on channel (??) is producing I/O errors. Although the array is still redundant, please replace this drive as soon as possible, as it is likely to fail soon
Now the logs say:
Sun Feb 24 23:40:16 CST 2013 RAID sync started on volume C. Sun Feb 24 23:41:45 CST 2013 System is up.
And the 3rd disk light is flashing but I can still access my shares. According to the Health screen, disk 3's status is "Resync".
I think the problem is with the new disk3, you can use a disk tool to test it. If you want to upgrade the volume, you need to put a fine 2T disk on bay3.
Start with Vendor tools (Seatools for Seagate, Lifeguard for Western Digital). If you also want to browse the SMART parameters, you can use Acronis Disk Monitor.
Is there an easy way to cut and paste those SMART stats from Acronis? All the stats say OK, but is there something in particular I should be looking for?
The drive is a Seagate ST2000DM001-1CH164, Barracuda 2TB drive, just purchased.
If FW on the drive label means Firmware, then the version is CC26.
Raw Value Value Threshold Status Reallocated Sectors = 0 100 10 OK Current Pend Sect Count = 0 100 0 OK Uncorrectable Sect Count = 0 100 0 OK Command Timeout = 0 100 0 OK
The Seagate site says "No newer firmware available"
That worries me, because I've bought 3 of them to replace the drives I had in my NV+. Two of them are in there already. I only had problems with the last one.
If you can do an exchange with the reseller, that might be one option. That is, leave the working drives alone, and exchange the non-working one for a WD20EFRX.
We Replace disks at 50 Reallocated Sectors or above, and at above 1 ATA error. Thats if you purchased NAS with disks. It could be a bad slot - Try the following. (1) If you have a known good disk that is compatible with the NAS. Turn the NAS off. Take out all disks and remember their order. Put in that 1 disk in that slot. Go to Factory Default it throught the Boot Menu (http://www.kossboss.com/rnasbootmenu). Dont worry about factory defaulting - I wouldnt have you do something that would hurt your data - the config is on your old disks that are sitting out of the NAS.NOTE: Factory defaulting with 1 known good drive in 1 slot should take no more than 10 to 15 minutes.Anyhow after the boot menu Once you select Factory Default open up RAIDAR and hit rescan until you seee that NAS with the bold Setup comment on the right most column. Press Setup button and do XRAID and hit Apply. If the NAS comes up with that disk we know the slot is good and the disk that you had problems with is bad To bring NAS back in the way it was: Turn off NAS, Put in all the good disks back in NAS in same order, questionable disk on the Side - not in the nas. Turn NAS on - voila there is your old setup - as if you never did a factory default
(2) Take that disk connect up to PC and run Comprehensive Diagnostic with the manufacturers tools - SeaTools
(3) Turn off NAS, take disks out remember order. Take questionable disk and put it in known good slot. Factory Default thru boot menu. Go to Raidar, hit rescan once you see nas, hit Setup. Do XRAID if it works it works the disk is good the slot is bad. To bring NAS back in the way it was: Turn off NAS, Put in all the good disks back in NAS in same order, questionable disk on the Side - not in the nas. Turn NAS on - voila there is your old setup - as if you never did a factory default
If you come to the conclusion the slot is bad call in support so we can check warranty and RMA the chassis. If you come to the conclusion the disk is bad call in support if that disk came with your NAS - if not buy new disk or call disk manufacturer for RMA
...If you have a known good disk that is compatible with the NAS...
That is the question at the end of the day: Is the ST2000DM001 really compatible with the NAS? Yes, it's on the HCL. But it seems obvious that the Netgear testing did not (and does not) include all the drive submodels.
Kossboss - he's already gone down the seatools route. I agree it is reasonable (though tedious) to test the various NAS slots.
network23 - if you want to do this, you can skip kossboss' step 2, since seatools already is known to pass.
Do you think there is any point to putting it back into the NAS and see if it works a second time?
Well I wouldn't put it back with your existing RAID array - there is too much risk.
Trying it by itself (all other drives removed with the power down) would let you see if the problem only happens when the disk is plugged into slot 3, or if it happens in all slots. To be certain, you'd have to confirm that it fails in slot 3 (with other slots empty) by doing a factory default with the drive in that slot. And then do it again in other slots (particularly slot 1).
Kossboss is thinking that sometimes the NAS hardware fails so that one slot doesn't work at all (or doesn't work reliably). In that case, you'd be entitled to a replacement unit. It is a possibility.
I then replaced the drive in Slot 3 with the Seagate. It resynced overnight and reported success the next morning. That evening, RAIDAR reported the drive as failed.
So, for years, I've been using that slot...ever since buying the NV+ back in 2007.
Based on that knowledge, if you still think it might be a bad slot, let me know and I will do the test you recommend. I just wanted to make sure you weren't thinking I was using the slot for the first time.
Also, FYI, after the failure, I put the original 1TB drive back in slot 3 (I had not power-cycled the NV+ yet, so it hadn't run through the expansion process yet), which resynced and everything is running fine at:
