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

[wessu]

Under BIOS>Advanced>SATA Configuration

I get only SATA 1-8 and 2 NVMEs. Is it possible that those two NVMEs are causing 7,8 errors in the previous picture?

 

[flyride]

13 minutes ago, wessu said:

 

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.

 

Your motherboard supports UEFI boot and CSM boot.  The one you should use is based on the img file you used to write to the TCRP USB flash drive:

 

tinycore-redpill.vX.X.X.img.gz                    (for BIOS/CSM/Legacy boot from USB flash drive)
tinycore-redpill-uefi.vX.X.X.img.gz            (for UEFI/EFI boot from USB flash drive)
tinycore-redpill.vX.X.X.vmdk.gz                 (for hypervisor VM boot from disk image)

 

If you used the first one, you should pick A-DATA USB Flash Drive 0.00 (2.00GB) from the BIOS

 

18 minutes ago, wessu said:

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.

 

This says your motherboard maps 10 devices, not 8.  Apparently you just now tried to rebuild the loader with these values.  Please launch the TCRP console again and post:

 

cat /proc/cmdline

ls -la /sys/block

ls -la /sys/class/ata_device

 

Also, please confirm exactly which ports the drives are connected to.

 

It may be that your controllers are showing ports that aren't actually connected to hardware, which is a weird problem but it has been encountered before.

[flyride]

3 minutes ago, wessu said:

Under BIOS>Advanced>SATA Configuration

I get only SATA 1-8 and 2 NVMEs. Is it possible that those two NVMEs are causing 7,8 errors in the previous picture?

 

Possibly.  Maybe screenshot that.  Sometimes a M.2 port can be either a SATA SSD or NVMe SSD depending on BIOS.  If you don't have any SATA M.2 SSD's, they should be disabled probably.

[wessu]

22 minutes ago, flyride said:

 

Your motherboard supports UEFI boot and CSM boot.  The one you should use is based on the img file you used to write to the TCRP USB flash drive:

 

tinycore-redpill.vX.X.X.img.gz                    (for BIOS/CSM/Legacy boot from USB flash drive)
tinycore-redpill-uefi.vX.X.X.img.gz            (for UEFI/EFI boot from USB flash drive)
tinycore-redpill.vX.X.X.vmdk.gz                 (for hypervisor VM boot from disk image)

 

If you used the first one, you should pick A-DATA USB Flash Drive 0.00 (2.00GB) from the BIOS

 

 

This says your motherboard maps 10 devices, not 8.  Apparently you just now tried to rebuild the loader with these values.  Please launch the TCRP console again and post:

 

cat /proc/cmdline

ls -la /sys/block

ls -la /sys/class/ata_device

 

Also, please confirm exactly which ports the drives are connected to.

 

It may be that your controllers are showing ports that aren't actually connected to hardware, which is a weird problem but it has been encountered before.

 

I used tinycore-redpill-main.zip

Extracted it and got tinycore-redpill.v0.4.6.img and I burned it using Rufus. Maybe that's why I got both. I tried with either one and I still got 7,8 errors in installation page.

 

Here is the output:

SynologyNAS> cat /proc/cmdline
BOOT_IMAGE=/zImage withefi syno_hw_version=DS3622xs+ console=ttyS0,115200n8 netif_num=5 earlycon=uart8250,io,0x3f8,115200n8 mac1=001132E0E1AC sn=2150SQRC31KAY HddHotplug=0 DiskIdxMap=0004 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=0 root=/dev/md0 SataPortMap=46
SynologyNAS> ls -la /sys/block
drwxr-xr-x    2 root     root             0 May 26 01:55 .
dr-xr-xr-x   12 root     root             0 May 26 01:55 ..
lrwxrwxrwx    1 root     root             0 May 26 01:55 nvme0n1 -> ../devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1
lrwxrwxrwx    1 root     root             0 May 26 01:59 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx    1 root     root             0 May 26 01:59 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx    1 root     root             0 May 26 01:59 ram10 -> ../devices/virtual/block/ram10
lrwxrwxrwx    1 root     root             0 May 26 01:59 ram11 -> ../devices/virtual/block/ram11
lrwxrwxrwx    1 root     root             0 May 26 01:59 ram12 -> ../devices/virtual/block/ram12
lrwxrwxrwx    1 root     root             0 May 26 01:59 ram13 -> ../devices/virtual/block/ram13
lrwxrwxrwx    1 root     root             0 May 26 01:59 ram14 -> ../devices/virtual/block/ram14
lrwxrwxrwx    1 root     root             0 May 26 01:59 ram15 -> ../devices/virtual/block/ram15
lrwxrwxrwx    1 root     root             0 May 26 01:59 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx    1 root     root             0 May 26 01:59 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx    1 root     root             0 May 26 01:59 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx    1 root     root             0 May 26 01:59 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx    1 root     root             0 May 26 01:59 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx    1 root     root             0 May 26 01:59 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx    1 root     root             0 May 26 01:59 ram8 -> ../devices/virtual/block/ram8
lrwxrwxrwx    1 root     root             0 May 26 01:59 ram9 -> ../devices/virtual/block/ram9
lrwxrwxrwx    1 root     root             0 May 26 01:55 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:55 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:55 sdi -> ../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/sdi
lrwxrwxrwx    1 root     root             0 May 26 01:55 sdj -> ../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/sdj
lrwxrwxrwx    1 root     root             0 May 26 01:59 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/host10/target10:0:0/10:0:0:0/block/synoboot
SynologyNAS> ls -la /sys/class/ata_device
drwxr-xr-x    2 root     root             0 May 26 02:00 .
drwxr-xr-x   54 root     root             0 May 26 01:55 ..
lrwxrwxrwx    1 root     root             0 May 26 02:00 dev1.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:0a:00.0/ata1/link1/dev1.0/ata_device/dev1.0
lrwxrwxrwx    1 root     root             0 May 26 02:00 dev10.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata10/link10/dev10.0/ata_device/dev10.0
lrwxrwxrwx    1 root     root             0 May 26 02:00 dev2.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:0a:00.0/ata2/link2/dev2.0/ata_device/dev2.0
lrwxrwxrwx    1 root     root             0 May 26 02:00 dev3.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:0a:00.0/ata3/link3/dev3.0/ata_device/dev3.0
lrwxrwxrwx    1 root     root             0 May 26 02:00 dev4.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:0a:00.0/ata4/link4/dev4.0/ata_device/dev4.0
lrwxrwxrwx    1 root     root             0 May 26 02:00 dev5.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata5/link5/dev5.0/ata_device/dev5.0
lrwxrwxrwx    1 root     root             0 May 26 02:00 dev6.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata6/link6/dev6.0/ata_device/dev6.0
lrwxrwxrwx    1 root     root             0 May 26 02:00 dev7.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata7/link7/dev7.0/ata_device/dev7.0
lrwxrwxrwx    1 root     root             0 May 26 02:00 dev8.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata8/link8/dev8.0/ata_device/dev8.0
lrwxrwxrwx    1 root     root             0 May 26 02:00 dev9.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata9/link9/dev9.0/ata_device/dev9.0
SynologyNAS>

 

 

Here is what my motherboards shows:

SATA6G_1 = CT1000MX500SSD1
SATA6G_2 = ST9750423AS
SATA6G_3 = SAMSUNG HD103SJ
SATA6G_4 = SanDisk Ultra II 480GB
SATA6G_5 = Not Present
SATA6G_6 = Not Present
SATA6G_7 = Not Present
SATA6G_8 = Not Present
M.2_1 = Windows Boot NVME Drive (Sabrent Rocket 4.0 1TB)
M.2_2 = Not Present

 

Attached are screenshots

 

 

 

 

output.txt

Edited May 26, 2022 by wessu
typos

[flyride]

This board reverses the disk connections to each controller versus what is reported in the BIOS.

 

0000:03:09.0/0000:0a:00.0 - this is your first enumerated controller, with 4 ports

0000:03:0a.0/0000:0b:00.0 - this is your second enumerated controller, with 6 ports (not sure why it has two extra still)

 

The BIOS calls disk 1 the first port on the second controller.  So this is defeating any reasonable algorithm to detect this correctly.

You happened upon a partial solution with previous values on the first DS3622xs+ install, but it would not have allowed you to use all your ports.

 

Now it's trial and error until it can be figured out.  I would try two things:

 

1. Reverse the DiskIdxMap settings - (i.e. instead of 0004 change to 0600)

This is easiest and has a good chance of working.

 

2. Move your disks to the places that are actually being presented.  I assume that would be ports 5,6,7,8 on your motherboard.

This is most "techically correct" if that matters to you.

 

We might still have errors on the last two ports, but this will get it closer.

 

Sorry but sometimes hardware manufacturers do weird stuff.  Let me know how it goes.

[wessu]

Interesting finding. In my attempt to install DSM I started cutting the number of available disks to try to force it to work and it did but then I lose access to other disks. I will try those solutions you recommended tonight and report back. Looking at the technical specs of the motherboard, it has 8 SATA physical ports on the board. The specs report that NVME will work as a SATA. Since there are 2 NVME slots then that should get the total number to 10.

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

 

[IG-88]

17 hours ago, wessu said:

Is there a difference if you select a UEFI boot vs CSM boot for tinyCore?

in general, to use CSM you would need to select the non uefi usb boot device (in your case "A-DATA USB Flash Drive") , csm is just an option and if you use a uefi boot device the csm option is not used

[wessu]

8 hours ago, flyride said:

1. Reverse the DiskIdxMap settings - (i.e. instead of 0004 change to 0600)

This is easiest and has a good chance of working.

 

 

So I made the first controller 6 instead of 4 and made the second controller 4 instead of 6 (reversed them).

See the screenshot for errors. Here is output:

 

SynologyNAS>  cat /proc/cmdline
BOOT_IMAGE=/zImage withefi syno_hw_version=DS3622xs+ console=ttyS0,115200n8 netif_num=5 earlycon=uart8250,io,0x3f8,115200n8 mac1=00113214A042 sn=2040SQRW7L4RA HddHotplug=0 DiskIdxMap=0006 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=0 root=/dev/md0 SataPortMap=64
SynologyNAS>  ls -la /sys/block
drwxr-xr-x    2 root     root             0 May 27 01:07 .
dr-xr-xr-x   12 root     root             0 May 27 01:07 ..
lrwxrwxrwx    1 root     root             0 May 27 01:07 nvme0n1 -> ../devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1
lrwxrwxrwx    1 root     root             0 May 27 01:10 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx    1 root     root             0 May 27 01:10 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx    1 root     root             0 May 27 01:10 ram10 -> ../devices/virtual/block/ram10
lrwxrwxrwx    1 root     root             0 May 27 01:10 ram11 -> ../devices/virtual/block/ram11
lrwxrwxrwx    1 root     root             0 May 27 01:10 ram12 -> ../devices/virtual/block/ram12
lrwxrwxrwx    1 root     root             0 May 27 01:10 ram13 -> ../devices/virtual/block/ram13
lrwxrwxrwx    1 root     root             0 May 27 01:10 ram14 -> ../devices/virtual/block/ram14
lrwxrwxrwx    1 root     root             0 May 27 01:10 ram15 -> ../devices/virtual/block/ram15
lrwxrwxrwx    1 root     root             0 May 27 01:10 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx    1 root     root             0 May 27 01:10 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx    1 root     root             0 May 27 01:10 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx    1 root     root             0 May 27 01:10 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx    1 root     root             0 May 27 01:10 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx    1 root     root             0 May 27 01:10 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx    1 root     root             0 May 27 01:10 ram8 -> ../devices/virtual/block/ram8
lrwxrwxrwx    1 root     root             0 May 27 01:10 ram9 -> ../devices/virtual/block/ram9
lrwxrwxrwx    1 root     root             0 May 27 01:07 sdg -> ../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sdg
lrwxrwxrwx    1 root     root             0 May 27 01:07 sdh -> ../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata8/host7/target7:0:0/7:0:0:0/block/sdh
lrwxrwxrwx    1 root     root             0 May 27 01:10 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/host10/target10:0:0/10:0:0:0/block/synoboot
SynologyNAS>  ls -la /sys/class/ata_device
drwxr-xr-x    2 root     root             0 May 27 01:10 .
drwxr-xr-x   54 root     root             0 May 27 01:07 ..
lrwxrwxrwx    1 root     root             0 May 27 01:10 dev1.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:0a:00.0/ata1/link1/dev1.0/ata_device/dev1.0
lrwxrwxrwx    1 root     root             0 May 27 01:10 dev10.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata10/link10/dev10.0/ata_device/dev10.0
lrwxrwxrwx    1 root     root             0 May 27 01:10 dev2.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:0a:00.0/ata2/link2/dev2.0/ata_device/dev2.0
lrwxrwxrwx    1 root     root             0 May 27 01:10 dev3.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:0a:00.0/ata3/link3/dev3.0/ata_device/dev3.0
lrwxrwxrwx    1 root     root             0 May 27 01:10 dev4.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:0a:00.0/ata4/link4/dev4.0/ata_device/dev4.0
lrwxrwxrwx    1 root     root             0 May 27 01:10 dev5.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:0a:00.0/ata5/link5/dev5.0/ata_device/dev5.0
lrwxrwxrwx    1 root     root             0 May 27 01:10 dev6.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:0a:00.0/ata6/link6/dev6.0/ata_device/dev6.0
lrwxrwxrwx    1 root     root             0 May 27 01:10 dev7.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata7/link7/dev7.0/ata_device/dev7.0
lrwxrwxrwx    1 root     root             0 May 27 01:10 dev8.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata8/link8/dev8.0/ata_device/dev8.0
lrwxrwxrwx    1 root     root             0 May 27 01:10 dev9.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata9/link9/dev9.0/ata_device/dev9.0
SynologyNAS>

[flyride]

24 minutes ago, wessu said:

So I made the first controller 6 instead of 4 and made the second controller 4 instead of 6 (reversed them).

See the screenshot for errors. Here is output:

 

SynologyNAS>  cat /proc/cmdline
BOOT_IMAGE=/zImage withefi syno_hw_version=DS3622xs+ console=ttyS0,115200n8 netif_num=5 earlycon=uart8250,io,0x3f8,115200n8 mac1=00113214A042 sn=2040SQRW7L4RA HddHotplug=0 DiskIdxMap=0006 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=0 root=/dev/md0 SataPortMap=64

 

Unfortunately that wasn't what we needed to do.  Just changing the answers to ./rploader satamap now won't solve this.

You need to manually edit user_config.json.  As I said before DiskIdxMap=0600 (and SataPortMap=46 stays the same).

[wessu]

8 minutes ago, flyride said:

 

Unfortunately that wasn't what we needed to do.  Just changing the answers to ./rploader satamap now won't solve this.

You need to manually edit user_config.json.  As I said before DiskIdxMap=0600 (and SataPortMap=46 stays the same).

 

I will work on this later.

In the mean time, I removed my NVME drive in slot 1. It did not change anything.

I flipped the SATA disks to port 5,6,7,8 on the motherboard. I ended up with the same error message. Here is the output. I will do what you have suggested after I come back from the gym and post.

 

BOOT_IMAGE=/zImage withefi syno_hw_version=DS3622xs+ console=ttyS0,115200n8 netif_num=5 earlycon=uart8250,io,0x3f8,115200n8 mac1=00113267126E sn=2030SQRQYM5GK HddHotplug=0 DiskIdxMap=0004 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=0 root=/dev/md0 SataPortMap=46
SynologyNAS>  ls -la /sys/block
drwxr-xr-x    2 root     root             0 May 27 01:43 .
dr-xr-xr-x   12 root     root             0 May 27 01:43 ..
lrwxrwxrwx    1 root     root             0 May 27 01:45 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx    1 root     root             0 May 27 01:45 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx    1 root     root             0 May 27 01:45 ram10 -> ../devices/virtual/block/ram10
lrwxrwxrwx    1 root     root             0 May 27 01:45 ram11 -> ../devices/virtual/block/ram11
lrwxrwxrwx    1 root     root             0 May 27 01:45 ram12 -> ../devices/virtual/block/ram12
lrwxrwxrwx    1 root     root             0 May 27 01:45 ram13 -> ../devices/virtual/block/ram13
lrwxrwxrwx    1 root     root             0 May 27 01:45 ram14 -> ../devices/virtual/block/ram14
lrwxrwxrwx    1 root     root             0 May 27 01:45 ram15 -> ../devices/virtual/block/ram15
lrwxrwxrwx    1 root     root             0 May 27 01:45 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx    1 root     root             0 May 27 01:45 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx    1 root     root             0 May 27 01:45 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx    1 root     root             0 May 27 01:45 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx    1 root     root             0 May 27 01:45 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx    1 root     root             0 May 27 01:45 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx    1 root     root             0 May 27 01:45 ram8 -> ../devices/virtual/block/ram8
lrwxrwxrwx    1 root     root             0 May 27 01:45 ram9 -> ../devices/virtual/block/ram9
lrwxrwxrwx    1 root     root             0 May 27 01:43 sda -> ../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:09.0/0000:06:00.0/ata1/host0/target0:0:0/0:0:0:0/block/sda
lrwxrwxrwx    1 root     root             0 May 27 01:43 sdb -> ../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:09.0/0000:06:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdb
lrwxrwxrwx    1 root     root             0 May 27 01:43 sdc -> ../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:09.0/0000:06:00.0/ata3/host2/target2:0:0/2:0:0:0/block/sdc
lrwxrwxrwx    1 root     root             0 May 27 01:43 sdd -> ../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:09.0/0000:06:00.0/ata4/host3/target3:0:0/3:0:0:0/block/sdd
lrwxrwxrwx    1 root     root             0 May 27 01:45 synoboot -> ../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:05:00.1/usb1/1-4/1-4:1.0/host10/target10:0:0/10:0:0:0/block/synoboot
SynologyNAS>  ls -la /sys/class/ata_device
drwxr-xr-x    2 root     root             0 May 27 01:45 .
drwxr-xr-x   54 root     root             0 May 27 01:43 ..
lrwxrwxrwx    1 root     root             0 May 27 01:45 dev1.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:09.0/0000:06:00.0/ata1/link1/dev1.0/ata_device/dev1.0
lrwxrwxrwx    1 root     root             0 May 27 01:45 dev10.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:0a.0/0000:07:00.0/ata10/link10/dev10.0/ata_device/dev10.0
lrwxrwxrwx    1 root     root             0 May 27 01:45 dev2.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:09.0/0000:06:00.0/ata2/link2/dev2.0/ata_device/dev2.0
lrwxrwxrwx    1 root     root             0 May 27 01:45 dev3.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:09.0/0000:06:00.0/ata3/link3/dev3.0/ata_device/dev3.0
lrwxrwxrwx    1 root     root             0 May 27 01:45 dev4.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:09.0/0000:06:00.0/ata4/link4/dev4.0/ata_device/dev4.0
lrwxrwxrwx    1 root     root             0 May 27 01:45 dev5.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:0a.0/0000:07:00.0/ata5/link5/dev5.0/ata_device/dev5.0
lrwxrwxrwx    1 root     root             0 May 27 01:45 dev6.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:0a.0/0000:07:00.0/ata6/link6/dev6.0/ata_device/dev6.0
lrwxrwxrwx    1 root     root             0 May 27 01:45 dev7.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:0a.0/0000:07:00.0/ata7/link7/dev7.0/ata_device/dev7.0
lrwxrwxrwx    1 root     root             0 May 27 01:45 dev8.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:0a.0/0000:07:00.0/ata8/link8/dev8.0/ata_device/dev8.0
lrwxrwxrwx    1 root     root             0 May 27 01:45 dev9.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:0a.0/0000:07:00.0/ata9/link9/dev9.0/ata_device/dev9.0
SynologyNAS>

[flyride]

23 hours ago, wessu said:

SATA6G_1 = CT1000MX500SSD1
SATA6G_2 = ST9750423AS
SATA6G_3 = SAMSUNG HD103SJ
SATA6G_4 = SanDisk Ultra II 480GB
SATA6G_5 = Not Present
SATA6G_6 = Not Present
SATA6G_7 = Not Present
SATA6G_8 = Not Present
M.2_1 = Windows Boot NVME Drive (Sabrent Rocket 4.0 1TB)
M.2_2 = Not Present

 

 

M.2_1 = Windows Boot NVME Drive (Sabrent Rocket 4.0 1TB)

Why would this be in the system?  It doesn't appear to be present based on the screenshot above.  Do you intend to leave the NVMe slots empty?

 

It also looks like in the screenshot that the menu can be expanded for M.2_1 and M.2_2.  If those ports have a SATA or NVMe option, please change to NVMe.

[wessu]

3 hours ago, flyride said:

 

Unfortunately that wasn't what we needed to do.  Just changing the answers to ./rploader satamap now won't solve this.

You need to manually edit user_config.json.  As I said before DiskIdxMap=0600 (and SataPortMap=46 stays the same).

 

Okay, I just did that. I'm getting disks 3,4 error now instead of 7&8. See attached screenshot.

 

Here is the output:

 

Spoiler

SynologyNAS> cat /proc/cmdline
BOOT_IMAGE=/zImage withefi syno_hw_version=DS3622xs+ console=ttyS0,115200n8 netif_num=5 earlycon=uart8250,io,0x3f8,115200n8 mac1=001132C4A96E sn=20C0SQRPN3FRL HddHotplug=0 DiskIdxMap=0600 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=0 root=/dev/md0 SataPortMap=46
SynologyNAS>  ls -la /sys/block
drwxr-xr-x    2 root     root             0 May 27 04:38 .
dr-xr-xr-x   12 root     root             0 May 27 04:38 ..
lrwxrwxrwx    1 root     root             0 May 27 04:43 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx    1 root     root             0 May 27 04:43 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx    1 root     root             0 May 27 04:43 ram10 -> ../devices/virtual/block/ram10
lrwxrwxrwx    1 root     root             0 May 27 04:43 ram11 -> ../devices/virtual/block/ram11
lrwxrwxrwx    1 root     root             0 May 27 04:43 ram12 -> ../devices/virtual/block/ram12
lrwxrwxrwx    1 root     root             0 May 27 04:43 ram13 -> ../devices/virtual/block/ram13
lrwxrwxrwx    1 root     root             0 May 27 04:43 ram14 -> ../devices/virtual/block/ram14
lrwxrwxrwx    1 root     root             0 May 27 04:43 ram15 -> ../devices/virtual/block/ram15
lrwxrwxrwx    1 root     root             0 May 27 04:43 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx    1 root     root             0 May 27 04:43 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx    1 root     root             0 May 27 04:43 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx    1 root     root             0 May 27 04:43 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx    1 root     root             0 May 27 04:43 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx    1 root     root             0 May 27 04:43 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx    1 root     root             0 May 27 04:43 ram8 -> ../devices/virtual/block/ram8
lrwxrwxrwx    1 root     root             0 May 27 04:43 ram9 -> ../devices/virtual/block/ram9
lrwxrwxrwx    1 root     root             0 May 27 04:38 sdg -> ../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:09.0/0000:06:00.0/ata1/host0/target0:0:0/0:0:0:0/block/sdg
lrwxrwxrwx    1 root     root             0 May 27 04:38 sdh -> ../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:09.0/0000:06:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdh
lrwxrwxrwx    1 root     root             0 May 27 04:38 sdi -> ../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:09.0/0000:06:00.0/ata3/host2/target2:0:0/2:0:0:0/block/sdi
lrwxrwxrwx    1 root     root             0 May 27 04:38 sdj -> ../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:09.0/0000:06:00.0/ata4/host3/target3:0:0/3:0:0:0/block/sdj
lrwxrwxrwx    1 root     root             0 May 27 04:43 synoboot -> ../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:05:00.1/usb1/1-4/1-4:1.0/host10/target10:0:0/10:0:0:0/block/synoboot
SynologyNAS>  ls -la /sys/class/ata_device
drwxr-xr-x    2 root     root             0 May 27 04:43 .
drwxr-xr-x   54 root     root             0 May 27 04:38 ..
lrwxrwxrwx    1 root     root             0 May 27 04:43 dev1.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:09.0/0000:06:00.0/ata1/link1/dev1.0/ata_device/dev1.0
lrwxrwxrwx    1 root     root             0 May 27 04:43 dev10.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:0a.0/0000:07:00.0/ata10/link10/dev10.0/ata_device/dev10.0
lrwxrwxrwx    1 root     root             0 May 27 04:43 dev2.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:09.0/0000:06:00.0/ata2/link2/dev2.0/ata_device/dev2.0
lrwxrwxrwx    1 root     root             0 May 27 04:43 dev3.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:09.0/0000:06:00.0/ata3/link3/dev3.0/ata_device/dev3.0
lrwxrwxrwx    1 root     root             0 May 27 04:43 dev4.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:09.0/0000:06:00.0/ata4/link4/dev4.0/ata_device/dev4.0
lrwxrwxrwx    1 root     root             0 May 27 04:43 dev5.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:0a.0/0000:07:00.0/ata5/link5/dev5.0/ata_device/dev5.0
lrwxrwxrwx    1 root     root             0 May 27 04:43 dev6.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:0a.0/0000:07:00.0/ata6/link6/dev6.0/ata_device/dev6.0
lrwxrwxrwx    1 root     root             0 May 27 04:43 dev7.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:0a.0/0000:07:00.0/ata7/link7/dev7.0/ata_device/dev7.0
lrwxrwxrwx    1 root     root             0 May 27 04:43 dev8.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:0a.0/0000:07:00.0/ata8/link8/dev8.0/ata_device/dev8.0
lrwxrwxrwx    1 root     root             0 May 27 04:43 dev9.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:0a.0/0000:07:00.0/ata9/link9/dev9.0/ata_device/dev9.0
SynologyNAS>

Edited May 27, 2022 by wessu

[wessu]

2 hours ago, flyride said:

 

M.2_1 = Windows Boot NVME Drive (Sabrent Rocket 4.0 1TB)

Why would this be in the system?  It doesn't appear to be present based on the screenshot above.  Do you intend to leave the NVMe slots empty?

 

It also looks like in the screenshot that the menu can be expanded for M.2_1 and M.2_2.  If those ports have a SATA or NVMe option, please change to NVMe.

 

I am using my desktop PC to tinker with the installation and try DSM. That NVME holds my Windows files (C Drive). I thought to remove it and see if it makes any difference but it is not. I will put it back. I don't plan to use it inside DSM at all.

When you try to expand the NVME option in the BIOS you can just rename it. No other options are available. Not sure why it doesn't show in this menu though. But it was there in the other menus.

[flyride]

1 hour ago, wessu said:

Okay, I just did that. I'm getting disks 3,4 error now instead of 7&8. See attached screenshot.

 

Here is the output:

But you left the disks on motherboard ports 5,6,7,8?

[wessu]

Somehow, it seems that it doesn't matter which ports are the drives connected to.

I put the disks back to the original ports 1-4. I still got the same error message.

Spoiler

SynologyNAS> cat /proc/cmdline
BOOT_IMAGE=/zImage withefi syno_hw_version=DS3622xs+ console=ttyS0,115200n8 netif_num=5 earlycon=uart8250,io,0x3f8,115200n8 mac1=001132C4A96E sn=20C0SQRPN3FRL HddHotplug=0 DiskIdxMap=0600 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=0 root=/dev/md0 SataPortMap=46
SynologyNAS>  ls -la /sys/block
drwxr-xr-x    2 root     root             0 May 27 13:30 .
dr-xr-xr-x   12 root     root             0 May 27 13:30 ..
lrwxrwxrwx    1 root     root             0 May 27 13:30 nvme0n1 -> ../devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1
lrwxrwxrwx    1 root     root             0 May 27 13:33 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx    1 root     root             0 May 27 13:33 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx    1 root     root             0 May 27 13:33 ram10 -> ../devices/virtual/block/ram10
lrwxrwxrwx    1 root     root             0 May 27 13:33 ram11 -> ../devices/virtual/block/ram11
lrwxrwxrwx    1 root     root             0 May 27 13:33 ram12 -> ../devices/virtual/block/ram12
lrwxrwxrwx    1 root     root             0 May 27 13:33 ram13 -> ../devices/virtual/block/ram13
lrwxrwxrwx    1 root     root             0 May 27 13:33 ram14 -> ../devices/virtual/block/ram14
lrwxrwxrwx    1 root     root             0 May 27 13:33 ram15 -> ../devices/virtual/block/ram15
lrwxrwxrwx    1 root     root             0 May 27 13:33 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx    1 root     root             0 May 27 13:33 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx    1 root     root             0 May 27 13:33 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx    1 root     root             0 May 27 13:33 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx    1 root     root             0 May 27 13:33 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx    1 root     root             0 May 27 13:33 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx    1 root     root             0 May 27 13:33 ram8 -> ../devices/virtual/block/ram8
lrwxrwxrwx    1 root     root             0 May 27 13:33 ram9 -> ../devices/virtual/block/ram9
lrwxrwxrwx    1 root     root             0 May 27 13:30 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 27 13:30 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 27 13:30 sde -> ../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/sde
lrwxrwxrwx    1 root     root             0 May 27 13:30 sdf -> ../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/sdf
lrwxrwxrwx    1 root     root             0 May 27 13:33 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/host10/target10:0:0/10:0:0:0/block/synoboot
SynologyNAS>  ls -la /sys/class/ata_device
drwxr-xr-x    2 root     root             0 May 27 13:34 .
drwxr-xr-x   54 root     root             0 May 27 13:30 ..
lrwxrwxrwx    1 root     root             0 May 27 13:34 dev1.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:0a:00.0/ata1/link1/dev1.0/ata_device/dev1.0
lrwxrwxrwx    1 root     root             0 May 27 13:34 dev10.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata10/link10/dev10.0/ata_device/dev10.0
lrwxrwxrwx    1 root     root             0 May 27 13:34 dev2.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:0a:00.0/ata2/link2/dev2.0/ata_device/dev2.0
lrwxrwxrwx    1 root     root             0 May 27 13:34 dev3.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:0a:00.0/ata3/link3/dev3.0/ata_device/dev3.0
lrwxrwxrwx    1 root     root             0 May 27 13:34 dev4.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:0a:00.0/ata4/link4/dev4.0/ata_device/dev4.0
lrwxrwxrwx    1 root     root             0 May 27 13:34 dev5.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata5/link5/dev5.0/ata_device/dev5.0
lrwxrwxrwx    1 root     root             0 May 27 13:34 dev6.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata6/link6/dev6.0/ata_device/dev6.0
lrwxrwxrwx    1 root     root             0 May 27 13:34 dev7.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata7/link7/dev7.0/ata_device/dev7.0
lrwxrwxrwx    1 root     root             0 May 27 13:34 dev8.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata8/link8/dev8.0/ata_device/dev8.0
lrwxrwxrwx    1 root     root             0 May 27 13:34 dev9.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:0b:00.0/ata9/link9/dev9.0/ata_device/dev9.0
SynologyNAS>

 

[flyride]

I know it seems like we have been just trying things randomly, but let's summarize what we have managed to observe:

• Your motherboard exposes its SATA ports from controllers using two different PCI slot addresses
• As presented to Linux, the high-ordered (second) controller controls the first four ports
• The low-ordered controller (first) controller controls the second four ports, plus two more phantom ports which might be the M.2 slots when in SATA mode
• The M.2 SATA mode slots seem to be placed in the middle of the range and might be the cause of the "bad port" message
• Somehow the PCI slot addresses of the controllers can change
  • sometimes your low ordered controller is this 0000:03:09.0/0000:0a:00.0 and other times it is 0000:02:09.0/0000:06:00.0
  • sometimes your high ordered controller is this 0000:03:0a.0/0000:0b:00.0 and other times it is 0000:02:0a.0/0000:07:00.0

That last behavior is very strange, as it appears that the system and chipset are dynamically assigning PCI slot resources based on BIOS settings. It also suggests that you made some other change that resulted in that effect - moving drives around would not be a cause.  The slot addresses changing technically shouldn't matter, but it is unusual.

 

The next few things I would try are:

 

1. BIOS disable all unpopulated disk slots and see if you get a different result.  Please note that different result doesn't mean it installs, so don't gloss over details. For example you say you see the same error message, but does that mean the same ports were disabled?

 

2. Populate both NVMe slots with blank NVMe drives and see if the phantom slots disappear (skip this if you don't have any suitable devices).

 

3. Drop the ports on the second controller down to 2 (that would give you 6 usable ports in total).

In other words, try SataPortMap=42 and DiskIdxMap=0200.  That also means you would need to put two disks on ports 5,6 and two disk on ports 1,2.  If that actually works, that might be the best solution with this board.  There is one other thought I have to try that might get the last two ports working, but I'll leave that to later.

[wessu]

I changed the BIOS settings to disable CSM and only kept UEFI to boot devices. Maybe that caused the strange behavior. I don't have currently a spare NMVE laying around but I will in 2-3 weeks. I will try the option to populate both and see if anything changes. One thing I can think of is that those bad ports if eliminated would stop this message, regardless of the population of the hard drives. Nevertheless, I will work structurally on the points you presented and report my findings back. I really appreciate all the work you do.

[wessu]

11 hours ago, flyride said:

 

1. BIOS disable all unpopulated disk slots and see if you get a different result.  Please note that different result doesn't mean it installs, so don't gloss over details. For example you say you see the same error message, but does that mean the same ports were disabled?

 

 

 

By disabling, do you mean disabling HOT PLUG feature for disconnected driver? That's the only way I can disable them based on what I can find in my BIOS.

[flyride]

No, I misunderstood the screencap - I thought you could disable the port itself.  Never mind that then.  So for now, you want to try option 3:

-Drop the ports on the second controller down to 2 (that would give you 6 usable ports in total).

 

Also another trial and error option, as you are doing a baremetal install, you may be able to try a null SataPortMap and DiskIdxMap, but I think you'll have the same problem with the M.2 ports.  You can delete the lines from user_config.json altogether, or just delete the numeric values from between the quotes.

[wessu]

53 minutes ago, flyride said:

No, I misunderstood the screencap - I thought you could disable the port itself.  Never mind that then.  So for now, you want to try option 3:

-Drop the ports on the second controller down to 2 (that would give you 6 usable ports in total).

It worked! I kept drives on port 1,2 and 5,6 on the motherboard. Anything else I can test

 

Here is the output:

 

Spoiler

SynologyNAS>  cat /proc/cmdline
BOOT_IMAGE=/zImage withefi syno_hw_version=DS3622xs+ console=ttyS0,115200n8 netif_num=5 earlycon=uart8250,io,0x3f8,115200n8 mac1=001132E1EB5D sn=20C0SQRTGW3KG HddHotplug=0 DiskIdxMap=0200 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=0 root=/dev/md0 SataPortMap=42
SynologyNAS>  ls -la /sys/block
drwxr-xr-x    2 root     root             0 May 28 02:15 .
dr-xr-xr-x   12 root     root             0 May 28 02:15 ..
lrwxrwxrwx    1 root     root             0 May 28 02:15 nvme0n1 -> ../devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1
lrwxrwxrwx    1 root     root             0 May 28 02:16 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx    1 root     root             0 May 28 02:16 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx    1 root     root             0 May 28 02:16 ram10 -> ../devices/virtual/block/ram10
lrwxrwxrwx    1 root     root             0 May 28 02:16 ram11 -> ../devices/virtual/block/ram11
lrwxrwxrwx    1 root     root             0 May 28 02:16 ram12 -> ../devices/virtual/block/ram12
lrwxrwxrwx    1 root     root             0 May 28 02:16 ram13 -> ../devices/virtual/block/ram13
lrwxrwxrwx    1 root     root             0 May 28 02:16 ram14 -> ../devices/virtual/block/ram14
lrwxrwxrwx    1 root     root             0 May 28 02:16 ram15 -> ../devices/virtual/block/ram15
lrwxrwxrwx    1 root     root             0 May 28 02:16 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx    1 root     root             0 May 28 02:16 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx    1 root     root             0 May 28 02:16 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx    1 root     root             0 May 28 02:16 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx    1 root     root             0 May 28 02:16 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx    1 root     root             0 May 28 02:16 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx    1 root     root             0 May 28 02:16 ram8 -> ../devices/virtual/block/ram8
lrwxrwxrwx    1 root     root             0 May 28 02:16 ram9 -> ../devices/virtual/block/ram9
lrwxrwxrwx    1 root     root             0 May 28 02:15 sda -> ../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata5/host4/target4:0:0/4:0:0:0/block/sda
lrwxrwxrwx    1 root     root             0 May 28 02:15 sdb -> ../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata6/host5/target5:0:0/5:0:0:0/block/sdb
lrwxrwxrwx    1 root     root             0 May 28 02:15 sde -> ../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata3/host2/target2:0:0/2:0:0:0/block/sde
lrwxrwxrwx    1 root     root             0 May 28 02:15 sdf -> ../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata4/host3/target3:0:0/3:0:0:0/block/sdf
lrwxrwxrwx    1 root     root             0 May 28 02:16 synoboot -> ../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.1/usb1/1-4/1-4:1.0/host6/target6:0:0/6:0:0:0/block/synoboot
SynologyNAS>  ls -la /sys/class/ata_device
drwxr-xr-x    2 root     root             0 May 28 02:17 .
drwxr-xr-x   54 root     root             0 May 28 02:15 ..
lrwxrwxrwx    1 root     root             0 May 28 02:17 dev1.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata1/link1/dev1.0/ata_device/dev1.0
lrwxrwxrwx    1 root     root             0 May 28 02:17 dev2.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata2/link2/dev2.0/ata_device/dev2.0
lrwxrwxrwx    1 root     root             0 May 28 02:17 dev3.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata3/link3/dev3.0/ata_device/dev3.0
lrwxrwxrwx    1 root     root             0 May 28 02:17 dev4.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata4/link4/dev4.0/ata_device/dev4.0
lrwxrwxrwx    1 root     root             0 May 28 02:17 dev5.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata5/link5/dev5.0/ata_device/dev5.0
lrwxrwxrwx    1 root     root             0 May 28 02:17 dev6.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata6/link6/dev6.0/ata_device/dev6.0
SynologyNAS>

 

[flyride]

I think you've helped me out a ton.  It's unfortunate that board isn't simple as it is a decent platform with 8 real SATA ports.  Go install and enjoy DSM 7.

[wessu]

Sorry for this but it is not working again. Apparently I already had DSM installed on the HDD and it just let me login. I formatted the HDD to try to install it again and it is throwing the same error message about drive 3,4. I modified the serial/mac to see if I can get QuickConnect to work. Not sure if this makes a difference though.

Here is the output:

Spoiler

SynologyNAS>  cat /proc/cmdline
BOOT_IMAGE=/zImage withefi syno_hw_version=DS3622xs+ console=ttyS0,115200n8 netif_num=5 earlycon=uart8250,io,0x3f8,115200n8 mac1=0011324E15C5 sn=1590MQN594302 HddHotplug=0 DiskIdxMap=0200 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=0 root=/dev/md0 SataPortMap=46
SynologyNAS>  ls -la /sys/block
drwxr-xr-x    2 root     root             0 May 28 03:54 .
dr-xr-xr-x   12 root     root             0 May 28 03:54 ..
lrwxrwxrwx    1 root     root             0 May 28 03:54 nvme0n1 -> ../devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1
lrwxrwxrwx    1 root     root             0 May 28 03:57 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx    1 root     root             0 May 28 03:57 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx    1 root     root             0 May 28 03:57 ram10 -> ../devices/virtual/block/ram10
lrwxrwxrwx    1 root     root             0 May 28 03:57 ram11 -> ../devices/virtual/block/ram11
lrwxrwxrwx    1 root     root             0 May 28 03:57 ram12 -> ../devices/virtual/block/ram12
lrwxrwxrwx    1 root     root             0 May 28 03:57 ram13 -> ../devices/virtual/block/ram13
lrwxrwxrwx    1 root     root             0 May 28 03:57 ram14 -> ../devices/virtual/block/ram14
lrwxrwxrwx    1 root     root             0 May 28 03:57 ram15 -> ../devices/virtual/block/ram15
lrwxrwxrwx    1 root     root             0 May 28 03:57 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx    1 root     root             0 May 28 03:57 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx    1 root     root             0 May 28 03:57 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx    1 root     root             0 May 28 03:57 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx    1 root     root             0 May 28 03:57 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx    1 root     root             0 May 28 03:57 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx    1 root     root             0 May 28 03:57 ram8 -> ../devices/virtual/block/ram8
lrwxrwxrwx    1 root     root             0 May 28 03:57 ram9 -> ../devices/virtual/block/ram9
lrwxrwxrwx    1 root     root             0 May 28 03:54 sda -> ../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata5/host4/target4:0:0/4:0:0:0/block/sda
lrwxrwxrwx    1 root     root             0 May 28 03:54 sdb -> ../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata6/host5/target5:0:0/5:0:0:0/block/sdb
lrwxrwxrwx    1 root     root             0 May 28 03:54 sde -> ../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata3/host2/target2:0:0/2:0:0:0/block/sde
lrwxrwxrwx    1 root     root             0 May 28 03:54 sdf -> ../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata4/host3/target3:0:0/3:0:0:0/block/sdf
lrwxrwxrwx    1 root     root             0 May 28 03:57 synoboot -> ../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.1/usb1/1-4/1-4:1.0/host10/target10:0:0/10:0:0:0/block/synoboot
SynologyNAS>  ls -la /sys/class/ata_device
drwxr-xr-x    2 root     root             0 May 28 03:57 .
drwxr-xr-x   54 root     root             0 May 28 03:54 ..
lrwxrwxrwx    1 root     root             0 May 28 03:57 dev1.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata1/link1/dev1.0/ata_device/dev1.0
lrwxrwxrwx    1 root     root             0 May 28 03:57 dev10.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata10/link10/dev10.0/ata_device/dev10.0
lrwxrwxrwx    1 root     root             0 May 28 03:57 dev2.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata2/link2/dev2.0/ata_device/dev2.0
lrwxrwxrwx    1 root     root             0 May 28 03:57 dev3.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata3/link3/dev3.0/ata_device/dev3.0
lrwxrwxrwx    1 root     root             0 May 28 03:57 dev4.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata4/link4/dev4.0/ata_device/dev4.0
lrwxrwxrwx    1 root     root             0 May 28 03:57 dev5.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata5/link5/dev5.0/ata_device/dev5.0
lrwxrwxrwx    1 root     root             0 May 28 03:57 dev6.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata6/link6/dev6.0/ata_device/dev6.0
lrwxrwxrwx    1 root     root             0 May 28 03:57 dev7.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata7/link7/dev7.0/ata_device/dev7.0
lrwxrwxrwx    1 root     root             0 May 28 03:57 dev8.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata8/link8/dev8.0/ata_device/dev8.0
lrwxrwxrwx    1 root     root             0 May 28 03:57 dev9.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata9/link9/dev9.0/ata_device/dev9.0
SynologyNAS>

 

[Peter Suh]

@wessu

 

Has the DS1621+ build been abandoned?
Looks like @pocopico didn't give a concrete solution.
In the middle of the script related to build action,
patchdtc function is executed, this part must be blocked.
You can finish the normal build with just dtc ext of jumkey.

 

Download the rploader.sh that I modified below and try to build DS1621+ again.

 

tc@box:~$ curl --location "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/rploader.sh" --output rploader.sh

Edited May 28, 2022 by Peter Suh

[wessu]

6 hours ago, Peter Suh said:

@wessu

 

Has the DS1621+ build been abandoned?
Looks like @pocopico didn't give a concrete solution.
In the middle of the script related to build action,
patchdtc function is executed, this part must be blocked.
You can finish the normal build with just dtc ext of jumkey.

 

Download the rploader.sh that I modified below and try to build DS1621+ again.

 

tc@box:~$ curl --location "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/rploader.sh" --output rploader.sh

 

It worked!. I was able to boot and reach the installation screen. See attached screenshots. I got no drives available. I did not modify the parameters similar to what @flyride suggested before. I will try again now. In the mean time, here is the output

 

Spoiler

SynologyNAS>  cat /proc/cmdline
BOOT_IMAGE=/zImage syno_hw_version=DS1621+ console=ttyS0,115200n8 netif_num=1 synoboot2 earlycon=uart8250,io,0x3f8,115200n8 mac1=001132AFCAB7 sn=2080S7RKP86TK SMBusHddDynamicPower=1 DiskIdxMap=0004 vender_format_version=2 root=/dev/md0 SataPortMap=46 syno_ttyS1=serial,0x2f8 syno_ttyS0=serial,0x3f8
SynologyNAS>  ls -la /sys/block
drwxr-xr-x    2 root     root             0 May 28 18:55 .
dr-xr-xr-x   12 root     root             0 May 28 18:55 ..
lrwxrwxrwx    1 root     root             0 May 28 18:55 nvme0n1 -> ../devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1
lrwxrwxrwx    1 root     root             0 May 28 18:59 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx    1 root     root             0 May 28 18:59 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx    1 root     root             0 May 28 18:59 ram10 -> ../devices/virtual/block/ram10
lrwxrwxrwx    1 root     root             0 May 28 18:59 ram11 -> ../devices/virtual/block/ram11
lrwxrwxrwx    1 root     root             0 May 28 18:59 ram12 -> ../devices/virtual/block/ram12
lrwxrwxrwx    1 root     root             0 May 28 18:59 ram13 -> ../devices/virtual/block/ram13
lrwxrwxrwx    1 root     root             0 May 28 18:59 ram14 -> ../devices/virtual/block/ram14
lrwxrwxrwx    1 root     root             0 May 28 18:59 ram15 -> ../devices/virtual/block/ram15
lrwxrwxrwx    1 root     root             0 May 28 18:59 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx    1 root     root             0 May 28 18:59 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx    1 root     root             0 May 28 18:59 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx    1 root     root             0 May 28 18:59 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx    1 root     root             0 May 28 18:59 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx    1 root     root             0 May 28 18:59 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx    1 root     root             0 May 28 18:59 ram8 -> ../devices/virtual/block/ram8
lrwxrwxrwx    1 root     root             0 May 28 18:59 ram9 -> ../devices/virtual/block/ram9
lrwxrwxrwx    1 root     root             0 May 28 18:55 sata1 -> ../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata4/host3/target3:0:0/3:0:0:0/block/sata1
lrwxrwxrwx    1 root     root             0 May 28 18:59 synoboot -> ../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.1/usb1/1-4/1-4:1.0/host10/target10:0:0/10:0:0:0/block/synoboot
SynologyNAS>  ls -la /sys/class/ata_device
drwxr-xr-x    2 root     root             0 May 28 18:59 .
drwxr-xr-x   47 root     root             0 May 28 18:55 ..
lrwxrwxrwx    1 root     root             0 May 28 18:59 dev1.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata1/link1/dev1.0/ata_device/dev1.0
lrwxrwxrwx    1 root     root             0 May 28 18:59 dev10.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata10/link10/dev10.0/ata_device/dev10.0
lrwxrwxrwx    1 root     root             0 May 28 18:59 dev2.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata2/link2/dev2.0/ata_device/dev2.0
lrwxrwxrwx    1 root     root             0 May 28 18:59 dev3.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata3/link3/dev3.0/ata_device/dev3.0
lrwxrwxrwx    1 root     root             0 May 28 18:59 dev4.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata4/link4/dev4.0/ata_device/dev4.0
lrwxrwxrwx    1 root     root             0 May 28 18:59 dev5.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata5/link5/dev5.0/ata_device/dev5.0
lrwxrwxrwx    1 root     root             0 May 28 18:59 dev6.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata6/link6/dev6.0/ata_device/dev6.0
lrwxrwxrwx    1 root     root             0 May 28 18:59 dev7.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata7/link7/dev7.0/ata_device/dev7.0
lrwxrwxrwx    1 root     root             0 May 28 18:59 dev8.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata8/link8/dev8.0/ata_device/dev8.0
lrwxrwxrwx    1 root     root             0 May 28 18:59 dev9.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata9/link9/dev9.0/ata_device/dev9.0
SynologyNAS>

 

[wessu]

I still ended up with the same error message. I tried another SATA port and rebooted and still the same. Here is the output

Spoiler

SynologyNAS>  cat /proc/cmdline
BOOT_IMAGE=/zImage syno_hw_version=DS1621+ console=ttyS0,115200n8 netif_num=1 synoboot2 earlycon=uart8250,io,0x3f8,115200n8 mac1=001132DFD5D3 sn=2080S7RDFAFBD SMBusHddDynamicPower=1 DiskIdxMap=0200 vender_format_version=2 root=/dev/md0 SataPortMap=42 syno_ttyS1=serial,0x2f8 syno_ttyS0=serial,0x3f8
SynologyNAS>  ls -la /sys/block
drwxr-xr-x    2 root     root             0 May 28 19:14 .
dr-xr-xr-x   12 root     root             0 May 28 19:14 ..
lrwxrwxrwx    1 root     root             0 May 28 19:14 nvme0n1 -> ../devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1
lrwxrwxrwx    1 root     root             0 May 28 19:16 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx    1 root     root             0 May 28 19:16 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx    1 root     root             0 May 28 19:16 ram10 -> ../devices/virtual/block/ram10
lrwxrwxrwx    1 root     root             0 May 28 19:16 ram11 -> ../devices/virtual/block/ram11
lrwxrwxrwx    1 root     root             0 May 28 19:16 ram12 -> ../devices/virtual/block/ram12
lrwxrwxrwx    1 root     root             0 May 28 19:16 ram13 -> ../devices/virtual/block/ram13
lrwxrwxrwx    1 root     root             0 May 28 19:16 ram14 -> ../devices/virtual/block/ram14
lrwxrwxrwx    1 root     root             0 May 28 19:16 ram15 -> ../devices/virtual/block/ram15
lrwxrwxrwx    1 root     root             0 May 28 19:16 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx    1 root     root             0 May 28 19:16 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx    1 root     root             0 May 28 19:16 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx    1 root     root             0 May 28 19:16 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx    1 root     root             0 May 28 19:16 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx    1 root     root             0 May 28 19:16 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx    1 root     root             0 May 28 19:16 ram8 -> ../devices/virtual/block/ram8
lrwxrwxrwx    1 root     root             0 May 28 19:16 ram9 -> ../devices/virtual/block/ram9
lrwxrwxrwx    1 root     root             0 May 28 19:14 sata1 -> ../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata6/host5/target5:0:0/5:0:0:0/block/sata1
lrwxrwxrwx    1 root     root             0 May 28 19:16 synoboot -> ../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.1/usb1/1-4/1-4:1.0/host10/target10:0:0/10:0:0:0/block/synoboot
SynologyNAS>  ls -la /sys/class/ata_device
drwxr-xr-x    2 root     root             0 May 28 19:17 .
drwxr-xr-x   47 root     root             0 May 28 19:14 ..
lrwxrwxrwx    1 root     root             0 May 28 19:17 dev1.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata1/link1/dev1.0/ata_device/dev1.0
lrwxrwxrwx    1 root     root             0 May 28 19:17 dev10.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata10/link10/dev10.0/ata_device/dev10.0
lrwxrwxrwx    1 root     root             0 May 28 19:17 dev2.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata2/link2/dev2.0/ata_device/dev2.0
lrwxrwxrwx    1 root     root             0 May 28 19:17 dev3.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata3/link3/dev3.0/ata_device/dev3.0
lrwxrwxrwx    1 root     root             0 May 28 19:17 dev4.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:09.0/0000:07:00.0/ata4/link4/dev4.0/ata_device/dev4.0
lrwxrwxrwx    1 root     root             0 May 28 19:17 dev5.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata5/link5/dev5.0/ata_device/dev5.0
lrwxrwxrwx    1 root     root             0 May 28 19:17 dev6.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata6/link6/dev6.0/ata_device/dev6.0
lrwxrwxrwx    1 root     root             0 May 28 19:17 dev7.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata7/link7/dev7.0/ata_device/dev7.0
lrwxrwxrwx    1 root     root             0 May 28 19:17 dev8.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata8/link8/dev8.0/ata_device/dev8.0
lrwxrwxrwx    1 root     root             0 May 28 19:17 dev9.0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:0a.0/0000:08:00.0/ata9/link9/dev9.0/ata_device/dev9.0
SynologyNAS>