NoFate

so , created a new esxi virtual i boot from 6.1 synoboot.img loader created 1 extra virtual disk on my datastore, like 100GB for DSM soft , and apps installed DSM succesfully, all is working fine then i passthrough my sata ahci , with 4 bays , all western digital however, when i boot up synology, i only see 2 disks in passthrough, the ones in bay 3 and 4, disk number 3 and 4 so i think synology is confused about sata port mapping the virtual disk and synoboot are also disk 1 and disk 2 , so therefore i am not seeing the drives in bay 1 and 2 ? how can i fix this?? also tried this, from another topic, but doesnt help : set extra_args_3615='iommu=soft'

it seems whenever i start the loader jun 6.1 , 3651xs , it doesnt see the passthroughed disks were DSM 5.2 was installed on in my 4 bay, i had 4 disks, 2 disks were in raid shr, with 5.2 on, that 2 extra disks just as basic, for temp files when i start 6.1 , clean install, then i insert disk 3 in my bay, with temp files on, i have no issues, so i know passthrough is working so i think i need to move the DSM sofware, from my 2 first basic raid , to a virtual disk is that possible?

Well, running 5.2 for a while now in esxi i have 1 virtual disk, (apps) and passthrough my sata controller vor 4 four sata disks on my HP gen8 now on 5.2 esxi, i boot ide controller master, synoboot 5.2 vmdk/image first i started clean, so created a new 6.1 , 1 virtual disk, no passthrough ye installed and working fine then i reattach my passtrhough controller , but 6.1 doesnt see the disks, also enabled shr manally in syslinux, no change so removed 6.1 virtual host so edited 5.2 virtual host, changed ide controller master to new synoboot.img , 6.1 loader then i boot up, i get the migrate option , keep data but i am always in the same loop, after migrate is finished, on reboot, i get the same migrate option... in the past i started 5.2 on baremetal, i think the full DSM cnfiguration is on that shr raid, does it mather? it seems that that DSM config is not updated when i do the migration also, when 5.2 was started, all the disks, including virtual disk has the number 1 , i see that in my storage manager, also strange ?

ok, step further , seems its a grub.cfg file in 6.1 loader i was able to change the cfg file with OSFmount, my 6.1 is now starting up with new sn and new mac , this new mac and sn is from an real ds1512+ , so not ds3615xs seems quickconnect still not working cant i use the real sn / mac from another model (never registred to quickocnnect yet) ?4 thnx

Hey, i am working with esxi, i want to modify the syslinux.cfg file inside the synoboot.img (new sn + mac) i have an original one, so i want to have quickconnect but it seems i cant edit it with winiso or winiamage so tried to mount it wth daemon tools no , succes, renamed to iso, then mount it no success so how can we change the IMG file or the syslinux.cfg inside of it? does it mather if the new sn/mac is from another model? tnx

same here , did you ever resolve , i cant add sata controller either in esxi 6.5

hey, sorry , i dont understand russion, but can any1 provide me the patch for 8.1.2 ? thnx

i had the same issues about the drops, look in this topic started from this reply : lowe i fixed on my asrock by lowering from 4 GB to 2 GB ram, on my hp gen 8 i created a workaround,

Thnx , well that hpsva is resolved in 6.5 Jun release... But anyway, I have it working now with this config/setup... Still don't know what the issue is since it's not solved, because this is a workaround

Thnx indeed enough answers

Hi, well I I have indeed searched, but I couldn't find that many hits on it, also not a clear answer what the next step step is... Sorry in advance

Hi, yes I played around with different hardware, first ASRock on baremetal, then baremetal on hp gen 8, now added an extra controller on hp gen 8 and moved to esxi and passthrough the original controller Always moved the datadisks since the beginning, but I never runned 6.1 yet I am now running esxi with 2 disk controller, and want the same config on 6.1 But gonna make a backup first before pressing enter on that message

Yes, this is another question/issue since it's more related to upgrading 5.2 to 6.1

hi been using 5.2 for a while, on baremetal and now switched over to ESXI setup in esxi, 1 virtual disk (dsm & apps located) , passthroughd my sata controller for my other 4 disks that contains data now 6.1 so i create a new VM, give it again 1 virtual disk, i install DSM 6.1 , working perfect so far now i attach my sata controller again in passthrough to gain access to my data now when in boot DSM6.1 i have this warning message : we've detected that the hard drives of your current ds3615xs has been moved from a previous ds3615xs, and installing a newer dsm is required before continuing is it safe to proceed? probably there is stuff on a hidden partition on it, do i loose data? since i have esx, i have tried to replicate this when creating a new 5.2 with virtual disks, then attach those virtual disks to a new clean 6.1 install, but i dont get that warning anymore thnx again

yes, i can do that , thats the advantage of esxi thnx

Hi, I just want to start clean, there is not much config on mine, just some apps... So I start a new VM with Jun loader, create a new virtual disk, install Dsm on it After it, I insert my other disks, I get that warning I posted earlier, then it will overwrite without loosing data, right?

hey i am playing around with 5.2 in ESX, i am going to update to 6.1 , i will start with a clean VM, probably the DSM software will be replaced on all raid/disks but what if i am not happy with 6.1 and want to go back to my 5.2 VM can i just boot it up again, when i attach the controller that i passthrough because if i fireup 5.2 with this file again = XPEnoboot_DS3615xs_5.2-5967.1 , it will notice that DSM 6.1 was installed so, how can i downgrade in an ESX system from 6.1 to 5.2 without loosing data? thnx

ok, i tried anyway created a new VM , start clean, install DSM on a virtual disk (ssd), i turn off, i attach my other disk as soon as i start now 6 i get this message : we've detected that the hard drives of your current ds3615xs has been moved from a previous ds3615xs, and installing a newer dsm is required before continuing am i save to proceed? , probably it will overwrite, so i think i can continue?? if i continue, lets say, i want to go back to 5.2 , can i still do that then? will it downgrade? without loosing data offcourse

Ok, thnx for info... What happens if I start clean with 6.1 instead of 5.2 If I then insert the disk, witch contains the config from 5.2 ? Will it crash or ? Will it migrate automatically?

hi same issues here on my asrock and hpgen 8 systems look here from page 3 , watch the videos, same issue as you have? with asrock system , i managed it with lowering memory from 4 to 2 with hpgen 8, i totally switch over to esx, with another sata controller , read that topic , everything is there

well, i started always with a baremetal system, always used an SSD to install DSM and apps, later on , always plugged in the extra SATA disks for files and backup now, i started with esxi, created also an virtual disk on my ssd datastore now, installed DSM, did some basic setup, when everything was finished, i plugged in my other disks after i booted, my dsm started up, BUT with the configuration of my old system so am i correct that the configuration/settings of DSM is saved on every disk? am i also correct that DSM is installled and published on all disks, if you plugin more disk? in case of failure of a disk, so synology still boots? so , how can i tell my new configuration in ESX, to always take the config of the new SSD disk, and NOT take the config of the plugged disk later on? because , i am now still at 5.2, if i start clean in esxi, with a new VM, and start with 6.1, if i then plugin my disks, maybe it strats again loading 5.2 ... thnx i hope you understand my question

hi pigr8, recieved my new sata controller with asm1061 chip everything working now as expected! thnx all

to all, i found another way to make it work on my hp gen 8 bought a 2 sata controller with asmedia chipset (marevell doesnt work, not compatible with vt-d) http://www.sybausa.com/index.php?route=product/product&path=64_77_85&product_id=151 installed esxi on a microsim card (on the mainboard) boot esxi from microsd attached 1 ssd drive to that asmedia sata controller, so my datatstore in on that ssd passthrough the whole cougar controller with 4 bay no issues now anymore, copy is working perfect! and i have the smart status now visible in synology me happy

Hi, yes, that's also a bug, but resolved in 6.5 update 1 , but that was an other story, that bug was more like that the speeds were not faster then 60 MB / sec... The bug we have is that it starts at 110 , but drops to 0 and even crashes... That's something else... I resolved it on my ASRock from changing 4 GB ram to 2, but on my gen8 it didn't help.. Also to be sure, I tried older esxi like 5.5, also same story, so it has nothing to do with hpsva driver... Tried all that stuff also

Normally you notice it in 15 sec