kc1 wrote:Not true. I ordered this disk as soon as the error showed up. The count rose to that level in the 3 days it took for the disk to arrive.
When a disk is clearly failing, some will shutdown their NAS units as a precaution to minimise the risk of running into problems or take the opportunity then to ensure their backup is up to date.
kc1 wrote:...and how would I know I was having problems with multiple disks if the NAS only told me about one of them?
The NAS runs short online SMART tests daily. These normally pickup a problem disk but they won't always. That's one reason why backups are important.
kc1 wrote:"one" being who? a Tech? How would a regular know about this? In any case there weren't any SMART errors on disk 3mdgm wrote:3) One would think there would be info in a disk_smart log or one of the other ones indicating the problem if they are also problematic.
There are several logs in the zip file that is downloaded. Normally on the rare occasion when a serious problem is encountered a tech can look at the logs and if necessary remotely login to the NAS unit and find a way to rectify the problem but sometimes problems are encountered where this isn't possible.
kc1 wrote:lol! so if it's not "dead" why would it say "dead"?!mdgm wrote:4) It depends how dead it is
A disk is considered dead if it repeatedly fails to respond or fails the SMART self assessment test.
Now such a disk may be able to be read but it may take multiple attempts to read the data. Think of a car that takes multiple attempts to start. It's in a bad way but it's not completely useless. In those cases dd_rescue can be used to clone the disk onto a new one. It will make multiple attempts to read the data. You can even run the clone to read the disk backwards if reading the disk forwards is problematic. Cloning onto a good disk in working order depending on the situation (how badly the dead disk has failed) this can be enough to be able to recover data.
mdgm wrote: the issue is the ReadyNas not reporting multiple disk failures - or in fact causing them.
When you replace a dead/failing disk heavy stress is put on all disks. If a second disk is failing the resync can finish it off. The resync is necessary to rebuild the RAID (disks need to be synced sector by sector).
mdgm wrote: ...they're all on this list
Wasn't suggesting they weren't. If things work fine with new drives then one would just put the problem down to the old drives.
mdgm wrote:Will see what samsung/seagate tools throw up, but like I said - it won't be much use diagnostically now if indeed the NAS caused it to fail.
One could also say using a car caused the tyres or some other part to wear out.