Jump to content
XPEnology Community

RedPill - the new loader for 6.2.4 - Discussion


Recommended Posts

5 minutes ago, sbtec said:

@pocopico Joining you in the ranks of the mighty HP Gen7, compiled 3615xs 7.01 from latest lkm/loader pair using syno toolkit.

Have booted/installed on a blank hard drive. Rebooted and crashed deliberately a few times, still ok.

In the process of installing some software and will continue testing, as per other posts here the Info Centre in Control Panel contains no detail in the General section.

 

Previous install of 6.2.4 from earlier lkm/loader (see post Aug 1st) has been in use 24/7 until now. 😀

 

 

 

I actually feel lucky to even be able to install 7.01 on my G7 that for some reason refuses to die. 😂

Link to comment
Share on other sites

Hi! When i try to install on proxmox i had error mount md0


[  119.952767] EXT4-fs (md0): mounting ext3 file system using the ext4 subsystem
[  120.016877] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[  121.191939] <redpill/rtc_proxy.c:37> MfgCompatTime raw data: sec=9 min=1 hr=9 wkd=2 day=7 mth=8 yr=121
[  121.193622] <redpill/rtc_proxy.c:95> Writing BCD-based RTC
[  121.194653] RTC time set to 2021-09-07  9:01:09 (UTC)
[  121.209845] EXT4-fs (md0): mounting ext3 file system using the ext4 subsystem
[  121.277528] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[  121.392446] EXT4-fs (md0): mounting ext3 file system using the ext4 subsystem
[  121.402739] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[  121.423260] EXT4-fs (md0): mounting ext3 file system using the ext4 subsystem
[  121.440052] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[  121.515162] md0: detected capacity change from 2549940224 to 0
[  121.516100] md: md0: set sdh1 to auto_remap [0]
[  121.516890] md: md0: set sdi1 to auto_remap [0]
[  121.517703] md: md0 stopped.
[  121.518220] md: unbind<sdh1>
[  121.521023] md: export_rdev(sdh1)
[  121.521535] md: unbind<sdi1>
[  121.525034] md: export_rdev(sdi1)
[  121.568367] md1: detected capacity change from 2147418112 to 0
[  121.569287] md: md1: set sdh2 to auto_remap [0]
[  121.569996] md: md1: set sdi2 to auto_remap [0]
[  121.570701] md: md1 stopped.
[  121.571170] md: unbind<sdh2>
[  121.577035] md: export_rdev(sdh2)
[  121.577606] md: unbind<sdi2>
[  121.584056] md: export_rdev(sdi2)
[  124.686739] md: bind<sdh1>
[  124.687362] md: bind<sdi1>
[  124.688378] md/raid1:md0: active with 2 out of 16 mirrors
[  124.703310] md0: detected capacity change from 0 to 2549940224
[  126.057168] EXT4-fs (md0): mounting ext3 file system using the ext4 subsystem
[  126.078430] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[  127.766177] md: bind<sdh2>
[  127.767187] md: bind<sdi2>
[  127.767939] md/raid1:md1: active with 2 out of 16 mirrors
[  127.785579] md1: detected capacity change from 0 to 2147418112
[  128.446373] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[  128.466030] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[  128.554349] <redpill/rtc_proxy.c:222> Got an invalid call to rtc_proxy_set_auto_power_on
[  128.559532] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[  128.578612] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)

 

 

Link to comment
Share on other sites

28 minutes ago, shibby said:

I tested fresh install 7.0.1 with redpill on my bare metal - it works. Now i wanted to migrate from 6.2.3 to 7.0.1. What kind of steps should i do? I turn off xpenology, replace flashdrive from jun`s loader to redpill and power on. Result is: i see nothing in synology assistant. I thought i will see my NAS with status "migrate" or something.

 

any suggestion?

if you have a DHCP in your network try to see ip assigned, if you know mac-address of your baremetal, once targeted you can poi browser to this ip 

Link to comment
Share on other sites

In /var/log/messages
Sep  7 09:13:13 updater: updater.c:7045 ==== Start flash update ====
Sep  7 09:13:13 updater: updater.c:7049 This is X86 platform
Sep  7 09:13:13 updater: boot/boot_lock.c(228): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:2)
Sep  7 09:13:13 updater: updater.c:6510 Failed to mount boot partition
Sep  7 09:13:13 updater: updater.c:3134 No need to reset reason for v.42214 
Sep  7 09:13:13 updater: updater.c:7652 Failed to accomplish the update! (errno = 21)
Sep  7 09:13:13 install.cgi: ninstaller.c:1546 Executing [/tmpData/upd@te/updater -v /tmpData > /dev/null 2>&1] error[21]
Sep  7 09:13:15 install.cgi: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot
Sep  7 09:13:15 install.cgi: ninstaller.c:1515 Moving updater for configuration upgrade...cmd=[/bin/mv -f /tmpData/upd@te/updater /tmpRoot/.updater > /dev/null 2>&1]
Sep  7 09:13:15 install.cgi: ninstaller.c:152 umount partition /tmpRoot
Sep  7 09:13:15 install.cgi: ErrFHOSTCleanPatchDirFile: After updating /tmpData/upd@te...cmd=[/bin/rm -rf /tmpData/upd@te > /dev/null 2>&1]
Sep  7 09:13:15 install.cgi: ErrFHOSTCleanPatchDirFile: Remove /tmpData/upd@te.pat...
Sep  7 09:13:15 install.cgi: ErrFHOSTDoUpgrade(1794): child process failed, retv=-21
Sep  7 09:13:15 install.cgi: ninstaller.c:1811(ErrFHOSTDoUpgrade) err=[-1]
Sep  7 09:13:15 install.cgi: ninstaller.c:1815(ErrFHOSTDoUpgrade) retv=[-21]
Sep  7 09:13:15 install.cgi: install.c:409 Upgrade by the manual patch fail.
Sep  7 09:13:15 install.cgi: install.c:678 Upgrade by the uploaded patch /tmpData/@autoupdate/upload.pat fail.

 

any ideas?

Link to comment
Share on other sites

I had a couple more odd reboots of my system this morning. They always seem to occur shortly after a reboot. I'd restarted the system after updating firmware on the iLO card in my system, and the server rebooted almost immediately after it had booted into DSM (I think it managed about 3 minutes uptime), then rebooted again shortly afterwards. Looking in /var/log/messages for entries just before it reboots each time there's nothing that stands out, other than that it's typically doing stuff you'd expect after the system had just rebooted: starting docker containers and registering certificates for a couple of webhosts I have on the server

Link to comment
Share on other sites

Question: I have an HP NC360T PCIe NIC card in my system. I'm only using one interface, so have only declared one of them in my user_config.json. Is this a problem?

 

I notice in Control Panel in DSM that two interfaces are detected, and both have the same MAC address (the one I declared for the interface that I'm actually using). Likewise, running 'ifconfig' from the cli reports two interfaces with the same MAC address. I know that an OSI 7-layer network stack shouldn't have an issue with multiple interfaces on a system having the same MAC address (it's standard on Sun machines, for example), but will DSM complain about this?

 

Next time I rebuild the boot stick I'll be sure to declare both interfaces, but am just curious for now.

Edited by WiteWulf
Link to comment
Share on other sites

firmware: DS918+ 6.2.4, redpill-6.2.4.

Hardware: Lenovo M93p (i5 4gen, one SSD drive) - this is only for test.

 

first try: turn off nas, replace flashdrive with redpill-7.0, turn on nas. Result: nas is not available, no ping, empty list in synology assistant

 

second try: from DSM 6.2.4 i run manually update to 7.0-41890. NAS has been restarted (still runned on redpil-6.2.4) goes to recovery state. Tried to continue recovery, NAS restarted but still was in recovery mode. So i replace loader to redpill-7.0 and run recovery once again but after few second i back to recovery main page.

I`m testing and trying to figure out a working procedure to upgrade Xpenology from 6.2.3 to 7.0 before i will do this on my prime NAS.

 

 

  • Thanks 1
Link to comment
Share on other sites

My spare baremetal PC (Optiplex 9020 SFF) starts the boot from USB and gets stuck at the Booting Kernel message.  I can then find the device from my laptop by either using find.synology.com or the IP address. The issue I have from there is that I get the error message that others appear to have had.

 

We've detected an error on the hard drives (3,4,5,6) and the SATA ports have also been disabled.

 

I have tried this using both UEFI and Legacy boot from within the BIOS and get the same issue. Does anyone have any tips to get past this point?

Link to comment
Share on other sites

2 minutes ago, Franks4fingers said:

We've detected an error on the hard drives (3,4,5,6) and the SATA ports have also been disabled.

 

had the same. Solution for me was added
 

DiskIdxMap=00 SataPortMap=1 SasIdxMap=0

 

to boot/grup/grub.cfg file (line 45: linux /zImage ...)

  • Like 1
Link to comment
Share on other sites

On 9/4/2021 at 1:24 PM, tocinillo2 said:

Compiled 7.0.1 with last BSP patch and works perfect ;)

 

https://drive.google.com/file/d/1CqqhO-TBdwOff0dH54iP-XPdrhzgvtNR/view?usp=sharing

 

- Add UEFI support.
- Deleted twice EFI folder.
- Fixed SynoBoot_EFI place.
- Compiled with last BSP Patch for 7.0.1.
- Insmod efi_gop into EFI.
- Tested with Baremetal and works fine (Astock 3455-ITX).
- After installation (the reboot process can take 15-20 minutes) you have to install File Station manually: https://www.synology.com/en-us/support/download/DS918+#system (select DSM 7.0), find and download File Station SPK and install it in Package Center.

 

1RZ3yro.jpg

 

I successfully upgraded my elitedesk 800 G2 (i7-6700) from 6.2.3 to 7.0.1

Just added DiskIdxMap=00 SataPortMap=4 SasIdxMap=0 to config!

Everything works fine and super fast, also face recognition on photos. File Station was already installed (maybe because I did an upgrade)

Thank you very much!

Edited by TSo3
  • Like 1
Link to comment
Share on other sites

5 minutes ago, shibby said:

 

had the same. Solution for me was added
 


DiskIdxMap=00 SataPortMap=1 SasIdxMap=0

 

to boot/grup/grub.cfg file (line 45: linux /zImage ...)

 

5 minutes ago, TSo3 said:

 

I successfully upgraded my elitedesk 800 G2 (i7-6700) from 6.2.3 to 7.0.1

Just added DiskIdxMap=00 SataPortMap=4 SasIdxMap=0 to config!
Thank you very much!

That line in my grub.cfg file is as follows:

 

linux /zImage netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=1 syno_hdd_detect=0 elevator=elevator root=/dev/md0 loglevel=15 log_buf_len=32M mac1=123456789012 vid=0x0781 pid=0x5572 console=ttyS0,115200n8 sn=xxxxxxxxxxxxx earlyprintk syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS918+ vender_format_version=2 

 

Did you add the DiskIdxMap= SataPortMap= SasIdxMap= values to the end of that line?

 

Also, how did you derive what the SataPortMap value needed to be?

 

Cheers for the help.

Link to comment
Share on other sites

Just now, shibby said:

 

can you discribe steps which yuo made?


I did exactly what the old guide says. Mount the img with OSFMount and added VIN, PID, SN, MAC and DiskIdxMap=00 SataPortMap=4 SasIdxMap=0 on grub.
After that i just put the usb on PC and i started the upgrade

Link to comment
Share on other sites

3 minutes ago, Franks4fingers said:

 

That line in my grub.cfg file is as follows:

 

linux /zImage netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=1 syno_hdd_detect=0 elevator=elevator root=/dev/md0 loglevel=15 log_buf_len=32M mac1=123456789012 vid=0x0781 pid=0x5572 console=ttyS0,115200n8 sn=xxxxxxxxxxxxx earlyprintk syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS918+ vender_format_version=2 

 

Did you add the DiskIdxMap= SataPortMap= SasIdxMap= values to the end of that line?

 

Also, how did you derive what the SataPortMap value needed to be?

 

Cheers for the help.


linux /zImage netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=1 syno_hdd_detect=0 elevator=elevator root=/dev/md0 loglevel=15 log_buf_len=32M mac1=xxxxxxxxxxx vid=0xxxxx pid=0xxxxx console=ttyS0,115200n8 DiskIdxMap=00 SataPortMap=4 SasIdxMap=0 sn=xxxxxxxxxxx earlyprintk syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS918+ vender_format_version=2

That is my config. I copy SataPortMap=4 from my previous (6.2.3) config. As for DiskIdxMap=00 SasIdxMap=0 I set them to 0 just for check.
So i dont know what the SataPortMap DiskIdxMap SasIdxMap value needed to be. I suppose i am lucky

  • Like 2
Link to comment
Share on other sites

4 minutes ago, Franks4fingers said:

Did you add the DiskIdxMap= SataPortMap= SasIdxMap= values to the end of that line?

 

to be honest i put those values between "HddHotplug=0 withefi" but this propably is not important, it may be in the middle, it may be at the end :)

 

6 minutes ago, Franks4fingers said:

Also, how did you derive what the SataPortMap value needed to be?

 

testing, testing, testing. I tried few options and this will work for me. Just try. If it will not work for you, then change SataPortMap value.

  • Like 2
Link to comment
Share on other sites

another try and another fail.

 

fresh/clean instalation of DS918+ 6.2.3. Swaped usb drive with redpill-7.0.1 and power on PC. Result: NAS is not available, no ping, not found by assistant.

 

The strange is that i replace HDD to the formated/clean then NAS has been available in network (found by assistant) and ready to install fresh DSM.

 

i tested redpill compiled by myself and also shared by @tocinillo2. Result is the same. No have idea what else i can do.

 

Best Regards.

Link to comment
Share on other sites

Just now, nemesis122 said:

Maybe its releated to this and you need 3615 Bromolow


i have 4-gen CPU (Haswell). I can install DS918+ 6.2.3 (jun). I can install DS918+ 7.0.1 on fresh HDD using redpill. I can even upgrade from 6.2.3 (jun) to 6.2.4 (redpill) using DS918+ image.

But i can`t upgrade from 6.2.3/6.2.4 to 7.x 😕

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...