mandreto10

ESXI 6.5, DS918+, Jun 1.04, - Cannot create VM - ERROR "SCSI0:3"

Recommended Posts

Does anyone know hot to get past this error? What is ISCI anyway? In previous Guest OS (Mac, Win), I never had to do anything about it.

315760982_error2.thumb.jpg.da3788ecc53de70c227d3fa0e98ab1f0.jpg

error.thumb.jpg.567e0d7c626ce784f157dd53b713de57.jpg

Share this post


Link to post
Share on other sites

This is an ESXi error, nothing to do with XPEnology.

 

You need to use a virtual SATA controller for 1.04b bootloader not SCSI.  Set up SATA Controller 0 with the bootloader as disk 0.  Set up a second SATA Controller 1 with your data drive(s)

Share this post


Link to post
Share on other sites
51 minutes ago, flyride said:

This is an ESXi error, nothing to do with XPEnology.

 

You need to use a virtual SATA controller for 1.04b bootloader not SCSI.  Set up SATA Controller 0 with the bootloader as disk 0.  Set up a second SATA Controller 1 with your data drive(s)

 

Where is SATA controller?

 

VDN 1.jpg

VDN.jpg

 

 

Is this what you mean? If yes, the package is already installed. Where do you set it up for Syno?

 

VDN2.thumb.jpg.54fb382315fd880ed7fd41bbf21cc03c.jpg

Edited by mandreto10

Share this post


Link to post
Share on other sites

image.thumb.png.c428916e4bd3f581c93992cf27f12888.png
 

Patchlevel?  Unsure about why you don't have it.  But it is required for 6.2.x so you will need to solve it.

 

Share this post


Link to post
Share on other sites
4 minutes ago, flyride said:

image.thumb.png.c428916e4bd3f581c93992cf27f12888.png
 

Patchlevel?  Unsure about why you don't have it.  But it is required for 6.2.x so you will need to solve it.

 

 

 

I see SATA driver installed. But NOTE that I have PCIE SSD (M.2) wit NVMe protocol. I do not have anything plugged into SATA drives.

This website specifically says that 918 supports NVMe, and NVME is a PCIE interface not SATA. Not so?

 

VDN2.thumb.jpg.e2871150e84890d22c5537eb36e308a4.jpg

Share this post


Link to post
Share on other sites
1 minute ago, mandreto10 said:

I see SATA driver installed. But NOTE that I have PCIE SSD (M.2) wit NVMe protocol. I do not have anything plugged into SATA drives.

This website specifically says that 918 supports NVMe, and NVME is a PCIE interface not SATA. Not so?

 

DSM 6.2 on DS918 as compiled by Synology supports NVMe drives for cache only.  Not for installation/boot/data, which must be SATA.

 

But I don't think that's the issue here, it seems that maybe you don't fully understand how devices are represented in ESXi.

 

Your NVMe drive seems to be attached to ESXi as a datastore (which is fine).

Then you are trying to configure a virtual SCSI controller (which won't work with DSM 6.2).

I'm not sure if you created a virtual data disk or not but you need something to attach to the controller.

 

You can definitely create a virtual disk on your NVMe datastore and present it to your VM as a SATA-connected drive.

You can also create a physical RDM pointer to your NVMe drive and present it to the VM as a SATA-connected drive.  But you can't use it as an ESXi datastore at the same time (you will need something else for your datastore).

In each of the above cases, you will have NVMe performance but DSM will think it's a SATA drive.

Share this post


Link to post
Share on other sites
44 minutes ago, flyride said:

 

DSM 6.2 on DS918 as compiled by Synology supports NVMe drives for cache only.  Not for installation/boot/data, which must be SATA.

 

I appreciate the answer.

 

Fair enough.

IMO, this should be clearly stated somewhere on this forum, in a place titled "Hardware Requirements"! This is a  limitation, given that NVMe drives are replacing SATA drives....

 

Quote

 

But I don't think that's the issue here, it seems that maybe you don't fully understand how devices are represented in ESXi.

 

Correct! 

 

 

Quote

 

Your NVMe drive seems to be attached to ESXi as a datastore (which is fine).

 

Correct.

 

 

Quote

Then you are trying to configure a virtual SCSI controller (which won't work with DSM 6.2).

 

Quote

I'm not sure if you created a virtual data disk or not but you need something to attach to the controller.

 

I create Virtual Machines first, then defined within that virtual machines a virtual disk.

How is reverse possible?

 

Quote

 

You can definitely create a virtual disk on your NVMe datastore and present it to your VM as a SATA-connected drive.

 

How is that done?

I always created VM first, then created virtual harddrive within a Virtual Machine.

 

Quote

You can also create a physical RDM pointer to your NVMe drive and present it to the VM as a SATA-connected drive.  But you can't use it as an ESXi datastore at the same time (you will need something else for your datastore).

 

I don't understand what RDM is.

 

Quote

 

In each of the above cases, you will have NVMe performance but DSM will think it's a SATA drive.

 

That sounds good, so how is virtual drive created, without first creating VM? There is no SSD drive listed when I try to do that.

 

vd.thumb.jpg.96cd5838073d8c00d1821c4a55026ef0.jpgvd.thumb.jpg.96cd5838073d8c00d1821c4a55026ef0.jpg

Edited by mandreto10

Share this post


Link to post
Share on other sites
1 hour ago, flyride said:

 

DSM 6.2 on DS918 as compiled by Synology supports NVMe drives for cache only.  Not for installation/boot/data, which must be SATA.

 

But I don't think that's the issue here, it seems that maybe you don't fully understand how devices are represented in ESXi.

 

Your NVMe drive seems to be attached to ESXi as a datastore (which is fine).

Then you are trying to configure a virtual SCSI controller (which won't work with DSM 6.2).

I'm not sure if you created a virtual data disk or not but you need something to attach to the controller.

 

You can definitely create a virtual disk on your NVMe datastore and present it to your VM as a SATA-connected drive.

You can also create a physical RDM pointer to your NVMe drive and present it to the VM as a SATA-connected drive.  But you can't use it as an ESXi datastore at the same time (you will need something else for your datastore).

In each of the above cases, you will have NVMe performance but DSM will think it's a SATA drive.

 

Again, I appreciate feedback.

 

IMO, the error is in Xpenology bootloaders, or a maze of its, often outdated, conflicting and/or incomplete user guides.

 

I just tried to install FreeNAS (10 minutes exercise vs almost 20+ hours of going through Xpenology forums). When I try to install FreeNAS, I can clearly see SATA controller as an option!! 

 

freeNAS.thumb.jpg.d518ae56d2e837cda67a0978ab685c0d.jpg

 

I verified that I have SATA controller as an option for EVERY of the following operating systems listed, EXCEPT for Xpenology.

Ubuntu,

Kubuntu

Mac OS

Windows 10

Linux Oracle

FreeNAS

 

How do you explain that?

 

 

 

 

Edited by mandreto10

Share this post


Link to post
Share on other sites

XPEnology is not an operating system.  DSM is the operating system.

The SATA configuration option you are referring to is ESXi, not XPEnology, and not DSM.

 

Regardless of how we define things, perhaps when created your VM, you selected something other than the recommended "Other 3.x or later Linux (x64)" as the tutorial instructs.

 

image.thumb.png.ad72463bcd010505cc642ec07ca9f1d4.png

 

In any case, it does take some time to navigate the versions and information out there, since nobody is getting paid for it.

 

Edited by flyride
better discretion in all things

Share this post


Link to post
Share on other sites

Maybe some baseline perspective would be helpful.

 

Synology sells hardware that runs open-source software on it which they brand as DSM.  They would prefer that nobody uses this software outside of their paid hardware platform, so they put in failsafe checks to disable the software when their hardware is not detected.  XPEnology intends to defeat those failsafe checks and allow DSM to run on other hardware.  But the capabilities of DSM are defined by Synology (NVMe support, for example), and we can extend some of those capabilities by leveraging the hardware options available to us (using ESXi to map NVMe drives into DSM, for example).

 

Most who want to DSM using XPEnology have a base understanding of what DSM is and does, and may understand its limitations, having used it on actual Synology hardware before, so the above statements are neither controversial or offensive.

 

Many who deploy DSM using XPEnology for the first time do so on baremetal (without virtualization) because the behavior of the system and how it relates to the hardware is closest to the experience they have had with actual Synology hardware.

 

ESXi adds more complexity to the installation but increases hardware options and capabilities. It's a bit easier to make functional if already familiar with a baremetal install of DSM under XPEnology, and practical knowledge of ESXi is also very helpful.

  • Like 1

Share this post


Link to post
Share on other sites
12 hours ago, flyride said:

XPEnology is not an operating system.  DSM is the operating system.

The SATA configuration option you are referring to is ESXi, not XPEnology, and not DSM.

 

Regardless of how we define things, perhaps when created your VM, you selected something other than the recommended "Other 3.x or later Linux (x64)" as the tutorial instructs.

 

Can you please provide reference to that tutorial? I have seen at least a dozen tutorials so far on this website. 

 

This one doesn't have files any longer: 

 

Did you mean this one: 

 

or this one: 

 

or maybe this one: 

 or this one:

 

 

 

12 hours ago, flyride said:

 

image.thumb.png.ad72463bcd010505cc642ec07ca9f1d4.png

 

In any case, it does take some time to navigate the versions and information out there, since nobody is getting paid for it.

 

 

Share this post


Link to post
Share on other sites
12 hours ago, flyride said:

Maybe some baseline perspective would be helpful.

 

Synology sells hardware that runs open-source software on it which they brand as DSM.  They would prefer that nobody uses this software outside of their paid hardware platform, so they put in failsafe checks to disable the software when their hardware is not detected.  XPEnology intends to defeat those failsafe checks and allow DSM to run on other hardware.  But the capabilities of DSM are defined by Synology (NVMe support, for example), and we can extend some of those capabilities by leveraging the hardware options available to us (using ESXi to map NVMe drives into DSM, for example).

 

I currently own Synology, with my own porting set up (their list of routers isn't up to date), and my own access from internet (less dependent on Syno account).

 

Quote

 

Most who want to DSM using XPEnology have a base understanding of what DSM is and does, and may understand its limitations, having used it on actual Synology hardware before, so the above statements are neither controversial or offensive.

 

I think I do have basic understanding of DSM after owning it for several years.

I do not have basic understanding of what Xpenology does, because there is not coherent guide and introduction. It also doesn't help that when someone mentions a reference, they either don't provide the link (hyperlink), or the hyperlink is invalid.

 

IMO, the problem is not my lack of understanding Synology, but lack of organization of basic information on this site. The best product is worthless, if user guide is not user-friendly. 

 

Ater 20+ hours it is unclear to me:

 

- Exactly WHAT is Jun's loader? Is it:

  1. IMG file
  2. VMDK file
  3. IMG+ VMDK file
  4. IMG + VMDK + some other patch files?

The answer to that questions should be straight forward and mere seconds. This is important, because some guides show reference to IMG file only, while others to both IMG and VMDK files. It's important for users to know WHAT they are looking for, and when they download it to KNOW whether it is complete (set of files) or not.

 

That should have been stated here: 

 

and it isn't. It says what bootloader DOES, but not what it IS in terms of ACTUAL FILES that user need to download from Xpenology.com!

It should have stated: "Bootloader is ONE/A SET of files" and "here is an example of a Bootlader file name", "and "here is where you find all bootloaders: hyperlink"

 

What is the AUTHORITATIVE SOURCE for Jun's loader?

In other words, where is ONE single page that lists them. Is it this:

 

 

 

 

- Does the user generate VMDK from IMG, or must VDMK be downloaded from this website (and from where)?

  • I've seen some users providing reference to already pre-made VMDK, while others state one must generate their own VMDK using image converter.

 

- Exactly WHAT and WHY needs to be modified in .IMG image file? (Or maybe IMG and VMDK file). What happens if it's NOT modified

  1. MAC (I assume without this Synology cannot be detected on network)
  2. PID, VID?
  3. SN
    1. Where are SN generators?
    2. Here: 
    3. Here: https://xpenogen.github.io/serial_generator/index.html
    4. Here: https://github.com/brianpow/synology-sn-mac-generator/blob/master/Synology NAS Serial Number and MAC address Generator for Mobile Browser.htm
    5. or here: https://idmedia.no/wp-content/uploads/2015/07/Synology-mod-new.xlsm
    6. If it's somehwere on Xpenology forum, where?

 

It should take mere seconds for knowledgable person to create a table, with first column listing changes required, second stating how to do it, third, why it's needed, and foruth what happens if these changes are not made. This needs to be done ONCE ONLY!

 

This is vaguely and incompletely explained here: 

 

 

Personally, I could not care less for Syno services (nor for their support, who damaged the volume on my harddrive during one of their "support" sessions, when attempting to clean up the mess that iDrive created). I don't trust any of my data running through their service, so I set up my own service. With personal VPN, DDNS and correct ports configured, I can access my NAS from anywhere, without Syno "service" (if you insist calling it a "service").

 

 

- Exactly how to set up Jun's Loader in ESXI?

- The way EVERY one of these OSs are installed in ESXI , aside from USB, (Ubuntu, Kubuntu, Mac OS, Windows 11, Linux Oracle) is by:

-  Uploading ISO image (ISO!, not VMDK or IMG)  to data storage

-  Creating VM

-  Adding CD/DVD drive

- pointing CD/DVD drive to ISO file

- Adding Hard drive, where system and files will be installed - it's THAT EASY!

 

It's not only easy, but it's logical and takes seconds to learn, BECAUSE(!) it replicates the process all of us have done at least once in our lives. Majority has installed an OS either from CD/DVD (up until 5 or so years ago) or from USB drive (more recently).

 

If Xpenology does it differently, it's logical to point that out and provide detailed, explicit and explanatory guide on how to do it, with image shots. This can be done ONCE only. I can't imagine this would require more than 30 minutes to do it.  

 

What would you choose: Spend an hour creating a complete, thorough User Guide or spend hours answering newbies questions?

 

Xpenology does not have ISO file, but VMDK and IMG. Xpenology doesn't need CD/DVD drive to load the image, and this is nowhere stated.

It's not clear whether user needs ONE, TWO, or more Hard drives to install Synology on a PC that has one HDD/SDD; let alone when more HDDs are involved. 

It's not clear whether harddrives for Xpenology/Synology need to be thin or thick provisioned. I've seen guides where users SWORE that only one option should be choosen (the opposite, of course).

 

 

Quote

 

Many who deploy DSM using XPEnology for the first time do so on baremetal (without virtualization) because the behavior of the system and how it relates to the hardware is closest to the experience they have had with actual Synology hardware.

 

ESXi adds more complexity to the installation but increases hardware options and capabilities. It's a bit easier to make functional if already familiar with a baremetal install of DSM under XPEnology, and practical knowledge of ESXi is also very helpful.

 

The reason I chose to instal ESXI on bare metal is exclusively because I wanted to run several OSs including pfSense.

Edited by mandreto10

Share this post


Link to post
Share on other sites

This is just one person's opinion and I do not speak for anyone else:

 

I'm not an admin here, I did not write the loaders.  I'm just a tech-savvy user, that likes DSM and how it performs on my own hardware - far better than on Synology hardware.  Over time, I have figured out a lot of things about XPEnology, and am willing to spend some personal time to help others, just like countless other contributors here. 

 

You are on a forum where the stated purpose is to enable people to use a hack.  It's not a product support page.  This collective effort has spanned 10 years of DSM releases, and people are still using some of the old software versions.  So ALL the information here is still relevant to someone, and nobody's being paid to curate the part you think you need, just for you.

 

If you want to use XPEnology, you need to put in the time (and have the tech skills) to understand the ecosystem and the tools involved.  Many people, myself included, have done research and written up documentation or coded tools to try and help with this.  But it won't be delivered on a platter like FreeNAS, which is bankrolled by the commercial side of the product.

 

As you perceive a need for things to be organized differently, may I suggest that you become an expert here and start contributing instead of lecturing to people you don't know, and who don't owe you anything on how a loosely structured forum and its content should be presented.

 

Again, I personally am happy to help when I have something useful to contribute, but I'm having a hard time getting over the attitude and general lack of patience that I perceive from you.  This has caused me to delete several draft posts (intended to be of assistance to you) out of exasperation. In a prior post, I suggested that "maybe XPEnology wasn't for you" and while it's not for me to defend that, I do believe that your approach may prove to be very frustrating, should you persist.

  • Like 3

Share this post


Link to post
Share on other sites

Hey mandreto10...

 

Hi! You sound very frustrieted! Let me help you. There is lot of information on this forum....It can be confusing for new person.

 

Here is a very good guide: https://xpenology.com/forum/topic/13061-tutorial-install-dsm-62-on-esxi-67/ 

This guide will work on ESXI 6.5 and 6.7. Make sure you read through the entire post, as there are few important modifications. Specifically changes to Network Card...This link contains all files you need in one place. It has screen shots. The fourth link seems broken. Don't worry about that file. For now, don't go to any other forum site, as it will confuse you.

 

Can you try this and see if it works? If you have any problems, then just write what it is. There is usually a solution.

 

Now to your general questions:

 

For install you must have 3 files:

  • File 1 (aka Jun's bootloader, .IMG file):
    • Jun's loader is one file in .IMG format. The name is often "bootloader.IMG". This file tricks Synology (DSM) into thinking that you are installing DSM on a Synology device, versus your own.This is the most important file to download on this forum! This is the "hack".
      • You MUST edit this IMG file with OSFMount image mounter (Win, free). If you don't have Windows, download and install Windows 10 into VM on ESXI. You can use evaluation version for free.
        • You need to edit IMG file to set the correct Serial Number (SN) and MAC address.
          • SN gives your a Synology a unique identity, and allows you to create an account with Synology, so that you can access your Synology drive over internet. It seems you are well-versed in porting. You can ignore SN. You are right, you will have better speeds and privacy with your own VPN.
          • MAC allows you to find synology drive on your own network, when you type http://http://find.synology.com/ in your browser. You can manually set MAC address (any address really), but you must insure you specify the same address in your VM setting under "Network Setting". If your http://http://find.synology.com doesn not find synology, this is number one reason why this happens. 
          • Don't worry about PID and VID.
      • After you edit this file save the changes.
  • File 2 (file .VMDK)
    • This file is what is loads VM and enables to you start installation process. This file brings that black terminal screen when you installed other OS.
    • You can use VMDK file from above link or generate your own using StartWind V2V Image converter (Win, free) from the IMG file you edited above. It doesn't matter.
  • File 3 (PAT file)
    • This file contains synology DSM OS. This file has same perpose to .ISO files used for Windows, Ubunti and other installs!
    • This file is found on sYnology website. For exmaple for the installation link I gave you, the PAT file will be located here: https://www.synology.com/en-global/support/download/DS3615xs#utilities
    • You probably never saw PAT file, because Synology devices install DSM over internet or come pre-installed with it. PAT file is used in cases where your Synology device crashes or something bad happens to it and you have to reinstall the entire DSM. Just like when you have to reinstall your Windows OS.

 

Now to ESXI!...

  • The process for installing DSM is different from that for other OS, but it's very easy.
    • You must use one Harddrive that points to VMDK file
      • this is almost the same as using CD/DVD drive and pointing it to .ISO image, like you did for Windows installation.
    • You must use the second hard drive that will have actual DSM installed, and all your volumes. You can set minimum 16GB and expand as you wish.
      • You can add any number of other drives later (after you install Synology), for additional volumes.
    • For each harddrive you add, you must add a separate SATA controller. There must be one added SATA controller for each harddrive you add. SATA controller is something that helps move data from your harddrive through Virtual Machine into Synology and back. 
      • Some users use IDE. I suggest you use SATA.
      • Don't worry about details on SATA, IDE, ISCS...etc. 
  • Note:
    • There is no .ISO file for Xpenology/Synology....you only work with .IMG, VMDK and PAT files.
    • SATA drives you specify in VM, will not slow down your NVMe. Your NVMe will work as fast as it should.
    • When booting you may have to choose to boot in Legacy mode versus UEFI mode. Note that this is boot for Virtual MAchine, and not boot for your ESXI server (bare metal boot). In other words, don't worry that Legacy booting in VM will break your ESXI server. (And I hope you boot your ESXI in UEFI mode :-)...
      • Bottom line, lot of things in VM (but not all) will just create some fog or glue to make your Synology work with your hardware, so don't go to much into details.

 

I hope this helps.

Ask questions if you have.

 

 

Edited by munchgeil1
  • Like 1

Share this post


Link to post
Share on other sites
18 hours ago, mandreto10 said:

Exactly WHAT is Jun's loader?

That is an .img file that allows you to boot and install DSM on baremetal non-synology devices.

Based on what version you use, it will emulate the HW of ie. a DS3615xs, DS3617xs, DS918+ (and so on)

This is a spesific set of files, created and maintained by a regular member of this forum, on his own sparetime, for free.

 

Does that answer your question?

 

Edited by bearcat
typo..

Share this post


Link to post
Share on other sites
On 1/20/2019 at 12:52 AM, mandreto10 said:

What is ISCI anyway?

 

iSCSI is a IP based storage networking standard for linking data storage facilities, using SCSI commands/protocol on top of the TCP/IP protocol

 

What you are referring to on the screenshot, is not iSCSI, it's SCSI, a set of standards for physically connecting and transferring data between computers and peripheral devices.

It was widely used earlier (pre-SATA) as a effective way to use many diskdrives, with hight speed and low CPU usage, due to own controllers.

Optical units and scanners could allso be used in the daisy-chained bus.

 

Did this make sense for you?

 

 

btw: This thread should have been in the "Virtual Environment" sub-forum I guess...

Edited by bearcat
btw..

Share this post


Link to post
Share on other sites
12 hours ago, munchgeil1 said:

Hey mandreto10...

 

Hi! You sound very frustrieted! Let me help you. There is lot of information on this forum....It can be confusing for new person.

 

Here is a very good guide: https://xpenology.com/forum/topic/13061-tutorial-install-dsm-62-on-esxi-67/ 

This guide will work on ESXI 6.5 and 6.7. Make sure you read through the entire post, as there are few important modifications. Specifically changes to Network Card...This link contains all files you need in one place. It has screen shots. The fourth link seems broken. Don't worry about that file. For now, don't go to any other forum site, as it will confuse you.

 

Can you try this and see if it works? If you have any problems, then just write what it is. There is usually a solution.

 

Now to your general questions:

 

For install you must have 3 files:

  • File 1 (aka Jun's bootloader, .IMG file):
    • Jun's loader is one file in .IMG format. The name is often "bootloader.IMG". This file tricks Synology (DSM) into thinking that you are installing DSM on a Synology device, versus your own.This is the most important file to download on this forum! This is the "hack".
      • You MUST edit this IMG file with OSFMount image mounter (Win, free). If you don't have Windows, download and install Windows 10 into VM on ESXI. You can use evaluation version for free.
        • You need to edit IMG file to set the correct Serial Number (SN) and MAC address.
          • SN gives your a Synology a unique identity, and allows you to create an account with Synology, so that you can access your Synology drive over internet. It seems you are well-versed in porting. You can ignore SN. You are right, you will have better speeds and privacy with your own VPN.
          • MAC allows you to find synology drive on your own network, when you type http://http://find.synology.com/ in your browser. You can manually set MAC address (any address really), but you must insure you specify the same address in your VM setting under "Network Setting". If your http://http://find.synology.com doesn not find synology, this is number one reason why this happens. 
          • Don't worry about PID and VID.
      • After you edit this file save the changes.
  • File 2 (file .VMDK)
    • This file is what is loads VM and enables to you start installation process. This file brings that black terminal screen when you installed other OS.
    • You can use VMDK file from above link or generate your own using StartWind V2V Image converter (Win, free) from the IMG file you edited above. It doesn't matter.
  • File 3 (PAT file)
    • This file contains synology DSM OS. This file has same perpose to .ISO files used for Windows, Ubunti and other installs!
    • This file is found on sYnology website. For exmaple for the installation link I gave you, the PAT file will be located here: https://www.synology.com/en-global/support/download/DS3615xs#utilities
    • You probably never saw PAT file, because Synology devices install DSM over internet or come pre-installed with it. PAT file is used in cases where your Synology device crashes or something bad happens to it and you have to reinstall the entire DSM. Just like when you have to reinstall your Windows OS.

 

Now to ESXI!...

  • The process for installing DSM is different from that for other OS, but it's very easy.
    • You must use one Harddrive that points to VMDK file
      • this is almost the same as using CD/DVD drive and pointing it to .ISO image, like you did for Windows installation.
    • You must use the second hard drive that will have actual DSM installed, and all your volumes. You can set minimum 16GB and expand as you wish.
      • You can add any number of other drives later (after you install Synology), for additional volumes.
    • For each harddrive you add, you must add a separate SATA controller. There must be one added SATA controller for each harddrive you add. SATA controller is something that helps move data from your harddrive through Virtual Machine into Synology and back. 
      • Some users use IDE. I suggest you use SATA.
      • Don't worry about details on SATA, IDE, ISCS...etc. 
  • Note:
    • There is no .ISO file for Xpenology/Synology....you only work with .IMG, VMDK and PAT files.
    • SATA drives you specify in VM, will not slow down your NVMe. Your NVMe will work as fast as it should.
    • When booting you may have to choose to boot in Legacy mode versus UEFI mode. Note that this is boot for Virtual MAchine, and not boot for your ESXI server (bare metal boot). In other words, don't worry that Legacy booting in VM will break your ESXI server. (And I hope you boot your ESXI in UEFI mode :-)...
      • Bottom line, lot of things in VM (but not all) will just create some fog or glue to make your Synology work with your hardware, so don't go to much into details.

 

I hope this helps.

Ask questions if you have.

 

 

 

 

THANK YOU SO MUCH!

 

You made the maze of confusing information simple and easy to understand and follow. I needed OS up and running, not a degree in computer science.

Your recommendations worked flawlessly!

 

You must be incredibly intelligent! Not everyone has the ability to simplify like you just did.

 

THANK YOU!!!!!

 

 

Edited by mandreto10

Share this post


Link to post
Share on other sites

[mention=44403]mandreto10[/mention] I highly suggest you review your attitude and the way you talk to others. People have been trying to help you but your arrogance is beyond my understanding. I have spend countless hours restructuring and running the forum, making tutorials, helping thousands of people and when I read your posts I even wonder why people answered to you in the first place. To this day I have never, not even once, come across a user in the this forum that has shown such behavior. You are new here so modesty is probably something you should consider if you want others to help.

 

 For your information no one here is paid to:

1 - make the loader

2 - run the forum

3 - moderate the forum

4 - contribute to the forum

 

You can start by reading the Rules and Guidelines. That will give you a general understanding of how we roll here. Then you can read the FAQs. That should provide a general understanding of what XPEnology is and how it all works.

 

If you have additional questions please ask them in the appropriate section and in a manner that is respectful to others.

 

Thank you.

 

  • Like 3

Share this post


Link to post
Share on other sites
4 hours ago, Polanskiman said:

@mandreto10 I highly suggest you review your attitude and the way you talk to others. People have been trying to help you but your arrogance is beyond my understanding. I have spend countless hours restructuring and running the forum, making tutorials, helping thousands of people and when I read your posts I even wonder why people answered to you in the first place. To this day I have never, not even once, come across a user in the this forum that has shown such behavior. You are new here so modesty is probably something you should consider if you want others to 

 

 For your information no one here is paid to:

1 - make the loader

2 - run the forum

3 - moderate the forum

4 - contribute to the forum

 

You can start by reading the Rules and Guidelines. That will give you a general understanding of how we roll here. Then you can read the FAQs. That should provide a general understanding of what XPEnology is and how it all works.

 

If you have additional questions please ask them in the appropriate section and in a manner that is respectful to others.

 

Thank you.

 

Thank you for the feedback.

 

I asked simple and specific questions, and I am thankful to the one forum user who stepped in to provide simple answers, and to the one who wrote a simple but useful guide. I made commends very explicit. Many users stated that they spent hours trying to make it work, because guides were incomplete.

 

I hope you have a wonderful day.

Edited by mandreto10

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now