Bingo.

 

Do you have an Unraid flash drive attached to the VM? You'd need to have it to run Unraid properly.

 

As a temp band aid, just for testing, run this command:

/usr/local/sbin/emhttp &

and see if you have progress.

 

6 minutes ago, doron said:

Bingo.

 

Do you have an Unraid flash drive attached to the VM? You'd need to have it to run Unraid properly.

 

As a temp band aid, just for testing, run this command:

/usr/local/sbin/emhttp &

and see if you have progress.

 

Excited now, looks like we are getting close to resolution.. I have plugged in a usb drive and edited the vm to add it.

 

Let me run the command you posted and i will report back in a bit (as it completes)

What do u want me to execute, or navigate to the url once the command is complete?

I ran this command a couple of times, as i did not see any visible (miracle).. lol

 

root@Tower:/boot/config/ssh# /usr/local/sbin/emhttp &
[1] 12978
root@Tower:/boot/config/ssh#
[1]+  Exit 255                /usr/local/sbin/emhttp
root@Tower:/boot/config/ssh#
root@Tower:/boot/config/ssh#
root@Tower:/boot/config/ssh#
root@Tower:/boot/config/ssh# /usr/local/sbin/emhttp &
[1] 13054
root@Tower:/boot/config/ssh#
[1]+  Exit 255                /usr/local/sbin/emhttp
root@Tower:/boot/config/ssh#
 

But yea, it did get complete the very flash second.

The command runs the unraid main management tasks, including the web server, in the background. So you should then be able to navigate your browser to the tower.

Pls note the flash drive is blank, Do u want me to install the bootable unraid into it first, and then plug it into the server and then map it to the vm?

2 minutes ago, Socrates said:

I have plugged in a usb drive and edited the vm to add it.

The USB drive should be built with the same unraid version you have in the VMDK.

Ah i see.. is there a repository of the unraid versions where i can download the old version from?

I cant seem to find v6.2.3 anywhere.. thats the vmdk i have (the one thats posted in the last line in the first page).

I dont mind using any version of vmdk if there is an installer of it. I will upgrade it later once i can get this started.

2 minutes ago, Socrates said:

I cant seem to find v6.2.3 anywhere.. thats the vmdk i have (the one thats posted in the last line in the first page).

Can you find files by the names of bzroot, bzimage, bzmodules and bzfirmware in your vmdk? They usually live under the mounted /boot but seems like your vmdk is different.

12 minutes ago, Socrates said:

Ah i see.. is there a repository of the unraid versions where i can download the old version from?

I need to go, so once you locate the bz* files, you can do this

1. Build the USB with the bootable Unraid, latest version, make_bootable, as the doc instructs.
2. Make it available to the VM.
3. copy to it, under its root directory, the bz* files (overwriting similarly named files on the flash drive)
4. Reboot, while the USB is available to the VM.

 

By the way, once you ran the "emhttpd" command from a few messages ago (only once!...), you should have been able to connect to your unraid server from a web browser. Could you?

Let me work on this, and i will post back the results mate. Are you planning to jump back in, in few hours?

Cant seem to find 6.2.3 anywhere. i tried to download from archives but get access denied errors.

https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.2.3-x86_64.zip

Ok, so i've tried to do this again the other way around. I installed the latest build using plop.

And have been able to boot the unraid. the ip address assigned this time is not in the 192 series.. rather it is 169.254.141.1

 

I am logged into root@tower.. using the esxi client, however the ip address is not working if i use putty.

tower/ also does not work.. when i run emhttp i get an error..

 

 

Now when i point the ipaddress or the tower/ url i get the msg "tower’s server IP address could not be found." in chrome browser.

5 minutes ago, Socrates said:

169.254.141.1

That address is in the range that is self-assigned when it can't get DHCP.

Just now, trurl said:

That address is in the range that is self-assigned when it can't get DHCP.

I just realized the network adaptor was vmxnet 3 (it auto assigned), changed it to E1000e now, and booting up now. Will keep you posted in a bit.

8 minutes ago, trurl said:

That address is in the range that is self-assigned when it can't get DHCP.

By the way, is there a way i can download the older version of unraid.. perferably v6.2.3 ?

10 minutes ago, Socrates said:

By the way, is there a way i can download the older version of unraid.. perferably v6.2.3 ?

Not that I know.

 

I'm not at all familiar with what you're trying to do, but is there some reason the latest stable won't work for your purposes?

 

Or, I sort of got the impression that doron was explaining how you can replace files from the latest with files from the vmdk. People often change version simply by replacing the bz* files on flash.

19 minutes ago, trurl said:

Not that I know.

 

I'm not at all familiar with what you're trying to do, but is there some reason the latest stable won't work for your purposes?

 

Or, I sort of got the impression that doron was explaining how you can replace files from the latest with files from the vmdk. People often change version simply by replacing the bz* files on flash.

So i got the idea to replace the bz* files from the new binaries and replace it with the bz* files within the vmdk. In order for me to do that, i need to extract the vmdk using 7zip.. then replace the bz* files from the current build into the extracted folder and then recompile it using 7zip.. is that right?

I see this warning when i extract the vmdk.. 

 

 

Is it ok to ignore these warnings? Or is there a better way to do this without tampering with the integrity of the vmdk files.?

It sounds as if the unraid USB stick has not been passed through correctly to the VM!   If it is then you will see the contents listed under /boot.   If it is not being passed through and recognised by unRAID then that would explain your symptoms as the USB stick is required to correctly complete the later stages of the boot process and this would include launching the web GUI.

So finally I am able to connect via ip address, i can see the ui page.. but i when i try http://tower it does not work.. instead it says "refused to connect"

So finally I am able to connect via ip address, i can see the ui page.. but i when i try http://tower it does not work.. instead it says "refused to connect"

Can you describe what you've done to get to this point, and how you see the ui page (if the browser still shows "refused")?

6 hours ago, Socrates said:

I installed the latest build using plop

i recommend you to stay with that plopKExec(https://www.plop.at/en/plopkexec/download.html) to avoid confusion with your VMDK. it boots the same fast as from your flash.

BTW, are you prepared your Flash as per instruction? https://wiki.unraid.net/USB_Flash_Drive_Preparation

6 hours ago, Socrates said:

Ok, so i've tried to do this again the other way around. I installed the latest build using plop.

 And have been able to boot the unraid. the ip address assigned this time is not in the 192 series.. rather it is 169.254.141.1

As we are a bit out of sync: This (quoted) is good. Unraid needs some more driver modules that it wants to read from a USB drive.

What is left to do now is to copy the bz* files from the boot drive you created (where you installed the latest version) into the USB drive you prepared earlier (overwrite), and then attach the USB to the VM and reboot. At that point you should see the network, i.e. get a proper IP address and be able to connect to your server via HTTP.

34 minutes ago, uldise said:

i recommend you to stay with that plopKExec(https://www.plop.at/en/plopkexec/download.html) to avoid confusion with your VMDK. it boots the same fast as from your flash.

That's good advice too.