Tried to update remotely (its cold outside, do not want to freeze my butt in the garage), started normally, but unmounting the array got stuck with a non existing file beeing busy. Had to kill shfs after an hour of waiting. But the rest went ok.,

Then I waited for the box to reappear in the LAN, and soon after, the ping was working again.

SSH worked too, but NO WEBINTERFACE

(and of course, all the unraid stuff has not been started too)

I looked for "emhttpd", but even "which" told me, there was none on the stick anymore!

So, what to launch???

 

I reverted to the old 6.12.14 just by copying "previous" to "/" and rebooting. Reboot got stuck again... had to use the reset switch!

 

6.12.14 came back up fine again, not even a parity check was needed! Fine.

 

So once more trying to update... this time without a stuck file.

Update went ok, rebooting... NO GUI! again.

Same procedure as before, no emhttp, no unraid started. just a minimal linux. (this time again I was in the garage, dispite the cold)

 

Reverted to 6.12.14 again, giving up on 7!

 

I have a 7 beta box (fresh install) which works fine, but updating a real one obviously does not work!

So, what am I missing (or what did the update forgot to change? "emhttpd" now elsewhere, renamed, whatever???)

 

 

Please post the diagnostics after updating.

not possible, even the basic linux does not work correctly

 

but I have managed to find the differences that Limetech forgot to update:

 

* /usr/local/bin/emhttpd has been moved to /usr/libexec/unraid/emhttpd

* the 7.0 "go" file is NOT updated. The new startscript seems to be now /usr/local/sbin/emhttp (without the leading "d")

 

This is a really stupid mistake, if you move files (which is stupid by itself already, thats why I hate Linux that much), you should also look for and update all references.

A normal user has no chance to find this error.

Maybe I am able to correct it... I will give it another try now (brrrrr, cccccooooooold...)

 

Hmm, I just see, that /usr/local/sbin stuff is on 6.12.14 too already. But the link in go has never been updated. So the bug must have happened a few versions before already and did not show up because there was a symlink.... LINUX!!!

Edited January 10, 20251 yr by MAM59

15 minutes ago, MAM59 said:

 

 

* /usr/local/bin/emhttpd has been moved to /usr/libexec/unraid/emhttpd

* the 7.0 "go" file is NOT updated. The new startscript seems to be now /usr/local/sbin/emhttp (without the leading "d")

 

7 starts fine with
 

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp 

not sure what youre looking for


the only change that happened was the removal of the & at some point

Solved!

Maybe I should summerize to warn potential users:

 

If updating from a very old (not clear how old, better check always) to 7.0 take a look into the /boot/config/go file before!

if it contains a line like

/usr/local/bin/emhttpd &

change it to
/usr/local/sbin/emhttp

before.

(if you forget the unraid management stuff may not be started after the update. you can ssh in and start it manually by running /usr/local/sbin/emhttp but correct the go file then to prevent further problems)

 

2 minutes ago, Mainfrezzer said:

the only change that happened was the removal of the & at some point

No! the change was from emhttpd to emhttp !!!

 

Just now, MAM59 said:

No! the change was from emhttpd to emhttp !!!

 

/usr/local/sbin/emhttp &

this is from 6.11.5, not sure what version are you on that you have emhttpd^^

Just now, Mainfrezzer said:

this is from 6.11.5, not sure what version are you on that you have emhttpd^^

As I said, this error happened long ago and was covered by a symlink. Maybe even before V6 already, I cannot check anymore.