This is a second round of problems I am having with my main unraid server (FS1). The first batch of problems is documented here:

http://lime-technology.com/forum/index.php?topic=15866.0

and it was mostly solved, except for the unmenu "bad-method" errors that keep popping up.

 

I am now running unraid 5 beta 13. The only add-ons I have running are unmenu and cache-dirs, the latest versions of both I believe.

 

This is what is happening:

 

1 - Login - Yesterday I found out I could not login to unraid main anymore. I get a prompt "The server at 10.199.54.20:80 requires a username and password. The server says unRAID SMU". I do not remember changing any password.

I thought I found a solution to reset root password here:

http://lime-technology.com/forum/index.php?topic=2414.0

I powered down, removed the "passwd" file from /flash/config, and restarted: still could not login

 

Right now unmenu is the only way I have to access the server, I am sure glad it's installed. Often the same username / password prompt appears on the unmenu page as well, but simply clicking "cancel" allows the page to be shown. If I click cancel at the prompt on port 80 (unraid main), all I get is a blank page

 

2 - Unmenu package manager - openssh does not get re-installed upon reboot. Every time the machine is re-started, openssh shows as uninstalled. I tried installing a different package (htop), and it got re-installed at reboot.

Other packages installed are apcuspd, lighttpd and powerdown. Other few packages are shown and "installed, not downloaded" like mc and gamin for instance, which I don't remember installing

 

3 - Missing icons - some unmenu icons are missing from the web page. Occasionally I get a 404 page not found error. Hit refresh and the page is back

 

4 - flash drive -  run a chkdsk on the USB flash drive: it found some errors in the file system and fixed them

 

5 - lost access to flash share - I used to be able to access all share via UNC, including \\fs1\flash. As of this morning (!), a windows network security username/ password box pop-up, so apparently I lost access to the flash share as well. All other shares are still accessible.

 

6 - bad-method - unmenu keep pelting the syslog with a bunch of errors that look like this:

Oct 29 09:57:27 FS1 unmenu[3146]: bad method - 17551 339 141769 193460 9 3 96 100 0 192870 19356017551-^M

this is apparently caused by some device on my network scanning all ports in a way unmenu does not like. I am having a hard time figuring out the source of the problem however, compared with these other newer issues, it feels more like a nuisance. I thought I mentioned as a piece of the picture

 

7 - the good news - all the media shares are working. A parity check was run just yesterday with zero errors. All drives are on green. I have a recent copy of all the data on the backup server

 

On the one hand, I am tempted to restart from scratch with a fresh 4.7 unraid install, and forget about beta releases. On the other hand, I am not sure how much this has to do with me using 5beta in the first place; and also would like to figure out what is causing the problems, rather than by-passing them. Especially losing the ability to login is cause for concern.

 

Any insight? 

 

Luca

syslog-2011-10-29.zip

the unMenu bad method error try hitting the "Kill unMenu" button on the user scripts page.

 

I have notice lately that this is happening to me and if you do a ps -ef looking for the processes id it gave you (3146) then you will probably see that it is a logger that looks similar to:

logger -tunmenu -plocal7.info -is

 

if you do a ps -ef | grep unmenu and see 2 of the logger processes you will need to kill one and see if that stops the bad method errors.

thanks prosuff, but I went for a fresh start.  My xbmc zotac box started asking for a username/password to open a file, soon after I posted my message. Pressure mounted to get things fixed quickly.   Funny I could still access the media shares from my computer.

 

I took a snapshot my USB stick, and slow formatted it. Re-installed a freshly-downloaded copy of 5b13. Server was up and running in 1/2 an hour. Put a strong password right away on the root account. Parity check run, zero errors. I'm attaching a syslog from this new install, if anyone's interested.

 

I still have to see any "bad-method" errors with the new install. Is it at all possible that these bad-methods were symptoms of something screwy on the unraid server itself (and not by an external device)?

syslog-2011-10-30.zip