Jump to content
XPEnology Community

mcdull

Member
 View Profile  See their activity

  • Posts

    252

  • Joined

  • Last visited

  • Days Won

    4

 Content Type 

Posts posted by mcdull

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted · Edited by mcdull

    1 hour ago, ThorGroup said:

    Can you post the full dmesg? I also see your RTC is not working - did you pull the newest release? The one you're using seems to be lacking RTC support.

     

    I have used the redpill toolchain v0.4 and force switch to the original repo instead of jumkey's one.

    The full dmesg is attached.  nothing with boot_device_shim, and no rtc.

    DSM7_918dmesg.txt

     

    I have also tried apollolake + 6.2.4, the same.

    In short, 3615 works fine, 918 do not.

     

    p.s. the same proxmox is running a DS918 with jun's loader rock solid.

     

    For comparison, I also attached the dmesg of 3615 DSM 6.2.4. The file is much larger as it is a full boot to the DSM.

    DSM624_3615_dmesgout.txt

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted · Edited by mcdull

    1 hour ago, ThorGroup said:

    Can you post the full dmesg? I also see your RTC is not working - did you pull the newest release? The one you're using seems to be lacking RTC support.

    I uses redpill toolchain v0.4 and seems it pull the latest release.  

    I will do it all over again and post the dmesg. 

     

    umm after checking the source, redpill toolchain do switch to another repo as below if configurated for DSM 7.0

    https://github.com/jumkey/redpill-load.git

     

    I will revert to 6.2.4 and test again. Until the RedPill-TTG repo support DSM7, I will test DSM7 again.

     

     

    Update:

    Tested with DSM 6.2.4 and 3615 version and the synoboot mounts correctly.

     

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted · Edited by mcdull

    1 hour ago, ThorGroup said:

    Do you see any usb devices in the preboot system? If there's nothing reported by grepping vid (you can also try grepping for "boot_device_shim") it's probably not seeing your usb stick at all.

    you are right, nothing with boot_device_shim.

    but I am using proxmox, and this should not be an expected behaviour, right?  Although I am using AMD CPU and qmeu64 as machine type.

      

    [    5.762165] usb-storage 2-1:1.0: USB Mass Storage device detected
[    5.764347] scsi host12: usb-storage 2-1:1.0

    However, the DSM itself should see the usb mass storage. 

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted

    37 minutes ago, gadreel said:

    @ThorGroup Thanks for clarifying. The Jun's loader had support for AMD?

     

    Ok, I managed to get the output and it fails at:

     

    :: Loading module syno_hddmon ... [FAILED]

     

      

    
[    1.017935] console [ttyS2] enabled
[    1.019129] bootconsole [uart0] disabled
[    1.255514] serial8250: ttyS2 at I/O 0x3e8 (irq = 4, base_baud = 115200) is a 16550A
[    1.257050] Linux agpgart interface v0.103
[    1.263322] brd: module loaded
[    1.263982] lpc_ich 0000:00:1f.0: I/O space for GPIO uninitialized
[    1.265249] Loading iSCSI transport class v2.0-870.
[    1.272651] ahci 0000:00:1f.2: version 3.0
[    1.273585] ACPI: PCI Interrupt Link [GSIA] enabled at IRQ 16
[    1.275276] ahci 0000:00:1f.2: AHCI 0001.0000 32 slots 6 ports 1.5 Gbps 0x3f impl SATA mode
[    1.276760] ahci 0000:00:1f.2: flags: 64bit ncq only 
[    1.290446] scsi host0: ahci
[    1.302461] scsi host1: ahci
[    1.313839] scsi host2: ahci
[    1.317903] scsi host3: ahci
[    1.319242] scsi host4: ahci
[    1.320234] scsi host5: ahci
[    1.320795] ata1: SATA max UDMA/133 abar m4096@0xfc81a000 port 0xfc81a100 irq 28
[    1.322134] ata2: SATA max UDMA/133 abar m4096@0xfc81a000 port 0xfc81a180 irq 28
[    1.323483] ata3: SATA max UDMA/133 abar m4096@0xfc81a000 port 0xfc81a200 irq 28
[    1.324674] ata4: SATA max UDMA/133 abar m4096@0xfc81a000 port 0xfc81a280 irq 28
[    1.325786] ata5: SATA max UDMA/133 abar m4096@0xfc81a000 port 0xfc81a300 irq 28
[    1.326956] ata6: SATA max UDMA/133 abar m4096@0xfc81a000 port 0xfc81a380 irq 28
[    1.633227] ata1: SATA link down (SStatus 0 SControl 300)
[    1.634898] ata1: Disk is present for SATA link down event
[    1.941312] ata2: SATA link down (SStatus 0 SControl 300)
[    1.943332] ata2: No present pin info for SATA link down event
[    2.249258] ata3: SATA link down (SStatus 0 SControl 300)
[    2.250877] ata3: No present pin info for SATA link down event
[    2.557239] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    2.559248] ata4.00: ATA-7: QEMU HARDDISK, 2.5+, max UDMA/100
[    2.560943] ata4.00: 41943040 sectors, multi 16: LBA48 NCQ (depth 31/32)
[    2.562099] ata4.00: SN:QM00007
[    2.562555] ata4.00: applying bridge limits
[    2.563310] ata4.00: configured for UDMA/100
[    2.563997] ata4.00: Find SSD disks. [QEMU HARDDISK]
[    2.564843] I/O scheduler elevator not found
[    2.565697] scsi 3:0:0:0: Direct-Access     QEMU     HARDDISK                 2.5+ PQ: 0 ANSI: 5
[    2.567201] sd 3:0:0:0: [sdd] 41943040 512-byte logical blocks: (21.5 GB/20.0 GiB)
[    2.568664] sd 3:0:0:0: [sdd] Write Protect is off
[    2.569555] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[    2.570514] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.572490]  sdd: sdd1 sdd2
[    2.573272] sd 3:0:0:0: [sdd] Attached SCSI disk
[    2.872266] ata5: SATA link down (SStatus 0 SControl 300)
[    2.874765] ata5: No present pin info for SATA link down event
[    3.180240] ata6: SATA link down (SStatus 0 SControl 300)
[    3.181836] ata6: No present pin info for SATA link down event
[    3.183832] i2c /dev entries driver
[    3.185258] i801_smbus 0000:00:1f.3: SMBus using polling
[    3.186805] md: raid1 personality registered for level 1
[    3.187856] NET: Registered protocol family 17
[    3.188679] Key type dns_resolver registered
[    3.189478] mce: Unable to init device /dev/mcelog (rc: -5)
[    3.190802] registered taskstats version 1
[    3.191584] Loading compiled-in untrusted X.509 certificates
[    3.192622] Loading compiled-in X.509 certificates
[    3.193530] Loaded X.509 cert 'Synology SDG kernel module signing key: 7bd0b0d6bcd31651c22ce3978bdc8c8bdc417329'
[    3.195837] Loaded X.509 cert 'Synology Root Certification Authority: f2c075361f168425f8b5ef31b796406c3aab2089'
[    3.197586] Loaded X.509 cert 'Synology Kernel Module Signing Certification Authority: 600839b5d127e0e11d817a31f0575d323a7c0e28'
[    3.199339] Loaded X.509 cert 'Synology kernel module signing key: 4646ce54489669338118a3b1286da156ac366fa5'
[    3.200784] page_owner is disabled
[    3.201368] AppArmor: AppArmor sha1 policy hashing enabled
[    3.202754] hctosys: unable to open rtc device (rtc0)
[    3.204931] Freeing unused kernel memory: 916K
[    3.205645] Write protecting the kernel read-only data: 8192k
[    3.206977] Freeing unused kernel memory: 508K
[    3.208267] Freeing unused kernel memory: 300K
START /linuxrc.syno
START /linuxrc.syno.impl
[    3.213752] redpill: loading out-of-tree module taints kernel.
[    3.214694] redpill: module verification failed: signature and/or required key missing - tainting kernel
[    3.216358] <redpill/redpill_main.c:24> ================================================================================================
[    3.218496] <redpill/redpill_main.c:25> RedPill loading...
[    3.220185] <redpill/call_protected.c:65> Got addr ffffffff812041e0 for cmdline_proc_show
[    3.221409] <redpill/cmdline_delegate.c:266> Cmdline count: 329
[    3.222321] <redpill/cmdline_delegate.c:310> Cmdline: BOOT_IMAGE=/zImage mac1=00505623F398 netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=1 vid=0x46f4 syno_hdd_detect=0 pid=0x0001 console=ttyS2,115200n8 elevator=elevator sn=1780PDN123456 root=/dev/md0 earlyprintk loglevel=15 syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS918+ vender_format_version=2
[    3.222321] 
[    3.227503] <redpill/cmdline_delegate.c:321> Param #0: |BOOT_IMAGE=/zImage|
[    3.228562] <redpill/cmdline_delegate.c:248> Option "BOOT_IMAGE=/zImage" not recognized - ignoring
[    3.229901] <redpill/cmdline_delegate.c:321> Param #1: |mac1=00505623F398|
[    3.230948] <redpill/cmdline_delegate.c:236> Set MAC #1: 00505623F398
[    3.231935] <redpill/cmdline_delegate.c:321> Param #2: |netif_num=1|
[    3.232995] <redpill/cmdline_delegate.c:191> Declared network ifaces # as 1
[    3.234122] <redpill/cmdline_delegate.c:321> Param #3: |earlycon=uart8250,io,0x3f8,115200n8|
[    3.235385] <redpill/cmdline_delegate.c:248> Option "earlycon=uart8250,io,0x3f8,115200n8" not recognized - ignoring
[    3.236904] <redpill/cmdline_delegate.c:321> Param #4: |syno_hdd_powerup_seq=1|
[    3.238022] <redpill/cmdline_delegate.c:248> Option "syno_hdd_powerup_seq=1" not recognized - ignoring
[    3.239436] <redpill/cmdline_delegate.c:321> Param #5: |vid=0x46f4|
[    3.240414] <redpill/cmdline_delegate.c:75> VID override: 0x46f4
[    3.241355] <redpill/cmdline_delegate.c:321> Param #6: |syno_hdd_detect=0|
[    3.242403] <redpill/cmdline_delegate.c:248> Option "syno_hdd_detect=0" not recognized - ignoring
[    3.243734] <redpill/cmdline_delegate.c:321> Param #7: |pid=0x0001|
[    3.244719] <redpill/cmdline_delegate.c:110> PID override: 0x0001
[    3.245670] <redpill/cmdline_delegate.c:321> Param #8: |console=ttyS2,115200n8|
[    3.246780] <redpill/cmdline_delegate.c:248> Option "console=ttyS2,115200n8" not recognized - ignoring
[    3.248207] <redpill/cmdline_delegate.c:321> Param #9: |elevator=elevator|
[    3.249288] <redpill/cmdline_delegate.c:248> Option "elevator=elevator" not recognized - ignoring
[    3.250622] <redpill/cmdline_delegate.c:321> Param #10: |sn=1780PDN123456|
[    3.251659] <redpill/cmdline_delegate.c:40> S/N set to: 1780PDN123456
[    3.252644] <redpill/cmdline_delegate.c:321> Param #11: |root=/dev/md0|
[    3.253656] <redpill/cmdline_delegate.c:248> Option "root=/dev/md0" not recognized - ignoring
[    3.254921] <redpill/cmdline_delegate.c:321> Param #12: |earlyprintk|
[    3.255901] <redpill/cmdline_delegate.c:248> Option "earlyprintk" not recognized - ignoring
[    3.257206] <redpill/cmdline_delegate.c:321> Param #13: |loglevel=15|
[    3.258187] <redpill/cmdline_delegate.c:248> Option "loglevel=15" not recognized - ignoring
[    3.259448] <redpill/cmdline_delegate.c:321> Param #14: |syno_port_thaw=1|
[    3.260493] <redpill/cmdline_delegate.c:162> Port thaw set to: 1
[    3.261423] <redpill/cmdline_delegate.c:321> Param #15: |HddHotplug=0|
[    3.262489] <redpill/cmdline_delegate.c:248> Option "HddHotplug=0" not recognized - ignoring
[    3.263747] <redpill/cmdline_delegate.c:321> Param #16: |withefi|
[    3.264723] <redpill/cmdline_delegate.c:248> Option "withefi" not recognized - ignoring
[    3.265947] <redpill/cmdline_delegate.c:321> Param #17: |syno_hw_version=DS918+|
[    3.267099] <redpill/cmdline_delegate.c:20> HW version set to: DS918+
[    3.268073] <redpill/cmdline_delegate.c:321> Param #18: |vender_format_version=2|
[    3.269217] <redpill/cmdline_delegate.c:248> Option "vender_format_version=2" not recognized - ignoring
[    3.270610] <redpill/cmdline_delegate.c:285> Add cmdline blacklist "vid=" @ 0
[    3.271696] <redpill/cmdline_delegate.c:286> Add cmdline blacklist "pid=" @ 1
[    3.272773] <redpill/cmdline_delegate.c:287> Add cmdline blacklist "mfg" @ 2
[    3.273846] <redpill/cmdline_delegate.c:288> Add cmdline blacklist "loglevel=" @ 3
[    3.274984] <redpill/cmdline_delegate.c:289> Add cmdline blacklist "elevator=" @ 4
[    3.276182] <redpill/cmdline_delegate.c:290> Add cmdline blacklist "earlyprintk" @ 5
[    3.277355] <redpill/cmdline_delegate.c:291> Add cmdline blacklist "syno_port_thaw=" @ 6
[    3.278561] <redpill/cmdline_delegate.c:338> CmdLine processed successfully, tokens=19
[    3.279737] <redpill/runtime_config.c:122> Found platform definition for "DS918+"
[    3.280914] <redpill/runtime_config.c:133> Validating runtime config...
[    3.281926] <redpill/runtime_config.c:142> Config validation resulted in OK
[    3.282992] <redpill/runtime_config.c:159> Runtime config populated
[    3.286091] <redpill/call_protected.c:81> Got addr ffffffff81928292 for early_serial_setup
[    3.287350] kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
[    3.288341] BUG: unable to handle kernel paging request at ffffffff81928292
[    3.288341] IP: [<ffffffff81928292>] early_serial_setup+0x0/0x150
[    3.288341] PGD 180d067 PUD 180e063 PMD 2768ad063 PTE 8000000001928163
[    3.288341] Oops: 0011 [#1] SMP 
[    3.288341] Modules linked in: redpill(OE+)
[    3.288341] CPU: 3 PID: 3836 Comm: insmod Tainted: G           OE   4.4.180+ #41890
[    3.288341] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org 04/01/2014
[    3.288341] task: ffff88026b995940 ti: ffff880036104000 task.ti: ffff880036104000
[    3.288341] RIP: 0010:[<ffffffff81928292>]  [<ffffffff81928292>] early_serial_setup+0x0/0x150
[    3.288341] RSP: 0018:ffff880036107b38  EFLAGS: 00010246
[    3.288341] RAX: ffffffff81928292 RBX: ffff880036107b58 RCX: 00000000000001fa
[    3.288341] RDX: 0000000000000001 RSI: 0000000000000246 RDI: ffff880036107b58
[    3.288341] RBP: ffff880036107b48 R08: 6c6c69706465723c R09: 00000000000001fa
[    3.288341] R10: ffffffff816fab40 R11: 65746365746f7270 R12: ffff8800365e65e0
[    3.288341] R13: 0000000000000000 R14: ffffffffa0012000 R15: ffff880272ad5600
[    3.288341] FS:  00007f6b9677d740(0000) GS:ffff88027fd80000(0000) knlGS:0000000000000000
[    3.288341] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    3.288341] CR2: ffffffff81928292 CR3: 00000002747bd000 CR4: 00000000003406b0
[    3.288341] Stack:
[    3.288341]  ffffffffa000107c 0000000000000000 ffff880036107cd0 ffffffffa00071f3
[    3.288341]  0000000000000000 00000000000003f8 0000000000000000 0000000000000000
[    3.288341]  0000000000000000 0000000000000000 0000000000000000 0000000000000000
[    3.288341] Call Trace:
[    3.288341]  [<ffffffffa000107c>] ? _early_serial_setup+0x1c/0xa0 [redpill]
[    3.288341]  [<ffffffffa00071f3>] fix_muted_ttyS0+0x53/0xc0 [redpill]
[    3.288341]  [<ffffffffa00072ab>] register_uart_fixer+0x1b/0x90 [redpill]
[    3.288341]  [<ffffffffa001207b>] init_redpill+0x7b/0x143 [redpill]
[    3.288341]  [<ffffffff810003b8>] do_one_initcall+0x88/0x1a0
[    3.288341]  [<ffffffff8116daaa>] ? __vunmap+0x9a/0xf0
[    3.288341]  [<ffffffff811305d3>] do_init_module+0x5a/0x1bf
[    3.288341]  [<ffffffff810cb1a0>] load_module+0x1ca0/0x22b0
[    3.288341]  [<ffffffff810c80b0>] ? __symbol_put+0x40/0x40
[    3.288341]  [<ffffffff810cb981>] SYSC_finit_module+0x81/0xa0
[    3.288341]  [<ffffffff810cb9b9>] SyS_finit_module+0x9/0x10
[    3.288341]  [<ffffffff8157998a>] entry_SYSCALL_64_fastpath+0x1e/0x8e
[    3.288341] Code: cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc <cc> cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc 
[    3.288341] RIP  [<ffffffff81928292>] early_serial_setup+0x0/0x150
[    3.288341]  RSP <ffff880036107b38>
[    3.288341] CR2: ffffffff81928292
[    3.288341] ---[ end trace cc15cf19e1dc28a8 ]---
Killed
Insert basic USB modules...
:: Loading module usb-common ... [  OK  ]
:: Loading module usbcore[    3.364522] ACPI: bus type USB registered
[    3.365224] usbcore: registered new interface driver usbfs
[    3.366276] usbcore: registered new interface driver hub
[    3.367316] usbcore: registered new interface driver ethub
[    3.368343] usbcore: registered new device driver usb
 ... [  OK  ]
:: Loading module xhci-hcd ... [  OK  ]
:: Loading module xhci-pci[    3.382130] xhci_hcd 0000:00:07.0: xHCI Host Controller
[    3.383276] xhci_hcd 0000:00:07.0: new USB bus registered, assigned bus number 1
[    3.584961] xhci_hcd 0000:00:07.0: hcc params 0x00087001 hci version 0x100 quirks 0x00000010
[    3.587087] hub 1-0:1.0: USB hub found
[    3.587819] hub 1-0:1.0: 15 ports detected
[    3.589196] xhci_hcd 0000:00:07.0: xHCI Host Controller
[    3.590282] xhci_hcd 0000:00:07.0: new USB bus registered, assigned bus number 2
[    3.591936] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    3.593823] hub 2-0:1.0: USB hub found
[    3.594737] hub 2-0:1.0: 15 ports detected
 ... [  OK  ]
:: Loading module usb-storage[    3.605934] usbcore: registered new interface driver usb-storage
 ... [  OK  ]
Insert net driver(Mindspeed only)...
[    3.614145] apollolake_synobios: module license 'Synology Inc.' taints kernel.
[    3.615860] synobios open /dev/ttyS1 success
[    3.616590] WARNING: inconsistent syno gpio info, hdd detect
[    3.617520] correction with 0x00
[    3.617983] 1900-1-0 0:0:0 UTC
[    3.618490] synobios: load, major number 201
[    3.619185] Brand: Synology
[    3.619626] Model: DS-918+
[    3.620096] This is default settings: set group disks wakeup number to 1, spinup time deno 1
[    3.621377] synobios cpu_arch proc entry initialized
[    3.622200] synobios crypto_hw proc entry initialized
[    3.622921] synobios syno_platform proc entry initialized
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
[    3.627371] Module [apollolake_synobios] is removed. 
[    3.628204] synobios: unload
insmod: can't insert '/lib/modules/virtio-rng.ko': No such file or directory
Assemble args: -u 323c41e0:4c6e4857:3017a5a8:c86610be /dev/sdd1
[    3.669883] md: md0 stopped.
[    3.671210] md: bind<sdd1>
[    3.672135] md/raid1:md0: active with 1 out of 16 mirrors
[    3.678975] md0: detected capacity change from 0 to 2549940224
mdadm: /dev/md0 has been started with 1 drive (out of 16).
Partition Version=8
 /sbin/e2fsck exists, checking /dev/md0... 
e2fsck 1.44.1 (24-Mar-2018)
/sbin/e2fsck -yvf returns 0
Mounting /dev/md0 /tmpRoot
[    3.714786] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[    3.721941] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
------------upgrade
Begin upgrade procedure
Mount data partition: /dev/md0 -> /tmpData
No upgrade file exists
End upgrade procedure
[    3.912112] usb 1-2: new high-speed USB device number 2 using xhci_hcd
[    4.171305] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
[    4.186561] usb-storage 2-1:1.0: USB Mass Storage device detected
[    4.188733] scsi host6: usb-storage 2-1:1.0
============upgrade
------------bootup-smallupdate
Try bootup smallupdate
chroot: can't execute '/usr/syno/sbin/synoupgrade': No such file or directory
Failed to synoupgrade --bootup-smallupdate [127]
Exit on error [6] bootup-smallupdate failed...
Tue Aug 10 04:06:32 UTC 2021
/dev/md0 /tmpRoot ext4 rw,relatime,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
umount: /etc/mtab: No such file or directory
linuxrc.syno failed on 6
starting pid 4566, tty '': '/etc/rc'
:: Starting /etc/rc
:: Mounting procfs ... [  OK  ]
:: Mounting tmpfs ... [  OK  ]
:: Mounting devtmpfs ... [  OK  ]
:: Mounting devpts ... [  OK  ]
:: Mounting sysfs ... [  OK  ]
[    4.887949] random: syno_swap_ctl: uninitialized urandom read (4 bytes read, 108 bits of entropy available)
[    4.893773] md: md1 stopped.
[    4.895279] md: bind<sdd2>
[    4.895954] md/raid1:md1: active with 1 out of 16 mirrors
[    4.902636] md1: detected capacity change from 0 to 2147418112
[    4.912786] Adding 2097084k swap on /dev/md1.  Priority:-1 extents:1 across:2097084k 
:: Loading module fat ... [  OK  ]
:: Loading module vfat ... [  OK  ]
:: Loading module udp_tunnel ... [  OK  ]
:: Loading module ip6_udp_tunnel ... [  OK  ]
:: Loading module vxlan ... [  OK  ]
:: Loading module e1000e[    4.983863] e1000e: Intel(R) PRO/1000 Network Driver - 3.4.2.4-NAPI
[    4.985437] e1000e: Copyright(c) 1999 - 2019 Intel Corporation.
[    4.987196] e1000e 0000:01:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[    5.029655] random: nonblocking pool is initialized
[    5.036352] e1000e 0000:01:00.0 0000:01:00.0 (uninitialized): registered PHC clock
[    5.093370] e1000e 0000:01:00.0 eth0: (PCI Express:2.5GT/s:Width x1) 00:50:56:23:f3:98
[    5.094825] e1000e 0000:01:00.0 eth0: Intel(R) PRO/1000 Network Connection
[    5.096178] e1000e 0000:01:00.0 eth0: MAC: 3, PHY: 8, PBA No: 000000-000
 ... [  OK  ]
:: Loading module i2c-algo-bit ... [  OK  ]
:: Loading module igb[    5.104482] Intel(R) Gigabit Ethernet Linux Driver - version 5.3.5.22
[    5.105750] Copyright(c) 2007 - 2018 Intel Corporation.
 ... [  OK  ]
:: Loading module r8168 ... [  OK  ]
:: Loading module sunrpc[    5.123875] RPC: Registered named UNIX socket transport module.
[    5.124985] RPC: Registered udp transport module.
[    5.125913] RPC: Registered tcp transport module.
[    5.126799] RPC: Registered tcp NFSv4.1 backchannel transport module.
 ... [  OK  ]
:: Loading module grace ... [  OK  ]
:: Loading module lockd ... [  OK  ]
:: Loading module nfs ... [  OK  ]
:: Loading module nfsv3 ... [  OK  ]
[    5.148904] synobios open /dev/ttyS1 success
[    5.149644] WARNING: inconsistent syno gpio info, hdd detect
[    5.150712] correction with 0x00
[    5.151294] 1900-1-0 0:0:0 UTC
[    5.151757] synobios: load, major number 201
[    5.152537] Brand: Synology
[    5.153041] Model: DS-918+
[    5.153493] This is default settings: set group disks wakeup number to 1, spinup time deno 1
[    5.154825] synobios cpu_arch proc entry initialized
[    5.155712] synobios crypto_hw proc entry initialized
[    5.156540] synobios syno_platform proc entry initialized
mknod: /dev/synobios: File exists
Starting SW init...
[    5.159360] Invalid disk Number [9]
[    5.160275] Invalid disk Number [10]
[    5.161040] Invalid disk Number [11]
[    5.161574] Invalid disk Number [12]
[    5.162171] Invalid disk Number [13]
[    5.162690] Invalid disk Number [14]
[    5.163352] Invalid disk Number [15]
[    5.163868] Invalid disk Number [16]
[    5.192381] I/O scheduler elevator not found
[    5.194539] scsi 6:0:0:0: Direct-Access     QEMU     QEMU HARDDISK            2.5+ PQ: 0 ANSI: 5
[    5.196828] I/O scheduler elevator not found
[    5.198069] sd 6:0:0:0: [sdq] 262144 512-byte logical blocks: (134 MB/128 MiB)
[    5.199817] sd 6:0:0:0: [sdq] Write Protect is off
[    5.200828] sd 6:0:0:0: [sdq] Mode Sense: 63 00 00 08
[    5.202147] sd 6:0:0:0: [sdq] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    5.204763]  sdq: sdq1 sdq2 sdq3
[    5.206434] sd 6:0:0:0: [sdq] Attached SCSI disk
[    5.769882] Module [apollolake_synobios] is removed. 
[    5.770707] synobios: unload
:: Loading module synobios[    5.791466] synobios open /dev/ttyS1 success
[    5.792610] WARNING: inconsistent syno gpio info, hdd detect
[    5.793773] correction with 0x00
[    5.794319] 1900-1-0 0:0:0 UTC
[    5.794761] synobios: load, major number 201
[    5.795448] Brand: Synology
[    5.795915] Model: DS-918+
[    5.796386] This is default settings: set group disks wakeup number to 1, spinup time deno 1
[    5.797667] synobios cpu_arch proc entry initialized
[    5.798474] synobios crypto_hw proc entry initialized
[    5.799274] synobios syno_platform proc entry initialized
 ... [  OK  ]
[    6.024130] e1000e 0000:01:00.0 eth0: MSI interrupt test failed, using legacy interrupt.
udhcpc: started, v1.30.1
[    6.399809] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
eth0      Link encap:Ethernet  HWaddr 00:50:56:23:F3:98  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:437 (437.0 B)  TX bytes:60 (60.0 B)
          Interrupt:22 Memory:fc640000-fc660000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

:: Starting syslogd ... [  OK  ]
:: Starting scemd
[   12.061743] Invalid disk Number [9]
[   12.062849] Invalid disk Number [10]
[   12.063947] Invalid disk Number [11]
[   12.064992] Invalid disk Number [12]
[   12.065552] Invalid disk Number [13]
[   12.066117] Invalid disk Number [14]
[   12.066641] Invalid disk Number [15]
[   12.067210] Invalid disk Number [16]
:: Starting services in background
Starting findhostd in flash_rd...
Starting services in flash_rd...
Running /usr/syno/etc/rc.d/J01httpd.sh...
Starting httpd:80 in flash_rd...
Starting httpd:5000 in flash_rd...
Running /usr/syno/etc/rc.d/J03ssdpd.sh...
[   14.195266] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
/usr/bin/minissdpd -i eth0
(15): upnp:rootdevice
(51): uuid:upnp_SynologyNAS-00505623f398::upnp:rootdevice
(56): Synology/synology_apollolake_918+/7.0-41890/192.168.0.49
(45): http://192.168.0.49:5000/description-eth0.xml
Connected.
done.
/usr/syno/bin/reg_ssdp_service 192.168.0.49 00505623f398 7.0-41890 synology_apollolake_918+ eth0
[   14.209875] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Running /usr/syno/etc/rc.d/J04synoagentregisterd.sh...
Starting synoagentregisterd...
Running /usr/syno/etc/rc.d/J30DisableNCQ.sh...
[   14.242610] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Running /usr/syno/etc/rc.d/J80ADTFanControl.sh...
Running /usr/syno/etc/rc.d/J98nbnsd.sh...
Starting nbnsd...
Running /usr/syno/etc/rc.d/J99avahi.sh...
[   14.248544] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Starting Avahi mDNS/DNS-SD Daemon
cname_load_conf failed:/var/tmp/nginx/avahi-aliases.conf
[   14.264534] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[   14.270245] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
:: Loading module hid ... [  OK  ]
:: Loading module usbhid[   14.286853] usbcore: registered new interface driver usbhid
[   14.287888] usbhid: USB HID core driver
 ... [  OK  ]
:: Loading module syno_hddmon ... [FAILED]
Excution Error
============ Date ============
Tue Aug 10 04:06:42 UTC 2021
==============================
starting pid 5868, tty '': '/sbin/getty 115200 console'

Tue Aug 10 04:06:42 2021

DiskStation login:

     

    Yours is another issue.  You have completed the boot process.

    The major issue is missing LAN adaptor. There are no network from the e1000e.

    I uses Virt-io network which obtain fine.  (but I use a correct mac address and serial number)

     

    anyway, you can login "root" without password to see more from /var/log/messages

     

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted · Edited by mcdull

      

    [    0.000000] Command line: BOOT_IMAGE=/zImage mac1=001122334455 netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=1 vid=0xF400 syno_hdd_detect=0 pid=0xF400 console=ttyS2,115200n8 elevator=elevator sn=2000PDN000000 root=/dev/md0 earlyprintk loglevel=15 syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS918+ vender_format_version=2
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] Kernel command line: BOOT_IMAGE=/zImage mac1=001122334455 netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=1 vid=0xF400 syno_hdd_detect=0 pid=0xF400 console=ttyS2,115200n8 elevator=elevator sn=2000PDN000000 root=/dev/md0 earlyprintk loglevel=15 syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS918+ vender_format_version=2
[    5.083969] <redpill/cmdline_delegate.c:310> Cmdline: BOOT_IMAGE=/zImage mac1=001122334455 netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=1 vid=0xF400 syno_hdd_detect=0 pid=0xF400 console=ttyS2,115200n8 elevator=elevator sn=2000PDN000000 root=/dev/md0 earlyprintk loglevel=15 syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS918+ vender_format_version=2
[    5.092919] <redpill/cmdline_delegate.c:321> Param #5: |vid=0xF400|
[    5.109385] <redpill/cmdline_delegate.c:285> Add cmdline blacklist "vid=" @ 0

     

    Whatever vid/pid I use, it only reports the quoted lines that "matches" my specified vid/pid.

    So I guess the important message where the redpill see which vid/pid is missing in my log.

     

    For whatever vid/pid I tried, it fails with this statement

    (f400:f400) (46f4:0001), capital letters or small..

    Jan  1 00:00:49 updater: boot/boot_lock.c(228): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:2)

     

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted

    3 hours ago, gadreel said:

    @kelvin701 I managed to boot it from Unraid using haydibe v4. The previous bootloader from Jun was booting using OVMF Bios but the new bootloader I had to use SeaBios to make it work. OVMF just takes me back to bios...no idea why is that. :)

    Attached a screen of what I selected...

    image.thumb.png.0a7e78f6a2e15289e58b515b10dcc932.png

     

    Unfortunately though when I try to install it will stuck at 55% with the message "Failed to install the file. The file is corrupted." I am not an expert but when I use virsh console VM_NAME I have the following output... I do not know if that will help ThorGroup in any way...

     

    I do not know if somebody else knows a better command to connect to the Virtual Serial port from Qemu to get more output during installation...

      

    
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.180+ (root@build15) (gcc version 7.5.0 (GCC) ) #41890 SMP Thu Jul 15 03:43:42 CST 2021
[    0.000000] Command line: BOOT_IMAGE=/zImage mac1=XXXXXXXXX netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=1 vid=0x46f4 syno_hdd_detect=0 pid=0x0001 console=ttyS2,115200n8 elevator=elevator sn=XXXXXXXXX root=/dev/md0 earlyprintk loglevel=15 syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS918+ vender_format_version=2
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000] CPU: vendor_id 'AuthenticAMD' unknown, using generic init.
[    0.000000] CPU: Your system may be unstable.
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
[    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000007ffddfff] usable
[    0.000000] BIOS-e820: [mem 0x000000007ffde000-0x000000007fffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000027fffffff] usable
[    0.000000] earlycon: Early serial console at I/O port 0x3f8 (options '115200n8')
[    0.000000] bootconsole [uart0] enabled
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] SMBIOS 2.8 present.
[    0.000000] DMI: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org 04/01/2014
[    0.000000] Kernel/User page tables isolation: disabled
[    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000000] e820: last_pfn = 0x280000 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 00C0000000 mask FFC0000000 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] x86/PAT: Configuration [0-7]: WB  WT  UC- UC  WB  WT  UC- UC  
[    0.000000] e820: last_pfn = 0x7ffde max_arch_pfn = 0x400000000
[    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 28672
[    0.000000] Using GB pages for direct mapping
[    0.000000] BRK [0x01a6c000, 0x01a6cfff] PGTABLE
[    0.000000] BRK [0x01a6d000, 0x01a6dfff] PGTABLE
[    0.000000] BRK [0x01a6e000, 0x01a6efff] PGTABLE
[    0.000000] RAMDISK: [mem 0x35917000-0x36c82fff]
[    0.000000] ACPI: Early table checksum verification disabled
[    0.000000] ACPI: RSDP 0x00000000000F58B0 000014 (v00 BOCHS )
[    0.000000] ACPI: RSDT 0x000000007FFE2148 000034 (v01 BOCHS  BXPCRSDT 00000001 BXPC 00000001)
[    0.000000] ACPI: FACP 0x000000007FFE1F60 0000F4 (v03 BOCHS  BXPCFACP 00000001 BXPC 00000001)
[    0.000000] ACPI: DSDT 0x000000007FFE0040 001F20 (v01 BOCHS  BXPCDSDT 00000001 BXPC 00000001)
[    0.000000] ACPI: FACS 0x000000007FFE0000 000040
[    0.000000] ACPI: APIC 0x000000007FFE2054 000090 (v01 BOCHS  BXPCAPIC 00000001 BXPC 00000001)
[    0.000000] ACPI: MCFG 0x000000007FFE20E4 00003C (v01 BOCHS  BXPCMCFG 00000001 BXPC 00000001)
[    0.000000] ACPI: WAET 0x000000007FFE2120 000028 (v01 BOCHS  BXPCWAET 00000001 BXPC 00000001)
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.000000]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.000000]   Normal   [mem 0x0000000100000000-0x000000027fffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000001000-0x000000000009efff]
[    0.000000]   node   0: [mem 0x0000000000100000-0x000000007ffddfff]
[    0.000000]   node   0: [mem 0x0000000100000000-0x000000027fffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x000000027fffffff]
[    0.000000] On node 0 totalpages: 2097020
[    0.000000]   DMA zone: 64 pages used for memmap
[    0.000000]   DMA zone: 22 pages reserved
[    0.000000]   DMA zone: 3998 pages, LIFO batch:0
[    0.000000]   DMA32 zone: 8128 pages used for memmap
[    0.000000]   DMA32 zone: 520158 pages, LIFO batch:31
[    0.000000]   Normal zone: 24576 pages used for memmap
[    0.000000]   Normal zone: 1572864 pages, LIFO batch:31
[    0.000000] ACPI: PM-Timer IO Port: 0x608
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
[    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: 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] smpboot: Allowing 4 CPUs, 0 hotplug CPUs
[    0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
[    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
[    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000effff]
[    0.000000] PM: Registered nosave memory: [mem 0x000f0000-0x000fffff]
[    0.000000] PM: Registered nosave memory: [mem 0x7ffde000-0x7fffffff]
[    0.000000] PM: Registered nosave memory: [mem 0x80000000-0xafffffff]
[    0.000000] PM: Registered nosave memory: [mem 0xb0000000-0xbfffffff]
[    0.000000] PM: Registered nosave memory: [mem 0xc0000000-0xfed1bfff]
[    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
[    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffbfff]
[    0.000000] PM: Registered nosave memory: [mem 0xfeffc000-0xfeffffff]
[    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xfffbffff]
[    0.000000] PM: Registered nosave memory: [mem 0xfffc0000-0xffffffff]
[    0.000000] e820: [mem 0xc0000000-0xfed1bfff] available for PCI devices
[    0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns
[    0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:4 nr_node_ids:1
[    0.000000] PERCPU: Embedded 33 pages/cpu @ffff88027fc00000 s95128 r8192 d31848 u524288
[    0.000000] pcpu-alloc: s95128 r8192 d31848 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: 2064230
[    0.000000] Kernel command line: BOOT_IMAGE=/zImage mac1=XXXXXXXXX netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=1 vid=0x46f4 syno_hdd_detect=0 pid=0x0001 console=ttyS2,115200n8 elevator=elevator sn=XXXXXXXXX root=/dev/md0 earlyprintk loglevel=15 syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS918+ vender_format_version=2
[    0.000000] Mac1: 00505623F398
[    0.000000] Internal netif num: 1
[    0.000000] Power on seq num: 1
[    0.000000] SYNO GPIO hdd detect pin: 0 
[    0.000000] Serial Number: 1780PDN123456
[    0.000000] Synology Hardware Version: DS918+
[    0.000000] Vender format version: 2
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[    0.000000] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
[    0.000000] Memory: 8147308K/8388080K available (5623K kernel code, 863K rwdata, 1748K rodata, 916K init, 664K bss, 240772K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 64.
[    0.000000]  RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4
[    0.000000] NR_IRQS:4352 nr_irqs:456 16
[    0.000000] Console: colour dummy device 80x25
[    0.000000] tsc: Fast TSC calibration using PIT
[    0.000000] tsc: Detected 3792.661 MHz processor
[    0.000000] tsc: Marking TSC unstable due to TSCs unsynchronized
[    0.004865] Calibrating delay loop (skipped), value calculated using timer frequency.. 7585.32 BogoMIPS (lpj=3792661)
[    0.005415] pid_max: default: 32768 minimum: 301
[    0.006005] ACPI: Core revision 20150930
[    0.007336] ACPI: 1 ACPI AML tables successfully acquired and loaded
[    0.008058] Security Framework initialized
[    0.009008] AppArmor: AppArmor initialized
[    0.009601] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
[    0.010002] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
[    0.012200] Initializing cgroup subsys io
[    0.012789] Initializing cgroup subsys memory
[    0.013006] Initializing cgroup subsys devices
[    0.014006] Initializing cgroup subsys freezer
[    0.022302] mce: CPU supports 10 MCE banks
[    0.022900] mce: unknown CPU type - not enabling MCE support
[    0.023002] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
[    0.024002] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
[    0.025005] Speculative Store Bypass: Vulnerable
[    0.027552] Freeing SMP alternatives memory: 24K
[    0.029167] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.039095] TSC deadline timer enabled
[    0.039639] smpboot: CPU0: AuthenticAMD AMD Ryzen 9 3900X 12-Core Processor (family: 0x17, model: 0x71, stepping: 0x0)
[    0.040263] Performance Events: no PMU driver, software events only.
[    0.041371] NMI watchdog: disabled (cpu0): hardware events not enabled
[    0.042002] NMI watchdog: Shutting down hard lockup detector on all cpus
[    0.043112] x86: Booting SMP configuration:
[    0.043718] .... node  #0, CPUs:      #1 #2 #3
[    0.280021] x86: Booted up 1 node, 4 CPUs
[    0.280655] smpboot: Total of 4 processors activated (30430.50 BogoMIPS)
[    0.281331] devtmpfs: initialized
[    0.282155] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
[    0.283006] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.284042] pinctrl core: initialized pinctrl subsystem
[    0.285223] NET: Registered protocol family 16
[    0.289006] cpuidle: using governor ladder
[    0.293011] cpuidle: using governor menu
[    0.294098] ACPI: bus type PCI registered
[    0.295105] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xb0000000-0xbfffffff] (base 0xb0000000)
[    0.296004] PCI: MMCONFIG at [mem 0xb0000000-0xbfffffff] reserved in E820
[    0.297006] PCI: Using configuration type 1 for base access
[    0.303077] ACPI: Added _OSI(Module Device)
[    0.304029] ACPI: Added _OSI(Processor Device)
[    0.305025] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.305909] ACPI: Added _OSI(Processor Aggregator Device)
[    0.307063] ACPI: Interpreter enabled
[    0.307610] ACPI: (supports S0 S4 S5)
[    0.308003] ACPI: Using IOAPIC for interrupt routing
[    0.308735] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.310308] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[    0.311006] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[    0.312053] acpi PNP0A08:00: _OSC: OS now controls [PME AER PCIeCapability]
[    0.313040] PCI host bridge to bus 0000:00
[    0.313631] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
[    0.314004] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
[    0.314977] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
[    0.315003] pci_bus 0000:00: root bus resource [mem 0x80000000-0xafffffff window]
[    0.316002] pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfebfffff window]
[    0.317003] pci_bus 0000:00: root bus resource [mem 0x280000000-0xa7fffffff window]
[    0.318004] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.318841] pci 0000:00:00.0: [8086:29c0] type 00 class 0x060000
[    0.319370] pci 0000:00:01.0: [1b36:0100] type 00 class 0x030000
[    0.321772] pci 0000:00:01.0: reg 0x10: [mem 0xf4000000-0xf7ffffff]
[    0.323039] pci 0000:00:01.0: reg 0x14: [mem 0xf8000000-0xfbffffff]
[    0.324889] pci 0000:00:01.0: reg 0x18: [mem 0xfc814000-0xfc815fff]
[    0.327690] pci 0000:00:01.0: reg 0x1c: [io  0xd040-0xd05f]
[    0.331110] pci 0000:00:01.0: reg 0x30: [mem 0xfc800000-0xfc80ffff pref]
[    0.332365] pci 0000:00:02.0: [1b36:000c] type 01 class 0x060400
[    0.333960] pci 0000:00:02.0: reg 0x10: [mem 0xfc816000-0xfc816fff]
[    0.335400] pci 0000:00:02.1: [1b36:000c] type 01 class 0x060400
[    0.336693] pci 0000:00:02.1: reg 0x10: [mem 0xfc817000-0xfc817fff]
[    0.338401] pci 0000:00:02.2: [1b36:000c] type 01 class 0x060400
[    0.339714] pci 0000:00:02.2: reg 0x10: [mem 0xfc818000-0xfc818fff]
[    0.342257] pci 0000:00:02.3: [1b36:000c] type 01 class 0x060400
[    0.343737] pci 0000:00:02.3: reg 0x10: [mem 0xfc819000-0xfc819fff]
[    0.345458] pci 0000:00:07.0: [1b36:000d] type 00 class 0x0c0330
[    0.346406] pci 0000:00:07.0: reg 0x10: [mem 0xfc810000-0xfc813fff 64bit]
[    0.348850] pci 0000:00:1f.0: [8086:2918] type 00 class 0x060100
[    0.349422] pci 0000:00:1f.0: quirk: [io  0x0600-0x067f] claimed by ICH6 ACPI/GPIO/TCO
[    0.350168] pci 0000:00:1f.2: [8086:2922] type 00 class 0x010601
[    0.353533] pci 0000:00:1f.2: reg 0x20: [io  0xd060-0xd07f]
[    0.354550] pci 0000:00:1f.2: reg 0x24: [mem 0xfc81a000-0xfc81afff]
[    0.355817] pci 0000:00:1f.3: [8086:2930] type 00 class 0x0c0500
[    0.358305] pci 0000:00:1f.3: reg 0x20: [io  0x0700-0x073f]
[    0.360163] pci 0000:01:00.0: [8086:10d3] type 00 class 0x020000
[    0.362007] pci 0000:01:00.0: reg 0x10: [mem 0xfc640000-0xfc65ffff]
[    0.363538] pci 0000:01:00.0: reg 0x14: [mem 0xfc660000-0xfc67ffff]
[    0.365004] pci 0000:01:00.0: reg 0x18: [io  0xc000-0xc01f]
[    0.366736] pci 0000:01:00.0: reg 0x1c: [mem 0xfc680000-0xfc683fff]
[    0.370004] pci 0000:01:00.0: reg 0x30: [mem 0xfc600000-0xfc63ffff pref]
[    0.371487] pci 0000:00:02.0: PCI bridge to [bus 01]
[    0.372017] pci 0000:00:02.0:   bridge window [io  0xc000-0xcfff]
[    0.372904] pci 0000:00:02.0:   bridge window [mem 0xfc600000-0xfc7fffff]
[    0.373036] pci 0000:00:02.0:   bridge window [mem 0xfea00000-0xfebfffff 64bit pref]
[    0.374597] pci 0000:02:00.0: [1af4:1043] type 00 class 0x078000
[    0.376288] pci 0000:02:00.0: reg 0x14: [mem 0xfc400000-0xfc400fff]
[    0.378532] pci 0000:02:00.0: reg 0x20: [mem 0xfe800000-0xfe803fff 64bit pref]
[    0.380141] pci 0000:00:02.1: PCI bridge to [bus 02]
[    0.380882] pci 0000:00:02.1:   bridge window [mem 0xfc400000-0xfc5fffff]
[    0.381032] pci 0000:00:02.1:   bridge window [mem 0xfe800000-0xfe9fffff 64bit pref]
[    0.383208] pci 0000:03:00.0: [1af4:1045] type 00 class 0x00ff00
[    0.385604] pci 0000:03:00.0: reg 0x20: [mem 0xfe600000-0xfe603fff 64bit pref]
[    0.386815] pci 0000:00:02.2: PCI bridge to [bus 03]
[    0.387031] pci 0000:00:02.2:   bridge window [mem 0xfc200000-0xfc3fffff]
[    0.388023] pci 0000:00:02.2:   bridge window [mem 0xfe600000-0xfe7fffff 64bit pref]
[    0.389481] pci 0000:00:02.3: PCI bridge to [bus 04]
[    0.390031] pci 0000:00:02.3:   bridge window [mem 0xfc000000-0xfc1fffff]
[    0.391032] pci 0000:00:02.3:   bridge window [mem 0xfe400000-0xfe5fffff 64bit pref]
[    0.393286] pci_bus 0000:00: on NUMA node 0
[    0.394119] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
[    0.395026] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
[    0.395919] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
[    0.396243] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
[    0.397107] ACPI: PCI Interrupt Link [LNKE] (IRQs 5 *10 11)
[    0.397994] ACPI: PCI Interrupt Link [LNKF] (IRQs 5 *10 11)
[    0.398254] ACPI: PCI Interrupt Link [LNKG] (IRQs 5 10 *11)
[    0.399114] ACPI: PCI Interrupt Link [LNKH] (IRQs 5 10 *11)
[    0.399979] ACPI: PCI Interrupt Link [GSIA] (IRQs *16)
[    0.400117] ACPI: PCI Interrupt Link [GSIB] (IRQs *17)
[    0.400887] ACPI: PCI Interrupt Link [GSIC] (IRQs *18)
[    0.401114] ACPI: PCI Interrupt Link [GSID] (IRQs *19)
[    0.401867] ACPI: PCI Interrupt Link [GSIE] (IRQs *20)
[    0.402114] ACPI: PCI Interrupt Link [GSIF] (IRQs *21)
[    0.402898] ACPI: PCI Interrupt Link [GSIG] (IRQs *22)
[    0.403117] ACPI: PCI Interrupt Link [GSIH] (IRQs *23)
[    0.404098] ACPI: Enabled 1 GPEs in block 00 to 3F
[    0.405075] vgaarb: setting as boot device: PCI:0000:00:01.0
[    0.405844] vgaarb: device added: PCI:0000:00:01.0,decodes=io+mem,owns=io+mem,locks=none
[    0.406010] vgaarb: loaded
[    0.406398] vgaarb: bridge control possible 0000:00:01.0
[    0.407124] SCSI subsystem initialized
[    0.407718] libata version 3.00 loaded.
[    0.408054] pps_core: LinuxPPS API ver. 1 registered
[    0.408799] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.409028] PTP clock support registered
[    0.409685] PCI: Using ACPI for IRQ routing
[    0.464507] PCI: pci_cache_line_size set to 64 bytes
[    0.465191] e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
[    0.466009] e820: reserve RAM buffer [mem 0x7ffde000-0x7fffffff]
[    0.467187] clocksource: Switched to clocksource refined-jiffies
[    0.476361] AppArmor: AppArmor Filesystem Enabled
[    0.477026] pnp: PnP ACPI init
[    0.477529] pnp 00:00: Plug and Play ACPI device, IDs PNP0501 (active)
[    0.478022] pnp 00:01: Plug and Play ACPI device, IDs PNP0501 (active)
[    0.478985] pnp 00:02: Plug and Play ACPI device, IDs PNP0303 (active)
[    0.479027] pnp 00:03: Plug and Play ACPI device, IDs PNP0f13 (active)
[    0.479978] pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.480157] pnp: PnP ACPI: found 5 devices
[    0.488524] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    0.489060] clocksource: Switched to clocksource acpi_pm
[    0.490619] pci 0000:00:02.1: bridge window [io  0x1000-0x0fff] to [bus 02] add_size 1000
[    0.492263] pci 0000:00:02.2: bridge window [io  0x1000-0x0fff] to [bus 03] add_size 1000
[    0.493837] pci 0000:00:02.3: bridge window [io  0x1000-0x0fff] to [bus 04] add_size 1000
[    0.495075] pci 0000:00:02.1: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
[    0.496458] pci 0000:00:02.1: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
[    0.497828] pci 0000:00:02.2: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
[    0.499224] pci 0000:00:02.2: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
[    0.500631] pci 0000:00:02.3: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
[    0.501990] pci 0000:00:02.3: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
[    0.503392] pci 0000:00:02.1: BAR 13: assigned [io  0x1000-0x1fff]
[    0.504357] pci 0000:00:02.2: BAR 13: assigned [io  0x2000-0x2fff]
[    0.505291] pci 0000:00:02.3: BAR 13: assigned [io  0x3000-0x3fff]
[    0.506220] pci 0000:00:02.0: PCI bridge to [bus 01]
[    0.506922] pci 0000:00:02.0:   bridge window [io  0xc000-0xcfff]
[    0.508351] pci 0000:00:02.0:   bridge window [mem 0xfc600000-0xfc7fffff]
[    0.509679] pci 0000:00:02.0:   bridge window [mem 0xfea00000-0xfebfffff 64bit pref]
[    0.511969] pci 0000:00:02.1: PCI bridge to [bus 02]
[    0.512757] pci 0000:00:02.1:   bridge window [io  0x1000-0x1fff]
[    0.514146] pci 0000:00:02.1:   bridge window [mem 0xfc400000-0xfc5fffff]
[    0.515486] pci 0000:00:02.1:   bridge window [mem 0xfe800000-0xfe9fffff 64bit pref]
[    0.517259] pci 0000:00:02.2: PCI bridge to [bus 03]
[    0.518055] pci 0000:00:02.2:   bridge window [io  0x2000-0x2fff]
[    0.519489] pci 0000:00:02.2:   bridge window [mem 0xfc200000-0xfc3fffff]
[    0.520871] pci 0000:00:02.2:   bridge window [mem 0xfe600000-0xfe7fffff 64bit pref]
[    0.523356] pci 0000:00:02.3: PCI bridge to [bus 04]
[    0.524158] pci 0000:00:02.3:   bridge window [io  0x3000-0x3fff]
[    0.525494] pci 0000:00:02.3:   bridge window [mem 0xfc000000-0xfc1fffff]
[    0.526820] pci 0000:00:02.3:   bridge window [mem 0xfe400000-0xfe5fffff 64bit pref]
[    0.528591] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
[    0.529551] pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
[    0.530541] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
[    0.532118] pci_bus 0000:00: resource 7 [mem 0x80000000-0xafffffff window]
[    0.533171] pci_bus 0000:00: resource 8 [mem 0xc0000000-0xfebfffff window]
[    0.534205] pci_bus 0000:00: resource 9 [mem 0x280000000-0xa7fffffff window]
[    0.535299] pci_bus 0000:01: resource 0 [io  0xc000-0xcfff]
[    0.536145] pci_bus 0000:01: resource 1 [mem 0xfc600000-0xfc7fffff]
[    0.537080] pci_bus 0000:01: resource 2 [mem 0xfea00000-0xfebfffff 64bit pref]
[    0.538174] pci_bus 0000:02: resource 0 [io  0x1000-0x1fff]
[    0.538969] pci_bus 0000:02: resource 1 [mem 0xfc400000-0xfc5fffff]
[    0.539927] pci_bus 0000:02: resource 2 [mem 0xfe800000-0xfe9fffff 64bit pref]
[    0.541039] pci_bus 0000:03: resource 0 [io  0x2000-0x2fff]
[    0.541851] pci_bus 0000:03: resource 1 [mem 0xfc200000-0xfc3fffff]
[    0.542800] pci_bus 0000:03: resource 2 [mem 0xfe600000-0xfe7fffff 64bit pref]
[    0.543898] pci_bus 0000:04: resource 0 [io  0x3000-0x3fff]
[    0.544789] pci_bus 0000:04: resource 1 [mem 0xfc000000-0xfc1fffff]
[    0.545773] pci_bus 0000:04: resource 2 [mem 0xfe400000-0xfe5fffff 64bit pref]
[    0.546908] NET: Registered protocol family 2
[    0.547771] TCP established hash table entries: 65536 (order: 7, 524288 bytes)
[    0.549251] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[    0.550890] TCP: Hash tables configured (established 65536 bind 65536)
[    0.551977] UDP hash table entries: 4096 (order: 5, 131072 bytes)
[    0.553040] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
[    0.554146] NET: Registered protocol family 1
[    0.554825] pci 0000:00:01.0: Video device with shadowed ROM
[    0.555878] ACPI: PCI Interrupt Link [GSIH] enabled at IRQ 23
[    0.557193] PCI: CLS 0 bytes, default 64
[    0.840100] Trying to unpack rootfs image as initramfs...
[    0.895476] Freeing initrd memory: 19888K
[    0.896401] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    0.897462] software IO TLB: mapped [mem 0x7bfde000-0x7ffde000] (64MB)
[    0.898660] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x6d5685db502, max_idle_ns: 881590404252 ns
[    0.901935] audit: initializing netlink subsys (disabled)
[    0.903081] audit: type=2000 audit(1628546252.902:1): initialized
[    0.904413] Initialise system trusted keyring
[    0.929399] VFS: Disk quotas dquot_6.6.0
[    0.930387] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    1.050480] Key type asymmetric registered
[    1.051308] Asymmetric key parser 'x509' registered
[    1.052231] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    1.053559] io scheduler noop registered
[    1.054259] io scheduler deadline registered
[    1.054991] io scheduler cfq registered
[    1.055996] ACPI: PCI Interrupt Link [GSIG] enabled at IRQ 22
[    1.063094] aer 0000:00:02.0:pcie02: service driver aer loaded
[    1.064330] aer 0000:00:02.1:pcie02: service driver aer loaded
[    1.065554] aer 0000:00:02.2:pcie02: service driver aer loaded
[    1.066775] aer 0000:00:02.3:pcie02: service driver aer loaded
[    1.068296] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
[    1.069395] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[    1.070484] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
[    1.071527] pcieport 0000:00:02.1: Signaling PME through PCIe PME interrupt
[    1.072581] pci 0000:02:00.0: Signaling PME through PCIe PME interrupt
[    1.073592] pcie_pme 0000:00:02.1:pcie01: service driver pcie_pme loaded
[    1.074650] pcieport 0000:00:02.2: Signaling PME through PCIe PME interrupt
[    1.075705] pci 0000:03:00.0: Signaling PME through PCIe PME interrupt
[    1.076732] pcie_pme 0000:00:02.2:pcie01: service driver pcie_pme loaded
[    1.077794] pcieport 0000:00:02.3: Signaling PME through PCIe PME interrupt
[    1.078850] pcie_pme 0000:00:02.3:pcie01: service driver pcie_pme loaded
[    1.112952] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    1.139659] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
[    1.141274] console [ttyS2] enabled
[    1.142369] bootconsole [uart0] disabled

     

    Yes. Lagacy bios is requird. It has been discussed before.

    And your log is irrelevant, which the issue happens after uart0 disabled.

    Your case is same as mine i guess, missing /dev/synoboot

     

     

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted

    8 minutes ago, cwiggs said:

    Yes, those are the correct vid/pids.  You need to make sure the boot device is mounted via usb, any other way will not work with this loader.

    DSM7
    args: -device 'qemu-xhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/303/redpill-DS918+_7.0-41890_b1628529091.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot,bootindex=5'

     

    DSM6.2.3 (Working Jun Loader)

    args: -device 'qemu-xhci,id=usb-ctl-synoboot,addr=0x18' -drive 'id=usb-drv-synoboot,file=/var/lib/vz/images/301/synoboot.img,if=none,format=raw' -device 'usb-storage,id=usb-stor-synoboot,bootindex=1,removable=off,drive=usb-drv-synoboot' 

     

    Any hints for me? 

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted

    On 8/8/2021 at 12:55 AM, dodo-dk said:

    @cwiggs

    It works, something you do wrong. VM_ID have you changed in the line?

    This is my args line in Proxmox 7:

      

    
args: -device 'qemu-xhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/100/redpill-DS3615xs_6.2.4-25556_b1628330868.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot,bootindex=5'

     

    I am using Proxmox as well, and still not able to see /dev/synoboot*

    are you using 0x46F4, 0x0001 as usb vid/pid?

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted

    failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:2) 

    Jan  1 00:00:43 updater: updater.c:7033 This is X86 platform
Jan  1 00:00:43 updater: boot/boot_lock.c(228): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:2)
Jan  1 00:00:43 updater: updater.c:6494 Failed to mount boot partition
Jan  1 00:00:43 updater: updater.c:3118 No need to reset reason for v.41890 
Jan  1 00:00:43 updater: updater.c:7636 Failed to accomplish the update! (errno = 21)
Jan  1 00:00:43 install.cgi: ninstaller.c:1546 Executing [/tmpData/upd@te/updater -v /tmpData > /dev/null 2>&1] error[21]

     

    I think this loader do not have /dev/synoboot* right?
    In that case how can I mount boto device?

     

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted · Edited by mcdull

    Finally got DSM to boot with haydibe's v0.4 script.

    under proxmox v7 and AMD Ryzen 3900X, I have to use qemu64 as cpu type or it will not boot.

     

    Update: 

    [  141.005313] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
    [  141.008687] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
    [  141.032935] Failed to set alarm data.
    [  141.037685] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
    [  141.041520] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
    [  141.056471] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
    [  141.059888] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)

     

    Failed with installation.  dunno if it is cpu incompatibility. (AMD Ryzen 3900x)

     

    Update2 :

    Seems the above error is not fatal, I stopped at 55%. And in the next trial, DSM7 detected my hdd has old configuration, which was a brand new one created under pve 7.0

     

    Update3 :

    Added 2 SATA hdd, stopped at 55% with error 21 

    Aug  9 14:12:53 updater: updater.c:7029 ==== Start flash update ====
Aug  9 14:12:53 updater: updater.c:7033 This is X86 platform
Aug  9 14:12:53 updater: boot/boot_lock.c(228): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:2)
Aug  9 14:12:53 updater: updater.c:6494 Failed to mount boot partition
Aug  9 14:12:53 updater: updater.c:3118 No need to reset reason for v.41890 
Aug  9 14:12:53 updater: updater.c:7636 Failed to accomplish the update! (errno = 21)
Aug  9 14:12:53 install.cgi: ninstaller.c:1546 Executing [/tmpData/upd@te/updater -v /tmpData > /dev/null 2>&1] error[21]
Aug  9 14:13:07 install.cgi: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot
Aug  9 14:13:07 install.cgi: ninstaller.c:1515 Moving updater for configuration upgrade...cmd=[/bin/mv -f /tmpData/upd@te/updater /tmpRoot/.updater > /dev/null 2>&1]
Aug  9 14:13:07 install.cgi: ninstaller.c:152 umount partition /tmpRoot
Aug  9 14:13:07 install.cgi: ErrFHOSTCleanPatchDirFile: After updating /tmpData/upd@te...cmd=[/bin/rm -rf /tmpData/upd@te > /dev/null 2>&1]
Aug  9 14:13:07 install.cgi: ErrFHOSTCleanPatchDirFile: Remove /tmpData/upd@te.pat...
Aug  9 14:13:07 install.cgi: ErrFHOSTDoUpgrade(1794): child process failed, retv=-21
Aug  9 14:13:07 install.cgi: ninstaller.c:1811(ErrFHOSTDoUpgrade) err=[-1]
Aug  9 14:13:07 install.cgi: ninstaller.c:1815(ErrFHOSTDoUpgrade) retv=[-21]
Aug  9 14:13:07 install.cgi: install.c:409 Upgrade by the manual patch fail.
Aug  9 14:13:07 install.cgi: install.c:678 Upgrade by the uploaded patch /tmpData/@autoupdate/upload.pat fail.
Jan  1 00:00:00 install.cgi: ninstaller.c:152 umount partition /tmpData

    This error seems familiar: failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:2)

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted

    16 minutes ago, ThorGroup said:

    Status Update! ;)

    Recently we were working hard in the kernel space to bring even more missing things and bring it into a more stable state. That meant we had little time to respond but we're blown away by the number of posts here!


    mfgBIOS shimming stability
    As we discussed here before there were moments where some BIOS functions weren't shimmed or there were flaky. This caused the OS to sometimes work correctly but sometimes fail the 24h test. Guess how easy was that to debug and fix :D
    However, we did it and now the mfgBIOS shimming should be almost bulletproof!


    RTC emulation
    We've added a full RTC proxy layer. This wasn't strictly needed for 3515xs series. However, 918+ and other models use RTC chip which is not natively/fully supported for the Linux kernel. This means that various subsystems rely on mfgBIOS to update the time from RTC on boot. Since that chip does not exist outside of the official hardware we needed to go around that. In short the LKM code plugs into mfgBIOS and serves as a proxy layer between what's a real RTC (or a one from hypervisor) and what mfgBIOS can understand.

    Currently, the time set/get is implemented. Alarms are mocked to the point that mfgBIOS doesn't complain. In fact the BIOS code can even set these alarms but they will be erased upon reboot. We didn't bother actually writing them to the RTC. The reason being a) we've never seen anybody using it and b) most RTCs [or actually the hw connected to them] is broken to the point that they don't work anyway (or only work from certain sleep states).
    If the community desires we can add that.


    Inverting serial ports on 3615xs
    We hate it. We did it. It's sort of working and it's a big hack. We will most likely disable it by default as this isn't even fully stable. Also this method cannot work on kernel v4 which... well, v7 and 3615xs. Whoever in syno had this brilliant idea should seriously think again before pulling such a stunt again. This breaks a lot of stuff.


    Fix ttyS0 on 918+
    On some platforms first serial port is intentionally disabled. We added a small hack to re-enable it.


    Virtual Serial Port / UART
    This is big. In many ways actually. This single commit with over 1300 new lines and the patch taking 70KB was by far the biggest addition. The complexity of this part is really something we grind our teeth on. To make sure the solution works on all kernels without hacks we had to emulate a physical UART chip. So we did. We wrote a whole software-based emulator of National Semiconductors 16550A UART controller, along with support for FIFOs. Additionally, as we wanted the code to perform great we raised the bar and wrote an additional layer of virtual IRQ (as the real ones cannot be used for many reasons here) which actually made the module multithreaded in the kernel.

    This whole thing took, across all of us, probably close to 150 hours to develop. There were many ideas and failed endeavors. But the full chip emulation should serve us a long way you truly cannot distinguish it from a real thing (as it is not hacking the kernel in any way).

     

    If anyone wants to borrow that code for something non-DSM related feel free - it's actually modular and not coupled with the RedPill LKM in any substantial way.

     

    Currently, this vUART stuff is not running in the actual LKM. It is meant to be a component to implement PMU emulation. That part requires a two (hopefully) simple functions which react to the data from the DSM and respond like the PMU would. This will also allow us to give a simple hook to anybody who's willing to connect a hardware PMU to get LEDs and what not working ;)


    *********************************************************************************

     

    v7 testing
    We're so happy to see the community effort to add v7. As it is now available for 3615xs we will definitelly jump into it and merge PRs if they pass ;)

    AFTER merging them we will probably reorganize template files a bit as that symlink-hell was a bad idea.

     

    Now let us respond to everything:

    RedPill actually blocks telemetry as well ;) If you want to check that just go the Control Panel and click "What's new" on an update - you will not see a syno page.

     

     

    Currently it SHOULD work on some baremetal configs but it's definitely not tested. It will be plug-and-play when it's stable.

     

     

    We confirmed that ESXi doesn't allow adding virtual USB drives, so we need SATA DOM boot support. Stay tuned.

    Setting vid/pid or any other options will NOT make the loader work without LKM changes (ok, technically MAYBE if you recreate PCI tree in Proxmox but .... no, that's not the solution and definitelly not for ESXi or baremetal ;)).

     

     

    You didn't provide RedPill LKMs. You need to compile them if you want to play with the current build.

     

     

    You shouldn't try to compile the kernel but the module. Executing make in the kernel dir will try to build the whole kernel (which doesn't make any sense as it will not be usable really). If you're having problems compiling the module the release is not meant for you (yet).

     

     

    We weren't able to access the telegram as they force us to give a valid, physical phone number. For obvious reasons we didn't give them one ;) When we have a moment to arrange that we will arrive for sure. However, as the current stage is still intended for developers (and we're BEGGING normal users to not use it due to missing stuff which causes various trips in the DSM itself).

    Unless there's some way to use telegram without a phone number which we don't know about?

     

     

    DO NOT USE IT. Seriously, we don't want to sound rude but if we say this is a development release we mean it. The kernel module lacks some functionality required for the DSM to stay stable. In the current state data loss is a possibility.

     

     

    Thanks! We need some smart way for adding kernel extensions outside of the ramdisk (as it's limited in size). Something like Jun's extra.lzma. However, as it uses a different method of loading we cannot simply merge ramdisks automatically hmm...

     

     

    Great job! We love the approach of going docker. We honestly didn't look into the docker toolchain (yet!) you've built but we're excited!

    What do you think about incorporating it into RedPill-Load repository? We think it will be a great addition so that the whole thing can be run on any dockerized system.
    Drop us a PM to not pollute the thread. In general it's great - the only thing which we will keep is making sure the user can actually use JSON config and not makefile - we pulled teeth for hours to make it happen in bash as JSON is user-friendly while Makefile... well :D

     

     

    Onboard network will require a separate kernel extension. This is the same issue as with power button kernel extension - we don't have a good way for not including all extensions in the main ramdisk (which cannot grow too much, especially for 918+).

     

     

    This looks like a broken patch for ramdisk hmm. Is the file even loaded via network?

     

     

    Did you use virtio driver for the ethernet?

     

     

    For any error 13 a full log from /var/log/messages and install_log is needed. However, in general VMWare will not work until we implement SATA DOM as VMWare Workstation/Fusion/ESXi doesn't allow creating virtual USB drives.

     

    To add to that EFI boot is problematic in many way as it tries to initialize devices before Linux can touch them. This can end poorly on some hardware when running DSM. That's why we disabled EFI in the GRUB deliberately.

     

     

    You cannot do that. There's no support for SATA DOM in the LKM.

     

    This is a known issue: https://github.com/RedPill-TTG/redpill-lkm/issues/3

     

     

    Telnet access has nothing to do with the loader. It's up to the settings you set in your hypervisor ;) On Proxmox there's a local access through "qm console", on VirtualBox you can set COM1-4 in settings to be a telnet or a raw socket or whatever else.

     

     

    These warning are just really warnings and GCC isn't correct here actually. As 4.8 is old we need some creative way to make it happy. But since this code works as expected and is a weak warning we aren't worried about that.
    The one regarding unused function is there because we left some skeleton for future shims - that one used to be used before we implemented proper RTC.

    As for rebuilding kernel: you MUST use the proper GCC for that. It will NOT build with GCC 5.4 properly as v3 only supports up to v4.9 (or something along the lines).

     

     

    Unfortunately Proxmox (or rather QEMU) cannot do a split-brain situation where some instructions are virtualized with hardware KVM acceleration and some are done in software. This means it's not feasible to run emulated haswell when your host CPU doesn't support all the instructions. You CAN do that for testing (disable HW acceleration in VM options) but it's PAINFULLY slow. We use it from time-to-time for testing LKM but it's really like working on a Pentium MMX.

     

     

    That's a good decision in our opinion to move to debian8. It is old... but so is the kernel. We also use Debian 8 VM internally. From what we've heard syno does not use a cross-toolchain for building kernels either. That says something.

     

    As for booting on ESXi see above - it will not boot as of now.

     

     

    Isn't unraid using qemu? It should boot no problem (at least to grub) as long as it's a TRUE usb boot and not a sata boot. Can you run the VM and check the output from "ps -a"? Go through it manually and try to find the qemu/kvm process. It will have a VERY long cmdline (like several lines long). This is the ultimate source of truth regarding what's being run.

     

    Where precisely does it stop? Can you post a screenshot?

     

    Thanks for replying.  It must be some stupid mistakes that I've made.

    Screenshot here:-

     

    grub.png

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted

    5 minutes ago, gadreel said:

    @kelvin701 I did, and as I posted a few posts back to Haydibe that using his docker image on Unraid it does not boot up. I do not know what is going on. Maybe is something that has to do with GRUB... I have no idea really. Feel free to try though :)

    me 2, my image always stopped at grub before loading kernel.  Since I am not good at it, probably my mistake in following the procedure.

    (proxmox 7.0)

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted

    15 hours ago, haydibe said:

    The redpill tool chain docker image builder is updated to v0.3:

    - added support to use DSM7 fork of redpill-load for DSM918+ as done by @rlatn0123 (just comment/uncomment the required lines in the "outer" Makefile)

    - base image can now be configured, defaults to debian:8 now (as seen in a recommendation from ThorGroup)

    - uses generic jq 1.6 regardless of the base image 

     

    Please bare in mind, that this image builder creates an environment based on the official Synology tool chain and kernel sources, and the sources of redpill-lkm and ledpill-load. The Makefile to create the image is just for your convience. The Makefile to build the bootloader follows the instructiosn of redpill-load. @ThorGroupcan you take a look at the image builder and "aprove" that it actualy meets the expectation?

     

    Usage bromolow:

    - (on host) build image: make build_image_bromolow

    - (on host) create your own user_config.json or edit the USERCONFIG_* variables in the Makefile

    - (on host) run container: make  run_container_bromolow

    - (in container) build kernel and loader image: make build_all

     

    Usage apollolake:

    - (on host) build image: make build_image_apollolake

    - (on host) create your own user_config.json or edit the USERCONFIG_* variables in the Makefile

    - (on host) run container: make  run_container_apollolake

    - (in container) build kernel and loader image: make build_all

     

    After running `make build_all` the created redpill bootloader image will be present in the ./image folder on the host.

     

    Tested with hosts: Ubuntu 18.04 VM, Ubuntu 20.04 WSL2 and XPE  (the make binary to build on Synology/XPE can be found a couple of posts earlier)

     

    Dependencies: make and docker

    redpill-tool-chain_x86_64_v0.3.zip 4.37 kB · 41 downloads

    What is the format of user_config.json?

     

    "vid": "0x46f4",

    "pid": "0x0001",

    "sn": "20xxxxxxx",

    "mac": "00:11:22:33:44:55"

     

    is this correct?   Thanks

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted 

    root@d6622ebf13fe:/opt# fdisk -l /opt/redpill-load/images/redpill-DS918+_6.2.4-25556_b1628198282.img
Disk /opt/redpill-load/images/redpill-DS918+_6.2.4-25556_b1628198282.img: 128 MiB, 134217728 bytes, 262144 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xf110ee87

Device                                                               Boot  Start    End Sectors Size Id Type
/opt/redpill-load/images/redpill-DS918+_6.2.4-25556_b1628198282.img1        2048 100351   98304  48M 83 Linu
/opt/redpill-load/images/redpill-DS918+_6.2.4-25556_b1628198282.img2      100352 253951  153600  75M 83 Linu
/opt/redpill-load/images/redpill-DS918+_6.2.4-25556_b1628198282.img3      253952 262143    8192   4M 83 Linu

     

    I cannot mount the img using vfat or ext2 for checking the grub, and the fdisk show the above.

    mount: /mnt/boot: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted

    3 minutes ago, haydibe said:

    Did you use the make target run_container_apollolake to actualy run the container, or did you start it with `docker  run`?

    The container needs a shitload of permissions and trickery to actualy lift the image repackaging part. The docker run statement ecapsulated in the  run_container_apollolake takes care of setting the required parameters. 

    I user make run_container_apollolake

    and make build all inside

     

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted

    1 hour ago, haydibe said:

    For all of you that want a "redpill tool chain".

    Well, I created a make based project that creates a docker image with the toolchain for brolow or apollolake

     

    make targets `build_image_bromolow` and `build_image_apollolake`:

    - download matching toolchain and kernel version on the host before building the image

    - base image ubuntu:18.04

    - sources of redpill-lkm fetched while building the image

    - sources of redpill-load fetched while building the image

    - A Makefile is added inside the image, that allows to generate the user_data.json based on container environment variables and cover build of redpill.ko and the image

     

    make targets 'run_container_bromolow` and `run_container_apollolake`

    - mount a volume for the redpill-load/cache folder

    - mount a folder to the redpill-load/image folder

    - set parameters for user_data.json (requires editing of the Makefile)

    - take care of parameters that allow to mount the loop device while creating the image

     

    Though, there is one caveat: the project requires make, which is not available on Synology

     

    Note1: once you compile make for Synology (out of scope for this tool chain), you can actualy create and use the image on a Synology or XPE box :)

    Note2: even works on wsl2 with enabled systemd, installed docker.io and make package

     

    Usage: change into the folder you extracted the zip into and run `make` to see the list of available targets.

     

    Update: re-uploaded, because I accidently broke the apollolake part in the Makefile . 

     

    redpill-tool-chain.zip 3.92 kB · 10 downloads

     

    Thx for your tools, when I try boot the redpill-DS918+_6.2.4-25556_b1628193475.img, it stopped at GRUB. anything that I have missed? thanks.

    RedPill - the new loader for 6.2.4 - Discussion

    in Developer Discussion Room

    Posted

    1 hour ago, gadreel said:

     

    @calimansiYes, even with Jun's loader you could modify it to support new models. I think there is a post somewhere that on a Chinese forum, somebody did it for 1019+ (if I am not mistaken). The issue here is that developing a loader to support other models you wont gain anything. For example 3615xs and 3617xs support different amount of cores, the DS918+ supports booting from UEFI and NVMEs. So taking the example with the 1019+ compared to 918+ there is no difference between them, no point of making a new loader if they both offer the same stuff.

    They modified it to 1019+ simply because it has the exact same core hardware.  And it is NOT an easy task to support whatever emulated model because of those pci address issues as discussed.

×
×
  • Create New...