× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Betreff: Readynas 104 SMB won't activate

JaBiXP
Aspirant

Readynas 104 SMB won't activate

Dear folks,

 

could you please advise me how to handle my problem with SMB. First I had the issue that root space was full, so i did a cleanup manually via SSH. Accidently I deleted the diretory of /mnt/var but at least it solved the space issue 😮 ;-). After rebooting I set up the NAS as before, but SMB will not work as expected. It stays not activated and I can't access the NAS via Windows explorer, just via ftp or web interface. I read this Thread but don't know exactly how to solve the issue.  Does this system log file help? It's a ReadyNAS 104 with four slots. Firmware is 6.9.5. Thanks in advance.

Jan

 

 

 

Model: RN104|ReadyNAS 100 Series
Message 1 of 8

Accepted Solutions
StephenB
Guru

Betreff: Readynas 104 SMB won't activate

Well, as I said you could try an OS reinstall (pages 28-29 here: http://www.downloads.netgear.com/files/GDC/READYNAS-100/ReadyNAS_%20OS6_Desktop_HM_EN.pdf )

 

If that fails, then I'd do a factory reset and restore the files from backup. I guess you could also try a factory install to a scratch disk, and then attempt to copy it's /var to your disks.  You'd need to be careful to reinstall any apps you are using (since some might put libraries in /var), and very careful to preserve file ownership/permissions when you did the copy.

 

 

View solution in original post

Message 7 of 8

All Replies
JaBiXP
Aspirant

Betreff: Readynas 104 SMB won't activate

Mar 27 13:01:18 JABI connmand[2207]: eth0 {add} address 192.168.178.33/24 label eth0 family 2
Mar 27 13:01:18 JABI connmand[2207]: ntp: adjust (slew): +0.062706 sec
Mar 27 13:01:18 JABI connmand[2207]: eth0 {add} route 192.168.178.0 gw 0.0.0.0 scope 253 <LINK>
Mar 27 13:01:18 JABI connmand[2207]: eth0 {add} route 192.168.178.1 gw 0.0.0.0 scope 253 <LINK>
Mar 27 13:01:19 JABI connmand[2207]: eth0 {add} route 0.0.0.0 gw 192.168.178.1 scope 0 <UNIVERSE>
Mar 27 13:01:19 JABI freshclam[2355]: Can't change dir to /var/lib/clamav
Mar 27 13:01:20 JABI avahi-daemon[2212]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::eafc:afff:fee4:d8b4.
Mar 27 13:01:20 JABI avahi-daemon[2212]: New relevant interface eth0.IPv6 for mDNS.
Mar 27 13:01:20 JABI avahi-daemon[2212]: Registering new address record for fe80::eafc:afff:fee4:d8b4 on eth0.*.
Mar 27 13:01:21 JABI apache2[2350]: [error] server reached MaxClients setting, consider raising the MaxClients setting
Mar 27 13:01:26 JABI connmand[2207]: LeafNets {create} index 4 type 1 <ETHER>
Mar 27 13:01:26 JABI connmand[2207]: LeafNets {update} flags 4098 <DOWN>
Mar 27 13:01:26 JABI connmand[2207]: LeafNets {newlink} index 4 address FA:F2:DB:F3:2D:03 mtu 1500
Mar 27 13:01:26 JABI connmand[2207]: LeafNets {newlink} index 4 operstate 2 <DOWN>
Mar 27 13:01:26 JABI connmand[2207]: LeafNets {add} address 5.222.146.197/8 label LeafNets family 2
Mar 27 13:01:26 JABI connmand[2207]: LeafNets {update} flags 69699 <UP,RUNNING,LOWER_UP>
Mar 27 13:01:26 JABI connmand[2207]: LeafNets {newlink} index 4 address FA:F2:DB:F3:2D:03 mtu 1500
Mar 27 13:01:26 JABI connmand[2207]: LeafNets {newlink} index 4 operstate 0 <UNKNOWN>
Mar 27 13:01:26 JABI connmand[2207]: LeafNets {add} route 5.0.0.0 gw 0.0.0.0 scope 253 <LINK>
Mar 27 13:01:26 JABI connmand[2207]: LeafNets {add} route ff00:: gw :: scope 0 <UNIVERSE>
Mar 27 13:01:26 JABI connmand[2207]: LeafNets {add} route fe80:: gw :: scope 0 <UNIVERSE>
Mar 27 13:01:26 JABI connmand[2207]: LeafNets {newlink} index 4 address FA:F2:DB:F3:2D:03 mtu 1500
Mar 27 13:01:26 JABI connmand[2207]: LeafNets {newlink} index 4 operstate 0 <UNKNOWN>
Mar 27 13:01:26 JABI connmand[2207]: LeafNets {newlink} index 4 address FA:F2:DB:F3:2D:03 mtu 1400
Mar 27 13:01:26 JABI connmand[2207]: LeafNets {newlink} index 4 operstate 0 <UNKNOWN>
Mar 27 13:01:26 JABI connmand[2207]: LeafNets {del} route 5.0.0.0 gw 0.0.0.0 scope 253 <LINK>
Mar 27 13:01:35 JABI connmand[2207]: ntp: adjust (slew): +0.001160 sec
Mar 27 13:01:39 JABI dbus[2184]: [system] Failed to activate service 'org.freedesktop.hostname1': timed out
Mar 27 13:02:07 JABI connmand[2207]: ntp: adjust (slew): +0.001176 sec
Mar 27 13:02:11 JABI apache2[2580]: [error] (2)No such file or directory: could not open transfer log file /var/log/apache2/other_vhosts_access.log.
Mar 27 13:02:11 JABI apache2[2583]: [warn] RSA server certificate CommonName (CN) `nas-E4-D8-B4.local' does NOT match server name!?
Mar 27 13:02:11 JABI apache2[2586]: [warn] RSA server certificate CommonName (CN) `nas-E4-D8-B4.local' does NOT match server name!?
Mar 27 13:02:14 JABI apache2[2586]: [error] server reached MaxClients setting, consider raising the MaxClients setting
Mar 27 13:02:24 JABI dbus[2184]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Mar 27 13:02:24 JABI dbus[2184]: [system] Successfully activated service 'org.opensuse.Snapper'
Mar 27 13:02:27 JABI apache2[2723]: [error] (2)No such file or directory: could not open transfer log file /var/log/apache2/other_vhosts_access.log.
Mar 27 13:02:28 JABI apache2[2726]: [warn] RSA server certificate CommonName (CN) `nas-E4-D8-B4.local' does NOT match server name!?
Mar 27 13:02:28 JABI apache2[2730]: [warn] RSA server certificate CommonName (CN) `nas-E4-D8-B4.local' does NOT match server name!?
Mar 27 13:02:31 JABI apache2[2730]: [error] server reached MaxClients setting, consider raising the MaxClients setting
Mar 27 13:03:11 JABI connmand[2207]: ntp: adjust (slew): +0.002118 sec
Mar 27 13:05:19 JABI connmand[2207]: ntp: adjust (slew): +0.003208 sec
Mar 27 13:06:19 JABI freshclam[3166]: Can't change dir to /var/lib/clamav
Mar 27 13:09:35 JABI connmand[2207]: ntp: adjust (slew): +0.004940 sec
Mar 27 13:11:19 JABI freshclam[3184]: Can't change dir to /var/lib/clamav
Mar 27 13:16:20 JABI freshclam[3207]: Can't change dir to /var/lib/clamav
Mar 27 13:17:01 JABI CRON[3211]: pam_unix(cron:session): session opened for user root by (uid=0)
Mar 27 13:17:01 JABI CRON[3215]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Mar 27 13:17:01 JABI CRON[3211]: pam_unix(cron:session): session closed for user root
Mar 27 13:18:07 JABI connmand[2207]: ntp: adjust (slew): +0.007799 sec
Mar 27 13:21:20 JABI freshclam[3250]: Can't change dir to /var/lib/clamav
Mar 27 13:21:20 JABI freshclam[3251]: Can't change dir to /var/lib/clamav
Mar 27 13:26:20 JABI freshclam[3272]: Can't change dir to /var/lib/clamav
Mar 27 13:31:20 JABI freshclam[3282]: Can't change dir to /var/lib/clamav
Mar 27 13:35:11 JABI connmand[2207]: ntp: adjust (slew): +0.012687 sec
Mar 27 13:36:21 JABI freshclam[3301]: Can't change dir to /var/lib/clamav
Mar 27 13:41:21 JABI freshclam[3311]: Can't change dir to /var/lib/clamav
Mar 27 13:46:21 JABI freshclam[3330]: Can't change dir to /var/lib/clamav
Mar 27 13:51:21 JABI freshclam[3340]: Can't change dir to /var/lib/clamav
Mar 27 13:52:15 JABI connmand[2207]: ntp: adjust (slew): +0.007125 sec
Mar 27 13:56:22 JABI freshclam[3366]: Can't change dir to /var/lib/clamav
Mar 27 14:01:22 JABI freshclam[3376]: Can't change dir to /var/lib/clamav
Mar 27 14:06:22 JABI freshclam[3389]: Can't change dir to /var/lib/clamav
Mar 27 14:09:19 JABI connmand[2207]: ntp: adjust (slew): +0.004361 sec
Mar 27 14:11:22 JABI freshclam[3399]: Can't change dir to /var/lib/clamav
Mar 27 14:16:23 JABI freshclam[3411]: Can't change dir to /var/lib/clamav

Message 2 of 8
StephenB
Guru

Betreff: Readynas 104 SMB won't activate

You might need to do a factory reset and restore the NAS from backup.

 

Message 3 of 8
JaBiXP
Aspirant

Betreff: Readynas 104 SMB won't activate

Sorry, but that is not an option! Anybody else?

Message 4 of 8
StephenB
Guru

Betreff: Readynas 104 SMB won't activate


@JaBiXP wrote:

Sorry, but that is not an option! Anybody else?


Then you might have no options.  At the end of the day, you need the contents of /var.

 

You can try an OS reinstall instead of a factory reset - that might possibly work. 

 

Or you can try paid Netgear support (my.netgear.com) - but since you did this yourself, they might not help you.

 

https://kb.netgear.com/30068/ReadyNAS-OS-6-SSH-access-support-and-configuration-guides wrote:
  • Support may be denied if it is determined that actions taken through SSH have contributed to problems encountered on the ReadyNAS. However, you may factory reset the ReadyNAS and restore data from backup at which point normal support may resume.

BTW, your issue isn't the same as the one in the thread you linked in your first post.  That person had an issue with file permissions being set incorrectly in the OS partition.  Your problem is that the files have been deleted.

Message 5 of 8
JaBiXP
Aspirant

Betreff: Readynas 104 SMB won't activate

Ok got it... Any advice how to reinstall properly?

Message 6 of 8
StephenB
Guru

Betreff: Readynas 104 SMB won't activate

Well, as I said you could try an OS reinstall (pages 28-29 here: http://www.downloads.netgear.com/files/GDC/READYNAS-100/ReadyNAS_%20OS6_Desktop_HM_EN.pdf )

 

If that fails, then I'd do a factory reset and restore the files from backup. I guess you could also try a factory install to a scratch disk, and then attempt to copy it's /var to your disks.  You'd need to be careful to reinstall any apps you are using (since some might put libraries in /var), and very careful to preserve file ownership/permissions when you did the copy.

 

 

Message 7 of 8
JaBiXP
Aspirant

Betreff: Readynas 104 SMB won't activate

Thanks, OS reinstall worked!

 

Have a nice day!

Model: RN104|ReadyNAS 100 Series 4- Bay
Message 8 of 8
Top Contributors
Discussion stats
  • 7 replies
  • 2352 views
  • 0 kudos
  • 2 in conversation
Announcements