by brinka123 » Mon Mar 17, 2014 7:41 am
Hi thanks for the focus on this issue.
My test setup was not OK with the 164 kernel, because nzbget was not fully operational due to user right problems. It looks like I solved the rights problems now.
So I didn't test on 164 yet.
To confirm that it is a difficult problem:
Last night 15-1 with nzbget 12.0 downloaded without a problem, but it was not parchecking and repairing due to the parcheck problems, it only downloaded. Maybe the issue occurs faster when parcheck and repairing is executed, this requires a lot of disk access. I also watched a movie (samba read) during downloading.
Does parchecking and reparing work at your side with nzbget 12.0??
I download items of 5 - 25 GB.....
Any idea how to approach such a problem ? I think we have to be able to reproduce it, but the external files we are downloading are not the same, it probably also independant of the file. But (I agree) circumstances.
So according to me test setup:
- File IO from samba (read,write) (To much load will block the nas console, but it doesn't crash)
- Download using nzbget.
- Http access by continuosly request page updates.
- Torrent download using transmission.
Then it will crash....
The crash is visible by the fact that
- the nas webpage is accessable, but no respons from actions.
- Also login with ssh is possible but commands like ps -f stop.
- The disk can't be switched off using the power button.
- Using samba, all files are normally accessable.
Regards.
PS send-file is switched off now, but maybe the root cause of the problem is not found yet.....