Jump to content
XPEnology Community

lazygatto

Member
  • Posts

    15
  • Joined

  • Last visited

Posts posted by lazygatto

  1. As I understood there is no link with valid SN/MAC for Chat notifications to work. So no any of Synology services used for that.

    For me notifications work well only if using local accounts of DSM.

    If I switch for LDAP users in Chat App - then all notifications on mobile devices gone away :(

  2. I've recently annouce that my work on a kernel mode dynamic patcher in this post

    ....

     

    How to install:

     

    find the vid/pid of your usb drive

    Burn the image to the drive, optionally edit grub.cfg to set vid/pid and boot entry, OR

    connect monitor/keyboard/serial console to your Box.

    Press C during Grub boot menu to enter command line

    vid 0xXXXX
    pid 0xYYYY
    

    to configure pid and vid ("pid" and "vid" are command, and "XXXX", "YYYY" are you usb drive's vid,pid)

    (There are a few other options can be config this way, you can read grub.cfg to know more detail.)

    Press Esc to go back to boot menu

    Select baremeta/baremetal AMD entry, press enter to boot.

    If your encounter the "disk port disabled" error during installation, try the force install menu entry.

    if both option does not work, you have to fallback to SataPortMap method,

    type this line in grub command line, replace XX with appropriate value.

    append SataPortMap=XX

     

    11/2:

    as I promised, here is v1.01, download link is the same as v1.0

    This update contains nothing fancy, mainly for inner peace,

    Plus, I revert megaraid_sas mpt3sas to old version.

     

    It's not shining new now, the title is obsolete

    My HP Microserver Gen8 can't boot by U-disk burned in your loader v1.01 as your indicate above. It shows "Non system disk" but works well with 5.2 XPEnoboot_DS3615xs_5.2-5644.5 from this forum.

    As I known, Gen8 can't boot by UEFI mode. Any suggestions?

     

    update: The U-disk above was unstable and my Gen8 was updated to DSM 6.0.2 with new U-sidk by your loader v1.01. Thanks!

     

     

    This DSM loader can boot in UEFI AND in legacy (BIOS) mode as well.

  3. I Update whit Jun 1.0.1 and its working fine everything

     

    Just a quick question

     

    DSM 6.0.2-8451 Update 3 is available, someone know if its safe to update?

    Updated successfully 2 VMs on eSXI and Proxmox :wink:

  4. Нюансов особых нет.

    Из темы New loader берете из первого поста образ загрузчика.

    Для установки на голое железо разворачиваете образ на USB flash.

    Загружаетесь, через браузер ищете свой NAS, find.synology.com

    Ну и в режиме ручной установки устанавливаете pat файл последний на текущий момент (8451).

  5. BTW, how can i hide my IDE drive with loader from DSM?

    Adding

    set extra_args_3615='rmmod=ata_piix'

    doesn't work for me =(

     

    oops, good news is ata_piix works,

    bad news is seems not everyone loves it :smile:

    =) yeap.

    so is it possible to disable ata_piix?

     

    PS Thanks a lot for your work :wink:

  6. Епт. Как же я жду это. Ура

    Если кто скажет как все делать пошагово то это будет круто. И буду признателен. Переводчик мне такого напереводит

    Смотря куда ставить? На голую железку или в вирт. машину - от этого и инструкции будут разниться :wink:

  7. I've managed to install original 8451 pat in Proxmox VM with Arcao uefi-boot img. (Mount qcow2 file as USB, Boot in UEFI from USB).

    No error 13.

    But after install I stuck on upgrade for now =))

    Every time after reboot DSM shows me:

    We've detected that the hard drives of your current DS3615xs had been moved from a previous DS3615xs, and installing a newer DSM is required before continuing.
    Status: Upgrade required
    Firmware version: 6.0.2-8451
    DSM version: 6.0.2-8451
    

  8. For all KVM users, i did the following;

     

    hF1vEvs.png

     

    downloaded the latest 'jun img'-file

    mounted with read-write permissions

    edited the 'grub.cfg'-file with an valid MAC-SN (used the same from my DSM 5.5 installation) and the VID+PID (vid=0x46f4 pid=0x0001)

    changed my virtual MAC-address (same as 'grub.cfg' via "virsh edit vm_name")

    booted via text-console

    used the browser to start the installation

    used the official 'DSM_DS3615xs_8451.pat' file

    created btrfs without problems

    updated to '6.0.2-8451 Update 2'

     

    Good luck!

    Could you please provide more details?

    Your VM booting from your virtual USB device?

    What hypervisor do you use?

  9. Good day, everyone :wink:

     

    Could you please help me or show in which direction i should investigate? =)

     

    I has the following problem.

     

    Trying to install DSM 6.0.2-8451 into Proxmox VM.

     

    I got jun-baremetal-uefi-arcao-v2.img, convert it into qcow2 disk. (Thanks to Arcao :smile: )

    Connect it into VM, setted as UEFI boot.

     

    Xpenology booted Ok. But when I try to install DSM_DS3615xs_8451.pat I always totting error 13 - "Failed to install the file. The file is probably corrupted. (13)".

     

    Here is my grub.cfg

    # cat ~/xpe/grub/grub.cfg 
    serial --port=0x3F8 --speed=115200
    terminal_input serial console
    terminal_output serial console
    set default='0'
    set timeout='5'
    set fallback='0'
    insmod part_msdos
    insmod part_gpt
    set locale_dir=$prefix/locale
    set lang=en_US
    
    menuentry 'Synology DS3615xs' --class os {
    insmod fat
          set img=$prefix/../image/DS3615xs
    linux $img/zImage root=/dev/md0 syno_hdd_powerup_seq=0 netif_num=1 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 rmmod=ata_piix console=ttyS0,115200n8 sn=B2LWN08140 mac1=001132FFB5A0 withefi elevator=your_magic_elevator quiet
    initrd $img/ramdisk.lzma
    }
    

     

    I read that error 13 related to wrong vid/pid, but I don't really know which of them I have to use. Because VM booting from IDE.

     

    Here is VM config file

     

    # cat /etc/pve/qemu-server/111.conf 
    bios: ovmf
    bootdisk: ide0
    cores: 1
    efidisk0: local:111/vm-111-disk-3.qcow2,size=128K
    ide0: local:111/vm-111-xp-uefi.qcow2
    memory: 512
    net0: e1000=00:11:32:FF:B5:A0,bridge=vmbr0
    numa: 0
    ostype: l26
    sata0: local:111/vm-111-disk-2.qcow2,size=320G
    scsihw: virtio-scsi-pci
    smbios1: uuid=9d85a89b-043d-4bf8-9c9d-9955c1add4e0
    sockets: 1
    

     

    Would be very appreciated for any help :wink:

×
×
  • Create New...