crkrr

Did some more trials on the maxdisks change. I set up a new VM under ESXi 6.5 as follows: - Downloaded 1.02b img file (ds3615), changed serial, copied the existing mac address to clipboard, didn't touch vid and pid - Converted the img to vmdk with StarWind V2V - Created new VM : new vmdk as boot drive + 8GB disk for testing, UEFI boot, OS: Linux other 64bit, hw version 13, set mac to manual and pasted the address from grub file - Boot with ESXi option, install latest DSM, reboot - Enable SSH change values in /etc.defaults/synoinfo.conf - Same issue on reboot, forces me to migrate after Does anyone here have their maxdisks increased under ESXi? How did you do it?

Hi Everyone! What is the correct way to increase the maximum number of drives? I am running korovi's ESXi template with an HBA passed through. Everything seems to work but I'm up against the disk limit and would like to increase. Tried asking around in the thread for the ovf, but it seems to be dead. The issue is if I ssh in and edit the synoinfo.conf file and reboot it thinks I moved my drives to a new DiskStation; it pulls a new address from the DHCP server and forces me to reinstall after which data and packages (and settings mostly) are intact but the max number of drives in Storage Manager is reset to 12. This is the config I'm trying: maxdisks 36 0000 0000 0000 1111 1111 0000 0000 0000 0000 0000 0000 0000 0000 0000 - esataportcfg 0000 0000 0011 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 - usbportcfg 0000 0000 0000 0000 0000 1111 1111 1111 1111 1111 1111 1111 1111 1111 - internalportcfg Thanks for any help!

Hi! Thanks so much to koroziv! After a failed update from DSM 6.0 to DSM 6.1, giving up on trying to restore I also failed to boot Jun's loader under ESXI to create a new VM. I was panicking for a while (have backups of important stuff, but would take forever to restore) this saved my ass, and was so easy to setup! After importing the ovf and vmdks I recreated my users and config everything is working great, but now I'm facing a different issue. I need to increase the max disks, trying to follow the idmedia guide on YouTube (going for 36 disks). The same guide worked perfectly with my previous install. However with this template after I edit the synoinfo.conf file and reboot, the VM pulls a new address via DHCP (I set a static one previously) and forces me to reinstall DSM. I can reinstall and my data, config and packages remain intact, but the max drives is reset to 12. This is what I'm doing: - ssh in to the VM deployed from koroziv's template - pull the synoinfo.conf file via scp to my destop - edit values following the idmedia guide - rename synoinfo.conf on the VM for backup - scp the edited file in place of the orignal - cat the contents to make confirm the new file is in the correct place and has new values - reboot via DSM web gui What is the "proper" way to increase max disks? Thanks for any help! /Config: Running the VM under ESXI 6.5 with 2 cores and 4GB RAM and a Dell RAID card flashed to HBA mode These are the values I'm trying: maxdisks 36 Binary: 0000 0000 0000 1111 1111 0000 0000 0000 0000 0000 0000 0000 0000 0000 - esataportcfg 0000 0000 0011 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 - usbportcfg 0000 0000 0000 0000 0000 1111 1111 1111 1111 1111 1111 1111 1111 1111 - internalportcfg Hex (writen to file): ff000000000 - esataportcfg 300000000000 - usbportcfg fffffffff - internalportcfg

At this point, I'm willing to give a Bitcoin tip/donation for some help. I have been flashing my dell h200 to various LSI 92118IT firmware (p07,p12,p16,p19,p20) and still cannot get it detected in DSM via PassThrough. When I test passthrough on FreeNAS, it detects it no problem and everything works. I am using a dell r710 with ESXi 6. I have also tried to flash the firmware with and without the bios. Does anyone have any suggestions of what I can try? Any CLI commands I can run to troubleshoot? Driver loading? Thanks in advance Hi. I tried a cross-flashed H310, if you look back at p42 I did not succeed. My conclusion was that 3rd party drivers are required to run them. I gave up on DSM 6 at that point. If you manage to find a solution, please let us know, I would be very interested.

Thanks, this explains a lot! I was under the impression that the LSI cards are natively supported. I'm using a Dell H310 flashed to LSI-9211i8i firmware. Is the LSI-9211i8i not supported, or did I wonk something with the flash? The card still does show up as a Dell HBA in esxi. Anyways, think I'll try running whatever the last "supported" Xpenology build if all else fails. BTW update 6.0.2-8451 gave me "Unknown error occurs (21)." as others already posted above.

Thanks for looking into it. This is my first foray into xpenology, plus I'm not too familiar with linux, don't know how the drivers are loaded. I also don't understand the difference between the "Install" and run options. After a lot of trial and error I found out the controller does work if booted to "install". If I then restart to "run" the first time setup screen comes up, my previously created account seems to be gone, but then I reboot to install and everything is there as before. I can create volumes, but not btrfs (immediete crash), and I'm a little uncomfortable running it with install as I don't see that being the intended way and do not understand the implications.

Hi, I used okitsme's Workstation files on page 7 (oktisme » 16 Jun 2016 11:33). Converted the vm with VMware standalone converter. I used hardware version 10 and changed the nic to 1000e before converting. No install, booted straight away with the run option, has been working since. There's a ready made one from haydibe I didn't notice until now, might be a more straightforward way, also on page 7.

DSM 6 running fine on esxi, used okitsme's hw10 workstation vmdks converted. Tested with sata virtual disks, btrfs raid 6, everything seems to work. Thank you so much for sharing this, I would have never been able do pull something like this off! I have two issues. One is the lack of shr support which I attribute to the DS3615xs pat. Anyone have a workaround? The bigger problem for me however is that the perc H310 card finally arrived, flashed it to LSI it firmware (following techmattr's guide) but it does not work with dsm. Have two disks connected for testing, passed the card to DSM but disks dont show. If I pass it to a Windows vm drives show and operate as expected. Do I have to take any additional steps to enable the card? One weird thing is that even though the flashing worked (confirmed multiple times to test my sanity) the card shows as a Dell in esxi.

If I understand correctly there are no "extra" drivers, so you can either only run on Synology supported parts or in a VM. My plan is to run DSM 6 on top of ESXi 6 with a RAID/HBA card passed through instead of rdm. I guess in this case the card might cause issues, as it has to be supported. I never owned a RAID card and have no experience. Or do these cards "abstract" the disks in a sense that they work without drivers? At the moment all my drives are on the motherboard SATA headers, mapped to a Windows Server 2012 VM. But all ports are filled up; I need to but can't expand further. This is what I am trying to replace and move away from Windows at the same time. It's a home setup mostly for backups and media and some tinkering, nothing critical. I'm looking to reduce the administration pain of Windows with DSM as it is more than enough for my needs. I just got a second hand Supermicro case with a SAS2 expander backplane and need to choose a card. I read good things about the IBM m1015 and the Dell H310 both crossflashed to LSI firmware. I’m leaning toward the Dell, since I can source it locally, while the IBM I can only find on ebay from Chinese sellers. Is it a smart idea to buy from one of the sellers from Chine/Hong Kong? I know there are many fake Intel NICs sold on ebay, don't want to run into such a thing with the HBA card. Would one of these work in the above configuration; passed through to the DSM 6 VM? tldr; Would a crossflashed IBM m1015 or a Dell h310 work if I passed it through to a DSM 6 VM on ESXi 6? Thanks for any help!