Jump to content
XPEnology Community


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

OzTechGeek's Achievements

Junior Member

Junior Member (2/7)



  1. Just an FYI, looks like Synology disabled/removed the ability to use "http://<dsm-ip-address>:5000/webman/start_telnet.cgi" in the 7.1-42661-1-NanoPacked update. Did a fresh install and got the below message. Also checked /usr/syno/synoman/webman/ and there is no longer a start_telnet.cgi file.
  2. @Pocopico and All I’m putting my list together of what extensions to add for a standard DS3622xs+ ESXI VM build and have come up with the following so far: # “ACPI” ./rploader.sh ext broadwellnk-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/main/redpill-acpid/rpext-index.json # “MPT3SAS” ./rploader.sh ext broadwellnk-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/main/mpt3sas/rpext-index.json # “PVSCSI” ./rploader.sh ext broadwellnk-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/main/vmw_pvscsi/rpext-index.json # “VMXNET3” ./rploader.sh ext broadwellnk-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/main/vmxnet3/rpext-index.json The one I’m not sure about is the “redpill-misc” I can find it in the “redpill-load” repo but not in the “rp-ext” repo, should it be in the “rp-ext” repo? (Just my OCD kicking in that’s all) ./rploader.sh ext broadwellnk-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/redpill-load/master/redpill-misc/rpext-index.json I’ve seen mention of “Telnet Extension” before, but when I check the “rp-ext” repo there are actually 2 listed, not sure which one to use or if it’s even needed Extension Name: "Early telnet start" Description : "Simple extension which starts telnet early at boot" https://raw.githubusercontent.com/pocopico/rp-ext/master/early-telnet/rpext-index.json Extension Name: "Early telnet start" Description : "Simple extension which starts telnet early at boot" https://raw.githubusercontent.com/pocopico/rp-ext/master/raspbi-pill/rpext-index.json Are there any extension that would be “good to have” on a build for troubleshooting or information purposes? Thanks
  3. @pocopico and All When adding extensions and doing a build, is there a command, file or folder to check to see what extensions have been added after running a “./rploader.sh build <platform>”. I would like to check/verify what extensions are added in TCRP after doing a build, either on a standard build or one where I’ve added extensions. Thanks
  4. @Pocopico and All I’m putting my documentation together for building my 2 new DS3622xs+ ESXI VM’s and had a question about extension URL’s. I noticed throughout this thread various URL’s been used in different forms, so is there a standard we should all use when using the “./rploader.sh ext <platform> add <url>”? Which is preferred long term: https://github.com/pocopico/rp-ext/blob/main/<extension>/rpext-index.json or https://raw.githubusercontent.com/pocopico/rp-ext/main/<extension>/rpext-index.json Thanks for all your hard work
  5. OzTechGeek

    DSM 6.2 Loader

    Still trying to figure out the SAS controller mapping issue, it's driving me crazy, it seems the "SataPortMap" setting is controlling the SAS address but according to what I have read it's not working how I thought, here is what I get with different settings: SataPortMap=1 :: Loading module mptsas[ 2.221996] sd 31:0:0:0: [sdaf] Assuming drive cache: write through [ 2.224469] sd 31:0:0:0: [sdaf] Assuming drive cache: write through [ 2.225998] sd 31:0:0:0: [sdaf] Assuming drive cache: write through ... [ OK ] SataPortMap=11 :: Loading module mptsas[ 2.101528] sd 2:0:0:0: [sdc] Assuming drive cache: write through [ 2.103279] sd 2:0:0:0: [sdc] Assuming drive cache: write through [ 2.105453] sd 2:0:0:0: [sdc] Assuming drive cache: write through ... [ OK ] SataPortMap=111 :: Loading module mptsas[ 2.100789] sd 2:0:0:0: [sdc] Assuming drive cache: write through [ 2.102862] sd 2:0:0:0: [sdc] Assuming drive cache: write through [ 2.104874] sd 2:0:0:0: [sdc] Assuming drive cache: write through ... [ OK ] SataPortMap=148 :: Loading module mptsas[ 2.085214] sd 5:0:0:0: [sdf] Assuming drive cache: write through [ 2.087088] sd 5:0:0:0: [sdf] Assuming drive cache: write through [ 2.089221] sd 5:0:0:0: [sdf] Assuming drive cache: write through ... [ OK ] "SataPortMap=1" SAS disk "sdaf" does not even appear in DSM "SataPortMap=111" puts the SAS disk "sdc" on Disk 2 in DSM "SataPortMap=148" puts the SAS disk "sdf" on Disk 6 in DSM I thought "SataPortMap=148" meant 1 Port on 1st Controller, 4 Ports on 2nd Controller and 8 Ports on 3rd Controller, but that not what that setting is doing, to me it looks like for the SAS controller it takes the first 2 nm,bers of "SataPortMap", adds them together to get the SCSI ID? and then adds 1 to that number to get the starting drive sdf? I don't know at this point I'm just grasping at straws trying to figure something out
  6. OzTechGeek

    DSM 6.2 Loader

    Have you set “DiskIdxMap=0C00” in grub.cfg? Sent from my iPhone using Tapatalk
  7. OzTechGeek

    DSM 6.2 Loader

    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?
  8. OzTechGeek

    DSM 6.2 Loader

    @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.
  9. So I solved my own problem FYI for anyone having the same issue: Make sure the "synoboot.vmdk" is set to a "Virtual Device Node: SATA controller 0 / SATA (0:0)" Once I did this the "Health Info" tab worked and now I also can see the "S.M.A.R.T Info" tab. Teaches me for building my VMX from scratch
  10. I am migrating over to DSM 6.1 with jun's loader and ESXi 6.5 and passing through a 9211-8i, but I noticed SMART info is not passing through. When I select "Storage Manager - Health Info" I get a "Not Available" message. Nothing shows in "Storage Manager - Logs" either. Strange thing is both "smartctl --info /dev/sdb" and "synodisk --info /dev/sdb" both connect and return the correct information for the 1 disk I'm testing. I did notice in "/var/log/messages" the following error every time I select "Storage Manager - Health Info": DS3615xs synoscgi_SYNO.Storage.CGI.Smart_1_get_health_info[19566]: disk/disk_current_health_get.c:46 SYNODiskXmlErrCtGet failed on /dev/sdb Wondering if I'm missing a setting or config change that will allow a LSI 9211-8i and pass-through to work correctly with DSM 6.1? Thoughts?
  11. For ESXi users, does anyone know how to change the Syno Boot VMDK from SATA 0:0 to another port? Wanted to set the boot drive to a different port so that in DSM the data drives show up a Port/Slot 1,2,3,4,5,6 etc. Right now disks start at Port/Slot 2. I tried moving the boot VMDK to other SATA ports and even IDE and SCSI 0;0, but the install fails. I might be missing something simple. Thanks for all the hard work and effort from @jun and others on this project
  12. Have Trust Level set to "Any Publisher", Patched 7.1-4152 loads fine, but license count still shows 2 Get these "Warnings" when patching:
  13. Gaendalf, Any chance you could upload 0.6 to mega.nz please? 0.6.1 does not work with 7.1-4152 or 7.2.2-4649. Thanks
  14. I apologize but English is my first and only language Tried a Google translate just in case I missed something, in case uploadduck.com was "code" for something else but I'm unable to download the file from http://uploadduck.com/SJ3 don't know if it's a location issue or if http://uploadduck.com/ no longer exists but is there a mirror available or could it be uploaded to mega.nz please?
  15. Does anyone know how to disable S.M.A.R.T monitoring in XPEonology? I'm running on ESXi 6.0 with RDM disks and the /var/log/message file is filling up with the following: SmartDataRead(108) read value /dev/sda fail disk_temperature_get.c:75 read value /dev/sda fail SmartFirmAndSerialRead(156) AtaSmartFirmAndSerialRead fail I do not need S.M.A.R.T monitoring within DSM since I'm running on an LSI card on ESXi with it's own monitoring. Any help would be greatly appreciated. Thanks
  • Create New...