DS1621+ V1000 issues with TinyCore - No USB boot option after build and missing SATA controller

[wessu]

I was curious to test DSM on my AMD rig and learn more about the software. I have 8 SATA ports per my motherboard specs. I used tinycore build and followed the tutorials. I got two problems: after the installation and rebooting I don't see DSM option in GRUB and only tinycore. There was an error about writing something to the USB but I couldn't figure it out.

Quote

Patching USB to include your loader. Loader found in 1-4 port
Converting dts file : ds1621p.dts to dtb file : >ds1621p.dtb
dtb extension is not loaded and its required for DSM to find disks on ds1621p_42661
Copy of the DTB file ds1621p.dtb to  was not succesfull.
Please remember to replace the dtb extension model file ...

 

 

 

The other thing as I was going through the logs is missing SATA controller extension. I'm using Ryzen CPU on X570 chipset motherboard from Asus.

Quote

Found SATA Controller : pciid 1022d00007901  Required Extension :
No matching extension
Found SATA Controller : pciid 1022d00007901  Required Extension :
No matching extension
Found VGA Controller : pciid 10ded00002484  Required Extension :
No matching extension

 

 

Attached is the log I grabbed from Putty. I copy pasted everything in a Notepad++ file. I don't know how to generate a log either. Help is appreciated.

 

tinycore.txt

[flyride]

Those errors are for hardware that is not in your system, no issues there.

 

DS1621+ uses a Device Tree to identify disk ports, which is somewhat experimental.  I think recently part of the code to generate the device tree was non-functional, although it may have been corrected in the last 24 hours or so.

 

Regardless, DS3622xs+ is a better choice.  There is no known advantage to using the AMD-specific build.

 

For more information:

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

 

[wessu]

So I can use DS3622xs+ with AMD? I will try it tonight and post my results.

Any explanation why the bootloader did not show DSM after the build? was it because of the device tree issue?

[pocopico]

15 minutes ago, flyride said:

Those errors are for hardware that is not in your system, no issues there.

 

DS1621+ uses a Device Tree to identify disk ports, which is somewhat experimental.  I think recently part of the code to generate the device tree was non-functional, although it may have been corrected in the last 24 hours or so.

 

Regardless, DS3622xs+ is a better choice.  There is no known advantage to using the AMD-specific build.

 

For more information:

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

 

 

Im afraid i have to agree with @flyride, although TTH always said running non AMD kernel is not your best option, i have found no real issues with my main AMD system running DS3622xs+ loader.

 

Avoid using 0 on your first adapter in Satamap cause it is known to cause kernel panic. I think we've got that fixed. Perform an update on the script and it should be fixed.

[R0AHJ]

1 час назад, wessu сказал:

I was curious to test DSM on my AMD rig and learn more about the software. I have 8 SATA ports per my motherboard specs. I used tinycore build and followed the tutorials. I got two problems: after the installation and rebooting I don't see DSM option in GRUB and only tinycore. There was an error about writing something to the USB but I couldn't figure it out.

 

 

 

The other thing as I was going through the logs is missing SATA controller extension. I'm using Ryzen CPU on X570 chipset motherboard from Asus.

 

 

Attached is the log I grabbed from Putty. I copy pasted everything in a Notepad++ file. I don't know how to generate a log either. Help is appreciated.

 

tinycore.txtFetching info...

This is what I see as well. The saddest thing is that a few days ago, on the same machine, the DS 1621 was working fine... Then I inadvertently damaged the USB drive with the bootloader. Now, when trying to restore my system, I get the following:

Actually interested in the following:
  1. What is this line 23281 ?
2. Why does it say " DTB-extension not loaded " when it is loaded from the repository?
3. Is it somehow possible to fix it yourself? If "yes", please tell me step by step.

 

Edited May 23, 2022 by R0AHJ

[wessu]

4 minutes ago, R0AHJ said:

This is what I see as well. The saddest thing is that a few days ago, on the same machine, the DS 1621 was working fine... Then I inadvertently damaged the USB drive with the bootloader. Now, when trying to restore my system, I get the following:

 

I tried to do cp ds1621p.dtb but there is no destination? so I didn't know where to copy it to.

 

I'm new to all this but excited as well. I will try the DS3622xs+ tonight as it should work on AMD even thought it is a non AMD kernel per @flyride and @pocopico.

[pocopico]

5 minutes ago, wessu said:

 

I tried to do cp ds1621p.dtb but there is no destination? so I didn't know where to copy it to.

 

I'm new to all this but excited as well. I will try the DS3622xs+ tonight as it should work on AMD even thought it is a non AMD kernel per @flyride and @pocopico.

 

It just happens to build your loader now that we are in the middle of a decision. Jumkey performed a change on hist dtb extension and we need to decide which process we keep. Meanwhile, i suggest you use the redpill dtb and ignore this message.

 

 

[R0AHJ]

1 минуту назад, pocopico сказал:

 

, я предлагаю вам использовать redpill dtb и игнорировать это сообщение.

 

 

I don't quite understand how to use redpill dtb
could you give instructions - what needs to be done to burn the bootloader?

[pocopico]

3 hours ago, R0AHJ said:

I don't quite understand how to use redpill dtb
could you give instructions - what needs to be done to burn the bootloader?

 

You dont have to do anything, its a prerequisite for your loader, so it will be added automatically. 

 

[wessu]

I was able to install DSM using DS3622xs+ configuration on Ryzen 9 3900X on a X570 chipset!  😀

 

I have some questions though: when I do the configuration, it asks me "twice" for number of SATA ports when you run the command, and it asks to select from 0-9. So If I select 1 for the first and 2 for the second I get my SATA HDD recognized as it is attached to SATA 2 port on the motherboard (per BIOS info). Also, I go to the BIOS I can see 6 SATA drives configuration under SATA, so I set them all to HOT PLUG.

Now, if I change the settings on the second command option to 8 ports or even 4 ports, I get a weird message when I try to install DSM. I captured screenshots to highlight the problem. I don't know why this happens. So I had to go back and downgrade my ports number to be able to get the installer to work. I thought this was supposed to be automatic detect not like drive tree. Maybe I don't understand how this works.

I also tried to get the second option set to 1 but it was unable to locate my HDD attached to SATA 2 so I had to go back and bump the number from 1 to 2 and it worked. Maybe some explanation on how the SATA ports numbering system works would be helpful.

[flyride]

If it asks you twice, it is because it sees that you have two different SATA controllers.  You should understand how your ports are connected to the controllers in order to answer.  What motherboard are you using?

[wessu]

2 minutes ago, flyride said:

If it asks you twice, it is because it sees that you have two different SATA controllers.  You should understand how your ports are connected to the controllers in order to answer.  What motherboard are you using?

 

Thanks for the quick response! Here is my motherboard.

https://www.asus.com/us/Motherboards-Components/Motherboards/TUF-Gaming/TUF-GAMING-X570-PLUS-WI-FI/

 

I'm using this as a learning opportunity.

[flyride]

I finally found this reference on your board. 

https://linux-hardware.org/?probe=7b71c09e85

 

It looks like there are two SATA controllers presented to the system. Given the way the ports are grouped, I would assume that 4 are attached to one, and 4 to the other.

 

If you want to retry the satamap you can put in 4 and 4 and see what it does.  Alternatively, the next update of the TCRP rploader script will have a query for the port count in it and suggest it to you instead of making you choose (or guess, in this case).

 

[wessu]

I tried to look for the Linux commands you posted earlier but they are gone now. Can you post them again?

I did a 4 x 4 setup and now DSM cannot detect the disk for installation. I only have an HDD drive attached to SATA 3 port. Somehow it moved to it after I reconnected it and unplugged all of my other drives.

 

[wessu]

Plugging 3 of my other drives back in, I got the following error message.

[flyride]

launch the TCRP console at https://<your ip>:7681

 

login with root

 

confirm your grub args with

cat /proc/cmdline

 

See what drives are connected where with

ls -la /sys/block

 

Post the outputs.

[wessu]

tc@box:~$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz64 loglevel=3 cde waitusb=5 vga=791
tc@box:~$ ls -la /sys/block
total 0
drwxr-xr-x  2 root root 0 May 25 13:24 ./
dr-xr-xr-x 13 root root 0 May 25 13:24 ../
lrwxrwxrwx  1 root root 0 May 25 13:24 loop0 -> ../devices/virtual/block/loop0
lrwxrwxrwx  1 root root 0 May 25 13:24 loop1 -> ../devices/virtual/block/loop1
lrwxrwxrwx  1 root root 0 May 25 13:25 loop10 -> ../devices/virtual/block/loop10
lrwxrwxrwx  1 root root 0 May 25 13:25 loop11 -> ../devices/virtual/block/loop11
lrwxrwxrwx  1 root root 0 May 25 13:25 loop12 -> ../devices/virtual/block/loop12
lrwxrwxrwx  1 root root 0 May 25 13:25 loop13 -> ../devices/virtual/block/loop13
lrwxrwxrwx  1 root root 0 May 25 13:25 loop14 -> ../devices/virtual/block/loop14
lrwxrwxrwx  1 root root 0 May 25 13:25 loop15 -> ../devices/virtual/block/loop15
lrwxrwxrwx  1 root root 0 May 25 13:25 loop16 -> ../devices/virtual/block/loop16
lrwxrwxrwx  1 root root 0 May 25 13:25 loop17 -> ../devices/virtual/block/loop17
lrwxrwxrwx  1 root root 0 May 25 13:25 loop18 -> ../devices/virtual/block/loop18
lrwxrwxrwx  1 root root 0 May 25 13:25 loop19 -> ../devices/virtual/block/loop19
lrwxrwxrwx  1 root root 0 May 25 13:24 loop2 -> ../devices/virtual/block/loop2
lrwxrwxrwx  1 root root 0 May 25 13:25 loop20 -> ../devices/virtual/block/loop20
lrwxrwxrwx  1 root root 0 May 25 13:25 loop21 -> ../devices/virtual/block/loop21
lrwxrwxrwx  1 root root 0 May 25 13:25 loop22 -> ../devices/virtual/block/loop22
lrwxrwxrwx  1 root root 0 May 25 13:25 loop23 -> ../devices/virtual/block/loop23
lrwxrwxrwx  1 root root 0 May 25 13:25 loop24 -> ../devices/virtual/block/loop24
lrwxrwxrwx  1 root root 0 May 25 13:25 loop25 -> ../devices/virtual/block/loop25
lrwxrwxrwx  1 root root 0 May 25 13:25 loop26 -> ../devices/virtual/block/loop26
lrwxrwxrwx  1 root root 0 May 25 13:25 loop27 -> ../devices/virtual/block/loop27
lrwxrwxrwx  1 root root 0 May 25 13:25 loop28 -> ../devices/virtual/block/loop28
lrwxrwxrwx  1 root root 0 May 25 13:25 loop29 -> ../devices/virtual/block/loop29
lrwxrwxrwx  1 root root 0 May 25 13:24 loop3 -> ../devices/virtual/block/loop3
lrwxrwxrwx  1 root root 0 May 25 13:25 loop30 -> ../devices/virtual/block/loop30
lrwxrwxrwx  1 root root 0 May 25 13:25 loop31 -> ../devices/virtual/block/loop31
lrwxrwxrwx  1 root root 0 May 25 13:25 loop32 -> ../devices/virtual/block/loop32
lrwxrwxrwx  1 root root 0 May 25 13:25 loop33 -> ../devices/virtual/block/loop33
lrwxrwxrwx  1 root root 0 May 25 13:25 loop34 -> ../devices/virtual/block/loop34
lrwxrwxrwx  1 root root 0 May 25 13:25 loop35 -> ../devices/virtual/block/loop35
lrwxrwxrwx  1 root root 0 May 25 13:25 loop36 -> ../devices/virtual/block/loop36
lrwxrwxrwx  1 root root 0 May 25 13:25 loop37 -> ../devices/virtual/block/loop37
lrwxrwxrwx  1 root root 0 May 25 13:25 loop38 -> ../devices/virtual/block/loop38
lrwxrwxrwx  1 root root 0 May 25 13:25 loop39 -> ../devices/virtual/block/loop39
lrwxrwxrwx  1 root root 0 May 25 13:24 loop4 -> ../devices/virtual/block/loop4
lrwxrwxrwx  1 root root 0 May 25 13:25 loop40 -> ../devices/virtual/block/loop40
lrwxrwxrwx  1 root root 0 May 25 13:25 loop41 -> ../devices/virtual/block/loop41
lrwxrwxrwx  1 root root 0 May 25 13:25 loop42 -> ../devices/virtual/block/loop42
lrwxrwxrwx  1 root root 0 May 25 13:25 loop43 -> ../devices/virtual/block/loop43
lrwxrwxrwx  1 root root 0 May 25 13:25 loop44 -> ../devices/virtual/block/loop44
lrwxrwxrwx  1 root root 0 May 25 13:25 loop45 -> ../devices/virtual/block/loop45
lrwxrwxrwx  1 root root 0 May 25 13:25 loop46 -> ../devices/virtual/block/loop46
lrwxrwxrwx  1 root root 0 May 25 13:25 loop47 -> ../devices/virtual/block/loop47
lrwxrwxrwx  1 root root 0 May 25 13:25 loop48 -> ../devices/virtual/block/loop48
lrwxrwxrwx  1 root root 0 May 25 13:25 loop49 -> ../devices/virtual/block/loop49
lrwxrwxrwx  1 root root 0 May 25 13:24 loop5 -> ../devices/virtual/block/loop5
lrwxrwxrwx  1 root root 0 May 25 13:25 loop50 -> ../devices/virtual/block/loop50
lrwxrwxrwx  1 root root 0 May 25 13:25 loop51 -> ../devices/virtual/block/loop51
lrwxrwxrwx  1 root root 0 May 25 13:24 loop6 -> ../devices/virtual/block/loop6
lrwxrwxrwx  1 root root 0 May 25 13:24 loop7 -> ../devices/virtual/block/loop7
lrwxrwxrwx  1 root root 0 May 25 13:25 loop8 -> ../devices/virtual/block/loop8
lrwxrwxrwx  1 root root 0 May 25 13:25 loop9 -> ../devices/virtual/block/loop9
lrwxrwxrwx  1 root root 0 May 25 13:24 nvme0n1 -> ../devices/pci0000:00/0000:00:                                                                                        01.1/0000:01:00.0/nvme/nvme0/nvme0n1
lrwxrwxrwx  1 root root 0 May 25 13:24 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx  1 root root 0 May 25 13:24 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx  1 root root 0 May 25 13:24 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx  1 root root 0 May 25 13:24 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx  1 root root 0 May 25 13:24 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx  1 root root 0 May 25 13:24 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx  1 root root 0 May 25 13:24 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx  1 root root 0 May 25 13:24 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx  1 root root 0 May 25 13:24 sda -> ../devices/pci0000:00/0000:00:01.2                                                                                        /0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata5/host4/target4:0:0/4:0:0:0/block/sda
lrwxrwxrwx  1 root root 0 May 25 13:24 sdb -> ../devices/pci0000:00/0000:00:01.2                                                                                        /0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata6/host5/target5:0:0/5:0:0:0/block/sdb
lrwxrwxrwx  1 root root 0 May 25 13:24 sdc -> ../devices/pci0000:00/0000:00:01.2                                                                                        /0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata9/host8/target8:0:0/8:0:0:0/block/sdc
lrwxrwxrwx  1 root root 0 May 25 13:24 sdd -> ../devices/pci0000:00/0000:00:01.2                                                                                        /0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata10/host9/target9:0:0/9:0:0:0/block/sd                                                                                        d
lrwxrwxrwx  1 root root 0 May 25 13:24 sde -> ../devices/pci0000:00/0000:00:01.2                                                                                        /0000:02:00.0/0000:03:08.0/0000:09:00.1/usb1/1-4/1-4:1.0/host10/target10:0:0/10:                                                                                        0:0:0/block/sde
lrwxrwxrwx  1 root root 0 May 25 13:24 zram0 -> ../devices/virtual/block/zram0
tc@box:~$

 

 

BTW, when I try to boot tinyCore, I am presented with 3 options in the bios. I can pick the first one or the last one. Not sure if there is any difference. Attached is the same dump in a Notepad++ file.

pci.txt

[flyride]

You executed that from TinyCore. The instructions were to launch the TCRP shell when DSM was at an install page, fwiw.

 

No matter.  Re-run ./rploader.sh update now and ./rploader.sh satamap now and post the output.

[flyride]

40 minutes ago, wessu said:

BTW, when I try to boot tinyCore, I am presented with 3 options in the bios. I can pick the first one or the last one. Not sure if there is any difference. 

Not sure what this means.  Are you referring to the grub menu?

[wessu]

2 hours ago, flyride said:

You executed that from TinyCore. The instructions were to launch the TCRP shell when DSM was at an install page, fwiw.

 

No matter.  Re-run ./rploader.sh update now and ./rploader.sh satamap now and post the output.

 

I read the instructions but did not quite understand it at first. Now it makes sense. I will do that tonight and report. I will also try the script again and report. Thanks.

[wessu]

2 hours ago, flyride said:

Not sure what this means.  Are you referring to the grub menu?

I enabled UEFI and CSM boot options in BIOS. So I am presented with 4 USB boot options from the memory stick (3 look the same, and one by itself). I am not sure what's the difference. The first one has a nice resolution and the last one has more like a VGA look. I thought the first one is UEFI boot and the last one is CSM boot? I could be wrong. I will post screen shots as well. I used Rufus to prepare the stick.

[wessu]

19 hours ago, flyride said:

launch the TCRP console at https://<your ip>:7681

 

login with root

 

confirm your grub args with

cat /proc/cmdline

 

See what drives are connected where with

ls -la /sys/block

 

Post the outputs.

 

Synology strongly advises you not to run commands as the root user, who has
the highest privileges on the system. Doing so may cause major damages
to the system. Please note that if you choose to proceed, all consequences are
at your own risk.

BusyBox v1.30.1 () built-in shell (ash)

SynologyNAS> cat /proc/cmdline
BOOT_IMAGE=/zImage withefi syno_hw_version=DS3622xs+ console=ttyS0,115200n8 netif_num=5 earlycon=uart8250,io,0x3f8,115200n8 mac1=0011320A0075 sn=2030SQRFRJPWX HddHotplug=0 DiskIdxMap=0004 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=0 root=/dev/md0 SataPortMap=44
SynologyNAS> ls -la /sys/block
drwxr-xr-x    2 root     root             0 May 26 01:02 .
dr-xr-xr-x   12 root     root             0 May 26 01:02 ..
lrwxrwxrwx    1 root     root             0 May 26 01:02 nvme0n1 -> ../devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1
lrwxrwxrwx    1 root     root             0 May 26 01:04 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx    1 root     root             0 May 26 01:04 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx    1 root     root             0 May 26 01:04 ram10 -> ../devices/virtual/block/ram10
lrwxrwxrwx    1 root     root             0 May 26 01:04 ram11 -> ../devices/virtual/block/ram11
lrwxrwxrwx    1 root     root             0 May 26 01:04 ram12 -> ../devices/virtual/block/ram12
lrwxrwxrwx    1 root     root             0 May 26 01:04 ram13 -> ../devices/virtual/block/ram13
lrwxrwxrwx    1 root     root             0 May 26 01:04 ram14 -> ../devices/virtual/block/ram14
lrwxrwxrwx    1 root     root             0 May 26 01:04 ram15 -> ../devices/virtual/block/ram15
lrwxrwxrwx    1 root     root             0 May 26 01:04 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx    1 root     root             0 May 26 01:04 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx    1 root     root             0 May 26 01:04 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx    1 root     root             0 May 26 01:04 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx    1 root     root             0 May 26 01:04 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx    1 root     root             0 May 26 01:04 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx    1 root     root             0 May 26 01:04 ram8 -> ../devices/virtual/block/ram8
lrwxrwxrwx    1 root     root             0 May 26 01:04 ram9 -> ../devices/virtual/block/ram9
lrwxrwxrwx    1 root     root             0 May 26 01:02 sde -> ../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata5/host4/target4:0:0/4:0:0:0/block/sde
lrwxrwxrwx    1 root     root             0 May 26 01:02 sdf -> ../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata6/host5/target5:0:0/5:0:0:0/block/sdf
lrwxrwxrwx    1 root     root             0 May 26 01:04 synoboot -> ../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:09:00.1/usb1/1-4/1-4:1.0/host8/target8:0:0/8:0:0:0/block/synoboot
SynologyNAS>

[wessu]

11 hours ago, flyride said:

Not sure what this means.  Are you referring to the grub menu?

 

Is there a difference if you select a UEFI boot vs CSM boot for tinyCore? See attached image. BTW, these are all my currently connected drives.

[wessu]

11 hours ago, flyride said:

You executed that from TinyCore. The instructions were to launch the TCRP shell when DSM was at an install page, fwiw.

 

No matter.  Re-run ./rploader.sh update now and ./rploader.sh satamap now and post the output.

 

I did update now command. Here is the results:

 

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

Found "0a:00.0 Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)"
Detected 4 ports/0 drives. Override # of ports or ENTER to accept <4> 4

Found "0b:00.0 Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)"
Detected 6 ports/4 drives. Override # of ports or ENTER to accept <6> 6

Recommended settings:
SataPortMap=46
DiskIdxMap=0004

Should i update the user_config.json with these values ? [Yy/Nn] y
Done.

[wessu]

Trying again with 4 for SATA controller 1 and 6 for SATA controller 2, I get this error message. Not sure why those are triggering the problem.