Jump to content
XPEnology Community

TinyCore RedPill Loader (TCRP)


pocopico

Recommended Posts

14 minutes ago, Badger said:

Ok so you're saying <yourplatform> refers to the current DSM "version" I'm running?  I just want to make sure.  Maybe it'll just error out, but I fear worse if I don't type the correct value here.  Maybe it's just semantic differences, but in other posts "platform" refers to the hardware (e.g. DS3622xs+.).  Then in a previous post on this page Loveburn (member) described a successfull manual update to 7.1 U2... with a postupdate command that specifies 7.0.1 42218.  Can you really make that jump?

 

Review both links carefully, you should find the answers to your questions.

 

https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/

https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/

 

  • Like 1
Link to comment
Share on other sites

32 minutes ago, alex.god007 said:

Thanks for info. I was trying to create a new USB drive with 918+ loader with the same settings (except USB PID/VID + new generated S/N with MAC) but I'm getting only message that there are no disks in system.

image.thumb.png.5caea992ca8546caf064d43845ec1543.png

Using sataportmap in installation giving me an error that there is an error with disks 1 and 2.

 

Really don't want to lose data that was created during DS3615xs installation and don't know what next steps I should do further with detecting disks on new platform 😃

 

In fresh env of tinycore here is output of devices. Currently there is no ata1 and ata2 (only 4 SATA ports on this motherboard):

 

lrwxrwxrwx  1 root root 0 Jun  5 16:40 sda -> ../devices/pci0000:00/0000:00:17.0/ata3/host2/target2:0:0/2:0:0:0/block/sda
lrwxrwxrwx  1 root root 0 Jun  5 16:40 sdb -> ../devices/pci0000:00/0000:00:17.0/ata4/host3/target3:0:0/3:0:0:0/block/sdb
lrwxrwxrwx  1 root root 0 Jun  5 16:40 sdc -> ../devices/pci0000:00/0000:00:17.0/ata5/host4/target4:0:0/4:0:0:0/block/sdc
lrwxrwxrwx  1 root root 0 Jun  5 16:40 sdd -> ../devices/pci0000:00/0000:00:17.0/ata6/host5/target5:0:0/5:0:0:0/block/sdd

lrwxrwxrwx  1 root root 0 Jun  5 16:40 nvme0n1 -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/nvme/nvme0/nvme0n1
lrwxrwxrwx  1 root root 0 Jun  5 16:40 nvme1n1 -> ../devices/pci0000:00/0000:00:1d.0/0000:07:00.0/nvme/nvme1/nvme1n1
 

 

I cannot read the Russian image, but I suspect you have a motherboard that is exhibiting a problem we don't fully have a solution for.

 

From TinyCore, please post the result of

dmesg | grep "DUMMY"

 

And we can advise further.

Link to comment
Share on other sites

5 minutes ago, flyride said:

 

I cannot read the Russian image, but I suspect you have a motherboard that is exhibiting a problem we don't fully have a solution for.

 

From TinyCore, please post the result of

dmesg | grep "DUMMY"

 

And we can advise further.

Yeah, I think so. 

 

tc@box:~$ dmesg | grep "DUMMY"
[    0.270826] ata1: DUMMY
[    0.270827] ata2: DUMMY
tc@box:~$


I think that is the problem that using M.2 PCI-E SSDs are using ATA1/2 ports and installation cannot be proceeded. I cannot disable SATA on M.2 - there is no option in BIOS.

I have a really weird plan - maybe it will work? I can rebuild back NAS with old motherboard on Z270 chipset via ASRock mini itx z270 with 6 SATA ports in it and connect to them 4 disks + 2 SATA SSDs (that was used as SSD Cache). Then I'll create a new installation and try to migrate data. If it will be OK - I'll switch back to new motherboard with connected M.2 SSDs in it and loaded to needed platform with m.2 modules in it. Should it work?

Edited by alex.god007
Link to comment
Share on other sites

2 minutes ago, alex.god007 said:

Yeah, I think so. 

 

tc@box:~$ dmesg | grep "DUMMY"
[    0.270826] ata1: DUMMY
[    0.270827] ata2: DUMMY
tc@box:~$


I think that is the problem that using M.2 PCI-E SSDs are using ATA1/2 ports and installation cannot be proceeded. I cannot disable SATA on M.2 - there is no option in BIOS.

I have a really weird plan - maybe it will work? I can rebuild back NAS with old motherboard on Z270 chipset via ASRock mini itx z270 with 6 SATA ports in it and connect to them 4 disks + 2 SATA SSDs (that was used as SSD Cache). Then I'll create a new installation and try to migrate data. If it will be OK - I'll switch back to new motherboard with connected M.2 SSDs in it and loaded to needed platform with m.2 modules in it. Should it work?

 

The DUMMY responses indicate that the motherboard has dual-use M.2 ports.  They can support SATA SSD's or NVMe.

Any SATA port that is not configured for "hotplug" is disabled by the kernel. Any disabled port results in a DSM installation failure.

The dual use ports have no BIOS provision for hotplug.  Thus there is no easy fix.

 

Your idea of upgrade on another platform will probably work. There are a few other options you might consider that are outlined in the tutorial.

https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/

 

However, I strongly suggest you remove the SSD cache prior to ANY upgrade or migration, and then add it back in afterward.

Link to comment
Share on other sites

2 minutes ago, flyride said:

 

The DUMMY responses indicate that the motherboard has dual-use M.2 ports.  They can support SATA SSD's or NVMe.

Any SATA port that is not configured for "hotplug" is disabled by the kernel. Any disabled port results in a DSM installation failure.

The dual use ports have no BIOS provision for hotplug.  Thus there is no easy fix.

 

Your idea of upgrade on another platform will probably work. There are a few other options you might consider that are outlined in the tutorial.

https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/

 

However, I strongly suggest you remove the SSD cache prior to ANY upgrade or migration, and then add it back in afterward.

Thanks mate! Going to rebuild it, migrate current platform from DS3615xs to 920+ and then rebuild it with new motherboard. Will write down after I'll finish those operations.

Link to comment
Share on other sites

29 minutes ago, loveburn said:

sorry , but I made a typo.... i mean postupdate with 7.1....

Thanks.  Glad you had success.  So it looks like <yourplatform> in the postupdate command really refers to the build/version.  I will try that

Link to comment
Share on other sites

2 hours ago, flyride said:

Your idea of upgrade on another platform will probably work.

I've made all the things and loaded up with platform 918+. SATA disks are visible and array is in normal state. But there is no cache devices in Disk manager.

I've checked system output and there are an NVMe devices :

akoznov@NAS:~$ udevadm info /dev/nvme0n1
P: /devices/pci0000:00/0000:00:1b.4/0000:04:00.0/nvme/nvme0/nvme0n1
N: nvme0n1
E: DEVNAME=/dev/nvme0n1
E: DEVPATH=/devices/pci0000:00/0000:00:1b.4/0000:04:00.0/nvme/nvme0/nvme0n1
E: DEVTYPE=disk
E: MAJOR=259
E: MINOR=0
E: PHYSDEVBUS=pci
E: PHYSDEVDRIVER=nvme
E: PHYSDEVPATH=/devices/pci0000:00/0000:00:1b.4/0000:04:00.0
E: SUBSYSTEM=block
E: SYNO_ATTR_SERIAL=S64PNF0R705302
E: SYNO_DEV_DISKPORTTYPE=UNKNOWN
E: SYNO_INFO_PLATFORM_NAME=apollolake
E: SYNO_KERNEL_VERSION=4.4
E: SYNO_SUPPORT_XA=no
E: TAGS=:systemd:
E: USEC_INITIALIZED=986445

akoznov@NAS:~$
akoznov@NAS:~$ udevadm info /dev/nvme1n1
P: /devices/pci0000:00/0000:00:1d.0/0000:07:00.0/nvme/nvme1/nvme1n1
N: nvme1n1
E: DEVNAME=/dev/nvme1n1
E: DEVPATH=/devices/pci0000:00/0000:00:1d.0/0000:07:00.0/nvme/nvme1/nvme1n1
E: DEVTYPE=disk
E: MAJOR=259
E: MINOR=1
E: PHYSDEVBUS=pci
E: PHYSDEVDRIVER=nvme
E: PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.0/0000:07:00.0
E: SUBSYSTEM=block
E: SYNO_ATTR_SERIAL=S64PNF0R705285
E: SYNO_DEV_DISKPORTTYPE=UNKNOWN
E: SYNO_INFO_PLATFORM_NAME=apollolake
E: SYNO_KERNEL_VERSION=4.4
E: SYNO_SUPPORT_XA=no
E: TAGS=:systemd:
E: USEC_INITIALIZED=986883

Also I've created /etc.defaults/extensionPorts file and there is no luck after reboot:

 

cat /etc.defaults/extensionPorts
[pci]
pci1="0000:00:1b.4"
pci2="0000:00:1d.0"

Any ideas?

  • Like 1
Link to comment
Share on other sites

5 hours ago, Badger said:

Ok so you're saying <yourplatform> refers to the current DSM "version" I'm running?  I just want to make sure.  Maybe it'll just error out, but I fear worse if I don't type the correct value here.  Maybe it's just semantic differences, but in other posts "platform" refers to the hardware (e.g. DS3622xs+.).  Then in a previous post on this page Loveburn (member) described a successfull manual update to 7.1 U2... with a postupdate command that specifies 7.0.1 42218.  Can you really make that jump?


it’s actually the Platform ID as is set in custom_config.json. For post update it’s not critical. It will just process the rd.gz it finds on your loader disk. 

Link to comment
Share on other sites

7 hours ago, Badger said:

Thanks.  Glad you had success.  So it looks like <yourplatform> in the postupdate command really refers to the build/version.  I will try that

 

As for my personal opinion regarding this update 2,
I think the last update 1 is an important update because it patched security vulnerabilities.

However, as in the release notes of this update 2, it has nothing to do with the security vulnerability patch and only issues of SSD, S.M.A.R.T , and Link Aggregation.
So, in my case update 2 patch is pending.

Of course, we cannot rule out the possibility that Synology has internally patched security without announcing it in update 2.

Isn't it a matter to think about whether to forcefully upgrade to update 2 while taking such a large burden into consideration?

 

Version: 7.1-42661 Update 2

[Compatibility & Installation]
When an SSD's firmware version doesn't support the S.M.A.R.T test, the system will disable related functions.
[Fixed Issues]
Fixed an issue where the out-of-band port couldn't function properly when users configured Link Aggregation with only the ports on the external network card.

 

Link to comment
Share on other sites

10 hours ago, Badger said:

Ok so you're saying <yourplatform> refers to the current DSM "version" I'm running?  I just want to make sure.  Maybe it'll just error out, but I fear worse if I don't type the correct value here.  Maybe it's just semantic differences, but in other posts "platform" refers to the hardware (e.g. DS3622xs+.).  Then in a previous post on this page Loveburn (member) described a successfull manual update to 7.1 U2... with a postupdate command that specifies 7.0.1 42218.  Can you really make that jump?

Hello, I am certainly not an expert but if you run the ./rploader.sh postupdate command it will spit out usage and there you can see examples of what you can specify as arguments. I believe that the postudate command would be useful only in minor updates like Update1 or Update2 where the main version number will remain the same for example 7.1.0-42661. If it was a major version number change I think a loader rebuild would be necessary.

In you case the broadwellnk-7.1.0-42661 the broadwellnk defines the platform and the 7.1.0-42661 the DSM version.

When I did the postupdate for DS918+ I had to use ./rploader.sh postupdate apollolake-7.1.0-42661. On the DS3615xs+ I used  ./rploader.sh postupdate bromolow-7.1.0-42661

 

The codenames apollolake, bromolow etc are the Intel platform.

Try run the command ./rploader.sh postupdate only and you will see the output.

I hope I am not making any mistakes and hopefully someone with more knowledge can chime in. I did two successful postupdates with DS3615xs and DS918+ and in both cases it was intel platform-dsmversion (bromolow-7.1.0-42661, apollolake-7.1.0-42661)

Link to comment
Share on other sites

By the way: it is possible to add one more MAC address to user_config.json file to enable one more port on 10 gigabit NIC? my.sh finds that there are more than one NIC in system and generates mac for second port, but script doesn't get info that there are 2 ports in that second NIC  

What are the proper steps to update settings and apply them to the current installation? 

Should I boot up to Linux and use postupdate option after making changes in user_config.json ?

 

Link to comment
Share on other sites

2 minutes ago, alex.god007 said:

By the way: it is possible to add one more MAC address to user_config.json file to enable one more port on 10 gigabit NIC? my.sh finds that there are more than one NIC in system and generates mac for second port, but script doesn't get info that there are 2 ports in that second NIC  

What are the proper steps to update settings and apply them to the current installation? 

Should I boot up to Linux and use postupdate option after making changes in user_config.json ?

 

The issue is that DS918+ has limit of two lan ports from Synology.

Add maxlanport=4 or whatever you need in user_config.json and TCRP will patch it on bootup.

 

MAC address configuration is optional, it uses the hardware addresses by default.  I don't really know what my.sh does with it.

 

Link to comment
Share on other sites

1 hour ago, flyride said:

Add maxlanport=4 or whatever you need in user_config.json and TCRP will patch it on bootup.

 

Still no luck. I've seen that only 2 interfaces are up and running. 

image.png.80e78162b7e19a212e82efa91d9bdd29.png

At synoinfo.conf I've updated option to 4:

maxlanport="4" 

 

In grub.conf I see netif_num option and needed MAC addresses:

 

image.thumb.png.1c7e085cc1c81a0db0a6f351a28f3398.png

Maybe I'm missing something? Or should I move to another platform one more time ? :D

Link to comment
Share on other sites

I would like to share again some of the misconceptions about the jun mode build of TCRP.
Although the jun mode test has not yet been completed for all seven models in TCRP,
Currently, ds918+ has been successfully updated from 7.0.1-42218 u4 to 7.1.0-42661 u2.

 

Last month, @pocopico released version 0.7.1.4 of TCRP on 5/17.
He mentioned just one line, but I don't know if I didn't pay attention.

 

 

 

Since then, the use of jun mode in TCRP has not been promoted and there is no guide, so it seems that some users misunderstand that jun mode is not available in TCRP.

 

As in the text of the link above, you need to add one more jun option at the end.

./rploader.sh build broadwellnk-7.0.1-42218-JUN jun

 

However, if you build like this without this jun option as shown below, there is no error.

./rploader.sh build broadwellnk-7.0.1-42218-JUN

 

However, if you build like this, it will be built in abnormal mode, not in Jot mode or Jun mode.

As if it was built in Jun mode, the grub boot menu called Yet Another Jun's Mode also looks changed, so it is easy to be mistaken.
I also made a mistake on this part.

 

It has been modified to enable normal build by adding the missing jun option to the m shell.

When it is built in jun mode, the log that you normally can't see rises considerably.
Finally, it seems that the process of making a new custum.gz file and patching it goes into it.

 

It has been confirmed that it is currently working well on DS918+ baremetal.

As shared by @dolbycat, it takes a while for all of JUN to recognize the LAN. Please take that into consideration and use it.

 

528365879_2022-06-064_05_49.thumb.png.916b8f0cb1179658ca7efc80ce7d64c0.png518687459_2022-06-064_18_27.thumb.png.f6bfc3b92f2d9b143e807967b244115b.png

  • Like 2
Link to comment
Share on other sites

In folder 

/etc/sysconfig/network-scripts

i've created ifcfg-eth2 config that is the same for ifcfg-eth1 except device and brigde name:

ash-4.4# cat ifcfg-eth2
DEVICE=eth2
BOOTPROTO=dhcp
ONBOOT=yes
BRIDGE=ovs_eth2


then restarted network services with

/etc/rc.network restart

and both 10 gigabit interfaces are up and running:

image.thumb.png.f552a89106a6cb6591a6fb4330c75f16.png

I hope that these setting wouldn't reset after reboot 😃

Link to comment
Share on other sites

Hi,

Apologies if this has already been answered. I did a search of this topic and couldn't find anything regarding errors for QuickConnect not registering. My real DS3615xs died a while back and I have been using the serial and mac from it on Jun's loader 1.03B. I upgraded to redpill TC loader yesterday using latest script and am running 7.1 build 42661-U1. 

 

Everything else works except the above. I have confirmed the serial, mac1 and mac2 are both set correctly but keep getting prompted to sign in to synology account. Once I sign in and hit appy I get an error "ynology account was signed out.  Please sign in and register the service again". Is this a known issue/fix for this?

 

Thanks

Edited by j911
Link to comment
Share on other sites

Hi, I upgraded one of my boxes fine earlier tonight running a Asrock Q1900-ITX.

 

However, I'm getting a warning when trying to upgrade my Asrock Q2900-ITX (which has four SATA ports) on the motherboard.  My SATA controller card isn't detected

RAID bus controller: Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller (rev 01)

 

tc@box:~$ ./rploader.sh satamap

Found "00:13.0 Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e)"
Detected 2 ports/1 drives. Override # of ports or ENTER to accept <2>

Found "04:00.0 ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)"
Detected 2 ports/2 drives. Override # of ports or ENTER to accept <2>

Recommended settings:
SataPortMap=22
DiskIdxMap=0002

 

tc@box:~$ lspci
00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e)
00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e)
00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e)
00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e)
00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e)
00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e)
00:1c.1 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 2 (rev 0e)
00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e)
00:1c.3 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 4 (rev 0e)
00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e)
00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e)
01:00.0 RAID bus controller: Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller (rev 01)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 11)
04:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)

 

tc@box:~$ ./rploader.sh listmods bromolow-7.1.0-42661
Rploader Version : 0.8.0.1
Loader source : https://github.com/pocopico/redpill-load.git Loader Branch : develop
Redpill module source : https://github.com/pocopico/redpill-lkm.git : Redpill module branch : master
Extensions :   redpill-misc
Extensions URL : "https://github.com/pocopico/redpill-load/raw/master/redpill-misc/rpext-index.json"
TOOLKIT_URL : https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.bromolow-7.0.dev.txz/download
TOOLKIT_SHA : a5fbc3019ae8787988c2e64191549bfc665a5a9a4cdddb5ee44c10a48ff96cdd
SYNOKERNEL_URL : https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/25426branch/bromolow-source/linux-3.10.x.txz/download
SYNOKERNEL_SHA : 18aecead760526d652a731121d5b8eae5d6e45087efede0da057413af0b489ed
COMPILE_METHOD : toolkit_dev
TARGET_PLATFORM       : bromolow
TARGET_VERSION    : 7.1.0
TARGET_REVISION : 42661
REDPILL_LKM_MAKE_TARGET : dev-v7
KERNEL_MAJOR : 3
MODULE_ALIAS_FILE :  modules.alias.3.json
SYNOMODEL : ds3615xs_42661
MODEL : DS3615xs
Local Cache Folder : /mnt/sdf3/auxfiles
DATE Internet : 06062022 Local : 06062022
Checking Internet Access -> OK
Redpill sources already downloaded, pulling latest
Already up to date.
Loader sources already downloaded, pulling latest
Already up to date.
Testing modules.alias.3.json -> File OK
------------------------------------------------------------------------------------------------
It looks that you will need the following modules :


Found VGA Controller : pciid 8086d00000f31  Required Extension :
No matching extension
Found SATA Controller : pciid 8086d00000f23  Required Extension :
No matching extension
[#] Checking runtime for required tools... [OK]
[#] Adding new extension from https://raw.githubusercontent.com/pocopico/rp-ext/master/r8168/rpext-index.json...
[#] Downloading remote file https://raw.githubusercontent.com/pocopico/rp-ext/master/r8168/rpext-index.json to /home/tc/redpill-load/custom/extensions/_new_ext_index.tmp_json
######################################################################## 100.0%

[!] Extension is already added (index exists at /home/tc/redpill-load/custom/extensions/pocopico.r8168/pocopico.r8168.json). For more info use "ext-manager.sh info pocopico.r8168"

*** Process will exit ***
Found Ethernet Interface : pciid 10ecd00008168 Required Extension : r8168
r8169
Searching for matching extension for r8168
Found matching extension :
"https://raw.githubusercontent.com/pocopico/rp-ext/master/r8168/rpext-index.json"
Found SATA Controller : pciid 1b21d00000612  Required Extension :
No matching extension

 

 

 

I haven't proceeded with the upgrade.  Any advice on what to do from here?

Edited by techhit
lspci info
Link to comment
Share on other sites

6 hours ago, alex.god007 said:

Still no luck. I've seen that only 2 interfaces are up and running. 

image.png.80e78162b7e19a212e82efa91d9bdd29.png

At synoinfo.conf I've updated option to 4:

maxlanport="4" 

 

In grub.conf I see netif_num option and needed MAC addresses:

 

image.thumb.png.1c7e085cc1c81a0db0a6f351a28f3398.png

Maybe I'm missing something? Or should I move to another platform one more time ? :D

 

Did you build the loader again after making the user_config.json change?  Anything in user_config.json will override what is in synoinfo.conf

Link to comment
Share on other sites

2 hours ago, techhit said:

Hi, I upgraded one of my boxes fine earlier tonight running a Asrock Q1900-ITX.

 

However, I'm getting a warning when trying to upgrade my Asrock Q2900-ITX (which has four SATA ports) on the motherboard.  My SATA controller card isn't detected

RAID bus controller: Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller (rev 01)

 

tc@box:~$ ./rploader.sh satamap

Found "00:13.0 Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e)"
Detected 2 ports/1 drives. Override # of ports or ENTER to accept <2>

Found "04:00.0 ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)"
Detected 2 ports/2 drives. Override # of ports or ENTER to accept <2>

Recommended settings:
SataPortMap=22
DiskIdxMap=0002

<snip>

Found SATA Controller : pciid 1b21d00000612  Required Extension :
No matching extension

 

I haven't proceeded with the upgrade.  Any advice on what to do from here?

 

As you can see the PCI ids of the controllers that are reported by satamap are different than the error.  The red highlighting is yours.

My understanding is that this particular controller is part of the RedPill model and no extension is required. You might have missed that notice on your previous build.

 

I think you are okay to proceed.  However, if you use the full test procedure as outlined in the tutorial, however, your risk would be minimal.

 

EDIT: Are you saying you have a third controller?  The 1b21.0612 is the second on-board controller, which has TCRP support.  Did you build with the manual argument?  If so, omit "manual" and see if you get a different result.

 

If you really have a third controller and it is an HBA, it may not behave as an AHCI SATA controller.  If that is the case, it is treated as a SCSI controller which is unaffected by sataportmap/diskidxmap.  There is a pending update for rploader.sh which will confirm the status of HBAs in satamap because that question is a common one.

 

On 5/22/2022 at 11:47 PM, flyride said:

Migration

 

DSM 6.x (with Jun’s loader) can be migrated to DSM 7.x using TCRP. Do not attempt to upgrade from 6.x to 7.x using the Control Panel.

 

Complete the following tasks prior to migration:

  1. Read through this reference thoroughly
  2. Remove the 6.x loader USB and array disks (making sure to mark their order)
  3. Build a TCRP loader on a new USB to practice and confirm the build process
    (with all the same NAS hardware that will be used for the upgrade)
  4. Trial install DSM 7.x to a test HDD/SDD
  5. Verify DSM is working perfectly with all the NAS hardware
  6. Remove the test USB and HDD/SDD, and restore the 6.x loader USB and array disks
  7. VERIFY BACKUP of all data saved elsewhere before attempting an in-place upgrade

The actual migration process is simple:

  1. Remove any existing SSD cache configuration (strongly recommended)
  2. Shut down the NAS
  3. Replace the existing 6.x USB loader with the TCRP 7.x USB loader from the process above
  4. Boot the NAS and complete the DSM Migration when prompted
  5. Restore SSD cache configuration as desired
Edited by flyride
may have misunderstood OP's configuration
  • Like 1
Link to comment
Share on other sites

On 25/2/2022 at 14:55, Orphée said:

È già stato spiegato più volte.

 

SataPortMap definisce il numero di porte contenute in ciascun controller SATA. impostato su 1 cifra.

58 significa: il primo controller SATA ha 5 porte (5 dischi SATA collegabili), il secondo controller SATA ha 8 porte (8 dischi SATA collegabili)

 

DiskIdxMap definisce la posizione iniziale della mappatura del disco per ogni controller, impostata su 2 cifre.

00 = / sviluppo / sda

01 = /dev/sdb

eccetera...

 

quindi 0A00 significa :

- Le prime 2 cifre sono 0A: è l'undicesima posizione: /dev/sdk

- La seconda cifra è 00: è la prima pozione: /dev/sda

 

Quindi i primi dischi del controller inizieranno da sdk a sdo

e il secondo disco del controller partirà da sda a sdh

 

A seconda di quanti controller SATA hai sulla tua scheda madre (sono tutti sulla scheda madre, o hai una scheda PCI, o nmve... ecc...) il numero può essere diverso da una configurazione all'altra.

 

Considerando che su ESXi si definiscono i numeri del controller SATA (come SATA0:0 per il caricatore e SATA1:x per i dischi DATA)

di solito usando le impostazioni di cui sopra, puoi impostare SataPortMap = 18 e DiskIdxMap su qualcosa come 1000

Poiché hai solo il caricatore impostato su SATA0, puoi avere la prima cifra impostata solo su 1, dove il secondo numero sarà 8 per poter avere 8 dischi (virtuali o RDM) collegati al controller SATA 1.


Then if I have a mainboard with only one controller, 4 sata ports, only one drive connected (on sata0 illustrated on the mainboard), it should be:
SataPortMap=4
DiskIdxMap=00
Is it right? Why did not works?!? 

 

Link to comment
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.

×
×
  • Create New...