Jump to content
XPEnology Community

RedPill - the new loader for 6.2.4 - Discussion

ThorGroup

By ThorGroup
in Developer Discussion Room

 Share

Recommended Posts

Aigor Guru

Aigor

Posted
Posted (edited)

I would like boot redpill image via pxe, i have already setup pxe boot env, and i'm trying to add Redpill boot, so i setup a entry like this 
  

LABEL Synology-DSM7
       MENU LABEL DSM7
       KERNEL images/DSM7/zImage
	   APPEND initrd images/DSM7/rd.gz netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=0 syno_hdd_detect=0 elevator=elevator root=/dev/md0 loglevel=15 mac1=005056b54653 vid= pid= console=ttyS0,115200n8 sn=1130LWN020274 earlyprintk syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS3615xs vender_format_version=2

But i get a kernel panic, 
  

[    0.873466] BUG: unable to handle kernel paging request at ffffffffffffffc0
[    0.874430] IP: [<ffffffff8188b29c>] populate_rootfs+0xea/0x1d8
[    0.874435] PGD 1810067 PUD 1812067 PMD 0
[    0.874440] Oops: 0000 [#1] SMP
[    0.874445] Modules linked in:
[    0.874450] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.10.105 #25556
[    0.874455] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020
[    0.874460] task: ffff88003e1c4800 ti: ffff88003e1d8000 task.ti: ffff88003e1d8000
[    0.874465] RIP: 0010:[<ffffffff8188b29c>]  [<ffffffff8188b29c>] populate_rootfs+0xea/0x1d8
[    0.874470] RSP: 0000:ffff88003e1dbe98  EFLAGS: 00010286
[    0.874475] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000010
[    0.874480] RDX: ffffffffffffffc0 RSI: ffffffffffffffc0 RDI: ffff88003e1dbeb8
[    0.874485] RBP: ffffffff8188b1b2 R08: ffff88003e1dbe98 R09: 0000000000000000
[    0.874490] R10: ffff88003e1dbe70 R11: fffffe266ae66564 R12: 0000000000000093
[    0.874495] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[    0.874500] FS:  0000000000000000(0000) GS:ffff88003fc00000(0000) knlGS:0000000000000000
[    0.874505] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[    0.874510] CR2: ffffffffffffffc0 CR3: 000000000180e000 CR4: 00000000000607f0
[    0.874515] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    0.874520] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[    0.874525] Stack:
[    0.874530]  715c9d1252e7dcd8 a1064449adeacd81 9d1ef9257fe4c3e2 387ce064ba66fa03
[    0.874535]  0000000000000001 ffff88003e3dda00 ffff88003e1dbeb4 0000000000000000
[    0.874540]  0000000000000008 ffffffff818ab135 0800000000000082 0000000000000000
[    0.874545] Call Trace:
[    0.874555]  [<ffffffff818ab135>] ? pci_apply_final_quirks+0xe2/0xfb
[    0.874563]  [<ffffffff8100038a>] ? do_one_initcall+0xca/0x180
[    0.874570]  [<ffffffff81888e3d>] ? kernel_init_freeable+0x13a/0x1bb
[    0.874578]  [<ffffffff814bc9c0>] ? rest_init+0x70/0x70
[    0.874586]  [<ffffffff814bc9c5>] ? kernel_init+0x5/0x180
[    0.874593]  [<ffffffff814cfc0d>] ? ret_from_fork+0x5d/0xb0
[    0.874600]  [<ffffffff814bc9c0>] ? rest_init+0x70/0x70
[    0.874605] Code: 24 17 9d c6 44 24 18 03 c6 44 24 19 fa c6 44 24 1a 66 c6 44 24 1b ba c6 44 24 1c 64 c6 44 24 1d e0 c6 44 24 1e 7c c6 44 24 1f 38 <f3> a5 48 8d 7c 24 20 48 c7 c1 05 89 6e 81 48 89 c6 e8 de f7 9c
[    0.874610] RIP  [<ffffffff8188b29c>] populate_rootfs+0xea/0x1d8
[    0.874615]  RSP <ffff88003e1dbe98>
[    0.874620] CR2: ffffffffffffffc0
[    0.874625] ---[ end trace 478ae565ccf7d2e4 ]---
[    0.874639] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
[    0.874639]

Do i have to add disk to VM or change ipxe command line? 
Thanks 

Edited by Aigor
Link to comment
Share on other sites
Orphée Guru Master

Orphée

Posted
Posted
18 hours ago, haydibe said:

The redpill tool chain docker image builder is updated:

- bind-mounts an existing user_config.json file into the redpill-load folder (and then skips autogeneration of the file inside the container)

- added variables in the Makefile to specify the redpill-lkm and redpill-load repository urls and branches  

- added variables in the Makefile to specify the urls for the bromolow and apollolake toolchain/kernel

- refactored repated code blocks into Make functions

- refactored to single Dockerfile using ARGs to build the target bromolow or apolloake image

 

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.2.zip 4.03 kB · 34 downloads

Thanks, I built it and tried to use it on ESXi, but it hangs on "booting kernel"

Thanks anyway

Link to comment
Share on other sites
haydibe Guru

haydibe

Posted
Posted (edited)

Did you set the vNIC interface to E1000E before booting?

 

Haven't succeeded in the migration on ESXi 6.7 myself: the box can be found with Syno Assistent, though the migration aboards with error 13.

 

Edited by haydibe
Link to comment
Share on other sites
haydibe Guru

haydibe

Posted
Posted

There is a fork of redpill-load, that hopefilly will be merge back into the official redpill-load. This is the reason why I made the checkout URLs for redpill-load and redpill-lkm configurable in the new version of the tool chain image builder.

 

Though, without the 7.0 kernel sources for the redpill-lkm build, I highly doubt that redpill-load will be able to create a bootable image...   

Link to comment
Share on other sites
rlatn0123 Newbie

rlatn0123

Posted
Posted
6 minutes ago, haydibe said:

There is a fork of redpill-load, that hopefilly will be merge back into the official redpill-load. This is the reason why I made the checkout URLs for redpill-load and redpill-lkm configurable in the new version of the tool chain image builder.

 

Though, without the 7.0 kernel sources for the redpill-lkm build, I highly doubt that redpill-load will be able to create a bootable image...   

try this i edited for apollolake

redpill-tool-chain-with-7.0.zip

  • Like 1
Link to comment
Share on other sites
haydibe Guru

haydibe

Posted
Posted

I see, you used the old script package. The new does the modification in Dockerfile.apollolake obselete. The second that changes the build parameter for build-loader.sh.

 

This works, if the kernel for DS918 is identical for 7.0-41890 and 6.2.4-25556.

 

  • Like 1
Link to comment
Share on other sites
cwiggs Junior Member

cwiggs

Posted
Posted (edited)
19 hours ago, haydibe said:

The redpill tool chain docker image builder is updated:

- bind-mounts an existing user_config.json file into the redpill-load folder (and then skips autogeneration of the file inside the container)

- added variables in the Makefile to specify the redpill-lkm and redpill-load repository urls and branches  

- added variables in the Makefile to specify the urls for the bromolow and apollolake toolchain/kernel

- refactored repated code blocks into Make functions

- refactored to single Dockerfile using ARGs to build the target bromolow or apolloake image

 

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.2.zip 4.03 kB · 36 downloads

 

Used the tool chain here to create a 6.2.4 image.  The image seems to boot correctly in proxmox 6.4-13 but the VM never gets an IP, and I can't find it with find.synology.com.  I updated the s/n, nic, usb vid/pid but still no luck.  I am booting the img as sata0 after using a 'qm import'.

 

Here is the tail of serial0: 

[    5.123258] <redpill/bios_shims_collection.c:61> Finished printing memory at ffffffffa00def20
[    5.124466] <redpill/bios_shim.c:117> bromolow_synobios BIOS *fully* shimmed
[    5.271843] <redpill/intercept_execve.c:87> Blocked /usr/syno/bin/syno_pstore_collect from running
-3-4-k[   11.610373] usbcore: registered new interface driver usbhid
[   11.611339] usbhid: USB HID core driver
--
-Sat Aug  7 14:58:10 2021
-
-DiskStation login:

 

tail of serial1: 

Running /usr/syno/etc/rc.d/J03ssdpd.sh...
/usr/bin/minissdpd
Usage: /usr/bin/minissdpd [-d] [-6] [-s socket] [-p pidfile] -i <interface> [-i <interface2>] ...

  <interface> is either an IPv4 address such as 192.168.1.42, or an
interface name such as eth0.

  By default, socket will be open as /var/run/minissdpd.sock
and pid written to file /var/run/minissdpd.pid
start SSDPD failed
Running /usr/syno/etc/rc.d/J04synoagentregisterd.sh...
Starting synoagentregisterd...
Running /usr/syno/etc/rc.d/J30DisableNCQ.sh...
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...
Starting Avahi mDNS/DNS-SD Daemon
cname_load_conf failed:/var/tmp/nginx/avahi-aliases.conf
:: Loading module hid ... [  OK  ]
:: Loading module usbhid ... [  OK  ]
============ Date ============
Sat Aug  7 15:06:55 UTC 2021
==============================
starting pid 5050, tty '': '/sbin/getty 115200 console'

 

Nothing on serial2

 

Any ideas?

Edited by cwiggs
Link to comment
Share on other sites
haydibe Guru

haydibe

Posted
Posted

I took a look at the DSM918+ build chain for 41890. The filename apollolake-gcc750_glibc226_x86_64-GPL.txz indicates that the tool chain is based on gcc7.50 now. I would expect the kernel sources to be gcc7.5 complient as well.

 

Sadly I have no copy of the kernel sources.

 

Link to comment
Share on other sites
p3t3 Junior Member

p3t3

Posted
Posted

I make loader on 6.2.4 - apollolake, test on vmware workstation (nic: e1000e)

While testing, find.synology.com is successful, but dsm install step gets error 13.

Is it works on vmware workstation? Also, loader cannot boot efi. It boots bios only?

Link to comment
Share on other sites
T-REX-XP Super Member

T-REX-XP

Posted
Posted
54 minutes ago, rlatn0123 said:

it has vid & pid but no luck

Did you try to load 1.04 via pxe. I was tried, find synology found the new device but install process is not successfully. I guess you need to start from the worked loader, then try to use new one with the same parameters. Now I'm still research the worked solution for booting 1.04 via pxe. 

Link to comment
Share on other sites
dodo-dk Advanced Member

dodo-dk

Posted
Posted (edited)
39 minutes ago, cwiggs said:

 

Used the tool chain here to create a 6.2.4 image.  The image seems to boot correctly in proxmox 6.4-13 but the VM never gets an IP, and I can't find it with find.synology.com.  I updated the s/n, nic, usb vid/pid but still no luck.  I am booting the img as sata0 after using a 'qm import'.

 

. . .

 

Any ideas?

 

In Proxmox use Virtio Nic (or E1000E)

Edited by dodo-dk
  • Like 1
Link to comment
Share on other sites
cwiggs Junior Member

cwiggs

Posted
Posted

I was able to get 6.2.4 running but when I upload the pat file I get the generic error code 13.  I logged into the system via serial0 and tailed /var/log/messeges.

  

Jan  1 00:10:47 install.cgi: RemoveUpgradeFile: Remove /tmpData/upd@te.pat...
Jan  1 00:10:47 install.cgi: Verify checksum of [/tmpData/upd@te]...
-Jan  1 00:10:48 install.cgi: Pass checksum of /tmpData/upd@te...
-Jan  1 00:10:49 install.cgi: synopartition.c:340 Patch version is: [25556], ignore the partition version check
Jan  1 00:10:49 updater: updater.c:6554 Start of the updater...
Jan  1 00:10:49 updater: updater.c:3114 orgBuildNumber = 25556, newBuildNumber=25556
Jan  1 00:10:49 updater: updater_util.c:119 fail to read company in /tmpRoot//etc.defaults/synoinfo.conf
Jan  1 00:10:49 updater: file_check_key_value.c:25 SLIBCFileGetKeyValue(runccc) failed [0x0900 file_get_key_value.c:29]
Jan  1 00:10:49 updater: updater.c:6825 ==== Start flash update ====
Jan  1 00:10:49 updater: updater.c:6829 This is X86 platform
Jan  1 00:10:49 updater: boot/boot_lock.c(228): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:2)
Jan  1 00:10:49 updater: updater.c:6252 Failed to mount boot partition
Jan  1 00:10:49 updater: updater.c:3013 No need to reset reason for v.25556 
Jan  1 00:10:49 updater: updater.c:7398 Failed to accomplish the update! (errno = 21)
Jan  1 00:10:49 install.cgi: ninstaller.c:2024 Executing [/tmpData/upd@te/updater -v /tmpData > /dev/null 2>&1] error[21]
Jan  1 00:10:49 install.cgi: ninstaller.c:224 Mount partion /dev/md0 /tmpRoot
Jan  1 00:10:49 install.cgi: ninstaller.c:1993 Moving updater for configuration upgrade...cmd=[/bin/mv -f /tmpData/upd@te/updater /tmpRoot/.updater > /dev/null 2>&1]
Jan  1 00:10:49 install.cgi: ninstaller.c:253 umount partition /tmpRoot
Jan  1 00:10:49 install.cgi: ErrFHOSTCleanPatchDirFile: After updating /tmpData/upd@te...cmd=[/bin/rm -rf /tmpData/upd@te > /dev/null 2>&1]
Jan  1 00:10:49 install.cgi: ErrFHOSTCleanPatchDirFile: Remove /tmpData/upd@te.pat...
Jan  1 00:10:49 install.cgi: ErrFHOSTDoUpgrade(2710): child process failed, retv=-21
Jan  1 00:10:49 install.cgi: ninstaller.c:2730(ErrFHOSTDoUpgrade) err=[-1]
Jan  1 00:10:49 install.cgi: ninstaller.c:2746(ErrFHOSTDoUpgrade) retv=[-21]
Jan  1 00:10:49 install.cgi: install.c:948 Upgrade by the manual patch fail.
Jan  1 00:10:49 install.cgi: install.c:1285 Upgrade by the uploaded patch /tmpData/@autoupdate/upload.pat fail.
Jan  1 00:00:00 install.cgi: ninstaller.c:253 umount partition /tmpData

 

Any ideas why that might be failing?

Link to comment
Share on other sites
cwiggs Junior Member

cwiggs

Posted
Posted (edited)
33 minutes ago, cwiggs said:

I was able to get 6.2.4 running but when I upload the pat file I get the generic error code 13.  I logged into the system via serial0 and tailed /var/log/messeges.

  



Jan  1 00:10:47 install.cgi: RemoveUpgradeFile: Remove /tmpData/upd@te.pat...
Jan  1 00:10:47 install.cgi: Verify checksum of [/tmpData/upd@te]...
-Jan  1 00:10:48 install.cgi: Pass checksum of /tmpData/upd@te...
-Jan  1 00:10:49 install.cgi: synopartition.c:340 Patch version is: [25556], ignore the partition version check
Jan  1 00:10:49 updater: updater.c:6554 Start of the updater...
Jan  1 00:10:49 updater: updater.c:3114 orgBuildNumber = 25556, newBuildNumber=25556
Jan  1 00:10:49 updater: updater_util.c:119 fail to read company in /tmpRoot//etc.defaults/synoinfo.conf
Jan  1 00:10:49 updater: file_check_key_value.c:25 SLIBCFileGetKeyValue(runccc) failed [0x0900 file_get_key_value.c:29]
Jan  1 00:10:49 updater: updater.c:6825 ==== Start flash update ====
Jan  1 00:10:49 updater: updater.c:6829 This is X86 platform
Jan  1 00:10:49 updater: boot/boot_lock.c(228): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:2)
Jan  1 00:10:49 updater: updater.c:6252 Failed to mount boot partition
Jan  1 00:10:49 updater: updater.c:3013 No need to reset reason for v.25556 
Jan  1 00:10:49 updater: updater.c:7398 Failed to accomplish the update! (errno = 21)
Jan  1 00:10:49 install.cgi: ninstaller.c:2024 Executing [/tmpData/upd@te/updater -v /tmpData > /dev/null 2>&1] error[21]
Jan  1 00:10:49 install.cgi: ninstaller.c:224 Mount partion /dev/md0 /tmpRoot
Jan  1 00:10:49 install.cgi: ninstaller.c:1993 Moving updater for configuration upgrade...cmd=[/bin/mv -f /tmpData/upd@te/updater /tmpRoot/.updater > /dev/null 2>&1]
Jan  1 00:10:49 install.cgi: ninstaller.c:253 umount partition /tmpRoot
Jan  1 00:10:49 install.cgi: ErrFHOSTCleanPatchDirFile: After updating /tmpData/upd@te...cmd=[/bin/rm -rf /tmpData/upd@te > /dev/null 2>&1]
Jan  1 00:10:49 install.cgi: ErrFHOSTCleanPatchDirFile: Remove /tmpData/upd@te.pat...
Jan  1 00:10:49 install.cgi: ErrFHOSTDoUpgrade(2710): child process failed, retv=-21
Jan  1 00:10:49 install.cgi: ninstaller.c:2730(ErrFHOSTDoUpgrade) err=[-1]
Jan  1 00:10:49 install.cgi: ninstaller.c:2746(ErrFHOSTDoUpgrade) retv=[-21]
Jan  1 00:10:49 install.cgi: install.c:948 Upgrade by the manual patch fail.
Jan  1 00:10:49 install.cgi: install.c:1285 Upgrade by the uploaded patch /tmpData/@autoupdate/upload.pat fail.
Jan  1 00:00:00 install.cgi: ninstaller.c:253 umount partition /tmpData

 

Any ideas why that might be failing?

 

Found this issue: https://github.com/RedPill-TTG/redpill-load/issues/6 looks like I can't mount the img file as a disk, but need to do it as a usb drive.  I've tried that previously with juns loaders in proxmox and it doesn't work.  Anyone have a way to mount the img file as a usb in proxmox 6.4?

 

Edit:
I added the info below to the vm config but it seems like this method of booting from usb no longer works in proxmox 6.4. 

args: -device 'qemu-xhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/{VM_ID}/synoboot.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot,bootindex=5

 

Edited by cwiggs
Link to comment
Share on other sites
dodo-dk Advanced Member

dodo-dk

Posted
Posted

@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'

 

  • Like 1
Link to comment
Share on other sites
cwiggs Junior Member

cwiggs

Posted
Posted
16 minutes ago, 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'

You are right, I ended up getting it working.  Not 100% sure what changed.  I did remove the line that says "boot", perhaps that was it.

Link to comment
Share on other sites
haydibe Guru

haydibe

Posted
Posted (edited)

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

Edited by haydibe
  • Like 2
Link to comment
Share on other sites
Orphée Guru Master

Orphée

Posted
Posted
5 hours ago, haydibe said:

Did you set the vNIC interface to E1000E before booting?

 

Haven't succeeded in the migration on ESXi 6.7 myself: the box can be found with Syno Assistent, though the migration aboards with error 13.

 

Yes, I think I did :

 

image.thumb.png.cfa73cb45639aff8fb84df3a890784b0.png

 

image.thumb.png.331c3eb08ca1eca7a9c571a8dbec7dce.png

 

image.thumb.png.94746c10416fc1295554ff9af470192c.png

 

Same with v0.3

Link to comment
Share on other sites
haydibe Guru

haydibe

Posted
Posted (edited)

I get the same console output. Though, Syno assistent finds the box and opens the browser page to migrate to the new OS version.

I assume due to missing parameters in the user_config.json the installer tries to write on the boot device and fails.  

 

I took these parameters from the old grub.cfg and added them to the user_config.json.

    "bootdev": "sata", 
    "sata_args": "sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1 SasIdxMap=0" 

    "bootdev": "sata", 
    "sata_args": "sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1 SasIdxMap=0"

 

Still no luck. 

Edited by haydibe
  • Thanks 1
Link to comment
Share on other sites
Orphée Guru Master

Orphée

Posted
Posted
21 minutes ago, haydibe said:

I get the same console output. Though, Syno assistent finds the box and opens the browser page to migrate to the new OS version.

I assume due to missing parameters in the user_config.json the installer tries to write on the boot device and fails.  

 

I took these parameters from the old grub.cfg and added them to the user_config.json.

    "bootdev": "sata", 
    "sata_args": "sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1 SasIdxMap=0" 


    "bootdev": "sata", 
    "sata_args": "sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1 SasIdxMap=0"

 

Still no luck. 

Ok actually I found it on my routeur dhcp lease, I'm trying a new install, I will see once PAT downloaded.

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...