Jump to content
XPEnology Community

RedPill - the new loader for 6.2.4 - Discussion


Recommended Posts

I'm also seeing this one appear less regularly:

[ 2393.339671] <redpill/smart_shim.c:340> ATA_CMD_ID_ATA confirmed SMART support - noop
[ 2393.380207] <redpill/smart_shim.c:794> Handling ioctl(0x30d) for /dev/sdc
[ 2393.413945] <redpill/smart_shim.c:809> sd_ioctl(0x30d) - not a hooked ioctl, noop

0x30d appears to be querying the HDD for it's identity, HDIO_GET_IDENTITY, ie. the disk serial number.

 

Again, mdadm seems happy with the state of my disks/volumes, as does Storage Manager in DSM (which is really just a GUI frontend to mdadm anyway).

 

*edit*

 

Indeed, issuing 'hdparm -i /dev/sde' from the command line immediately results in the following to appear in the console output:

 

[ 3550.279075] <redpill/smart_shim.c:794> Handling ioctl(0x304) for /dev/sde
[ 3550.312542] <redpill/smart_shim.c:809> sd_ioctl(0x304) - not a hooked ioctl, noop
[ 3550.349957] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sde
[ 3550.383866] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[ 3550.424725] <redpill/smart_shim.c:794> Handling ioctl(0x30d) for /dev/sde
[ 3550.457940] <redpill/smart_shim.c:809> sd_ioctl(0x30d) - not a hooked ioctl, noop

 

...although hdparm itself outputs the following with no error:

bash-4.4# hdparm -i /dev/sde

/dev/sde:

 Model=OCZ-VERTEX2, FwRev=1.37, SerialNo=OCZ-8N58I75919N424M6
 Config={ Fixed }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
 BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=1
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=117231408
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4 
 DMA modes:  mdma0 mdma1 mdma2 
 UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6 
 AdvancedPM=no WriteCache=disabled
 Drive conforms to: unknown:  ATA/ATAPI-2,3,4,5,6,7

 * signifies the current active mode

 

Something in DSM is querying the storage devices in a way that smart_shim isn't equipped to handle, or doesn't like.

 

Having said that, these don't seem to be errors. Did someone just leave debug turned on?

 

Yeah, having had a quick look over smart_shim.c itself, it appears that the actions undertaken on lines 794 and 809 (as referenced in the logging output) are announcing that it's not a special drive command that needs to be handled by the shim, and should simply be proxied to the device as-is:

https://github.com/RedPill-TTG/redpill-lkm/blob/021ed51e7fb35848b9bf80c49f82ee3d95c1f26e/shim/storage/smart_shim.c#L787-L812

 

It's code that's meant to emulate SMART on device that don't have it natively, which the disks in my system do. Same goes for the ATA_CMD_ID_ATA messages, it's confirming that a valid SMART response was received from the drive and there's no need to handle it with the shim.

 

I'm convinced this is simply a case of excessive logging, and nothing's actually going wrong.

Edited by WiteWulf
Link to comment
Share on other sites

33 minutes ago, WiteWulf said:

I just booted my baremetal Gen8 off an image created with @ThorGroup's latest redpill code (as of this release), and haydibe's 0.8 toolchain. This is using bromolow 7.0.1-RC1 (42214) It booted successfully, all disks and NICs in my configuration are online, but I'm seeing the following on the serial console every 10-60 seconds (it is not occurring on a regular pattern):

The messages appear in clumps for each SATA device in my system (four HDDs and SSD used for read cache). It's as if something is trying to query the disks at a low level and failing as the redpill smart_shim doesn't handle it (hence the 'noop').

 

0x31f appears to be "HDIO_DRIVE_CMD execute a special drive command"

0x2285 is SG_IO, which appears to be used for sending SCSI commands to a device

 

The system appears to be fully functional other than the logging described above. NB these messages were not present in the console output on ThorGroup's previous release.

 

*edit*

 

My guess is it's to do with this:
 


SCSI drives monitoring subsystem
This is more of a dev-only functionality, but lies in the core of all the features described above. In short, Linux kernel contains a mechanism for publishing and subscribing to events. Unfortunately it's a rather new and niche subsystem. The SCSI driver, as one of the oldest parts of the Linux kernel, doesn't support the notifications. In order to react to new drives being connected to the system we developed an extension for the SCSI driver adding that functionality. We will probably pursue upstreaming of these changes, so one day they can land in the kernel natively.
 
For details see the following commits:
https://github.com/RedPill-TTG/redpill-lkm/commit/098bae23fe21ccd495e57b846539704899fda639 (add the notification subsystem)
https://github.com/RedPill-TTG/redpill-lkm/commit/ccc58c0883c3f0cc8a8599918cc0d5cd9491f678 (extract common SCSI functionality to a submodule)

 


When you say "NICs in my config are online", you're reffering to the onboard ones?
I watched this thread from the start and everything you posted. I'm in the same situation, gen8 baremetal, 16gb + 1230v2, but with onboard nics.
I have jun's loader + dsm 6.2.3.

I tried redpill, but i was unsuccesfull, like you, because my onboard nics were offline.

What should i try next?

Link to comment
Share on other sites

On 9/13/2021 at 3:19 PM, p33ps said:

Can someone paste here their VM Proxmox setup for a DS3615xs boot? I am having huge CPU issues when the Photos app starts their face recognition index process. It blocks the VM completely and I need to stop-start it. It never finishes the recognition process. This is the CPU and network status when it starts:

 

image.thumb.png.7af0e2b3b2153c4356eb0637a4a1b9f8.png

 

Current hardware setup is:

 

HP Proliant Microserver G8

16GB RAM

Xeon E3 1265l v2

1 x 1TB 870 SSD

3 x 12TB Seagate Exos X16

1 x 12TB Seagate IronWolf Pro

DSM 7.0.1 RC.

 

I've tested it with LVM and ZFS storage pool.

 

Thanks!

 

Hi, i found the problem. You need to change the CPU Settings from kvm64 to host or haswell.

So it works with my E3-1241 V3 CPU - Bromolow - 7.0.1-42214 setup.

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

Just now, Fallen said:


When you say "NICs in my config are online", you're reffering to the onboard ones?
I watched this thread from the start and everything you posted. I'm in the same situation, gen8 baremetal, 16gb + 1230v2, but with onboard nics.
I have jun's loader + dsm 6.2.3.

I tried redpill, but i was unsuccesfull, like you, because my onboard nics were offline.

What should i try next?

No, if you look in my sig (I'm aware it doesn't display on mobile devices, sorry) you'll see I'm running a PCIe HP NC360T dual GigE NIC instead of the onboard Broadcom adapter (which I have disabled). It should be possible to add the correct driver (tg3.ko, iirc) to a boatloader image and some folk in this thread have been working on it.

Link to comment
Share on other sites

The logs are located in /var/log/synobootup.log to follow the error messages.

 

Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:340> ATA_CMD_ID_ATA confirmed SMART support - noop
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:794> Handling ioctl(0x800c0910) for /dev/sdb
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:809> sd_ioctl(0x800c0910) - not a hooked ioctl, noop
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:794> Handling ioctl(0x800c0910) for /dev/sda
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:809> sd_ioctl(0x800c0910) - not a hooked ioctl, noop
Sep 14 18:12:21 Apollo synocrond[9775]: scemd_connector/scemd_connector.c:195 Scemd isn't ready, so cannot get scemd status.
Sep 14 18:12:21 Apollo synocrond[9775]: utils.cpp:73 Fail to SYNOScemdStatusGet() (No such file or directory)
Sep 14 18:12:21 Apollo [10168]: scemd_connector/scemd_connector.c:139 Fail to sendto() for scemd connector client.
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:794> Handling ioctl(0x800c0910) for /dev/sdc
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:809> sd_ioctl(0x800c0910) - not a hooked ioctl, noop
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:794> Handling ioctl(0x30d) for /dev/sdc
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:809> sd_ioctl(0x30d) - not a hooked ioctl, noop
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:794> Handling ioctl(0x31f) for /dev/sdc
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:340> ATA_CMD_ID_ATA confirmed SMART support - noop
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:794> Handling ioctl(0x800c0910) for /dev/sdc
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:809> sd_ioctl(0x800c0910) - not a hooked ioctl, noop
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:794> Handling ioctl(0x31f) for /dev/sdc
Sep 14 18:12:21 Apollo bash[9763]: Boot not ready
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:794> Handling ioctl(0x30d) for /dev/sdb
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:809> sd_ioctl(0x30d) - not a hooked ioctl, noop
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:794> Handling ioctl(0x31f) for /dev/sdb
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:794> Handling ioctl(0x31f) for /dev/sdc
Sep 14 18:12:21 Apollo systemd[1]: Started Remove session if the option enabled..
Sep 14 18:12:21 Apollo systemd[1]: Starting Synology CGI Auth Daemon...
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:794> Handling ioctl(0x30d) for /dev/sda
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:809> sd_ioctl(0x30d) - not a hooked ioctl, noop
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:794> Handling ioctl(0x31f) for /dev/sda
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:794> Handling ioctl(0x30d) for /dev/sdc
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:809> sd_ioctl(0x30d) - not a hooked ioctl, noop
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:794> Handling ioctl(0x31f) for /dev/sdc
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:340> ATA_CMD_ID_ATA confirmed SMART support - noop
Sep 14 18:12:21 Apollo kernel: <redpill/smart_shim.c:794> Handling ioctl(0x30d) for /dev/sdd

 

Link to comment
Share on other sites

@WiteWulf I know you use the serial port emulator on ILO 4 . 

 

I have my GEN8 now booting with the onboard NIC and discoverable , but my serial log stop at :

 

 

[    2.758884] <redpill/uart_swapper.c:427> ======= OUTPUT ON THIS PORT WILL STOP AND CONTINUE ON ANOTHER ONE (swapping ttyS1 & ttyS0) =======

[    2.762939] <redpill/uart_swapper.c:429> ### LAST MESSAGE BEFORE SWAP ON "OLD" PORT ttyS1<=>ttyS0

 

Are you doing something to resolve this ? 

Link to comment
Share on other sites

24 minutes ago, scoobdriver said:

@WiteWulf I know you use the serial port emulator on ILO 4 . 

 

I have my GEN8 now booting with the onboard NIC and discoverable , but my serial log stop at :

 

 

[    2.758884] <redpill/uart_swapper.c:427> ======= OUTPUT ON THIS PORT WILL STOP AND CONTINUE ON ANOTHER ONE (swapping ttyS1 & ttyS0) =======

[    2.762939] <redpill/uart_swapper.c:429> ### LAST MESSAGE BEFORE SWAP ON "OLD" PORT ttyS1<=>ttyS0

 

Are you doing something to resolve this ? 

No, it's weird, someone else (@altas?) contacted me with exactly the same problem. Mine "just works" and continues to output to the vsp, it even offers me a login prompt. I'm running with Advanced iLO license on my system (only cost me £10 on eBay) which also allows for virtual boot media.

 

Just to be clear, to access the console, I:

- ssh to the ilo, ie. 'ssh Administrator@diskstation-ilo'

- from the </>hpiLO-> prompt I issue the 'vsp' command to launch the virtual serial port

- I don't login if all I want to see is console output

 % ssh Administrator@diskstation-ilo
Administrator@diskstation-ilo's password: 
User:Administrator logged-in to diskstation-ilo.osx.ninja(192.168.1.11 / FE80::D2BF:9CFF:FE45:F58A)

iLO Advanced 2.78 at  Apr 28 2021
Server Name: diskstation-iLO
Server Power: On




</>hpiLO-> vsp

Virtual Serial Port Active: COM1

Starting virtual serial port.
Press 'ESC (' to return to the CLI Session.


Password: [ 6968.613699] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sda
[ 6968.614727] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdb
[ 6968.614728] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[ 6968.616323] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdc
[ 6968.616324] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[ 6968.617563] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdd
[ 6968.617564] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[ 6968.859345] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop

 

Edited by WiteWulf
Link to comment
Share on other sites

@scoobdriver @altas I've just had a grep through /var/log/synobootup.log on my system and can't see any reference to 'redpill/uart_swapper', which seems to be the culprit for you two.

 

Here's the code, see if you can figure out what's going on:

https://github.com/RedPill-TTG/redpill-lkm/blob/master/internal/uart/uart_swapper.c

 

It seems to be a module written to "fix" behaviour in some kernels that erroneously swaps the console output to an alternate tty by swapping it back again. For some reason this is being called unnecessarily on your systems, and swapping the console output away from your active, functioning virtual tty. FYI, I'm running a bromolow 7.0.1-RC1 42214 image.

 

I don't know why this is happening for you, or why it's not happening for me. Closer inspection of the code (or explanation from @ThorGroup) may help.

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

@pocopico

Thank you for your rd.gz with the .ko's for the Gen8 onboard NIC .. 

on bare metal this boots, and I am able to see the machine on the network and reach the Web assistant . 

At this moment it is not seeing my HDD , (on a HBA card flashed IT ) 

not sure if I need to modify the DiskIdxMap values or SataPortMap (I did with Juns) 

 

However I am seeing these and other args / parameters not been recognised and been ignored as per the serial output below (Iv'e removed my real Mac and Serial) 

is anybody else seeing this  ?

 

[    2.150381] Freeing initrd memory: 34164k freed
[    2.156393] redpill: module verification failed: signature and/or required key missing - tainting kernel
[    2.159947] <redpill/redpill_main.c:44> ================================================================================================
[    2.164332] <redpill/redpill_main.c:45> RedPill v0.5-git-021ed51 loading...
[    2.167431] <redpill/call_protected.c:55> Got addr ffffffff8119d370 for cmdline_proc_show
[    2.170194] <redpill/cmdline_delegate.c:322> Cmdline count: 410
[    2.172284] <redpill/cmdline_delegate.c:389> Cmdline: BOOT_IMAGE=/zImage mac2=001122334455 DiskIdxMap=0C00 mac1=001122334456 netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=0 vid=0x058f syno_hdd_detect=0 pid=0x6387 console=ttyS0,115200n8 sata_pcislot=5 elevator=elevator sn=1560LWN004120 root=/dev/md0 SataPortMap=8 earlyprintk loglevel=15 log_buf_len=32M syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS3615xs vender_format_version=2
[    2.172284] 
[    2.186333] <redpill/cmdline_delegate.c:401> Param #0: |BOOT_IMAGE=/zImage|
[    2.188639] <redpill/cmdline_delegate.c:296> Option "BOOT_IMAGE=/zImage" not recognized - ignoring
[    2.191645] <redpill/cmdline_delegate.c:401> Param #1: |mac2=001122334455|
[    2.193899] <redpill/cmdline_delegate.c:284> Set MAC #1: 001122334455
[    2.195989] <redpill/cmdline_delegate.c:401> Param #2: |DiskIdxMap=0C00|
[    2.198210] <redpill/cmdline_delegate.c:296> Option "DiskIdxMap=0C00" not recognized - ignoring
[    2.201164] <redpill/cmdline_delegate.c:401> Param #3: |mac1=001122334456|
[    2.203441] <redpill/cmdline_delegate.c:284> Set MAC #2: 001122334456
[    2.205575] <redpill/cmdline_delegate.c:401> Param #4: |netif_num=1|
[    2.207673] <redpill/cmdline_delegate.c:239> Declared network ifaces # as 1
[    2.209984] <redpill/cmdline_delegate.c:401> Param #5: |earlycon=uart8250,io,0x3f8,115200n8|
[    2.212866] <redpill/cmdline_delegate.c:296> Option "earlycon=uart8250,io,0x3f8,115200n8" not recognized - ignoring
[    2.216276] <redpill/cmdline_delegate.c:401> Param #6: |syno_hdd_powerup_seq=0|
[    2.218675] <redpill/cmdlinelegate.c:296> Option "syno_hdd_powerup_seq=0" not recognized - ignoring
[    2.322084] <redpill/cmdline_delegate.c:401> Param #7: |vid=0x058f|
[    2.324158] <redpill/cmdline_delegate.c:108> VID override: 0x058f
[    2.326209] <redpill/cmdline_delegate.c:401> Param #8: |syno_hdd_detect=0|
[    2.328484] <redpill/cmdline_delegate.c:296> Option "syno_hdd_detect=0" not recognized - ignoring
[    2.331519] <redpill/cmdline_delegate.c:401> Param #9: |pid=0x6387|
[    2.333548] <redpill/cmdline_delegate.c:142> PID override: 0x6387
[    2.335521] <redpill/cmdline_delegate.c:401> Param #10: |console=ttyS0,115200n8|
[    2.337920] <redpill/cmdline_delegate.c:296> Option "console=ttyS0,115200n8" not recognized - ignoring
[    2.341013] <redpill/cmdline_delegate.c:401> Param #11: |sata_pcislot=5|
[    2.343186] <redpill/cmdline_delegate.c:296> Option "sata_pcislot=5" not recognized - ignoring
[    2.345976] <redpill/cmdline_delegate.c:401> Param #12: |elevator=elevator|
[    2.348211] <redpill/cmdline_delegate.c:296> Option "elevator=elevator" not recognized - ignoring
[    2.351154] <redpill/cmdline_delegate.c:401> Param #13: |sn=1560LWN004120|
[    2.353394] <redpill/cmdline_delegate.c:45> S/N set to: 1560LWN004120
[    2.355481] <redpill/cmdline_delegate.c:401> Param #14: |root=/dev/md0|

 

Link to comment
Share on other sites

32 minutes ago, WiteWulf said:

@scoobdriver @altas I've just had a grep through /var/log/synobootup.log on my system and can't see any reference to 'redpill/uart_swapper', which seems to be the culprit for you two.

 

Here's the code, see if you can figure out what's going on:

https://github.com/RedPill-TTG/redpill-lkm/blob/master/internal/uart/uart_swapper.c

 

It seems to be a module written to "fix" behaviour in some kernels that erroneously swaps the console output to an alternate tty by swapping it back again. For some reason this is being called unnecessarily on your systems, and swapping the console output away from your active, functioning virtual tty. FYI, I'm running a bromolow 7.0.1-RC1 42214 image.

 

I don't know why this is happening for you, or why it's not happening for me. Closer inspection of the code (or explanation from @ThorGroup) may help.

 

Wonder if it is this line which seems like it is been ignored along with other parameters 

 

[    2.335521] <redpill/cmdline_delegate.c:401> Param #10: |console=ttyS0,115200n8|

[    2.337920] <redpill/cmdline_delegate.c:296> Option "console=ttyS0,115200n8" not recognized - ignoring

Link to comment
Share on other sites

Hmmm, rather than grep'ing through /var/log/synoboot.log I looked in dmesg output instead:

 

$ dmesg | grep ttyS0
[    0.000000] Command line: BOOT_IMAGE=/zImage mac2=001B78579575 mac1=001B78579574 netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=0 vid=0x05dc syno_hdd_detect=0 pid=0xc75c console=ttyS0,115200n8 elevator=elevator sn=xxxxLWNxxxxx root=/dev/md0 earlyprintk loglevel=15 log_buf_len=32M syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS3615xs vender_format_version=2
[    0.000000] Kernel command line: BOOT_IMAGE=/zImage mac2=001B78579575 mac1=001B78579574 netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=0 vid=0x05dc syno_hdd_detect=0 pid=0xc75c console=ttyS0,115200n8 elevator=elevator sn=xxxxLWNxxxxx root=/dev/md0 earlyprintk loglevel=15 log_buf_len=32M syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS3615xs vender_format_version=2
[    0.000000] console [ttyS0] enabled, bootconsole disabled
[    0.630529] <redpill/cmdline_delegate.c:389> Cmdline: BOOT_IMAGE=/zImage mac2=001B78579575 mac1=001B78579574 netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=0 vid=0x05dc syno_hdd_detect=0 pid=0xc75c console=ttyS0,115200n8 elevator=elevator sn=xxxxLWNxxxxx root=/dev/md0 earlyprintk loglevel=15 log_buf_len=32M syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS3615xs vender_format_version=2
[    0.634385] <redpill/cmdline_delegate.c:401> Param #9: |console=ttyS0,115200n8|
[    0.634552] <redpill/cmdline_delegate.c:296> Option "console=ttyS0,115200n8" not recognized - ignoring
[    0.641367] <redpill/uart_swapper.c:410> Swapping ttyS1<=>ttyS0 started
[    0.649547] <redpill/uart_swapper.c:427> ======= OUTPUT ON THIS PORT WILL STOP AND CONTINUE ON ANOTHER ONE (swapping ttyS1 & ttyS0) =======
[    0.649844] <redpill/uart_swapper.c:429> ### LAST MESSAGE BEFORE SWAP ON "OLD" PORT ttyS1<=>ttyS0
[    0.650045] <redpill/uart_swapper.c:433> ### FIRST MESSAGE AFTER SWAP ON "NEW" PORT ttyS1<=>ttyS0
[    0.650048] <redpill/uart_swapper.c:340> Shutting down physical port iobase=0x2f8 (mapped to ttyS0)
[    0.650049] <redpill/uart_swapper.c:318> Checking if port iobase=0x2f8 irq=3 (mapped to ttyS0) active
[    0.678077] <redpill/uart_swapper.c:461> ======= OUTPUT ON THIS PORT CONTINUES FROM A DIFFERENT ONE (swapped ttyS1 & ttyS0) =======
[    0.681962] <redpill/uart_swapper.c:464> Swapping ttyS1 (curr_iob=0x2f8) <=> ttyS0 (curr_iob=0x3f8) finished successfully
[    1.942332] <redpill/sanitize_cmdline.c:102> Sanitized cmdline to: BOOT_IMAGE=/zImage mac2=001B78579575 mac1=001B78579574 netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=0 syno_hdd_detect=0 console=ttyS0,115200n8 sn=sn=xxxxLWNxxxxx root=/dev/md0 HddHotplug=0 withefi syno_hw_version=DS3615xs vender_format_version=2
[    2.984023] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

 

My system appears to be behaving the same as yours after all, and calling uart_swapper. But in my case the output continues on the iLO VSP ¯\_(ツ)_/¯ 

 

Not sure I trust the content of /var/log/synoboot.log any more. I think it may be sanitised.

Link to comment
Share on other sites

Forgive me if i'm dumb, if i would build loader for 7.01 for HP Gen8 Microserver, how should i do? 
Can i perform direct upgrade in place without lost config and data? 
Should i backup, perform new installation and restore? 
Which process should be better with balance between data integrity and less operation? 

many thanks 
 

Link to comment
Share on other sites

I have compiled the loader with 3615 Bromlow for my Gen8 with the correct vid pid MAC and  serial 

I can sucessfull install (fresh install with blank HDD)but after the reboot i have in the synology Asisstant Server recoverable and when i clickt it there is a message no connection to my server

Anyone knows what is the problem ?

thanks

 

I can remember i had the same problem with dsm 6.2 and it was nic releated but with en other Nic /  so i think in this case there is no driver for my 10GB Intel 520 Nic

this nic is working with loader 103b and DSM 6.2 without extra driver pack

 

image.png.a7a02baea794b52ee9286ee9b3affc7f.png

Edited by nemesis122
Link to comment
Share on other sites

Just now, scoobdriver said:

At this moment it is not seeing my HDD , (on a HBA card flashed IT ) 

 

Which HBA are you using ? If its MPT2SAS or MPT3SAS you have no luck at the moment. TTG said they will be the need to fake SAS to SATA.

 

If you have the smart array you can use this latest rd.gz

rd.gz.3615.microserver.7z

 

Edited by pocopico
Added latest 3615 7.0.1. rd.gz
Link to comment
Share on other sites

On 9/13/2021 at 12:02 AM, ThorGroup said:

That could be an issue with the card being seen as a proper SAS device. After quickly asking around none of have any free LSI card running in a server to test but we will look into it. Can you put a GH issue in the kernel module repo? It probably needs a small kick similar to VirtIO SCSI - currently as you see the SCSI driver attempts to add a disk with a "/dev/" name (literally empty name) which should and will fail. The problem lies somewhere in the syno modifications to the SCSI driver.

 

Hello,

I tried again to passtrough LSI SAS2 card to ESXi.

 

I edited rd.gz from loader to add a new file in /usr/lib/modules-load.d/

70-disk-0000-lsi-mpt2sas.conf

 

put in it just : mpt2sas

 

as a reminder, mpt2sas module is already part of default DS3615xs loader.

 

It works as this, mpt2sas module is loaded correctly at boot.

 

I still have the same issue, disk is not considered as SATA disk :

 

Quote

:: Loading module mpt2sas[    2.033193] mpt2sas version 20.00.00.00 loaded
[    2.033607] scsi34 : Fusion MPT SAS Host
[    2.034189] I/O scheduler elevator not found
[    2.035640] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (4022256 kB)
[    2.108088] mpt2sas0: MSI-X vectors supported: 1, no of cores: 2, max_msix_vectors: -1
[    2.109085] mpt2sas 0000:0b:00.0: irq 74 for MSI/MSI-X
[    2.110071] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 74
[    2.110091] mpt2sas0: iomem(0x00000000fd3fc000), mapped(0xffffc90000018000), size(16384)
[    2.111067] mpt2sas0: ioport(0x0000000000005000), size(256)
[    2.225979] mpt2sas0: Allocated physical memory: size(7445 kB)
[    2.226000] mpt2sas0: Current Controller Queue Depth(3305), Max Controller Queue Depth(3432)
[    2.226972] mpt2sas0: Scatter Gather Elements per IO(128)
[    2.286584] mpt2sas0: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03), BiosVersion(07.39.02.00)
[    2.286922] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
[    2.289072] mpt2sas0: sending port enable !!
[    2.293066] mpt2sas0: host_add: handle(0x0001), sas_addr(0x5003005703dbf193), phys(8)
[    2.299931] mpt2sas0: port enable: SUCCESS
[    2.300423] I/O scheduler elevator not found
[    2.301076] I/O scheduler elevator not found
[    2.302799] scsi 34:0:0:0: Direct-Access     Samsung  SSD 850 EVO 250GB        1B6Q PQ: 0 ANSI: 6
[    2.303198] scsi 34:0:0:0: SATA: handle(0x0009), sas_addr(0x4433221103000000), phy(3), device_name(0x5002538d4026c106)
[    2.303902] scsi 34:0:0:0: SATA: enclosure_logical_id(0x5003005703dbf193), slot(0)
[    2.304037] scsi 34:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    2.305024] scsi 34:0:0:0: serial_number(S21PNXBXXXXXXX     )
[    2.305910] scsi 34:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    2.307034] <redpill/scsi_notifier.c:65> Probing SCSI device using sd_probe_shim
[    2.307566] <redpill/scsi_notifier.c:77> Triggering SCSI_EVT_DEV_PROBING notifications
[    2.307970] <redpill/native_sata_boot_shim.c:153> Found new SCSI disk vendor="Samsung SSD 850         1B6QS21PNXBGXXXXXX     " model="SSD 850 EVO 250GB       ": checking boot shim viability
[    2.308909] <redpill/boot_shim_base.c:29> scsi_is_boot_dev_target: it's not a SATA disk, ignoring
[    2.309493] <redpill/scsi_notifier.c:87> Calling original sd_probe()
[    2.310003] <redpill/scsi_notifier.c:91> Triggering SCSI_EVT_DEV_PROBED notifications - sd_probe() exit=0
[    2.311104] sd 34:0:0:0: [sas0] 488397168 512-byte logical blocks: (250 GB/232 GiB)
[    2.312916] sd 34:0:0:0: [sas0] Write Protect is off
[    2.313276] sd 34:0:0:0: [sas0] Mode Sense: 7f 00 10 08
[    2.314101] sd 34:0:0:0: [sas0] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    2.316281]  sas0: p1
[    2.318016] sd 34:0:0:0: [sas0] Attached SCSI disk

 

fdisk result :

Quote

# fdisk -l
Disk /dev/synoboot: 128 MiB, 134217728 bytes, 262144 sectors
Disk model: TYPE D 3SE
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
/dev/synoboot1        2048 100351   98304  48M 83 Linux
/dev/synoboot2      100352 253951  153600  75M 83 Linux
/dev/synoboot3      253952 262143    8192   4M 83 Linux


Disk /dev/sda: 16 GiB, 17179869184 bytes, 33554432 sectors
Disk model: Virtual
SATA Hard Drive
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: 0x2d4890c5

Device     Boot   Start      End  Sectors  Size Id Type
/dev/sda1          2048  4982527  4980480  2.4G fd Linux raid autodetect
/dev/sda2       4982528  9176831  4194304    2G fd Linux raid autodetect
/dev/sda3       9437184 33349631 23912448 11.4G fd Linux raid autodetect


Disk /dev/sas0: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Disk model: SSD 850 EVO 250GB       
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: 0x49e15208

Device      Boot Start       End   Sectors   Size Id Type
/dev/sas0p1       2048 488394751 488392704 232.9G  7 HPFS/NTFS/exFAT


Disk /dev/md0: 2.4 GiB, 2549940224 bytes, 4980352 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


Disk /dev/zram0: 1.2 GiB, 1236271104 bytes, 301824 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram1: 1.2 GiB, 1236271104 bytes, 301824 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/md1: 2 GiB, 2147418112 bytes, 4194176 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


Disk /dev/md2: 11.4 GiB, 12242124800 bytes, 23910400 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


Disk /dev/mapper/vg1-syno_vg_reserved_area: 12 MiB, 12582912 bytes, 24576 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


Disk /dev/mapper/vg1-volume_1: 11 GiB, 11811160064 bytes, 23068672 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


Disk /dev/mapper/cachedev_0: 11 GiB, 11811160064 bytes, 23068672 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

 

Serial console output in attachment.

 

My disk is a SATA disk plugged on SAS controller.

It works fine on Jun's loader.

and SMART is working with passtrough LSI card on it.

 

I'll check if issue has been raised on GH.

 

 

 

7.0.1_21.log

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

3 minutes ago, pocopico said:

 

Which HBA are you using ? If its MPT2SAS or MPT3SAS you have no luck at the moment. TTG said they will be the need to fake SAS to SATA.

G8 Microserver 16GB  E3-1265L V2 

 

its a HP H220 card flashed IT mode, believe the 9207-8i with 2308 chipset . (MPT2SAS)

My 8 Disks are SATA not SAS , but on the HBA card (4xHDD, 4xSSD) 

 

I'll move a test disk on to the onboard Sata to check (in ACHI mode)

 

Good news is the rd.qz you supplied me, allow the onboard NIC to work . Thank You ! 

 

are the options in my log been ignored normal ? 

Link to comment
Share on other sites

Il y a 16 heures, plarkass a dit :

Hello,

 

I would like to know if there is a documentation about how to start with this amazing loader.

In the past, I used jun loader on my actual xpenology but I want to install a new one on dsm7.

 

If someone have a link are few explanation, I really appreciate.

 

 

 

Just to reply for other, i get it using 


download the zip file redpill-tool-chain_x86_64_v0.8.zip


unzip redpill*.zip
vi user_config.json
    - update vid/pid  in format (0x0000)
    - update mac address in format 001122334455
run
usermod -aG docker $USER
chmod +x docker/entrypoint.sh
chmod +x redpill_tool_chain.sh

redpill_tool_chain.sh build bromolow-7.0-41222
or replace bromolow-7.0-41222 with other version you desired
redpill_tool_chain.sh auto bromolow-7.0-41222

exit
cd images
the img file is here"

Link to comment
Share on other sites

3 hours ago, dodo-dk said:

 

Hi, i found the problem. You need to change the CPU Settings from kvm64 to host or haswell.

So it works with my E3-1241 V3 CPU - Bromolow - 7.0.1-42214 setup.

 

Wow! You saved my day. I changed it to Ivy Bridge and now it works! Thanks for your input.

Link to comment
Share on other sites

1 hour ago, Aigor said:

Forgive me if i'm dumb, if i would build loader for 7.01 for HP Gen8 Microserver, how should i do? 
Can i perform direct upgrade in place without lost config and data? 
Should i backup, perform new installation and restore? 
Which process should be better with balance between data integrity and less operation? 

 

Regardless of what upgrade/migration/fresh build approach you take, you should always take a backup of your data first. The developers do not recommend this release for production use in it's current state and you should not risk your data with it.

 

With that in mind...

 

It's not possible to do an "upgrade" from 6.2.3/Jun's loader (which I assume you're on at present) in the sense of invoking an upgrade in the DSM Control Panel. However, most people on here refer to the following procedure as "upgrade", although it's really a migration:   

- take a backup

- shutdown your server

- remove the Jun's bootloader USB stick

- replace with a new USB stick with the redpill loader on it, built with your SN, MAC address(es) and VID/PID in the grub.cfg

- boot the server on the redpill stick

- the server should dchp and you can either use the Syno tool to find it, or look at the DHCP logs on your router and see what IP address it gets

- browse to http://<your_server_ip>:5001, if it's gone well you should see the Syno web page telling you that it's found disks from another Synology server and offering to migrate them for you. Run through the migration process and you should have 7.x server with all your existing data, settings and packages preserved

 

Did I mention to TAKE A BACKUP first? :D

  • Like 2
Link to comment
Share on other sites

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