NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Firmware update to os 6.5 breaks SMB on USB connections RN104 #26893300
Updated my OS6.4.2 to 6.5 on my RN104's
However after rebooting I now cannot access my USB devices on any of the usb ports using SMB on windows PC. The main device ie the NAS share/s show in windows but not the usb device.
Devices show as connected on the NAS web admin page, SMB and NFS services are running on the share
Can access the files via the web browser from the path shown I am assuming that by this method I am accessing using nfs
Tried by using the full smb url on Windows PC but no go. It would seem that smb IS NOT activated on the usb ports!
I have tried rebooting/disconnecting Nas/USB drives and PC just incase.
I reported this similar behaviour some firmware updates back I cannot remember specifically but pre 6.2.5 where the an update "broke" usb smb access.
Pretty standard USB devices WD My book and Icy box USB units
My RN104's that have not been updated to 6.4.2 are still showing the usb devices so it is not my network system
Can someone get a firmware fix ASAP or how do I go back to OS 6.4, without afactory reset I see the release notes say do not.
Well I think it is only fair that when issues are fixed that thanks be due that they are made public as forums can tend to err on the side of a "moan-fest"
I will start by thanking the member of Support that dealt with my case I hope that I am not breaking any rules by naming them, Quin Hong. I would also tlike to thank the un-named R&D engineer that was also was involved and all the support staff that were involved in resolving this issue.
Of course in the end it was an "simple" fix In fact it involved a change of order of two lines in a configuration file but tracking these sort of things down can obviously be a nightmare, but they found it.
I was even told what to do. to correct my other units.
And the final "confirmation" was to update one of the OS 6.4.2 Units to 6.5 and edit the file
YES YES YES it works
It still begs the question "why does this only show up in disk's above a certain size",
(EDIT) Just been informed that it may be due to the size of the disk that extra delay is required. By changing the two lines that gives enough response time for the disc to be "fully" mounted
I also extend my thanks to all that contributed on this thread and to mdgm who escalated this.
Once I was "in the system " Netgear showed that they can work with the customer to resolve issues
Not to sour any praise but this is a "bug" in the firmware which I was unfortunate (fortunate for any other users who this may affect at some stage) to find and this I still believe the issue was addressed intially in a less than suitable manner.
Obviously my issue was initially very specific and Netgear has many many units with operating with a myriad of third party peripherals and disks, compatibility is always going to be an issue. And there is always the variability associated with the level of "user competence". Anyway it seems to be resolved and thanks again to all involved
I understand that the change in the configuration file will be incorporated in a later firmware update.
Maybe another unit in a couple of months time!!
37 Replies
Replies have been turned off for this discussion
Checked this all ways
Turning off smb for nas main unit removes share in windows explorer, turning in back on restores OK
For attached usb, Webrowser indicates on and off status of SMB service but no actual share appears/disappears.
USB discs are is still available vis nfs service checked using linux box and confirms that not reacheable by cifs/smb from linux
SMB service is broken in 6.5.0 for usb ports on my RN104's at least (7 off)
Firmware fix required
We removed some kernel modules from the main package, so if your USBs are using XFS, then we don't mount them natively anymore without the Kernel Plus package.
but since you are using NTFS, we should pick that up. We did update the NTFS-support in 6.5.0. Did you e-mail your logs to support?
I have just updated to 6.5.0 and completely lost SMB support/access to all the internal volumes.
All works fine via web, but when I try access with Windows Explorer it fails to connect "cannot access...".
Tried turning OFF/ON, rebooting, etc. Still not working. IP adresses all ok. SMB is simply not working! Never had an issue before this update!
Please fix ASAP!! I cannot use the NAS without SMB!
Hello NSDias,
Do you have ReadyCloud app on this computer? If so, make sure it is updated to 1.12 version then login with your ReadyCloud account that you used to enable ReadyCloud in the admin page. Then map the NAS IP.
Regards,
Below is the response from Netgear about this issue
"Thank you for the response.
Our firmware is tested several times before it is released. We also do not have reported issues with this firmware regarding USB file access. With this, we would need to further check on the settings of the NAS. Retrieving back to the old firmware is not advisable as indicated on the release notes of the latest firmware.
Due to the device's warranty, we will be giving you limited options for support. If you are not interested in purchasing our support contract, you may still visit our support site and community forums."So No interest in fixing unless I give them money.
Here is my response
What sort of response is this
I have now reported an issue. The usb devices work in v6.4.2 and directly on a PC How do I get back to a working firmware on my system?
If I buy an new unit and then plug these in a they do not work then are you committing to fixing my issue. If I buy a support contract are you committing to resolving my issue.
This type of response is typical of your attitude and you are probably taking the view that I am being unreasonable.
USB devices of 4TB and above do not work in OS 6.5 I have supplied my logs as requested and i they show that directly after installing OS 6.5 the drives do not Mount.
Your response is not a response of any Customer-centric Company at all but "Please go away we have no responsibility or interest and we Netgear can destroy a customers system at will after any warranty period with firmware updates. We even take the view that we will not help a client revert to a working firmware So if we break it we do not care about the customer as what if we lose a few along the way, and take no responsibility ".
I am reporting to to Trading standards in my countryas you are selling goods not fit for purpose."
All I wnat now is to get back to OS6.4.2 which Netgear will not even help me withand then sell all my netgera devices and buy sSynology as Netgear Obviusly have no interst in their customers
I am not "stepping over any line" here Netgear clearly show th in this response their customer care attitude
If their procedure is to check warranty entitlement by validating a proof of purchase, it doesn't mean they imply that YOU are trying to cheat the system. It's just a procedure.
Now that you have proved you qualify for support and provided info, they'll be able to help you with the issue.
There is no "easy" way to downgrade a chassis to a previous major version. Downgrades between minor versions are "fibe" but not between major versions. Most of the time, the major updates, 6.2, 6.4, 6.5 include an update of the kernel. Some modifications may also occur on the BTRFS volume(s). Downgrading the firmware to an older major version may create issues as the OS can't manage the volume properly. For example, on 6.4.0, a new version of btrfs-progs was included and quotas were implemented on the volume(s). If you downgrade to a 6.2.x, you may run into issues as the kernel and btrfs-progs versions may not be recent enough. I'm quite sure NETGEAR won't be able to help downgrading a chassis, as stated in the Release Notes.
If you REALLY want to downgrade, some people here managed to do so by performing a USB Boot Recovery AND a Factory Default (but you wipe all the data).
But now that you have a support case open, I'd give them a chance.I see that the notes for 6.5 indicated kernel updates that is why I wanted a bit more clarification as to the amount of changes that took place as to any dangers if I manunlly reverted to 6.4.2
As for the shipping date warranty issue. I have a significant number of units registered with Netgear and have been purchasing one unit every three months or so recently, So Netgear have evidence of a long term customer. as I register them on arrival. I fully understand the requirement of an invoice It was the date of manufacture stuff which was added blah blah blah combined with the intransigence as to any acceptance that a firmware update has caused a issue with five of my units. I have supplied proof of purchase before when a ReadyNAS NV+ v1 chassis crapped out. I was impressed with the service I recieved then. However the service and support I believe has rapidly gone downhill since then, IMHO and Stephen B has "scolded" me just a while ago about another complaint that I had. This issue is stiil going on by the way. The BTFS hook business. I have a solution to this though.
At least now Netgear have accepted that something is amiss but still no real acceptance that they should have done something about it without me making such a fuss as it is firmware related issue in something pushed out by them. It is purely that I have an "in Warranty unit" that I have got this far.
Another update on the issue. It is an smb issue as I activated ftp via the web browser on one of the attached USB units that I cannot see by smb and can see it in an via a FTP client , Filezilla and winscp for example
Anyway we will wait and see, don't hold your breath
As you can see looking at the GPL, the kernel update was a minor kernel update compared with what we did between 6.2.5 and 6.4.0. We are using the same LTS kernel series in 6.5.0 that we were using in 6.4.x, but a newer kernel in that series.
However in a major firmware update we may do some further tweaks like enabling/disabling kernel options and btrfs features (such as enabling quotas in 6.4.0) which could make a firmware downgrade not recommended.
Where a downgrade is not recommended you should update your regular backup before attempting any downgrade. Where we block downgrades (i.e. we currently block downgrades to older firmware than 6.4.0) it's because a downgrade would lead to data loss (or create a high risk of data loss).
Also if you use ReadyCLOUD please note that ReadyCLOUD now requires the use of 6.5.0 and later.
We would prefer if you keep at least one system running 6.5.0 so we can troubleshoot the problem you are facing with you. If we can confirm there is a bug we'd like to get it fixed in a future firmware release.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
