Post by omega on Feb 5, 2007 18:38:46 GMT 7
Hi,
in order to write my posting for Razzleultra I connected an USB disk to my N5200 and it is still connected. Now I wanted to access the "Module Mgmt" page and the entry is not available any more in the "System" pulldown menu.
So, as always in that kind of situation, I consulted again the definite manual - the source code - and the bug is in the file /img/www/htdocs/adm/menu/menu-footer.html.
There is some logic there whether to display the "Module Mgmt" entry or not. And that logic is wrong.
One precondition for showing the module management entry, /raid/data needs to be mounted. This check is done by this command:
df | awk -F " " '/data/ {print $6}'
Despite the fact that the -F flag is not needed in this case, the search for a line containing "data" results in at least two lines when a USB disk is mounted.
I would suggest this command as a bug fix:
df | awk '/\/raid\/data$/ { print $6 }'
as this command really does what it is supposed to do. It would be more error prone to check the complete path as the compare later compares against /raid/data.
Conclusion: with the current firmware 1.00.06.5 you cannot access the module management as long as there are any mounted filesystems on external USB drives. The same most likely applies to external attached eSATA drives too, but I haven't checked this.
As a workaround detach all your external attached drives whenever you want to access the module management.
For those who are using the IMGDUP module, just edit the buggy file and correct that single line as I described above. I've done it and it works for me. If you need more details, don't hesitate to ask.
Andreas
in order to write my posting for Razzleultra I connected an USB disk to my N5200 and it is still connected. Now I wanted to access the "Module Mgmt" page and the entry is not available any more in the "System" pulldown menu.
So, as always in that kind of situation, I consulted again the definite manual - the source code - and the bug is in the file /img/www/htdocs/adm/menu/menu-footer.html.
There is some logic there whether to display the "Module Mgmt" entry or not. And that logic is wrong.
One precondition for showing the module management entry, /raid/data needs to be mounted. This check is done by this command:
df | awk -F " " '/data/ {print $6}'
Despite the fact that the -F flag is not needed in this case, the search for a line containing "data" results in at least two lines when a USB disk is mounted.
I would suggest this command as a bug fix:
df | awk '/\/raid\/data$/ { print $6 }'
as this command really does what it is supposed to do. It would be more error prone to check the complete path as the compare later compares against /raid/data.
Conclusion: with the current firmware 1.00.06.5 you cannot access the module management as long as there are any mounted filesystems on external USB drives. The same most likely applies to external attached eSATA drives too, but I haven't checked this.
As a workaround detach all your external attached drives whenever you want to access the module management.
For those who are using the IMGDUP module, just edit the buggy file and correct that single line as I described above. I've done it and it works for me. If you need more details, don't hesitate to ask.
Andreas
(so many new members the last 4 weeks... fine 
)
(only joking... ;D )