|
|
Post by omega on Sept 11, 2007 20:45:24 GMT 7
Hi,
I have finally upgraded my N5200 from FW 1.00.10 to 2.00.01 in order to be able to find the reasons for some strange problems reported recently with that versions and the module management.
I'd like to use this thread to discuss any problems with any modules which are or might be somehow related to version 2.00.01 or alike.
Up to now I haven't experienced any problems with 2.00.01 and any modules. I've reinstalled some of them (including USHARE) and everything works. So at the moment I'm not able to reproduce any of the reported problems.
I've corrected the INFO module so it should work for the 2.00.01 and even for the older firmware versions.
I'll keep you informed.
Andreas
|
|
|
|
Post by georg54 on Sept 12, 2007 0:28:20 GMT 7
Hi Andreas, " I've reinstalled some of them (including USHARE) and everything works"...  I do not understand that.... (USHARE)  Module configuration: SYSUSER, SSHD, INFO, MLdonkey and TWONKYMEDIA (uninstall bevor install USHARE) br georg |
|
|
|
Post by peterfu on Sept 12, 2007 0:45:10 GMT 7
... So at the moment I'm not able to reproduce any of the reported problems... May be the problems result in a different file system structure as it seems theres a difference if You build a RAID new with FW 2.00.01 or upgrade with an existing RAID from FW 1.00.10 to FW 2.00.01. At least in the official thecus forum on hexus Yvon (the Thecus official) mentioned something about changes in the filesystem. So may be a good question for analyzing the problems would be if the N5200 was upgraded with existing raid or the raid was build with FW 2.00.01. br Peter PS : Release notes would realy help  |
|
|
|
Post by omega on Sept 12, 2007 1:51:47 GMT 7
Hi Georg,
what is unclear to you?
I only wanted to point out that after upgrading to 2.00.01 I've uninstalled and installed again the USHARE module and didn't see any errors.
Do you have any idea how I can reproduce the error you were experiencing?
Andreas
|
|
|
|
Post by georg54 on Sept 12, 2007 15:06:42 GMT 7
Hi Andreas, unclear: why you do not have errors I did not have alone the problem..!no, I do not have an idea (I do not install USHARE again  ) but an idea:  - you uninstalled and installed again the USHARE module - I've installed the USHARE module br georg |
|
|
|
Post by omega on Sept 12, 2007 17:53:41 GMT 7
Hi everybody, finally I've found the reason for USHARE module misbehaving like it does - after reinstallation and deletion of the module backup data the same errors happend to me too. The error is just small but has really bad consequences.... So first of all I beg for pardon: I'm really sorry that the USHARE module was giving real troubles to some of you!  I'd like to give a short explanation what was wrong: The start/stop script /raid/data/module/USHARE/Shell/module.rc reads the command line how to start ushare from an sqlite database. After the initial install this database is empty and therefore the command for starting ushare is empty too. In the script module.rc there is a call to ProcKillall which is called on start and stop of the module which kills all running ushare processes. Because the command was an empty string ProcKillall killed almost all killable processes. As a result power cycling the device was the only way to bring the device to live again. If someone still has the buggy version 2.00.00 of USHARE installed, there are two possibilities how to fix it until a corrected version is available: 1) Rename the file /raid/data/module/USHARE/Shell/module.rc to something different. In this case the module is not working anymore after reboot. 2) Edit the file /raid/data/module/USHARE/Shell/module.rc and protect the call to ProcKillall so that it won't be called with an empty string. Most of you won't do this and in fact it would be the best to do solution 1) and wait for the fixed version. I want to conclude that this is a stupid error which only applies to the USHARE module. As I'm running FW 2.00.01 now and I was doing a lot of tests with the other modules the last days, I can tell you that there are no known problems (at least to me) running the modules on FW 2.00.01 - at least no disastrous ones. Andreas |
|
|
|
Post by georg54 on Sept 13, 2007 3:12:37 GMT 7
|
|
|
|
Post by omega on Sept 13, 2007 5:52:48 GMT 7
There is one issue with FW 2.00.01 which really disturbs me: whenever a module gets uninstalled, I only see the message "uninstall pass" on an otherwise empty page and I'm not redirected to the module overview page.
Am I the only who gets this behavior?
I checked the source code (/img/www/htdocs/adm/module.html) and the code there outputs this message and then it outputs a "header('Location: /adm/getform.html?name=module')".
If I'm correct there mustn't be any output before the redirect command and therefore the redirect directive is not working.
It seems to me that this is a leftover from debugging.
Thecus: please correct this for the next version!
Andreas
|
|
|
|
Post by gideon007 on Sept 13, 2007 6:42:12 GMT 7
Yes, or at least similar, I don't quite remember what I got, but something like that and I wondered what now... That aside, are the SSH and Shutdown modules dependant on the imgdup module? I though not but the other day when I was trying I couldn't get it to work, but didn't have time to look more closely at it, since I just wanted to quickly shutdown  |
|
|
|
Post by georg54 on Sept 13, 2007 7:56:54 GMT 7
There is one issue with FW 2.00.01 which really disturbs me: whenever a module gets uninstalled, I only see the message "uninstall pass" on an otherwise empty page and I'm not redirected to the module overview page. Am I the only who gets this behavior? ..... Andreas br georg |
|
|
|
Post by gideon007 on Sept 30, 2007 18:53:59 GMT 7
hmm, I still can't get the shutdown or reboot modult to work with the 2.00.01 firmware. All it does is log me in as either the user reboot or shutdown but it doesn't do what is expected of it AND my question is whethter this module is dependant on imgdup module. In the wiki it doesn't say so. Unfortunately I made the mistake of re-enabling imgdup (I had it disabled due to an old problem I donT' remember anymore). After I enabled imgdup, my thecuse seemed to have reverted back to the 1.00.6.5 firmware. VERY strange. The module ppage link also disappeared from the system menu. Does anyone have any idea how to get back into my Thecus and get rid of the imgdup module? I can't even ssh into it (I can still get onto the web admin page, though) |
|
|
|
Post by gideon007 on Sept 30, 2007 19:15:09 GMT 7
After panicking, I brute forced imgdup out of the system.
I could't ssh as users sys but as user reboot (strange but true) and this way I went onto /raid/data and deleted the directory IMGDUP in /modules. After that I had to brutally shut off the Thecus, and boot it again and I was back onto the 2.00.01 Web admin page, my data was accessible again and also the module page. It still shows imgdup as enabled but I can't uninstall it or remove it.
Any idea what happened there and how I can get rid of the imgdup leftovers?
|
|
)
