unMENU 1.5 ... now available for download.

[Thornwood]

That last one is my fault.  I've uploaded the newer version of the syslog_match.conf file, but not the checksum in the release list.  (The release_list has the checksum of the prior syslog_match.conf file.)

 

You can put the newer syslog_match.conf file into place by typing:

cp /tmp/unmenu_tmp/syslog_match.conf  /boot/unmenu/

 

I'll be updating the release list today and get things back into sync.   You just caught me in the middle.

 

Joe L.

Ops sorry for that.

 

 

thank you for your help.

Did I do somthing wrong with my go script?

 

Thank you again.

[Joe L.]

That last one is my fault.  I've uploaded the newer version of the syslog_match.conf file, but not the checksum in the release list.  (The release_list has the checksum of the prior syslog_match.conf file.)

 

You can put the newer syslog_match.conf file into place by typing:

cp /tmp/unmenu_tmp/syslog_match.conf  /boot/unmenu/

 

I'll be updating the release list today and get things back into sync.   You just caught me in the middle.

 

Joe L.

Ops sorry for that.

 

 

thank you for your help.

Did I do somthing wrong with my go script?

 

Thank you again.

No, you did nothing wrong at all.

 

There were a number of files where I was in the process of testing and uploading newer versions.  The new versions have different checksums than the old versions. 

 

I just now finished uploading the new files.  I also just now uploaded a new "release_list" file with the new updated checksums.

 

If you use the Check for Updates now it should show a number of new files available.  This time they will probably install just fine (unless I made a mistake)

 

The unmenu_install script uses the checksums to make sure the downloaded files match those expected.  You can see the "release_list" it uses here if you are curious:

http://code.google.com/p/unraid-unmenu/source/browse/trunk/release_list?r=194

 

Joe L.

[Joe L.]

Did I do somthing wrong with my go script?

 

Thank you again.

If you have a copy of unmenu_install at the root of your flash drive ( /boot )you can remove it.  The copy is needed only in the /boot/unmenu directory.

 

/boot/unmenu_install    <--- once the copy is in the unmenu directory, this is no longer needed.

/boot/unmenu/unmenu_install  <--- this should exist.

 

You can remove the extra file, if it exists, by typing:

rm /boot/unmenu_install

[abeta]

Does today's version of myMain fix the password issue?

[Joe L.]

Does today's version of myMain fix the password issue?

Yes.

 

You'll need to install, via the package manager in unMENU, the new image_server.sh package I created and set it to re-install on reboot. 

It is set to use port 8088.  This is configurable if you need to change it if something else is already using that port, but for 99.99% of unRAID users, it will be unused and available for use by the image server.

 

Then in the myMain config you need to set the image server field to

tower:8088

(Click on the myMain Logo to open the configuration screen.)

 

You can use an IP address as an alternative to the server name (for those using a MAC). In that case set the image server to

xxx.xxx.xxx.xxx:8088

where the xxx.xxx.xxx.xxx = your specific IP address of your unRAID server.

 

Joe L.

[SSD]

Does today's version of myMain fix the password issue?

 

Make sure you check in the myMain thread.

[BlackCat]

Background:

I decided to do a fresh install of UnRaid v4.5.6 on my flash drive. I inserted the drive into my windows XP machine and formatted it per instructions, http://lime-technology.com/wiki/index.php?title=USB_Flash_Drive_Preparation#Instructions, same as I did the first time. Followed the instructions on the google page, http://code.google.com/p/unraid-unmenu/, to install unMenu 1.3.7.1. Once I started the server and installed unMenu. I followed the instructions here, http://www.lime-technology.com/wiki/index.php?title=UnRAID_Add_Ons#UnMENU, to modify the go script to always start unMenu. I then rebooted the server using the regular Web GUI.

Problem:

Once the server booted, I opened unMenu and it was showing duplicates of my two data drives, sdb, sdb1, sdc, and sdc1 (not yet added to the array). I have attached a picture and my syslog. I did some searching around and I didn't find anything that touched on this so I thought I would ask.

Syslog_Fresh_Install-12-16-2010_unMenu_Duplicate_disks.txt

[Joe L.]

Background:

I decided to do a fresh install of UnRaid v4.5.6 on my flash drive. I inserted the drive into my windows XP machine and formatted it per instructions, http://lime-technology.com/wiki/index.php?title=USB_Flash_Drive_Preparation#Instructions, same as I did the first time. Followed the instructions on the google page, http://code.google.com/p/unraid-unmenu/, to install unMenu 1.3.7.1. Once I started the server and installed unMenu. I followed the instructions here, http://www.lime-technology.com/wiki/index.php?title=UnRAID_Add_Ons#UnMENU, to modify the go script to always start unMenu. I then rebooted the server using the regular Web GUI.

Problem:

Once the server booted, I opened unMenu and it was showing duplicates of my two data drives, sdb, sdb1, sdc, and sdc1 (not yet added to the array). I have attached a picture and my syslog. I did some searching around and I didn't find anything that touched on this so I thought I would ask.

It is showing both "devices" for each disk.  The full disk, as /dev/sdb, and the first partition on it as /dev/sdb1.    This is perfectly normal and correct.  (same with sdc and sdc1.)

 

Joe L.

[BlackCat]

Background:

I decided to do a fresh install of UnRaid v4.5.6 on my flash drive. I inserted the drive into my windows XP machine and formatted it per instructions, http://lime-technology.com/wiki/index.php?title=USB_Flash_Drive_Preparation#Instructions, same as I did the first time. Followed the instructions on the google page, http://code.google.com/p/unraid-unmenu/, to install unMenu 1.3.7.1. Once I started the server and installed unMenu. I followed the instructions here, http://www.lime-technology.com/wiki/index.php?title=UnRAID_Add_Ons#UnMENU, to modify the go script to always start unMenu. I then rebooted the server using the regular Web GUI.

Problem:

Once the server booted, I opened unMenu and it was showing duplicates of my two data drives, sdb, sdb1, sdc, and sdc1 (not yet added to the array). I have attached a picture and my syslog. I did some searching around and I didn't find anything that touched on this so I thought I would ask.

It is showing both "devices" for each disk.  The full disk, as /dev/sdb, and the first partition on it as /dev/sdb1.    This is perfectly normal and correct.  (same with sdc and sdc1.)

 

Joe L.

Thanks Joe, that is interesting because I could swear when I had installed unMenu the first time (before this format) they weren't there.

[Joe L.]

Background:

I decided to do a fresh install of UnRaid v4.5.6 on my flash drive. I inserted the drive into my windows XP machine and formatted it per instructions, http://lime-technology.com/wiki/index.php?title=USB_Flash_Drive_Preparation#Instructions, same as I did the first time. Followed the instructions on the google page, http://code.google.com/p/unraid-unmenu/, to install unMenu 1.3.7.1. Once I started the server and installed unMenu. I followed the instructions here, http://www.lime-technology.com/wiki/index.php?title=UnRAID_Add_Ons#UnMENU, to modify the go script to always start unMenu. I then rebooted the server using the regular Web GUI.

Problem:

Once the server booted, I opened unMenu and it was showing duplicates of my two data drives, sdb, sdb1, sdc, and sdc1 (not yet added to the array). I have attached a picture and my syslog. I did some searching around and I didn't find anything that touched on this so I thought I would ask.

It is showing both "devices" for each disk.  The full disk, as /dev/sdb, and the first partition on it as /dev/sdb1.    This is perfectly normal and correct.  (same with sdc and sdc1.)

 

Joe L.

Thanks Joe, that is interesting because I could swear when I had installed unMenu the first time (before this format) they weren't there.

You probably had the drives assigned to the array before you installed unMENU.   It only shows those details on "Drive Partitions" for drives not assigned in the protected array.

[BlackCat]

Background:

I decided to do a fresh install of UnRaid v4.5.6 on my flash drive. I inserted the drive into my windows XP machine and formatted it per instructions, http://lime-technology.com/wiki/index.php?title=USB_Flash_Drive_Preparation#Instructions, same as I did the first time. Followed the instructions on the google page, http://code.google.com/p/unraid-unmenu/, to install unMenu 1.3.7.1. Once I started the server and installed unMenu. I followed the instructions here, http://www.lime-technology.com/wiki/index.php?title=UnRAID_Add_Ons#UnMENU, to modify the go script to always start unMenu. I then rebooted the server using the regular Web GUI.

Problem:

Once the server booted, I opened unMenu and it was showing duplicates of my two data drives, sdb, sdb1, sdc, and sdc1 (not yet added to the array). I have attached a picture and my syslog. I did some searching around and I didn't find anything that touched on this so I thought I would ask.

It is showing both "devices" for each disk.  The full disk, as /dev/sdb, and the first partition on it as /dev/sdb1.    This is perfectly normal and correct.  (same with sdc and sdc1.)

 

Joe L.

Thanks Joe, that is interesting because I could swear when I had installed unMenu the first time (before this format) they weren't there.

You probably had the drives assigned to the array before you installed unMENU.   It only shows those details for drives not assigned in the array.

Ah, that would explain it. I did have my drives assigned first.

[pastrychef]

I recently checked for updates to unMENU and saw that there were a long list of images and clicked Install unMENU updates.  When it finished, I got the following:

 

Local myMain_local.conf file exists, /tmp/unmenu_tmp/myMain_local.conf not installed.  You will need to delete the local file first before the new will be installed.

 

So, I telnet to unRAID and rm myMAIN_local.conf and tried to install again.  But I ended up getting the same message.  Even after a reboot, I have the same problem.  How can I resolve this?  Thank you.

[burtjr]

I recently checked for updates to unMENU and saw that there were a long list of images and clicked Install unMENU updates.  When it finished, I got the following:

 

Local myMain_local.conf file exists, /tmp/unmenu_tmp/myMain_local.conf not installed.  You will need to delete the local file first before the new will be installed.

 

So, I telnet to unRAID and rm myMAIN_local.conf and tried to install again.  But I ended up getting the same message.  Even after a reboot, I have the same problem.  How can I resolve this?  Thank you.

You need to either change the name or delete the myMain_local.conf on the flash drive located in the unmenu folder. Then run the update again.

[pastrychef]

You need to either change the name or delete the myMain_local.conf on the flash drive located in the unmenu folder. Then run the update again.

 

Wow!  That was fast!!  Thank you very much for the help.  That worked perfectly.

[dvd.collector]

Does today's version of myMain fix the password issue?

Yes.

 

You'll need to install, via the package manager in unMENU, the new image_server.sh package I created and set it to re-install on reboot.  

It is set to use port 8088.  This is configurable if you need to change it if something else is already using that port, but for 99.99% of unRAID users, it will be unused and available for use by the image server.

 

Then in the myMain config you need to set the image server field to

tower:8088

(Click on the myMain Logo to open the configuration screen.)

 

You can use an IP address as an alternative to the server name (for those using a MAC). In that case set the image server to

xxx.xxx.xxx.xxx:8088

where the xxx.xxx.xxx.xxx = your specific IP address of your unRAID server.

 

Joe L.

 

I've installed the new package (and rebooted), and also updated myMain to try both "tower:8088" and IP:8088 and I'm still not seeing any images in Mymain.

 

Is there anyway I can confirm that the image server is up and running?  (Syslog snippet below, seems to suggest it is.. but also it is crashing?)

 

Dec 19 09:04:17 Tower bash[2433]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:05:02 Tower bash[2480]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:05:27 Tower bash[2535]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:05:37 Tower unmenu[1589]: /boot/unmenu/uu: line 55:  1594 User defined signal 1   awk -W re-interval -f ./unmenu.awk 2>$stuff$1 </dev/null
Dec 19 09:05:37 Tower unmenu-status: Exiting unmenu web-server, exit status code = 138
Dec 19 09:05:37 Tower unmenu-status: Starting unmenu web-server
Dec 19 09:07:23 Tower bash[2603]: connect from 192.168.11.4 (192.168.11.4) (Routine)
Dec 19 09:07:24 Tower bash[2613]: connect from 192.168.11.4 (192.168.11.4) (Routine)
Dec 19 09:07:25 Tower bash[2623]: connect from 192.168.11.4 (192.168.11.4) (Routine)
Dec 19 09:07:26 Tower bash[2633]: connect from 192.168.11.4 (192.168.11.4) (Routine)
Dec 19 09:07:27 Tower bash[2643]: connect from 192.168.11.4 (192.168.11.4) (Routine)
Dec 19 09:07:28 Tower bash[2653]: connect from 192.168.11.4 (192.168.11.4) (Routine)
Dec 19 09:07:29 Tower bash[2663]: connect from 192.168.11.4 (192.168.11.4) (Routine)
Dec 19 09:07:30 Tower bash[2673]: connect from 192.168.11.4 (192.168.11.4) (Routine)
Dec 19 09:07:31 Tower bash[2683]: connect from 192.168.11.4 (192.168.11.4) (Routine)
Dec 19 09:07:32 Tower bash[2693]: connect from 192.168.11.4 (192.168.11.4) (Routine)
Dec 19 09:07:39 Tower bash[2783]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:07:39 Tower bash[2784]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:07:39 Tower bash[2785]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:07:39 Tower bash[2790]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:07:39 Tower bash[2794]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:07:39 Tower bash[2807]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:07:39 Tower bash[2831]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:07:39 Tower bash[2841]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:07:49 Tower bash[2871]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:07:54 Tower nss_wins[1298]: Listening on interface #2 eth0, 192.168.11.4#123 Enabled (Network)
Dec 19 09:09:39 Tower bash[3199]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:09:39 Tower bash[3200]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:09:39 Tower bash[3198]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:09:39 Tower bash[3201]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:09:39 Tower bash[3202]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:09:39 Tower bash[3203]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:09:39 Tower bash[3264]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:09:39 Tower bash[3265]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:09:48 Tower bash[3398]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:09:57 Tower bash[3524]: connect from 192.168.11.97 (192.168.11.97) (Routine)
Dec 19 09:10:06 Tower unmenu[1589]: /boot/unmenu/uu: line 55:  2552 User defined signal 1   awk -W re-interval -f ./unmenu.awk 2>$stuff$1 </dev/null
Dec 19 09:10:06 Tower unmenu-status: Exiting unmenu web-server, exit status code = 138
Dec 19 09:10:06 Tower unmenu-status: Starting unmenu web-server

[Joe L.]

It does not look like the unMENU awk server is crashing.

 

Did you set the image_server package to re-install on reboot?

If you did, you should see the .auto_install file when you type this command:

ls -l /boot/packages/image_server.sh.auto_install

 

If yes, you should see it if you type the following command.

ls -l /usr/local/sbin/image_server.sh

 

If the .auto_install is in place, and the image_Server.sh exists, then the only thing left is to see that the line unMENU appended to the bottom of your /boot/config/go script that runs the .auto_install files is in place properly.

 

To do that type the following command and post the output.

tail /boot/config/go

 

Joe L.

[dvd.collector]

It does not look like the unMENU awk server is crashing.

 

Did you set the image_server package to re-install on reboot?

If you did, you should see the .auto_install file when you type this command:

ls -l /boot/packages/image_server.sh.auto_install

 

If yes, you should see it if you type the following command.

ls -l /usr/local/sbin/image_server.sh

 

If the .auto_install is in place, and the image_Server.sh exists, then the only thing left is to see that the line unMENU appended to the bottom of your /boot/config/go script that runs the .auto_install files is in place properly.

 

To do that type the following command and post the output.

tail /boot/config/go

 

Joe L.

 

Hi Joe, yes I set it to autoinstall on reboot and i can see from the packages page it says install on reboot enabled too.

 

Heres the output of the queries you asked for:

 

Tower login: root
Password:
Linux 2.6.27.7-unRAID.
root@Tower:~# ls -l /boot/packages/image_server.sh.auto_install
-rwx------ 1 root root 2091 Dec 19 08:56 /boot/packages/image_server.sh.auto_ins                 tall*
root@Tower:~# ls -l /usr/local/sbin/image_server.sh
-rwxr-xr-x 1 root root 1103 Dec 19 09:03 /usr/local/sbin/image_server.sh*
root@Tower:~# tail /boot/config/go
echo nameserver 192.168.11.1 >/etc/resolv.conf
echo 192.168.11.4 tower >>/etc/hosts

echo "powerdown" | at 23:00

cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c


/boot/custom/bin/cache_dirs -w -B
# /boot/custom/bin/cache_user.shroot@Tower:~#

[SSD]

You need to either change the name or delete the myMain_local.conf on the flash drive located in the unmenu folder. Then run the update again.

 

Wow!  That was fast!!  Thank you very much for the help.  That worked perfectly.

 

The unmenu config files that end with "_local.conf" are not meant to be overwritten with each update.  These files contain user specific settings and preferences.  For example, myMain_local.conf contains information about your specific drives/serial numbers, your specific view configurations, and other configuration items as well.

 

If you delete the file, the update will install a default file.  But any settings you've customized will be lost.  In general, DO NOT remove these files!

[Joe L.]

It does not look like the unMENU awk server is crashing.

 

Did you set the image_server package to re-install on reboot?

If you did, you should see the .auto_install file when you type this command:

ls -l /boot/packages/image_server.sh.auto_install

 

If yes, you should see it if you type the following command.

ls -l /usr/local/sbin/image_server.sh

 

If the .auto_install is in place, and the image_Server.sh exists, then the only thing left is to see that the line unMENU appended to the bottom of your /boot/config/go script that runs the .auto_install files is in place properly.

 

To do that type the following command and post the output.

tail /boot/config/go

 

Joe L.

 

Hi Joe, yes I set it to autoinstall on reboot and i can see from the packages page it says install on reboot enabled too.

 

Heres the output of the queries you asked for:

 

Tower login: root
Password:
Linux 2.6.27.7-unRAID.
root@Tower:~# ls -l /boot/packages/image_server.sh.auto_install
-rwx------ 1 root root 2091 Dec 19 08:56 /boot/packages/image_server.sh.auto_ins                 tall*
root@Tower:~# ls -l /usr/local/sbin/image_server.sh
-rwxr-xr-x 1 root root 1103 Dec 19 09:03 /usr/local/sbin/image_server.sh*
root@Tower:~# tail /boot/config/go
echo nameserver 192.168.11.1 >/etc/resolv.conf
echo 192.168.11.4 tower >>/etc/hosts

echo "powerdown" | at 23:00

cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c


/boot/custom/bin/cache_dirs -w -B
# /boot/custom/bin/cache_user.shroot@Tower:~#

Everything looks normal.

 

Only things left would be to check if you might have a fire-wall in place blocking port 8088 or

to possibly clear your browser's cache.

[SSD]

I've installed the new package (and rebooted), and also updated myMain to try both "tower:8088" and IP:8088 and I'm still not seeing any images in Mymain.

 

Try entering the following URL:

 

http://tower:8088/log/images/stock/myMainLogo.jpg

 

Joe -

 

This is probably unrelated - but appears that there is a directory called "images/slock" not "images/stock" that is being created by the install process.

 

 

[Joe L.]

This is probably unrelated - but appears that there is a directory called "images/slock" not "images/stock" that is being created by the install process.

I'll look into that later this evening.  I probably misstyped something at one point in google.code

 

[sacretagent]

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

[dvd.collector]

I've installed the new package (and rebooted), and also updated myMain to try both "tower:8088" and IP:8088 and I'm still not seeing any images in Mymain.

 

Try entering the following URL:

 

http://tower:8088/log/images/stock/myMainLogo.jpg

 

Joe -

 

This is probably unrelated - but appears that there is a directory called "images/slock" not "images/stock" that is being created by the install process.

 

 

 

Here is what I see when accessing that url:

 

404 Not Found

/var/log/images/stock/myMainLogo.jpg Not Found

 

I assume that the 404 shows that the web server is up and running? (Rather than seeing a page cannot be displayed message).

 

Have also tried clearing browser cache, and unless my router is playing up, there is no firewall in place.

[Joe L.]

I've installed the new package (and rebooted), and also updated myMain to try both "tower:8088" and IP:8088 and I'm still not seeing any images in Mymain.

 

Try entering the following URL:

 

http://tower:8088/log/images/stock/myMainLogo.jpg

 

Joe -

 

This is probably unrelated - but appears that there is a directory called "images/slock" not "images/stock" that is being created by the install process.

 

 

 

Here is what I see when accessing that url:

 

404 Not Found

/var/log/images/stock/myMainLogo.jpg Not Found

 

I assume that the 404 shows that the web server is up and running? (Rather than seeing a page cannot be displayed message).

Correct. The image server responded with the 404 message.

Have also tried clearing browser cache, and unless my router is playing up, there is no firewall in place.

OK... one or two more things to check.  Let's see if the image files were downloaded at all.

 

Please let me know what you see for the following

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.

 

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

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)

 

If it does not, you need to download the newer version of unmenu_install.  When the new myMain plugin was released I had stated users needed to run the Check-for-updates/Install updates twice.  ( the first time would download everything except the images in the sub-directories.  Sound like your symptoms perhaps.)

 

The first time would download the newer version of unmenu_install that could create and download to the sub-directories for the images.    The SECOND time it was invoked the new version it just downloaded would be used and it would be able to properly download and save the image files, which are apparently missing on your server.

 

You can do invoke it (that second time) using the buttons on the unMENU user-scripts page or on the Linux command line by typing:

cd /boot/unmenu

./unmenu_install -u -d  /boot/unmenu

 

If everything goes as expected, the image directory should now exist. under /boot/unmenu/images

Again type

ls -l /boot/unmenu/images

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.

 

Last, we need to make sure the older version of unmenu_install is not being invoked.  If there is an older copy of it at /boot, we can remove it.

ls -l /boot/unmenu_install

if it exists:

rm /boot/unmenu_install

 

Joe L.

[prostuff1]

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.