It was Friday morning i had a phone call from my customer who had trouble accessing there file server "N5200" Raid 5.
Logging into the Web service i noticed that the SMB service was in a "stopped" state.
I proceeded to go to services & enable it again which it did just fine, it then told me to reboot/shutdown as i did, after rebooting the system had not changed & the SMB service was still in the "stopped" state. After some playing around i realised that no matter which setting i changed it would not accept it, date/info/anything..
At this point it was running firmware 1.00.07 so i thought ok will upgrade it to the latest firmware and see how this goes, from here on it only made things worse.
It failed to apply the firmware update to 2.00.08. Reading up on how to apply a firmware update using a usb stick i followed that procedure in which it completed and now the N5200 has 2.00.08 installed.
Problem is now that the web interface is totaly screwy & all the web interface is hardly recognisable. Trying a differant browser istead of IE7, Firefox was little better. Trying a differant system altogether with IE6 running XP pro it made no differance either. I was able to try and enable the SMB service once again with no luck.
Luckily the company had a spare N5200 that had failed months prior and had gone back for repair so we swapped the RAID 5 drives into the spare N5200 and resumed off.
Now i'm stuck with another N5200 that has failed whithin 2 months of each other & only 3 months old.
after flashin to 2.00.08 the Webinterface was "scrambled" here, too. Used all browsers that are avaible on the MAC. Nothing helped. My N5200 is at the night off. After shutdown the N5200 and start it at the next morning again, all was finde.
I read some other posts where people from really early FW's are getting this issue so Im wondering if the upgrade to 08 is really only safe if your going from an incremental .04 to .08. i.e its not liking jumping 3 or 4 firmware updates.
It shouldnt matter, but maybe its expecting something on the disk or there is a compatibility issue with how the disk was originally setup in the old firmware and its expecting a prior firmware which wasnt apply to have tweaked it somehow.