BobPhoenix

It is a rather minor change to the preclear script that I have done for a while now. I just add the ".txt" like below. Before: report_out+="$errs \n" report_out+="============================================================================\n" echo -e "$report_out" >/tmp/preclear_report_$d if [ "$save_report" = "y" ] then mkdir -p /boot/preclear_reports dt=`date "+%Y-%m-%d"` if [ "$save_report_by_dev" = "yes" ] then cp /tmp/preclear_report_$d /boot/preclear_reports/preclear_rpt_${d}_${dt} cp /tmp/smart_start_$d /boot/preclear_reports/preclear_start_${d}_${dt} cp /tmp/smart_finish_$d /boot/preclear_reports/preclear_finish_${d}_${dt} else # name the reports by their serial number cp /tmp/preclear_report_$d "/boot/preclear_reports/preclear_rpt_${serial}_${dt}" cp /tmp/smart_start_$d "/boot/preclear_reports/preclear_start_${serial}_${dt}" cp /tmp/smart_finish_$d "/boot/preclear_reports/preclear_finish_${serial}_${dt}" fi fi To: report_out+="$errs \n" report_out+="============================================================================\n" echo -e "$report_out" >/tmp/preclear_report_$d if [ "$save_report" = "y" ] then mkdir -p /boot/preclear_reports dt=`date "+%Y-%m-%d"` if [ "$save_report_by_dev" = "yes" ] then cp /tmp/preclear_report_$d /boot/preclear_reports/preclear_rpt_${d}_${dt}.txt cp /tmp/smart_start_$d /boot/preclear_reports/preclear_start_${d}_${dt}.txt cp /tmp/smart_finish_$d /boot/preclear_reports/preclear_finish_${d}_${dt}.txt else # name the reports by their serial number cp /tmp/preclear_report_$d "/boot/preclear_reports/preclear_rpt_${serial}_${dt}.txt" cp /tmp/smart_start_$d "/boot/preclear_reports/preclear_start_${serial}_${dt}.txt" cp /tmp/smart_finish_$d "/boot/preclear_reports/preclear_finish_${serial}_${dt}.txt" fi fi

You will have to use the UEFI boot method then. Sounds like your MB like the SuperMicro X9SCM is not compatible with firmware flashing via dos boot USB stick. Before I accidentally bricked it I used a SuperMicro C2SBA+II to flash mine via the USB boot method. I have seen others post the UEFI boot method works on a X9SCM MB but I've never used it so cannot help.

Oh that's interesting. I guess it's something else with my install then. Is there anything else required for this to work other than the Clean Powerdown package (installed through unMenu)? Or is there a separate shutdown plugin I'm missing. Actually I think it was the Powerdown plugin (.plg) that is needed not the one from unMenu - but I could be wrong.

I downloaded it and the comments in the PLG say that too (RC3). So now if I upgrade from 14b I will use the new PLG or upgrade them in the GUI if that is an option. Had a scare already today when that ESXi server wouldn't boot after a shut down. Did get that sorted but I have recordings scheduled on the Windows VM so will not do that tonight. So far only missed the local news but not going to miss anything else. Maybe tomorrow night. I just installed the plugin and I'm running rc5. The plugin doesn't appear to work with this version. I get this message when I try to restart or shutdown my unRAID guest VM. Ill test it out myself tomorrow night but not going to do that tonight. One thing I've done for 14b and before is get the .tgz file link from the PLG and put that in the extras folder. Not sure that helped any but was how I was used to doing it for V5 unraid (extras folder).

I downloaded it and the comments in the PLG say that too (RC3). So now if I upgrade from 14b I will use the new PLG or upgrade them in the GUI if that is an option. Had a scare already today when that ESXi server wouldn't boot after a shut down. Did get that sorted but I have recordings scheduled on the Windows VM so will not do that tonight. So far only missed the local news but not going to miss anything else. Maybe tomorrow night.

Did he start a new thread for V6 from this one? http://lime-technology.com/forum/index.php?topic=38279 It still says b15 not RC5 in the first post but reading further down the list it looks like the first post wasn't updated. In any case I'm back to 14b now anyway.

No it is not normal. CD to the unmenu directory is almost instaneous. WebUI is fast as well. Did find my version of unRAID is V6b14b but doubt that would make a difference. But am upgrading to V6rc5 now. I just updated and if anything it is faster with V6rc5 then it was with V6b14b. Here is how I updated: Update unRAID OS in the GUI and rebooted like they said in the instructions When booted it looked like it hadn't upgraded correctly the version said V6b14b. So I shut down the unRAID VM Connect the VMDK to a Windows VM and start the VM. Reformat the VMDK to have an UNRAID label. extract the V6rc5 files run make_makebootable disconnect from Windows VM after shutting down reboot windows VM reboot unRAID VM and now looks upgraded. realize I didn't rename the VMDK volume from UNRAID so now the following are in progess shutdown both VM connect to Windows VM again start Windows VM rename VMDK to BOOT shutdown Windows VM reboot Windows VM reboot unRAID VM - feel safe now Thanks for checking back in. I think I'm good to go. Formatted the USB drive again and all looks well as of now. Going to get screen installed so I can start pre-clearing my drives. Also, good to know the process for upgrading is very simple now with the webgui and that all I have to do is edit the vmdk after upgrading. Real easy. Was editing post while you posted so am re-posting it here. I may switch back to 14b since the VMTools says NOT loaded which maybe causing your problems. It definitely CAN cause slow downs. Needs to get Zeron to upgrade them to use kernel 4.0.4 now but doubt he will until V6 final. .

No it is not normal. CD to the unmenu directory is almost instaneous. WebUI is fast as well. Did find my version of unRAID is V6b14b but doubt that would make a difference. But am upgrading to V6rc5 now. I just updated and if anything it is faster with V6rc5 then it was with V6b14b. Here is how I updated: [*]Update unRAID OS in the GUI and rebooted like they said in the instructions [*]When booted it looked like it hadn't upgraded correctly the version said V6b14b. [*]So I shut down the unRAID VM [*]Connect the VMDK to a Windows VM and start the VM. [*]Reformat the VMDK to have an UNRAID label. [*]extract the V6rc5 files [*]run make_makebootable [*]disconnect from Windows VM after shutting down [*]reboot windows VM [*]reboot unRAID VM and now looks upgraded. [*]realize I didn't rename the VMDK volume from UNRAID so now the following are in progess [*]shutdown both VM [*]connect to Windows VM again [*]start Windows VM [*]rename VMDK to BOOT [*]shutdown Windows VM [*]reboot Windows VM [*]reboot unRAID VM - feel safe now I may switch back to 14b since the VMTools says NOT loaded which maybe causing your problems. It definitely CAN cause slow downs. Needs to get Zeron to upgrade them to use kernel 4.0.4 now but doubt he will until V6 final.

No it is not normal. CD to the unmenu directory is almost instaneous. WebUI is fast as well. Did find my version of unRAID is V6b14b but doubt that would make a difference. But am upgrading to V6rc5 now.

I had this (or something similar) happen to me on my ESXi boot flash. It worked but was unable to save VM configurations. Rebooted and the flash drive was gone and my unRAID Flash drive booted. Spent about 2 hours setting up ESXi again on a new flash drive.

You did rename your VMDK to something other than UNRAID for the volume name correct? Also you are passing through the UNRAID labeled unRAID USB flash drive to the VM? That message is saying it can't find your flash drive. I have ESXi 5.0 but I don't believe 5.5 would be any different when passing through the USB flash drive. But if you are unable to get unRAID to find just the flash drive passed through (like I have done with 5.0) then you may need to pass through the whole controller. I will get the settings from my ESXi 5.0 server that has unRAID V6 VM tonight. Edit: One other thought is I used IDE for the VMDK based on your screen you might be using SCSI? I would switch to an IDE VMDK.

Ok sweet, that seems simple enough. Any gotchas for me in terms of transferring my license key over from my current USB (version 6 beta 15) up to the newest version? I've got all brand new disks so I'm basically just doing a fresh install/setup of unRAID at this point. I believe the key file is required in the CONFIG directory now and is not recognized at the ROOT level but I think that was also true of all Version 6 betas so you should already be doing that. Assuming my memory is correct (am at work currently so cannot confirm). I just copy the key file from my backup of the USB flash drive to the config directory on the reformatted flash drive. The latest unRAID version I have is V6b15. I have V6b15 on one ESXi server and 5.0rc16 on the other two. I've downloaded V6rc4 but I'm not sure I will get time to upgrade to it before V6 final comes out.

I've never used one of the pre-built VMDKs. I always just connect the existing VMDK to a Windows VM and install unRAID like I would on the flash drive. [*]I format the drive [*]Unzip unraid on it [*]Run MakeBootable.bat on it with the VMDK named UNRAID. [*]When that is all done I rename the VMDK to BOOT and disconnect if from the Windows VM [*]Reconnect it to my unRaid VM and boot the VM with the new version. I do essentially the same thing to the flash drive but I back it up first.

That's how I've done all of my upgrades from 5 to 6.

I believe thats any new packages. Pre-existing ones in the packages folder will still attempt to run From original unMenu 1.5 thread: So only those scripts with .auto_install will automatically installed. If you delete all files with .auto_install before upgrading then unMenu would only show and execute those packages that are 64 bit compatible.

With the DoubleTwin I bought the drives would mount closer together and allowed the top back on. I would look at your mounting bracket and see if there is a position that puts the drives closer together. You don't need much especially if you add small fans to push air past them from the front.

I am just doing a new config on the array and reassigning the drives back to there original location. So if I copy from disk1 to disk16 then I do a new config and disk1 and disk16 get swapped.

Thank you for the info. Do you know much about the RES2SV240? Bill You may need to flash it to current firmware. I didn't do it for a long time to mine but I was having a few problems and proceed to flash it to current. Once I did that my problems went away. NOTE that was at least a year ago now so my RES2SV240s might have out of date firmware now - haven't checked for updates since then and I no longer remember what said problems were any more. I was able to update the firmware of the RES2SV240s from within unRAID. Was quite easy as I remember it I just followed the linux directions.

I like this idea.

It would be nice if you could keep the post read times down like bjp999 did for his version of preclear. The post read is approximately the same as the pre-read and the write.

Also if you have IPMI you can get to the console remotely without having to connect a monitor and keyboard.

You should be able to see it with IPMI. Just bring up the IPMI display before you start the PC with IPMI then you can see the bios as well as the unRAID boot screen.

The plugin is really easy to setup but to setup VMs you will need to go the virtualbox.org here: https://www.virtualbox.org/wiki/Documentation. For help with windows vms specifically you can go to the VirtualBox forums here: https://forums.virtualbox.org/viewforum.php?f=2&sid=9b9805868e234241739e0b4d791c041d. I've never used phpvirtualbox but a place to start might be the wiki for it here: http://sourceforge.net/p/phpvirtualbox/wiki/Home/

Think you left out the NOT.

Better answer then my though.