RedPill - the new loader for 6.2.4 - Discussion

ThorGroup

By ThorGroup,
in Developer Discussion Room

 Share Followers 180

Recommended Posts

YouMeXPE

YouMeXPE 0

Posted
Posted
1 hour ago, WiteWulf said:

Everyone that's contacted me so far has been using either Xeon or Celeron CPUs, I've not heard from anyone with non-Intel CPU so far. Also, I (and others) extensively used docker on 6.2.3 and earlier versions on Jun's boot loader. These problems have only been observed on DSM 6.2.4 and 7.x since moving to redpill, and only on DS3615xs.


Would it make sense to create a 6.2.3 / Redpill combo to test if it's related to either Redpill OR 6.2.4 ?
As I see it, there have been two changes: Jun's -> Redpill and 6.2.3 -> 6.2.4

Link to post
Share on other sites
altas

altas 33

Posted
Posted
1 hour ago, altas said:

is it possible to upgrade from DSM 7.0 to DSM 7.0.1  with the DSM7.0 Redpill Loader ?

Upgrade done!

1. download the 7.0.1 from Synology

2. start upgrade on the currrent DSM 7.0

3. compile the Loader for 7.01 (i used a new USB Stick)

4.Shutdown the GEn8 replace the USB Stick with the new 7.0.1 Loader onit

5. Start the Gen8 and maybe 5min later you should have access again on the WebPage

Link to post
Share on other sites
erkify

erkify 0

Posted
Posted

Hp Gen8 - Baremetal - DS3615xs - DSM 7.0.1

CPU Intel (R) Xeon (R) E3-1265 V2

 

remove from "automatic" to disabled IPv6, update Docker to version 1239 and activate only Pihole and Tautulli, at the moment 45 minutes on without restart. Before that activate these two containers and later activate the portainer, at the moment it restarted, for now I'm going to try these two to see what happens.

 

* I have also updated ilo to version 2.78

 

 

Link to post
Share on other sites
nemesis122

nemesis122 29

Posted
Posted (edited)

hi at the moment im testing the same yep and it seems stable 

remove from "automatic" to disabled IPv6, update Docker to version 1239

with JD2 and Filezilla😆

 

* I have also updated ilo to version 2.78

*  also and the bios to 2019

*  and provisioning to the newest version 

*  now running virtual DSM 

 

btw i have update my other Gen 8 to 1.03b with 3617 before it was 1.03b 3615 and smb has increased from 250MB to 900MB why?????

Specs: 1240 v2 Xeon with 16gb RAM 4x 6tb wd Red 1TB SSD as chache drive and Intel 520 SFP+ 

Edited by nemesis122
Link to post
Share on other sites
rok1

rok1 9

Posted
Posted

I built a new nas using a SuperMicro C7B250-CB-ML w/i7-7700/32gb ram. I added an old Intel 1000PT and it's working just fine on 918+ 7.0.1.

 

I run one docker (Tautulli) and 1 VM (Valheim Server using debian). I did have to install opkg (lmsensor support) via command line, but otherwise, it's working great.

Link to post
Share on other sites
nemesis122

nemesis122 29

Posted
Posted (edited)

All night the server was running and enjoyed his life.

update Docker to version 1239

this morning i used filezilla and copy files over the ftp protocoll after 500GB the server lost the network connection i  have to reboot the server  and started  Docker again and the server reboots again crash  --> set docker new JD2 and filezilla and the Server reboots again crash

Console output:

[  250.810133] Call Trace:
[  250.821880]  <NMI>  [<ffffffff814a2759>] ? dump_stack+0xc/0x15
[  250.850334]  [<ffffffff814a16b1>] ? panic+0xbb/0x1df
[  250.875015]  [<ffffffff810a9eb8>] ? watchdog_overflow_callback+0xa8/0xb0
[  250.907339]  [<ffffffff810db7d3>] ? __perf_event_overflow+0x93/0x230
[  250.938568]  [<ffffffff810da612>] ? perf_event_update_userpage+0x12/0xf0
[  250.970751]  [<ffffffff810152a4>] ? intel_pmu_handle_irq+0x1b4/0x340
[  251.001576]  [<ffffffff814a9d06>] ? perf_event_nmi_handler+0x26/0x40
[  251.032170]  [<ffffffff814a944e>] ? do_nmi+0xfe/0x440
[  251.056806]  [<ffffffff814a8a53>] ? end_repeat_nmi+0x1e/0x7e
 

Edited by nemesis122
Link to post
Share on other sites
WiteWulf

WiteWulf 145

Posted
Posted

The docker crash behaviour seems to be quite specific to individuals' set up. A few people here have tried to run influxdb, at my suggestion, with no problems, while it crashes my system each time. Others are having repeated problems with jdownloader2, which I tried and was completely stable. Since we're all running with different data, I think this may be influenced by the load generated by the docker containers causing ppl problems (Java and database containers seem particularly problematic) 🤔

 

Likewise, while influxdb causes me problems, I've several other docker containers that continue to run on my system without problems.

Link to post
Share on other sites
ct85msi

ct85msi 17

Posted
Posted

I have DS918+ booloader, baremetal. I have no problem with docker. Even Face detection works fine. No unexpected reboots, no errors.

  

root@Apollo:~# tail -f /var/log/synofoto.log
2021-09-19T21:13:25+03:00 Apollo synofoto-notify-center[15504]: /source/synofoto/src/daemon/notify-center/process/sdk_request.cpp:14 User Home Enable Change
2021-09-19T21:19:03+03:00 Apollo synoscgi_SYNO.Foto.Setting.User_1_set[18046]: /source/synofoto/src/webapi/module/Foto/Setting/user_setting.cpp:243 User sorin(1026) enable FaceExtraction
2021-09-19T21:19:03+03:00 Apollo synofoto-notify-center[15504]: /source/synofoto/src/daemon/notify-center/process.cpp:45 Reload File Extension
2021-09-19T21:19:03+03:00 Apollo synofoto-task-center[15273]: /source/synofoto/src/daemon/task-center/process/process_daemon_action.cpp:58 Reload File Extension
2021-09-19T21:21:54+03:00 Apollo synofoto-face-extraction[15502]: /source/synophoto-plugin-face/src/face_plugin/main.cpp:22 face plugin init
2021-09-19T21:22:42+03:00 Apollo synofoto-task-center[15273]: /source/synofoto/src/daemon/task-center/plugin-monitor/plugin_monitor_send_request.cpp:71 send unload plugin 4
2021-09-19T21:22:42+03:00 Apollo synofoto-task-center[15273]: /source/synofoto/src/daemon/task-center/person/face_extraction_queue.cpp:172 FaceExtractionQueue Collecting
2021-09-19T21:22:46+03:00 Apollo synofoto-face-extraction[15502]: /source/synophoto-plugin-face/src/face_plugin/main.cpp:28 face plugin shutdown
2021-09-19T21:24:46+03:00 Apollo synofoto-task-center[15273]: /source/synofoto/src/daemon/task-center/plugin-monitor/plugin_monitor_send_request.cpp:71 send unload plugin 5
2021-09-19T21:24:48+03:00 Apollo synofoto-person-clustering[15514]: /source/synofoto/src/daemon/plugin-person/clustering_plugin_handler.cpp:175 Clustering plugin shutdown

 

  • Thanks 1
Link to post
Share on other sites
WiteWulf

WiteWulf 145

Posted
Posted (edited)
12 minutes ago, toyanucci said:

Created the bootable USB but when I try to boot it hangs at starting the kernel. Happens with apollolake 7.0 and 7.0.1.  Anyone able to point me in the right direction? 🥲

You seeing something like this?

image.thumb.png.540b6c00a0337c73cf58c37310f338a1.png

 

If so it's not hanging, it's just there's no more output to the screen from that point as there's no frame buffer driver in the Synology kernel. Jun's bootloader used to put a message on screen to this effect, something that would be quite helpful in redpill, too, I think.

 

Further boot information is output to the serial port. If you're on a machine with a physical serial port you can view it there. If you're using ESXi or proxmox you'll need to attach a virtual serial port. If you're using some server-grade hardware with lights-out management you may be able to attach to it via ssh or web UI.

 

You should be able to connect to the server's web UI once it boots and gets a DHCP lease, though. Have a look in your DHCP server logs to find it's IP address, or use the Synology Assistant tool to find it.

Edited by WiteWulf
Link to post
Share on other sites
toyanucci

toyanucci 5

Posted
Posted (edited)
16 minutes ago, WiteWulf said:

You seeing something like this?

image.thumb.png.540b6c00a0337c73cf58c37310f338a1.png

 

If so it's not hanging, it's just there's no more output to the screen from that point as there's no frame buffer driver in the Synology kernel. Jun's bootloader used to put a message on screen to this effect, something that would be quite helpful in redpill, too, I think.

 

Further boot information is output to the serial port. If you're on a machine with a physical serial port you can view it there. If you're using ESXi or proxmox you'll need to attach a virtual serial port. If you're using some server-grade hardware with lights-out management you may be able to attach to it via ssh or web UI.

 

You should be able to connect to the server's web UI once it boots and gets a DHCP lease, though. Have a look in your DHCP server logs to find it's IP address, or use the Synology Assistant tool to find it.

I wasn't able to connect to the web ui though I had left it for like 5 minutes in that state. Maybe something else has gone wrong 🤔. I'll try again when I get home and hope for the best! 

 

Thanks for the quick reply!

 

Last question...about how long would it take before the web ui becomes accessible on boot?

Edited by toyanucci
Link to post
Share on other sites
toyanucci

toyanucci 5

Posted
Posted (edited)
59 minutes ago, WiteWulf said:

Sounds like your system isn't bringing up the network, then. Check that your hardware is supported. If you post full details of your system people here can probably let you know what's supported or not.

I'm using the ASRock J4105 ITX motherboard. The network card it uses is the Realtek RTL8111H.

 

I guess the problem is the NIC...I just assumed it worked but I guess I'll need to get a compatible one.  I'll search the thread when I get home or if you have any recommendations I'd appreciate it!

Edited by toyanucci
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Followers 180
Go to topic listing