Reply
tony359
Apprentice

ReadyNAS Pro6 (OS 6.10.0) crashed

Greetings all,

I think for the first time in years my ReadyNas has crashed. It was not accessible anymore even though it was displaying an IP on the front panel. Changing Ethernet port would change the IP (one is fixed, the other one is DHCP) but I wouldn't be able to access the unit, or ping it anyway.

I had to force a shutdown but after 15 minutes of "powering off, goodbye" I pulled the plug. The unit came back ok, no issues.

 

I do not see anything wrong from the standard logs, is there anything else I can check to try to ascertain the root cause of this issue?

 

Thanks!

Message 1 of 25
tony359
Apprentice

Re: ReadyNAS Pro6 (OS 6.10.0) crashed

Right, I didn't realise that the system would save all the system logs when downloaded.

 

So far I think I found this but I am not sure what to make out of it. Any help?

--------------------

Oct 27 07:41:30 Enterprise-NAS kernel: general protection fault: 0000 [#2] SMP
Oct 27 07:41:30 Enterprise-NAS kernel: Modules linked in: nv6lcd(O) vpd(PO)
Oct 27 07:41:30 Enterprise-NAS kernel: CPU: 1 PID: 24426 Comm: bash Tainted: P D O 4.4.178.x86_64.1 #1
Oct 27 07:41:30 Enterprise-NAS kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./To be filled by O.E.M., BIOS 080014 07/26/2010
Oct 27 07:41:30 Enterprise-NAS kernel: task: ffff88007c75aa00 ti: ffff880026760000 task.ti: ffff880026760000
Oct 27 07:41:30 Enterprise-NAS kernel: RIP: 0010:[<ffffffff8813368b>] [<ffffffff8813368b>] dup_fd+0x176/0x1e4
Oct 27 07:41:30 Enterprise-NAS kernel: RSP: 0018:ffff880026763dc0 EFLAGS: 00010206
Oct 27 07:41:30 Enterprise-NAS kernel: RAX: 0000000000000001 RBX: ffff88006ef31b80 RCX: ffff88007cdbd128
Oct 27 07:41:30 Enterprise-NAS kernel: RDX: 28e0ffffffffffff RSI: ffff88005738e828 RDI: ffff88007cdbd120
Oct 27 07:41:30 Enterprise-NAS kernel: RBP: ffff880026763e00 R08: ffff88007cdbd0a8 R09: ffff88007cdbd0a8
Oct 27 07:41:30 Enterprise-NAS kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000040
Oct 27 07:41:30 Enterprise-NAS kernel: R13: ffff88007bd9a000 R14: 0000000000000040 R15: ffff88007cdbd080
Oct 27 07:41:30 Enterprise-NAS kernel: FS: 00007fa0bfe4e700(0000) GS:ffff88007f880000(0000) knlGS:0000000000000000
Oct 27 07:41:30 Enterprise-NAS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 27 07:41:30 Enterprise-NAS kernel: CR2: 00000000015201c0 CR3: 0000000029a76000 CR4: 0000000000000670
Oct 27 07:41:30 Enterprise-NAS kernel: Stack:
Oct 27 07:41:30 Enterprise-NAS kernel: ffff88007c210a80 ffff88007cdbd0a8 ffff88007cdbd0a8 0000000001200011
Oct 27 07:41:30 Enterprise-NAS kernel: 0000000000000000 ffff88007c75aa00 00007fa0bfe4e9d0 ffff88007c210a80
Oct 27 07:41:30 Enterprise-NAS kernel: ffff880026763ec8 ffffffff88061585 ffff880026763ed8 00000000880fdff8
Oct 27 07:41:30 Enterprise-NAS kernel: Call Trace:
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff88061585>] copy_process+0x5b1/0x1611
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff8809cb39>] ? rcu_is_watching+0x9/0xb
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff88062727>] _do_fork+0x78/0x243
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff8806d8f0>] ? __set_current_blocked+0x3d/0x51
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff8806da50>] ? sigprocmask+0x5b/0x5f
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff88062964>] SyS_clone+0x14/0x16
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff888e43ca>] entry_SYSCALL_64_fastpath+0x1e/0x8e
Oct 27 07:41:30 Enterprise-NAS kernel: Code: 4d d0 e8 f5 fa ff ff 4c 8b 4d d0 4d 8b 6c 24 08 31 c0 45 89 f4 49 8b 79 08 48 89 f9 4c 39 e0 74 32 49 8b 54 c5 00 48 85 d2 74 07 <f0> 48 ff 42 38 eb 15 49 8b 71 18 48 0f b3 06 89 c6 4d 8b 59 20
Oct 27 07:41:30 Enterprise-NAS kernel: RIP [<ffffffff8813368b>] dup_fd+0x176/0x1e4
Oct 27 07:41:30 Enterprise-NAS kernel: RSP <ffff880026763dc0>
Oct 27 07:41:30 Enterprise-NAS kernel: ---[ end trace d6f71a1ca94fb120 ]---
Oct 27 07:41:30 Enterprise-NAS kernel: general protection fault: 0000 [#3] SMP
Oct 27 07:41:30 Enterprise-NAS kernel: Modules linked in: nv6lcd(O) vpd(PO)
Oct 27 07:41:30 Enterprise-NAS kernel: CPU: 1 PID: 24426 Comm: bash Tainted: P D O 4.4.178.x86_64.1 #1
Oct 27 07:41:30 Enterprise-NAS kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./To be filled by O.E.M., BIOS 080014 07/26/2010
Oct 27 07:41:30 Enterprise-NAS kernel: task: ffff88007c75aa00 ti: ffff880026760000 task.ti: ffff880026760000
Oct 27 07:41:30 Enterprise-NAS kernel: RIP: 0010:[<ffffffff8811b42d>] [<ffffffff8811b42d>] filp_close+0x9/0x6f
Oct 27 07:41:30 Enterprise-NAS kernel: RSP: 0018:ffff880026763ba0 EFLAGS: 00010206
Oct 27 07:41:30 Enterprise-NAS kernel: RAX: 0000000000000001 RBX: ffff88006ef31b80 RCX: ffff88007bd9a000
Oct 27 07:41:30 Enterprise-NAS kernel: RDX: 0000000080000000 RSI: ffff88006ef31b80 RDI: 28e0ffffffffffff
Oct 27 07:41:30 Enterprise-NAS kernel: RBP: ffff880026763bb8 R08: 0000000000000001 R09: ffffffff880ff700
Oct 27 07:41:30 Enterprise-NAS kernel: R10: ffff880026763b30 R11: fffffffffffffffc R12: 0000000000000001
Oct 27 07:41:30 Enterprise-NAS kernel: R13: ffff880056ac1000 R14: 0000000000000000 R15: 0000000000000003
Oct 27 07:41:30 Enterprise-NAS kernel: FS: 0000000000000000(0000) GS:ffff88007f880000(0000) knlGS:0000000000000000
Oct 27 07:41:30 Enterprise-NAS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 27 07:41:30 Enterprise-NAS kernel: CR2: 00000000015201c0 CR3: 0000000008cce000 CR4: 0000000000000670
Oct 27 07:41:30 Enterprise-NAS kernel: Stack:
Oct 27 07:41:30 Enterprise-NAS kernel: ffff88006ef31b80 0000000000000001 ffff880056ac1000 ffff880026763bf8
Oct 27 07:41:30 Enterprise-NAS kernel: ffffffff8813378b 0000000100000001 ffff88007c75aa00 ffff88006ef31b80
Oct 27 07:41:30 Enterprise-NAS kernel: ffff880026763c50 0000000000000001 ffff8800636a34e8 ffff880026763c18
Oct 27 07:41:30 Enterprise-NAS kernel: Call Trace:
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff8813378b>] put_files_struct+0x65/0xad
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff88133854>] exit_files+0x3c/0x41
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff8806500b>] do_exit+0x3d7/0x8fc
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff880055c9>] oops_end+0x9d/0xa4
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff88005625>] die+0x55/0x5e
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff88003a18>] do_general_protection+0x8f/0x135
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff888e5b22>] general_protection+0x22/0x30
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff8813368b>] ? dup_fd+0x176/0x1e4
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff88061585>] copy_process+0x5b1/0x1611
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff8809cb39>] ? rcu_is_watching+0x9/0xb
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff88062727>] _do_fork+0x78/0x243
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff8806d8f0>] ? __set_current_blocked+0x3d/0x51
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff8806da50>] ? sigprocmask+0x5b/0x5f
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff88062964>] SyS_clone+0x14/0x16
Oct 27 07:41:30 Enterprise-NAS kernel: [<ffffffff888e43ca>] entry_SYSCALL_64_fastpath+0x1e/0x8e
Oct 27 07:41:30 Enterprise-NAS kernel: Code: 00 01 00 74 05 b8 02 00 00 00 41 0f ba e0 11 72 03 83 c8 01 48 8d 4d ec 89 45 fc e8 5c e6 00 00 c9 c3 55 48 89 e5 41 55 41 54 53 <48> 8b 47 38 48 85 c0 75 11 48 c7 c7 14 dd b5 88 45 31 e4 e8 f7
Oct 27 07:41:30 Enterprise-NAS kernel: RIP [<ffffffff8811b42d>] filp_close+0x9/0x6f
Oct 27 07:41:30 Enterprise-NAS kernel: RSP <ffff880026763ba0>
Oct 27 07:41:30 Enterprise-NAS kernel: ---[ end trace d6f71a1ca94fb121 ]---
Oct 27 07:41:30 Enterprise-NAS kernel: Fixing recursive fault but reboot is needed!

Message 2 of 25
StephenB
Guru

Re: ReadyNAS Pro6 (OS 6.10.0) crashed

Assuming nothing has changed with the OS recently, I'd run the memory test. 

 

Another cause I've seen posted elsewhere is an aging/dying PSU.  Though that would be harder to confirm.

 

It would be prudent to run a disk test on each volume followed by a scrub.  Though that is more about confirming file system integrity.

Message 3 of 25
tony359
Apprentice

Re: ReadyNAS Pro6 (OS 6.10.0) crashed

Hi Stephen,

 

Thanks for your usual help.

 

No, nothing has changed. I have moved to iDrive from Crashplan but that was more than a month ago.

I've also found another thread showing the same issues and you were recommending running smartctl - which I have just done: only one drive shows some errors but that was abour 20.000 hours ago so I don't think that's relevant! Smiley Happy

 

Disk tests and scrubs are run automatically every month I think. Last was run 28 days ago - maybe I should run another one now.

 

I think the memory test is run from the boot menu - I'll find out and I'll run it overnight.

 

I suppose that if the RAM test checks out and drives don't show issues, my next step would be to look at the PSU.

 

I shall keep you posted.

Thanks!

Message 4 of 25
tony359
Apprentice

Re: ReadyNAS Pro6 (OS 6.10.0) crashed

A silly question for the community, just to sanity check my finding.

 

To access the BOOT menu I shall power off the NAS, keep holding on the RESET button at the back and power up until the BOOT menu shows up?

I'm sure you understand my caution of pressing a RESET button on a live 12TB NAS Smiley Wink  I've done this in the past but I cannot remember anymore.

Thanks!

Message 5 of 25
StephenB
Guru

Re: ReadyNAS Pro6 (OS 6.10.0) crashed

My own pro-6 is still running 4.2.31 (and likely will until I need to do a factory reset or expand it).  So I'm not 100% sure if the conversion affects the boot menu.

 

I think it doesn't - and that the hardware manual instructions  on pages 28-29 are still correct. http://www.downloads.netgear.com/files/GDC/RNDU2000/ReadyNAS_Ultra_UltraPlus_NVX_Pro_HW_en_8July11.p...

 

Hopefully someone who has converted their pro-6 will confirm. 

Message 6 of 25
tony359
Apprentice

Re: ReadyNAS Pro6 (OS 6.10.0) crashed

Thank Stephen - I also believe it did not change but I'm sure you understand my reluctancy to test it! Smiley Happy 

 

Hopefully someone will confirm but it looks like there are not many people with a converted "series 1" here.

Message 7 of 25
StephenB
Guru

Re: ReadyNAS Pro6 (OS 6.10.0) crashed


@tony359 wrote:

 but I'm sure you understand my reluctancy to test it! Smiley Happy 


Yup.  I think @Sandshark can answer this definitively.

Message 8 of 25
Sandshark
Sensei

Re: ReadyNAS Pro6 (OS 6.10.0) crashed

That is correct, the boot menu does not change.  That's at least one reason you must still use the OS4.2.x USB recovery method (but with a converted OS6 image) if you ever have the need.

Message 9 of 25
tony359
Apprentice

Re: ReadyNAS Pro6 (OS 6.10.0) crashed

Back on this subject, the NAS crashed in the same way 2 months later. This time logs are partially missing so I cannot compare the root cause with last time. 

This time I ran the memory test overnight: 14 passes and they're all ok.

 

What's next? As it only happens every two months I find it difficult to diagnose...

Message 10 of 25
StephenB
Guru

Re: ReadyNAS Pro6 (OS 6.10.0) crashed


@tony359 wrote:

Back on this subject, the NAS crashed in the same way 2 months later.


Meaning that the

  • LCD panel showed the correct IP address (as usual)?
  • The NAS did not respond to ping?
  • The NAS wouldn't shut down gracefully ("Preferred Shutdown"), so you needed to forcibly shut it down?

Do you recall if there was any disk activity?

Message 11 of 25
tony359
Apprentice

Re: ReadyNAS Pro6 (OS 6.10.0) crashed

Hi Stephen,

 

I did not try to ping it this time, I do not think I could last time. The display was showing the usual stuff, only I noticed at some point it said "waking up disk 2" which then disappeared.

 

I could shut it down via front button, it said "shutting down, goodbye" but kept displaying that for a long time until I power cycled it.

It's hard to see disk activity on my NAS, the LED is hidden and only visible from an angle which I cannot achieve in the NAS' current position unfortunately. I do not recall hearing any activity but WD RED are very quiet in operation.

Message 12 of 25
StephenB
Guru

Re: ReadyNAS Pro6 (OS 6.10.0) crashed

As far as troubleshooting goes, you've ruled out memory, but not much else.

 

Have you expanded the memory, or are you still using the original 1 GB?

Are you running any apps in the NAS (I'm particularly wondering about Plex).

Message 13 of 25
tony359
Apprentice

Re: ReadyNAS Pro6 (OS 6.10.0) crashed

memory is expanded to 2GB. CPU is also upgraded. Hardware configuration has been the same for years - besides I have updated the main fan recently but temperatures are perfectly fine.

 

I only use iDrive on the NAS. In fact, I have installed it in October and the first crash was end of october.

Message 14 of 25
tony359
Apprentice

Re: ReadyNAS Pro6 (OS 6.10.0) crashed

I think I discovered something so I’d like to keep this thread updated.
Yesterday my NAS disappeared from the network again. Last time it happened a month ago so as you can see it’s not easy to troubleshoot.
This time I spent a little time troubleshooting before power cycling.

- the front panel showed the correct IP but I could not ping it.
- I moved the Ethernet cable to the secondary port (both are set to DHCP with a ‘bind Mac to IP’ set for ETH0) and I got a new IP which gave me access to the unit. So I knew the software was working fine.
- I went back to ETH0 but I did not get an IP at all this time.
- I then restarted my switch and my router and the IP came back and I could access the unit again.

So it’s either a NAS software issue with the network (maybe the router release the IP every month or so and something is broken in the software?) or there’s something happening with my router or my switch.

As I said the NAS is on DHCP but it’s getting the same IP every time as that’s assigned in the router configuration. But the same happens for all my devices on the network.

The only thing is that on the previous occurrence the NAS also refused to reboot and the first time that that happened I found a kernel panic in the log.

The saga continues 🙂
Message 15 of 25
StephenB
Guru

Re: ReadyNAS Pro6 (OS 6.10.0) crashed


@tony359 wrote:

- I then restarted my switch and my router and the IP came back and I could access the unit again.


Interesting.  Maybe next time try just restarting the switch, and see if that is enough.

Message 16 of 25
tony359
Apprentice

Re: ReadyNAS Pro6 (OS 6.10.0) crashed

Indeed that going to be my next troubleshooting step.
I don’t normally power cycle switch and router but I’ve never had issues with that. It’s a netgear switch btw, those which never fail or crash 🙂 (I’m serious, those are tanks)

I have updated the router’s firmware some time ago though. I’ll see when I did that and I’ll try to see if that could be related.
Message 17 of 25
tony359
Apprentice

Re: ReadyNAS Pro6 (OS 6.10.0) crashed

And here I am, three months later my NAS disappeared from the network.

 

Symptoms: I couldn't ping it, the front panel would show a 169 IP address. 

 

Tests

- Last time I resolved by restarting switch and router. This time I first restarted the switch alone: nothing.

- I restarted the router: nothing.

- I moved the ethernet cable to the other port: it would get an IP and I could access the NAS.

- Moving back to the usual port would get no IP.

 

Eventually I unplugged the NAS, restarted the router and plugged the NAS back. The NAS got an IP and it's working now, without requiring a reboot.

 

I'd really would like to investigate but I cannot find a log file that is giving me details on network status and DHCP requests. The only one that seems suitable is kernel.log which - as usual - seems to be corrupted as I only have a few lines from March, 6th and then a few from yesterday; nothing else.

 

I searched the FS for kernel.log and I couldn't find it.

 

Any hint on where to find some logs that can tell me what happened today? I can check the router logs too.

Thanks!

Message 18 of 25
StephenB
Guru

Re: ReadyNAS Pro6 (OS 6.10.0) crashed


@tony359 wrote:

 

I searched the FS for kernel.log and I couldn't find it.

OS-6 uses journalctl

 

To see the kernel  log entries you could use

# journalctl -k -r
Message 19 of 25
tony359
Apprentice

Re: ReadyNAS Pro6 (OS 6.10.0) crashed

Hi  Stephen,

 

thanks!

 

I generated the logs but they still only show a few lines from March, 6th and from April, 27th. Nothing else. Is this a known issue maybe?

 

Thanks!

Message 20 of 25
StephenB
Guru

Re: ReadyNAS Pro6 (OS 6.10.0) crashed


@tony359 wrote:

 

I generated the logs but they still only show a few lines from March, 6th and from April, 27th. Nothing else. Is this a known issue maybe?

 


I don't know why the logs are so sparse.  They are rotated, but there should be stuff in between 6 March and 27 April.  Maybe try w/o -k, and see if there is more information.  It is often useful to pipe journalctl through grep (using the --no-pager option in journalctl).

 

As to the main problem, it sounds more like a network issue to me (since rebooting the network was needed to resolve it).  

Message 21 of 25
tony359
Apprentice

Re: ReadyNAS Pro6 (OS 6.10.0) crashed

that worked thanks.

 

Indeed it seems more a DHCP issue (I assign IPs on DHCP but they're bind to the MAC so the unit should get the same IP every time). I have involved AVM as well. 

 

This is the only device showing this issue on my network - I have other devices on 24/7 and they never disappear to be honest.

Message 22 of 25
tony359
Apprentice

Re: ReadyNAS Pro6 (OS 6.10.0) crashed

I can now see the relevant events.

 

 

Apr 27 16:18:25 Enterprise-NAS systemd-logind[2761]: Power key pressed.
Apr 27 16:18:05 Enterprise-NAS systemd-logind[2761]: Power key pressed.
Apr 27 16:17:01 Enterprise-NAS CRON[2656]: pam_unix(cron:session): session closed for user root
Apr 27 16:17:01 Enterprise-NAS CRON[2657]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Apr 27 16:17:01 Enterprise-NAS CRON[2656]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 27 16:12:10 Enterprise-NAS connmand[2765]: eth1 {add} route 0.0.0.0 gw 0.0.0.0 scope 253 <LINK>
Apr 27 16:12:10 Enterprise-NAS connmand[2765]: eth1 {add} route 169.254.0.0 gw 0.0.0.0 scope 253 <LINK>
Apr 27 16:12:10 Enterprise-NAS connmand[2765]: eth1 {add} address 169.254.221.79/16 label eth1 family 2
Apr 27 16:12:10 Enterprise-NAS readynasd[2967]: PropertyChanged (/ethernet_001f33ea1502_cable): State=ready
Apr 27 16:12:10 Enterprise-NAS wsdd2[2745]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Apr 27 16:12:10 Enterprise-NAS avahi-daemon[2766]: Registering new address record for 169.254.221.79 on eth1.IPv4.
Apr 27 16:12:10 Enterprise-NAS avahi-daemon[2766]: New relevant interface eth1.IPv4 for mDNS.
Apr 27 16:12:10 Enterprise-NAS avahi-daemon[2766]: Joining mDNS multicast group on interface eth1.IPv4 with address 169.254.221.79.
Apr 27 16:12:10 Enterprise-NAS minissdpd[3364]: sendto(udp_notify=6, http://169.254.221.79:10000/nasService.xml): Network is unreachable
Apr 27 16:12:10 Enterprise-NAS minissdpd[3364]: sendto(udp_notify=6, http://169.254.221.79:10000/nasService.xml): Network is unreachable
Apr 27 16:12:10 Enterprise-NAS raidard[2749]: IP=169.254.221.79 Mac=00:1f:33:ea:15:02 BroadAddress=169.254.255.255
Apr 27 16:12:10 Enterprise-NAS raidard[2749]: got 1 interfaces:
Apr 27 16:12:10 Enterprise-NAS minissdpd[3364]: sendto(udp_notify=6, http://169.254.221.79:10000/nasService.xml): Network is unreachable
Apr 27 16:12:10 Enterprise-NAS upnphttpd[3365]: registering urn:schemas-upnp-org:device:networkstoragedevice:, desc=http://169.254.221.79:10000/nasService.xml, uuid=3a0c2c93-44b5-46eb-92a9-91cf13ed5000
Apr 27 16:12:10 Enterprise-NAS upnphttpd[3365]: registering upnp:rootdevice, desc=http://169.254.221.79:10000/nasService.xml, uuid=3a0c2c93-44b5-46eb-92a9-91cf13ed5000
Apr 27 16:12:10 Enterprise-NAS upnphttpd[3365]: registering uuid:3a0c2c93-44b5-46eb-92a9-91cf13ed5000, desc=http://169.254.221.79:10000/nasService.xml, uuid=3a0c2c93-44b5-46eb-92a9-91cf13ed5000
Apr 27 16:11:44 Enterprise-NAS minidlnad[2748]: minissdp.c:260: error: sendto(udp): Network is unreachable
Apr 27 16:11:44 Enterprise-NAS minissdpd[3364]: SendSSDPMSEARCHResponse: sendto(udp): Network is unreachable
Apr 27 16:11:41 Enterprise-NAS minidlnad[2748]: minissdp.c:260: error: sendto(udp): Network is unreachable
Apr 27 16:11:41 Enterprise-NAS minissdpd[3364]: SendSSDPMSEARCHResponse: sendto(udp): Network is unreachable
Apr 27 16:11:21 Enterprise-NAS minidlnad[2748]: minissdp.c:260: error: sendto(udp): Network is unreachable
Apr 27 16:11:21 Enterprise-NAS minissdpd[3364]: SendSSDPMSEARCHResponse: sendto(udp): Network is unreachable
Apr 27 16:11:06 Enterprise-NAS minidlnad[2748]: minissdp.c:260: error: sendto(udp): Network is unreachable
Apr 27 16:11:04 Enterprise-NAS minidlnad[2748]: minissdp.c:260: error: sendto(udp): Network is unreachable
Apr 27 16:11:04 Enterprise-NAS minidlnad[2748]: minissdp.c:260: error: sendto(udp): Network is unreachable
Apr 27 16:11:04 Enterprise-NAS minissdpd[3364]: SendSSDPMSEARCHResponse: sendto(udp): Network is unreachable
Apr 27 16:10:59 Enterprise-NAS minidlnad[2748]: minissdp.c:260: error: sendto(udp): Network is unreachable
Apr 27 16:10:59 Enterprise-NAS minissdpd[3364]: SendSSDPMSEARCHResponse: sendto(udp): Network is unreachable
Apr 27 16:10:57 Enterprise-NAS minissdpd[3364]: setsockopt(udp_notify, IP_MULTICAST_IF): Cannot assign requested address
Apr 27 16:10:57 Enterprise-NAS avahi-daemon[2766]: Registering new address record for fe80::21f:33ff:feea:1502 on eth1.*.
Apr 27 16:10:57 Enterprise-NAS avahi-daemon[2766]: New relevant interface eth1.IPv6 for mDNS.
Apr 27 16:10:57 Enterprise-NAS avahi-daemon[2766]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::21f:33ff:feea:1502.
Apr 27 16:10:56 Enterprise-NAS readynasd[2967]: Service ethernet_001f33ea1502_cable changed: State=configuration
Apr 27 16:10:56 Enterprise-NAS connmand[2765]: Skipping disconnect of carrier, network is connecting.
Apr 27 16:10:56 Enterprise-NAS connmand[2765]: eth1 {newlink} index 3 operstate 6 <UP>
Apr 27 16:10:56 Enterprise-NAS connmand[2765]: eth1 {newlink} index 3 address 00:1F:33:EA:15:02 mtu 1500
Apr 27 16:10:56 Enterprise-NAS connmand[2765]: eth1 {update} flags 102467 <UP,RUNNING,LOWER_UP>
Apr 27 16:10:56 Enterprise-NAS connmand[2765]: eth1 {TX} 766815498 packets 1790552547 bytes
Apr 27 16:10:56 Enterprise-NAS connmand[2765]: eth1 {RX} 867038336 packets 891306446 bytes
Apr 27 16:10:56 Enterprise-NAS connmand[2765]: eth1 {add} route fe80:: gw :: scope 0 <UNIVERSE>
Apr 27 16:10:56 Enterprise-NAS connmand[2765]: eth1 {add} route ff00:: gw :: scope 0 <UNIVERSE>
Apr 27 16:10:56 Enterprise-NAS kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Apr 27 16:10:56 Enterprise-NAS kernel:     rx-polling:      enabled
Apr 27 16:10:56 Enterprise-NAS kernel:     rx-checksum:     enabled
Apr 27 16:10:56 Enterprise-NAS kernel:     tx-checksum:     enabled
Apr 27 16:10:56 Enterprise-NAS kernel:     scatter-gather:  enabled
Apr 27 16:10:56 Enterprise-NAS kernel:     tcp offload:     enabled
Apr 27 16:10:56 Enterprise-NAS kernel:     role:            slave
Apr 27 16:10:56 Enterprise-NAS kernel:     flowctrl:        symmetric
Apr 27 16:10:56 Enterprise-NAS kernel:     duplex mode:     full
Apr 27 16:10:56 Enterprise-NAS kernel:     autonegotiation: yes
Apr 27 16:10:56 Enterprise-NAS kernel:     speed:           1000
Apr 27 16:10:56 Enterprise-NAS kernel:     interrupt src:   MSI
Apr 27 16:10:56 Enterprise-NAS kernel: eth1: network connection up using port A
Apr 27 16:10:45 Enterprise-NAS readynasd[2967]: Service ethernet_001f33ea1502_cable removed

Would the line

 

Apr 27 16:10:57 Enterprise-NAS minissdpd[3364]: setsockopt(udp_notify, IP_MULTICAST_IF): Cannot assign requested address

 

mean anything to the board? It seems the NAS is asked to use an IP it cannot use?

 

 

Message 23 of 25
StephenB
Guru

Re: ReadyNAS Pro6 (OS 6.10.0) crashed

It looks like you have ipv6 enabled in the NAS. If your local network doesn't support ipv6, I suggest disabling it. There are some cases where PCs will use ipv6 link local addresses, and that can create performance issues. Plus it's a needless complication if you don't have ipv6 deployed in your routers.

 


@tony359 wrote:

Would the line

 

Apr 27 16:10:57 Enterprise-NAS minissdpd[3364]: setsockopt(udp_notify, IP_MULTICAST_IF): Cannot assign requested address

 

mean anything to the board? It seems the NAS is asked to use an IP it cannot use?

 


I believe that is linked to the three avahi demon messages below it.  There's a similar message a bit later on: Apr 27 16:12:10 Enterprise-NAS wsdd2[2745]: error: wsdd-mcast-v4: wsd_send_soap_msg: send\

 

I don't see any indication that the NAS is being given an IP address it can't use.  Instead it is defaulting to IP addresses that don't work

.

Message 24 of 25
tony359
Apprentice

Re: ReadyNAS Pro6 (OS 6.10.0) crashed

Thanks Stephen

 

I have now disabled ipv6 for both ports. Let's see if I can find anything in the router logs - it's a Fritzbox and its logs are quite detailed.

Message 25 of 25
Top Contributors
Discussion stats
  • 24 replies
  • 1533 views
  • 0 kudos
  • 3 in conversation
Announcements