kitmsg

Tutorial: Install 6.x on Oracle Virtualbox (Jun's loader)

Recommended Posts

Thanks Gex for the update for v1.02a

 

1. Read the original post announced by jun: http://xpenology.com/forum/viewtopic.php?f=2&t=20216

2. Download the bootloader v1.01 (DSM 6.0.2-8451) or bootloader v1.02a (alpha version for DSM 6.1-15047): https://mega.nz/#F!BtFQ2DgC!JgomNP3X8V9EuwxL4TXbng

3. Unzip the package. We will need 2 files: synoboot.img and synoboot.vmdk

4. Create a Virtualbox VM:

  • 4.1 Operation System: Other Linux (64bit)

  • 4.2 Create 2 Storage Controller:

  • a) IDE: Mount the file synoboot.vmdk

  • b) SCSI: Create a new harddisk for your data storage (Has to be SCSI, otherwise it won't work!)

  • 4.3 Setup the network:

  • a) Bridge or NAT, it's up to you

  • b) Expand the Advanced option

  • c) Adapter type: Intel PRO/1000 MT Desktop (8254OEM)

  • d) MAC Address: 0011322CA785 (This is the most important setting to make your Xpenology accesssible!)

5. Start the VM, press F12 to enable the boot menu

6. Boot from IDE harddisk 1

7. In the gnub menu, select the last option (xxx VMware xxx)

8. Wait around 2~5 minutes, depends on your Hardware spec. The bootloader only show around 10 lines of message. Don't worry. Be patient and it's still loading the system.

9. Install synology assistant. Press Search button

10. You should see your new DiskStation now. If not, wait for another 1 or 2 minutes

11. The most important step! Verify the MAC address shown in the Synology Assistant. Make sure it's the same as the one you set in step 4.3d above.

12. Here you go, do what you usually do to a Synology system to install the DSM.

 

Enjoy!

Edited by Guest
  • Like 1

Share this post


Link to post
Share on other sites

Hi, i foun an issue.

I have to virtual disk of 8GB. When i select create a raid group type "raid0", the final capacity is 3,6GB and not 16GB.

Same issue on other raid types.

Share this post


Link to post
Share on other sites

Thank you for sharing! Finally a way to get DSM working on Virtualbox. Plus, it's really dead simple. :cool:

 

I just successfully installed DSM 6.1-15047 for DS3617xs using Jun's Loader 1.02a. (So it would be safe to edit the thread title accordingly :wink:)

 

Pitfalls:

* Make sure you add a SCSI controller for the data disks. I didn't read the instructions too thoroughly and added a SATA controller. This will lead to error 35 during installation (Failed to format the drive).

* Make sure you make the virtual harddisk(s) bigger than the standard 8 GB. If the virtual disks are too small you might encounter error 35, too.

 

Edit:

@sera

This is due to the partition layout that DSM creates during the installation. Every hard disk will hold a system partition (mirrored across all disks), a swap partition and a data partition. So the first two will use a certain amount of disk space and the data partition gets what's left.

 

Edit: The link to Jun's loader in the first post is dead. Currently this one is working: https://mega.nz/#F!BtFQ2DgC!JgomNP3X8V9EuwxL4TXbng

 

Edit: Installed DSM 6.1 Update 1 without any problems.

Edited by Guest

Share this post


Link to post
Share on other sites

thanks for the tutorial.

 

I can't wait for someone to add the proper Hyper-V modules/drivers to Jun's loader. Everything currently boots fine, but there is no network connection. One day...

 

:grin:

Share this post


Link to post
Share on other sites

hi Gex,

 

Thanks for your update.

 

However, I couldn't migrate the xpenology from 6.0.2 bootloader. Are you able to do that? I can find my xpenology by synology assistant before upgrade. I can install the pat file. However, after the pat file is uploaded, the vm restarts. After that, synology assistant is not able to find the xpenology anymore.

 

Cheers,

kitmsg

Share this post


Link to post
Share on other sites

I tried the following update procedure without success:

 

1. Install DSM 6.0.2 into a new VM using Jun's loader 1.01 and create a basic volume

2. Update to 6.0.2 U9 (had to do a hard reset of the VM once after upgrading), successful

3. Shutdown

4. Remove 1.01 synoboot.vmdk, add 1.02a synoboot.vmdk and boot the VM

5. VM won't completely boot into DSM, web interface tells me to update to 6.1

6. Upload .pat file for 6.1 via web interface, everything seems fine up to this point. Chose the "migrate and keep settings" option over the "reinstall and only keep data" option. Update begins.

7. VM reboots and won't come up again --> fail.

 

I had the VM redirect its COM1 port to a txt file and this is what it looks like now:

 

[    4.528899] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    4.581904] sd 0:0:0:0: [sda] Incomplete mode parameter data
[    4.611890] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    4.651344] sd 0:0:0:0: [sda] Incomplete mode parameter data
[    4.661292] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    4.982197] ata1: Read current link speed fail, retry 1
[    5.017897] ata1: Read current link speed fail, retry 2
[    5.036262] ata1: Read current link speed fail, retry 3
[    5.074569] ata2: Read current link speed fail, retry 1
[    5.088286] ata2: Read current link speed fail, retry 2
[    5.098893] ata2: Read current link speed fail, retry 3
[    5.106148] ata1: Issued IDENTIFY to non-existent device ?!
[    7.226517] ata1: Read current link speed fail, retry 1
[    7.238722] ata1: Read current link speed fail, retry 2
[    7.259413] ata1: Read current link speed fail, retry 3
[    7.261137] ata1: Issued IDENTIFY to non-existent device ?!
[    9.418591] ata1: Read current link speed fail, retry 1
[    9.440276] ata1: Read current link speed fail, retry 2
[    9.465911] ata1: Read current link speed fail, retry 3
[    9.480874] ata1: Issued IDENTIFY to non-existent device ?!
[   11.639599] ata1: Read current link speed fail, retry 1
[   11.649804] ata1: Read current link speed fail, retry 2
[   11.679829] ata1: Read current link speed fail, retry 3
[   11.879651] md: invalid raid superblock magic on sda3
[  868.949994] Restarting system.

.............

[    4.386686] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    4.443562] sd 0:0:0:0: [sda] Incomplete mode parameter data
[    4.472466] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    4.509918] sd 0:0:0:0: [sda] Incomplete mode parameter data
[    4.521888] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    4.834537] ata1: Read current link speed fail, retry 1
[    4.869557] ata1: Read current link speed fail, retry 2
[    4.901761] ata1: Read current link speed fail, retry 3
[    4.935602] ata2: Read current link speed fail, retry 1
[    4.947774] ata2: Read current link speed fail, retry 2
[    4.957817] ata2: Read current link speed fail, retry 3
[    4.959723] ata1: Issued IDENTIFY to non-existent device ?!
[    7.089336] ata1: Read current link speed fail, retry 1
[    7.110555] ata1: Read current link speed fail, retry 2
[    7.120545] ata1: Read current link speed fail, retry 3
[    7.122814] ata1: Issued IDENTIFY to non-existent device ?!
[    9.282435] ata1: Read current link speed fail, retry 1
[    9.309388] ata1: Read current link speed fail, retry 2
[    9.355944] ata1: Read current link speed fail, retry 3
[    9.389786] ata1: Issued IDENTIFY to non-existent device ?!
[   11.549004] ata1: Read current link speed fail, retry 1
[   11.576282] ata1: Read current link speed fail, retry 2
[   11.591274] ata1: Read current link speed fail, retry 3
[   11.773601] md: invalid raid superblock magic on sda3
[   42.114714] BTRFS: has skinny extents

 

So now you could go ahead and try different approaches, two of them being:

- Attempt to do the update via the DSM web interface before changing the synoboot.vmdk to 1.02a or

- Choose the "reinstall and keep data" option when prompted on the web interface

 

If I had taken a snapshot of the VM before the update, I would try... oh well. :roll:

 

 

Edit:

After rebooting the VM, the log looks a bit more promising:

patching file etc/synoinfo.conf
patching file linuxrc.syno
patching file usr/sbin/init.post
START /linuxrc.syno
Insert basic USB modules...
:: Loading module usb-common ... [  OK  ]
:: Loading module usbcore ... [  OK  ]
:: Loading module ehci-hcd ... [  OK  ]
:: Loading module ehci-pci ... [  OK  ]
:: Loading module ohci-hcd ... [  OK  ]
:: Loading module uhci-hcd ... [  OK  ]
:: Loading module xhci-hcd ... [  OK  ]
:: Loading module etxhci-hcd ... [  OK  ]
:: Loading module usb-storage ... [  OK  ]
:: Loading module BusLogic ... [  OK  ]
:: Loading module vmw_pvscsi ... [  OK  ]
:: Loading module megaraid_mm ... [  OK  ]
:: Loading module megaraid_mbox ... [  OK  ]
:: Loading module megaraid ... [  OK  ]
:: Loading module scsi_transport_spi ... [  OK  ]
:: Loading module mptbase ... [  OK  ]
:: Loading module mptscsih ... [  OK  ]
:: Loading module mptspi[    4.444826] sd 0:0:0:0: [sda] Incomplete mode parameter data
[    4.449110] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    4.463970] sd 0:0:0:0: [sda] Incomplete mode parameter data
[    4.465942] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    4.482676] sd 0:0:0:0: [sda] Incomplete mode parameter data
[    4.484877] sd 0:0:0:0: [sda] Assuming drive cache: write through
... [  OK  ]
:: Loading module mptsas ... [  OK  ]
:: Loading module mptctl ... [  OK  ]
:: Loading module ata_piix[    4.809929] ata1: Read current link speed fail, retry 1
[    4.844371] ata1: Read current link speed fail, retry 2
[    4.869253] ata1: Read current link speed fail, retry 3
[    4.893491] ata2: Read current link speed fail, retry 1
[    4.929099] ata2: Read current link speed fail, retry 2
[    4.958922] ata2: Read current link speed fail, retry 3
[    4.972704] ata1: Issued IDENTIFY to non-existent device ?!
[    7.050180] ata1: Read current link speed fail, retry 1
[    7.063623] ata1: Read current link speed fail, retry 2
[    7.093430] ata1: Read current link speed fail, retry 3
[    7.110508] ata1: Issued IDENTIFY to non-existent device ?!
[    9.272260] ata1: Read current link speed fail, retry 1
[    9.293305] ata1: Read current link speed fail, retry 2
[    9.308325] ata1: Read current link speed fail, retry 3
[    9.331196] ata1: Issued IDENTIFY to non-existent device ?!
[   11.493653] ata1: Read current link speed fail, retry 1
[   11.528889] ata1: Read current link speed fail, retry 2
[   11.559970] ata1: Read current link speed fail, retry 3
... [  OK  ]
:: Loading module megaraid_sas ... [  OK  ]
:: Loading module mpt2sas ... [  OK  ]
:: Loading module mpt3sas ... [  OK  ]
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
[   12.253539] md: invalid raid superblock magic on sda3
Partition Version=8
/sbin/e2fsck exists, checking /dev/md0... 
1.42.6-8438: recovering journal
1.42.6-8438: |==                                              |  3.7%   
1.42.6-8438: |========================================        / 84.0%   
1.42.6-8438: |================================================| 100.0%   


      30816 inodes used (19.80%, out of 155648)
         31 non-contiguous files (0.1%)
          8 non-contiguous directories (0.0%)
            # of inodes with ind/dind/tind blocks: 0/0/0
            Extent depth histogram: 28045/12
     244851 blocks used (39.33%, out of 622544)
          0 bad blocks
          1 large file

      24594 regular files
       3163 directories
          2 character device files
          0 block device files
          0 fifos
       1229 links
       3048 symbolic links (2749 fast symbolic links)
          0 sockets
------------
      32036 files
/sbin/e2fsck returns 1
Mounting /dev/md0 /tmpRoot
------------upgrade
Begin upgrade procedure
No upgrade file exists
End upgrade procedure
============upgrade
Wait 2 seconds for synology manufactory device
Thr Mar  2 16:34:15 UTC 2017
/dev/md0 /tmpRoot ext4 rw,relatime,journal_checksum,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
none /dev devtmpfs rw,relatime,size=506564k,nr_inodes=126641,mode=755 0 0
proc /proc proc rw,relatime 0 0

linuxrc.syno executed successfully.
Post init

[   23.438885] BTRFS: has skinny extents


DSMigrationTest login: 

 

Looks better to me (though still not good), but the web interface remains unreachable.

Share this post


Link to post
Share on other sites

Thanks, Gex.

 

I can install a clean DSM6.1 on a VM from scratch, so I think 1.02a partially work.

 

I like your idea to to upgrade to 6.1 with 1.01 first. Then at some stage afterward, I switch to 1.02a. I will have a try.

Share this post


Link to post
Share on other sites

hy,

i am trying to install ds916+ image inside virtualbox. it doesn't work. i am getting the error "Failed to install the file. The file is probably corrupted. 13"

this happens when i add disks with sata controller.

checked the md5 sum of my pat file - it is correct.

 

my cpu is haswell so it should be able for ds916+ image

 

if a add disks as scsi they aren't recognized

 

anyone managed to install ds916+ image in virtualbox? 

Share this post


Link to post
Share on other sites

Hi,

 

I'm trying to create a VM using Virtualbox and last jun's loader version (1.02b) by adding raw data disks but I can't add them : Vbox returns me VERR_ACCESS_DENIED error when adding the disk.vmdk.

Moreover is there a way to add data disks under SATA controller vs ISCI controller? Maybe that's the reason why I can't get SHR working when I'm creating a volume.

 

Thank you for your help! ;-)

Share this post


Link to post
Share on other sites

Hi,

 

I'm trying to create a VM using Virtualbox and last jun's loader version (1.02b).

All good until synology assistant not find anything.

what is wrong ?

 

Virtualbox show this message for 10 minutes

 

 

Screenshot_2.jpg

Share this post


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

Hi,

 

I'm trying to create a VM using Virtualbox and last jun's loader version (1.02b).

All good until synology assistant not find anything.

what is wrong ?

 

Virtualbox show this message for 10 minutes

 

1 - Use Linux 2.6 /3.x /4.x (64 bits), although this is not really the issue.

2 - Use Intel PRO/1000 T Server. Make sure to use the same MAC address in the grub.cfg file. Also try bridging instead of NAT.

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