NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
File service connection failure: RN21200 2-bay home NAS
My NAS box is just a month old. It has two 6TB IronWolf drives operating in RAID 0, giving me 10.9TB effective capacity. Firmware version is 6.10.1 which is the latest as of 10 minutes ago. Short...
Hi shuvam,
The SMB service on your NAS is now fixed.
The NFS service seems to be fine. It appears to be enabled currently on your NAS. It has been running for 2 days now.
Can you check if you can access your shares via SMB and NFS?
Regards,
I am sorry if I did not explain my position clearly.
SMB 3 is quite old, and is well supported by both the Linux on LibreELEC (which runs on my RaspBerry Pi) and on my Ubuntu Linux laptop. I was actually using the ReadyNAS box from both these devices over SMB till yesterday. Therefore, this is not a case of SMB 3 support or lack of it. Something broke yesterday, without me doing anything with the NAS box, not even upgrading its firmware.
Incidentally, it seems to be purely an SMB problem. I am able to access the box over NFS very well -- I hadn't tried this till now, and it's working well now. So, my problem is now limited to SMB. And it's not about SMB level compatibility between client and server.
I found evidence of the malfunction on the GUI. For some reason, I never bothered to check back here.
The SMB service itself is switched off. I have no idea why. And when I click on that icon and try to start it, I go through all the settings, including checking the check-box which "enable SMB", and then I click "OK". The pop-up dialog box disappears, but SMB does not start.
Dug down a bit deeper, and this is what I found by a very quick, superficial search through the raw logs. I downloaded the logs into my laptop and just ran a "grep SMB *" on all the log files. This is what I got -- see the attached file. It's clear that the SMB service is not starting up. I'll now poke around in the log files to see what else I can find.
Apparently, the system does not allow a TXT file to be attached to a message. Will try a PDF now.
For those unfamiliar with grep, the first word in each line gives the name of the file where the matching string was found.
I poked around in the log files, found a lot of entries clearly indicating that the SMB daemon is not starting up, but couldn't figure out why. The NMB daemon is working well, it appears.
I pulled out contiguous sets of lines from three log files and created the PDF file:
- systemd-journal.log
- smbd.log
- nmbd.log
and you can see the lines here. These are not grep outputs -- they are contiguous sets of lines, nothing omitted in between.
Any idea what is going on?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
