RedPill - the new loader for 6.2.4 - Discussion


Recommended Posts

Il y a 7 heures, pocopico a dit :

 

 

You can ignore the message about zImage. Redpill just mentions that it doesn't know how to handle that and actually shouldn't care about that.

 

Check messages on ttyS0 as well.

 

Ok thanks,

 

There is no ttys0 interface (only vsp on ILO) to get the next logs

Link to post
Share on other sites
13 hours ago, Buny74 said:

 

Ok thanks,

 

There is no ttys0 interface (only vsp on ILO) to get the next logs


 

Quote

 

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

 

 

 

Since redpill says all messages will be redirected you will not see any more messages on ttyS1 (COM2)

 

From the bios you can set your vsp to either com1 or com2 you are wathching com2  (?) switch to com1 or the other way around. the message is not clear to me 

  • Like 1
Link to post
Share on other sites

Successful installation Bare metal DS918+ 7.0.1-42218

 

Hotswap enabled on motherboard allowed for 2 drives to be connected with success without the failed 3,4,5,6 drive error.

 

Also have everything working QC & DDNS but do have a genuine serial & mac.

 

Thank you for the project.

DSM 7.jpg

  • Like 1
Link to post
Share on other sites

 

Hello everyone,

Following the recommendation of @haydibe  @WiteWulf (thanks to them) Can I help me and I think others for building my own configuration file version 7.0.1 global_config.json ? 

I have a problem for build IMG with redpill-tool-chain_x86_64_v0.11

[!] There doesn't seem to be a config for DS3615xs platform running 7.0.1-42214 (checked /opt/redpill-load/config/DS3615xs/7.0.1-42214/config.json)

*** Process will exit ***

IMG build is ok with "bromolow-6.2.4-25556" and "bromolow-7.0-41222" not with "7.0.1-42214"

Thank you very much.

Link to post
Share on other sites
9 hours ago, pocopico said:

 

I think that for SATA shim, Redpill looks for disks that are less or equal to 1GB size 

 

I don't get what you mean, my question was:

I heard Redpill support SATA DOM for VM configuration such as ESXi, but does it also support SATA DOM for Bare metal? 

  • Confused 1
Link to post
Share on other sites
12 hours ago, forests_gump said:

I don't get what you mean, my question was:

I heard Redpill support SATA DOM for VM configuration such as ESXi, but does it also support SATA DOM for Bare metal? 


You have asked the same question already on this thread and Thorgroup already answered that question on this thread in the past. I gave you an answer that I thought since you are on a developer thread you would understand. 

 

My answer was simple and clear  enough. I will try once more. 

SATA Is possible if you use a disk that is 1GB or smaller size. It doesn’t make sense to use SATA DOM for bare metal installations cause you can use usb. SATA Dom boot was created by TTG,  since it’s not possible to use USB to boot on VMware
 

 

 

Edited by pocopico
  • Like 3
Link to post
Share on other sites
On 12/3/2021 at 11:03 PM, s2k7 said:

9p worked well.
Please check my post in another thread.

Tapatalk を使用して私の ELS-NX9 から送信
 

Thanks, Does DSM moment work with 9pfs? I have tested same app(for example moment/backup..) didn't work with NFS in DSM6.

Can you share your vm config? Looks like you use the docker DSM?

Link to post
Share on other sites
7 minutes ago, KoenigLudwig said:

Quick question, is there a summary aynwhere, whats they status (apparently no one know since the last post?) respectively a tutorial / something alike? Can it be used semi productively (always having a a few backups of course, but sort of stable?) If redundant please delete.

 

I would not recommend anyone to use an in development proof of concept release like this in any way other than for the pure fun of testing it. I know some are actually storing they´re personal data at their own risk. Also, as we are standing right now we don't even know if the project is still alive, it's all just speculations bitcoin-style.

Edited by Piteball
  • Like 2
Link to post
Share on other sites
Thanks, Does DSM moment work with 9pfs? I have tested same app(for example moment/backup..) didn't work with NFS in DSM6.
Can you share your vm config? Looks like you use the docker DSM?
The photo app did work with 9pfs. That was my target. I don't know other way to use 9pfs other than a docker.
I used old way, just to put 9p modules directly. You can use any config in this post to include virtio default.

Tapatalk を使用して私の ELS-NX9 から送信

Link to post
Share on other sites
9 hours ago, s2k7 said:

The photo app did work with 9pfs. That was my target. I don't know other way to use 9pfs other than a docker.
I used old way, just to put 9p modules directly. You can use any config in this post to include virtio default.

Tapatalk を使用して私の ELS-NX9 から送信
 

 

Thank you! It's my target too.

The host directly manages the disks, and photo app in DSM.

Restore or backup data will be easy without virtual disk.

Link to post
Share on other sites

Hello everyone. I succesfully installed DS918+ with DSM 7.0.1 (42218) on vmware and it was working flawlessly but when i try the same image on a usb stick on a PC, I get all the time the error "We've detected errors on the hard drives (2, 3, 4, 5, 6), and the SATA ports have also been disabled. Please shut down your DS918+ to replace or remove the hard drives and try again."

I turned on hot plug on my motherboard in each of sata controllers (mobo has 4) with no luck.

The error is the same but it says that there is an error only on drives 5,6 and not 2, 3, 4, 5, 6.

Does anybody knows any solution?

 

Link to post
Share on other sites
1 hour ago, moustos said:

Hello everyone. I succesfully installed DS918+ with DSM 7.0.1 (42218) on vmware and it was working flawlessly but when i try the same image on a usb stick on a PC, I get all the time the error "We've detected errors on the hard drives (2, 3, 4, 5, 6), and the SATA ports have also been disabled. Please shut down your DS918+ to replace or remove the hard drives and try again."

I turned on hot plug on my motherboard in each of sata controllers (mobo has 4) with no luck.

The error is the same but it says that there is an error only on drives 5,6 and not 2, 3, 4, 5, 6.

Does anybody knows any solution?

 

Can you share lspci -nn please ?

Link to post
Share on other sites
17 minutes ago, moustos said:

 

Is this on the photo what you need?

I wrote just the command lspci because with lspci -nn i get an error "can't find command"

20211207_123138.jpg

 

can you try appending , DiskIdxMap=0004 SataPortMap=44 on the GRUB linux line 

Edited by pocopico
Link to post
Share on other sites
32 minutes ago, pocopico said:

 

can you try appending , DiskIdxMap=0004 SataPortMap=44 on the GRUB linux line 

 

Now it says "We've detected errors on the hard drives (2, 3, 4)"

But you helped me to understand what's going on. Maybe if i append DiskIdxMap=0 and SataPortMap=4 it goes well.

I'll give it a shot but any suggestions are welcome.

Link to post
Share on other sites

I figured it out. I set DiskIdxMap=0 (0 is the first port of sata controller)and SataPortMap=4 (controller has 4 ports) and everything works fine now.

Thanks pocopico for your help. Thanks to you I understood how it works.

Edited by moustos
  • Like 1
Link to post
Share on other sites

Hello everyone. Please help me. I migrated to apolokake 918. At first, like many people, I had an error that the disks would be disconnected. As a result, I connected only 4 disks and prescribed DiskIdxMap=0 SataPortMap=4 SasIdxMap=0 after that, the migration took place, but I did not see the rest of the disks when I connected them to the same controller. As a result, I mounted the flash drive and removed the lines that I added to grub. After that, I saw 2 more disks, but that's not all. As a result, I connected the remaining disks to the motherboard and they are all visible now, but I want to use all the ports. What should I register in grub so that all disks are visible ? I also tried to change the values of internalportcfg max disk in synoinfo.conf, but after rebooting, the native values are there again.

admin@Synology:/usr/lib/modules$ lspci -k | grep -EiA2 'SATA|SCSI'
admin@Synology:/usr/lib/modules$ ls /dev/sd?
/dev/sda /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf /dev/sdg /dev/sdh
admin@Synology:/usr/lib/modules$ cat /proc/scsi/sg/devices
0 0 0 0 0 1 31 0 1
1 0 0 0 0 1 31 0 1
2 0 0 0 0 1 31 0 1
3 0 0 0 0 1 31 0 1
4 0 0 0 0 1 31 1 1
5 0 0 0 0 1 31 1 1
6 0 0 0 0 1 31 1 1
7 0 0 0 0 1 31 1 1
32 0 0 0 0 1 31 0 1
36 0 0 0 0 1 1 0 1
admin@Synology:/usr/lib/modules$

Link to post
Share on other sites
2 hours ago, aportnov said:

Hello everyone. Please help me. I migrated to apolokake 918. At first, like many people, I had an error that the disks would be disconnected. As a result, I connected only 4 disks and prescribed DiskIdxMap=0 SataPortMap=4 SasIdxMap=0 after that, the migration took place, but I did not see the rest of the disks when I connected them to the same controller. As a result, I mounted the flash drive and removed the lines that I added to grub. After that, I saw 2 more disks, but that's not all. As a result, I connected the remaining disks to the motherboard and they are all visible now, but I want to use all the ports. What should I register in grub so that all disks are visible ? I also tried to change the values of internalportcfg max disk in synoinfo.conf, but after rebooting, the native values are there again.

admin@Synology:/usr/lib/modules$ lspci -k | grep -EiA2 'SATA|SCSI'
admin@Synology:/usr/lib/modules$ ls /dev/sd?
/dev/sda /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf /dev/sdg /dev/sdh
admin@Synology:/usr/lib/modules$ cat /proc/scsi/sg/devices
0 0 0 0 0 1 31 0 1
1 0 0 0 0 1 31 0 1
2 0 0 0 0 1 31 0 1
3 0 0 0 0 1 31 0 1
4 0 0 0 0 1 31 1 1
5 0 0 0 0 1 31 1 1
6 0 0 0 0 1 31 1 1
7 0 0 0 0 1 31 1 1
32 0 0 0 0 1 31 0 1
36 0 0 0 0 1 1 0 1
admin@Synology:/usr/lib/modules$

How many disks are in total ? Can you pass an lspci -n ? 
 

as for the synoinfo file, as per 

 

https://raw.githubusercontent.com/RedPill-TTG/redpill-load/master/FOR_DEVS.md

 

you should modify the synoinfo at the time of the loader creation as this file is on the ram disk and if it’s not modified it will be overwritten every time from the file that exists on the loaders ram disk (rd.gz) 

 

 

Edited by pocopico
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.