Jump to content
XPEnology Community

captainfred

Member
 View Profile  See their activity

  • Posts

    67

  • Joined

  • Last visited

 Content Type 

Posts posted by captainfred

    TCRP on ESXi Shutdown/Reboot

    in General Questions

    Posted

    I'm running the following hardware and software configuration: 

      

    HP ProLiant MicroServer Gen8
Intel Xeon CPU E31260L @ 2.40GHz
ESXi 7.0.3g (Build 20328353)
Hard Drives via SATA AHCI Controller passthrough to TCRP VM
tinycore-redpill.v0.9.3.0 withfriend
DSM 7.1.1-42962 Update 2
DS3617xs
open-vm-tools-12_broadwell-7.0_12.1.0-1

     

    When I attempt to reboot or shutdown the TCRP VM via ESXi, it doesn't work - I forgot to include the ACPI Optional Driver Extension, is that whats required to fix this? 

     

    However, now I've already done the build process of the loader and installed it all, how do I add the ACPI Optional Driver Extension afterwards?

     

    I think I need to use this command but thats before the build process so not sure how to go about it now:
    ./rploader.sh ext ds3617xs-7.1.1-42962 add https://raw.githubusercontent.com/pocopico/rp-ext/master/redpill-acpid/rpext-index.json

     

    Or is this an vmtools issue? ESXi says vmtools is installed and supported. If there is a newer than the one I found above I can't seem to find it...

     

    Minor question... when I click release notes in the update and restore menu in control panel it tries to go to http://example.com/null.xml?model=DS3617xs&update_version=42962-2 is this a Synology bug?

     

    Thanks in advance

    Strange outgoing connections from Synology

    in General Questions

    Posted · Edited by captainfred

    Hi, I've noticed using my router that sometimes there is some strange outgoing connections from my Synology to external IPs.

     

    It is definitely not open incoming, no ports are forwarded to it, so these are outgoing connections to external IPs destination port 23949 which is strange because its an unassigned port.

     

    These IPs according to ipinfo are mobile network ranges so that also seems strange to me.

     

    How can I tell what process is establishing these connections on Synology?

     

    I blocked one on my router a week or so ago and now there is another its connected to!

     

    Thanks

     

    DSM 3617-6, ESX, Microserver Gen8 - Post install woes

    in DSM 6.x

    Posted

    Hi R0bb0, I have almost exact same setup as you apart from the HP RAID card. 

     

    How did you work out the DiskIdxMap=0C0005 and SataPortMap=152 ?

     

    Also if you a passing through the "onboard" controller Cougar Point AHCI, just like I do, what do you use for the ESXi datastore to store the VM files for Xpenology?

     

    Fyi, I passthrough the the "onboard" controller Cougar Point AHCI for the 4 x 3.5" Drives and 1 x SSD Cache on the SATA port onboard and have a PCIe SATA card for SSD datastore for ESXi 

     

    Thanks

    Explanation of settings/lines in grub.cfg

    in Answered Questions

    Posted

    Is there a detailed list of all the settings/lines in grub.cfg what they do and what the options are?

     

    In particular these lines:

     

    Quote

    set common_args_3617='syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3617xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_port_thaw=1'

     

    set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1 SasIdxMap=0'

     

    Thanks

    NVMe optimization & baremetal to ESXi report

    in DSM 6.x

    Posted

    I have tried this, added SCSI Controller as LSI Logic SAS, setup the RDMs as pRDM in ESXi 6.5 but DSM doesn't then see the drives at all. It only seems to see them when they are on the SATA Controller which SMART obviously doesn't work for.

     

    What disk mode did you use?

    And which version of DSM?

    constant Smart temp read errors in var/messages how to eliminate

    in Software Modding

    Posted

    On 6/28/2018 at 12:25 PM, gits68 said:

    here is another, at boot, I'll reconfigure syslog-ng to drop thoses error messages :

      

    
b='\033[34m' # setaf 4
y='\033[33m' # setaf 3
g='\033[32m' # setaf 2
r='\033[31m' # setaf 1
w='\033[m' # sgr0
tab=${tab:-$(printf '\t')}
ws="[ ${tab}]"
foo() { file=$1; tag=$1; echo -n "${tag} ..."; }
bar() { eval "$@" && echo -e " ${b}updated${w}" || echo -e " ${r}failure${w}"; }
foobar() {
        foo "$1"
        if eval "$2"; then
                echo -e " ${g}success${w}"
        else
                eval "$3"
                bar "${4:-$2}"
        fi
}

case $(/bin/uname -u) in *cedarview*) ;; *) # xpenology
restart=0
foobar  /etc/syslog-ng/patterndb.d/smart.conf \
        '[ -f "${file}" ]' \
        'cat > "${file}"; restart=1' << EOF
filter f_smart_failed { (program("synostoraged") or program("sk") or program("SystemInfo.cgi")) and match("^(disk|[Ss]mart).*[Ff]ail" value("MESSAGE")) };
EOF
foobar  /etc/syslog-ng/patterndb.d/include/not2msg/smart \
        '[ -f "${file}" ]' \
        'cat > "${file}"; restart=1' << EOF
and not filter(f_smart_failed)
EOF
[ ${restart} = 1 ] && killall -1 syslog-ng
esac

    How do I use that? 
     

     

    Tutorial: How to access DSM's Data & System partitions

    in Tutorials and Guides

    Posted

    I was looking at this because I had the thought of using clonezilla to clone the system partition before a DSM update then I have an easy way to rollback in the case of a failure or bricked installation.

     

    So looking at all the partitions, I assume sdb1, sdc1, sdd1 etc is the system partition in my system here? The 2.4G partition on each drive basically?

     

    I've only got 1 volume across 4 x 5TB drives so why do I have a 1.8TB and 931GB partition on every drive?

     

    Whats the 2GB partition for?

     

    Thanks

     

    Partitions.thumb.JPG.3a87a4725bef65ba47a3af952158a582.JPG

    DSM 6.2 Loader

    in Loaders

    Posted

    On 9/1/2018 at 10:37 PM, Tibag said:

     

    So I just spent 4 hours trying to get it back to work. I ended up trying something like 

    But I can't get my Syno to be on the network with 1.03b. I've just tried again:

    • 1.02b fresh image: I can find the NAS via Assistant 
    • 1.03c fresh image: I can't find the NAS, even checked my rooter and it doesn't give it an IP. I checked the MAC matched on grub file and it does. 

    I am running ESXI 6 on an HP N54L. It's really odd as I had the feeling it worked on my very first attempt. 

     

    I am maybe doing something wrong but it seems that bootloader is not working on a setup like mine. I now have to reinstall 6.1... 😝

     

     

    1.03c??  Thought we were only on 1.03b?

×
×
  • Create New...