Loosing access to TS-809U

[odrakir]

Hi,

we have a TS-809U working flawlessly since day one, for the past 11 months. It's connected to our Active Directory and everything works fine. Since yesterday we experienced a strange behavior, we lost connection to the folder shares. No password is asked, nothing. We can access it by ssh and browser with no problems, but we have no access to the NAS via file sharing. We get only one error in the logs, a [SNMP] DoS detected from our Nagios server IP, which is working along side of the NAS with no problems at all.

If we try to reboot it or power it down either by web administration or SSH, it doesn't work. It just sits there. The only way to recover from this is to physically press the power button. After that it all works normally.

Today it happened again, almost at the same time. Same behavior. We've checked the logs on the NAS and on the Nagios server and everything looks normal.

Can some one help? Does anyone here experienced this? The NAS firmware is 3.3.6 Build 1110T.

Thanks!

[odrakir]

Update:

After monitoring /var/log/samba/log.winbindd-idmap I noticed these messages:

[2011/10/27 12:54:35.384776, 0] winbindd/idmap.c:201(smb_register_idmap_alloc)
idmap_alloc module ldap already registered!
[2011/10/27 12:54:35.384882, 0] winbindd/idmap.c:201(smb_register_idmap_alloc)
idmap_alloc module tdb already registered!
[2011/10/27 12:54:35.384920, 0] winbindd/idmap.c:149(smb_register_idmap)
Idmap module passdb already registered!
[2011/10/27 12:54:35.384955, 0] winbindd/idmap.c:149(smb_register_idmap)
Idmap module nss already registered!


Any clues?

[shanenzt]

I am experiencing the same problem, but we use the Qnap for iSCSI only and the iSCSI drives disappear although the target stays active.

When it happens I can not get any info on the drives in the web console, I can not reboot or shutdown from the web console.

The only error in the web console logs is [SNMP] DoS detected

We are running firmware 3.3.3 but it's been running fine with this firmware and setup for over a year.

Did you ever find out what was causing this?

[schumaku]

The only error in the web console logs is [SNMP] DoS detected

Any IP addresses locked-out? If oyu ae lucky, the SNMP DoS detected is form the iSCSI initiator system - and then you might be blocked.

[shanenzt]

After two of these incidents with the disks stopping working and the QNap not being able to be restarted, I now have a failed disk.

Status = Disk Read/Write Error

I wonder if the problem all along was just the disk starting to fail and this was causing the whole disk system to become unresponsive?

Strange there was no mention of disks issues in the logs on the previous two issues, although when we hard reset the QNAP to get it responding again it did log these events:

[RAID5 Disk Volume: Drive 1 2 3 4] The file system is not clean. It is suggested that you run "check disk".
[RAID5 Disk Volume: Drive 1 2 3 4] Start resyncing.

Thanks

[shanenzt]

The only error in the web console logs is [SNMP] DoS detected

Any IP addresses locked-out? If oyu ae lucky, the SNMP DoS detected is form the iSCSI initiator system - and then you might be blocked.

The DoS events were from our SNMP server which is a different server to our iSCSI initiator.

And the unresponsiveness was also apparent in the Qnaps web console, if I clicked on RAID management or HDD Smart or ISCSI it just loaded and loaded and then eventually came back with Drive information request failure alert in the web console

Thanks for your reply.