Jump to content
XPEnology Community

TinyCore RedPill Loader (TCRP)


pocopico

Recommended Posts

1 hour ago, wenderfit said:

Try "lspci -nnq" on my working DS3617xs DSM 6.2.3-25426 Update 3 with jun loader, found Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller. Perhaps this is the controller for my connected drives. Tinycore loader didn't find it🙃

  lspci -nnq (Hide contents)


root@NAS:~# lspci -nnq
0000:00:00.0 Host bridge [0600]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 DMI2 [8086:0e00] (rev 04)
0000:00:01.0 PCI bridge [0604]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 1a [8086:0e02] (rev 04)
0000:00:01.1 PCI bridge [0604]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 1b [8086:0e03] (rev 04)
0000:00:02.0 PCI bridge [0604]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 2a [8086:0e04] (rev 04)
0000:00:03.0 PCI bridge [0604]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 3a [8086:0e08] (rev 04)
0000:00:05.0 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 VTd/Memory Map/Misc [8086:0e28] (rev 04)
0000:00:05.2 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IIO RAS [8086:0e2a] (rev 04)
0000:00:05.4 PIC [0800]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IOAPIC [8086:0e2c] (rev 04)
0000:00:11.0 PCI bridge [0604]: Intel Corporation C600/X79 series chipset PCI Express Virtual Root Port [8086:1d3e] (rev 06)
0000:00:1a.0 USB controller [0c03]: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #2 [8086:1d2d] (rev 06)
0000:00:1b.0 Audio device [0403]: Intel Corporation C600/X79 series chipset High Definition Audio Controller [8086:1d20] (rev 06)
0000:00:1c.0 PCI bridge [0604]: Intel Corporation C600/X79 series chipset PCI Express Root Port 1 [8086:1d10] (rev b6)
0000:00:1c.2 PCI bridge [0604]: Intel Corporation C600/X79 series chipset PCI Express Root Port 3 [8086:1d14] (rev b6)
0000:00:1d.0 USB controller [0c03]: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #1 [8086:1d26] (rev 06)
0000:00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev a6)
0000:00:1f.0 ISA bridge [0601]: Intel Corporation C600/X79 series chipset LPC Controller [8086:1d41] (rev 06)
0000:00:1f.2 SATA controller [0106]: Intel Corporation C600/X79 series chipset 6-Port SATA AHCI Controller [8086:1d02] (rev 06)
0000:00:1f.3 SMBus [0c05]: Intel Corporation C600/X79 series chipset SMBus Host Controller [8086:1d22] (rev 06)
0000:03:00.0 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection [8086:10fb] (rev 01)
0000:03:10.0 Ethernet controller [0200]: Intel Corporation 82599 Ethernet Controller Virtual Function [8086:10ed] (rev 01)
0000:03:10.2 Ethernet controller [0200]: Intel Corporation 82599 Ethernet Controller Virtual Function [8086:10ed] (rev 01)
0000:03:10.4 Ethernet controller [0200]: Intel Corporation 82599 Ethernet Controller Virtual Function [8086:10ed] (rev 01)
0000:03:10.6 Ethernet controller [0200]: Intel Corporation 82599 Ethernet Controller Virtual Function [8086:10ed] (rev 01)
0000:03:11.0 Ethernet controller [0200]: Intel Corporation 82599 Ethernet Controller Virtual Function [8086:10ed] (rev 01)
0000:03:11.2 Ethernet controller [0200]: Intel Corporation 82599 Ethernet Controller Virtual Function [8086:10ed] (rev 01)
0000:03:11.4 Ethernet controller [0200]: Intel Corporation 82599 Ethernet Controller Virtual Function [8086:10ed] (rev 01)
0000:03:11.6 Ethernet controller [0200]: Intel Corporation 82599 Ethernet Controller Virtual Function [8086:10ed] (rev 01)
0000:08:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
0000:ff:08.0 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 QPI Link 0 [8086:0e80] (rev 04)
0000:ff:09.0 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 QPI Link 1 [8086:0e90] (rev 04)
0000:ff:0a.0 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 0 [8086:0ec0] (rev 04)
0000:ff:0a.1 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 1 [8086:0ec1] (rev 04)
0000:ff:0a.2 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 2 [8086:0ec2] (rev 04)
0000:ff:0a.3 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 3 [8086:0ec3] (rev 04)
0000:ff:0b.0 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 UBOX Registers [8086:0e1e] (rev 04)
0000:ff:0b.3 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 UBOX Registers [8086:0e1f] (rev 04)
0000:ff:0c.0 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers [8086:0ee0] (rev 04)
0000:ff:0c.1 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers [8086:0ee2] (rev 04)
0000:ff:0c.2 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers [8086:0ee4] (rev 04)
0000:ff:0c.3 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers [8086:0ee6] (rev 04)
0000:ff:0d.0 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers [8086:0ee1] (rev 04)
0000:ff:0d.1 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers [8086:0ee3] (rev 04)
0000:ff:0d.2 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers [8086:0ee5] (rev 04)
0000:ff:0d.3 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers [8086:0ee7] (rev 04)
0000:ff:0e.0 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 0 [8086:0ea0] (rev 04)
0000:ff:0e.1 Performance counters [1101]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 0 [8086:0e30] (rev 04)
0000:ff:0f.0 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Target Address/Thermal Registers [8086:0ea8] (rev 04)
0000:ff:0f.1 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 RAS Registers [8086:0e71] (rev 04)
0000:ff:0f.2 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers [808... (rev 04)
0000:ff:0f.3 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers [808... (rev 04)
0000:ff:0f.4 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers [808... (rev 04)
0000:ff:0f.5 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers [808... (rev 04)
0000:ff:10.0 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 0 [8086:0eb0] (rev 04)
0000:ff:10.1 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 1 [8086:0eb1] (rev 04)
0000:ff:10.2 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 0 [8086:0eb2] (rev 04)
0000:ff:10.3 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 1 [8086:0eb3] (rev 04)
0000:ff:10.4 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 2 [8086:0eb4] (rev 04)
0000:ff:10.5 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 3 [8086:0eb5] (rev 04)
0000:ff:10.6 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 2 [8086:0eb6] (rev 04)
0000:ff:10.7 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 3 [8086:0eb7] (rev 04)
0000:ff:13.0 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 R2PCIe [8086:0e1d] (rev 04)
0000:ff:13.1 Performance counters [1101]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 R2PCIe [8086:0e34] (rev 04)
0000:ff:13.4 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 QPI Ring Registers [8086:0e81] (rev 04)
0000:ff:13.5 Performance counters [1101]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 QPI Ring Performance Ring Monitoring [8086:0e36] (rev 04)
0000:ff:16.0 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 System Address Decoder [8086:0ec8] (rev 04)
0000:ff:16.1 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Broadcast Registers [8086:0ec9] (rev 04)
0000:ff:16.2 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Broadcast Registers [8086:0eca] (rev 04)
0001:00:02.0 Non-VGA unclassified device [0000]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 2 [8086:6f04] (rev ff)
0001:00:02.2 Non-VGA unclassified device [0000]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 2 [8086:6f06] (rev ff)
0001:00:03.0 Non-VGA unclassified device [0000]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 [8086:6f08] (rev ff)
0001:00:03.2 Non-VGA unclassified device [0000]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 [8086:6f0a] (rev ff)
0001:00:1f.0 Non-VGA unclassified device [0000]: Intel Corporation C224 Series Chipset Family Server Standard SKU LPC Controller [8086:8c54] (rev ff)
0001:00:1f.3 Non-VGA unclassified device [0000]: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] (rev ff)
0001:06:00.0 Non-VGA unclassified device [0000]: Marvell Technology Group Ltd. Device [1b4b:1475] (rev ff)
0001:08:00.0 Non-VGA unclassified device [0000]: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] (rev ff)
0001:09:00.0 Non-VGA unclassified device [0000]: Intel Corporation I210 Gigabit Network Connection [8086:1533] (rev ff)
0001:0c:00.0 Non-VGA unclassified device [0000]: Intel Corporation I210 Gigabit Network Connection [8086:1533] (rev ff)
0001:0d:00.0 Non-VGA unclassified device [0000]: Intel Corporation I210 Gigabit Network Connection [8086:1533] (rev ff)

 

 

if these are embedded sata controllers then I would try switching to 4 for satamap and 00 for diskid. If you plan on using both in the future then I would do 64 for sata and then 0007 for the diskid. Try that and see what ya get.

Link to comment
Share on other sites

15 minutes ago, Peter Suh said:

 

So far, a total of three platforms have been successfully installed with BAREMETAL.
The method is to start from 7.0.1 build as guided by @pocopico
It is a two step update build method.

The rest of the platforms still have errors, so I will continue to report bugs to @pocopico.

 

The following commands were used.

 

[DS3622xs+]

 

./rploader.sh update now

./rploader.sh fullupgrade now

 

./rploader.sh serialgen DS3622xs+

./rploader.sh identifyusb now

./rploader.sh satamap now

 

./rploader.sh build broadwellnk-7.0.1-42218

./rploader.sh clean now

./rploader.sh build broadwellnk-7.1.0-42661

 

./rploader.sh clean now;  rm -rf /mnt/sdb3/auxfiles;  rm -rf /home/tc/custom-module;  ./rploader.sh backup now;

 

1655034970_3622_2022-04-1012_02_58.thumb.png.b8df5ab6659d29c4d606d716bd4f38d7.png

 

[DS918+]

 

./rploader.sh update now

./rploader.sh fullupgrade now

 

./rploader.sh serialgen DS918+

./rploader.sh identifyusb now

./rploader.sh satamap now

 

./rploader.sh build apollolake-7.0.1-42218

./rploader.sh clean now

./rploader.sh build apollolake-7.1.0-42661

 

./rploader.sh clean now;  rm -rf /mnt/sdb3/auxfiles;  rm -rf /home/tc/custom-module;  ./rploader.sh backup now;

 

495950054_9182022-04-0911_18_45.thumb.png.73b4ad4f166e9673182e666da22f9540.png

 

[DS3615xs]

 

./rploader.sh update now

./rploader.sh fullupgrade now

 

./rploader.sh serialgen DS3615xs

./rploader.sh identifyusb now

./rploader.sh satamap now

 

./rploader.sh build bromolow-7.0.1-42218

./rploader.sh clean now

./rploader.sh build bromolow-7.1.0-42661

 

./rploader.sh clean now;  rm -rf /mnt/sdb3/auxfiles;  rm -rf /home/tc/custom-module;  ./rploader.sh backup now;

 

2066439837_36152022-04-101_07_21.thumb.png.d4417e6e96aca68d78069508f3764594.png

Going to try and do these commands now and see if I can get this installed. I am 15+ hours down trying to get this installed on Promox and nothing works :(. 

 

Anyone know how to get DSM installed on proxmox correctly? I have read about 4 different tutorials in here and none work. I dont know where I am messing up :(

Edited by NotHere
Link to comment
Share on other sites

@Peter Suh

I followed the steps and commands. I still get he 45% and then corrupted file. Im going to try and change my user_config.json and report back later. I can't do it right now, but if someone could check that maybe getting the same error, check for errors while pat is trying to install?  It would help out.  Thanks in advance.

Link to comment
Share on other sites

il y a 5 minutes, Dvalin21 a dit :

@Peter Suh

I followed the steps and commands. I still get he 45% and then corrupted file. Im going to try and change my user_config.json and report back later. I can't do it right now, but if someone could check that maybe getting the same error, check for errors while pat is trying to install?  It would help out.  Thanks in advance.

Same for me... I still get he 45% and then corrupted file

 

With this Guide for 918+

[DS918+]

 

./rploader.sh update now

./rploader.sh fullupgrade now

 

./rploader.sh serialgen DS918+

./rploader.sh identifyusb now

./rploader.sh satamap now

 

./rploader.sh build apollolake-7.0.1-42218

./rploader.sh clean now

./rploader.sh build apollolake-7.1.0-42661

 

./rploader.sh clean now;  rm -rf /mnt/sdb3/auxfiles;  rm -rf /home/tc/custom-module;  ./rploader.sh backup now;

 

I get the two ds918p_42661.pat in cache and auxfiles same error for this two files

 

Link to comment
Share on other sites

 

21 hours ago, pocopico said:
21 hours ago, Badger said:

I'll be attempting a Tinycore build for my existing setup (3615xs w/ 6.2.3-25426 Update 3).  I have three 4TB drives installed.  Should I leave them as is, or format and remove all partitions before I start?  They're JBOD.  It would be nice if I didn't have to do a restore, but I can go either way since I have everything backed up.

Leave them as is. Backup is always recommended 

Wow!  Plug and play.  So far so good.  3622xs+ w/7.0.1-42218 on old MSI (MS-7641) mobo w/ AMD CPU (Phenom I think).  All apps and data migrated as far as I can tell.  Thanks so much for this!

  • Like 1
Link to comment
Share on other sites

1 hour ago, Peter Suh said:

 

So far, a total of three platforms have been successfully installed with BAREMETAL.
The method is to start from 7.0.1 build as guided by @pocopico
It is a two step update build method.

The rest of the platforms still have errors, so I will continue to report bugs to @pocopico.

 

The following commands were used.

 

[DS3622xs+]

 

./rploader.sh update now

./rploader.sh fullupgrade now

 

./rploader.sh serialgen DS3622xs+

./rploader.sh identifyusb now

./rploader.sh satamap now

 

./rploader.sh build broadwellnk-7.0.1-42218

./rploader.sh clean now

./rploader.sh build broadwellnk-7.1.0-42661

 

./rploader.sh clean now;  rm -rf /mnt/sdb3/auxfiles;  rm -rf /home/tc/custom-module;  ./rploader.sh backup now;

 

1655034970_3622_2022-04-1012_02_58.thumb.png.b8df5ab6659d29c4d606d716bd4f38d7.png

 

[DS918+]

 

./rploader.sh update now

./rploader.sh fullupgrade now

 

./rploader.sh serialgen DS918+

./rploader.sh identifyusb now

./rploader.sh satamap now

 

./rploader.sh build apollolake-7.0.1-42218

./rploader.sh clean now

./rploader.sh build apollolake-7.1.0-42661

 

./rploader.sh clean now;  rm -rf /mnt/sdb3/auxfiles;  rm -rf /home/tc/custom-module;  ./rploader.sh backup now;

 

495950054_9182022-04-0911_18_45.thumb.png.73b4ad4f166e9673182e666da22f9540.png

 

[DS3615xs]

 

./rploader.sh update now

./rploader.sh fullupgrade now

 

./rploader.sh serialgen DS3615xs

./rploader.sh identifyusb now

./rploader.sh satamap now

 

./rploader.sh build bromolow-7.0.1-42218

./rploader.sh clean now

./rploader.sh build bromolow-7.1.0-42661

 

./rploader.sh clean now;  rm -rf /mnt/sdb3/auxfiles;  rm -rf /home/tc/custom-module;  ./rploader.sh backup now;

 

2066439837_36152022-04-101_07_21.thumb.png.d4417e6e96aca68d78069508f3764594.png

 

Screen Shot 2022-04-10 at 2.55.04 AM.png

  • Like 1
Link to comment
Share on other sites

The same error of HDDs. I think there is some error in recently modified files. Recently i successfully installed 7.0.1. version using 0.4.5 version of loader. Now the attempt to full clear install of 7.0.1 using 0.4.5 loader version gives same HDD errors. @pocopicoplease verify last changes. And I think it's not port map error because when I connect HDD with installed DSM 7.0.1 taken from other machine everything was working fine (with both versions of loader)

 

Now I found usb stick with 7.0.1 loader generated 1-2 month ago, take empty HDD. There is no errors at all.

Usb sticks with 0.4.5 and 0.4.6 versions of loader generated today can't install DSM showing HDDs error.

 

So all port map changes won't give result, we should find error in other part of loader

Edited by Korob
  • Like 1
  • Thanks 2
Link to comment
Share on other sites

il y a 2 minutes, blindspot a dit :

Download from Synology DS918+. I think it has to be the original one when you update from manual DSM update. That's how I did it. I've tried to use the cached one but didn't work.

ds918p_42661.pat decrypted is needed but the builded by rploader.sh is corrupt...

@Peter Suh and @loveburn They succeeded... 

 

I hope someone gonna shared ds918p_42661.pat decrypted

Link to comment
Share on other sites

3 hours ago, Peter Suh said:

[DS918+]

 

./rploader.sh update now

./rploader.sh fullupgrade now

 

./rploader.sh serialgen DS918+

./rploader.sh identifyusb now

./rploader.sh satamap now

 

./rploader.sh build apollolake-7.0.1-42218

./rploader.sh clean now

./rploader.sh build apollolake-7.1.0-42661

 

./rploader.sh clean now;  rm -rf /mnt/sdb3/auxfiles;  rm -rf /home/tc/custom-module;  ./rploader.sh backup now;

 

495950054_9182022-04-0911_18_45.thumb.png.73b4ad4f166e9673182e666da22f9540.png

 

Is this process to upgrade from dsm 7.0.1 (manual upgrade inside dsm using pat from synology, reboot to tc run these commands and reboot nas)

or is this process to install fresh 7.1 from the ground up?  I think thats where the confusion is.

Link to comment
Share on other sites

30 minutes ago, Doud said:

ds918p_42661.pat decrypted is needed but the builded by rploader.sh is corrupt...

@Peter Suh and @loveburn They succeeded... 

 

I hope someone gonna shared ds918p_42661.pat decrypted

I just did it like 30 min ago by running  ./rploader.sh build apollolake-7.1.0-42661 and it decrypted fine.

14 minutes ago, phone guy said:

this process to upgrade from dsm 7.0.1 ---> manual upgrade inside dsm using pat from synology, reboot to tc run these commands and reboot nas

Yes, tested and working.

Edited by blindspot
Link to comment
Share on other sites

So I went through the process and downloaded 7.1 from the site and installed it.  Im now setting up the NAS!!! The decrypted file for me didnt work. With the official file from the global I had to go into etc.defaults/synoinfo.conf and add support_syno_hybrid_raid="yes" and change supportraidgroup to "no" and reboot.

Edited by Dvalin21
Link to comment
Share on other sites

 

For users who are confused by multiple installation guides, I will define the purpose of each guide.

A. It is a TinyCore Redfill (shortened as TCRP) introductory document that installs only DSM 7.0.1.

 

 

 


B. It is a guide that utilizes postupdate action when DSM 7 is already installed and updates are needed.

 

 


C. This is a guide that requires the build process of TWOS STEP UPDATE (referred to as TSU for single installation of DSM 7.1).

 

 

 

 

 

  • Like 4
  • Thanks 1
Link to comment
Share on other sites

 

It is an important part of A's introductory content

Please use SataportMap when you are confused about how to set it.

It is happiest when it is a motherboard without a multi-speed (Sata2 + Sata3), multi sata controller and Muxed.

The moment you meet the Muxed Sata Port, it's a headache, and if you give up from the beginning and pretend to be a port that doesn't exist, it's simple to think.

The phenomenon of failing to fill 100% of the DSM installation and stopping in the middle is not irrelevant to the characteristics mentioned above in experience.

 

---------------------------------------------------------------------------------------------------------

 

5.BIOS built-in SATA port Hot Plug disable -> enable (important)

 

To avoid temporarily reducing the SataPortMap value set above by the number of HDD physically connected by Sata cable during DSM installation,

 

Be sure to turn on the Hot Plug function.

 

This reduces the probability of encountering an error message saying that the HDD cannot be found because the number of SataPortMap automatically above is recognized as normal recognized.

 

However, if M.2 and Sata ports are Muxed Sata ports that share Lane, it should be considered unusable.

Link to comment
Share on other sites

Thank you so much for this guides!!

 

I have successful install with your guide and by the original .pat on USB stick

 

But i try to 1st boot for make install by HDD on SATA and no work after first reboot install needed

Link to comment
Share on other sites

5 minutes ago, Doud said:

Thank you so much for this guides!!

 

I have successful install with your guide and by the original .pat on USB stick

 

But i try to 1st boot for make install by HDD on SATA and no work after first reboot install needed

 

The successful installation of the DSM means that the NIC has been given a normal IP, and I have experienced this IP change from time to time.


So I don't trust Synology Assistant, and I check and use the exact IP allocated from the router to the PC.

Link to comment
Share on other sites

17 minutes ago, phone guy said:

Can anyone help me get my second onboard nic port working? It worked under jun104b loader and dsm623, but something changed in rp and dsm7... now even under dsm 7.1 I still only have 1 working nic port.... please @pocopico@IG-88@Peter Suh

 

 

 

The second NIC is not an onboard type, but an external USB type NIC.
I have the same model
There have been no successful cases of REALTEK USB NIC
I tried to use it, but I failed.
It seems like the driver needs to be modified, but only @pocopico can solve it.

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...