Forum Discussion

Retired_Member

Nov 08, 2017

WARNING - Firmware Update 6.9.0

So, my NAS promted me to tell me that a firmware update was available and, upkeeping with the latest versions, I decided to go ahead and do the update via the web browser. Seems painless ...

After the update, at first glance things seemed okay, but after a while I noticed something very badly wrong. None of my SMB shares were availble, and nothing I tried worked to resolve the problem. Looking at the services page, SMB was disabled, and wouldn't enable!! Yep, that's all my music, videos, family photo's, work data - POOF!!

I enabled the SSH access (took me a few hours to get that service to enable as well!!) and after looging into the NAS via SSH (and a fair ammount of Googling) I notice every sigle file/folder on the NAS is now owned by both user:guest and group:guest. (See below screenshot of the Samba files)

drwxr-xr-x 3 root root 4096 Nov 27 2012 .
drwxr-xr-x 23 root root 4096 Sep 26 23:12 ..
-rw------- 1 guest guest 421888 Oct 2 2015 account_policy.tdb
-rw------- 1 guest guest 430080 Oct 4 2015 group_mapping.tdb
drwxr-xr-x 3 guest guest 4096 Nov 21 2012 private
-rw------- 1 guest guest 528384 Oct 2 2015 registry.tdb
-rw------- 1 guest guest 421888 Oct 2 2015 share_info.tdb

I'm now rebuilding my NAS (47 hour resync on the volume) before I can put my data back on the device. So what's my point?

People use thier NAS device as, guess what, a storage device for thier personal data. How can Netgear release such a rubbish firmware update that technically bricks a device?

C'mon Netgear, get your house in order. It's not rocket science to test your release in a lab environment before releasing it into the public! As for the support, why would I pay you to support a device you broke in the first place?!?

Installation & Upgrade

14 Replies

Replies have been turned off for this discussion

Kimera
Guide
Nov 08, 2017
You didn't told us which is the ReadyNAS OS software version that your NAS was running before the upgrade request to download and install latest ReadyNAS OS 6.9.0...also doing preliminary checking - through SSH - of most important log files would be helpful to understand what happened during/after the update (and Yes...knowing where to look for is important to have a smooth start...ranting isn't helpful).
- mdgm-ntgr
  NETGEAR Employee Retired
  Nov 08, 2017
  These symptoms are consistent with an app wrongly changing the ownership of folders/files that it shouldn’t rather than a firmware issue.
  
  Which apps do you have installed?
- Retired_Member
  Nov 08, 2017
  Here is an extract of the fwbroker.log:
  
  Oct 31 2017 17:23:06 INFO:AAGET_REMOTE_INFO(STEP 1 URL:) https://update.readynas.com/download/ReadyNASOS-arm/index?key=d4cd51e5cc36bb0736f67eb9123ae453&model=ReadyNAS&model_num=104&current_version=6.8.1
  Oct 31 2017 17:23:08 answer=info::name=ReadyNASOS,version=6.9.0,time=1507942835,size=68184064,md5sum=3ec076c7638efe8c6db2086fd44109cf,arch=arm,descr=ReadyNASOS Update,release_notes=https://kb.netgear.com/000049516/ReadyNAS-OS-6-Software-Version-6-9-0
  
  From the timestamps, the NAS was running 6.8.1 and prompted an update to 6.9.0.
  
  As for what happened next, who knows. What I can say is, the NAS worked fine before, and after the update doesn't!
  
  But hey, here's the question: why woud the /var, /sys, /etc directories need to be owned by guest? They wouldn't. If the config files for these services isn't owned by root (or at least admin) then none of the services will work.
  
  Apology for the rant, but yeah, after what should be a simple a update, needing to spend a week on data recovery does tend put you in a bad mood :-)
  
  Kudos
  - mdgm-ntgr
    NETGEAR Employee Retired
    Nov 08, 2017
    Again, this is consistent with a bad app, not a problem with the firmware. This is my experience from every time I’ve seen a customer have this issue.