kazuni

Also note that the internal SATAs do not work if you have the 12-bay model of the r510 with h200/h310 cards.

I got it all working, andy. I also am running a R510 with all 14 bays (12x 3.5s and 2x2.5s internal) working with onboard broadcom nic as well as my connectx-2 10Gbe as well. 1) make sure you are using 1.02b 2) make sure you are going only up to 6.1.7 update 2. Do not go into 6.2 3) download the extra.lzma that IG-88 made in the loader extra section of this forum 4) follow instructions to load the extra.lzma into the 2nd partition (30MB) of the synoboot.img You should be able to boot and install just fine with all that done.

Works for me. But you need to perform a progressive update. Meaning, 1) You need a synoboot.img that's never been installed over/touched by DSM install (the one you wrote to your USB or the ESXI datastore, after you modified the serial) *****If you had already attempted any types of install or reconfigure on that usb/synoinfo.img, it is already useless, please note***** 2) You need to use the older PAT file, preferrably the one specified in your Synology Assistant indicated version (in this case, 6.2.x if you use 1.03b) 3) after the initial install is completed and initial setup is completed THEN you install 6.2.x. Through this method it always works for me, whether in ESXi or baremetal.

Xeon X5670/L5640 (Nehalem EP) works fine (DSM 6.1.7). Loader: 1.02b Platform: DS3617xs Hardware: Dell PowerEdge R510/610, baremetal Baremetal mode works on 6.1.7u2 pat

Xeon X5670/L5640 (Nehalem EP) works fine (DSM 6.1.7).  Loader: 1.02b Platform: DS3617 Hardware: Dell PowerEdge R510/610, esxi. ESXi with vmxnet works on 6.1.7 pat and 6.7u1 esxi.

Xeon X5670/L5640 (Nehalem EP) works fine (DSM 6.2.1). Loader: 1.03b Platform: DS3615 and DS3617 Hardware: Dell PowerEdge R510/610, esxi. #### DSM 6.2.1 - Successful with E1000E and BIOS.

Were you able to enable the debug serial bridge to ? if so, can I pm you so that i can set up and see dmesg... thanks!

Much, much appreciated. I will do so on my own time to do the compilation too, because I wanted to also passthru a Connectx-2/3/4 to the PowerEdge server I have. The built in Broadcom NetXtreme II s on the server (R510/610/710s) do not work with compiled drivers as they require a special boot process that requires an intel NIC being booted up first, and also a certain version of the Firmware, amongst other things.

If you read my threads I was one of the first few that made 1.04B work on esxi. I've read enough to know that it's not natively going to work, but have you heard of loading extra.lzma to make non-standards to work? Precisely, if people adds certified 10Gbe NICs they would on a real DS environment, so I am asking if anyone had successfully injected card drivers that works (like the works of IG-88 for example).

Has anyone successfuly connected a vmxnet3 and make it functional in a DSM 6.2.1 environment? I've done the precautions of adding an extra mac (valid synology mac/serial), vmxnet3 matching mac, and yet it isn't shown up after boot (i have a e1000e as primary)

- Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 Update 1 - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: HW - Baremetal - QNAP TS-853A - Additional comments: Works fine.. No problem updating. All 4 LAN works (Intel)

- Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 Update 1 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: HW - Baremetal - H97M-ITX/ac - Additional comments: Works fine.. No problem updating. Both LAN works (Realtek/Intel)

Wondering if it is possible to boot up a 1.04b config via esxi on the older westmere harware. 1.03b bios works on it just fine (with DS3615/7 bios boot and updated successfully to 6.2.1) using E1000E. Serial debug doesn't work as 1.04b seems to not poll any output at all... so I can't really debug much.

Hide the partition via sata0:20or above.

if you havent' modified the synoboot.img, the common mac Jun will use is 00:11:32:12:34:56 afaicr.

Also, when you boot up, hang the pc to bios and check if the boot order is correct

They work fine. The only things so far that does not work with valid serials and MACs are Synology Quickconnect, Package purchases and Synology.me DDNS.

post your .conf?

serial doesn't report anything now... could it be that jun disabled serial piping ?

For some reason the app never worked for me.. just no-warning crashed. The only one that still works for me is v1.31...

That is the correct size. After all Synology requires a couple GBs of overheads for OS related settings and partitions.

I have the same machine. three things. 1) make sure your USB stick's VID and PID is correct 2) make sure your boot device is set to AHCI 3) use UEFI on 1.04, BIOS on 1.03a/b

Correct. 1.04b (which only works with 918+) works with UEFI and VMXNET3.

Please use this as the base settings. Items highlighted in red are important.

how many disk do you have?