alese

- Hardware: HP Microserver Gen8, Intel i5-3470T. 16GB RAM, Fujitsu D2607 (crossflashed to LSI 2008 HBA), HPE ESXI 6.7.0 - VM1 (Testsystem for updates, only ESXI disks) - Outcome of the update: SUCCESFUL (after changing from IDE to SATA of the disks) - DSM version prior update: 6.1.7 Update 2 with Jun's loader v1.02b - Loader version and model: Jun's Loader v1.03b - DS3615 - Using custom extra.lzma: NO - VM2 (4 disks over LSI 2008 pci pass-through, no esxi disk) - Update: UNSUCCESSFUL - New installation: UNSUCCESSFUL / 2nd time SUCCESSFUL - DSM version prior update: 6.1.7 Update 2 with Jun's loader v1.02b with extra.lzma - Loader version and model: Jun's Loader v1.03b - DS3615 - Using custom extra.lzma: YES (integrated mpt2sas and e1000e from Test-VM with DSM6.2-23739 update 2) - Additional info: after update failed, trying to do a fresh installation over old 6.1.7, which failed also with Error 13, I freshly installed 6.1.7 again, then added a esxi disk and tried to do a fresh installation of 6.2. This time it worked. All disks are there. Don't know what the problem with old 6.1.7 installation was.

I tried to compile the mpt2sas module for my LSI 2008 (checked in DSM6.1.7) and also intel e1000e but now I always get an IP of 169.254.x.y. Don't know what the problem is. Used the 22259branch for bromolow and the DSM 6.2 toolchain for bromolow. Something happens on the disks, cause I alway have to recover my DSm6.1.7 when going back to 1.02b loader.

Make sure the synoboot.vmdk is on SATA controller and not on IDE controller. It works with IDE controller on 6.1.7 but not on 6.2. That was my problem when I had no network connection. Look at my config for my test-vm which is running 6.2 with upgrade from 6.1.7

I think the harddrives are there, cause else I won't get info in the update screen when using the new loader. I don't use a vm-drive. 4 Physical drives directly with pass-through. So the normal partitioning from synology on them. The synoboot.vmdk is from 1.02a(?). I only change the synoboot.img in the vm. In my test-vm with vm-drive it works. Maybe the missing extra.lzma with additional modules I use on 6.1.7 are the problem so that the pass through don't work like expected? I think the mptsas or mpt2sas driver is missing. I think I have to wait for additional drivers for 3615. I tried to add a virtual serial port to check, but I cannot connect. Connection always refused. Sorry for german in the pictures. But I think the needed information can be read.

Hi all, I have a microserver gen8 with i5-3470t and 16gb ram, esxi 6.7.0 and LSI2008 (corss flashed Fujitsu D2607) with pci pass through where all my data and the system is on and it's working with 6.1. I updated the loader to 1.03b and made the changes for serial and mac (same as for 6.1). The old system is found, but now I get the Error 13 when I try to install the 6.2 pat file. What could be the problem? Has somebody a working esxi with pci pass through? When I put back the old loader, all works well again. Greets Alex

Hi, can you please provide a img for Non-UEFI systems? I still use old hardware where I need a mbr partition scheme on the usb stick. The 2.2 img is GPT based and so I cannot boot from it, because it cannot find the partitions. Thanks AlesE