NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
wsdd2 service failure after reboot
First reboot in month or so. I'm running 6.6.0 which has been super stable by the way. I shut the system down for an annual cleaning (just clean dust out of chassis really) and after booting wsdd2 service is seg faulting. I think this service has something to do with USB? Maybe I should reseat all the USB connectors and power cycle those devices?
It's strange because everything seems to be working fine. So I'm not sure what this service really does.
Thanks again. There's another update available now (or soon) that should fix the remaining issue.
21 Replies
Replies have been turned off for this discussion
I tried power cycling all the usb connected drives and then rebooted the nas. Same result for wsdd2:
ec 24 14:19:56 warehouse6 wsdd2[22719]: starting.
Dec 24 14:19:56 warehouse6 kernel: wsdd2[22719]: segfault at 0 ip 0000000000401ee0 sp 00007ffcdaf67170 error 4 in wsdd2[400000+a000]
Dec 24 14:19:56 warehouse6 systemd[1]: wsdd2.service: Main process exited, code=killed, status=11/SEGV
Dec 24 14:19:56 warehouse6 systemd[1]: wsdd2.service: Unit entered failed state.
Dec 24 14:19:56 warehouse6 systemd[1]: wsdd2.service: Failed with result 'signal'.I found another unresolved issue where the user was seeing this error in their logs. It might be frequent as you have to have ssh access to know about it. Nothing comes out in frontview about it. Can someone explain what this service really does?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
