3 drive failures w/in 10 days of 4.2.22 upgrade? #19570015

Just another 3 drive failures in 10 days story all of which stared the week after 4.2.22 on an XRaid 2 Pro Pioneer Edition Dual Redundant 6 disks ... Again couldn't replace them with RMA units quick enough so bought new drives which failed to be recognised despite being on the HCL. Ended up in 'life support mode' briefly. L2 support were great and really helped. They found an fsck problem which needed L3 support - L3 were hopeless at communicating and expected me to leave ports 22, 23 and 443 open on the firewall as well as their support software running 24/7 on a PC. I had no feedback from them at all despite them having my mobile, landline and email address which L2 seemed to find easy to use. After week of seeing random people log in and issue commands to a NAS in Telnet mode (and therefore completely offline to normal use) I did an 4.2.22 OS reinstall from the boot menu after re-downloading it and installing from Frontview, full advanced SEATOOL checks on all 6 drives (no errors) and a factory reset followed by restore of 4.2Tb of backup (because we ALL have up to date backups don't we...). I closed all the ports on the firewall too ;-)

All was fine until tonight when the same errors as noted above started happening on spinup but on one of the new disks. So I've downgraded to 4.2.21 and disabled spindown and will be keeping a close eye on things. I agree that the apparent error sounds like disks but as someone's already said there is a lot of quacking noise going on here...

If you don't have a full backup I would suggest yesterday was a good time to start it..

Mike