Jump to content
XPEnology Community

romansoft

Member
  • Posts

    17
  • Joined

  • Last visited

Posts posted by romansoft

  1. On 9/11/2020 at 11:37 AM, satdream said:

     

    Simply to configure, but not "inside" the gen8 ;) , and it is 6+6 = 12 HDD ...

     

    - a low-profile SAS card, a LSI 9202-16E which is a 4x ports SFF8644 = 16x HDD support (fully supported by DSM, but need MPT2 extended drivers)

    - a 12 (1.5U) or 16 slots (2U ) external rack with SAS/SATA (= 3x or 4x Mini SAS SFF-8087)

    - and 3x or 4x SFF-8644 > Mini SAS SFF-8087 cables ...

     

    in my case I toke a 12 slots external rack, and I also use the 4x gen8 internal HDD slots but connected to the LSI card ... disconnecting the internal HP storage card.

     

    Best.

     

    Even more difficult... did you (or somebody else) manage to "exchange" wires (in an easily way) in HP Gen8  so "5th SATA" (the one we usually plug into a SSD disk) could be exchanged by "1st SATA" (one of the four normal hd slots)? This would bring two benefits:

     

    1/ (main) Take profit of full SSD speed (because 1st SATA is SATA3 while 5th SATA is SATA2 so running SSD on 5th SATA is running it at half-speed).

    2/ Direct boot from SSD w/o nasty tricks (currently, I need to boot SD card with a special boot loader that in turn jump into SSD boot loader).

     

    Cheers,

    -r

  2. I suspect that, in my case, the problem's root cause is some dynamic parameter which may be changing between boots (Xpenology and/or Proxmox reboots), probably due to some recent change in Proxmox, and which finally lead to DSM "detecting" that the hw has changed (but then I cannot explain why a recovered backup does work; it shouldn't either).

     

    In your experience, which kind of hw changes do you think DSM could be detecting? See the (Proxmox) config I previosly posted (1st post in this thread).

     

    Re @haydibe's config, it seems simplest than mine but he took a different approach than me: I bet he included updated drivers in extra.lzma (so for instance, vmxnet3 works). My approach was to have always the same synoboot img (no modifications, apart from the initial config), valid for different DSM versions.

     

    Maybe my approach is worst since I have to maintain some hacks like the use of e1000e driver, which is not supported by Proxmox.

     

    I'll think about it and maybe I'll go for @haydibe's config.

     

    Thx!

  3. Hi all,

     

    DSM gets "continually broken" (I mean, I fix it but then it gets broken again) after a Proxmox 6 to 7 upgrade. Jun's loader shows (serial terminal):

    "lz failed 9
    alloc failed
    Cannot load /boot/zImage"

     

    But please, let me first explain all details and read until the end because the situation is very strange...

     

    I'm using JUN'S LOADER v1.03b - DS3617xs in a Proxmox VM (on HP Gen8), with DSM 6.2.3-25426. I've been using this config for months without any problem on Proxmox **6.x** (this seems relevant).

     

    The other day I decided to upgrade Proxmox to **7.x**. I upgraded Proxmox and rebooted. All my VMs booted up perfectly... except DSM one :(

     

    I observed that I couldn't reach my network shares at DSM, and after a quick investigation, I discovered that DSM booted up in "installation mode", showing this message in web interface:

    "We've detected that the hard drives of your current DS3617xs has been moved from a previous DS3617xs, and installing a newer DSM is required before continuing.".

     

    I thought DSM partition may have been corrupted in some way or (most likely) Proxmox 7 introduced kind of a "virtual hw change" so now DSM thinks it's been booted in another hw. This last option is very plausible because Proxmox 7 uses qemu 6.0, while Proxmox 6 (latest) uses qemu 5.2. Maybe other changes in new version of Proxmox could have been introduced (for instance, I've read something regarding assigned MAC of a bridge interface being different).

     

    What I did was:

    1/ Power off DSM VM.

    2/ Back up partition 1 for all my 4 disks (i.e the md0 array which contains DSM OS).

    3/ Power on DSM VM.

    4/ I followed instructions in the web interface, chose "Migrate" (which basically keeps my data and config untouched), selected a manual installation of DSM and uploaded the .pat corresponding to the very same version I was already running before the problem, i.e. DSM_DS3617xs_25426.pat (DSM 6.2.3-25426). I didn't want to downgrade, and of course, I shouldn't upgrade because next version is 6.2.4, which is incompatible with Jun's loader.

    5/ Migration got finished, DSM rebooted and... FIXED!!! :-) DSM was working again with no loss of data nor config.

     

    *But* another problem arised later... When my server (Proxmox) got rebooted again, DSM VM resulted broken again but this time in a very different way: I couldn't ping my DSM VM, and after investigation, I concluded DSM kernel was not being loaded at all. Indeed, I attached a serial terminal to DSM VM and I could see Jun's loader being stuck at the very beginning with these messages:

    "lz failed 9
    alloc failed
    Cannot load /boot/zImage"

     

    No idea why this is happening nor what these messages really mean (well, it seems obvius kernel is not being loaded but I don't know why) !!

     

    I managed to fix it again (yeah xD) by:

    1/ Power off DSM VM.

    2/ Restore partition 1 for all my disks from just the backup I took when solving former problem :)

    3/ Power on DSM VM

    4/ I confirmed loader worked again and that I got to the same point where DSM needed a migration

    5/ I "migrated" exactly in the same way I had done minutes before :). FIXED!!

     

    What's the problem then? Easy... every time I reboot my server (so Proxmox reboots), my DSM VM got broken again with the second error ("lz failed... etc), i.e, loader's kernel not being loaded. I could temporarily fix it but sooner or later I'll need to reboot Proxmox again and... boom again :-(

     

    Any of these problems are familiar to you? Any clue about how to solve this or a least, some ideas I should focus my investigation on?

     

    PLEASE, help!! :_(

     

     

    PS: My Proxmox VM config (a.k.a. qemu config) (with some info redacted):

     

     

    args: -device 'nec-usb-xhci,id=usb-ctl-synoboot,addr=0x18' -drive 'id=usb-drv-synoboot,file=/var/lib/vz/images/100/synoboot_103b_ds3617_roman.img,if=none,format=raw' -device 'usb-storage,id=usb-stor-synoboot,bootindex=1,removable=off,drive=usb-drv-synoboot' -netdev type=tap,id=net0,ifname=tap100i0 -device e1000e,mac=00:XX:XX:XX:XX:XX,netdev=net0,bus=pci.0,addr=0x12,id=net0

    bios: seabios

    boot: d

    cores: 4

    cpu: IvyBridge

    hotplug: disk,network,usb

    memory: 2048

    name: NAS-Synology

    numa: 0

    onboot: 1

    ostype: l26

    sata0: /dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4NXXXXXXX,size=2930266584K

    sata1: /dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4NYYYYYYY,size=2930266584K

    sata2: /dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4NZZZZZZZ,size=2930266584K

    sata3: /dev/disk/by-id/ata-WDC_WD40EFRX-68N32N0_WD-WCC7KAAAAAAA,size=3907018584K

    scsihw: virtio-scsi-pci

    serial0: socket

    smbios1: uuid=9ba1da8f-1321-4a5e-8b00-c7020e51f8ee

    sockets: 1

    startup: order=1

    usb0: host=5-2,usb3=1

     

  4. @IG-88 I didn't find any useful info in provided link but thank you anyway for trying to help.

     

    Finally, after some research, I managed to get a similar config *working:-) (it was a little bit tricky).

     

    1/ I guessed the kernel panic was due to some USB driver problem (related to my USB stick being loaded) so I simply changed the synoboot device from the USB stick to an emulated USB-disk (qemu storage disk).

    2/ Also, in order to install/upgrade DSM (avoiding the infamous "error 13"), I had to set proper vid/pid in synoboot.img (grub.cfg), which in case of qemu storage disk is:

     

    # QEMU STORAGE DISK
    set vid=0x46f4
    set pid=0x0001

     

    So not exactly what I wanted (I'd have prefered to keep using USB stick but I couldn't find any qemu option to alter USB driver/properties when the device is being passed-thru from host to vm) but it works.

     

    PD: I don't like e1000e trick (via args) either but it seems Proxmox won't support e1000e (according to Proxmox forum, although I don't have the exact link on hand).

     

    Btw, this is my final config for proxmox VM:

     

    Quote

    # USB disk plus e1000e fix
    args: -device 'nec-usb-xhci,id=usb-ctl-synoboot,addr=0x18' -drive 'id=usb-drv-synoboot,file=/var/lib/vz/images/100/synoboot_103b_ds3617_roman.img,if=none,format=raw' -device 'usb
    -storage,id=usb-stor-synoboot,bootindex=1,removable=off,drive=usb-drv-synoboot' -netdev type=tap,id=net0,ifname=tap100i0 -device e1000e,mac=00:11:32:73:68:AB,netdev=net0,bus=pci.
    0,addr=0x12,id=net0
    bios: seabios
    boot: d
    cores: 4
    cpu: IvyBridge
    hotplug: disk,network,usb
    memory: 1024
    name: NAS-Synology
    numa: 0
    onboot: 1
    ostype: l26
    sata0: /dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-**************,size=2930266584K
    sata1: /dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-**************,size=2930266584K
    sata2: /dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-**************size=2930266584K
    sata3: /dev/disk/by-id/ata-WDC_WD40EFRX-68N32N0_WD-**************,size=3907018584K
    scsihw: virtio-scsi-pci
    serial0: socket
    smbios1: uuid=9ba1da8f-1321-4a5e-8b00-c7020e51f8ee
    sockets: 1
    startup: order=1

     

    For editing grub.cfg at synoboot.img, you can use any Linux shell and type:

     

    Quote

    # mkdir k
    # mount -o offset=$((512*2048)) synoboot_103b_ds3617_roman.img k
    # vi k/grub/grub.cfg

    ...

    set vid=0x46f4
    set pid=0x0001

    ...
    # umount k

     

    Done! :-)

  5. Hi,

     

    I booted from loader 1.03b-ds3617xs, entered Syno's web-GUI and chose to install latest DSM (6.2.2-24922-4). Then rebooted and now I always get a Kernel panic when booting.

     

    Proxmox's host is Ivy Bridge:

    • CPU model name      : Intel(R) Xeon(R) CPU E3-1265L V2 @ 2.50GHz

     

    This is my Proxmox's config, which basically includes:

    • e1000e hack
    • Since Proxmox may only boot from USB if using UEFI and 1.03b doesn't support UEFI, I selected Seabios but did another hack: booting from CD and then chain-loads to USB.
    • 1.03b loader is embeded in a physical USB


     

    Quote

     

    root@proxmox:~# cat /etc/pve/qemu-server/100.conf
    #net0%3A e1000=00%3A11%3A32%3A73%3A68%3AAB,bridge=vmbr0
    # Fix para usar e1000e
    args: -netdev type=tap,id=net0,ifname=tap100i0 -device e1000e,mac=00:11:32:73:68:AB,netdev=net0,bus=pci.0,addr=0x12,id=net0
    bios: seabios
    boot: d
    cores: 4
    cpu: IvyBridge
    hotplug: disk,network,usb
    ide2: local:iso/plpbt-usbboot.iso,media=cdrom,size=538K
    memory: 1024
    name: NAS-Synology
    numa: 1
    ostype: l26
    parent: DSM62_update2
    sata0: /dev/disk/by-id/ata-WDC_WD40EFRX-68N32N0_WD-WCC7K1CN3NJK,size=3907018584K
    scsihw: virtio-scsi-pci
    serial0: socket
    smbios1: uuid=9ba1da8f-1321-4a5e-8b00-c7020e51f8ee
    sockets: 1
    usb0: host=1-1.2

     


     

     

    Boot process log (ends up with kernel panic)

     

    Quote

    root@proxmox:/mnt# qm term 100
    starting serial terminal on interface serial0 (press Ctrl+O to exit)

                       GNU GRUB  version 2.02~beta2-36ubuntu3.14

     +----------------------------------------------------------------------------+
     |*DS3617xs 6.2 Baremetal with Jun's Mod v1.03b                               | 
     | DS3617xs 6.2 Baremetal with Jun's Mod v1.03b Reinstall                     |
     | DS3617xs 6.2 VMWare/ESXI with Jun's Mod v1.03b                             |
     |                                                                            |
     |                                                                            |
     |                                                                            |
     |                                                                            |
     |                                                                            |
     |                                                                            |
     |                                                                            |
     |                                                                            |
     |                                                                            | 
     +----------------------------------------------------------------------------+

          Use the ^ and v keys to select which entry is highlighted.          
          Press enter to boot the selected OS, `e' to edit the commands       
          before booting or `c' for a command-line.                           
       The highlighted entry will be executed automatically in 0s.                 
    error: failure writing sector 0x3205 to `hd0'.

    Press any key to continue...
    [    0.000000] NX (Execute Disable) protection: active
    [    0.000000] SMBIOS 2.8 present.
    [    0.000000] DMI: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org 04/01/2014
    [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
    [    0.000000] e820: last_pfn = 0x3ffde max_arch_pfn = 0x400000000
    [    0.000000] MTRR default type: write-back
    [    0.000000] MTRR fixed ranges enabled:
    [    0.000000]   00000-9FFFF write-back
    [    0.000000]   A0000-BFFFF uncachable
    [    0.000000]   C0000-FFFFF write-protect
    [    0.000000] MTRR variable ranges enabled:
    [    0.000000]   0 base 0080000000 mask FF80000000 uncachable
    [    0.000000]   1 disabled
    [    0.000000]   2 disabled
    [    0.000000]   3 disabled
    [    0.000000]   4 disabled
    [    0.000000]   5 disabled
    [    0.000000]   6 disabled
    [    0.000000]   7 disabled
    [    0.000000] found SMP MP-table at [mem 0x000f5ab0-0x000f5abf] mapped at [ffff8800000f5ab0]
    [    0.000000] Base memory trampoline at [ffff880000094000] 94000 size 24576
    [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
    [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
    [    0.000000] BRK [0x01ac2000, 0x01ac2fff] PGTABLE
    [    0.000000] BRK [0x01ac3000, 0x01ac3fff] PGTABLE
    [    0.000000] BRK [0x01ac4000, 0x01ac4fff] PGTABLE
    [    0.000000] init_memory_mapping: [mem 0x3fc00000-0x3fdfffff]
    [    0.000000]  [mem 0x3fc00000-0x3fdfffff] page 2M
    [    0.000000] init_memory_mapping: [mem 0x3c000000-0x3fbfffff]
    [    0.000000]  [mem 0x3c000000-0x3fbfffff] page 2M
    [    0.000000] init_memory_mapping: [mem 0x00100000-0x3bffffff]
    [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
    [    0.000000]  [mem 0x00200000-0x3bffffff] page 2M
    [    0.000000] init_memory_mapping: [mem 0x3fe00000-0x3ffddfff]
    [    0.000000]  [mem 0x3fe00000-0x3ffddfff] page 4k
    [    0.000000] BRK [0x01ac5000, 0x01ac5fff] PGTABLE
    [    0.000000] RAMDISK: [mem 0x3669f000-0x37ffffff]
    [    0.000000] ACPI: RSDP 0x00000000000F58D0 00014 (v00 BOCHS )
    [    0.000000] ACPI: RSDT 0x000000003FFE25AC 00034 (v01 BOCHS  BXPCRSDT 00000001 BXPC 00000001)
    [    0.000000] ACPI: FACP 0x000000003FFE2388 00074 (v01 BOCHS  BXPCFACP 00000001 BXPC 00000001)
    [    0.000000] ACPI: DSDT 0x000000003FFE0040 02348 (v01 BOCHS  BXPCDSDT 00000001 BXPC 00000001)
    [    0.000000] ACPI: FACS 0x000000003FFE0000 00040
    [    0.000000] ACPI: APIC 0x000000003FFE23FC 00090 (v01 BOCHS  BXPCAPIC 00000001 BXPC 00000001)
    [    0.000000] ACPI: HPET 0x000000003FFE248C 00038 (v01 BOCHS  BXPCHPET 00000001 BXPC 00000001)
    [    0.000000] ACPI: SRAT 0x000000003FFE24C4 000E8 (v01 BOCHS  BXPCSRAT 00000001 BXPC 00000001)
    [    0.000000] ACPI: Local APIC address 0xfee00000
    [    0.000000]  [ffffea0000000000-ffffea0000dfffff] PMD -> [ffff88003e600000-ffff88003f3fffff] on node 0
    [    0.000000] Zone ranges:
    [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
    [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
    [    0.000000]   Normal   empty
    [    0.000000] Movable zone start for each node
    [    0.000000] Early memory node ranges
    [    0.000000]   node   0: [mem 0x00001000-0x0009efff]
    [    0.000000]   node   0: [mem 0x00100000-0x3ffddfff]
    [    0.000000] On node 0 totalpages: 262012
    [    0.000000]   DMA zone: 56 pages used for memmap
    [    0.000000]   DMA zone: 26 pages reserved
    [    0.000000]   DMA zone: 3998 pages, LIFO batch:0
    [    0.000000]   DMA32 zone: 3528 pages used for memmap
    [    0.000000]   DMA32 zone: 258014 pages, LIFO batch:31
    [    0.000000] ACPI: PM-Timer IO Port: 0x608
    [    0.000000] ACPI: Local APIC address 0xfee00000
    [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
    [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
    [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
    [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
    [    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
    [    0.000000] ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
    [    0.000000] IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-23
    [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
    [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
    [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
    [    0.000000] ACPI: IRQ0 used by override.
    [    0.000000] ACPI: IRQ2 used by override.
    [    0.000000] ACPI: IRQ5 used by override.
    [    0.000000] ACPI: IRQ9 used by override.
    [    0.000000] ACPI: IRQ10 used by override.
    [    0.000000] ACPI: IRQ11 used by override.
    [    0.000000] Using ACPI (MADT) for SMP configuration information
    [    0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
    [    0.000000] smpboot: Allowing 4 CPUs, 0 hotplug CPUs
    [    0.000000] nr_irqs_gsi: 40
    [    0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    [    0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
    [    0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
    [    0.000000] e820: [mem 0x40000000-0xfeffbfff] available for PCI devices
    [    0.000000] setup_percpu: NR_CPUS:16 nr_cpumask_bits:16 nr_cpu_ids:4 nr_node_ids:1
    [    0.000000] PERCPU: Embedded 26 pages/cpu @ffff88003fc00000 s76864 r8192 d21440 u524288
    [    0.000000] pcpu-alloc: s76864 r8192 d21440 u524288 alloc=1*2097152
    [    0.000000] pcpu-alloc: [0] 0 1 2 3 
    [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 258402
    [    0.000000] Kernel command line: 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 root=/dev/md0 sn=1710ODXXXXXXX mac1=XXXXXXXXXX netif_num=1 vid=0x13fe pid=0x4100 earlycon=uart8250,io,0x3f8,115200n8 earlyprintk loglevel=15
    [    0.000000] Power on seq num: 0
    [    0.000000] Synology Hardware Version: DS3617xs-j
    [    0.000000] Vender format version: 2
    [    0.000000] Serial Number: 1710ODN128000
    [    0.000000] Mac1: 0011327368AB
    [    0.000000] Internal netif num: 1
    [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
    [    0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
    [    0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
    [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
    [    0.000000] Memory: 994544k/1048440k available (4896k kernel code, 392k absent, 53504k reserved, 3722k data, 788k init)
    [    0.000000] Kernel/User page tables isolation: disabled
    [    0.000000] Hierarchical RCU implementation.
    [    0.000000]  CONFIG_RCU_FANOUT set to non-default value of 32
    [    0.000000]  RCU dyntick-idle grace-period acceleration is enabled.
    [    0.000000]  RCU restricting CPUs from NR_CPUS=16 to nr_cpu_ids=4.
    [    0.000000] NR_IRQS:4352 nr_irqs:712 16
    [    0.000000] Console: colour dummy device 80x25
    [    0.000000] console [ttyS0] enabled, bootconsole disabled
    [    0.000000] console [ttyS0] enabled, bootconsole disabled
    [    0.000000] allocated 4194304 bytes of page_cgroup
    [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
    [    0.000000] hpet clockevent registered
    [    0.000000] tsc: Fast TSC calibration using PIT
    [    0.000000] tsc: Detected 2494.571 MHz processor
    [    0.000001] Calibrating delay loop (skipped), value calculated using timer frequency.. 4989.14 BogoMIPS (lpj=2494571)
    [    0.001000] pid_max: default: 32768 minimum: 301
    [    0.001000] Security Framework initialized
    [    0.001000] AppArmor: AppArmor initialized
    [    0.001000] Mount-cache hash table entries: 256
    [    0.001000] Initializing cgroup subsys memory
    [    0.001000] Initializing cgroup subsys devices
    [    0.001000] Initializing cgroup subsys freezer
    [    0.001000] Initializing cgroup subsys blkio
    [    0.001000] CPU: Physical Processor ID: 0
    [    0.001000] CPU: Processor Core ID: 0
    [    0.001000] mce: CPU supports 10 MCE banks
    [    0.001000] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
    [    0.001000] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0
    [    0.001000] tlb_flushall_shift: 2
    [    0.001000] FEATURE SPEC_CTRL Not Present
    [    0.001000] FEATURE IBPB_SUPPORT Not Present
    [    0.001000] Spectre V2 : Vulnerable: Minimal ASM retpoline
    [    0.001000] Freeing SMP alternatives: 24k freed
    [    0.001000] ACPI: Core revision 20130328
    [    0.001000] ACPI: All ACPI Tables successfully acquired
    [    0.001000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    [    0.011088] smpboot: CPU0: Intel Xeon E3-12xx v2 (Ivy Bridge) (fam: 06, model: 3a, stepping: 09)
    [    0.013037] TSC deadline timer enabled
    [    0.013920] Performance Events: unsupported p6 CPU model 58 no PMU driver, software events only.
    [    0.014844] NMI watchdog: disabled (cpu0): hardware events not enabled
    [    0.015066] smpboot: Booting Node   0, Processors  #1 #2 #3 OK
    [    0.052026] Brought up 4 CPUs
    [    0.052779] smpboot: Total of 4 processors activated (19956.56 BogoMIPS)
    [    0.053529] devtmpfs: initialized
    [    0.055101] xor: automatically using best checksumming function:
    [    0.064000]    avx       : 24204.000 MB/sec
    [    0.064000] NET: Registered protocol family 16
    [    0.067098] ACPI: bus type PCI registered
    [    0.068051] PCI: Using configuration type 1 for base access
    [    0.083160] bio: create slab <bio-0> at 0
    [    0.101312] raid6: sse2x1   gen()  8468 MB/s
    [    0.118179] raid6: sse2x1   xor()  6669 MB/s
    [    0.135892] raid6: sse2x2   gen() 10253 MB/s
    [    0.152260] raid6: sse2x2   xor()  7505 MB/s
    [    0.169084] raid6: sse2x4   gen() 12187 MB/s
    [    0.187000] raid6: sse2x4   xor()  8902 MB/s
    [    0.187003] raid6: using algorithm sse2x4 gen() (12187 MB/s)
    [    0.188004] raid6: .... xor() 8902 MB/s, rmw enabled
    [    0.190004] raid6: using ssse3x2 recovery algorithm
    [    0.191152] ACPI: Added _OSI(Module Device)
    [    0.192003] ACPI: Added _OSI(Processor Device)
    [    0.192920] ACPI: Added _OSI(3.0 _SCP Extensions)
    [    0.193003] ACPI: Added _OSI(Processor Aggregator Device)
    [    0.194269] ACPI: EC: Look up EC in DSDT
    [    0.195622] ACPI: Interpreter enabled
    [    0.196009] ACPI: (supports S0 S4 S5)
    [    0.196583] ACPI: Using IOAPIC for interrupt routing
    [    0.198030] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    [    0.199623] ACPI: No dock devices found.
    [    0.216060] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    [    0.217007] acpi PNP0A03:00: ACPI _OSC support notification failed, disabling PCIe ASPM
    [    0.218004] acpi PNP0A03:00: Unable to request _OSC control (_OSC support mask: 0x08)
    [    0.219015] acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge.
    [    0.221034] PCI host bridge to bus 0000:00
    [    0.221592] pci_bus 0000:00: root bus resource [bus 00-ff]
    [    0.222020] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7]
    [    0.222854] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff]
    [    0.224006] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    [    0.224944] pci_bus 0000:00: root bus resource [mem 0x40000000-0xfebfffff]
    [    0.226004] pci_bus 0000:00: root bus resource [mem 0x100000000-0x17fffffff]
    [    0.227029] pci 0000:00:00.0: [8086:1237] type 00 class 0x060000
    [    0.228255] pci 0000:00:01.0: [8086:7000] type 00 class 0x060100
    [    0.230371] pci 0000:00:01.1: [8086:7010] type 00 class 0x010180
    [    0.233004] pci 0000:00:01.1: reg 20: [io  0xe0e0-0xe0ef]
    [    0.235035] pci 0000:00:01.2: [8086:7020] type 00 class 0x0c0300
    [    0.237990] pci 0000:00:01.2: reg 20: [io  0xe000-0xe01f]
    [    0.240064] pci 0000:00:01.3: [8086:7113] type 00 class 0x068000
    [    0.241203] pci 0000:00:01.3: address space collision: [io  0x0600-0x063f] conflicts with ACPI PM1a_EVT_BLK [??? 0x00000600-0x00000603 flags 0x80000000]
    [    0.244014] pci 0000:00:01.3: quirk: [io  0x0700-0x070f] claimed by PIIX4 SMB
    [    0.245138] pci 0000:00:02.0: [1234:1111] type 00 class 0x030000
    [    0.246805] pci 0000:00:02.0: reg 10: [mem 0xfd000000-0xfdffffff pref]
    [    0.249004] pci 0000:00:02.0: reg 18: [mem 0xfea94000-0xfea94fff]
    [    0.253299] pci 0000:00:02.0: reg 30: [mem 0xfea80000-0xfea8ffff pref]
    [    0.255097] pci 0000:00:03.0: [1af4:1002] type 00 class 0x00ff00
    [    0.256639] pci 0000:00:03.0: reg 10: [io  0xe020-0xe03f]
    [    0.260004] pci 0000:00:03.0: reg 20: [mem 0xfe400000-0xfe403fff 64bit pref]
    [    0.263438] pci 0000:00:07.0: [8086:2922] type 00 class 0x010601
    [    0.267261] pci 0000:00:07.0: reg 20: [io  0xe040-0xe05f]
    [    0.268531] pci 0000:00:07.0: reg 24: [mem 0xfea95000-0xfea95fff]
    [    0.270032] pci 0000:00:12.0: [8086:10d3] type 00 class 0x020000
    [    0.271675] pci 0000:00:12.0: reg 10: [mem 0xfea40000-0xfea5ffff]
    [    0.274920] pci 0000:00:12.0: reg 14: [mem 0xfea60000-0xfea7ffff]
    [    0.275989] pci 0000:00:12.0: reg 18: [io  0xe060-0xe07f]
    [    0.277994] pci 0000:00:12.0: reg 1c: [mem 0xfea90000-0xfea93fff]
    [    0.282637] pci 0000:00:12.0: reg 30: [mem 0xfea00000-0xfea3ffff pref]
    [    0.284357] pci 0000:00:1d.0: [8086:2934] type 00 class 0x0c0300
    [    0.287435] pci 0000:00:1d.0: reg 20: [io  0xe080-0xe09f]
    [    0.289030] pci 0000:00:1d.1: [8086:2935] type 00 class 0x0c0300
    [    0.291344] pci 0000:00:1d.1: reg 20: [io  0xe0a0-0xe0bf]
    [    0.294035] pci 0000:00:1d.2: [8086:2936] type 00 class 0x0c0300
    [    0.296545] pci 0000:00:1d.2: reg 20: [io  0xe0c0-0xe0df]
    [    0.298671] pci 0000:00:1d.7: [8086:293a] type 00 class 0x0c0320
    [    0.299360] pci 0000:00:1d.7: reg 10: [mem 0xfea96000-0xfea96fff]
    [    0.303067] pci 0000:00:1e.0: [1b36:0001] type 01 class 0x060400
    [    0.304713] pci 0000:00:1e.0: reg 10: [mem 0xfea97000-0xfea970ff 64bit]
    [    0.307074] pci 0000:00:1f.0: [1b36:0001] type 01 class 0x060400
    [    0.308596] pci 0000:00:1f.0: reg 10: [mem 0xfea98000-0xfea980ff 64bit]
    [    0.311213] pci 0000:00:1e.0: PCI bridge to [bus 01]
    [    0.312018] pci 0000:00:1e.0:   bridge window [io  0xd000-0xdfff]
    [    0.313016] pci 0000:00:1e.0:   bridge window [mem 0xfe800000-0xfe9fffff]
    [    0.313909] pci 0000:00:1e.0:   bridge window [mem 0xfe200000-0xfe3fffff 64bit pref]
    [    0.316198] pci 0000:00:1f.0: PCI bridge to [bus 02]
    [    0.317016] pci 0000:00:1f.0:   bridge window [io  0xc000-0xcfff]
    [    0.317923] pci 0000:00:1f.0:   bridge window [mem 0xfe600000-0xfe7fffff]
    [    0.319031] pci 0000:00:1f.0:   bridge window [mem 0xfe000000-0xfe1fffff 64bit pref]
    [    0.320736] pci_bus 0000:00: on NUMA node 0
    [    0.322324] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
    [    0.323287] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
    [    0.324290] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
    [    0.325654] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
    [    0.326364] ACPI: PCI Interrupt Link [LNKS] (IRQs *9)
    [    0.328040] ACPI: Enabled 2 GPEs in block 00 to 0F
    [    0.328040] acpi root: \_SB_.PCI0 notify handler is installed
    [    0.328897] Found 1 acpi root devices
    [    0.330038] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
    [    0.331019] vgaarb: loaded
    [    0.331451] vgaarb: bridge control possible 0000:00:02.0
    [    0.333201] SCSI subsystem initialized
    [    0.333535] ACPI: bus type ATA registered
    [    0.335044] libata version 3.00 loaded.
    [    0.336026] pps_core: LinuxPPS API ver. 1 registered
    [    0.336619] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
    [    0.337030] PTP clock support registered
    [    0.338017] PCI: Using ACPI for IRQ routing
    [    0.338614] PCI: pci_cache_line_size set to 64 bytes
    [    0.339172] e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
    [    0.340004] e820: reserve RAM buffer [mem 0x3ffde000-0x3fffffff]
    [    0.341088] Switching to clocksource hpet
    [    0.342209] AppArmor: AppArmor Filesystem Enabled
    [    0.343215] pnp: PnP ACPI init
    [    0.343723] ACPI: bus type PNP registered
    [    0.344615] pnp 00:00: Plug and Play ACPI device, IDs PNP0b00 (active)
    [    0.345857] pnp 00:01: Plug and Play ACPI device, IDs PNP0303 (active)
    [    0.347361] pnp 00:02: Plug and Play ACPI device, IDs PNP0f13 (active)
    [    0.348380] pnp 00:03: [dma 2]
    [    0.349072] pnp 00:03: Plug and Play ACPI device, IDs PNP0700 (active)
    [    0.350752] pnp 00:04: Plug and Play ACPI device, IDs PNP0501 (active)
    [    0.352309] pnp 00:05: Plug and Play ACPI device, IDs PNP0a06 (active)
    [    0.353944] pnp 00:06: Plug and Play ACPI device, IDs PNP0a06 (active)
    [    0.355337] pnp 00:07: Plug and Play ACPI device, IDs PNP0a06 (active)
    [    0.356806] pnp 00:08: Plug and Play ACPI device, IDs PNP0103 (active)
    [    0.357841] pnp: PnP ACPI: found 9 devices
    [    0.358500] ACPI: bus type PNP unregistered
    [    0.394398] pci 0000:00:01.3: BAR 13: [io  0x0600-0x063f] has bogus alignment
    [    0.395863] pci 0000:00:1e.0: PCI bridge to [bus 01]
    [    0.397046] pci 0000:00:1e.0:   bridge window [io  0xd000-0xdfff]
    [    0.399129] pci 0000:00:1e.0:   bridge window [mem 0xfe800000-0xfe9fffff]
    [    0.400641] pci 0000:00:1e.0:   bridge window [mem 0xfe200000-0xfe3fffff 64bit pref]
    [    0.402735] pci 0000:00:1f.0: PCI bridge to [bus 02]
    [    0.403582] pci 0000:00:1f.0:   bridge window [io  0xc000-0xcfff]
    [    0.405145] pci 0000:00:1f.0:   bridge window [mem 0xfe600000-0xfe7fffff]
    [    0.406599] pci 0000:00:1f.0:   bridge window [mem 0xfe000000-0xfe1fffff 64bit pref]
    [    0.431478] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
    [    0.432912] pci 0000:00:1e.0: setting latency timer to 64
    [    0.455812] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
    [    0.457612] pci 0000:00:1f.0: setting latency timer to 64
    [    0.458731] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7]
    [    0.459565] pci_bus 0000:00: resource 5 [io  0x0d00-0xffff]
    [    0.460394] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    [    0.461275] pci_bus 0000:00: resource 7 [mem 0x40000000-0xfebfffff]
    [    0.462197] pci_bus 0000:00: resource 8 [mem 0x100000000-0x17fffffff]
    [    0.463174] pci_bus 0000:01: resource 0 [io  0xd000-0xdfff]
    [    0.463981] pci_bus 0000:01: resource 1 [mem 0xfe800000-0xfe9fffff]
    [    0.464953] pci_bus 0000:01: resource 2 [mem 0xfe200000-0xfe3fffff 64bit pref]
    [    0.466068] pci_bus 0000:02: resource 0 [io  0xc000-0xcfff]
    [    0.466882] pci_bus 0000:02: resource 1 [mem 0xfe600000-0xfe7fffff]
    [    0.467820] pci_bus 0000:02: resource 2 [mem 0xfe000000-0xfe1fffff 64bit pref]
    [    0.469289] NET: Registered protocol family 2
    [    0.470424] TCP established hash table entries: 8192 (order: 5, 131072 bytes)
    [    0.471514] TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
    [    0.472386] TCP: Hash tables configured (established 8192 bind 8192)
    [    0.473260] TCP: reno registered
    [    0.473759] UDP hash table entries: 512 (order: 2, 16384 bytes)
    [    0.474714] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
    [    0.475998] NET: Registered protocol family 1
    [    0.477229] RPC: Registered named UNIX socket transport module.
    [    0.478108] RPC: Registered udp transport module.
    [    0.478790] RPC: Registered tcp transport module.
    [    0.479538] RPC: Registered tcp NFSv4.1 backchannel transport module.
    [    0.480539] pci 0000:00:00.0: Limiting direct PCI/PCI transfers
    [    0.481477] pci 0000:00:01.0: Activating ISA DMA hang workarounds
    [    0.506263] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
    [    0.530608] pci 0000:00:02.0: Boot video device
    [    0.554618] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
    [    0.717378] PCI: CLS 64 bytes, default 64
    [    0.718398] Trying to unpack rootfs image as initramfs...
    [    1.025814] Freeing initrd memory: 25988k freed
    [    1.029565] cepsw: module verification failed: signature and/or required key missing - tainting kernel
    [    1.054108] Initialise module verification
    [    1.055077] audit: initializing netlink socket (disabled)
    [    1.055832] type=2000 audit(1577467497.055:1): initialized
    [    1.058053] bounce pool size: 64 pages
    [    1.059441] VFS: Disk quotas dquot_6.5.2
    [    1.060472] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    [    1.066645] NFS: Registering the id_resolver key type
    [    1.067377] Key type id_resolver registered
    [    1.067911] Key type id_legacy registered
    [    1.068488] msgmni has been set to 1993
    [    1.070786] async_tx: api initialized (async)
    [    1.071567] Key type asymmetric registered
    [    1.072545] Asymmetric key parser 'x509' registered
    [    1.073943] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
    [    1.075414] io scheduler noop registered
    [    1.076402] io scheduler deadline registered
    [    1.077084] io scheduler cfq registered (default)
    [    1.385498] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    [    1.411782] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    [    1.413699] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 8250
    [    1.451101] brd: module loaded
    [    1.454555] Loading iSCSI transport class v2.0-870.
    [    1.470384] rdac: device handler registered
    [    1.473346] ahci 0000:00:07.0: version 3.0
    [    1.496934] ahci 0000:00:07.0: irq 40 for MSI/MSI-X
    [    1.498595] ahci 0000:00:07.0: AHCI 0001.0000 32 slots 6 ports 1.5 Gbps 0x3f impl SATA mode
    [    1.500397] ahci 0000:00:07.0: flags: 64bit ncq only 
    [    1.501345] ahci 0000:00:07.0: setting latency timer to 64
    [    1.512765] scsi0 : ahci
    [    1.515770] scsi1 : ahci
    [    1.517124] scsi2 : ahci
    [    1.518791] scsi3 : ahci
    [    1.520641] scsi4 : ahci
    [    1.522188] scsi5 : ahci
    [    1.523643] ata1: SATA max UDMA/133 abar m4096@0xfea95000 port 0xfea95100 irq 40
    [    1.525551] ata2: SATA max UDMA/133 abar m4096@0xfea95000 port 0xfea95180 irq 40
    [    1.526618] ata3: SATA max UDMA/133 abar m4096@0xfea95000 port 0xfea95200 irq 40
    [    1.528043] ata4: SATA max UDMA/133 abar m4096@0xfea95000 port 0xfea95280 irq 40
    [    1.529183] ata5: SATA max UDMA/133 abar m4096@0xfea95000 port 0xfea95300 irq 40
    [    1.530195] ata6: SATA max UDMA/133 abar m4096@0xfea95000 port 0xfea95380 irq 40
    [    1.535259] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
    [    1.539280] serio: i8042 KBD port at 0x60,0x64 irq 1
    [    1.540538] serio: i8042 AUX port at 0x60,0x64 irq 12
    [    1.541989] rtc_cmos 00:00: RTC can wake from S4
    [    1.543699] rtc_cmos 00:00: rtc core: registered rtc_cmos as rtc0
    [    1.545419] rtc_cmos 00:00: alarms up to one day, y3k, 114 bytes nvram, hpet irqs
    [    1.547451] i2c /dev entries driver
    [    1.548565] md: linear personality registered for level -1
    [    1.549973] md: raid0 personality registered for level 0
    [    1.551280] md: raid1 personality registered for level 1
    [    1.552630] md: raid10 personality registered for level 10
    [    1.554538] md: raid6 personality registered for level 6
    [    1.555857] md: raid5 personality registered for level 5
    [    1.557152] md: raid4 personality registered for level 4
    [    1.558451] md: raidF1 personality registered for level 45
    [    1.560481] device-mapper: ioctl: 4.25.0-ioctl (2013-06-26) initialised: dm-devel@redhat.com
    [    1.562576] cpuidle: using governor ladder
    [    1.563489] cpuidle: using governor menu
    [    1.564093] TCP: cubic registered
    [    1.564584] NET: Registered protocol family 17
    [    1.565275] Key type dns_resolver registered
    [    1.836202] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    [    1.838111] ata5: SATA link down (SStatus 0 SControl 300)
    [    1.839312] ata2: SATA link down (SStatus 0 SControl 300)
    [    1.840194] ata3: SATA link down (SStatus 0 SControl 300)
    [    1.840985] ata1.00: ATA-7: QEMU HARDDISK, 2.5+, max UDMA/100
    [    1.842228] ata1.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32)
    [    1.843530] ata1.00: SN:QM00005
    [    1.844145] ata1.00: applying bridge limits
    [    1.845132] ata6: SATA link down (SStatus 0 SControl 300)
    [    1.846310] ata4: SATA link down (SStatus 0 SControl 300)
    [    1.847669] ata1.00: configured for UDMA/100
    [    1.848269] ata1.00: Find SSD disks. [QEMU HARDDISK]
    [    1.849454] scsi 0:0:0:0: Direct-Access     QEMU     HARDDISK                 2.5+ PQ: 0 ANSI: 5
    [    1.851854] sd 0:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.63 TiB)
    [    1.853363] sd 0:0:0:0: [sda] Write Protect is off
    [    1.854120] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    [    1.854939] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [    1.860128]  sda: sda1 sda2
    [    1.862134] sd 0:0:0:0: [sda] Attached SCSI disk
    [    1.863391] Loading module verification blacklist certificates
    [    1.864603] Loading module verification certificates
    [    1.865587] MODSIGN: Loaded cert 'Synology SDG kernel module signing key: 7bd0b0d6bcd31651c22ce3978bdc8c8bdc417329'
    [    1.869093] MODSIGN: Loaded cert 'Synology Root Certification Authority: f2c075361f168425f8b5ef31b796406c3aab2089'
    [    1.871462] MODSIGN: Loaded cert 'Synology Kernel Module Signing Certification Authority: 600839b5d127e0e11d817a31f0575d323a7c0e28'
    [    1.873318] MODSIGN: Loaded cert 'Synology kernel module signing key: 4646ce54489669338118a3b1286da156ac366fa5'
    [    1.874824] registered taskstats version 1
    [    1.876394] rtc_cmos 00:00: setting system clock to 2019-12-27 17:24:58 UTC (1577467498)
    [    1.878439] Freeing unused kernel memory: 788k freed
    [    1.879597] Write protecting the kernel read-only data: 8192k
    [    1.881236] Freeing unused kernel memory: 1236k freed
    [    1.883203] Freeing unused kernel memory: 476k freed
    patching file etc/rc
    Hunk #1 succeeded at 182 (offset 11 lines).
    patching file etc/synoinfo.conf
    Hunk #1 FAILED at 261.
    1 out of 1 hunk FAILED -- saving rejects to file etc/synoinfo.conf.rej
    patching file linuxrc.syno
    Hunk #1 succeeded at 40 with fuzz 2 (offset 1 line).
    Hunk #2 succeeded at 141 (offset 6 lines).
    Hunk #3 succeeded at 579 (offset 28 lines).
    patching file usr/sbin/init.post
    cat: can't open '/etc/synoinfo_override.conf': No such file or directory
    START /linuxrc.syno
    Insert Marvell 1475 SATA controller driver
    Insert basic USB modules...
    :: Loading module usb-common ... [  OK  ]
    :: Loading module usbcore[    1.963061] ACPI: bus type USB registered
    [    1.964779] usbcore: registered new interface driver usbfs
    [    1.966289] usbcore: registered new interface driver hub
    [    1.968202] usbcore: registered new interface driver ethub
    [    1.969546] usbcore: registered new device driver usb
     ... [  OK  ]
    :: Loading module ehci-hcd[    1.982573] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
     ... [  OK  ]
    :: Loading module ehci-pci[    1.989693] ehci-pci: EHCI PCI platform driver
    [    2.013714] ehci-pci 0000:00:1d.7: setting latency timer to 64
    [    2.014606] ehci-pci 0000:00:1d.7: EHCI Host Controller
    [    2.015663] ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 1
    [    2.017209] kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
    [    2.018195] BUG: unable to handle kernel paging request at ffff88003dad4300
    [    2.018195] IP: [<ffff88003dad4300>] 0xffff88003dad42ff
    [    2.018195] PGD 1ac2067 PUD 1ac3067 PMD 800000003da000e3 
    [    2.018195] Oops: 0011 [#1] SMP 
    [    2.018195] Modules linked in: ehci_pci(F+) ehci_hcd(F) usbcore usb_common mv14xx(O) cepsw(OF)
    [    2.018195] CPU: 2 PID: 3444 Comm: insmod Tainted: GF          O 3.10.105 #24922
    [    2.018195] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org 04/01/2014
    [    2.018195] task: ffff88003db79800 ti: ffff880039ec4000 task.ti: ffff880039ec4000
    [    2.018195] RIP: 0010:[<ffff88003dad4300>]  [<ffff88003dad4300>] 0xffff88003dad42ff
    [    2.018195] RSP: 0018:ffff880039ec7b78  EFLAGS: 00010046
    [    2.018195] RAX: ffff88003d44d810 RBX: 0000000000000006 RCX: 0000000000000002
    [    2.018195] RDX: 0000000000000006 RSI: 0000000000000000 RDI: ffff88003d4d2800
    [    2.018195] RBP: ffff88003d4d2800 R08: ffff880039ec7b84 R09: 000000000000fffb
    [    2.018195] R10: 0000000000000000 R11: 00000000000001ae R12: 0000000000000000
    [    2.018195] R13: ffff880039ec7bbe R14: 0000000000000246 R15: ffffffffa00ecb40
    [    2.018195] FS:  00007fa6dec5a700(0000) GS:ffff88003fd00000(0000) knlGS:0000000000000000
    [    2.018195] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [    2.018195] CR2: ffff88003dad4300 CR3: 0000000039d1e000 CR4: 00000000001406e0
    [    2.018195] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    [    2.018195] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    [    2.018195] Stack:
    [    2.018195]  ffffffff81293625 0000000039ec7bd8 000000000000001a 000000000000000a
    [    2.018195]  ffff88003d4d1ff8 0000000000000000 ffff88003d4d2090 ffffffff81298746
    [    2.018195]  0000000000000001 ffff88003d4d1ff8 ffffffff8129878b ffff88003bacb800
    [    2.018195] Call Trace:
    [    2.018195]  [<ffffffff81293625>] ? pci_bus_read_config_word+0x65/0x90
    [    2.018195]  [<ffffffff81298746>] ? __pci_bus_find_cap_start+0x16/0x40
    [    2.047186] tsc: Refined TSC clocksource calibration: 2494.334 MHz
    [    2.047201] Switching to clocksource tsc
    [    2.047203]  [<ffffffff8129878b>] ? pci_find_capability+0x1b/0x50
    [    2.047203]  [<ffffffffa00ec09d>] ? ehci_pci_setup+0x9d/0x5a0 [ehci_pci]
    [    2.047203]  [<ffffffffa00abc4d>] ? usb_add_hcd+0x1bd/0x660 [usbcore]
    [    2.047203]  [<ffffffffa00ba9d3>] ? usb_hcd_pci_probe+0x363/0x410 [usbcore]
    [    2.047203]  [<ffffffff8129c480>] ? pci_device_probe+0x60/0xa0
    [    2.047203]  [<ffffffff81305e9a>] ? really_probe+0x5a/0x220
    [    2.047203]  [<ffffffff81306121>] ? __driver_attach+0x81/0x90
    [    2.047203]  [<ffffffff813060a0>] ? __device_attach+0x40/0x40
    [    2.047203]  [<ffffffff81304193>] ? bus_for_each_dev+0x53/0x90
    [    2.047203]  [<ffffffff81305638>] ? bus_add_driver+0x158/0x250
    [    2.047203]  [<ffffffffa00ee000>] ? 0xffffffffa00edfff
    [    2.047203]  [<ffffffff81306728>] ? driver_register+0x68/0x150
    [    2.047203]  [<ffffffffa00ee000>] ? 0xffffffffa00edfff
    [    2.047203]  [<ffffffff810003aa>] ? do_one_initcall+0xea/0x140
    [    2.047203]  [<ffffffff8108bda4>] ? load_module+0x1a04/0x2120
    [    2.047203]  [<ffffffff81088f60>] ? store_uevent+0x40/0x40
    [    2.047203]  [<ffffffff8108c551>] ? SYSC_init_module+0x91/0xc0
    [    2.047203]  [<ffffffff814c2dc4>] ? system_call_fastpath+0x22/0x27
    [    2.047203] Code: 88 ff ff 00 d8 44 3d 00 88 ff ff 70 63 69 30 30 30 30 3a 30 30 00 48 85 ed 74 0d 48 8d 7d 5c e8 47 9d 3a 00 85 c0 74 93 83 6b 58 <70> 63 69 30 30 30 30 3a 30 30 00 89 df e8 0e e1 ff ff 48 89 df 
    [    2.047203] RIP  [<ffff88003dad4300>] 0xffff88003dad42ff
    [    2.047203]  RSP <ffff880039ec7b78>
    [    2.047203] CR2: ffff88003dad4300
    [    2.047203] ---[ end trace 9ce56b15c18acfcb ]---
     ... [FAILED]
    :: Loading module ohci-hcd[    2.078186] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
     ... [  OK  ]
    :: Loading module uhci-hcd[    2.084727] uhci_hcd: USB Universal Host Controller Interface driver

    :

     

    Any idea why it's failing?

     

    Can anybody post a full working Proxmox config (/etc/pve/qemu-server/XXX.conf)?

     

    Thanks in advance for your help.

     

    Cheers.

    -r

     

     

     

     

  6. I found a solution which permits me to boot my USB stick :)

     

    Simply I created a CD image (.iso) with plop (https://www.plop.at/en/bootmanager/index.html) with the sole funtion of booting USB (similar to "chainloading" with grub2). I've attached the .iso here (just in case somebody needs it; happens that it also will work -not tested, though- even if your BIOS doesn't support USB boot at all -old BIOSes-).

     

    Now simply add a CDROM device to your Proxmox VM and select this .iso as image.

     

    Finally, configure: Options -> Boot order -> CDROM.

     

    You are done :)

     

    Whenever you start the VM, it will boot to cdrom, which in turn will jump into USB boot. Simple.

     

    The only (minor) drawback I've found with this method is that Jun's loader cannot hot-update its grub config/env (for any reason I don't still get, grub cannot write to disk [*]), so you cannot "save" the default choice in Jun's loader menu. But to be honest, it doesn't hurt too much (just edit Jun's loader .img "offline" and select another default if you need it).

     

    [*] You'll get an error by grub but you can ignore it. You'll also be prompted to press a key but you can ignore too (after ~5 secs, booting will resume automagically :-)). Btw, you can get rid of both error and press-key prompt by editing Jun's image and simply deleting (or renaming) grub/grubenv file ("ren grub/grubenv grub/grubenv_OFF" will do the trick). After doing so, Jun's loader (grub) won't autosave chosen menu option.

     

     

    plpbt-usbboot.iso

  7. Loader version and type: 1.03b  / 3617XS

    DSM version in use (including critical update):  None (kernel crash when booting from loader so I cannot install DSM)

    Using custom modules/ramdisk? If yes which one?:  None

    Hardware details: Proxmox on Hp Gen8.

     

    Problem: 1.03b loader fails to boot (kernel crash) when OVMF (UEFI) bios is selected. It works only when SeaBIOS is selected (which is Proxmox's default but it lacks features).

     

    Detailed info & logs in the following post:

     

     

  8. I've been iddle some time but I'm coming back with some responses I discovered by researching this a little bit.

     

    1/ In order to have a *full* serial console, you need to uncomment/comment these lines in grub.cfg:

    set extra_args_3617='earlycon=uart8250,io,0x3f8,115200n8 earlyprintk loglevel=15'
    #set extra_args_3617=''

    Then you can observe the complete boot process with a simple "qm terminal <vmid>".

     

    2/ When doing so, I discovered what was happening:

    [    0.000000] NX (Execute Disable) protection: active
    [    0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 3.10.105 #23739
    [    0.000000]  ffffffff814b6c18 ffffffff8187b1a1 0000000000000001 0000000000000001
    [    0.000000]  00000000366b1000 000000000194f000 0000000000000bff fffffffeffbcd000
    [    0.000000]  0000000100000000 0000000000000000 0000000000000000 000000000000000e
    [    0.000000] Call Trace:
    [    0.000000]  [<ffffffff814b6c18>] ? dump_stack+0xc/0x15
    [    0.000000]  [<ffffffff8187b1a1>] ? early_idt_handler_common+0x81/0xa8
    [    0.000000]  [<ffffffff8188c20e>] ? efi_init+0x238/0x476
    [    0.000000]  [<ffffffff8188c1fb>] ? efi_init+0x225/0x476
    [    0.000000]  [<ffffffff8187f091>] ? setup_arch+0x43d/0xc50
    [    0.000000]  [<ffffffff814b5f8b>] ? printk+0x4a/0x52
    [    0.000000]  [<ffffffff8187b957>] ? start_kernel+0x7b/0x3b0
    [    0.000000] RIP 0xfffffffeffbcd000

    I.e., I was getting a kernel-crash at the very beginning of the kernel-loading stage.

     

    I compared the crash with a normal kernel-loading, like this:

    [    0.000000] NX (Execute Disable) protection: active
    [    0.000000] SMBIOS 2.8 present.
    [    0.000000] DMI: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org 04/01/2014
    [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
    [    0.000000] e820: last_pfn = 0x1ffdf max_arch_pfn = 0x400000000

    ...

     

    So in the first case, kernel is crashing at BIOS check phase.

     

    I reviewed Proxmox VM config and I came across the root cause: 1.03b loader fails to boot when OVMF bios is selected. It works only when SeaBIOS is selected (which is Proxmox's default).

     

    Why am I currently using OVMF over SeaBIOS? Because only OVMF permits to permanently define a USB device as primary boot device, and I need this in order to boot from my USB stick.

     

    I've just emailed Jun with this info in order to know whether this is a known issue with 1.03b (the issue doesn't exist in 1.02b) and whether we could expect a fix.

     

    I'll update this post in case I have positive feedback :)

     

    Cheers,

    -r

  9. So are you confirming Proxmox's serial console works for you with 1.03b? (it didn't work for me).

     

    My VM already has serial console defined (so your 1st cmd isn't necessary).

    Could you run a "qm terminal 101" and tell me if that works for you? I think it should be equivalent to socat cmd.

     

    For me, it doesn't work either "qm terminal" nor socat, with 1.03b (it works if I boot with 1.02b, as I already commented in my post).

     

    Cheers,

    -r

     

     

  10. Hi,

     

    I have DSM 6.1 (1.02b loader) on HP Gen8. I'm using an usb stick (with synoboot.img burnt), which can work both on baremetal and Proxmox so I can switch between starting DSM on HP Gen8 without any virtualization layer, or starting DSM from Proxmox (running over HP Gen8). I'd recommend this environment so if your proxmox fails, you can pick up your phisical disks (I'm currently passing them thru to proxmox) and the usb stick and start directly in the server (even another new server!).

     

    What's the procedure to update to DSM 6.2? I thought that new 1.03b loader would support both DSM 6.2 (and 6.1) so my idea was to burn 1.03b loader, start DSM 6.1, test new loader in that environment, and finally upgrade DSM (via GUI). But I tried it and it isn't working, so maybe I'm wrong with that, and 1.03b only support 6.2. Could somebody confirm?

     

    And a second question: I was successfully using serial console on Proxmox to monitorize the booting process (qm terminal <vmid>) on 1.02b, but it seems not to work for 1.03b loader. Is this fact known? Any workaround?

     

    Thank you for your help.

  11. And you're probably right. This is specially true for freenas/zfs (where low-level optimizations are done by SO; hypervisor may affect).

     

    In case of xpenology, well, it's a simple Linux with software raid (then lvm + btrfs). If you monitor (smart) disks health from outside VM, you're done.

     

    Cheers,

    -r

     

     

    Enviado desde mi iPhone utilizando Tapatalk

  12. Please, open a new thread for installation/upgrade issues, This thread was supposed to be related to *PERFORMANCE*

     

    ===

     

    Btw, quick responses/ideas:

    1/ you can import Jun's ovf first on Vmware Workstation (a lot more flexible than ESXi) on your laptop, play on that (change VM compatibility, etc), and finally "upload" to esxi directly from vmware wks (there's an option for that). This way you will get .vmdk only file "translated" to vmdk + flat-vmdk files (which ESXi 6.5 uses).

    2/ For migration (DSM 6.0.2 -> 6.1), once you have full DSM 6.1 vm uploaded to ESXi 6.5, then pick up 1st disk (2 files: vmdk + flat) and copy to "legacy DSM" vm dir, then create a new disk with "opening existing disk". Finally change boot priority or best: simply edit vm hw and change port number so your new boot disk start the vm instead of old DSM boot disk (you can destroy oldest boot disk if you prefer). Upon starting vm, you'll get into DSM migration wizard (DSM will detect you're migrating).

    3/ DSM migration wizard has 2 choices: 1/ try to preserve config&data; or 2/ only preserve data but not config. I did a quick test with 1, on another vm (with fake data), and it failed (migration seems ok but after rebooting I don't get IP address). So finally I upgraded using the "only preserve data" choice (you'll loose configs!!!!!) and it worked.

     

    ===

     

    Again, please, be so kind to open a NEW thread for installation issues. This was not the purpose of this thread and I don't have any valid answer regarding the original question: performance.

     

    Thanks.

  13. Hi,

     

    I have a HP Gen8 Microserver with upgraded CPU&RAM (Xeon + 16GB RAM), running ESXi 6.5 so I installed Xpenology/DSM 6.1 (yes, new version) in a VM (with Jun's 1.02a loader).

     

    I've attached 3 WD Red disks, in *AHCI* mode, and I've configured them in the VM as RDM disks (I don't have extra sata card in order to use VTd/Passthrough).

     

    After solving a first huge performance problem (horrible 2 MB/s speed!!!), by disabling Vmware AHCI driver and enabling legacy one (full story here: http://www.nxhut.com/2016/11/fix-slow-d ... wahci.html), these are the current speeds I'm getting *inside* DSM:

     

    Read:

    - iops: 109

    - performance: 154 MB/s

    - latency: 16.2 ms

    Write:

    - iops: 94

    - performance: 35 MB/s

    - latency: 17.6 ms

     

    (data obtained using DSM 6.1: Storage admin -> HDD/SSD -> Test bank)

     

    For me, 154 MB/s read is ok and according to WD Red specs. But, isn't 35 MB/s write quite slow????

     

    Are this values correct for you? Which values are you getting on WD Red disks?

     

    Please, could you complete this thread providing your values, and specifying:

    - virtualization / baremetal (eg: esxi, vbox, baremetal)

    - hw specs or server model

    - disk model

     

    Thank you.

     

    Cheers,

    -r

  14. Hi,

     

    Just created a VM in vmware workstation for testing xpenology (with the idea of moving to ESXi if test is ok):

    - hw type: workstation 11.x (esxi compatible)

    - sata disk: synoboot.vmdk (DS3615xs 6.0.2 Jun's Mod V1.01)

    - sata disk 2: new disk (8gb)

    - serial port: named pipe (only to have a look to console)

     

    With former config, I can boot xpenology and do basic install (DSM_DS3615xs_8451.pat) / config. I had to use option 1 from Jun's menu (yes, baremetal even being a vm!!); if esxi option is used, DSM doesn´t detect any disk and it's impossible to proceed with DSM install).

     

    Upon having a basic install, I shutdown VM.

     

    Then I added virtual hw:

    - sata disk 3: new disk (2gb)

    - sata disk 4: new disk (2gb)

    - sata disk 5: new disk (2gb)

     

    The problem is that I cannot init any of those 3 disks in storage manager. In particular, if I try to create a RAID group, I get this error:

    "System failed to create [RAID Group 1](Device Type is [basic]) with disk [5]."

    I also noticed that, during former raid creation process, DSM is showing a wrong capacity (tons of TBs instead of 2 gb capacity).

    I tried all kinds of different RAIDs (5, etc) but the problem is with those 3 disks, which btw are similar to disk2 (8gb) I created for testing (same kind of virtual sata device).

     

    I only can create a RAID group using disk2 (which is where DSM resides, and was init during DSM installation).

     

    Any ideas? What's going on?

     

    I'd appreciate some help, please,

     

    Cheers,

    -r

×
×
  • Create New...