kitmsg Posted February 23, 2017 #1 Posted February 23, 2017 (edited) 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!yQpw0YTI!DQqIzUCG2RbBtQ6YieScWg 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 July 16, 2019 by Polanskiman Updated OP with loader link as it was broken. 2 Quote
CtrlAltDel Posted February 27, 2017 #2 Posted February 27, 2017 Not tested your guide but thanks for sharing. Quote
sera Posted March 1, 2017 #3 Posted March 1, 2017 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. Quote
Gex Posted March 1, 2017 #4 Posted March 1, 2017 (edited) Thank you for sharing! Finally a way to get DSM working on Virtualbox. Plus, it's really dead simple. 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 ) 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 March 2, 2017 by Guest Quote
tjbain Posted March 1, 2017 #5 Posted March 1, 2017 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... Quote
kitmsg Posted March 2, 2017 Author #6 Posted March 2, 2017 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 Quote
Gex Posted March 2, 2017 #7 Posted March 2, 2017 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. 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. Quote
kitmsg Posted March 3, 2017 Author #8 Posted March 3, 2017 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. Quote
nevusZ Posted July 10, 2017 #9 Posted July 10, 2017 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? Quote
jcdln Posted August 7, 2017 #10 Posted August 7, 2017 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! Quote
aoprea Posted April 16, 2018 #11 Posted April 16, 2018 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 Quote
polanskiman Posted April 17, 2018 #12 Posted April 17, 2018 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. Quote
aoprea Posted April 17, 2018 #13 Posted April 17, 2018 (edited) Done with Bridget network. Thanx Edited April 17, 2018 by aoprea Quote
pepeEL Posted June 12, 2018 #14 Posted June 12, 2018 Is any chance for Virtualbox for DSM version 6.2 ? Quote
IG-88 Posted July 22, 2018 #15 Posted July 22, 2018 On 6/12/2018 at 8:01 PM, pepeEL said: Is any chance for Virtualbox for DSM version 6.2 ? no problem if the cpu of the host system would work as baremetal for that version/model (min. 4th gen intel core with 918+ image) as with 916+ the 918+ needs a sata disk as bootdevice (instead of the usb flash drive with baremetal or the IDE mentioned above) and the disks for data also have to be defined as sata 1st sata 50mb boot vmdk (use the wrapper file for the img file that comes with 1.02a), 2nd sata 100GB, ... dsm will "ignore" the 1st 50mb disk as it cant hold any data like system or swap partition Quote
CQTIT Posted September 29, 2018 #16 Posted September 29, 2018 Danke es hat zum Testen Wunderbar geklappt. Danke dafür an die Autoren und die Betreiber der Webseite. Quote
kenysc Posted January 7, 2019 #17 Posted January 7, 2019 Followed the guide and got DSM installed as a Vbox 6.0 guest on Ubuntu 18.04 on a HP N54L hardware. Moreover, successfully added 3 raw disks to DSM and set up those as a RAID5 volume. Reference to below pages: Added raw disk access https://www.serverwatch.com/server-tutorials/using-a-physical-hard-drive-with-a-virtualbox-vm.html Raw disks auto detected as eSATA shared drives, solution to force them as internal https://hedichaibi.com/fix-xpenology-problems-viewing-internal-hard-drives-as-esata-hard-drives/ Quote
peyota Posted January 31, 2019 #18 Posted January 31, 2019 (edited) from were i download the files ? The links cant work Edited January 31, 2019 by peyota Quote
wilmer fernandez Posted July 15, 2019 #19 Posted July 15, 2019 I have a problem and I do not know what it is. someone can help me with the subject, apparently it is the connection. thanks from colombia Quote
Beatcoin Posted November 5, 2019 #20 Posted November 5, 2019 Just in case you want to play with the v1.04b synoboot.img, you have to use 001132123456 MAC adress, not 0011322CA785 as said in the tutorial. Otherwise network connexion won't work. Quote
Neocide Posted November 20, 2020 #21 Posted November 20, 2020 Hello, i tried to install DSM 6.1.7 on virtualbox with Jun's Loader 1.02-alpha DS3615xs, but i have an issue, vm boot normaly, i'm install dsm pat , vm reboot, but never boot. Log serial : [H[J[1;1H[?25l[m[H[J[1;1H[2;21HGNU GRUB version 2.02~beta2-36ubuntu3.7 [m[4;2H+----------------------------------------------------------------------------+[5;2H|[5;79H|[6;2H|[6;79H|[7;2H|[7;79H|[8;2H|[8;79H|[9;2H|[9;79H|[10;2H|[10;79H|[11;2H|[11;79H|[12;2H|[12;79H|[13;2H|[13;79H|[14;2H|[14;79H|[15;2H|[15;79H|[16;2H|[16;79H|[17;2H+----------------------------------------------------------------------------+[m[18;2H[19;2H[m Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. [5;80H [7m[5;3H*DS3615xs 6.1 Baremetal with Jun's Mod v1.02-alpha [m[5;78H[m[m[6;3H DS3615xs 6.1 Baremetal with Jun's Mod v1.02-alpha Reinstall [m[6;78H[m[m[7;3H DS3615xs 6.1 Baremetal with Jun's Mod v1.02-alpha Force Install [m[7;78H[m[m[8;3H DS3615xs 6.1 VMWare/ESXI with Jun's Mod v1.02-alpha [m[8;78H[m[m[9;3H [m[9;78H[m[m[10;3H [m[10;78H[m[m[11;3H [m[11;78H[m[m[12;3H [m[12;78H[m[m[13;3H [m[13;78H[m[m[14;3H [m[14;78H[m[m[15;3H [m[15;78H[m[m[16;3H [m[16;78H[m[16;80H [5;78H[22;1H The highlighted entry will be executed automatically in 1s. [5;78H[22;1H [23;1H [5;78H[m[5;3H DS3615xs 6.1 Baremetal with Jun's Mod v1.02-alpha [m[5;78H[m[7m[6;3H*DS3615xs 6.1 Baremetal with Jun's Mod v1.02-alpha Reinstall [m[6;78H[m[m[6;3H DS3615xs 6.1 Baremetal with Jun's Mod v1.02-alpha Reinstall [m[6;78H[m[7m[7;3H*DS3615xs 6.1 Baremetal with Jun's Mod v1.02-alpha Force Install [m[7;78H[m[m[7;3H DS3615xs 6.1 Baremetal with Jun's Mod v1.02-alpha Force Install [m[7;78H[m[7m[8;3H*DS3615xs 6.1 VMWare/ESXI with Jun's Mod v1.02-alpha [m[8;78H[m[?25h[H[J[1;1H[H[J[1;1H[H[J[1;1H[H[J[1;1Hpatching file etc/rc 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[ 18.477407] sd 0:0:0:0: [sda] Incomplete mode parameter data [ 18.484494] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 18.538770] sd 0:0:0:0: [sda] Incomplete mode parameter data [ 18.544159] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 18.604068] sd 0:0:0:0: [sda] Incomplete mode parameter data [ 18.610665] sd 0:0:0:0: [sda] Assuming drive cache: write through ... [ OK ] :: Loading module mptsas ... [ OK ] :: Loading module mptctl ... [ OK ] :: Loading module ata_piix[ 18.999336] ata1: Read current link speed fail, retry 1 [ 19.012201] ata1: Read current link speed fail, retry 2 [ 19.021473] ata1: Read current link speed fail, retry 3 [ 19.032429] ata2: Read current link speed fail, retry 1 [ 19.043626] ata2: Read current link speed fail, retry 2 [ 19.056113] ata2: 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 Partition Version=0 Partition layout is not DiskStation style. NOT EXECUTE /sbin/e2fsck. Mounting /dev/md0 /tmpRoot mount: lseek failed, msg:Invalid argument mount: mounting /dev/md0 on /tmpRoot failed: No such device mount /dev/md0 fail, returns Exit on error [3] no init exists... Fri Nov 20 16:39:40 UTC 2020 none /sys/kernel/debug debugfs rw,relatime 0 0 sys /sys sysfs rw,relatime 0 0 none /dev devtmpfs rw,relatime,size=4086792k,nr_inodes=1021698,mode=755 0 0 proc /proc proc rw,relatime 0 0 linuxrc.syno failed on 3 starting pid 3869, tty '': '/etc/rc' :: Starting /etc/rc :: Mounting procfs ... [ OK ] :: Mounting tmpfs ... [ OK ] :: Mounting devtmpfs ... [ OK ] :: Mounting devpts ... [ OK ] :: Mounting sysfs ... [ OK ] mdadm: error opening /dev/md1: No such file or directory rc: Use all internal disk as swap. swapon: can't stat '/dev/md1': No such file or directory :: Loading module sg ... [ OK ] :: Loading module mdio ... [ OK ] :: Loading module fat ... [ OK ] :: Loading module vfat ... [ OK ] :: Loading module dca ... [ OK ] :: Loading module e1000e ... [ OK ] :: Loading module i2c-algo-bit ... [ OK ] :: Loading module igb ... [ OK ] :: Loading module ixgbe ... [ OK ] :: Loading module libcrc32c ... [ OK ] :: Loading module mii ... [ OK ] :: Loading module libphy ... [ OK ] :: Loading module atl1 ... [ OK ] :: Loading module atl1e ... [ OK ] :: Loading module atl1c ... [ OK ] :: Loading module alx ... [ OK ] :: Loading module uio ... [ OK ] :: Loading module ipg ... [ OK ] :: Loading module jme ... [ OK ] :: Loading module skge ... [ OK ] :: Loading module sky2 ... [ OK ] :: Loading module ptp_pch ... [ OK ] :: Loading module pch_gbe ... [ OK ] :: Loading module qla3xxx ... [ OK ] :: Loading module qlcnic ... [ OK ] :: Loading module qlge ... [ OK ] :: Loading module netxen_nic ... [ OK ] :: Loading module sfc ... [ OK ] :: Loading module e1000 ... [ OK ] :: Loading module pcnet32 ... [ OK ] :: Loading module vmxnet3 ... [ OK ] :: Loading module bnx2 ... [ OK ] :: Loading module bnx2x ... [ OK ] :: Loading module cnic ... [FAILED] :: Loading module r8169 ... [ OK ] :: Loading module tg3 ... [ OK ] :: Loading module usbnet ... [ OK ] :: Loading module ax88179_178a ... [ OK ] :: Loading module button ... [ OK ] :: Loading module synobios ... [ OK ] udhcpc (v1.16.1) started eth0 Link encap:Ethernet HWaddr 00:11:32:2C:A7:86 inet addr:192.168.0.223 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:44 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3221 (3.1 KiB) TX bytes:1480 (1.4 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) :: Starting syslogd ... [ OK ] :: Starting scemd :: Starting services in background Starting findhostd in flash_rd... Starting services in flash_rd... Running /usr/syno/etc/rc.d/J01httpd.sh... Starting httpd:80 in flash_rd... Starting httpd:5000 in flash_rd... Running /usr/syno/etc/rc.d/J03ssdpd.sh... /usr/bin/minissdpd -i eth0 (15): upnp:rootdevice (51): uuid:upnp_SynologyNAS-0011322ca786::upnp:rootdevice (57): Synology/synology_bromolow_3615xs/6.1-15047/192.168.0.223 (46): http://192.168.0.223:5000/description-eth0.xml Connected. done. /usr/syno/bin/reg_ssdp_service 192.168.0.223 0011322ca786 6.1-15047 synology_bromolow_3615xs eth0 Running /usr/syno/etc/rc.d/J04synoagentregisterd.sh... Starting synoagentregisterd... Running /usr/syno/etc/rc.d/J30DisableNCQ.sh... Running /usr/syno/etc/rc.d/J80ADTFanControl.sh... Running /usr/syno/etc/rc.d/J98nbnsd.sh... Starting nbnsd... Running /usr/syno/etc/rc.d/J99avahi.sh... Starting Avahi mDNS/DNS-SD Daemon cname_load_conf failed:/var/tmp/nginx/avahi-aliases.conf :: Loading module hid ... [ OK ] :: Loading module usbhid ... [ OK ] ============ Date ============ Fri Nov 20 16:39:55 UTC 2020 ============================== starting pid 5537, tty '': '/sbin/getty 115200 console' Fri Nov 20 16:39:56 2020 DiskStation login: The system is going down NOW! Sent SIGTERM to all processes Sent SIGKILL to all processes Unmounting all file systems. Unmounting /sys/kernel/debug ... Unmounting /proc/bus/usb ... Unmounting /sys ... Unmounting /dev/pts ... Unmounting /dev ... Failed to umount /dev, 16 Unmounting /tmp ... Unmounting / ... All file systems unmounted. Requesting system reboot [ 243.287747] Restarting system. [H[J[1;1H[?25l[m[H[J[1;1H[2;21HGNU GRUB version 2.02~beta2-36ubuntu3.7 [m[4;2H+----------------------------------------------------------------------------+[5;2H|[5;79H|[6;2H|[6;79H|[7;2H|[7;79H|[8;2H|[8;79H|[9;2H|[9;79H|[10;2H|[10;79H|[11;2H|[11;79H|[12;2H|[12;79H|[13;2H|[13;79H|[14;2H|[14;79H|[15;2H|[15;79H|[16;2H|[16;79H|[17;2H+----------------------------------------------------------------------------+[m[18;2H[19;2H[m Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. [5;80H [m[5;3H DS3615xs 6.1 Baremetal with Jun's Mod v1.02-alpha [m[5;78H[m[m[6;3H DS3615xs 6.1 Baremetal with Jun's Mod v1.02-alpha Reinstall [m[6;78H[m[m[7;3H DS3615xs 6.1 Baremetal with Jun's Mod v1.02-alpha Force Install [m[7;78H[m[7m[8;3H*DS3615xs 6.1 VMWare/ESXI with Jun's Mod v1.02-alpha [m[8;78H[m[m[9;3H [m[9;78H[m[m[10;3H [m[10;78H[m[m[11;3H [m[11;78H[m[m[12;3H [m[12;78H[m[m[13;3H [m[13;78H[m[m[14;3H [m[14;78H[m[m[15;3H [m[15;78H[m[m[16;3H [m[16;78H[m[16;80H [8;78H[22;1H The highlighted entry will be executed automatically in 1s. [8;78H[22;1H The highlighted entry will be executed automatically in 0s. [8;78H[?25h[H[J[1;1H[H[J[1;1H[H[J[1;1H[H[J[1;1H Have you got any idea ? Thanks for you help. Quote
IG-88 Posted November 24, 2020 #23 Posted November 24, 2020 (edited) i'd suggest replacing the synoboot.img with the one from 1.03b (the vmdk is just a text file acting as "translation") with 1.03b (dsm 6.2.3) you need to have sata as boot solution not ide its not eve needed to have two sata controllers (1st for the boot vmdk), it work with just one and having the 1st disk the boot vmdk and 2nd the data disk taht will be used to install dsm and as data volume the important thing is that mac in the grub.cfg and the one used in the VM need to be the same so look in your vm and put that mac in the grub.cfg inside your sonoboot.img, osfmount is your friend and you might read this https://xpenology.com/forum/topic/29872-tutorial-mount-boot-stick-partitions-in-windows-edit-grubcfg-add-extralzma/ that how my (working) dsm 6.2 x vm looks like Edited November 24, 2020 by IG-88 Quote
Soogs Posted December 16, 2020 #24 Posted December 16, 2020 Hi there, i've successfully set the 6.2 system on windows via vmware player trying to set it up via mac osx using virtualbox but with no success. the bootloader works but i cant find the synology via fin.synology.com or even see the vm on my netowork using fing. ive tried nat and bridged connections using the mac address listed in the op and random macs with no joy. what am i doing wrong? Quote
billat29 Posted December 16, 2020 #25 Posted December 16, 2020 This is my test virtual machine under virtualbox - but on Linux. As IG-88 says you MUST make sure that the mac address in the virtualbox network adapter matches the one in the loader or you won't see the VM on the network. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.