autohintbot Posted August 11, 2018 Share #226 Posted August 11, 2018 12 hours ago, tdutrieux said: Hi, I experience one small problem. I'm on ESXi6.5 with synoboot as SATA0:0 and a virtualdisk as SCSI0:0 The system bootup and seems to work fine. The only problem is that I don't have a drive 1, and the virtual disk shows as drive 2. BTW, the synoboot disk isn't shown. I've tried with both 3615 and 3617. Anybody experiencing that ? and solved that ? Thanks, TitiD Are you using the ESXi option on the boot menu? It's only shown for a second or two by default. Quote Link to comment Share on other sites More sharing options...
pacemaker Posted August 12, 2018 Share #227 Posted August 12, 2018 Hi all, would anyone be able to take a look at this topic and provide any help? Thanks! Quote Link to comment Share on other sites More sharing options...
sunny5227322 Posted August 12, 2018 Share #228 Posted August 12, 2018 (edited) On 8/2/2018 at 4:46 AM, dan1j3l said: @jun No luck for me, tried both loaders ds3615 and ds3617. Even with serial console there is nothing past grub selection screen. Both previous versions (6.1) are working fine. Hardware: MSI N3150I Eco (Intel Celeron N3150, with two SATAIII ports), 4Gb RAM, 3Tb HDD WD Green. Also tried loader for ds918+ but there is KP after installation because board has only two SATA ports (syno_ahci_disk_led_enable error). Hello, my hardware is also N3150I ECO now using DS916+ 1.02b loader It is also not working properly. After installing the 6.1.x system pat, it cannot be started! Can you share your modified loader? Thank you! Edited August 12, 2018 by sunny5227322 Quote Link to comment Share on other sites More sharing options...
sunny5227322 Posted August 12, 2018 Share #229 Posted August 12, 2018 (edited) Hello @jun, the motherboard I use is N3150I ECO. A friend said that it is not embedded in Intel P-State driver. Now it is tested from loader 1.02b to the latest 1.03b. After installing the system pat, the DSM could not be found and tested. Bios has also set up a possible combination. Can I integrate the Intel P-State driver under the latest system? Or inform the integration method, thank you! Edited August 12, 2018 by sunny5227322 Quote Link to comment Share on other sites More sharing options...
tdutrieux Posted August 12, 2018 Share #230 Posted August 12, 2018 9 hours ago, autohintbot said: Are you using the ESXi option on the boot menu? It's only shown for a second or two by default. Yes, fore sure ! I forgot to mention... Regards, TitiD Quote Link to comment Share on other sites More sharing options...
mirekmal Posted August 12, 2018 Share #231 Posted August 12, 2018 21 hours ago, tdutrieux said: Hi, I experience one small problem. I'm on ESXi6.5 with synoboot as SATA0:0 and a virtualdisk as SCSI0:0 The system bootup and seems to work fine. The only problem is that I don't have a drive 1, and the virtual disk shows as drive 2. BTW, the synoboot disk isn't shown. I've tried with both 3615 and 3617. Anybody experiencing that ? and solved that ? Thanks, TitiD Have you played somehow with HDD ontrollers configuration via grub.cfg or synoinfo.conf? Such change could cause, eventually, one port controller being visible to DSM as first disk slot... Quote Link to comment Share on other sites More sharing options...
tdutrieux Posted August 12, 2018 Share #232 Posted August 12, 2018 19 minutes ago, mirekmal said: Have you played somehow with HDD ontrollers configuration via grub.cfg or synoinfo.conf? Such change could cause, eventually, one port controller being visible to DSM as first disk slot... Hello, If I'm correct, both files are located on the synoboot image, right ? I didn't change anything on the synoboot, just using the downloaded files right away. Regards, TitiD Quote Link to comment Share on other sites More sharing options...
tdutrieux Posted August 12, 2018 Share #233 Posted August 12, 2018 1 minute ago, tdutrieux said: Hello, If I'm correct, both files are located on the synoboot image, right ? I didn't change anything on the synoboot, just using the downloaded files right away. Regards, TitiD Maybe could somebody make an OVF for ESXi that's working well for testing ? Thanks ! TitiD Quote Link to comment Share on other sites More sharing options...
Mouth Posted August 12, 2018 Share #234 Posted August 12, 2018 On 8/6/2018 at 9:04 AM, macguru8 said: HP Microserver Gen7 N54L works fine. Did a migration from DSM 6.1 DS3617 to 6.2 DS3617. Nice, thanks! Means my N36L should work fine too. Quote Link to comment Share on other sites More sharing options...
gold8009 Posted August 12, 2018 Share #235 Posted August 12, 2018 (edited) Loader: Jun's loader 1.03B. Network: RTL8111 CPU: Core i7 8700T Memory: 16GB ESXI6.7 DS3615 1.03b SATA Drive: ASM1062 Passthrough Problem: Find the "NAS" host and can't find the hard drive on "ASM1062". 1.02b ds3615 is good. Doubt 1.03b "extra.lzma" does not have "ASM1062" driver Edited August 12, 2018 by Dfds Translated to english Quote Link to comment Share on other sites More sharing options...
pacemaker Posted August 12, 2018 Share #236 Posted August 12, 2018 Hi all, for everyone with issues concerning network and services after upgrade: Try deleting the .xpenoboot folder locate in the root folder (if present). Quote Link to comment Share on other sites More sharing options...
Dfds Posted August 12, 2018 Share #237 Posted August 12, 2018 @gold8009 I have translated your post this time but please ensure that future posts are in English 39 minutes ago, gold8009 said: Loader: Jun's loader 1.03B. Network: RTL8111 CPU: Core i7 8700T Memory: 16GB ESXI6.7 DS3615 1.03b SATA Drive: ASM1062 Passthrough Problem: Find the "NAS" host and can't find the hard drive on "ASM1062". 1.02b ds3615 is good. Doubt 1.03b "extra.lzma" does not have "ASM1062" driver Quote Link to comment Share on other sites More sharing options...
marigo Posted August 12, 2018 Share #238 Posted August 12, 2018 Successfully migrated my Proxmox VM from 6.2 (918+) to 6.2 (DS3615XS) with the new (1.03b) loader! Great work Jun! Quote Link to comment Share on other sites More sharing options...
andrey00188 Posted August 12, 2018 Share #239 Posted August 12, 2018 (edited) Hуllo everyone! Tell me, please, how to update me with 6.1 downloader 1.02b to 6.2 downloader 1.03b. Install in ESXi I tried simply to replace the bootloader, but the machine willn't get ip (( Edited August 12, 2018 by andrey00188 Quote Link to comment Share on other sites More sharing options...
Ikyo Posted August 13, 2018 Share #240 Posted August 13, 2018 8 hours ago, andrey00188 said: Hуllo everyone! Tell me, please, how to update me with 6.1 downloader 1.02b to 6.2 downloader 1.03b. Install in ESXi I tried simply to replace the bootloader, but the machine willn't get ip (( I haven't tried this yet, but I am going to guess you need to update the GRUB configuration to have the correct MAC1 address to match the ESXI configuration. Quote Link to comment Share on other sites More sharing options...
OzTechGeek Posted August 13, 2018 Share #241 Posted August 13, 2018 On 8/11/2018 at 4:30 AM, tdutrieux said: Hi, I experience one small problem. I'm on ESXi6.5 with synoboot as SATA0:0 and a virtualdisk as SCSI0:0 The system bootup and seems to work fine. The only problem is that I don't have a drive 1, and the virtual disk shows as drive 2. BTW, the synoboot disk isn't shown. I've tried with both 3615 and 3617. Anybody experiencing that ? and solved that ? Thanks, TitiD @tdutrieux I have spent the last 10 hours trying to solve the same problem and other issues related to SAS controllers in ESXi 6.7, for the problem you are having add another SATA controller to your VM "SATA Controller 1" then assign your DSM disks to that controller SATA1:0, SATA1:1 etc and remove the "SCSI Controller 0" from the VM. This worked for me, I am now able to add VMDK to SATA1:x and have them in any slot and they will show correctly in DSM in the correct disk slot in "Stroage Manager". SAS Controller are a whole other issue. Quote Link to comment Share on other sites More sharing options...
OzTechGeek Posted August 13, 2018 Share #242 Posted August 13, 2018 For the last 10 hours I've been struggling with getting any SAS controller (LSI Logic SAS or VMware Paravirtual) to work correctly with ESXI 6.7 and DS3617 1.03b, here is my current VM config: SATA Controller 0 : SATA(0:0) = synoboot.vmdk SATA Controller 1 : SATA(1:0) = Test0.vmdk (Shows in "Stroage Manager as Disk 9) = Correct SATA Controller 1 : SATA(1:3) = Test3.vmdk (Shows in "Stroage Manager as Disk 12) = Correct SCSI Controller 0 : SCSI(0:0) = SAS0.vmdk (Shows in "Stroage Manager as Disk 6) = WRONG Over the last 10 hours I have tried different grub.cfg changes but here is my current config: set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C0801 SataPortMap=148 SasIdxMap=0' DiskIdxMap=0C0801 = Starting Disk in DSM for each controllers: 0C= 1st controller SATA0 start at "Disk 13" in DSM 08= 2nd controller SATA1 start at "Disk 9" in DSM 00= 3rd controller SCSI0 start at "Disk 1" in DSM = NOT WORKING SataPortMap=148 = Ports Per Controller 1 = 1 Port SATA0:0 synoboot.vmdk DSM Disk 13 4 = 4 Ports SATA1:0,1,2,3 DSM DIsk 9, 10, 11, 12 8 = 8 Port SCSI0:0-7 DSM Disk 1 -8 The problem is the SCSI/SAS disk SAS0.vmdk never starts at DISM Disk 1 it's currently DSM Disk 6, during some initally testing it was coming in a DSM Disk 2 but now it's Disk 6. I noticed the following in the serial console for the SAS disk: :: Loading module mptsas[ 2.087825] sd 5:0:0:0: [sdf] Assuming drive cache: write through [ 2.089707] sd 5:0:0:0: [sdf] Assuming drive cache: write through [ 2.091766] sd 5:0:0:0: [sdf] Assuming drive cache: write through ... [ OK ] Where is sda to sde? I only have 1 SCSI disk currently assigned in the VM SAS0.vmdk on port SCSI(0:0). I have tried different settings for "SasIdxMap=" such as "SasIdxMap=0xFFFFFFFA" (-6) and "SasIdxMap=0xFFFFFFFF" (-1) but the SAS0.vmdk still shows in DSM in Disk 6. not matter what I do I cannot get the SCSI/SAS disk to show in Disk 1 in DSM. Also noticed the following from "cat /proc/cmdline" no mention of any "SasIdxMap" setting if it makes a differeance: cat /proc/cmdline syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3617xs vender_format_version=2 console=ttyS0,115200n8 withefi quiet root=/dev/md0 sn=<removed> mac1=<removed> netif_num=1 synoboot_satadom=1 DiskIdxMap=0C0800 SataPortMap=148 I'm currently testing this in a VM in this configuration becuase my real production box has this same configuration but the SAS/SCSI controller is actually a LSI 9207-8e in pass-through mode, but I wanted to validate and test 6.2 before I migrate to 6.2, but so far no luck with the SCSI/SAS issue. The only thing I have not tested yet and just thought of and wonder if it would make a differance is the "Guest OS Version" of the VM I currently have it set to "Other 3.x Linux 64-bit" since DS3617 is only running the 3.x Kernel that's why I chose it. Anybody else having trouble/issues getting the SAS/SCSI controllers in a ESXi 6.7 VM to number/show correctly or is it just me or did I miss some configuration setting somehwere? BTW during this whole time trying to get it working I must have read this thread of 10 pages at least 8 times from start to finish looking for something I may have missed or a catch/gotcha Thoughts/Suggestions? Quote Link to comment Share on other sites More sharing options...
kula Posted August 13, 2018 Share #243 Posted August 13, 2018 Hi all! I'm not that lucky. I've tried upgrading from 6.1 to 6.2 without success. I get the File currupt (13) error during both migration and re-install with md5 checked pat-file. Same HW bare metal Supermicro itx board with Atom 2550 and onboard quad intel nic running fine before. I've downloaded Jun's 1.03b loader and updated the vid/pid/sn/mac. Everything else is untouched. For troubleshooting I noticed that telnet isn't open when the box boots but after the installation error I can use telnet and I've tried to get some logs. Only somewhat helpful is /var/log/messages that looks like this: Aug 12 22:05:03 install.cgi: Remove /tmpData/upd@te...cmd=[/bin/rm -rf /tmpData/upd@te > /dev/null 2>&1] Aug 12 22:05:03 install.cgi: Create /tmpData/upd@te...cmd=[/bin/mkdir -p /tmpData/upd@te > /dev/null 2>&1] Aug 12 22:05:03 install.cgi: Untar /tmpData/upd@te.pat...cmd=[/bin/tar xpf "/tmpData/upd@te.pat" -C /tmpData/upd@te > /dev/null 2>&1] Aug 12 22:05:04 install.cgi: ErrFHOSTCheckUpgradeFile: Remove /tmpData/upd@te.pat... Aug 12 22:05:04 install.cgi: Verify codesign of [/tmpData/upd@te]... Aug 12 22:05:07 install.cgi: Verify checksum of [/tmpData/upd@te]... Aug 12 22:05:09 install.cgi: Pass checksum of /tmpData/upd@te... Aug 12 22:05:09 updater: updater.c:6006 Start of the updater... Aug 12 22:05:09 updater: updater.c:2812 orgBuildNumber = 23739, newBuildNumber=23739 Aug 12 22:05:09 updater: updater_util.c:52 fail to read company in /tmpRoot//etc.defaults/synoinfo.conf Aug 12 22:05:09 updater: file_check_key_value.c:25 SLIBCFileGetKeyValue(runccc) failed [0x0900 file_get_key_value.c:29] Aug 12 22:05:09 updater: updater.c:6272 ==== Start flash update ==== Aug 12 22:05:09 updater: updater.c:6276 This is X86 platform Aug 12 22:05:09 updater: boot/boot_lock.c(227): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:2) Aug 12 22:05:09 updater: updater.c:5816 Failed to mount boot partition Aug 12 22:05:09 updater: updater.c:2711 No need to reset reason for v.23739 Aug 12 22:05:09 updater: updater.c:6810 Failed to accomplish the update! (errno = 21) Aug 12 22:05:09 install.cgi: ninstaller.c:1822 Executing [/tmpData/upd@te/updater -v /tmpData > /dev/null 2>&1] error[21] Aug 12 22:05:13 install.cgi: ninstaller.c:206 Mount partion /dev/md0 /tmpRoot Aug 12 22:05:13 install.cgi: ninstaller.c:1791 Moving updater for configuration upgrade...cmd=[/bin/mv -f /tmpData/upd@te/updater /tmpRoot/.updater > /dev/null 2>&1] Aug 12 22:05:13 install.cgi: ninstaller.c:235 umount partition /tmpRoot Aug 12 22:05:13 install.cgi: ErrFHOSTCleanPatchDirFile: After updating /tmpData/upd@te...cmd=[/bin/rm -rf /tmpData/upd@te > /dev/null 2>&1] Aug 12 22:05:13 install.cgi: ErrFHOSTCleanPatchDirFile: Remove /tmpData/upd@te.pat... Aug 12 22:05:13 install.cgi: ErrFHOSTDoUpgrade(2407): child process failed, retv=-21 Aug 12 22:05:13 install.cgi: ninstaller.c:2415(ErrFHOSTDoUpgrade) err=[-1] Aug 12 22:05:13 install.cgi: ninstaller.c:2424(ErrFHOSTDoUpgrade) retv=[-21] Aug 12 22:05:13 install.cgi: install.c:948 Upgrade by the manual patch fail. Aug 12 22:05:13 install.cgi: install.c:1263 Upgrade by the uploaded patch /tmpData/@autoupdate/upload.pat fail. The /dev/synoboot2 device doesn't exist so I'm note sure what that is. Any suggestions? Quote Link to comment Share on other sites More sharing options...
ZerOneX Posted August 13, 2018 Share #244 Posted August 13, 2018 thank you jun... gonna test it today Quote Link to comment Share on other sites More sharing options...
tdutrieux Posted August 13, 2018 Share #245 Posted August 13, 2018 11 hours ago, OzTechGeek said: @tdutrieux I have spent the last 10 hours trying to solve the same problem and other issues related to SAS controllers in ESXi 6.7, for the problem you are having add another SATA controller to your VM "SATA Controller 1" then assign your DSM disks to that controller SATA1:0, SATA1:1 etc and remove the "SCSI Controller 0" from the VM. This worked for me, I am now able to add VMDK to SATA1:x and have them in any slot and they will show correctly in DSM in the correct disk slot in "Stroage Manager". SAS Controller are a whole other issue. Hi, thanks for helping but still the same problem with this config : Quote Link to comment Share on other sites More sharing options...
OzTechGeek Posted August 13, 2018 Share #246 Posted August 13, 2018 Hi, thanks for helping but still the same problem with this config : Have you set “DiskIdxMap=0C00” in grub.cfg?Sent from my iPhone using Tapatalk Quote Link to comment Share on other sites More sharing options...
tdutrieux Posted August 13, 2018 Share #247 Posted August 13, 2018 53 minutes ago, OzTechGeek said: Have you set “DiskIdxMap=0C00” in grub.cfg? Sent from my iPhone using Tapatalk Hey, the trick works ! Thanks for the help. Regards, TitiD Quote Link to comment Share on other sites More sharing options...
nicoueron Posted August 14, 2018 Share #248 Posted August 14, 2018 For me it's OK on my N54L with VMWare ESXi 6.0.2. I have only needed to recreate a new virtual machine. The loader refuses to boot after select ESXi in the menu. I do not know why and the file wich map the serial port does not have any information anymore. But whith a new VM all it's OK! The upgrade has taken only 7 minutes and all my data seems to be ok Very good job @jun! Quote Link to comment Share on other sites More sharing options...
lubland Posted August 14, 2018 Share #249 Posted August 14, 2018 3 hours ago, nicoueron said: For me it's OK on my N54L with VMWare ESXi 6.0.2. I have only needed to recreate a new virtual machine. The loader refuses to boot after select ESXi in the menu. I do not know why and the file wich map the serial port does not have any information anymore. But whith a new VM all it's OK! The upgrade has taken only 7 minutes and all my data seems to be ok Very good job @jun! I have try the same but my DSM not start or contact on LAN. Can you share how you VM setup / config is? //L Quote Link to comment Share on other sites More sharing options...
nicoueron Posted August 14, 2018 Share #250 Posted August 14, 2018 Il y a 1 heure, lubland a dit : I have try the same but my DSM not start or contact on LAN. Can you share how you VM setup / config is? //L and if you want to deploy a OVF file you can try mine : https://file.niko44.fr/sharing/CAGHguOMW 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.