unMENU 1.5 ... now available for download.


Recommended Posts

any plans to make the preclear script part of unmenu ?

we have already a disk management tab

just add a button for each drive in the "not in protected array" part of the screen

and remove the cache drive from there ... he has his own section anyway on the main screen

 

or you could make a new tab for it... then you can make a progress screen...  just make sure the disks in the array can not be precleared :)

 

would make it easier for us lazy people :)

anyway love the preclear function... another 4 disks to clear and then can take advantage of all 12 drive :)

 

That will more than likely NOT happen in the current version of unMenu.  It waits for output to come back and the preclear script would hang the browser for 30 hours (depending on the size of the drive).

 

Once 5.0 is stable the preclear script may get an update to integrated it into the native 5.0 web interface.  That is probably a ways off though and won't happen in the near future.

True... I would love to get a graphical interface... but would not want to wait 30+ hours for a web-page to finish loading.  ;D 

 

It will take a re-structure of the preclear script.  I would need to split up the clearing task from the display/monitoring task.  Then we could start the task in the background, let it run, and then check on its status occasionally.

 

Joe L.

Link to comment
  • Replies 1.3k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

ls -l /boot/unmenu/images

(we expect the "images" directory to have been created and in it a "stock" sub-directory with most of the image files.  The image directory is new with the new release of the myMain plugin.

 

root@Tower:~# ls -l /boot/unmenu/images
total 160
-rwx------ 1 root root 120047 Dec  6 10:45 MyServer.jpg*
-rwx------ 1 root root  33072 Dec  6 10:45 MySlots.jpg*
drwx------ 2 root root   4096 Dec  6 10:45 stock/

 

The older unmenu_install program had no concept of dealing with sub-directories.  For that reason a new version had to be developed.  To see if you have the new version, type:

ls -l /boot/unmenu/unmenu_install

root@Tower:~# ls -l /boot/unmenu/unmenu_install
-rwx------ 1 root root 13168 Dec 19 08:54 /boot/unmenu/unmenu_install*

and

grep Revision /boot/unmenu/unmenu_install | grep RELEASE

 

The output of the "grep" should look like this:

#UNMENU_RELEASE $Revision: 186 $ $Date: 2010-12-04 14:58:29 -0500 (Sat, 04 Dec 2010)

 

root@Tower:~# grep Revision /boot/unmenu/unmenu_install | grep RELEASE
#UNMENU_RELEASE $Revision: 186 $ $Date: 2010-12-04 14:58:29 -0500 (Sat, 04 Dec 2010) $

 

 

I think, as the grep matches.. I don't need to follow the instructions in the rest of this post?

Link to comment

The only thing left is to look at the files in the "stock" subdirectory.

 

ls -l /boot/unmenu/stock

 

and to see if it got linked to the /var directory. 

type

ls -l /var/log

the output should look much like this  (we are interested in the line in BLUE showing the link from "images" to /boot/unmenu/images):

-rw-r----- 1 root root    80 Dec 18 23:54 acpid

-rw-r--r-- 1 root root      0 Dec 18 23:54 cron

-rw-r--r-- 1 root root  27867 Dec 18 23:54 dmesg

lrwxrwxrwx 1 root root    26 Dec 18 23:54 images -> /boot/unmenu/images/

drwxr-xr-x 2 root root      0 Dec 18 23:54 packages/

-rw-r--r-- 1 root root  17973 Dec 20 00:27 release_list

drwxr-xr-x 2 root root      0 Dec 18 23:54 removed_packages/

drwxr-xr-x 2 root root      0 Dec 18 23:54 removed_scripts/

drwxr-xr-x 3 root root      0 Dec 18 23:54 samba/

drwxr-xr-x 2 root root      0 Dec 18 23:54 scripts/

drwxr-xr-x 3 root root      0 Dec  6 18:18 setup/

-rw-r--r-- 1 root root 253452 Dec 20 15:09 syslog

 

As I said in my earlier post, the images sub-directory needs to be linked to the /var/log directory for the image server to find them  That "link" is only made once when you first invoke the myMain

plugin.  To force the "link" to be created you can type:

rm  /tmp/mymain_seq.txt

and then refresh the myMain web-page.  (much simpler than rebooting the entire unRAID server)

 

Joe L.

Link to comment

Not sure where to ask this question.

 

I have unmenu installed and using the email notification script.  It was working perfectly when i was on 4.5.6.  I had upgraded to 4.5.8.  Whenever i reboot my unraid server the machine always does a parity check.  Don't really mind this and never thought about it. Receive email notifications throughout the time telling me on an hourly basis of how much time is left as well as percentage complete.

 

Now here is the weird problem, since upgrading both 4.5.8 and the latest unmenu.  I keep getting emails every hour saying that it is  "Parity CHECK/RESYNC in progress,  0% complete,  est. finish in 0 minutes. Speed: 0 kb/s." even after it has completed.  The mymenu and "unraid mani" both say Parity has been completed and is ok.

 

What is going on?

 

Link to comment

The only thing left is to look at the files in the "stock" subdirectory.

 

ls -l /boot/unmenu/stock

 

and to see if it got linked to the /var directory. 

type

ls -l /var/log

the output should look much like this  (we are interested in the line in BLUE showing the link from "images" to /boot/unmenu/images):

-rw-r----- 1 root root     80 Dec 18 23:54 acpid

-rw-r--r-- 1 root root      0 Dec 18 23:54 cron

-rw-r--r-- 1 root root  27867 Dec 18 23:54 dmesg

lrwxrwxrwx 1 root root     26 Dec 18 23:54 images -> /boot/unmenu/images/

drwxr-xr-x 2 root root      0 Dec 18 23:54 packages/

-rw-r--r-- 1 root root  17973 Dec 20 00:27 release_list

drwxr-xr-x 2 root root      0 Dec 18 23:54 removed_packages/

drwxr-xr-x 2 root root      0 Dec 18 23:54 removed_scripts/

drwxr-xr-x 3 root root      0 Dec 18 23:54 samba/

drwxr-xr-x 2 root root      0 Dec 18 23:54 scripts/

drwxr-xr-x 3 root root      0 Dec  6 18:18 setup/

-rw-r--r-- 1 root root 253452 Dec 20 15:09 syslog

 

As I said in my earlier post, the images sub-directory needs to be linked to the /var/log directory for the image server to find them  That "link" is only made once when you first invoke the myMain

plugin.   To force the "link" to be created you can type:

rm  /tmp/mymain_seq.txt

and then refresh the myMain web-page.  (much simpler than rebooting the entire unRAID server)

 

Joe L.

 

OK.. so the issue may be where the stock folder is then.. as mine is under the "images" folder e.g. /boot/unmenu/images/stock

 

ls -l /boot/unmenu/stock returns:

root@Tower:~# ls -l /boot/unmenu/stock
/bin/ls: cannot access /boot/unmenu/stock: No such file or directory

 

I'm going to assume this may be a typo and you missed the images folder out of the command and continue with the other tests:

 

ls -l /var/log returns:

 

root@Tower:~# ls -l /var/log
total 6912
-rw-r----- 1 root root      80 Dec 21 06:02 acpid
-rw-r--r-- 1 root root       0 Dec 21 06:02 cron
-rw-r--r-- 1 root root   30603 Dec 21 06:02 dmesg
-rw-r--r-- 1 root root      53 Dec 21 06:02 go
lrwxrwxrwx 1 root root      19 Dec 21 06:02 images -> /boot/unmenu/images/
drwxr-xr-x 2 root root       0 Dec 21 06:02 packages/
drwxr-xr-x 2 root root       0 Dec 21 06:02 removed_packages/
drwxr-xr-x 2 root root       0 Dec 21 06:02 removed_scripts/
drwxr-xr-x 3 root root       0 Dec 21 06:02 samba/
drwxr-xr-x 2 root root       0 Dec 21 06:02 scripts/
drwxr-xr-x 3 root root       0 Dec 21 06:01 setup/
-rw-r--r-- 1 root root 7036640 Dec 21 15:05 syslog

 

rm  /tmp/mymain_seq.txt

 

I did this, and refreshed the mymain page, and unfortunately still no images!  I must be doing something simple wrong, i'm sure of it!!

Link to comment

ls -l /boot/unmenu/stock returns:

root@Tower:~# ls -l /boot/unmenu/stock
/bin/ls: cannot access /boot/unmenu/stock: No such file or directory

 

I'm going to assume this may be a typo and you missed the images folder out of the command and continue with the other tests:

Yes, it was a typo.  Sorry.

 

ls -l /var/log returns:

 

root@Tower:~# ls -l /var/log
total 6912
-rw-r----- 1 root root      80 Dec 21 06:02 acpid
-rw-r--r-- 1 root root       0 Dec 21 06:02 cron
-rw-r--r-- 1 root root   30603 Dec 21 06:02 dmesg
-rw-r--r-- 1 root root      53 Dec 21 06:02 go
lrwxrwxrwx 1 root root      19 Dec 21 06:02 images -> /boot/unmenu/images/
drwxr-xr-x 2 root root       0 Dec 21 06:02 packages/
drwxr-xr-x 2 root root       0 Dec 21 06:02 removed_packages/
drwxr-xr-x 2 root root       0 Dec 21 06:02 removed_scripts/
drwxr-xr-x 3 root root       0 Dec 21 06:02 samba/
drwxr-xr-x 2 root root       0 Dec 21 06:02 scripts/
drwxr-xr-x 3 root root       0 Dec 21 06:01 setup/
-rw-r--r-- 1 root root 7036640 Dec 21 15:05 syslog

 

rm  /tmp/mymain_seq.txt

 

I did this, and refreshed the mymain page, and unfortunately still no images!  I must be doing something simple wrong, i'm sure of it!!

The output shows that the /var/log/images directory is linked to /boot/unmenu/images.  That is correct.

 

I don't see anything wrong you've done...  not so far anyway.

 

What do you see when you type:

ls -l  /var/log/images/stock

 

Also.  what browser are you using?  (probably has absolutely nothing to do with anything, but just figured I'd ask)

 

Joe L.

Link to comment

 

What do you see when you type:

ls -l  /var/log/images/stock

 

Also.  what browser are you using?  (probably has absolutely nothing to do with anything, but just figured I'd ask)

 

Joe L.

 

Hi Joe, thanks for continuing to help!  Heres the output of that command:

 

root@Tower:~# ls -l  /var/log/images/stock
total 588
-rwx------ 1 root root   1640 Dec  6 10:45 Hitachi.png*
-rwx------ 1 root root   2914 Dec  6 10:45 Kingston.png*
-rwx------ 1 root root   5803 Dec  6 10:45 Maxtor.png*
-rwx------ 1 root root 120047 Dec  6 10:45 MyServer_sample.jpg*
-rwx------ 1 root root  33072 Dec  6 10:45 MySlots_sample.jpg*
-rwx------ 1 root root  71228 Dec  6 10:45 Samsung.png*
-rwx------ 1 root root  10141 Dec  6 10:45 Seagate.png*
-rwx------ 1 root root   2831 Dec  6 10:45 WD.png*
-rwx------ 1 root root   2673 Dec  6 10:45 bolt.png*
-rwx------ 1 root root   1522 Dec  6 10:45 down.png*
-rwx------ 1 root root  11077 Dec  6 10:45 myMainLogo.jpg*
-rwx------ 1 root root  24936 Dec  6 10:45 refresh.png*
-rwx------ 1 root root  11917 Dec  6 10:45 refreshall.png*
-rwx------ 1 root root   1102 Dec  6 10:45 spinning.gif*
-rwx------ 1 root root  19845 Dec  6 10:45 status_bt.gif*
-rwx------ 1 root root   9225 Dec  6 10:45 status_cache.png*
-rwx------ 1 root root  18677 Dec  6 10:45 status_dsbl.png*
-rwx------ 1 root root   3227 Dec  6 10:45 status_dsbl_new.png*
-rwx------ 1 root root  18677 Dec  6 10:45 status_dsbl_np.png*
-rwx------ 1 root root   2577 Dec  6 10:45 status_invalid.png*
-rwx------ 1 root root   2219 Dec  6 10:45 status_mt.gif*
-rwx------ 1 root root   3391 Dec  6 10:45 status_new.gif*
-rwx------ 1 root root  80213 Dec  6 10:45 status_np.png*
-rwx------ 1 root root  80213 Dec  6 10:45 status_np_missing.png*
-rwx------ 1 root root   3418 Dec  6 10:45 status_ok.png*
-rwx------ 1 root root   3391 Dec  6 10:45 status_raw.gif*
-rwx------ 1 root root   3254 Dec  6 10:45 status_wrong.png*
-rwx------ 1 root root   1433 Dec  6 10:45 up.png*
root@Tower:~#

 

I'm using Firefox, but have also tried IE8.

Link to comment

What version of unRAID are you running? 

 

I see that the permissions on the files in your images/stock directory make the images readable only by root on your server, and on mine they are readable by anybody.

 

Is the /boot/unmenu folder on your flash drive? 

Something about your server is making the permissions on the downloaded files in the images directory different.  Perhaps you'll be able to describe what might be different?

 

In any case, it is easy to see why you do not see the images on the web-browser.  The unMENU image-server is being run as user "nobody" and therefore would not have permission to read the image files on your server.  (they are currently only readable by user "root")

 

The solution is to make your image files readable by all (and the directories search-able by all too).

 

Type the following commands and odds are good you'll see the images.

chmod og+rx /var/log/images

chmod +rx /var/log/images/stock

chmod +r  /var/log/images/*

chmod +r /var/log/images/stock/*

 

Joe L.

Link to comment

What version of unRAID are you running?   

 

I see that the permissions on the files in your images/stock directory make the images readable only by root on your server, and on mine they are readable by anybody.

 

Is the /boot/unmenu folder on your flash drive? 

Something about your server is making the permissions on the downloaded files in the images directory different.  Perhaps you'll be able to describe what might be different?

 

In any case, it is easy to see why you do not see the images on the web-browser.  The unMENU image-server is being run as user "nobody" and therefore would not have permission to read the image files on your server.   (they are currently only readable by user "root")

 

The solution is to make your image files readable by all (and the directories search-able by all too).

 

Type the following commands and odds are good you'll see the images.

chmod og+rx /var/log/images

chmod +rx /var/log/images/stock

chmod +r  /var/log/images/*

chmod +r /var/log/images/stock/*

 

Joe L.

 

Hi Joe,

 

I'm running 4.4.2 and yes the boot/unmenu folder is on my flash drive.  As far as I know I haven't done anything out of the ordinary, as I wouldn't know how! :)

 

I've run those commands, but I don't think i'm seeing anything change..

 

root@Tower:~# ls -l  /var/log/images/stock
total 588
-rwx------ 1 root root   1640 Dec  6 10:45 Hitachi.png*
-rwx------ 1 root root   2914 Dec  6 10:45 Kingston.png*
-rwx------ 1 root root   5803 Dec  6 10:45 Maxtor.png*
-rwx------ 1 root root 120047 Dec  6 10:45 MyServer_sample.jpg*
-rwx------ 1 root root  33072 Dec  6 10:45 MySlots_sample.jpg*
-rwx------ 1 root root  71228 Dec  6 10:45 Samsung.png*
-rwx------ 1 root root  10141 Dec  6 10:45 Seagate.png*
-rwx------ 1 root root   2831 Dec  6 10:45 WD.png*
-rwx------ 1 root root   2673 Dec  6 10:45 bolt.png*
-rwx------ 1 root root   1522 Dec  6 10:45 down.png*
-rwx------ 1 root root  11077 Dec  6 10:45 myMainLogo.jpg*
-rwx------ 1 root root  24936 Dec  6 10:45 refresh.png*
-rwx------ 1 root root  11917 Dec  6 10:45 refreshall.png*
-rwx------ 1 root root   1102 Dec  6 10:45 spinning.gif*
-rwx------ 1 root root  19845 Dec  6 10:45 status_bt.gif*
-rwx------ 1 root root   9225 Dec  6 10:45 status_cache.png*
-rwx------ 1 root root  18677 Dec  6 10:45 status_dsbl.png*
-rwx------ 1 root root   3227 Dec  6 10:45 status_dsbl_new.png*
-rwx------ 1 root root  18677 Dec  6 10:45 status_dsbl_np.png*
-rwx------ 1 root root   2577 Dec  6 10:45 status_invalid.png*
-rwx------ 1 root root   2219 Dec  6 10:45 status_mt.gif*
-rwx------ 1 root root   3391 Dec  6 10:45 status_new.gif*
-rwx------ 1 root root  80213 Dec  6 10:45 status_np.png*
-rwx------ 1 root root  80213 Dec  6 10:45 status_np_missing.png*
-rwx------ 1 root root   3418 Dec  6 10:45 status_ok.png*
-rwx------ 1 root root   3391 Dec  6 10:45 status_raw.gif*
-rwx------ 1 root root   3254 Dec  6 10:45 status_wrong.png*
-rwx------ 1 root root   1433 Dec  6 10:45 up.png*
root@Tower:~# chmod og+rx /var/log/images
root@Tower:~# chmod +rx /var/log/images/stock
root@Tower:~# chmod +r  /var/log/images/*
root@Tower:~# chmod +r /var/log/images/stock/*
root@Tower:~# ls -l  /var/log/images/stock
total 588
-rwx------ 1 root root   1640 Dec  6 10:45 Hitachi.png*
-rwx------ 1 root root   2914 Dec  6 10:45 Kingston.png*
-rwx------ 1 root root   5803 Dec  6 10:45 Maxtor.png*
-rwx------ 1 root root 120047 Dec  6 10:45 MyServer_sample.jpg*
-rwx------ 1 root root  33072 Dec  6 10:45 MySlots_sample.jpg*
-rwx------ 1 root root  71228 Dec  6 10:45 Samsung.png*
-rwx------ 1 root root  10141 Dec  6 10:45 Seagate.png*
-rwx------ 1 root root   2831 Dec  6 10:45 WD.png*
-rwx------ 1 root root   2673 Dec  6 10:45 bolt.png*
-rwx------ 1 root root   1522 Dec  6 10:45 down.png*
-rwx------ 1 root root  11077 Dec  6 10:45 myMainLogo.jpg*
-rwx------ 1 root root  24936 Dec  6 10:45 refresh.png*
-rwx------ 1 root root  11917 Dec  6 10:45 refreshall.png*
-rwx------ 1 root root   1102 Dec  6 10:45 spinning.gif*
-rwx------ 1 root root  19845 Dec  6 10:45 status_bt.gif*
-rwx------ 1 root root   9225 Dec  6 10:45 status_cache.png*
-rwx------ 1 root root  18677 Dec  6 10:45 status_dsbl.png*
-rwx------ 1 root root   3227 Dec  6 10:45 status_dsbl_new.png*
-rwx------ 1 root root  18677 Dec  6 10:45 status_dsbl_np.png*
-rwx------ 1 root root   2577 Dec  6 10:45 status_invalid.png*
-rwx------ 1 root root   2219 Dec  6 10:45 status_mt.gif*
-rwx------ 1 root root   3391 Dec  6 10:45 status_new.gif*
-rwx------ 1 root root  80213 Dec  6 10:45 status_np.png*
-rwx------ 1 root root  80213 Dec  6 10:45 status_np_missing.png*
-rwx------ 1 root root   3418 Dec  6 10:45 status_ok.png*
-rwx------ 1 root root   3391 Dec  6 10:45 status_raw.gif*
-rwx------ 1 root root   3254 Dec  6 10:45 status_wrong.png*
-rwx------ 1 root root   1433 Dec  6 10:45 up.png*
root@Tower:~#

 

Would i need a reboot after making these changes?

Link to comment

i just tried with a small 20mg file and my main box(nas-screenshot) shows both read and send with bold text but the new box (tower-screenshot) does show anything in bold..

did you install bwm-ng on the new box?  It is what unMENU's myMain screen uses to report on i/o activity.

 

Joe L.

Link to comment

i just tried with a small 20mg file and my main box(nas-screenshot) shows both read and send with bold text but the new box (tower-screenshot) does show anything in bold..

did you install bwm-ng on the new box?  It is what unMENU's myMain screen uses to report on i/o activity.

 

Joe L.

 

that was it, thanks for the help...

 

Link to comment

Does the

unmenu_install -c

command download new updates, or just checked to see if there are any new updates?

The "-c" option just alerts you of updates.  It does not download or install them. 

 

It does download a "release_list" that contains the file names and expected checksums.  Those files on your server are compared to determine if they have those checksums.  If they do not, or if they are missing on your server, they will be downloaded and installed if you subsequently invoke with the -u option.

 

The release_list looks like this: http://code.google.com/p/unraid-unmenu/source/browse/trunk/release_list

 

Joe L.

Link to comment

Does the

unmenu_install -c

command download new updates, or just checked to see if there are any new updates?

The "-c" option just alerts you of updates.  It does not download or install them. 

 

It does download a "release_list" that contains the file names and expected checksums.  Those files on your server are compared to determine if they have those checksums.  If they do not, or if they are missing on your server, they will be downloaded and installed if you subsequently invoke with the -u option.

 

The release_list looks like this: http://code.google.com/p/unraid-unmenu/source/browse/trunk/release_list

 

Joe L.

 

So to upgrade I can just run the -u command?

Link to comment

Joe, can I suggest one improvement to the MySQL package?

 

There are some options that can be invoked in MySQL initialization that are able to increase the database performance, such as key buffer size, etc. IMHO, the users should be able to parse them to MySQL. So I propose:

 

a) the addition of one variable:

 

PACKAGE_VARIABLE Custom parameters||vDBCUSTOM=||Custom options parsed to MySQL. See more info <a href="http://dev.mysql.com/doc/refman/5.0/en/mysqld-safe.html">here</a>.

 

b) replace the line #40 to:

 

PACKAGE_INSTALLATION echo "/usr/bin/mysqld_safe --datadir=/mnt/${vDISKLABEL-disk1}/mysql/ --user=root --pid-file=/var/run/mysql/mysql.pid ${vDBCUSTOM} &" >>/etc/rc.d/unraid.d/rc.unraid_mysqld

 

:)

Link to comment

Does the

unmenu_install -c

command download new updates, or just checked to see if there are any new updates?

The "-c" option just alerts you of updates.  It does not download or install them. 

 

It does download a "release_list" that contains the file names and expected checksums.  Those files on your server are compared to determine if they have those checksums.  If they do not, or if they are missing on your server, they will be downloaded and installed if you subsequently invoke with the -u option.

 

The release_list looks like this: http://code.google.com/p/unraid-unmenu/source/browse/trunk/release_list

 

Joe L.

 

So to upgrade I can just run the -u command?

type

cd /boot/unmenu

./unmenu_install -u -d /boot/unmenu

or, use the check for updates/install updates buttons on the user-scripts unMENU page.

Link to comment

Joe, can I suggest one improvement to the MySQL package?

 

There are some options that can be invoked in MySQL initialization that are able to increase the database performance, such as key buffer size, etc. IMHO, the users should be able to parse them to MySQL. So I propose:

 

a) the addition of one variable:

 

PACKAGE_VARIABLE Custom parameters||vDBCUSTOM=||Custom options parsed to MySQL. See more info <a href="http://dev.mysql.com/doc/refman/5.0/en/mysqld-safe.html">here</a>.

 

b) replace the line #40 to:

 

PACKAGE_INSTALLATION echo "/usr/bin/mysqld_safe --datadir=/mnt/${vDISKLABEL-disk1}/mysql/ --user=root --pid-file=/var/run/mysql/mysql.pid ${vDBCUSTOM} &" >>/etc/rc.d/unraid.d/rc.unraid_mysqld

 

:)

Looks good to me.

 

I'll make the change to the "official release" version.

 

Thanks for contributing....  (and glad to see you could figure out how it all works in the unMENU package manager)

 

Joe L.

Link to comment

I think this is where I should post this.  I am trying to use the Dupe Files, but it doesn't seem to do anything.  I know there are Dupe Files because it shows them in the Syslog on the main unmenu page.  Another problem too when i actually click the SysLog link all I get is a e 0 at the top.  When I click the dupe files button it takes about 2 seconds and then shows Duplicate Files on Disk Shares and File with nothing else.  Any help?

 

EDIT: Nevermind about syslog, just needed to restart unmenu.  Still same problem with dupe files though...

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.