4.1.9-T2 minor bug

[John Bean]

Duo, pair of 500GB Seagates (ST3500320AS and ST3500418AS), X-RAID.

First let me congratulate those responsible for the CIFS performance improvement; not only has it pushed my 100mb/s PC NIC to its limits (13mB/s from about 8 max with 4.1. but it has also fixed the Windows 7 "red cross" annoyance where the share is reported as not connected but works anyway. I'm very pleased

Anyway, to the buglet. I accidentally lost power to the Duo while tidying cables. It recovered just fine, but while it was resyncing Frontview reported the percent complete correctly but the speed was shown as zero (always) and the estimated time was an apparently random very large number, different each time I checked.

This is the first time I've caused this to happen so I have no idea what would have been displayed in an earlier version of Frontview, but what I saw today was a bit odd and I'm sure isn't what was intended.

Keep up the good... nay, *excellent* work

[John Bean]

A few minutes ago I got an email warning: "ATA error count has increased in the last day. Disk 1: Previous count: 0 Current count: 1 Growing SMART errors indicate a disk that may fail soon. If the errors continue to increase, you should be prepared to replace the disk."

I immediately looked at the SMART data in Frontview, both disks are fine and both have ATA error counts of zero.

[mdgm]

Try clearing your web browser cache (e.g. Temporary Internet Files in Internet Explorer), close your web browser, then reopen Frontview and check again

[John Bean]

I did that before posting. The reported ATA error count is zero on both disks.

[mdgm]

What time of day did you get the email? The SMART check is done at boot and also at 4am daily.

[John Bean]

The Frontview log entry is timestamped "Sat Feb 11 10:00:14 WET 2012", Google's SMTP server three seconds later: "Sat, 11 Feb 2012 02:00:17 -0800 (PST)".

[mdgm]

Is that when you normally get SMART alerts? Was that shortly after booting the NAS?

[John Bean]

I've never had a SMART alert so I don't know. The Duo has not been rebooted recently.

PS: after posting I checked the cron.d entry and the check is indeed set to execute at 4am daily.

[awk]

I have just had the smart alert on disk 2 (ATA error count has increased in the last day. Disk 2: Previous count: 0 Current count: 2)
I have taken the drive out and tested it (long and short test) and it shows the disk is fine with NO smart errors. I have also put it in my pc and it shows as healthy.
I also got the Nas to check volumes on reboot (twice now) and it says they are fine!
Is this a chassis error?

[mdgm]

Please put the disks back in the PC and run SeaTools on the disks. Run both short and long tests.

ATA errors are an indication the disk is likely failing.

[awk]

I have allready done that, twice! (It passed long and short tests with Seatools and WD Lifegaurd) I have since put all the H/D's in another Nas, set it up and it worked fine with all four drives. I then set up the original Nas with the same drives and that also reports no bad drives. I just wondered if for some reason the original Nas marked the drive as bad after spindown and by preparing them again in a raid 5 array they are now all happy, even after spindown!!
Is there really an answer??????????