Factory Default on OS6? Because of SMB failure.

[Pasala]

Hello Netgear Forum,

just wanted to ask if there is a possibility to do a "real" factory default after switching to OS6 on a Netgear ReadyNas Pro Pioneer.

The problem is:
The NAS displays a factory default after switching to OS6
and then somehow does a rebuild of the volume?

Even more stange is that it takes 10 hours to do so although there is only 3.1 MB ( yes Megabyte ) on the new volume?


Is there a possibility to "nuke" everything and reset the NAS to default without the rebuild afterwards?

[vandermerwe]

No.
Whenever you factory default, the volume will rebuild. The duration of this depends on the volume size, so it will take some time even though the volume may be empty.

[Pasala]

Ok.
Thank you for the fast reply.

[Pasala]

So the NAS has finished a rebuild.

But unfortunately the data transfer failures still happen. 😞
Just like they did before switching to OS6.

The smbd.log reads the following errors:

"smbd version 4.0.21 started
Copyright Andrew Tridgell and the Samba Team 1992-2012
[2014/10/05 23:43:56.820793,  0] ../source3/smbd/server.c:1286(main)
 standard input is not a socket, assuming -D option
[2014/10/05 23:44:15.864328,  2] ../source/auth/auth.c:288(auth_check_ntlm_password)
 check_ntlm_password:   Authentication for user [*username] -> [*username] FAILED with error NT_STATUS_WRONG_PASSWORD
[2014/10/05 23:46:59.800179,  2] ../source/auth/auth.c:288(auth_check_ntlm_password)
 check_ntlm_password:   Authentication for user [*username] -> [*username] FAILED with error NT_STATUS_WRONG_PASSWORD"

The afp.log reads these errors, among others:

"Oct 05 23:07:00.350332 netalk[2122] {netalk_conf.c:1929} (E:AFPDaemon): Couldn't open extensions maping ->
file /etc/netalk/extmap.conf"

The results are that the NAS completely fails after coypying files from different clients ( Ubuntu 14.04 and Mac OS 10.9.5 ) onto it.
It has to be disconnected from power and restarted.

Very disappointing since this happened for a while with the RAIDiator OS up to version 4.2.26. 😞

[mdgm-ntgr]

Are some of your ordinary shares on the NAS, named the same as users or the computer name on your PC?

[Pasala]

The NAS was just set to "factory default" and no user nor specific share has been created
other than the standard ones like "Video" or "Pictures".

There is no data on it too.

Just done the switch to OS6.

[mdgm-ntgr]

Can you send me your logs?: http://www.readynas.com/kb/faq/misc/how_do_i_send_all_logs

[Pasala]

Thank you for your help.
I can send them tomorrow.

Again, there has basically done nothing to the NAS after the "factory default" only a new admin password and the timezone configuration.
I thought the NAS should be on "stock" then.

Very strange that there are so many errors despite the "factory default" and the new OS6 firmware.
All data on it has been deleted (as expected, and after backups) through this process.
I thought to get rid of the problems through that procedure.

Regards.

[mdgm-ntgr]

Hopefully your logs will give some clues as to what the problem is.

[Pasala]

Ok. I will downgrade to RAIDiator 4.2.26 again once too and download these logs as well.

Thanks again for the help.

Regards.

[Pasala]

Ok after quite some time the situation is as follows:

1. Switched back to 4.2.26 with RAID 0 set up.
2. Then again back to OS 6.1.9 with XRAID2.
3. shell command: apt-get update, apt-get upgrade
4. But the copying failures are still there.
5. Even more "debugging" now only some errors...

- The persistent afp errors:

"Oct 04 19:34:55.159399 netatalk[2081] {netatalk_conf.c:1229} (E:Default): Couldn't open extension maping file /etc/netatalk/extmap.conf"

-> probable solution:

"touch /etc/netatalk/extmap.conf"

according to this source: viewtopic.php?f=71&t=73177

--> The afp logs don't show the errors any more. But it is impossible to use afp with Linux clients. 😞

-the smbd errors:

"smbd version 4.0.21 started
Copyright Andrew Tridgell and the Samba Team 1992-2012
[2014/10/05 23:43:56.820793,  0] ../source3/smbd/server.c:1286(main)
 standard input is not a socket, assuming -D option
[2014/10/05 23:44:15.864328,  2] ../source/auth/auth.c:288(auth_check_ntlm_password)
 check_ntlm_password:   Authentication for user [*username] -> [*username] FAILED with error NT_STATUS_WRONG_PASSWORD
[2014/10/05 23:46:59.800179,  2] ../source/auth/auth.c:288(auth_check_ntlm_password)
 check_ntlm_password:   Authentication for user [*username] -> [*username] FAILED with error NT_STATUS_WRONG_PASSWORD"

-> probable part of the solution

1. Edited the smb.conf file in /etc/samba to the state described in this thread:

viewtopic.php?f=23&t=73808

2. The "NT_STATUS_WRONG_PASSWORD" errors could be improved through changing the password of the user like described here:

https://forums.freenas.org/index.php?th ... ser.20240/

The good news: File transfere hasn't crashed till now. 🙂
The bad news: The logs show these errors: 😞

"[2014/10/06 21:00:17.061298,  2] ../source3/auth/auth.c:288(auth_check_ntlm_password)
  check_ntlm_password:  Authentication for user [*username] -> [*username] FAILED with error NT_STATUS_WRONG_PASSWORD
[2014/10/06 21:00:17.231050,  2] ../source3/auth/auth.c:288(auth_check_ntlm_password)
  check_ntlm_password:  Authentication for user [*username] -> [*username] FAILED with error NT_STATUS_WRONG_PASSWORD
[2014/10/06 21:00:22.254075,  2] ../source3/auth/auth.c:288(auth_check_ntlm_password)
  check_ntlm_password:  Authentication for user [*username] -> [*username] FAILED with error NT_STATUS_WRONG_PASSWORD
[2014/10/06 21:00:29.680601,  2] ../source3/auth/auth.c:288(auth_check_ntlm_password)
  check_ntlm_password:  Authentication for user [*username] -> [*username] FAILED with error NT_STATUS_WRONG_PASSWORD
[2014/10/06 21:00:50.082946,  2] ../source3/auth/auth.c:278(auth_check_ntlm_password)
  check_ntlm_password:  authentication for user [*username] -> [*username] -> [*username] succeeded"

--> So it's a little bit better but far away from inspiring confidence.

Any ideas?
Thanks.
Regards.

[mdgm-ntgr]

We don't recommend an

# apt-get upgrade

as that can break things.

As for the samba errors to check my idea about that I would need to look at your logs.

[Pasala]

Ok. Do you need just the smbd.log?

Just switched to 6.2.0 beta.

There are no longer abortions when copying but the speed is quite low with just 20-50 MB/s.
In the old days with RAIDiator 4.1 it was 100MB/s.
Are there possibilities to speed it up?

Thanks for the support again.

[mdgm-ntgr]

No, I need the full logs zip file.

Is your volume redundant or is it still syncing?

Have you turned off features such as snapshots? If not, that may help with performance.

Also try turning off anti-virus if you are running that.

[StephenB]

Bit-rot checking will also slow write performance, not sure about read.

[Pasala]

Ok.
With the new 6.2.0 beta firmware and the fixes described in post #11 viewtopic.php?f=160&t=77971#p436301
the afp.log shows no errors any more.
While the smbd.log just shows:

  STATUS=daemon 'smbd' finished starting up and ready to serve connectionscheck_ntlm_password:  Authentication for user [*username] -> [*username] FAILED with error NT_STATUS_WRONG_PASSWORD
  STATUS=daemon 'smbd' finished starting up and ready to serve connectionscheck_ntlm_password:  authentication for user [*username] -> [*username] -> [*username] succeeded

I guess I can live with that.

The volume is XRAID2 and has finished syncing. And yes, Anti Virus and snapshots are turned off and the new bitrot protection too, with no difference: the max. write speed is 50MB/s

The read speed with afp and a Mac OS X client ( and bitrot protection on ) is at a good 100+ MB/s. The write speed with the same client is better too, at an unstable 60-80 MB/s.

If the Netgear NAS runs stable now (again) it will be probably ok. 🙂

Thank you for the support and help again.
Regards.

[Pasala]

Maybe the newer SAMBA version helped? Since 6.2.0 beta seems to run with 4.1.x?

mdgm wrote:
The current 6.2.0 beta (not supported on your Pro Business, but can upgrade to it - note this requires a factory default) has samba 4.1.x.

viewtopic.php?f=23&t=77962#p436151

[mdgm-ntgr]

Perhaps. If you like you could have a look at the Release Notes to see if anything stands out e.g. http://www.samba.org/samba/history/samba-4.1.0.html, http://www.samba.org/samba/history/samba-4.1.1.html etc.

I guess it's likely at least one of the changes has helped.