Jump to content
XPEnology Community

iLab

Transition Member
  • Posts

    7
  • Joined

  • Last visited

Everything posted by iLab

  1. Hm, strange, I can't get rid of quoting. I didn't want to quote anybody. Anyway. I've got a DS3615 VM running on VMWare ESX 6.7 (host is an old Fujitsu Siemens 1U machine). Attached to that is a supermicro SAS-shelf (via hostbus-adapter) with 45 disks to play with. I can easily passthrough SAS-drives to a FreeNAS-VM via scsi-controlers. Doing the same to the virtual DSM is way more tricky. What I managed to do consistently is attach a total of 22 disks (11 disks per SATA-controler). I can build one or two storage pools, make volumes, it creates everything very fastly (building two 18TB volumes was done overnight). But as soon as I reboot, everything is lost and I get to the standard :5000 page that tells me to reinstall DSM. Passing through a smaller amount of disks with only one additional controler is quite persistent with e.g. 3 disks. Serial out-errors are (only copying error-lines): - linuxrc.syno failed on 2 - /etc/rc: /etc/rc: line 108: line 108: /usr/syno/bin/synodiskpathparse: not foundawk: not found - rc: Failed to parse partition sdag2 - :: Loading module r8168 ... [FAILED] - :: Loading module jme ... [FAILED] - :: Loading module cnic ... [FAILED] - :: Loading module r8168 ... [FAILED] - :: Loading module r8169 ... [FAILED] - Can not detect ADT device, Retry: 1... - Can not detect ADT device, Retry: 2... - Can not detect ADT device, Retry: 3... I've also tried convincing it that 12 drives per controller is not the upper limit ( ) but that left me with a constantly recovering VM. All this mucking about takes so much time as ever time I try again, I have to passthrough the drives to the FreeNAS-VM to delete them. If I leave that out, the Syno-VM will always try to recover because the disks had been formatted through DSM. What I actually want to achieve is using the storage shelf in some way to hyperbackup to it. I would buy an actual small synology if I could achieve that through mounting storage (let's say hosted through FreeNAS) through NFS (which won't work, Hyperbackup Vault can't use that as destination) or iSCSI (which is also difficult to achieve as the Synos are not meant to be on the receiving end of iSCSI). I'm about to give up and try Hyperbackup through rSync-compatible, but that needs to be encrypted and so far, I've not been able to make that work.
  2. As for networking in ESXi: It all depends on how complex your network environment is. I'll just assume you have a single simple subnet (/24), then ESX makes a virtual switch and virtually connects your VMs to it. The IP-Addresses still come from your router, as if you'd connect a physical device to your network. Ideally, you'd create a DHCP-reservation for the MAC-address of the VM on the router so the virtual DSM always gets the same IP and also gets the IP you'd like it to have, without having to fiddle with it in the networking section of the DSM
  3. Dear JJJL, that is exactly the problem. Now you have two hosts with the same MAC-address, one physical and one virtual. ESX should not allow this, imho, but that's on another page. Shut down your vDSM and give it a MAC-address you generate, e.g. from here: https://jsfiddle.net/7Lorpu77/ Don't forget to edit the syslinux.cfg, not just change the mac-address in ESX Cheers and good luck
  4. You need to add a second SATA controller first
  5. thanks, @hpk, I finally made it work. I redownloaded everything and tried again from scratch. Seems like I had boggled up the .img File somehow. Now it's running again! Now to get those VLANs up to isolate the test-environment for AD-testing and I'm good. Happy times. Thanks to everyone for chiming in!
  6. I have the same trouble and it makes no difference if I use only one, two or three drives
×
×
  • Create New...