Please have a look.

 

 

I see unmenu invoked twice. Can one of them be deleted? Which one? Hopefully this is the source of many "bad method" lines in my syslog. Prostuff thanks.

go.txt

delete the first of the lines invoking unmenu.  You might replace it with a command to let emhttp finish starting the array before everything else.

 

instead of the first

/boot/unmenu/uu

put

while ! test -d /mnt/disk1; do sleep 5; continue; done

 

That command will loop testing for the existence of the mounted disk1 until continuing.

 

delete the first of the lines invoking unmenu.  You might replace it with a command to let emhttp finish starting the array before everything else.

 

instead of the first

/boot/unmenu/uu

put

while ! test -d /mnt/disk1; do sleep 5; continue; done

 

That command will loop testing for the existence of the mounted disk1 until continuing.

 

Is this just adding some conditional delay when booting? It is better then just killing unmenu start-up?

 

Why only test for disk1?

 

Just like to know.

delete the first of the lines invoking unmenu.  You might replace it with a command to let emhttp finish starting the array before everything else.

 

instead of the first

/boot/unmenu/uu

put

while ! test -d /mnt/disk1; do sleep 5; continue; done

 

That command will loop testing for the existence of the mounted disk1 until continuing.

 

Is this just adding some conditional delay when booting? It is better then just killing unmenu start-up?

 

Why only test for disk1?

 

Just like to know.

unMENU itself does not interfere with the start up of emhttp.   

However, some of the packages that can be installed via its package manager can be configured to use directories on the user and disk shares.  If those locations are accessed BEFORE they are created, they will fail and could also keep the array from starting properly since the mount points will not be empty.

 

So, the goal is to keep any add-ons from installing/running until the array is online.

 

I picked disk1 only because you are likely to have one.  If you like, you can use the number of the highest numbered disk you have in your array, or you can use /mnt/user/sharename

 

The goal again is to prevent anything being installed from keeping unRAID from starting properly.

 

Joe L.

Can I chech this in the syslog?