[GH-ISSUE #57 ] can we adjust SATA rate down for compatibility? #5

Author

Owner

@007revad commented on GitHub (Aug 3, 2025):

The DX513's eSATA speed is 3 Gbps (375 MB/s) and is shared between 5 drives (or 5 drive bays).

Your 150 MBps looks pretty good to me compared to what I get.

On my DX213, which only has to share 3 Gbps (375 MB/s) between 2 drives (or 2 drive bays) I only get 109.55 MB/sec direct reads:

root@DISKSTATION:~# hdparm -tT --direct /dev/sata1

/dev/sata1:
 Timing O_DIRECT cached reads:   190 MB in  2.01 seconds =  94.37 MB/sec
 Timing O_DIRECT disk reads: 330 MB in  3.01 seconds = 109.55 MB/sec

On the 16TB Ironwolf drives in the NAS, a DS1821+, I get 166.5 MB/sec direct reads:

root@DISKSTATION:~# hdparm -tT --direct /dev/sata2

/dev/sata2:
 Timing O_DIRECT cached reads:   672 MB in  2.00 seconds = 335.51 MB/sec
 Timing O_DIRECT disk reads: 500 MB in  3.00 seconds = 166.57 MB/sec

On the first 6 drives, 6TB WD Red Plus, in my old DS1812+, I get 165.3 MB/sec direct reads:

root@WEBBER:~# hdparm -tT --direct /dev/sda

/dev/sda:
 Timing O_DIRECT cached reads:   480 MB in  2.00 seconds = 239.48 MB/sec
 Timing O_DIRECT disk reads: 496 MB in  3.00 seconds = 165.30 MB/sec

On the last 2 drives, also 6TB WD Red Plus, in my old DS1812+, I get only 117.38 MB/sec direct reads because bays 7 and 8 are only SATA 2 (3 Gbps):

root@WEBBER:~# hdparm -tT --direct /dev/sdh

/dev/sdh:
 Timing O_DIRECT cached reads:   244 MB in  2.00 seconds = 121.94 MB/sec
 Timing O_DIRECT disk reads: 354 MB in  3.02 seconds = 117.38 MB/sec

@007revad commented on GitHub (Aug 3, 2025): The DX513's eSATA speed is 3 Gbps (375 MB/s) and is shared between 5 drives (or 5 drive bays). Your 150 MBps looks pretty good to me compared to what I get. On my DX213, which only has to share 3 Gbps (375 MB/s) between 2 drives (or 2 drive bays) I only get **109**.55 MB/sec direct reads: ``` root@DISKSTATION:~# hdparm -tT --direct /dev/sata1 /dev/sata1: Timing O_DIRECT cached reads: 190 MB in 2.01 seconds = 94.37 MB/sec Timing O_DIRECT disk reads: 330 MB in 3.01 seconds = 109.55 MB/sec ``` On the 16TB Ironwolf drives in the NAS, a DS1821+, I get **166**.5 MB/sec direct reads: ``` root@DISKSTATION:~# hdparm -tT --direct /dev/sata2 /dev/sata2: Timing O_DIRECT cached reads: 672 MB in 2.00 seconds = 335.51 MB/sec Timing O_DIRECT disk reads: 500 MB in 3.00 seconds = 166.57 MB/sec ``` On the first 6 drives, 6TB WD Red Plus, in my old DS1812+, I get **165**.3 MB/sec direct reads: ``` root@WEBBER:~# hdparm -tT --direct /dev/sda /dev/sda: Timing O_DIRECT cached reads: 480 MB in 2.00 seconds = 239.48 MB/sec Timing O_DIRECT disk reads: 496 MB in 3.00 seconds = 165.30 MB/sec ``` On the last 2 drives, also 6TB WD Red Plus, in my old DS1812+, I get only **117**.38 MB/sec direct reads because bays 7 and 8 are only SATA 2 (3 Gbps): ``` root@WEBBER:~# hdparm -tT --direct /dev/sdh /dev/sdh: Timing O_DIRECT cached reads: 244 MB in 2.00 seconds = 121.94 MB/sec Timing O_DIRECT disk reads: 354 MB in 3.02 seconds = 117.38 MB/sec ```

kerem commented

Author

Owner

@mervincm commented on GitHub (Aug 3, 2025):

I understand the chipset in the DX513 supports 3Gbps, and the tech used is port multiplier, and therefore shared with all disks in the enclosure. Despite spec'd for 3Gbps Synology purposefully links at 1.5Gbps for stability reasons (with DS1815+) According to that web-link and according to the performance I experience when it is connected to my 1815+ I was hoping that the script could optionally support 1.5Gbps so that I could trade some performance for more stability.

I have a bunch of 1TB SATA SSD I can use to do performance testing if that would be helpful?
(edit clarity)

@mervincm commented on GitHub (Aug 3, 2025): I understand the chipset in the DX513 supports 3Gbps, and the tech used is port multiplier, and therefore shared with all disks in the enclosure. Despite spec'd for 3Gbps Synology purposefully links at 1.5Gbps for stability reasons (with DS1815+) According to that web-link and according to the performance I experience when it is connected to my 1815+ I was hoping that the script could optionally support 1.5Gbps so that I could trade some performance for more stability. I have a bunch of 1TB SATA SSD I can use to do performance testing if that would be helpful? (edit clarity)

kerem commented

Author

Owner

@mervincm commented on GitHub (Aug 14, 2025):

I believe it’s the link speed that is causing the issue. I have replaced some of the disks and I get the error on most restart on even the replacement disks. I had only 4x 6TB NAS disks and the PSU should handle that I hope. I didn’t see these errors when it was connected at sata-1 speeds to my DS1815+.
Google tells me that these high response times can be caused by bad data cables in a reg PC, I confirmed my esata cable appears fine and I used contact cleaner on it and the NAS port, plus DX513 backplane. It seems it might be the same data errors that led Synology to run it at SATA1 (1.5Gbps) despite the fact it supports SATA2.

@mervincm commented on GitHub (Aug 14, 2025): I believe it’s the link speed that is causing the issue. I have replaced some of the disks and I get the error on most restart on even the replacement disks. I had only 4x 6TB NAS disks and the PSU should handle that I hope. I didn’t see these errors when it was connected at sata-1 speeds to my DS1815+. Google tells me that these high response times can be caused by bad data cables in a reg PC, I confirmed my esata cable appears fine and I used contact cleaner on it and the NAS port, plus DX513 backplane. It seems it might be the same data errors that led Synology to run it at SATA1 (1.5Gbps) despite the fact it supports SATA2.

kerem commented

Author

Owner

@007revad commented on GitHub (Aug 14, 2025):

Your DS1821+ has 2 eSATA ports. Have tried the 2nd eSATA port?

I know you said you've confirmed your eSATA cable appears fine, but there was another person having a similar issue (where the DX517 would work on 1 NAS but not the other) and when they tried a different eSATA cable it solved their problem.

I believe the port's link speed is determined by the BIOS, and not by DSM.

@007revad commented on GitHub (Aug 14, 2025): Your DS1821+ has 2 eSATA ports. Have tried the 2nd eSATA port? I know you said you've confirmed your eSATA cable appears fine, but there was another person having a similar issue (where the DX517 would work on 1 NAS but not the other) and when they tried a different eSATA cable it solved their problem. I believe the port's link speed is determined by the BIOS, and not by DSM.

kerem commented

Author

Owner

@mervincm commented on GitHub (Aug 14, 2025):

I have tried the second eSATA port with similar results. I tried a known working cable from another enclosure and had the same result.

@mervincm commented on GitHub (Aug 14, 2025): I have tried the second eSATA port with similar results. I tried a known working cable from another enclosure and had the same result.

kerem commented

Author

Owner

@ctl26481 commented on GitHub (Aug 30, 2025):

You can use libata.force=X.Y:1.5G in kernel cmdline to adjust the speed but you need to find out WHICH ata controller AND the port is eSATA.

Referenced from this post:
https://www.reddit.com/r/archlinux/comments/hegh2r/how_doshould_i_limit_sata_link_speed_on_a_hard/

Same type of 1.5G speed mitigation was also used with DX510 according to GPL'd source code. DX513 uses the same SIL3726 so it's probably the same mitigation method, I'm too lazy to find out.

@007revad
Check out the GPL'd source code of libata-pmp.c and libata-core.c from $yno's repo, might be very useful to understand how it authenticates the eunit firmware and what mitigations were applied. PMP=PortMultiPlier

@ctl26481 commented on GitHub (Aug 30, 2025): You can use libata.force=X.Y:1.5G in kernel cmdline to adjust the speed but you need to find out WHICH ata controller AND the port is eSATA. Referenced from this post: https://www.reddit.com/r/archlinux/comments/hegh2r/how_doshould_i_limit_sata_link_speed_on_a_hard/ Same type of 1.5G speed mitigation was also used with DX510 according to GPL'd source code. DX513 uses the same SIL3726 so it's probably the same mitigation method, I'm too lazy to find out. @007revad Check out the GPL'd source code of libata-pmp.c and libata-core.c from $yno's repo, might be very useful to understand how it authenticates the eunit firmware and what mitigations were applied. PMP=PortMultiPlier

kerem commented

Author

Owner

@steinreiter commented on GitHub (Sep 13, 2025):

Hello, I have a DS1621+ in combination with a DX213 and had the same problem as @mervincm, when I got it running under DSM 7.2 about 1.5 years ago using the synology_enable_eunit script. As far as I remember, I was able to reproduce the problem by forcing massive write and read operations on a specific hard drive in the expansion unit.

First of all, the DS1621+ is identical to the DS1821+, except for the two additional bays. Furthermore, the DX213 uses the same SiI3826 SATA port multiplier chip as the DX513.

I searched through several forums and tried a lot of things. At some point, I discovered that, according to the manufacturer's (Silicon Image) datasheet, the SATA port multiplier chip in the DX213 doesn't support NCQ (Native Command Queuing), but the one in the DS1621+ does.

Alongside, with NCQ, multiple write and read operations are transferred, and the sequence of operations is optimized so that they can be executed with as little rotational delay as possible by the HDD.

I wrote a script then for the synology task scheduler, which determines which hard drives belong to my DX213 and then sets the NCQ queue depth to 1 element. I started at the driver level (proc-fs/sys-fs), but later I discovered that Synology also has its own CLI tools for doing the same. It only needs to be executed once at every system startup or when hard drives are inserted into the expansion unit while the system is running. Since then, I haven't had any problems like the ones you described above with the expansion unit. The script would also be useful for all older expansion units that do not support NCQ.

Disable NCQ for drives in the DX (set queue depth of NCQ to 1 element)

DX_NAME=DX213   #capitalization of the name is important
DX_DISK_NUM=2   #max number of disks supported by the expansion unit

DX_DISKS=$(syno_disk_dump | grep "^Eunit disk info: $DX_NAME\$" -A $DX_DISK_NUM | tail -n+2 | head -n$DX_DISK_NUM | cut -d: -f2 | cut -f1 | xargs)

for dx_disk in $DX_DISKS; do
  syno_disk_ctl --ncq-off $dx_disk
done

For other expansion units, the script DX_NAME and DX_DISK_NUM obviously needs to be adapted. Maybe the script must be or expanded if you use more than one of the same expansion units. Maybe @007revad can take some of this script and integrate an option into its synology_enable_eunit script to make it more applicable.

@steinreiter commented on GitHub (Sep 13, 2025): Hello, I have a DS1621+ in combination with a DX213 and had the same problem as @mervincm, when I got it running under DSM 7.2 about 1.5 years ago using the synology_enable_eunit script. As far as I remember, I was able to reproduce the problem by forcing massive write and read operations on a specific hard drive in the expansion unit. First of all, the DS1621+ is identical to the DS1821+, except for the two additional bays. Furthermore, the DX213 uses the same SiI3826 SATA port multiplier chip as the DX513. I searched through several forums and tried a lot of things. At some point, I discovered that, according to the manufacturer's (Silicon Image) datasheet, the SATA port multiplier chip in the DX213 doesn't support NCQ (Native Command Queuing), but the one in the DS1621+ does. Alongside, with NCQ, multiple write and read operations are transferred, and the sequence of operations is optimized so that they can be executed with as little rotational delay as possible by the HDD. I wrote a script then for the synology task scheduler, which determines which hard drives belong to my DX213 and then sets the NCQ queue depth to 1 element. I started at the driver level (proc-fs/sys-fs), but later I discovered that Synology also has its own CLI tools for doing the same. It only needs to be executed once at every system startup or when hard drives are inserted into the expansion unit while the system is running. Since then, I haven't had any problems like the ones you described above with the expansion unit. The script would also be useful for all older expansion units that do not support NCQ. Disable NCQ for drives in the DX (set queue depth of NCQ to 1 element) ``` DX_NAME=DX213 #capitalization of the name is important DX_DISK_NUM=2 #max number of disks supported by the expansion unit DX_DISKS=$(syno_disk_dump | grep "^Eunit disk info: $DX_NAME\$" -A $DX_DISK_NUM | tail -n+2 | head -n$DX_DISK_NUM | cut -d: -f2 | cut -f1 | xargs) for dx_disk in $DX_DISKS; do syno_disk_ctl --ncq-off $dx_disk done ``` For other expansion units, the script `DX_NAME` and `DX_DISK_NUM` obviously needs to be adapted. Maybe the script must be or expanded if you use more than one of the same expansion units. Maybe @007revad can take some of this script and integrate an option into its synology_enable_eunit script to make it more applicable.

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 13, 2025):

Hello, I have a DS1621+ in combination with a DX213 and had the same problem as @mervincm, when I got it running under DSM 7.2 about 1.5 years ago using the synology_enable_eunit script. As far as I remember, I was able to reproduce the problem by forcing massive write and read operations on a specific hard drive in the expansion unit.

First of all, the DS1621+ is identical to the DS1821+, except for the two additional bays. Furthermore, the DX213 uses the same SiI3826 SATA port multiplier chip as the DX513.

I searched through several forums and tried a lot of things. At some point, I discovered that, according to the manufacturer's (Silicon Image) datasheet, the SATA port multiplier chip in the DX213 doesn't support NCQ (Native Command Queuing), but the one in the DS1621+ does.

I wrote a script then for the synology task scheduler, which determines which hard drives belong to my DX213 and then sets the NCQ queue depth to 1 element. I started at the driver level (proc-fs/sys-fs), but later I discovered that Synology also has its own CLI tools for doing the same. It only needs to be executed once at every system startup or when hard drives are inserted into the expansion unit while the system is running. Since then, I haven't had any problems like the ones you described above with the expansion unit. The script would also be useful for all older expansion units that do not support NCQ.

This is very interesting. I only seem to run into issue at restart. Did you see this happening at bootup as well? Do you think if I execute this as a startup initiated scheduled task that it will occur early enough to impact a boot up issue? It seems to work for you as a scheduled task, so I will try it out!

adapted for the 513

# Disable NCQ for drives in the DX (set queue depth of NCQ to 1 element)
DX_NAME=DX513   #capitalization of the name is important
DX_DISK_NUM=5   #max number of disks supported by the expansion unit
DX_DISKS=$(syno_disk_dump | grep "^Eunit disk info: $DX_NAME\$" -A $DX_DISK_NUM | tail -n+2 | head -n$DX_DISK_NUM | cut -d: -f2 | cut -f1 | xargs)
for dx_disk in $DX_DISKS; do
syno_disk_ctl --ncq-off $dx_disk
done

Currently I have to rebuild my volume every boot and it is less than great :)

@mervincm commented on GitHub (Sep 13, 2025): > Hello, I have a DS1621+ in combination with a DX213 and had the same problem as [@mervincm](https://github.com/mervincm), when I got it running under DSM 7.2 about 1.5 years ago using the synology_enable_eunit script. As far as I remember, I was able to reproduce the problem by forcing massive write and read operations on a specific hard drive in the expansion unit. > > First of all, the DS1621+ is identical to the DS1821+, except for the two additional bays. Furthermore, the DX213 uses the same SiI3826 SATA port multiplier chip as the DX513. > > I searched through several forums and tried a lot of things. At some point, I discovered that, according to the manufacturer's (Silicon Image) datasheet, the SATA port multiplier chip in the DX213 doesn't support NCQ (Native Command Queuing), but the one in the DS1621+ does. > > I wrote a script then for the synology task scheduler, which determines which hard drives belong to my DX213 and then sets the NCQ queue depth to 1 element. I started at the driver level (proc-fs/sys-fs), but later I discovered that Synology also has its own CLI tools for doing the same. It only needs to be executed once at every system startup or when hard drives are inserted into the expansion unit while the system is running. Since then, I haven't had any problems like the ones you described above with the expansion unit. The script would also be useful for all older expansion units that do not support NCQ. This is very interesting. I only seem to run into issue at restart. Did you see this happening at bootup as well? Do you think if I execute this as a startup initiated scheduled task that it will occur early enough to impact a boot up issue? It seems to work for you as a scheduled task, so I will try it out! adapted for the 513 ``` # Disable NCQ for drives in the DX (set queue depth of NCQ to 1 element) DX_NAME=DX513 #capitalization of the name is important DX_DISK_NUM=5 #max number of disks supported by the expansion unit DX_DISKS=$(syno_disk_dump | grep "^Eunit disk info: $DX_NAME\$" -A $DX_DISK_NUM | tail -n+2 | head -n$DX_DISK_NUM | cut -d: -f2 | cut -f1 | xargs) for dx_disk in $DX_DISKS; do syno_disk_ctl --ncq-off $dx_disk done ``` Currently I have to rebuild my volume every boot and it is less than great :)

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 13, 2025):

not sure if this is a fair way to share the boot experience I see but ...

ignore the sound bit as that is my boiler kicking in, not the drive array :)

Here is a OneDrive share
https://1drv.ms/v/c/fa051e577efa18b5/EchQZA6WD45IjbomnoWRDnEBRg2w6R5xJ4faaRaguVN1sw?e=pmBqbr

@mervincm commented on GitHub (Sep 13, 2025): not sure if this is a fair way to share the boot experience I see but ... ignore the sound bit as that is my boiler kicking in, not the drive array :) Here is a OneDrive share https://1drv.ms/v/c/fa051e577efa18b5/EchQZA6WD45IjbomnoWRDnEBRg2w6R5xJ4faaRaguVN1sw?e=pmBqbr

kerem commented

Author

Owner

@007revad commented on GitHub (Sep 13, 2025):

Very interesting. I've only ever had 1 HDD in my DX213 (for testing) so I've never experienced this issue.

I will add the code from @steinreiter today for the DX513 and DX213. I suspect the DX510 and RX410 may the same.

@007revad commented on GitHub (Sep 13, 2025): Very interesting. I've only ever had 1 HDD in my DX213 (for testing) so I've never experienced this issue. I will add the code from @steinreiter today for the DX513 and DX213. I suspect the DX510 and RX410 may the same.

kerem commented

Author

Owner

@007revad commented on GitHub (Sep 13, 2025):

According to Google:

DX510 uses the Silicon Image SiI3726 chip
DX513 uses the Silicon Image SiI3826 chip
DX517 uses the Silicon Image SiI3826 chip

If that is correct then DSM must set syno_disk_ctl --ncq-off when an officially supported expansion unit is connected (like a DX517 connected to a DS1821+).

Strangely Google also thinks the SiI3826 is a multi-function printer... and not

On my DS1821+ all drives are set to queue depth 31

root@DISKSTATION:~# syno_disk_ctl --ncq-get /dev/sata1
ncq-on (queue depth 31)

@007revad commented on GitHub (Sep 13, 2025): According to Google: - DX510 uses the Silicon Image SiI3726 chip - DX513 uses the Silicon Image SiI3826 chip - DX517 uses the Silicon Image SiI3826 chip If that is correct then DSM must set `syno_disk_ctl --ncq-off` when an officially supported expansion unit is connected (like a DX517 connected to a DS1821+). Strangely Google also thinks the SiI3826 is a multi-function printer... and not On my DS1821+ all drives are set to queue depth 31 ``` root@DISKSTATION:~# syno_disk_ctl --ncq-get /dev/sata1 ncq-on (queue depth 31) ```

kerem commented

Author

Owner

@007revad commented on GitHub (Sep 13, 2025):

@mervincm

When your NAS has finished repairing the storage pool can you test this version of syno_enable_eunit: https://github.com/007revad/Synology_enable_eunit/releases/tag/v3.0.20

@007revad commented on GitHub (Sep 13, 2025): @mervincm When your NAS has finished repairing the storage pool can you test this version of syno_enable_eunit: https://github.com/007revad/Synology_enable_eunit/releases/tag/v3.0.20

kerem commented

Author

Owner

@ctl26481 commented on GitHub (Sep 14, 2025):

According to Google:
* DX510 uses the Silicon Image SiI3726 chip

* DX513 uses the Silicon Image SiI3826 chip

* DX517 uses the Silicon Image SiI3826 chip
If that is correct then DSM must set syno_disk_ctl --ncq-off when an officially supported expansion unit is connected (like a DX517 connected to a DS1821+).

Strangely Google also thinks the SiI3826 is a multi-function printer... and not

On my DS1821+ all drives are set to queue depth 31
root@DISKSTATION:~# syno_disk_ctl --ncq-get /dev/sata1
ncq-on (queue depth 31)

~~Both 510 and 513 use SIL3726.~~ (latter used 3826)

DX517 uses Marvell 88SM9705 for 6Gb/s with support of NCQ. The GPL'd code doesn't disable command queue for mitigation.

Looks like syno_disk_ctl --ncq checks/writes to /sys/block/sd*/device/queue_depth, this can be used for adjusting command queue depth during runtime.(31 for max queue, default value) However this might not work for SSDs with queued TRIM bug, requiring libata.noncq at boot parameter.

@ctl26481 commented on GitHub (Sep 14, 2025): > According to Google: > > * DX510 uses the Silicon Image SiI3726 chip > > * DX513 uses the Silicon Image SiI3826 chip > > * DX517 uses the Silicon Image SiI3826 chip > > > If that is correct then DSM must set `syno_disk_ctl --ncq-off` when an officially supported expansion unit is connected (like a DX517 connected to a DS1821+). > > Strangely Google also thinks the SiI3826 is a multi-function printer... and not > > On my DS1821+ all drives are set to queue depth 31 > > ``` > root@DISKSTATION:~# syno_disk_ctl --ncq-get /dev/sata1 > ncq-on (queue depth 31) > ``` ~~Both 510 and 513 use SIL3726.~~ (latter used 3826) DX517 uses Marvell 88SM9705 for 6Gb/s with support of NCQ. The GPL'd code doesn't disable command queue for mitigation. Looks like `syno_disk_ctl --ncq` checks/writes to `/sys/block/sd*/device/queue_depth`, this can be used for adjusting command queue depth during runtime.(31 for max queue, default value) However this might not work for SSDs with queued TRIM bug, requiring libata.noncq at boot parameter.

kerem commented

Author

Owner

@007revad commented on GitHub (Sep 14, 2025):

Both 510 and 513 use SIL3726.

DX517 uses Marvell 88SM9705 for 6Gb/s support and supports NCQ. The GPL'd code doesn't disable command queue for mitigation.

Thanks for confirming my suspicions that Google Search's AI answer was wrong.

Looks like syno_disk_ctl --ncq checks/writes to /sys/block/sd*/device/queue_depth, this can be used for adjusting command queue depth during runtime.(31 for max queue, default value) However this might not work for SSDs with queued TRIM bug, requiring libata.noncq at boot parameter.

Sounds like I should update the script to only set --ncq-off if the drive in the expansion unit is a HDD.

@007revad commented on GitHub (Sep 14, 2025): > Both 510 and 513 use SIL3726. > > DX517 uses Marvell 88SM9705 for 6Gb/s support and supports NCQ. The GPL'd code doesn't disable command queue for mitigation. Thanks for confirming my suspicions that Google Search's AI answer was wrong. > Looks like syno_disk_ctl --ncq checks/writes to /sys/block/sd*/device/queue_depth, this can be used for adjusting command queue depth during runtime.(31 for max queue, default value) However this might not work for SSDs with queued TRIM bug, requiring libata.noncq at boot parameter. Sounds like I should update the script to only set `--ncq-off` if the drive in the expansion unit is a HDD.

kerem commented

Author

Owner

@007revad commented on GitHub (Sep 14, 2025):

Both 510 and 513 use SIL3726.

Going by this photo on https://www.techpowerup.com/review/synology-ds1515plus/7.html the DX513 uses a SIL3826

And by this photo on https://www.mobile01.com/topicdetail.php?f=494&t=2931809 the DX213 also uses a SIL3826

You were correct about the DX510 as this photo and the text on https://www.smallnetbuilder.com/nas/nas-reviews/synology-dx510-disk-station-expansion-unit-reviewed/ shows the DX510 uses a SIL3726.

From what I've found both the SIL3726 and SIL3826 do not support NCQ (Native Command Queuing).

@007revad commented on GitHub (Sep 14, 2025): > Both 510 and 513 use SIL3726. Going by [this photo](https://www.techpowerup.com/review/synology-ds1515plus/images/in_main_PCB1.jpg) on https://www.techpowerup.com/review/synology-ds1515plus/7.html the DX513 uses a SIL3**8**26 And by [this photo](https://attach.mobile01.com/attach/201209/mobile01-74fb7b0691ad1c03b35723e09fdbc2ae.jpg) on https://www.mobile01.com/topicdetail.php?f=494&t=2931809 the DX213 also uses a SIL3**8**26 You were correct about the DX510 as [this photo](https://www.smallnetbuilder.com/myincludes/image_page.php?/images/stories/nas/synology_dx510/synology_dx510_board.jpg) and the text on https://www.smallnetbuilder.com/nas/nas-reviews/synology-dx510-disk-station-expansion-unit-reviewed/ shows the DX510 uses a SIL3726. From what I've found both the SIL3726 and SIL3826 do not support NCQ (Native Command Queuing).

kerem commented

Author

Owner

@ctl26481 commented on GitHub (Sep 14, 2025):

Both 510 and 513 use SIL3726.

Going by this photo on https://www.techpowerup.com/review/synology-ds1515plus/7.html the DX513 uses a SIL3826

And by this photo on https://www.mobile01.com/topicdetail.php?f=494&t=2931809 the DX213 also uses a SIL3826

You were correct about the DX510 as this photo and the text on https://www.smallnetbuilder.com/nas/nas-reviews/synology-dx510-disk-station-expansion-unit-reviewed/ shows the DX510 uses a SIL3726.

From what I've found both the SIL3726 and SIL3826 do not support NCQ (Native Command Queuing).

You're right! I mistook the numbers.

DX517 using 88SM9705:
https://blog.ggrarea.cn/archives/37903.html

Marvell datasheet specifying Native Command Queuing supported to 32.
https://www.marvell.com/content/dam/marvell/en/public-collateral/storage/marvell-storage-88sm9xxx-product-brief-2013-06.pdf

@ctl26481 commented on GitHub (Sep 14, 2025): > > Both 510 and 513 use SIL3726. > > Going by [this photo](https://www.techpowerup.com/review/synology-ds1515plus/images/in_main_PCB1.jpg) on https://www.techpowerup.com/review/synology-ds1515plus/7.html the DX513 uses a SIL3**8**26 > > And by [this photo](https://attach.mobile01.com/attach/201209/mobile01-74fb7b0691ad1c03b35723e09fdbc2ae.jpg) on https://www.mobile01.com/topicdetail.php?f=494&t=2931809 the DX213 also uses a SIL3**8**26 > > You were correct about the DX510 as [this photo](https://www.smallnetbuilder.com/myincludes/image_page.php?/images/stories/nas/synology_dx510/synology_dx510_board.jpg) and the text on https://www.smallnetbuilder.com/nas/nas-reviews/synology-dx510-disk-station-expansion-unit-reviewed/ shows the DX510 uses a SIL3726. > > From what I've found both the SIL3726 and SIL3826 do not support NCQ (Native Command Queuing). You're right! I mistook the numbers. DX517 using 88SM9705: https://blog.ggrarea.cn/archives/37903.html Marvell datasheet specifying Native Command Queuing supported to 32. https://www.marvell.com/content/dam/marvell/en/public-collateral/storage/marvell-storage-88sm9xxx-product-brief-2013-06.pdf

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 15, 2025):

@mervincm

When your NAS has finished repairing the storage pool can you test this version of syno_enable_eunit: https://github.com/007revad/Synology_enable_eunit/releases/tag/v3.0.20

I added my slightly modified version of his script and made your e enable script a dependency of it so yours runs first. So far I have done about 5-6 reboots/restarts and while it doesn't stop the repeating cycle in my video, it has yet to crash the array or give any high response time messages, so I suspect that if not solved things are at least much better. I want to run a few more restart cycles on this solution before I swap over to you new script if that's OK.
I have not had a chance to look into how to apply the rate limiting as suggested by [ctl26481] .. maybe thats what I need to avoid the reboot eSATA light "dance" on my expansion.

@mervincm commented on GitHub (Sep 15, 2025): > [@mervincm](https://github.com/mervincm) > > When your NAS has finished repairing the storage pool can you test this version of syno_enable_eunit: https://github.com/007revad/Synology_enable_eunit/releases/tag/v3.0.20 I added my slightly modified version of his script and made your e enable script a dependency of it so yours runs first. So far I have done about 5-6 reboots/restarts and while it doesn't stop the repeating cycle in my video, it has yet to crash the array or give any high response time messages, so I suspect that if not solved things are at least much better. I want to run a few more restart cycles on this solution before I swap over to you new script if that's OK. I have not had a chance to look into how to apply the rate limiting as suggested by [ctl26481] .. maybe thats what I need to avoid the reboot eSATA light "dance" on my expansion.

kerem commented

Author

Owner

@steinreiter commented on GitHub (Sep 15, 2025):

Hello, it sounds good that disabling NCQ has stopped the volume from crashing. So it helps with your DX513 as well as my DX213.

Unfortunately, I haven't been able to test the adjustments from @007revad with my DX213 yet due to private timing issues.

It's strange that the blinking behavior on @mervincm DX513 hasn't changed. I just happen to be able to purchase a DX513 at a reasonable price right now (not the old version based on DX510, a newer version of the DX513, like yours with the DX517 housing).

I'll get back to you as soon as I've tested the changes from @007revad it with my DX213 and my future DX513 (when arrived).

Best regards

@steinreiter commented on GitHub (Sep 15, 2025): Hello, it sounds good that disabling NCQ has stopped the volume from crashing. So it helps with your DX513 as well as my DX213. Unfortunately, I haven't been able to test the adjustments from @007revad with my DX213 yet due to private timing issues. It's strange that the blinking behavior on @mervincm DX513 hasn't changed. I just happen to be able to purchase a DX513 at a reasonable price right now (not the old version based on DX510, a newer version of the DX513, like yours with the DX517 housing). I'll get back to you as soon as I've tested the changes from @007revad it with my DX213 and my future DX513 (when arrived). Best regards

kerem commented

Author

Owner

@steinreiter commented on GitHub (Sep 15, 2025):

Both 510 and 513 use SIL3726.
DX517 uses Marvell 88SM9705 for 6Gb/s support and supports NCQ. The GPL'd code doesn't disable command queue for mitigation.

Thanks for confirming my suspicions that Google Search's AI answer was wrong.

Looks like syno_disk_ctl --ncq checks/writes to /sys/block/sd*/device/queue_depth, this can be used for adjusting command queue depth during runtime.(31 for max queue, default value) However this might not work for SSDs with queued TRIM bug, requiring libata.noncq at boot parameter.

Sounds like I should update the script to only set --ncq-off if the drive in the expansion unit is a HDD.

@007revad , I think you misinterpreted that.

An SSD queued TRIM bug describes the faulty behavior of SSD firmwares, for example, older Samsung SSDs. With these firmwares, the TRIM command cannot be processed correctly within the NCQ queue, usually resulting in data loss or a controller crash.

In such cases, one possible solution is to disable NCQ (queue depth of 1) or disable TRIM completely. Depending on the kernel/driver, there may be blacklists that set this accordingly.

My point is that not disabling NCQ for SSDs in expansion units that don't support NCQ would therefore not be a solution. As with HDDs, NCQ should then also be disabled for SSDs.

regards

@steinreiter commented on GitHub (Sep 15, 2025): > > Both 510 and 513 use SIL3726. > > DX517 uses Marvell 88SM9705 for 6Gb/s support and supports NCQ. The GPL'd code doesn't disable command queue for mitigation. > > Thanks for confirming my suspicions that Google Search's AI answer was wrong. > > > Looks like syno_disk_ctl --ncq checks/writes to /sys/block/sd*/device/queue_depth, this can be used for adjusting command queue depth during runtime.(31 for max queue, default value) However this might not work for SSDs with queued TRIM bug, requiring libata.noncq at boot parameter. > > Sounds like I should update the script to only set `--ncq-off` if the drive in the expansion unit is a HDD. @007revad , I think you misinterpreted that. An SSD queued TRIM bug describes the faulty behavior of SSD firmwares, for example, older Samsung SSDs. With these firmwares, the TRIM command cannot be processed correctly within the NCQ queue, usually resulting in data loss or a controller crash. In such cases, one possible solution is to disable NCQ (queue depth of 1) or disable TRIM completely. Depending on the kernel/driver, there may be blacklists that set this accordingly. My point is that not disabling NCQ for SSDs in expansion units that don't support NCQ would therefore not be a solution. As with HDDs, NCQ should then also be disabled for SSDs. regards

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 17, 2025):

well darn. today on startup I got the high response error messages again (Dave'prior version script, and my adapted ver of steinreiter's NCQ disable. At least I didn't see an offline disk and RAID rebuild requirement. I will move to Dave's new script and test that out.

@mervincm commented on GitHub (Sep 17, 2025): well darn. today on startup I got the high response error messages again (Dave'prior version script, and my adapted ver of steinreiter's NCQ disable. At least I didn't see an offline disk and RAID rebuild requirement. I will move to Dave's new script and test that out.

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 17, 2025):

I swapped over to 3.20 and unfortunately I had a repeat of the high response time errors, plus this time I have an unhappy disk and had to repair the volume after remove and a further reboot. I checkedd the email log and it ran w/o error and did the NCQ disable.

@mervincm commented on GitHub (Sep 17, 2025): I swapped over to 3.20 and unfortunately I had a repeat of the high response time errors, plus this time I have an unhappy disk and had to repair the volume after remove and a further reboot. I checkedd the email log and it ran w/o error and did the NCQ disable.

kerem commented

Author

Owner

@steinreiter commented on GitHub (Sep 18, 2025):

Hey guys, the DX513 arrived today. It's relatively new and, according to the serial number, was manufactured in 2016.

So, as a precaution, I manually ran the old syno_enable_eunit.sh version 3.0.19 twice, once for the DX213 and then for the DX513. Afterward, I shut down the DS1621+.

Unfortunately, I only had two small SSDs and three smaller HDDs left, so I installed them in the DX513. Then I connected it to the DS1621+. My DX213 was also equipped with an HDD and connected.

After turning on the DS1621+, the DX513 started up and the DX513's flashing began. One after the other, the HDD LEDs on the front of the DX513 lit up. After about three seconds, all the LEDs went out, and it started again. This continued until I ran my code snippet shared above to disable NCQ for drives on the DX513. Then all the LEDs were permanently solid.

I then set up two pools on the DX513, each with one volume, one for the SSDs and one for the HDDs. The LEDs now started flashing briefly as usual when a drive was accessed.

root@DS1621plus:~# syno_disk_dump
Internal disk info:
01: /dev/sata2
02: /dev/sata3
03:
04: /dev/sata9
05:
06:
Eunit disk info: DX213
01: /dev/sata1
02:
Eunit disk info: DX513
01: /dev/sata4
02: /dev/sata5
03: /dev/sata6
04: /dev/sata7
05: /dev/sata8

I then updated syno_enable_eunit.sh to version 3.0.20 and adjusted the task scheduler so that it is called twice during boot, once for the DX213 and once for the DX513. I disabled the execution of my own disable NCQ script in the task scheduler.

After restarting the DX1621+, everything worked as expected, and syno_enable_eunit.sh reliably disabled NCQ for all drives in the DX213 and DX513. (checked via sys-fs)

Afterward, I looked at the boot log again and it was good to see that the ATA links of the DXs were constantly reset until NCQ was disabled.

root@DS1621plus:~# dmesg | grep -i ata | grep 'link'
[   10.932897] ata5 : SATA link down (SStatus 0 SControl 300)
[   10.938394] ata5 : No present pin info for SATA link down event
[   11.289904] ata2 (slot 1): SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   14.164821] ata10 : SATA link down (SStatus 0 SControl 300)
[   14.164828] ata10 : No present pin info for SATA link down event
[   14.167816] ata4 (slot 3): SATA link down (SStatus 0 SControl 300)
[   14.168013] ata4 (slot 3): Disk is not present for SATA link down event
[   17.166698] ata9 (slot 6): SATA link down (SStatus 0 SControl 300)
[   17.173854] ata9 (slot 6): Disk is not present for SATA link down event
[   17.180504] ata8 (slot 5): SATA link down (SStatus 0 SControl 300)
[   17.186858] ata8 (slot 5): Disk is not present for SATA link down event
[   18.005063] ata1 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   19.168633] ata6 : link is slow to respond, please be patient (ready=-19)
[   22.243533] ata7 (slot 4): link is slow to respond, please be patient (ready=-19)
[   24.019987] ata6 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   25.636449] ata3 (slot 2): SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   25.643418] ata3 (slot 2): link reset sucessfully clear error flags
[   29.117304] ata1.15 : link is slow to respond, please be patient (ready=-19)
[   29.269716] ata7 (slot 4): SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   29.833699] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   32.417773] ata6.01 : hard resetting link
[   32.890168] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[   32.896782] ata6.02 : hard resetting link
[   33.369800] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[   33.376413] ata6.03 : hard resetting link
[   33.850127] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[   33.856740] ata6.04 : hard resetting link
[   33.973566] ata1.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   34.328724] ata6.04 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[   36.336856] ata6.00 : hard resetting link
[   36.811028] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[   37.898580] ata1.01 : hard resetting link
[   38.207748] ata1.01 : SATA link down (SStatus 0 SControl 320)
[   38.213510] ata1 : No present pin info for SATA link down event
[   38.219536] ata1.02 : hard resetting link
[   38.528751] ata1.02 : SATA link down (SStatus 0 SControl 320)
[   38.534516] ata1 : No present pin info for SATA link down event
[   38.540539] ata1.03 : hard resetting link
[   38.849719] ata1.03 : SATA link down (SStatus 0 SControl 320)
[   38.855481] ata1 : No present pin info for SATA link down event
[   38.861506] ata1.04 : hard resetting link
[   39.170700] ata1.04 : SATA link down (SStatus 0 SControl 320)
[   39.176465] ata1 : No present pin info for SATA link down event
[   41.184007] ata1.00 : hard resetting link
[   41.657854] ata1.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[   54.564930] ata6.15 : hard resetting link
[   55.283452] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   56.333209] ata6.01 : hard resetting link
[   56.808955] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   56.815553] ata6.02 : hard resetting link
[   57.288325] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   57.294960] ata6.03 : hard resetting link
[   57.767043] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   57.773666] ata6.04 : hard resetting link
[   58.245927] ata6.04 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   60.254057] ata6.00 : hard resetting link
[   60.728830] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[   61.089853] ata6.15 : hard resetting link
[   61.808653] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   62.858882] ata6.01 : hard resetting link
[   63.332418] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   63.339057] ata6.02 : hard resetting link
[   63.812763] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   63.819581] ata6.03 : hard resetting link
[   64.292692] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   64.331531] ata6.04 : hard resetting link
[   64.803671] ata6.04 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   66.812126] ata6.00 : hard resetting link
[   67.287088] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[   67.788835] ata6.15 : hard resetting link
[   68.507043] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   69.560572] ata6.01 : hard resetting link
[   70.033609] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   70.040220] ata6.02 : hard resetting link
[   70.513599] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   70.520212] ata6.03 : hard resetting link
[   70.992802] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   70.999649] ata6.04 : hard resetting link
[   71.473153] ata6.04 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   73.481584] ata6.00 : hard resetting link
[   73.954467] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[   74.219767] ata6.15 : hard resetting link
[   74.938209] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   75.987956] ata6.01 : hard resetting link
[   76.462013] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   76.468657] ata6.02 : hard resetting link
[   76.942867] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   76.949498] ata6.03 : hard resetting link
[   77.423782] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   77.430405] ata6.04 : hard resetting link
[   77.904768] ata6.04 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   79.912927] ata6.00 : hard resetting link
[   80.385984] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)

Afterward, I ran several read and write tests on the various volumes of all pools. The connection to the drives was always stable.

If you are interested, here is the reading and writing performance of the HDDs:

#DS1621+@6.0Gbps: Toshiba 18TB HDD
root@DS1621plus:~# hdparm -tT --direct /dev/sata3
/dev/sata3:
 Timing O_DIRECT cached reads:   974 MB in  2.00 seconds = 486.86 MB/sec
 Timing O_DIRECT disk reads: 766 MB in  3.00 seconds = 255.19 MB/sec

#DS1621+@6.0Gbps: Toshiba 18TB HDD
root@DS1621plus:~# hdparm -tT --direct /dev/sata9
/dev/sata9:
 Timing O_DIRECT cached reads:   994 MB in  2.00 seconds = 496.74 MB/sec
 Timing O_DIRECT disk reads: 842 MB in  3.00 seconds = 280.33 MB/sec

#DX213@3.0Gbps: Seagate-Ironwolf 4TB
root@DS1621plus:~# hdparm -tT --direct /dev/sata1
/dev/sata1:
 Timing O_DIRECT cached reads:   134 MB in  2.02 seconds =  66.40 MB/sec
 Timing O_DIRECT disk reads: 578 MB in  3.00 seconds = 192.49 MB/sec

#DX513@3.0Gbps: WDC-Red 1TB HDD
root@DS1621plus:~# hdparm -tT --direct /dev/sata6
/dev/sata6:
 Timing O_DIRECT cached reads:   374 MB in  2.00 seconds = 186.82 MB/sec
 Timing O_DIRECT disk reads: 432 MB in  3.01 seconds = 143.63 MB/sec

#DX513@3.0Gbps: WDC-Red 1TB HDD
root@DS1621plus:~# hdparm -tT --direct /dev/sata7
/dev/sata7:
 Timing O_DIRECT cached reads:   426 MB in  2.00 seconds = 212.49 MB/sec
 Timing O_DIRECT disk reads: 426 MB in  3.00 seconds = 141.88 MB/sec

#DX513@3.0Gbps: WDC-Blue 2TB HDD
root@DS1621plus:~# hdparm -tT --direct /dev/sata8
/dev/sata8:
 Timing O_DIRECT cached reads:   354 MB in  2.00 seconds = 176.58 MB/sec
 Timing O_DIRECT disk reads: 416 MB in  3.00 seconds = 138.65 MB/sec

DS1621plus@6.0Gbps with 2HDDs SHR@Btrfs
root@DS1621plus:~# echo 3 > /proc/sys/vm/drop_caches
root@DS1621plus:~# dd if=/dev/zero of=/volume1/test/10gb.dump bs=1M count=10240; rm -f /volume1/test/10gb.dump
10240+0 records in
10240+0 records out
10737418240 bytes (11 GB, 10 GiB) copied, 33.5222 s, 320 MB/s

DX213@3.0Gbps with 1HDD SHR@Ext4
root@DS1621plus:~# echo 3 > /proc/sys/vm/drop_caches
root@DS1621plus:~# dd if=/dev/zero of=/volume2/test/10gb.dump bs=1M count=10240; rm -f /volume2/test/10gb.dump
10240+0 records in
10240+0 records out
10737418240 bytes (11 GB, 10 GiB) copied, 54.058 s, 199 MB/s

DX513@3.0Gbps with 3HDDs SHR@Btrfs
root@DS1621plus:~# echo 3 > /proc/sys/vm/drop_caches
root@DS1621plus:~# dd if=/dev/zero of=/volume5/dx513hdd/10gb.dump bs=1M count=10240; rm -f /volume5/dx513hdd/10gb.dump
10240+0 records in
10240+0 records out
10737418240 bytes (11 GB, 10 GiB) copied, 57.6258 s, 186 MB/s

Now I tried syno_enable_eunit.sh version 3.0.21. This Version does not disable NCQ for SSDs in DX. After a reboot, the result was the same as before: all LEDs eventually became solid. Now things get interesting... I ran the write test for 10GB on the SSD SHR volume of the DX513, just like before... After a few seconds the command was executed, the SSD volume crashed and one of the SSD drive's LED turned orange.

@007revad so please also disable NCQ for SSDs in DX expansion units that do not support NCQ, so please don't publish version 3.0.21 as it is.

@steinreiter commented on GitHub (Sep 18, 2025): Hey guys, the DX513 arrived today. It's relatively new and, according to the serial number, was manufactured in 2016. So, as a precaution, I manually ran the old syno_enable_eunit.sh version 3.0.19 twice, once for the DX213 and then for the DX513. Afterward, I shut down the DS1621+. Unfortunately, I only had two small SSDs and three smaller HDDs left, so I installed them in the DX513. Then I connected it to the DS1621+. My DX213 was also equipped with an HDD and connected. After turning on the DS1621+, the DX513 started up and the DX513's flashing began. One after the other, the HDD LEDs on the front of the DX513 lit up. After about three seconds, all the LEDs went out, and it started again. This continued until I ran my code snippet shared above to disable NCQ for drives on the DX513. Then all the LEDs were permanently solid. I then set up two pools on the DX513, each with one volume, one for the SSDs and one for the HDDs. The LEDs now started flashing briefly as usual when a drive was accessed. ![Image](https://github.com/user-attachments/assets/d8c4458a-8697-4581-8ae2-ea385ff7593c) <img width="603" height="459" alt="Image" src="https://github.com/user-attachments/assets/74d10449-5ea7-4e1c-8e3f-3916371d2abf" /> ``` root@DS1621plus:~# syno_disk_dump Internal disk info: 01: /dev/sata2 02: /dev/sata3 03: 04: /dev/sata9 05: 06: Eunit disk info: DX213 01: /dev/sata1 02: Eunit disk info: DX513 01: /dev/sata4 02: /dev/sata5 03: /dev/sata6 04: /dev/sata7 05: /dev/sata8 ``` I then updated syno_enable_eunit.sh to version 3.0.20 and adjusted the task scheduler so that it is called twice during boot, once for the DX213 and once for the DX513. I disabled the execution of my own disable NCQ script in the task scheduler. After restarting the DX1621+, everything worked as expected, and syno_enable_eunit.sh reliably disabled NCQ for all drives in the DX213 and DX513. (checked via sys-fs) Afterward, I looked at the boot log again and it was good to see that the ATA links of the DXs were constantly reset until NCQ was disabled. ``` root@DS1621plus:~# dmesg | grep -i ata | grep 'link' [ 10.932897] ata5 : SATA link down (SStatus 0 SControl 300) [ 10.938394] ata5 : No present pin info for SATA link down event [ 11.289904] ata2 (slot 1): SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 14.164821] ata10 : SATA link down (SStatus 0 SControl 300) [ 14.164828] ata10 : No present pin info for SATA link down event [ 14.167816] ata4 (slot 3): SATA link down (SStatus 0 SControl 300) [ 14.168013] ata4 (slot 3): Disk is not present for SATA link down event [ 17.166698] ata9 (slot 6): SATA link down (SStatus 0 SControl 300) [ 17.173854] ata9 (slot 6): Disk is not present for SATA link down event [ 17.180504] ata8 (slot 5): SATA link down (SStatus 0 SControl 300) [ 17.186858] ata8 (slot 5): Disk is not present for SATA link down event [ 18.005063] ata1 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 19.168633] ata6 : link is slow to respond, please be patient (ready=-19) [ 22.243533] ata7 (slot 4): link is slow to respond, please be patient (ready=-19) [ 24.019987] ata6 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 25.636449] ata3 (slot 2): SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 25.643418] ata3 (slot 2): link reset sucessfully clear error flags [ 29.117304] ata1.15 : link is slow to respond, please be patient (ready=-19) [ 29.269716] ata7 (slot 4): SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 29.833699] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 32.417773] ata6.01 : hard resetting link [ 32.890168] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 32.896782] ata6.02 : hard resetting link [ 33.369800] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 33.376413] ata6.03 : hard resetting link [ 33.850127] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 33.856740] ata6.04 : hard resetting link [ 33.973566] ata1.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 34.328724] ata6.04 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 36.336856] ata6.00 : hard resetting link [ 36.811028] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 37.898580] ata1.01 : hard resetting link [ 38.207748] ata1.01 : SATA link down (SStatus 0 SControl 320) [ 38.213510] ata1 : No present pin info for SATA link down event [ 38.219536] ata1.02 : hard resetting link [ 38.528751] ata1.02 : SATA link down (SStatus 0 SControl 320) [ 38.534516] ata1 : No present pin info for SATA link down event [ 38.540539] ata1.03 : hard resetting link [ 38.849719] ata1.03 : SATA link down (SStatus 0 SControl 320) [ 38.855481] ata1 : No present pin info for SATA link down event [ 38.861506] ata1.04 : hard resetting link [ 39.170700] ata1.04 : SATA link down (SStatus 0 SControl 320) [ 39.176465] ata1 : No present pin info for SATA link down event [ 41.184007] ata1.00 : hard resetting link [ 41.657854] ata1.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 54.564930] ata6.15 : hard resetting link [ 55.283452] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 56.333209] ata6.01 : hard resetting link [ 56.808955] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 56.815553] ata6.02 : hard resetting link [ 57.288325] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 57.294960] ata6.03 : hard resetting link [ 57.767043] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 57.773666] ata6.04 : hard resetting link [ 58.245927] ata6.04 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 60.254057] ata6.00 : hard resetting link [ 60.728830] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 61.089853] ata6.15 : hard resetting link [ 61.808653] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 62.858882] ata6.01 : hard resetting link [ 63.332418] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 63.339057] ata6.02 : hard resetting link [ 63.812763] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 63.819581] ata6.03 : hard resetting link [ 64.292692] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 64.331531] ata6.04 : hard resetting link [ 64.803671] ata6.04 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 66.812126] ata6.00 : hard resetting link [ 67.287088] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 67.788835] ata6.15 : hard resetting link [ 68.507043] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 69.560572] ata6.01 : hard resetting link [ 70.033609] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 70.040220] ata6.02 : hard resetting link [ 70.513599] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 70.520212] ata6.03 : hard resetting link [ 70.992802] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 70.999649] ata6.04 : hard resetting link [ 71.473153] ata6.04 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 73.481584] ata6.00 : hard resetting link [ 73.954467] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 74.219767] ata6.15 : hard resetting link [ 74.938209] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 75.987956] ata6.01 : hard resetting link [ 76.462013] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 76.468657] ata6.02 : hard resetting link [ 76.942867] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 76.949498] ata6.03 : hard resetting link [ 77.423782] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 77.430405] ata6.04 : hard resetting link [ 77.904768] ata6.04 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 79.912927] ata6.00 : hard resetting link [ 80.385984] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) ``` Afterward, I ran several read and write tests on the various volumes of all pools. The connection to the drives was always stable. If you are interested, here is the reading and writing performance of the HDDs: ``` #DS1621+@6.0Gbps: Toshiba 18TB HDD root@DS1621plus:~# hdparm -tT --direct /dev/sata3 /dev/sata3: Timing O_DIRECT cached reads: 974 MB in 2.00 seconds = 486.86 MB/sec Timing O_DIRECT disk reads: 766 MB in 3.00 seconds = 255.19 MB/sec #DS1621+@6.0Gbps: Toshiba 18TB HDD root@DS1621plus:~# hdparm -tT --direct /dev/sata9 /dev/sata9: Timing O_DIRECT cached reads: 994 MB in 2.00 seconds = 496.74 MB/sec Timing O_DIRECT disk reads: 842 MB in 3.00 seconds = 280.33 MB/sec #DX213@3.0Gbps: Seagate-Ironwolf 4TB root@DS1621plus:~# hdparm -tT --direct /dev/sata1 /dev/sata1: Timing O_DIRECT cached reads: 134 MB in 2.02 seconds = 66.40 MB/sec Timing O_DIRECT disk reads: 578 MB in 3.00 seconds = 192.49 MB/sec #DX513@3.0Gbps: WDC-Red 1TB HDD root@DS1621plus:~# hdparm -tT --direct /dev/sata6 /dev/sata6: Timing O_DIRECT cached reads: 374 MB in 2.00 seconds = 186.82 MB/sec Timing O_DIRECT disk reads: 432 MB in 3.01 seconds = 143.63 MB/sec #DX513@3.0Gbps: WDC-Red 1TB HDD root@DS1621plus:~# hdparm -tT --direct /dev/sata7 /dev/sata7: Timing O_DIRECT cached reads: 426 MB in 2.00 seconds = 212.49 MB/sec Timing O_DIRECT disk reads: 426 MB in 3.00 seconds = 141.88 MB/sec #DX513@3.0Gbps: WDC-Blue 2TB HDD root@DS1621plus:~# hdparm -tT --direct /dev/sata8 /dev/sata8: Timing O_DIRECT cached reads: 354 MB in 2.00 seconds = 176.58 MB/sec Timing O_DIRECT disk reads: 416 MB in 3.00 seconds = 138.65 MB/sec DS1621plus@6.0Gbps with 2HDDs SHR@Btrfs root@DS1621plus:~# echo 3 > /proc/sys/vm/drop_caches root@DS1621plus:~# dd if=/dev/zero of=/volume1/test/10gb.dump bs=1M count=10240; rm -f /volume1/test/10gb.dump 10240+0 records in 10240+0 records out 10737418240 bytes (11 GB, 10 GiB) copied, 33.5222 s, 320 MB/s DX213@3.0Gbps with 1HDD SHR@Ext4 root@DS1621plus:~# echo 3 > /proc/sys/vm/drop_caches root@DS1621plus:~# dd if=/dev/zero of=/volume2/test/10gb.dump bs=1M count=10240; rm -f /volume2/test/10gb.dump 10240+0 records in 10240+0 records out 10737418240 bytes (11 GB, 10 GiB) copied, 54.058 s, 199 MB/s DX513@3.0Gbps with 3HDDs SHR@Btrfs root@DS1621plus:~# echo 3 > /proc/sys/vm/drop_caches root@DS1621plus:~# dd if=/dev/zero of=/volume5/dx513hdd/10gb.dump bs=1M count=10240; rm -f /volume5/dx513hdd/10gb.dump 10240+0 records in 10240+0 records out 10737418240 bytes (11 GB, 10 GiB) copied, 57.6258 s, 186 MB/s ``` Now I tried syno_enable_eunit.sh version 3.0.21. This Version does not disable NCQ for SSDs in DX. After a reboot, the result was the same as before: all LEDs eventually became solid. Now things get interesting... I ran the write test for 10GB on the SSD SHR volume of the DX513, just like before... After a few seconds the command was executed, the SSD volume crashed and one of the SSD drive's LED turned orange. <img width="1214" height="866" alt="Image" src="https://github.com/user-attachments/assets/c86ab925-0324-40fb-8180-3019270ae3ff" /> @007revad so please also disable NCQ for SSDs in DX expansion units that do not support NCQ, so please don't publish version 3.0.21 as it is.

kerem commented

Author

Owner

@steinreiter commented on GitHub (Sep 18, 2025):

Okay, let's move on to the next problem: my own code snippet from above, which allows you to identify the drives of a DX expansion unit and then disable NCQ for each drive.

This snippet works as long as only one expansion unit of a given type is connected. So, a DX213 and a DX513 work at the same time. What if you have two identical expansion units connected? Then it doesn't work, and NCQ would only be disabled for the drives of the first expansion unit of a type found.

Today I borrowed a second DX213 from a friend and revised the code snippet. This one also works, regardless of how many expansion units of the same type are connected.

DX_NAME=DX213   #capitalization of the name is important
DX_DISK_NUM=2   #max number of disks supported by the expansion unit

DX_DISKS=$(syno_disk_dump | grep "^Eunit disk info: $DX_NAME\$" -A $DX_DISK_NUM | cut -d: -f2 | cut -f1 | xargs -L1 | grep -v "^$DX_NAME\$")

for dx_disk in $DX_DISKS; do
  syno_disk_ctl --ncq-off $dx_disk
done

@007revad , I would be happy if you included it in your script.

I also have another request. Would it be possible to adapt syno_enable_eunit.sh so that you can specify multiple expansion units simultaneously using the "unit" parameter? Then you wouldn't have to run the script multiple times in succession for different connected expansion units.

@steinreiter commented on GitHub (Sep 18, 2025): Okay, let's move on to the next problem: my own code snippet from above, which allows you to identify the drives of a DX expansion unit and then disable NCQ for each drive. This snippet works as long as only one expansion unit of a given type is connected. So, a DX213 and a DX513 work at the same time. What if you have two identical expansion units connected? Then it doesn't work, and NCQ would only be disabled for the drives of the first expansion unit of a type found. Today I borrowed a second DX213 from a friend and revised the code snippet. This one also works, regardless of how many expansion units of the same type are connected. ``` DX_NAME=DX213 #capitalization of the name is important DX_DISK_NUM=2 #max number of disks supported by the expansion unit DX_DISKS=$(syno_disk_dump | grep "^Eunit disk info: $DX_NAME\$" -A $DX_DISK_NUM | cut -d: -f2 | cut -f1 | xargs -L1 | grep -v "^$DX_NAME\$") for dx_disk in $DX_DISKS; do syno_disk_ctl --ncq-off $dx_disk done ``` @007revad , I would be happy if you included it in your script. I also have another request. Would it be possible to adapt syno_enable_eunit.sh so that you can specify multiple expansion units simultaneously using the "unit" parameter? Then you wouldn't have to run the script multiple times in succession for different connected expansion units.

kerem commented

Author

Owner

@steinreiter commented on GitHub (Sep 18, 2025):

well darn. today on startup I got the high response error messages again (Dave'prior version script, and my adapted ver of steinreiter's NCQ disable. At least I didn't see an offline disk and RAID rebuild requirement. I will move to Dave's new script and test that out.
I swapped over to 3.20 and unfortunately I had a repeat of the high response time errors, plus this time I have an unhappy disk and had to repair the volume after remove and a further reboot. I checkedd the email log and it ran w/o error and did the NCQ disable.

@mervincm, Is it possible that heavy tasks are running on the drives of your DX513 directly after boot before the task scheduler manages to disable NCQ for the drives via the script?

I'm going to completely disassemble my DX513 in the next few days, clean it of dust, and install new fans with modified pins. While I'm at it, I'll take a look at the printed PCB revision. Then you could compare it with yours. I'm just saying, if they're different revisions, the behavior could perhaps be hardware-related?! After all, the crazy blinking behavior of your DX513 in your video is significantly slower than on my DX513, or rather, what I mean is that on my DX513, the pause times of 3 Seconds where the LEDs stop blinking during a link reset of all drives are significantly shorter than on yours.

@steinreiter commented on GitHub (Sep 18, 2025): > well darn. today on startup I got the high response error messages again (Dave'prior version script, and my adapted ver of steinreiter's NCQ disable. At least I didn't see an offline disk and RAID rebuild requirement. I will move to Dave's new script and test that out. > I swapped over to 3.20 and unfortunately I had a repeat of the high response time errors, plus this time I have an unhappy disk and had to repair the volume after remove and a further reboot. I checkedd the email log and it ran w/o error and did the NCQ disable. @mervincm, Is it possible that heavy tasks are running on the drives of your DX513 directly after boot before the task scheduler manages to disable NCQ for the drives via the script? I'm going to completely disassemble my DX513 in the next few days, clean it of dust, and install new fans with modified pins. While I'm at it, I'll take a look at the printed PCB revision. Then you could compare it with yours. I'm just saying, if they're different revisions, the behavior could perhaps be hardware-related?! After all, the crazy blinking behavior of your DX513 in your video is significantly slower than on my DX513, or rather, what I mean is that on my DX513, the pause times of 3 Seconds where the LEDs stop blinking during a link reset of all drives are significantly shorter than on yours.

kerem commented

Author

Owner

@007revad commented on GitHub (Sep 18, 2025):

I've had reports from some people that their DX would not work and it turned out the eSATA cable was not making a reliable connection. Blowing the dust out of the eSATA ports and unplugging then reconnecting the eSATA cable (at both ends) got it working. Last night I was wondering if this may be the cause of the "works for while" issue.

@007revad commented on GitHub (Sep 18, 2025): I've had reports from some people that their DX would not work and it turned out the eSATA cable was not making a reliable connection. Blowing the dust out of the eSATA ports and unplugging then reconnecting the eSATA cable (at both ends) got it working. Last night I was wondering if this may be the cause of the "works for while" issue.

kerem commented

Author

Owner

@007revad commented on GitHub (Sep 18, 2025):

Today I borrowed a second DX213 from a friend and revised the code snippet. This one also works, regardless of how many expansion units of the same type are connected.

I would be happy if you included it in your script.

Done. See https://github.com/007revad/Synology_enable_eunit/releases/tag/v3.0.22

I also have another request. Would it be possible to adapt syno_enable_eunit.sh so that you can specify multiple expansion units simultaneously using the "unit" parameter? Then you wouldn't have to run the script multiple times in succession for different connected expansion units.

I thought it did already, but I just checked and I'm surprised it doesn't. I'll add that today.

@007revad commented on GitHub (Sep 18, 2025): > Today I borrowed a second DX213 from a friend and revised the code snippet. This one also works, regardless of how many expansion units of the same type are connected. > > I would be happy if you included it in your script. Done. See https://github.com/007revad/Synology_enable_eunit/releases/tag/v3.0.22 > I also have another request. Would it be possible to adapt syno_enable_eunit.sh so that you can specify multiple expansion units simultaneously using the "unit" parameter? Then you wouldn't have to run the script multiple times in succession for different connected expansion units. I thought it did already, but I just checked and I'm surprised it doesn't. I'll add that today.

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 18, 2025):

@mervincm, Is it possible that heavy tasks are running on the drives of your DX513 directly after boot before the task scheduler manages to disable NCQ for the drives via the script?

I only ever see issues at startup. if there are heavy tasks that exec at startup before a scheduled task executes ... I am not sure how to know that.

All of my scripting is done as scheduled task and as a user defined script and scheduled for boot-up. so they run every time I reboot.
Right now I have Dave's enable external units run first, then I have his HDD_db run

I'm going to completely disassemble my DX513 in the next few days, clean it of dust, and install new fans with modified pins. While I'm at it, I'll take a look at the printed PCB revision. Then you could compare it with yours. I'm just saying, if they're different revisions, the behavior could perhaps be hardware-related?! After all, the crazy blinking behavior of your DX513 in your video is significantly slower than on my DX513, or rather, what I mean is that on my DX513, the pause times of 3 Seconds where the LEDs stop blinking during a link reset of all drives are significantly shorter than on yours.

I cleaned mine completely about a month back when I started having these issues. All contacts on it, the eSATA cable, and my 1821+ were dusted, cleaned with isopropyl alcohol, inspected for damages components, and contacts done with CAIG Labs Deoxitgold G5 contact cleaner. I will gladly check any version numbers / serial numbers. I do have to wait at least one more day as my volume rebuild is under way.

@mervincm commented on GitHub (Sep 18, 2025): > [@mervincm](https://github.com/mervincm), Is it possible that heavy tasks are running on the drives of your DX513 directly after boot before the task scheduler manages to disable NCQ for the drives via the script? I only ever see issues at startup. if there are heavy tasks that exec at startup before a scheduled task executes ... I am not sure how to know that. All of my scripting is done as scheduled task and as a user defined script and scheduled for boot-up. so they run every time I reboot. Right now I have Dave's enable external units run first, then I have his HDD_db run > I'm going to completely disassemble my DX513 in the next few days, clean it of dust, and install new fans with modified pins. While I'm at it, I'll take a look at the printed PCB revision. Then you could compare it with yours. I'm just saying, if they're different revisions, the behavior could perhaps be hardware-related?! After all, the crazy blinking behavior of your DX513 in your video is significantly slower than on my DX513, or rather, what I mean is that on my DX513, the pause times of 3 Seconds where the LEDs stop blinking during a link reset of all drives are significantly shorter than on yours. I cleaned mine completely about a month back when I started having these issues. All contacts on it, the eSATA cable, and my 1821+ were dusted, cleaned with isopropyl alcohol, inspected for damages components, and contacts done with CAIG Labs Deoxitgold G5 contact cleaner. I will gladly check any version numbers / serial numbers. I do have to wait at least one more day as my volume rebuild is under way.

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 18, 2025):

I've had reports from some people that their DX would not work and it turned out the eSATA cable was not making a reliable connection. Blowing the dust out of the eSATA ports and unplugging then reconnecting the eSATA cable (at both ends) got it working. Last night I was wondering if this may be the cause of the "works for while" issue.

If only :) All contacts , cable plus NAS / expansion where blown with canned air, inspected for damage, and treated with contact cleaned. I also did the expansion unit backplane. This DX513 Unit/Cable worked well enough on the DS1815+ I also tried another shielded eSATA (non-Synology) cable that exhibited the same behavior.

@mervincm commented on GitHub (Sep 18, 2025): > I've had reports from some people that their DX would not work and it turned out the eSATA cable was not making a reliable connection. Blowing the dust out of the eSATA ports and unplugging then reconnecting the eSATA cable (at both ends) got it working. Last night I was wondering if this may be the cause of the "works for while" issue. If only :) All contacts , cable plus NAS / expansion where blown with canned air, inspected for damage, and treated with contact cleaned. I also did the expansion unit backplane. This DX513 Unit/Cable worked well enough on the DS1815+ I also tried another shielded eSATA (non-Synology) cable that exhibited the same behavior.

kerem commented

Author

Owner

@007revad commented on GitHub (Sep 18, 2025):

Thanks @mervincm At least we can rule that out.

@007revad commented on GitHub (Sep 18, 2025): Thanks @mervincm At least we can rule that out.

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 18, 2025):

OK. I noticed that my rebuild was complete and it was moved on to the data scrubbing, so I decided I could always complete that piece later. I updated to 3.022 and restarted, and I was able to startup (after the light dance my video shows) without any high response errors, or any failed volumes / disks. I will SSH in and see if I can use the command lines from above to grep for sata error messages and update.

@mervincm commented on GitHub (Sep 18, 2025): OK. I noticed that my rebuild was complete and it was moved on to the data scrubbing, so I decided I could always complete that piece later. I updated to 3.022 and restarted, and I was able to startup (after the light dance my video shows) without any high response errors, or any failed volumes / disks. I will SSH in and see if I can use the command lines from above to grep for sata error messages and update.

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 18, 2025):

dmesg | grep -i ata
[ 6.223231] ahci 0000:0a:00.0: AHCI 0001.0301 32 slots 5 ports 6 Gbps 0x1f i mpl SATA mode
[ 6.366972] ahci 0000:0a:00.0: JMB585 port=0, reg_addr=0x4, reg_data=0xae8
[ 6.473942] ahci 0000:0a:00.0: JMB585 port=1, reg_addr=0x11, reg_data=0xae5
[ 6.580986] ahci 0000:0a:00.0: JMB585 port=2, reg_addr=0x1e, reg_data=0xae5
[ 6.688032] ahci 0000:0a:00.0: JMB585 port=3, reg_addr=0x2b, reg_data=0xae5
[ 6.795078] ahci 0000:0a:00.0: JMB585 port=4, reg_addr=0x38, reg_data=0xae5
[ 6.902123] ahci 0000:0a:00.0: JMB585 port=0, reg_addr=0x73, reg_data=0x1e4
[ 7.009168] ahci 0000:0a:00.0: JMB585 port=1, reg_addr=0x75, reg_data=0x1e4
[ 7.116212] ahci 0000:0a:00.0: JMB585 port=2, reg_addr=0x77, reg_data=0x1e5
[ 7.223255] ahci 0000:0a:00.0: JMB585 port=3, reg_addr=0x79, reg_data=0x1e4
[ 7.330301] ahci 0000:0a:00.0: JMB585 port=4, reg_addr=0x7b, reg_data=0x1e5
[ 7.359246] ata1 : SATA max UDMA/133 abar m8192@0xd2700000 port 0xd2700100 i rq 302
[ 7.366864] ata2 : SATA max UDMA/133 abar m8192@0xd2700000 port 0xd2700180 i rq 303
[ 7.374437] ata3 : SATA max UDMA/133 abar m8192@0xd2700000 port 0xd2700200 i rq 304
[ 7.382008] ata4 : SATA max UDMA/133 abar m8192@0xd2700000 port 0xd2700280 i rq 305
[ 7.389584] ata5 : SATA max UDMA/133 abar m8192@0xd2700000 port 0xd2700300 i rq 306
[ 7.404147] ahci 0000:0b:00.0: AHCI 0001.0301 32 slots 5 ports 6 Gbps 0x1f i mpl SATA mode
[ 7.547836] ahci 0000:0b:00.0: JMB585 port=0, reg_addr=0x4, reg_data=0xae8
[ 7.654770] ahci 0000:0b:00.0: JMB585 port=1, reg_addr=0x11, reg_data=0xae5
[ 7.761785] ahci 0000:0b:00.0: JMB585 port=2, reg_addr=0x1e, reg_data=0xae5
[ 7.868801] ahci 0000:0b:00.0: JMB585 port=3, reg_addr=0x2b, reg_data=0x7e5
[ 7.975817] ahci 0000:0b:00.0: JMB585 port=4, reg_addr=0x38, reg_data=0x7e5
[ 8.082834] ahci 0000:0b:00.0: JMB585 port=0, reg_addr=0x73, reg_data=0x1e4
[ 8.189850] ahci 0000:0b:00.0: JMB585 port=1, reg_addr=0x75, reg_data=0x1e4
[ 8.296870] ahci 0000:0b:00.0: JMB585 port=2, reg_addr=0x77, reg_data=0x1e5
[ 8.403888] ahci 0000:0b:00.0: JMB585 port=3, reg_addr=0x79, reg_data=0x1e4
[ 8.510905] ahci 0000:0b:00.0: JMB585 port=4, reg_addr=0x7b, reg_data=0x1e5
[ 8.541187] ata6 : SATA max UDMA/133 abar m8192@0xd2600000 port 0xd2600100 i rq 325
[ 8.548770] ata7 : SATA max UDMA/133 abar m8192@0xd2600000 port 0xd2600180 i rq 326
[ 8.556339] ata8 : SATA max UDMA/133 abar m8192@0xd2600000 port 0xd2600200 i rq 327
[ 8.563904] ata9 : SATA max UDMA/133 abar m8192@0xd2600000 port 0xd2600280 i rq 328
[ 8.571469] ata10 : SATA max UDMA/133 abar m8192@0xd2600000 port 0xd2600300 irq 329
[ 11.694318] ata1 : SATA link down (SStatus 0 SControl 300)
[ 11.699813] ata1 : No present pin info for SATA link down event
[ 11.849312] ata6 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 11.855974] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1)
[ 11.861777] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1)
[ 12.898969] ata6.15 : Port Multiplier 1.1, 0x1095:0x3726 r23, 5 ports, feat 0x1/0x9
[ 12.998618] ata6 : Apply Synology fast PMP boot
[ 13.379655] ata10 (slot 8): SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 13.390971] ata10.00 (slot 8): disabling queued TRIM support
[ 13.390977] ata10.00 (slot 8): ATA-9: WDC WD80EFBX-68AZZN0, 85.00A85, max UD MA/133
[ 13.398551] ata10.00 (slot 8): 15628053168 sectors, multi 0: LBA48 NCQ (dept h 31/32), AA
[ 13.406640] ata10.00 (slot 8): SN:VYG80Z6M
[ 13.417605] ata10.00 (slot 8): disabling queued TRIM support
[ 13.417609] ata10.00 (slot 8): configured for UDMA/133
[ 14.528443] ata6.01 : hard resetting link
[ 15.002148] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 15.008772] ata6.02 : hard resetting link
[ 15.482427] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 15.489051] ata6.03 : hard resetting link
[ 15.963269] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 15.969856] ata6.04 : hard resetting link
[ 16.278511] ata6.04 : SATA link down (SStatus 0 SControl 320)
[ 16.284275] ata6 : No present pin info for SATA link down event
[ 16.886136] ata5 (slot 4): link is slow to respond, please be patient (ready =-19)
[ 16.893625] ata2 (slot 1): link is slow to respond, please be patient (ready =-19)
[ 16.922136] ata4 (slot 3): link is slow to respond, please be patient (ready =-19)
[ 16.963131] ata3 (slot 2): link is slow to respond, please be patient (ready =-19)
[ 18.291839] ata6.00 : hard resetting link
[ 18.295886] ata8 (slot 6): link is slow to respond, please be patient (ready =-19)
[ 18.303443] ata9 (slot 7): link is slow to respond, please be patient (ready =-19)
[ 18.310981] ata7 (slot 5): link is slow to respond, please be patient (ready =-19)
[ 18.787694] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 18.794787] ata6.00 : supports DRM functions and may not be fully accessible
[ 21.687419] ata5 (slot 4): SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 21.694399] ata5.00 (slot 4): link online but device misclassified
[ 21.694401] ata5 (slot 4): link online but 1 devices misclassified, retrying
[ 21.701472] ata2 (slot 1): SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 21.708441] ata2.00 (slot 1): link online but device misclassified
[ 21.708443] ata2 (slot 1): link online but 1 devices misclassified, retrying
[ 21.764012] ata3 (slot 2): SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 21.770976] ata3.00 (slot 2): link online but device misclassified
[ 21.770977] ata3 (slot 2): link online but 1 devices misclassified, retrying
[ 21.771246] ata8 (slot 6): SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 21.771253] ata8.00 (slot 6): link online but device misclassified
[ 21.771255] ata8 (slot 6): link online but 1 devices misclassified, retrying
[ 21.778036] ata9 (slot 7): SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 21.778044] ata9.00 (slot 7): link online but device misclassified
[ 21.778045] ata9 (slot 7): link online but 1 devices misclassified, retrying
[ 21.790039] ata7 (slot 5): SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 21.790047] ata7.00 (slot 5): link online but device misclassified
[ 21.790049] ata7 (slot 5): link online but 1 devices misclassified, retrying
[ 21.820068] ata4 (slot 3): SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 21.827040] ata4.00 (slot 3): link online but device misclassified
[ 21.827043] ata4 (slot 3): link online but 1 devices misclassified, retrying
[ 27.067257] ata5 (slot 4): link is slow to respond, please be patient (ready =-19)
[ 27.074750] ata2 (slot 1): link is slow to respond, please be patient (ready =-19)
[ 27.125256] ata8 (slot 6): link is slow to respond, please be patient (ready =-19)
[ 27.132753] ata9 (slot 7): link is slow to respond, please be patient (ready =-19)
[ 27.144255] ata7 (slot 5): link is slow to respond, please be patient (ready =-19)
[ 27.185898] ata3 (slot 2): link is slow to respond, please be patient (ready =-19)
[ 27.193389] ata4 (slot 3): link is slow to respond, please be patient (ready =-19)
[ 29.796330] ata3 (slot 2): SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 29.819855] ata3.00 (slot 2): disabling queued TRIM support
[ 29.819858] ata3.00 (slot 2): ATA-10: ST8000VN0022-2EL112, SC61, max UDMA/13 3
[ 29.826997] ata3.00 (slot 2): 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 29.834998] ata3.00 (slot 2): SN: ZA181JX3
[ 29.843174] ata3.00 (slot 2): disabling queued TRIM support
[ 29.843179] ata3.00 (slot 2): configured for UDMA/133
[ 29.939814] ata2 (slot 1): SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 29.949921] ata2.00 (slot 1): disabling queued TRIM support
[ 29.949926] ata2.00 (slot 1): ATA-10: ST8000VN0022-2EL112, SC61, max UDMA/13 3
[ 29.957090] ata2.00 (slot 1): 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 29.965094] ata2.00 (slot 1): SN: ZA1CQQYS
[ 29.973090] ata2.00 (slot 1): disabling queued TRIM support
[ 29.973095] ata2.00 (slot 1): configured for UDMA/133
[ 29.981133] scsi 1:0:0:0: Direct-Access ATA ST8000VN0022-2EL112 SC61 PQ: 0 ANSI: 5
[ 29.990196] got SATA disk[0]
[ 29.993179] sd 1:0:0:0: [sata1] 15628053168 512-byte logical blocks: (8.00 T B/7.28 TiB)
[ 29.997595] scsi 2:0:0:0: Direct-Access ATA ST8000VN0022-2EL112 SC61 PQ: 0 ANSI: 5
[ 29.997897] got SATA disk[1]
[ 29.997975] sd 2:0:0:0: [sata2] 15628053168 512-byte logical blocks: (8.00 T B/7.28 TiB)
[ 29.997977] sd 2:0:0:0: [sata2] 4096-byte physical blocks
[ 29.998018] sd 2:0:0:0: [sata2] Write Protect is off
[ 29.998021] sd 2:0:0:0: [sata2] Mode Sense: 00 3a 00 10
[ 29.998040] sd 2:0:0:0: [sata2] Write cache: enabled, read cache: enabled, s upports DPO and FUA
[ 30.044813] sd 1:0:0:0: [sata1] 4096-byte physical blocks
[ 30.050278] sata2: p1 p2 p5
[ 30.050313] sd 1:0:0:0: [sata1] Write Protect is off
[ 30.050317] sd 1:0:0:0: [sata1] Mode Sense: 00 3a 00 10
[ 30.050340] sd 1:0:0:0: [sata1] Write cache: enabled, read cache: enabled, s upports DPO and FUA
[ 30.067193] sd 2:0:0:0: [sata2] Attached SCSI disk
[ 30.110049] sata1: p1 p2 p5
[ 30.113269] sd 1:0:0:0: [sata1] Attached SCSI disk
[ 30.267993] ata6.00 : disabling queued TRIM support
[ 30.267999] ata6.00 : ATA-9: WDC WD80EDAZ-11TA3A0, 81.00A81, max UDMA/133
[ 30.274798] ata6.00 : 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 30.282102] ata6.00 : SN:VGJ9829G
[ 30.391083] ata6.00 : supports DRM functions and may not be fully accessible
[ 30.402773] ata6.00 : disabling queued TRIM support
[ 30.402779] ata6.00 : configured for UDMA/133
[ 30.407671] ata6.01 : supports DRM functions and may not be fully accessible
[ 30.584167] ata4 (slot 3): SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 30.594648] ata4.00 (slot 3): disabling queued TRIM support
[ 30.594654] ata4.00 (slot 3): ATA-10: ST8000VN0022-2EL112, SC61, max UDMA/13 3
[ 30.601795] ata4.00 (slot 3): 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 30.609793] ata4.00 (slot 3): SN: ZA19ZCSS
[ 30.617797] ata4.00 (slot 3): disabling queued TRIM support
[ 30.617803] ata4.00 (slot 3): configured for UDMA/133
[ 30.625839] scsi 3:0:0:0: Direct-Access ATA ST8000VN0022-2EL112 SC61 PQ: 0 ANSI: 5
[ 30.635123] got SATA disk[2]
[ 30.638100] sd 3:0:0:0: [sata3] 15628053168 512-byte logical blocks: (8.00 T B/7.28 TiB)
[ 30.646115] sd 3:0:0:0: [sata3] 4096-byte physical blocks
[ 30.651683] sd 3:0:0:0: [sata3] Write Protect is off
[ 30.656664] sd 3:0:0:0: [sata3] Mode Sense: 00 3a 00 10
[ 30.656725] sd 3:0:0:0: [sata3] Write cache: enabled, read cache: enabled, s upports DPO and FUA
[ 30.718240] sata3: p1 p2 p5
[ 30.721430] sd 3:0:0:0: [sata3] Attached SCSI disk
[ 31.229150] ata5 (slot 4): SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 31.239648] ata5.00 (slot 4): disabling queued TRIM support
[ 31.239655] ata5.00 (slot 4): ATA-10: ST8000VN0022-2EL112, SC61, max UDMA/13 3
[ 31.246801] ata5.00 (slot 4): 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 31.254799] ata5.00 (slot 4): SN: ZA19ZCYL
[ 31.262820] ata5.00 (slot 4): disabling queued TRIM support
[ 31.262825] ata5.00 (slot 4): configured for UDMA/133
[ 31.270903] scsi 4:0:0:0: Direct-Access ATA ST8000VN0022-2EL112 SC61 PQ: 0 ANSI: 5
[ 31.280213] got SATA disk[3]
[ 31.283256] sd 4:0:0:0: [sata4] 15628053168 512-byte logical blocks: (8.00 T B/7.28 TiB)
[ 31.291279] sd 4:0:0:0: [sata4] 4096-byte physical blocks
[ 31.296850] sd 4:0:0:0: [sata4] Write Protect is off
[ 31.301838] sd 4:0:0:0: [sata4] Mode Sense: 00 3a 00 10
[ 31.301889] sd 4:0:0:0: [sata4] Write cache: enabled, read cache: enabled, s upports DPO and FUA
[ 31.372871] sata4: p1 p2 p5
[ 31.376146] sd 4:0:0:0: [sata4] Attached SCSI disk
[ 31.743138] ata9 (slot 7): SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 31.753645] ata9.00 (slot 7): disabling queued TRIM support
[ 31.753654] ata9.00 (slot 7): ATA-10: ST8000VN0022-2EL112, SC61, max UDMA/13 3
[ 31.760802] ata9.00 (slot 7): 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 31.768798] ata9.00 (slot 7): SN: ZA1D91C1
[ 31.776821] ata9.00 (slot 7): disabling queued TRIM support
[ 31.776826] ata9.00 (slot 7): configured for UDMA/133
[ 31.796766] ata7 (slot 5): SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 31.813105] ata7.00 (slot 5): disabling queued TRIM support
[ 31.813111] ata7.00 (slot 5): ATA-10: ST8000VN0022-2EL112, SC61, max UDMA/13 3
[ 31.820251] ata7.00 (slot 5): 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 31.828247] ata7.00 (slot 5): SN: ZA1E9QJL
[ 31.836276] ata7.00 (slot 5): disabling queued TRIM support
[ 31.836281] ata7.00 (slot 5): configured for UDMA/133
[ 31.935131] ata8 (slot 6): SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 31.942106] ata8.00 (slot 6): link online but device misclassified
[ 31.942108] ata8 (slot 6): link online but 1 devices misclassified, retrying
[ 32.409121] ata8 (slot 6): SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 32.432387] ata8.00 (slot 6): disabling queued TRIM support
[ 32.432394] ata8.00 (slot 6): ATA-10: ST8000VN0022-2EL112, SC61, max UDMA/13 3
[ 32.439543] ata8.00 (slot 6): 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 32.447541] ata8.00 (slot 6): SN: ZA1DEE37
[ 32.455576] ata8.00 (slot 6): disabling queued TRIM support
[ 32.455580] ata8.00 (slot 6): configured for UDMA/133
[ 41.654370] ata6.01 : disabling queued TRIM support
[ 41.654378] ata6.01 : ATA-9: WDC WD80EDBZ-11B0ZA0, 85.00A85, max UDMA/133
[ 41.661204] ata6.01 : 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 41.668512] ata6.01 : SN:VRGG9WKK
[ 41.785706] ata6.01 : supports DRM functions and may not be fully accessible
[ 41.796897] ata6.01 : disabling queued TRIM support
[ 41.796909] ata6.01 : configured for UDMA/133
[ 41.801786] ata6.02 : supports DRM functions and may not be fully accessible
[ 53.230709] ata6.02 : disabling queued TRIM support
[ 53.230718] ata6.02 : ATA-9: WDC WD80EDBZ-11B0ZA0, 85.00A85, max UDMA/133
[ 53.237537] ata6.02 : 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 53.244848] ata6.02 : SN:VRGKPYGK
[ 53.366175] ata6.02 : supports DRM functions and may not be fully accessible
[ 53.377354] ata6.02 : disabling queued TRIM support
[ 53.377368] ata6.02 : configured for UDMA/133
[ 64.705070] ata6.03 : disabling queued TRIM support
[ 64.705078] ata6.03 : ATA-9: WDC WD80EFBX-68AZZN0, 85.00A85, max UDMA/133
[ 64.711894] ata6.03 : 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 64.719204] ata6.03 : SN:VYG7YL5M
[ 64.838673] ata6.03 : disabling queued TRIM support
[ 64.838685] ata6.03 : configured for UDMA/133
[ 64.843141] ata6 : EH complete
[ 64.887912] got SATA disk[4]
[ 64.890964] sd 5:0:0:0: [sata5] 15628053168 512-byte logical blocks: (8.00 T B/7.28 TiB)
[ 64.899058] sd 5:0:0:0: [sata5] 4096-byte physical blocks
[ 64.899447] got SATA disk[5]
[ 64.899568] sd 5:1:0:0: [sata6] 15628053168 512-byte logical blocks: (8.00 T B/7.28 TiB)
[ 64.899570] sd 5:1:0:0: [sata6] 4096-byte physical blocks
[ 64.899614] sd 5:1:0:0: [sata6] Write Protect is off
[ 64.899617] sd 5:1:0:0: [sata6] Mode Sense: 00 3a 00 10
[ 64.899636] sd 5:1:0:0: [sata6] Write cache: enabled, read cache: enabled, s upports DPO and FUA
[ 64.900217] got SATA disk[6]
[ 64.900312] sd 5:2:0:0: [sata7] 15628053168 512-byte logical blocks: (8.00 T B/7.28 TiB)
[ 64.900315] sd 5:2:0:0: [sata7] 4096-byte physical blocks
[ 64.900354] sd 5:2:0:0: [sata7] Write Protect is off
[ 64.900356] sd 5:2:0:0: [sata7] Mode Sense: 00 3a 00 10
[ 64.900372] sd 5:2:0:0: [sata7] Write cache: enabled, read cache: enabled, s upports DPO and FUA
[ 64.902306] got SATA disk[7]
[ 64.902496] sd 5:3:0:0: [sata8] 15628053168 512-byte logical blocks: (8.00 T B/7.28 TiB)
[ 64.902499] sd 5:3:0:0: [sata8] 4096-byte physical blocks
[ 64.902541] sd 5:3:0:0: [sata8] Write Protect is off
[ 64.902544] sd 5:3:0:0: [sata8] Mode Sense: 00 3a 00 10
[ 64.902561] sd 5:3:0:0: [sata8] Write cache: enabled, read cache: enabled, s upports DPO and FUA
[ 64.948472] sata7: p1 p2 p5
[ 64.948844] sd 5:2:0:0: [sata7] Attached SCSI disk
[ 64.952790] sata6: p1 p2 p5
[ 64.953307] sd 5:1:0:0: [sata6] Attached SCSI disk
[ 64.959030] sata8: p1 p2 p5
[ 64.959475] sd 5:3:0:0: [sata8] Attached SCSI disk
[ 65.043995] scsi 6:0:0:0: Direct-Access ATA ST8000VN0022-2EL112 SC61 PQ: 0 ANSI: 5
[ 65.044067] sd 5:0:0:0: [sata5] Write Protect is off
[ 65.044070] sd 5:0:0:0: [sata5] Mode Sense: 00 3a 00 10
[ 65.044095] sd 5:0:0:0: [sata5] Write cache: enabled, read cache: enabled, s upports DPO and FUA
[ 65.066724] got SATA disk[8]
[ 65.069747] sd 6:0:0:0: [sata9] 15628053168 512-byte logical blocks: (8.00 T B/7.28 TiB)
[ 65.077824] sd 6:0:0:0: [sata9] 4096-byte physical blocks
[ 65.083334] sd 6:0:0:0: [sata9] Write Protect is off
[ 65.088317] sd 6:0:0:0: [sata9] Mode Sense: 00 3a 00 10
[ 65.088352] scsi 7:0:0:0: Direct-Access ATA ST8000VN0022-2EL112 SC61 PQ: 0 ANSI: 5
[ 65.088360] sd 6:0:0:0: [sata9] Write cache: enabled, read cache: enabled, s upports DPO and FUA
[ 65.096417] sata5: p1 p2 p5
[ 65.096756] sd 5:0:0:0: [sata5] Attached SCSI disk
[ 65.113879] got SATA disk[9]
[ 65.116898] sd 7:0:0:0: [sata10] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
[ 65.124997] sd 7:0:0:0: [sata10] 4096-byte physical blocks
[ 65.129871] scsi 8:0:0:0: Direct-Access ATA ST8000VN0022-2EL112 SC61 PQ: 0 ANSI: 5
[ 65.130227] got SATA disk[10]
[ 65.130328] sd 8:0:0:0: [sata11] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
[ 65.130331] sd 8:0:0:0: [sata11] 4096-byte physical blocks
[ 65.130390] sd 8:0:0:0: [sata11] Write Protect is off
[ 65.130393] sd 8:0:0:0: [sata11] Mode Sense: 00 3a 00 10
[ 65.130413] sd 8:0:0:0: [sata11] Write cache: enabled, read cache: enabled, supports DPO and FUA
[ 65.131139] got SATA disk[11]
[ 65.131225] sd 9:0:0:0: [sata12] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
[ 65.131228] sd 9:0:0:0: [sata12] 4096-byte physical blocks
[ 65.131268] sd 9:0:0:0: [sata12] Write Protect is off
[ 65.131271] sd 9:0:0:0: [sata12] Mode Sense: 00 3a 00 10
[ 65.131287] sd 9:0:0:0: [sata12] Write cache: enabled, read cache: enabled, supports DPO and FUA
[ 65.152914] sata9: p1 p2 p5
[ 65.153214] sd 6:0:0:0: [sata9] Attached SCSI disk
[ 65.184901] sata12: p1 p2 p5
[ 65.185253] sd 9:0:0:0: [sata12] Attached SCSI disk
[ 65.187030] sata11: p1 p2 p5
[ 65.187470] sd 8:0:0:0: [sata11] Attached SCSI disk
[ 65.232578] sd 7:0:0:0: [sata10] Write Protect is off
[ 65.237640] sd 7:0:0:0: [sata10] Mode Sense: 00 3a 00 10
[ 65.237668] sd 7:0:0:0: [sata10] Write cache: enabled, read cache: enabled, supports DPO and FUA
[ 65.313113] sata10: p1 p2 p5
[ 65.316415] sd 7:0:0:0: [sata10] Attached SCSI disk
[ 65.327751] Write protecting the kernel read-only data: 8192k
[ 66.444467] md: bind
[ 66.448683] md: bind
[ 66.451868] md: bind
[ 66.455044] md: bind
[ 66.458187] md: bind
[ 66.461417] md: bind
[ 66.464591] md: bind
[ 66.467808] md: bind
[ 67.814934] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[ 67.920066] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: prjquota,rootprjquota,barrier=1
[ 72.397396] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[ 72.715468] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: prjquota,rootprjquota,barrier=1
[ 75.646845] acpi-cpufreq: overriding BIOS provided _PSD data
[ 76.484885] md: bind
[ 76.485065] md: bind
[ 76.496051] md: bind
[ 76.499185] md: bind
[ 76.513559] md: bind
[ 76.528022] md: bind
[ 76.540947] md: bind
[ 76.553064] md: bind
[ 79.231405] ata6.00 : failed to read SCR 1 (Emask=0x40)
[ 79.236661] ata6.01 : failed to read SCR 1 (Emask=0x40)
[ 79.241945] ata6.02 : failed to read SCR 1 (Emask=0x40)
[ 79.247199] ata6.03 : failed to read SCR 1 (Emask=0x40)
[ 79.252442] ata6.04 : failed to read SCR 1 (Emask=0x40)
[ 79.257694] ata6.00 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 79.265046] ata6.01 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 79.272399] ata6.02 : exception Emask 0x1 SAct 0x18 SErr 0x0 action 0x6 froz en
[ 79.279654] ata6.02 : failed command: READ FPDMA QUEUED
[ 79.284943] ata6.02 : cmd 60/08:18:10:35:7e/00:00:a3:03:00/40 tag 3 ncq 4096 in
[ 79.300072] ata6.02 : status: { DRDY }
[ 79.303856] ata6.02 : failed command: READ FPDMA QUEUED
[ 79.309146] ata6.02 : cmd 60/08:20:e0:5e:44/00:00:01:00:00/40 tag 4 ncq 4096 in
[ 79.324268] ata6.02 : status: { DRDY }
[ 79.328047] ata6.03 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 79.335386] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 79.342725] ata6.15 : hard resetting link
[ 80.061384] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 80.068112] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1)
[ 80.073977] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1)
[ 81.111316] ata6.01 : hard resetting link
[ 81.586887] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 81.593519] ata6.02 : hard resetting link
[ 82.066865] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 82.073475] ata6.03 : hard resetting link
[ 82.354935] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts : (null)
[ 82.549851] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 82.556471] ata6.04 : hard resetting link
[ 82.866561] ata6.04 : SATA link down (SStatus 0 SControl 320)
[ 82.873815] ata6 : No present pin info for SATA link down event
[ 84.886619] ata6.00 : hard resetting link
[ 85.363485] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 85.370627] ata6.00 : supports DRM functions and may not be fully accessible
[ 85.382217] ata6.00 : disabling queued TRIM support
[ 85.385907] ata6.00 : supports DRM functions and may not be fully accessible
[ 85.397754] ata6.00 : disabling queued TRIM support
[ 85.397759] ata6.00 : configured for UDMA/133
[ 85.402923] ata6.01 : supports DRM functions and may not be fully accessible
[ 85.413777] ata6.01 : disabling queued TRIM support
[ 85.417148] ata6.01 : supports DRM functions and may not be fully accessible
[ 85.428029] ata6.01 : disabling queued TRIM support
[ 85.428033] ata6.01 : configured for UDMA/133
[ 85.433071] ata6.02 : supports DRM functions and may not be fully accessible
[ 85.443826] ata6.02 : disabling queued TRIM support
[ 85.447078] ata6.02 : supports DRM functions and may not be fully accessible
[ 85.457837] ata6.02 : disabling queued TRIM support
[ 85.457841] ata6.02 : configured for UDMA/133
[ 85.475633] ata6.03 : disabling queued TRIM support
[ 85.489499] ata6.03 : disabling queued TRIM support
[ 85.489503] ata6.03 : configured for UDMA/133
[ 85.494075] ata6 : EH complete
[ 85.567239] ata6.00 : failed to read SCR 1 (Emask=0x40)
[ 85.572481] ata6.01 : failed to read SCR 1 (Emask=0x40)
[ 85.577726] ata6.02 : failed to read SCR 1 (Emask=0x40)
[ 85.582963] ata6.03 : failed to read SCR 1 (Emask=0x40)
[ 85.588196] ata6.04 : failed to read SCR 1 (Emask=0x40)
[ 85.593426] ata6.00 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 85.600746] ata6.01 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 85.608061] ata6.02 : exception Emask 0x1 SAct 0x30000 SErr 0x0 action 0x6 f rozen
[ 85.615546] ata6.02 : failed command: READ FPDMA QUEUED
[ 85.620775] ata6.02 : cmd 60/08:80:10:35:7e/00:00:a3:03:00/40 tag 16 ncq 409 6 in
[ 85.635972] ata6.02 : status: { DRDY }
[ 85.639728] ata6.02 : failed command: READ FPDMA QUEUED
[ 85.644959] ata6.02 : cmd 60/08:88:10:35:7e/00:00:a3:03:00/40 tag 17 ncq 409 6 in
[ 85.668151] ata6.02 : status: { DRDY }
[ 85.671912] ata6.03 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 85.679223] ata6.03 : failed command: READ LOG EXT
[ 85.684020] ata6.03 : cmd 2f/00:01:e0:00:00/00:00:00:00:00/00 tag 18 pio 512 in
[ 85.699389] ata6.03 : status: { DRDY }
[ 85.703145] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 85.710462] ata6.15 : hard resetting link
[ 86.430585] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 86.437380] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1)
[ 86.443399] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1)
[ 87.481231] ata6.01 : hard resetting link
[ 87.954126] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 87.960746] ata6.02 : hard resetting link
[ 88.434399] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 88.441033] ata6.03 : hard resetting link
[ 88.917662] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 88.924252] ata6.04 : hard resetting link
[ 89.234390] ata6.04 : SATA link down (SStatus 0 SControl 320)
[ 89.240165] ata6 : No present pin info for SATA link down event
[ 91.247751] ata6.00 : hard resetting link
[ 91.721576] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 91.728645] ata6.00 : supports DRM functions and may not be fully accessible
[ 91.740163] ata6.00 : disabling queued TRIM support
[ 91.743815] ata6.00 : supports DRM functions and may not be fully accessible
[ 91.755420] ata6.00 : disabling queued TRIM support
[ 91.755426] ata6.00 : configured for UDMA/133
[ 91.760316] ata6.01 : supports DRM functions and may not be fully accessible
[ 91.774572] ata6.01 : disabling queued TRIM support
[ 91.777953] ata6.01 : supports DRM functions and may not be fully accessible
[ 91.788867] ata6.01 : disabling queued TRIM support
[ 91.788871] ata6.01 : configured for UDMA/133
[ 91.793812] ata6.02 : supports DRM functions and may not be fully accessible
[ 91.804547] ata6.02 : disabling queued TRIM support
[ 91.807858] ata6.02 : supports DRM functions and may not be fully accessible
[ 91.818622] ata6.02 : disabling queued TRIM support
[ 91.818626] ata6.02 : configured for UDMA/133
[ 91.827375] ata6.03 : disabling queued TRIM support
[ 91.834382] ata6.03 : disabling queued TRIM support
[ 91.834386] ata6.03 : configured for UDMA/133
[ 91.838954] ata6 : EH complete
[ 92.415597] md: bind
[ 92.418784] md: bind
[ 92.421953] md: bind
[ 92.425119] md: bind
[ 92.428277] md: bind
[ 92.431516] md: bind
[ 92.434720] md: bind
[ 92.437988] md: bind
[ 92.516953] md/raid:md2: device sata1p5 operational as raid disk 0
[ 92.523144] md/raid:md2: device sata12p5 operational as raid disk 7
[ 92.529409] md/raid:md2: device sata11p5 operational as raid disk 6
[ 92.535676] md/raid:md2: device sata10p5 operational as raid disk 5
[ 92.541942] md/raid:md2: device sata9p5 operational as raid disk 4
[ 92.548122] md/raid:md2: device sata4p5 operational as raid disk 3
[ 92.554301] md/raid:md2: device sata3p5 operational as raid disk 2
[ 92.560478] md/raid:md2: device sata2p5 operational as raid disk 1
[ 92.579016] disk 0, o:1, dev:sata1p5
[ 92.579019] disk 1, o:1, dev:sata2p5
[ 92.579021] disk 2, o:1, dev:sata3p5
[ 92.579024] disk 3, o:1, dev:sata4p5
[ 92.579026] disk 4, o:1, dev:sata9p5
[ 92.579028] disk 5, o:1, dev:sata10p5
[ 92.579030] disk 6, o:1, dev:sata11p5
[ 92.579032] disk 7, o:1, dev:sata12p5
[ 92.628095] md: bind
[ 92.631269] md: bind
[ 92.634471] md: bind
[ 92.637676] md: bind
[ 92.643302] md/raid:md3: device sata5p5 operational as raid disk 0
[ 92.649498] md/raid:md3: device sata8p5 operational as raid disk 3
[ 92.655695] md/raid:md3: device sata7p5 operational as raid disk 2
[ 92.661886] md/raid:md3: device sata6p5 operational as raid disk 1
[ 92.680062] disk 0, o:1, dev:sata5p5
[ 92.680064] disk 1, o:1, dev:sata6p5
[ 92.680065] disk 2, o:1, dev:sata7p5
[ 92.680067] disk 3, o:1, dev:sata8p5
[ 92.768017] ata6.00 : failed to read SCR 1 (Emask=0x40)
[ 92.773264] ata6.01 : failed to read SCR 1 (Emask=0x40)
[ 92.778518] ata6.02 : failed to read SCR 1 (Emask=0x40)
[ 92.783751] ata6.03 : failed to read SCR 1 (Emask=0x40)
[ 92.788982] ata6.04 : failed to read SCR 1 (Emask=0x40)
[ 92.794226] ata6.00 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 92.801549] ata6.01 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 92.808861] ata6.02 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 92.816179] ata6.03 : exception Emask 0x1 SAct 0x28 SErr 0x0 action 0x6 froz en
[ 92.823403] ata6.03 : failed command: READ FPDMA QUEUED
[ 92.828635] ata6.03 : cmd 60/08:18:e8:5e:44/00:00:01:00:00/40 tag 3 ncq 4096 in
[ 92.843746] ata6.03 : status: { DRDY }
[ 92.847503] ata6.03 : failed command: READ FPDMA QUEUED
[ 92.852740] ata6.03 : cmd 60/01:28:e0:5e:44/00:00:01:00:00/40 tag 5 ncq 512 in
[ 92.867768] ata6.03 : status: { DRDY }
[ 92.871535] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 92.878849] ata6.15 : hard resetting link
[ 93.599041] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 93.606078] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1)
[ 93.611883] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1)
[ 94.649504] ata6.04 : limiting SATA link speed to 1.5 Gbps
[ 94.655031] ata6.01 : hard resetting link
[ 95.127557] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 95.134424] ata6.02 : hard resetting link
[ 95.607316] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 95.614151] ata6.03 : hard resetting link
[ 96.087595] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 96.094186] ata6.04 : hard resetting link
[ 96.403393] ata6.04 : SATA link down (SStatus 0 SControl 310)
[ 96.409155] ata6 : No present pin info for SATA link down event
[ 98.416829] ata6.00 : hard resetting link
[ 98.890875] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 98.898028] ata6.00 : supports DRM functions and may not be fully accessible
[ 98.909648] ata6.00 : disabling queued TRIM support
[ 98.913333] ata6.00 : supports DRM functions and may not be fully accessible
[ 98.924982] ata6.00 : disabling queued TRIM support
[ 98.924986] ata6.00 : configured for UDMA/133
[ 98.930011] ata6.01 : supports DRM functions and may not be fully accessible
[ 98.940856] ata6.01 : disabling queued TRIM support
[ 98.944310] ata6.01 : supports DRM functions and may not be fully accessible
[ 98.955169] ata6.01 : disabling queued TRIM support
[ 98.955172] ata6.01 : configured for UDMA/133
[ 98.960238] ata6.02 : supports DRM functions and may not be fully accessible
[ 98.970964] ata6.02 : disabling queued TRIM support
[ 98.974262] ata6.02 : supports DRM functions and may not be fully accessible
[ 98.985025] ata6.02 : disabling queued TRIM support
[ 98.985028] ata6.02 : configured for UDMA/133
[ 98.993801] ata6.03 : disabling queued TRIM support
[ 99.000813] ata6.03 : disabling queued TRIM support
[ 99.000816] ata6.03 : configured for UDMA/133
[ 99.005380] ata6 : EH complete
[ 99.929941] ata6.00 : failed to read SCR 1 (Emask=0x40)
[ 99.935183] ata6.01 : failed to read SCR 1 (Emask=0x40)
[ 99.940415] ata6.02 : failed to read SCR 1 (Emask=0x40)
[ 99.945645] ata6.03 : failed to read SCR 1 (Emask=0x40)
[ 99.950877] ata6.04 : failed to read SCR 1 (Emask=0x40)
[ 99.956111] ata6.00 : exception Emask 0x100 SAct 0x8000 SErr 0x0 action 0x6 frozen
[ 99.963686] ata6.00 : failed command: READ FPDMA QUEUED
[ 99.968922] ata6.00 : cmd 60/08:78:a8:2a:81/00:00:a3:03:00/40 tag 15 ncq 409 6 in
[ 99.984377] ata6.00 : status: { DRDY }
[ 99.988164] ata6.01 : exception Emask 0x100 SAct 0x400000 SErr 0x0 action 0x 6 frozen
[ 99.995907] ata6.01 : failed command: READ FPDMA QUEUED
[ 100.001140] ata6.01 : cmd 60/20:b0:00:00:00/00:00:00:00:00/40 tag 22 ncq 163 84 in
[ 100.016689] ata6.01 : status: { DRDY }
[ 100.020455] ata6.02 : exception Emask 0x100 SAct 0x40000 SErr 0x0 action 0x6 frozen
[ 100.028107] ata6.02 : failed command: READ FPDMA QUEUED
[ 100.033336] ata6.02 : cmd 60/20:90:00:00:00/00:00:00:00:00/40 tag 18 ncq 163 84 in
[ 100.048881] ata6.02 : status: { DRDY }
[ 100.052639] ata6.03 : exception Emask 0x1 SAct 0x1800000 SErr 0x0 action 0x6 frozen
[ 100.060296] ata6.03 : failed command: READ FPDMA QUEUED
[ 100.065529] ata6.03 : cmd 60/40:b8:20:00:00/00:00:00:00:00/40 tag 23 ncq 327 68 in
[ 100.080813] ata6.03 : status: { DRDY }
[ 100.084567] ata6.03 : failed command: READ FPDMA QUEUED
[ 100.089797] ata6.03 : cmd 60/80:c0:60:00:00/00:00:00:00:00/40 tag 24 ncq 655 36 in
[ 100.105077] ata6.03 : status: { DRDY }
[ 100.108837] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 100.116150] ata6.15 : hard resetting link
[ 100.835139] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 100.841918] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1)
[ 100.847720] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1)
[ 101.885205] ata6.04 : limiting SATA link speed to 1.5 Gbps
[ 101.890714] ata6.01 : hard resetting link
[ 102.364629] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 102.371238] ata6.02 : hard resetting link
[ 102.846771] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 102.853368] ata6.03 : hard resetting link
[ 103.326986] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 103.333596] ata6.04 : hard resetting link
[ 103.642870] ata6.04 : SATA link down (SStatus 0 SControl 310)
[ 103.648635] ata6 : No present pin info for SATA link down event
[ 105.656161] ata6.00 : hard resetting link
[ 106.129477] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 106.136828] ata6.00 : supports DRM functions and may not be fully accessible
[ 106.148448] ata6.00 : disabling queued TRIM support
[ 106.152157] ata6.00 : supports DRM functions and may not be fully accessible
[ 106.163773] ata6.00 : disabling queued TRIM support
[ 106.163778] ata6.00 : configured for UDMA/133
[ 106.168738] ata6.01 : supports DRM functions and may not be fully accessible
[ 106.179587] ata6.01 : disabling queued TRIM support
[ 106.182969] ata6.01 : supports DRM functions and may not be fully accessible
[ 106.193939] ata6.01 : disabling queued TRIM support
[ 106.193943] ata6.01 : configured for UDMA/133
[ 106.198916] ata6.02 : supports DRM functions and may not be fully accessible
[ 106.215836] ata6.02 : disabling queued TRIM support
[ 106.219083] ata6.02 : supports DRM functions and may not be fully accessible
[ 106.229815] ata6.02 : disabling queued TRIM support
[ 106.229819] ata6.02 : configured for UDMA/133
[ 106.238628] ata6.03 : disabling queued TRIM support
[ 106.245628] ata6.03 : disabling queued TRIM support
[ 106.245632] ata6.03 : configured for UDMA/133
[ 106.250081] ata6 : EH complete
[ 106.280909] ata6.00 : failed to read SCR 1 (Emask=0x40)
[ 106.286144] ata6.01 : failed to read SCR 1 (Emask=0x40)
[ 106.291372] ata6.02 : failed to read SCR 1 (Emask=0x40)
[ 106.296596] ata6.03 : failed to read SCR 1 (Emask=0x40)
[ 106.301821] ata6.04 : failed to read SCR 1 (Emask=0x40)
[ 106.307050] ata6.00 : exception Emask 0x100 SAct 0x4000000 SErr 0x0 action 0 x6 frozen
[ 106.314875] ata6.00 : failed command: READ FPDMA QUEUED
[ 106.320106] ata6.00 : cmd 60/08:d0:a8:2a:81/00:00:a3:03:00/40 tag 26 ncq 409 6 in
[ 106.335558] ata6.00 : status: { DRDY }
[ 106.339318] ata6.01 : exception Emask 0x100 SAct 0x10000000 SErr 0x0 action 0x6 frozen
[ 106.347233] ata6.01 : failed command: READ FPDMA QUEUED
[ 106.352461] ata6.01 : cmd 60/20:e0:00:00:00/00:00:00:00:00/40 tag 28 ncq 163 84 in
[ 106.368000] ata6.01 : status: { DRDY }
[ 106.371756] ata6.02 : exception Emask 0x100 SAct 0x20000000 SErr 0x0 action 0x6 frozen
[ 106.379666] ata6.02 : failed command: READ FPDMA QUEUED
[ 106.384892] ata6.02 : cmd 60/20:e8:00:00:00/00:00:00:00:00/40 tag 29 ncq 163 84 in
[ 106.400431] ata6.02 : status: { DRDY }
[ 106.404190] ata6.03 : exception Emask 0x1 SAct 0x40100000 SErr 0x0 action 0x 6 frozen
[ 106.411930] ata6.03 : failed command: READ FPDMA QUEUED
[ 106.417173] ata6.03 : cmd 60/08:a0:a8:2a:81/00:00:a3:03:00/40 tag 20 ncq 409 6 in
[ 106.432367] ata6.03 : status: { DRDY }
[ 106.436121] ata6.03 : failed command: READ FPDMA QUEUED
[ 106.441350] ata6.03 : cmd 60/80:f0:60:00:00/00:00:00:00:00/40 tag 30 ncq 655 36 in
[ 106.456626] ata6.03 : status: { DRDY }
[ 106.460382] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 106.467693] ata6.15 : hard resetting link
[ 107.185912] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 107.192696] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1)
[ 107.198498] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1)
[ 108.235948] ata6.04 : limiting SATA link speed to 1.5 Gbps
[ 108.241449] ata6.01 : hard resetting link
[ 108.714532] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 108.721142] ata6.02 : hard resetting link
[ 109.195339] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 109.201965] ata6.03 : hard resetting link
[ 109.674810] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 109.681596] ata6.04 : hard resetting link
[ 109.990805] ata6.04 : SATA link down (SStatus 0 SControl 310)
[ 109.996568] ata6 : No present pin info for SATA link down event
[ 112.004547] ata6.00 : hard resetting link
[ 112.478329] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 112.485441] ata6.00 : supports DRM functions and may not be fully accessible
[ 112.497042] ata6.00 : disabling queued TRIM support
[ 112.500761] ata6.00 : supports DRM functions and may not be fully accessible
[ 112.512393] ata6.00 : disabling queued TRIM support
[ 112.512399] ata6.00 : configured for UDMA/133
[ 112.517470] ata6.01 : supports DRM functions and may not be fully accessible
[ 112.528346] ata6.01 : disabling queued TRIM support
[ 112.531733] ata6.01 : supports DRM functions and may not be fully accessible
[ 112.542758] ata6.01 : disabling queued TRIM support
[ 112.542762] ata6.01 : configured for UDMA/133
[ 112.547840] ata6.02 : supports DRM functions and may not be fully accessible
[ 112.565180] ata6.02 : disabling queued TRIM support
[ 112.568439] ata6.02 : supports DRM functions and may not be fully accessible
[ 112.579153] ata6.02 : disabling queued TRIM support
[ 112.579157] ata6.02 : configured for UDMA/133
[ 112.587894] ata6.03 : disabling queued TRIM support
[ 112.595009] ata6.03 : disabling queued TRIM support
[ 112.595017] ata6.03 : configured for UDMA/133
[ 112.599530] ata6 : EH complete
[ 112.631163] ata6.00 : failed to read SCR 1 (Emask=0x40)
[ 112.636404] ata6.01 : failed to read SCR 1 (Emask=0x40)
[ 112.641637] ata6.02 : failed to read SCR 1 (Emask=0x40)
[ 112.646866] ata6.03 : failed to read SCR 1 (Emask=0x40)
[ 112.652094] ata6.04 : failed to read SCR 1 (Emask=0x40)
[ 112.657327] ata6.00 : exception Emask 0x100 SAct 0x400000 SErr 0x0 action 0x 6 frozen
[ 112.665071] ata6.00 : failed command: READ FPDMA QUEUED
[ 112.670303] ata6.00 : cmd 60/08:b0:a8:2a:81/00:00:a3:03:00/40 tag 22 ncq 409 6 in
[ 112.685755] ata6.00 : status: { DRDY }
[ 112.689526] ata6.01 : exception Emask 0x1 SAct 0x30000 SErr 0x0 action 0x6 f rozen
[ 112.697008] ata6.01 : failed command: READ FPDMA QUEUED
[ 112.702238] ata6.01 : cmd 60/40:80:20:00:00/00:00:00:00:00/40 tag 16 ncq 327 68 in
[ 112.717519] ata6.01 : status: { DRDY }
[ 112.721273] ata6.01 : failed command: READ FPDMA QUEUED
[ 112.726502] ata6.01 : cmd 60/80:88:60:00:00/00:00:00:00:00/40 tag 17 ncq 655 36 in
[ 112.741779] ata6.01 : status: { DRDY }
[ 112.745537] ata6.02 : exception Emask 0x100 SAct 0x2000000 SErr 0x0 action 0 x6 frozen
[ 112.753362] ata6.02 : failed command: READ FPDMA QUEUED
[ 112.758589] ata6.02 : cmd 60/20:c8:00:00:00/00:00:00:00:00/40 tag 25 ncq 163 84 in
[ 112.774126] ata6.02 : status: { DRDY }
[ 112.777881] ata6.03 : exception Emask 0x100 SAct 0x8000000 SErr 0x0 action 0 x6 frozen
[ 112.785711] ata6.03 : failed command: READ FPDMA QUEUED
[ 112.790937] ata6.03 : cmd 60/08:d8:a8:2a:81/00:00:a3:03:00/40 tag 27 ncq 409 6 in
[ 112.806387] ata6.03 : status: { DRDY }
[ 112.810141] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 112.817453] ata6.15 : hard resetting link
[ 113.536554] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 113.543344] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1)
[ 113.549164] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1)
[ 114.586504] ata6.04 : limiting SATA link speed to 1.5 Gbps
[ 114.592003] ata6.01 : hard resetting link
[ 115.066195] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 115.072801] ata6.02 : hard resetting link
[ 115.544878] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 115.551674] ata6.03 : hard resetting link
[ 116.025524] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 116.032150] ata6.04 : hard resetting link
[ 116.341605] ata6.04 : SATA link down (SStatus 0 SControl 310)
[ 116.347371] ata6 : No present pin info for SATA link down event
[ 118.355102] ata6.00 : hard resetting link
[ 118.829561] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 118.836686] ata6.00 : supports DRM functions and may not be fully accessible
[ 118.848347] ata6.00 : disabling queued TRIM support
[ 118.852085] ata6.00 : supports DRM functions and may not be fully accessible
[ 118.863710] ata6.00 : disabling queued TRIM support
[ 118.863716] ata6.00 : configured for UDMA/133
[ 118.868680] ata6.01 : supports DRM functions and may not be fully accessible
[ 118.879517] ata6.01 : disabling queued TRIM support
[ 118.882910] ata6.01 : supports DRM functions and may not be fully accessible
[ 118.893941] ata6.01 : disabling queued TRIM support
[ 118.893945] ata6.01 : configured for UDMA/133
[ 118.898929] ata6.02 : supports DRM functions and may not be fully accessible
[ 118.909679] ata6.02 : disabling queued TRIM support
[ 118.912984] ata6.02 : supports DRM functions and may not be fully accessible
[ 118.923754] ata6.02 : disabling queued TRIM support
[ 118.923758] ata6.02 : configured for UDMA/133
[ 118.937590] ata6.03 : disabling queued TRIM support
[ 118.951111] ata6.03 : disabling queued TRIM support
[ 118.951115] ata6.03 : configured for UDMA/133
[ 118.955565] ata6 : EH complete
[ 118.989419] ata6.00 : failed to read SCR 1 (Emask=0x40)
[ 118.994651] ata6.01 : failed to read SCR 1 (Emask=0x40)
[ 118.999880] ata6.02 : failed to read SCR 1 (Emask=0x40)
[ 119.005109] ata6.03 : failed to read SCR 1 (Emask=0x40)
[ 119.010336] ata6.04 : failed to read SCR 1 (Emask=0x40)
[ 119.015567] ata6.00 : exception Emask 0x100 SAct 0x80000 SErr 0x0 action 0x6 frozen
[ 119.023222] ata6.00 : failed command: READ FPDMA QUEUED
[ 119.028452] ata6.00 : cmd 60/08:98:a8:2a:81/00:00:a3:03:00/40 tag 19 ncq 409 6 in
[ 119.043905] ata6.00 : status: { DRDY }
[ 119.047667] ata6.01 : exception Emask 0x1 SAct 0x204000 SErr 0x0 action 0x6 frozen
[ 119.055235] ata6.01 : failed command: READ FPDMA QUEUED
[ 119.060465] ata6.01 : cmd 60/08:70:a8:2a:81/00:00:a3:03:00/40 tag 14 ncq 409 6 in
[ 119.075658] ata6.01 : status: { DRDY }
[ 119.079412] ata6.01 : failed command: READ FPDMA QUEUED
[ 119.084642] ata6.01 : cmd 60/80:a8:60:00:00/00:00:00:00:00/40 tag 21 ncq 655 36 in
[ 119.099921] ata6.01 : status: { DRDY }
[ 119.103677] ata6.02 : exception Emask 0x100 SAct 0x800000 SErr 0x0 action 0x 6 frozen
[ 119.111416] ata6.02 : failed command: READ FPDMA QUEUED
[ 119.116646] ata6.02 : cmd 60/20:b8:00:00:00/00:00:00:00:00/40 tag 23 ncq 163 84 in
[ 119.132183] ata6.02 : status: { DRDY }
[ 119.135941] ata6.03 : exception Emask 0x100 SAct 0x2000 SErr 0x0 action 0x6 frozen
[ 119.143507] ata6.03 : failed command: READ FPDMA QUEUED
[ 119.148733] ata6.03 : cmd 60/20:68:88:2a:81/00:00:a3:03:00/40 tag 13 ncq 163 84 in
[ 119.164271] ata6.03 : status: { DRDY }
[ 119.168026] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 119.175337] ata6.15 : hard resetting link
[ 119.894978] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 119.901728] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1)
[ 119.907733] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1)
[ 120.944926] ata6.04 : limiting SATA link speed to 1.5 Gbps
[ 120.950432] ata6.01 : hard resetting link
[ 121.424419] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 121.431204] ata6.02 : hard resetting link
[ 121.904825] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 121.911436] ata6.03 : hard resetting link
[ 122.385493] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 122.392109] ata6.04 : hard resetting link
[ 122.701255] ata6.04 : SATA link down (SStatus 0 SControl 310)
[ 122.707022] ata6 : No present pin info for SATA link down event
[ 124.714904] ata6.00 : hard resetting link
[ 125.187571] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 125.194949] ata6.00 : supports DRM functions and may not be fully accessible
[ 125.206503] ata6.00 : disabling queued TRIM support
[ 125.210181] ata6.00 : supports DRM functions and may not be fully accessible
[ 125.221788] ata6.00 : disabling queued TRIM support
[ 125.221793] ata6.00 : configured for UDMA/133
[ 125.226838] ata6.01 : supports DRM functions and may not be fully accessible
[ 125.237673] ata6.01 : disabling queued TRIM support
[ 125.241050] ata6.01 : supports DRM functions and may not be fully accessible
[ 125.253857] ata6.01 : disabling queued TRIM support
[ 125.253861] ata6.01 : configured for UDMA/133
[ 125.258948] ata6.02 : supports DRM functions and may not be fully accessible
[ 125.269687] ata6.02 : disabling queued TRIM support
[ 125.272995] ata6.02 : supports DRM functions and may not be fully accessible
[ 125.283753] ata6.02 : disabling queued TRIM support
[ 125.283757] ata6.02 : configured for UDMA/133
[ 125.292512] ata6.03 : disabling queued TRIM support
[ 125.299475] ata6.03 : disabling queued TRIM support
[ 125.299478] ata6.03 : configured for UDMA/133
[ 125.304047] ata6 : EH complete
[ 125.340647] ata6.00 : failed to read SCR 1 (Emask=0x40)
[ 125.345877] ata6.01 : failed to read SCR 1 (Emask=0x40)
[ 125.351106] ata6.02 : failed to read SCR 1 (Emask=0x40)
[ 125.356334] ata6.03 : failed to read SCR 1 (Emask=0x40)
[ 125.361560] ata6.04 : failed to read SCR 1 (Emask=0x40)
[ 125.366788] ata6.00 : exception Emask 0x100 SAct 0x8000 SErr 0x0 action 0x6 frozen
[ 125.374355] ata6.00 : failed command: READ FPDMA QUEUED
[ 125.379582] ata6.00 : cmd 60/08:78:80:20:00/00:00:00:00:00/40 tag 15 ncq 409 6 in
[ 125.395033] ata6.00 : status: { DRDY }
[ 125.398791] ata6.01 : exception Emask 0x100 SAct 0x41000 SErr 0x0 action 0x6 frozen
[ 125.406442] ata6.01 : failed command: READ FPDMA QUEUED
[ 125.411671] ata6.01 : cmd 60/20:60:88:2a:81/00:00:a3:03:00/40 tag 12 ncq 163 84 in
[ 125.427211] ata6.01 : status: { DRDY }
[ 125.430965] ata6.01 : failed command: READ FPDMA QUEUED
[ 125.436193] ata6.01 : cmd 60/80:90:60:00:00/00:00:00:00:00/40 tag 18 ncq 655 36 in
[ 125.451734] ata6.01 : status: { DRDY }
[ 125.455490] ata6.02 : exception Emask 0x1 SAct 0x6000 SErr 0x0 action 0x6 fr ozen
[ 125.462903] ata6.02 : failed command: READ FPDMA QUEUED
[ 125.468145] ata6.02 : cmd 60/40:68:20:00:00/00:00:00:00:00/40 tag 13 ncq 327 68 in
[ 125.483426] ata6.02 : status: { DRDY }
[ 125.487181] ata6.02 : failed command: READ FPDMA QUEUED
[ 125.492411] ata6.02 : cmd 60/80:70:60:00:00/00:00:00:00:00/40 tag 14 ncq 655 36 in
[ 125.507690] ata6.02 : status: { DRDY }
[ 125.511446] ata6.03 : exception Emask 0x100 SAct 0x800 SErr 0x0 action 0x6 f rozen
[ 125.518922] ata6.03 : failed command: READ FPDMA QUEUED
[ 125.524152] ata6.03 : cmd 60/08:58:80:20:00/00:00:00:00:00/40 tag 11 ncq 409 6 in
[ 125.539602] ata6.03 : status: { DRDY }
[ 125.543359] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 125.550670] ata6.15 : hard resetting link
[ 126.270054] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 126.277025] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1)
[ 126.282831] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1)
[ 127.320013] ata6.04 : limiting SATA link speed to 1.5 Gbps
[ 127.325515] ata6.01 : hard resetting link
[ 127.798683] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 127.805297] ata6.02 : hard resetting link
[ 128.278630] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 128.285252] ata6.03 : hard resetting link
[ 128.757301] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 128.763881] ata6.04 : hard resetting link
[ 129.073149] ata6.04 : SATA link down (SStatus 0 SControl 310)
[ 129.078912] ata6 : No present pin info for SATA link down event
[ 131.086600] ata6.00 : hard resetting link
[ 131.560841] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 131.567957] ata6.00 : supports DRM functions and may not be fully accessible
[ 131.579519] ata6.00 : disabling queued TRIM support
[ 131.583209] ata6.00 : supports DRM functions and may not be fully accessible
[ 131.594877] ata6.00 : disabling queued TRIM support
[ 131.594881] ata6.00 : configured for UDMA/133
[ 131.599979] ata6.01 : supports DRM functions and may not be fully accessible
[ 131.610859] ata6.01 : disabling queued TRIM support
[ 131.614244] ata6.01 : supports DRM functions and may not be fully accessible
[ 131.625124] ata6.01 : disabling queued TRIM support
[ 131.625128] ata6.01 : configured for UDMA/133
[ 131.630202] ata6.02 : supports DRM functions and may not be fully accessible
[ 131.641035] ata6.02 : disabling queued TRIM support
[ 131.646767] ata6.02 : supports DRM functions and may not be fully accessible
[ 131.664065] ata6.02 : disabling queued TRIM support
[ 131.664069] ata6.02 : configured for UDMA/133
[ 131.672869] ata6.03 : disabling queued TRIM support
[ 131.680017] ata6.03 : disabling queued TRIM support
[ 131.680021] ata6.03 : configured for UDMA/133
[ 131.684596] ata6 : EH complete
[ 131.715913] ata6.00 : failed to read SCR 1 (Emask=0x40)
[ 131.721142] ata6.01 : failed to read SCR 1 (Emask=0x40)
[ 131.726371] ata6.02 : failed to read SCR 1 (Emask=0x40)
[ 131.731596] ata6.02 : NCQ disabled due to excessive errors
[ 131.737081] ata6.03 : failed to read SCR 1 (Emask=0x40)
[ 131.742310] ata6.04 : failed to read SCR 1 (Emask=0x40)
[ 131.747537] ata6.00 : exception Emask 0x100 SAct 0x20000 SErr 0x0 action 0x6 frozen
[ 131.755194] ata6.00 : failed command: READ FPDMA QUEUED
[ 131.760423] ata6.00 : cmd 60/08:88:80:20:00/00:00:00:00:00/40 tag 17 ncq 409 6 in
[ 131.775877] ata6.00 : status: { DRDY }
[ 131.779638] ata6.01 : exception Emask 0x100 SAct 0x100000 SErr 0x0 action 0x 6 frozen
[ 131.787384] ata6.01 : failed command: READ FPDMA QUEUED
[ 131.792614] ata6.01 : cmd 60/20:a0:88:2a:81/00:00:a3:03:00/40 tag 20 ncq 163 84 in
[ 131.808156] ata6.01 : status: { DRDY }
[ 131.811914] ata6.02 : exception Emask 0x1 SAct 0x204000 SErr 0x0 action 0x6 frozen
[ 131.819778] ata6.02 : failed command: READ FPDMA QUEUED
[ 131.825018] ata6.02 : cmd 60/08:70:a8:2a:81/00:00:a3:03:00/40 tag 14 ncq 409 6 in
[ 131.840208] ata6.02 : status: { DRDY }
[ 131.843963] ata6.02 : failed command: READ FPDMA QUEUED
[ 131.849188] ata6.02 : cmd 60/80:a8:60:00:00/00:00:00:00:00/40 tag 21 ncq 655 36 in
[ 131.864467] ata6.02 : status: { DRDY }
[ 131.868225] ata6.03 : exception Emask 0x100 SAct 0x800000 SErr 0x0 action 0x 6 frozen
[ 131.875967] ata6.03 : failed command: READ FPDMA QUEUED
[ 131.881198] ata6.03 : cmd 60/08:b8:80:20:00/00:00:00:00:00/40 tag 23 ncq 409 6 in
[ 131.896654] ata6.03 : status: { DRDY }
[ 131.900423] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 131.907733] ata6.15 : hard resetting link
[ 132.625943] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 132.633057] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1)
[ 132.638898] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1)
[ 133.676214] ata6.04 : limiting SATA link speed to 1.5 Gbps
[ 133.681723] ata6.01 : hard resetting link
[ 134.154550] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 134.161332] ata6.02 : hard resetting link
[ 134.634592] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 134.641383] ata6.03 : hard resetting link
[ 135.114236] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 135.120858] ata6.04 : hard resetting link
[ 135.430775] ata6.04 : SATA link down (SStatus 0 SControl 310)
[ 135.436542] ata6 : No present pin info for SATA link down event
[ 137.444554] ata6.00 : hard resetting link
[ 137.919068] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 137.926356] ata6.00 : supports DRM functions and may not be fully accessible
[ 137.937910] ata6.00 : disabling queued TRIM support
[ 137.941613] ata6.00 : supports DRM functions and may not be fully accessible
[ 137.953276] ata6.00 : disabling queued TRIM support
[ 137.953280] ata6.00 : configured for UDMA/133
[ 137.958332] ata6.01 : supports DRM functions and may not be fully accessible
[ 137.969200] ata6.01 : disabling queued TRIM support
[ 137.972561] ata6.01 : supports DRM functions and may not be fully accessible
[ 137.983515] ata6.01 : disabling queued TRIM support
[ 137.983519] ata6.01 : configured for UDMA/133
[ 137.988587] ata6.02 : supports DRM functions and may not be fully accessible
[ 137.999355] ata6.02 : disabling queued TRIM support
[ 138.002606] ata6.02 : supports DRM functions and may not be fully accessible
[ 138.013330] ata6.02 : disabling queued TRIM support
[ 138.013334] ata6.02 : configured for UDMA/133
[ 138.022167] ata6.03 : disabling queued TRIM support
[ 138.034153] ata6.03 : disabling queued TRIM support
[ 138.034157] ata6.03 : configured for UDMA/133
[ 138.038729] ata6 : EH complete
[ 138.179142] ata6.00 : failed to read SCR 1 (Emask=0x40)
[ 138.184374] ata6.01 : failed to read SCR 1 (Emask=0x40)
[ 138.189603] ata6.02 : failed to read SCR 1 (Emask=0x40)
[ 138.194831] ata6.03 : failed to read SCR 1 (Emask=0x40)
[ 138.200056] ata6.03 : NCQ disabled due to excessive errors
[ 138.205543] ata6.04 : failed to read SCR 1 (Emask=0x40)
[ 138.210774] ata6.00 : exception Emask 0x100 SAct 0x400 SErr 0x0 action 0x6 f rozen
[ 138.218252] ata6.00 : failed command: READ FPDMA QUEUED
[ 138.223481] ata6.00 : cmd 60/08:50:a8:2a:81/00:00:a3:03:00/40 tag 10 ncq 409 6 in
[ 138.238935] ata6.00 : status: { DRDY }
[ 138.242703] ata6.01 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 138.250010] ata6.01 : failed command: FLUSH CACHE EXT
[ 138.255067] ata6.01 : cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 19
[ 138.269476] ata6.01 : status: { DRDY }
[ 138.273231] ata6.02 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 138.280536] ata6.02 : failed command: READ DMA EXT
[ 138.285330] ata6.02 : cmd 25/00:08:18:35:7e/00:00:a3:03:00/e0 tag 15 dma 409 6 in
[ 138.300779] ata6.02 : status: { DRDY }
[ 138.304536] ata6.03 : exception Emask 0x1 SAct 0x60000 SErr 0x0 action 0x6 f rozen
[ 138.312015] ata6.03 : failed command: READ FPDMA QUEUED
[ 138.317240] ata6.03 : cmd 60/40:88:20:00:00/00:00:00:00:00/40 tag 17 ncq 327 68 in
[ 138.332518] ata6.03 : status: { DRDY }
[ 138.336272] ata6.03 : failed command: READ FPDMA QUEUED
[ 138.341500] ata6.03 : cmd 60/80:90:60:00:00/00:00:00:00:00/40 tag 18 ncq 655 36 in
[ 138.356780] ata6.03 : status: { DRDY }
[ 138.360538] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 138.367849] ata6.15 : hard resetting link
[ 139.086558] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 139.093347] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1)
[ 139.099150] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1)
[ 140.136370] ata6.04 : limiting SATA link speed to 1.5 Gbps
[ 140.141876] ata6.01 : hard resetting link
[ 140.616192] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 140.622804] ata6.02 : hard resetting link
[ 141.096212] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 141.102830] ata6.03 : hard resetting link
[ 141.576284] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 141.582916] ata6.04 : hard resetting link
[ 141.892025] ata6.04 : SATA link down (SStatus 0 SControl 310)
[ 141.897792] ata6 : No present pin info for SATA link down event
[ 143.905718] ata6.00 : hard resetting link
[ 144.379761] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 144.386927] ata6.00 : supports DRM functions and may not be fully accessible
[ 144.398578] ata6.00 : disabling queued TRIM support
[ 144.402298] ata6.00 : supports DRM functions and may not be fully accessible
[ 144.413919] ata6.00 : disabling queued TRIM support
[ 144.413923] ata6.00 : configured for UDMA/133
[ 144.419008] ata6.01 : supports DRM functions and may not be fully accessible
[ 144.429848] ata6.01 : disabling queued TRIM support
[ 144.433252] ata6.01 : supports DRM functions and may not be fully accessible
[ 144.444298] ata6.01 : disabling queued TRIM support
[ 144.444302] ata6.01 : configured for UDMA/133
[ 144.448671] ata6.01 : retrying FLUSH 0xea Emask 0x100
[ 144.454814] ata6.02 : supports DRM functions and may not be fully accessible
[ 144.465580] ata6.02 : disabling queued TRIM support
[ 144.468833] ata6.02 : supports DRM functions and may not be fully accessible
[ 144.479659] ata6.02 : disabling queued TRIM support
[ 144.479663] ata6.02 : configured for UDMA/133
[ 144.488398] ata6.03 : disabling queued TRIM support
[ 144.495460] ata6.03 : disabling queued TRIM support
[ 144.495463] ata6.03 : configured for UDMA/133
[ 144.499988] ata6.01 : device reported invalid CHS sector 0
[ 144.505483] ata6 : EH complete
[ 144.539394] ata6.00 : failed to read SCR 1 (Emask=0x40)
[ 144.544625] ata6.01 : failed to read SCR 1 (Emask=0x40)
[ 144.549853] ata6.02 : failed to read SCR 1 (Emask=0x40)
[ 144.555081] ata6.03 : failed to read SCR 1 (Emask=0x40)
[ 144.560309] ata6.04 : failed to read SCR 1 (Emask=0x40)
[ 144.565541] ata6.00 : exception Emask 0x100 SAct 0x200000 SErr 0x0 action 0x 6 frozen
[ 144.573281] ata6.00 : failed command: READ FPDMA QUEUED
[ 144.578510] ata6.00 : cmd 60/08:a8:a8:2a:81/00:00:a3:03:00/40 tag 21 ncq 409 6 in
[ 144.593961] ata6.00 : status: { DRDY }
[ 144.597720] ata6.01 : exception Emask 0x1 SAct 0x18000 SErr 0x0 action 0x6 f rozen
[ 144.605201] ata6.01 : failed command: READ FPDMA QUEUED
[ 144.610431] ata6.01 : cmd 60/80:78:60:00:00/00:00:00:00:00/40 tag 15 ncq 655 36 in
[ 144.625709] ata6.01 : status: { DRDY }
[ 144.629459] ata6.01 : failed command: READ FPDMA QUEUED
[ 144.634688] ata6.01 : cmd 60/08:80:a8:2a:81/00:00:a3:03:00/40 tag 16 ncq 409 6 in
[ 144.649882] ata6.01 : status: { DRDY }
[ 144.653638] ata6.02 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 144.660942] ata6.02 : failed command: READ DMA
[ 144.665388] ata6.02 : cmd c8/00:08:20:5f:44/00:00:00:00:00/e1 tag 13 dma 409 6 in
[ 144.680841] ata6.02 : status: { DRDY }
[ 144.684597] ata6.03 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 144.691904] ata6.03 : failed command: READ DMA
[ 144.696353] ata6.03 : cmd c8/00:40:20:00:00/00:00:00:00:00/e0 tag 26 dma 327 68 in
[ 144.711891] ata6.03 : status: { DRDY }
[ 144.715647] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 144.722956] ata6.15 : hard resetting link
[ 145.441801] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 145.448988] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1)
[ 145.454805] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1)
[ 146.492231] ata6.04 : limiting SATA link speed to 1.5 Gbps
[ 146.497734] ata6.01 : hard resetting link
[ 146.971482] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 146.978096] ata6.02 : hard resetting link
[ 147.450675] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 147.457297] ata6.03 : hard resetting link
[ 147.931534] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 147.938146] ata6.04 : hard resetting link
[ 148.247266] ata6.04 : SATA link down (SStatus 0 SControl 310)
[ 148.253029] ata6 : No present pin info for SATA link down event
[ 150.260711] ata6.00 : hard resetting link
[ 150.734590] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 150.741707] ata6.00 : supports DRM functions and may not be fully accessible
[ 150.753270] ata6.00 : disabling queued TRIM support
[ 150.756912] ata6.00 : supports DRM functions and may not be fully accessible
[ 150.768570] ata6.00 : disabling queued TRIM support
[ 150.768576] ata6.00 : configured for UDMA/133
[ 150.773653] ata6.01 : supports DRM functions and may not be fully accessible
[ 150.784525] ata6.01 : disabling queued TRIM support
[ 150.787968] ata6.01 : supports DRM functions and may not be fully accessible
[ 150.798811] ata6.01 : disabling queued TRIM support
[ 150.798815] ata6.01 : configured for UDMA/133
[ 150.803866] ata6.02 : supports DRM functions and may not be fully accessible
[ 150.814633] ata6.02 : disabling queued TRIM support
[ 150.817900] ata6.02 : supports DRM functions and may not be fully accessible
[ 150.828636] ata6.02 : disabling queued TRIM support
[ 150.828640] ata6.02 : configured for UDMA/133
[ 150.843995] ata6.03 : disabling queued TRIM support
[ 150.851016] ata6.03 : disabling queued TRIM support
[ 150.851019] ata6.03 : configured for UDMA/133
[ 150.855602] ata6 : EH complete
[ 151.197641] ata6.00 : failed to read SCR 1 (Emask=0x40)
[ 151.202883] ata6.01 : failed to read SCR 1 (Emask=0x40)
[ 151.208111] ata6.01 : NCQ disabled due to excessive errors
[ 151.213594] ata6.02 : failed to read SCR 1 (Emask=0x40)
[ 151.218820] ata6.03 : failed to read SCR 1 (Emask=0x40)
[ 151.224048] ata6.04 : failed to read SCR 1 (Emask=0x40)
[ 151.229277] ata6.00 : exception Emask 0x100 SAct 0x1 SErr 0x0 action 0x6 fro zen
[ 151.236587] ata6.00 : failed command: READ FPDMA QUEUED
[ 151.241816] ata6.00 : cmd 60/08:00:e8:5e:44/00:00:01:00:00/40 tag 0 ncq 4096 in
[ 151.257184] ata6.00 : status: { DRDY }
[ 151.260949] ata6.01 : exception Emask 0x1 SAct 0x40000008 SErr 0x0 action 0x 6 frozen
[ 151.268691] ata6.01 : failed command: READ FPDMA QUEUED
[ 151.273921] ata6.01 : cmd 60/08:18:e8:5e:44/00:00:01:00:00/40 tag 3 ncq 4096 in
[ 151.289036] ata6.01 : status: { DRDY }
[ 151.292790] ata6.01 : failed command: READ FPDMA QUEUED
[ 151.298021] ata6.01 : cmd 60/20:f0:60:68:44/00:00:01:00:00/40 tag 30 ncq 163 84 in
[ 151.313303] ata6.01 : status: { DRDY }
[ 151.317062] ata6.02 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 151.324372] ata6.02 : failed command: READ DMA
[ 151.328823] ata6.02 : cmd c8/00:08:e8:5e:44/00:00:00:00:00/e1 tag 2 dma 4096 in
[ 151.344195] ata6.02 : status: { DRDY }
[ 151.347952] ata6.03 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 151.355258] ata6.03 : failed command: READ DMA
[ 151.359707] ata6.03 : cmd c8/00:08:e8:5e:44/00:00:00:00:00/e1 tag 1 dma 4096 in
[ 151.375383] ata6.03 : status: { DRDY }
[ 151.379146] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen
[ 151.386462] ata6.15 : hard resetting link
[ 152.105072] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 152.112029] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1)
[ 152.117853] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1)
[ 153.155064] ata6.04 : limiting SATA link speed to 1.5 Gbps
[ 153.160567] ata6.01 : hard resetting link
[ 153.634710] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 153.641318] ata6.02 : hard resetting link
[ 154.114936] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 154.121557] ata6.03 : hard resetting link
[ 154.594757] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 154.601367] ata6.04 : hard resetting link
[ 154.910537] ata6.04 : SATA link down (SStatus 0 SControl 310)
[ 154.916303] ata6 : No present pin info for SATA link down event
[ 156.923983] ata6.00 : hard resetting link
[ 157.396817] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 157.404298] ata6.00 : supports DRM functions and may not be fully accessible
[ 157.415883] ata6.00 : disabling queued TRIM support
[ 157.419563] ata6.00 : supports DRM functions and may not be fully accessible
[ 157.431176] ata6.00 : disabling queued TRIM support
[ 157.431181] ata6.00 : configured for UDMA/133
[ 157.436223] ata6.01 : supports DRM functions and may not be fully accessible
[ 157.447064] ata6.01 : disabling queued TRIM support
[ 157.450490] ata6.01 : supports DRM functions and may not be fully accessible
[ 157.461336] ata6.01 : disabling queued TRIM support
[ 157.461340] ata6.01 : configured for UDMA/133
[ 157.473017] ata6.02 : supports DRM functions and may not be fully accessible
[ 157.483763] ata6.02 : disabling queued TRIM support
[ 157.487054] ata6.02 : supports DRM functions and may not be fully accessible
[ 157.497816] ata6.02 : disabling queued TRIM support
[ 157.497820] ata6.02 : configured for UDMA/133
[ 157.518360] ata6.03 : disabling queued TRIM support
[ 157.538642] ata6.03 : disabling queued TRIM support
[ 157.538645] ata6.03 : configured for UDMA/133
[ 157.543220] ata6 : EH complete
[ 166.183550] ata2.00 (slot 1): disabling queued TRIM support
[ 166.186329] ata2.00 (slot 1): disabling queued TRIM support
[ 166.186336] ata2.00 (slot 1): configured for UDMA/133
[ 166.191407] ata2 (slot 1): EH complete
[ 166.431842] ata3.00 (slot 2): disabling queued TRIM support
[ 166.434588] ata3.00 (slot 2): disabling queued TRIM support
[ 166.434597] ata3.00 (slot 2): configured for UDMA/133
[ 166.439667] ata3 (slot 2): EH complete
[ 166.655168] ata4.00 (slot 3): disabling queued TRIM support
[ 166.657962] ata4.00 (slot 3): disabling queued TRIM support
[ 166.657968] ata4.00 (slot 3): configured for UDMA/133
[ 166.663033] ata4 (slot 3): EH complete
[ 166.864721] ata5.00 (slot 4): disabling queued TRIM support
[ 166.867506] ata5.00 (slot 4): disabling queued TRIM support
[ 166.867512] ata5.00 (slot 4): configured for UDMA/133
[ 166.872579] ata5 (slot 4): EH complete
[ 167.053822] ata10.00 (slot 8): disabling queued TRIM support
[ 167.067682] ata10.00 (slot 8): disabling queued TRIM support
[ 167.067692] ata10.00 (slot 8): configured for UDMA/133
[ 167.072845] ata10 (slot 8): EH complete
[ 167.160612] ata6.00 : supports DRM functions and may not be fully accessible
[ 167.172179] ata6.00 : disabling queued TRIM support
[ 167.175874] ata6.00 : supports DRM functions and may not be fully accessible
[ 167.187479] ata6.00 : disabling queued TRIM support
[ 167.187484] ata6.00 : configured for UDMA/133
[ 167.191901] ata6 : EH complete
[ 167.276847] ata6.01 : supports DRM functions and may not be fully accessible
[ 167.287569] ata6.01 : disabling queued TRIM support
[ 167.290916] ata6.01 : supports DRM functions and may not be fully accessible
[ 167.304940] ata6.01 : disabling queued TRIM support
[ 167.304948] ata6.01 : configured for UDMA/133
[ 167.309374] ata6 : EH complete
[ 167.394039] ata6.02 : supports DRM functions and may not be fully accessible
[ 167.404740] ata6.02 : disabling queued TRIM support
[ 167.415031] ata6.02 : supports DRM functions and may not be fully accessible
[ 167.430917] ata6.02 : disabling queued TRIM support
[ 167.430925] ata6.02 : configured for UDMA/133
[ 167.435360] ata6 : EH complete
[ 167.531718] ata6.03 : disabling queued TRIM support
[ 167.544473] ata6.03 : disabling queued TRIM support
[ 167.544483] ata6.03 : configured for UDMA/133
[ 167.548919] ata6 : EH complete
[ 167.628250] ata7.00 (slot 5): disabling queued TRIM support
[ 167.631037] ata7.00 (slot 5): disabling queued TRIM support
[ 167.631043] ata7.00 (slot 5): configured for UDMA/133
[ 167.636109] ata7 (slot 5): EH complete
[ 167.782435] ata8.00 (slot 6): disabling queued TRIM support
[ 167.785192] ata8.00 (slot 6): disabling queued TRIM support
[ 167.785198] ata8.00 (slot 6): configured for UDMA/133
[ 167.790262] ata8 (slot 6): EH complete
[ 167.900525] ata9.00 (slot 7): disabling queued TRIM support
[ 167.903297] ata9.00 (slot 7): disabling queued TRIM support
[ 167.903303] ata9.00 (slot 7): configured for UDMA/133
[ 167.908371] ata9 (slot 7): EH complete

@mervincm commented on GitHub (Sep 18, 2025): dmesg | grep -i ata [ 6.223231] ahci 0000:0a:00.0: AHCI 0001.0301 32 slots 5 ports 6 Gbps 0x1f i mpl SATA mode [ 6.366972] ahci 0000:0a:00.0: JMB585 port=0, reg_addr=0x4, reg_data=0xae8 [ 6.473942] ahci 0000:0a:00.0: JMB585 port=1, reg_addr=0x11, reg_data=0xae5 [ 6.580986] ahci 0000:0a:00.0: JMB585 port=2, reg_addr=0x1e, reg_data=0xae5 [ 6.688032] ahci 0000:0a:00.0: JMB585 port=3, reg_addr=0x2b, reg_data=0xae5 [ 6.795078] ahci 0000:0a:00.0: JMB585 port=4, reg_addr=0x38, reg_data=0xae5 [ 6.902123] ahci 0000:0a:00.0: JMB585 port=0, reg_addr=0x73, reg_data=0x1e4 [ 7.009168] ahci 0000:0a:00.0: JMB585 port=1, reg_addr=0x75, reg_data=0x1e4 [ 7.116212] ahci 0000:0a:00.0: JMB585 port=2, reg_addr=0x77, reg_data=0x1e5 [ 7.223255] ahci 0000:0a:00.0: JMB585 port=3, reg_addr=0x79, reg_data=0x1e4 [ 7.330301] ahci 0000:0a:00.0: JMB585 port=4, reg_addr=0x7b, reg_data=0x1e5 [ 7.359246] ata1 : SATA max UDMA/133 abar m8192@0xd2700000 port 0xd2700100 i rq 302 [ 7.366864] ata2 : SATA max UDMA/133 abar m8192@0xd2700000 port 0xd2700180 i rq 303 [ 7.374437] ata3 : SATA max UDMA/133 abar m8192@0xd2700000 port 0xd2700200 i rq 304 [ 7.382008] ata4 : SATA max UDMA/133 abar m8192@0xd2700000 port 0xd2700280 i rq 305 [ 7.389584] ata5 : SATA max UDMA/133 abar m8192@0xd2700000 port 0xd2700300 i rq 306 [ 7.404147] ahci 0000:0b:00.0: AHCI 0001.0301 32 slots 5 ports 6 Gbps 0x1f i mpl SATA mode [ 7.547836] ahci 0000:0b:00.0: JMB585 port=0, reg_addr=0x4, reg_data=0xae8 [ 7.654770] ahci 0000:0b:00.0: JMB585 port=1, reg_addr=0x11, reg_data=0xae5 [ 7.761785] ahci 0000:0b:00.0: JMB585 port=2, reg_addr=0x1e, reg_data=0xae5 [ 7.868801] ahci 0000:0b:00.0: JMB585 port=3, reg_addr=0x2b, reg_data=0x7e5 [ 7.975817] ahci 0000:0b:00.0: JMB585 port=4, reg_addr=0x38, reg_data=0x7e5 [ 8.082834] ahci 0000:0b:00.0: JMB585 port=0, reg_addr=0x73, reg_data=0x1e4 [ 8.189850] ahci 0000:0b:00.0: JMB585 port=1, reg_addr=0x75, reg_data=0x1e4 [ 8.296870] ahci 0000:0b:00.0: JMB585 port=2, reg_addr=0x77, reg_data=0x1e5 [ 8.403888] ahci 0000:0b:00.0: JMB585 port=3, reg_addr=0x79, reg_data=0x1e4 [ 8.510905] ahci 0000:0b:00.0: JMB585 port=4, reg_addr=0x7b, reg_data=0x1e5 [ 8.541187] ata6 : SATA max UDMA/133 abar m8192@0xd2600000 port 0xd2600100 i rq 325 [ 8.548770] ata7 : SATA max UDMA/133 abar m8192@0xd2600000 port 0xd2600180 i rq 326 [ 8.556339] ata8 : SATA max UDMA/133 abar m8192@0xd2600000 port 0xd2600200 i rq 327 [ 8.563904] ata9 : SATA max UDMA/133 abar m8192@0xd2600000 port 0xd2600280 i rq 328 [ 8.571469] ata10 : SATA max UDMA/133 abar m8192@0xd2600000 port 0xd2600300 irq 329 [ 11.694318] ata1 : SATA link down (SStatus 0 SControl 300) [ 11.699813] ata1 : No present pin info for SATA link down event [ 11.849312] ata6 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 11.855974] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1) [ 11.861777] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1) [ 12.898969] ata6.15 : Port Multiplier 1.1, 0x1095:0x3726 r23, 5 ports, feat 0x1/0x9 [ 12.998618] ata6 : Apply Synology fast PMP boot [ 13.379655] ata10 (slot 8): SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 13.390971] ata10.00 (slot 8): disabling queued TRIM support [ 13.390977] ata10.00 (slot 8): ATA-9: WDC WD80EFBX-68AZZN0, 85.00A85, max UD MA/133 [ 13.398551] ata10.00 (slot 8): 15628053168 sectors, multi 0: LBA48 NCQ (dept h 31/32), AA [ 13.406640] ata10.00 (slot 8): SN:VYG80Z6M [ 13.417605] ata10.00 (slot 8): disabling queued TRIM support [ 13.417609] ata10.00 (slot 8): configured for UDMA/133 [ 14.528443] ata6.01 : hard resetting link [ 15.002148] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 15.008772] ata6.02 : hard resetting link [ 15.482427] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 15.489051] ata6.03 : hard resetting link [ 15.963269] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 15.969856] ata6.04 : hard resetting link [ 16.278511] ata6.04 : SATA link down (SStatus 0 SControl 320) [ 16.284275] ata6 : No present pin info for SATA link down event [ 16.886136] ata5 (slot 4): link is slow to respond, please be patient (ready =-19) [ 16.893625] ata2 (slot 1): link is slow to respond, please be patient (ready =-19) [ 16.922136] ata4 (slot 3): link is slow to respond, please be patient (ready =-19) [ 16.963131] ata3 (slot 2): link is slow to respond, please be patient (ready =-19) [ 18.291839] ata6.00 : hard resetting link [ 18.295886] ata8 (slot 6): link is slow to respond, please be patient (ready =-19) [ 18.303443] ata9 (slot 7): link is slow to respond, please be patient (ready =-19) [ 18.310981] ata7 (slot 5): link is slow to respond, please be patient (ready =-19) [ 18.787694] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 18.794787] ata6.00 : supports DRM functions and may not be fully accessible [ 21.687419] ata5 (slot 4): SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 21.694399] ata5.00 (slot 4): link online but device misclassified [ 21.694401] ata5 (slot 4): link online but 1 devices misclassified, retrying [ 21.701472] ata2 (slot 1): SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 21.708441] ata2.00 (slot 1): link online but device misclassified [ 21.708443] ata2 (slot 1): link online but 1 devices misclassified, retrying [ 21.764012] ata3 (slot 2): SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 21.770976] ata3.00 (slot 2): link online but device misclassified [ 21.770977] ata3 (slot 2): link online but 1 devices misclassified, retrying [ 21.771246] ata8 (slot 6): SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 21.771253] ata8.00 (slot 6): link online but device misclassified [ 21.771255] ata8 (slot 6): link online but 1 devices misclassified, retrying [ 21.778036] ata9 (slot 7): SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 21.778044] ata9.00 (slot 7): link online but device misclassified [ 21.778045] ata9 (slot 7): link online but 1 devices misclassified, retrying [ 21.790039] ata7 (slot 5): SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 21.790047] ata7.00 (slot 5): link online but device misclassified [ 21.790049] ata7 (slot 5): link online but 1 devices misclassified, retrying [ 21.820068] ata4 (slot 3): SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 21.827040] ata4.00 (slot 3): link online but device misclassified [ 21.827043] ata4 (slot 3): link online but 1 devices misclassified, retrying [ 27.067257] ata5 (slot 4): link is slow to respond, please be patient (ready =-19) [ 27.074750] ata2 (slot 1): link is slow to respond, please be patient (ready =-19) [ 27.125256] ata8 (slot 6): link is slow to respond, please be patient (ready =-19) [ 27.132753] ata9 (slot 7): link is slow to respond, please be patient (ready =-19) [ 27.144255] ata7 (slot 5): link is slow to respond, please be patient (ready =-19) [ 27.185898] ata3 (slot 2): link is slow to respond, please be patient (ready =-19) [ 27.193389] ata4 (slot 3): link is slow to respond, please be patient (ready =-19) [ 29.796330] ata3 (slot 2): SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 29.819855] ata3.00 (slot 2): disabling queued TRIM support [ 29.819858] ata3.00 (slot 2): ATA-10: ST8000VN0022-2EL112, SC61, max UDMA/13 3 [ 29.826997] ata3.00 (slot 2): 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 29.834998] ata3.00 (slot 2): SN: ZA181JX3 [ 29.843174] ata3.00 (slot 2): disabling queued TRIM support [ 29.843179] ata3.00 (slot 2): configured for UDMA/133 [ 29.939814] ata2 (slot 1): SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 29.949921] ata2.00 (slot 1): disabling queued TRIM support [ 29.949926] ata2.00 (slot 1): ATA-10: ST8000VN0022-2EL112, SC61, max UDMA/13 3 [ 29.957090] ata2.00 (slot 1): 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 29.965094] ata2.00 (slot 1): SN: ZA1CQQYS [ 29.973090] ata2.00 (slot 1): disabling queued TRIM support [ 29.973095] ata2.00 (slot 1): configured for UDMA/133 [ 29.981133] scsi 1:0:0:0: Direct-Access ATA ST8000VN0022-2EL112 SC61 PQ: 0 ANSI: 5 [ 29.990196] got SATA disk[0] [ 29.993179] sd 1:0:0:0: [sata1] 15628053168 512-byte logical blocks: (8.00 T B/7.28 TiB) [ 29.997595] scsi 2:0:0:0: Direct-Access ATA ST8000VN0022-2EL112 SC61 PQ: 0 ANSI: 5 [ 29.997897] got SATA disk[1] [ 29.997975] sd 2:0:0:0: [sata2] 15628053168 512-byte logical blocks: (8.00 T B/7.28 TiB) [ 29.997977] sd 2:0:0:0: [sata2] 4096-byte physical blocks [ 29.998018] sd 2:0:0:0: [sata2] Write Protect is off [ 29.998021] sd 2:0:0:0: [sata2] Mode Sense: 00 3a 00 10 [ 29.998040] sd 2:0:0:0: [sata2] Write cache: enabled, read cache: enabled, s upports DPO and FUA [ 30.044813] sd 1:0:0:0: [sata1] 4096-byte physical blocks [ 30.050278] sata2: p1 p2 p5 [ 30.050313] sd 1:0:0:0: [sata1] Write Protect is off [ 30.050317] sd 1:0:0:0: [sata1] Mode Sense: 00 3a 00 10 [ 30.050340] sd 1:0:0:0: [sata1] Write cache: enabled, read cache: enabled, s upports DPO and FUA [ 30.067193] sd 2:0:0:0: [sata2] Attached SCSI disk [ 30.110049] sata1: p1 p2 p5 [ 30.113269] sd 1:0:0:0: [sata1] Attached SCSI disk [ 30.267993] ata6.00 : disabling queued TRIM support [ 30.267999] ata6.00 : ATA-9: WDC WD80EDAZ-11TA3A0, 81.00A81, max UDMA/133 [ 30.274798] ata6.00 : 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 30.282102] ata6.00 : SN:VGJ9829G [ 30.391083] ata6.00 : supports DRM functions and may not be fully accessible [ 30.402773] ata6.00 : disabling queued TRIM support [ 30.402779] ata6.00 : configured for UDMA/133 [ 30.407671] ata6.01 : supports DRM functions and may not be fully accessible [ 30.584167] ata4 (slot 3): SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 30.594648] ata4.00 (slot 3): disabling queued TRIM support [ 30.594654] ata4.00 (slot 3): ATA-10: ST8000VN0022-2EL112, SC61, max UDMA/13 3 [ 30.601795] ata4.00 (slot 3): 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 30.609793] ata4.00 (slot 3): SN: ZA19ZCSS [ 30.617797] ata4.00 (slot 3): disabling queued TRIM support [ 30.617803] ata4.00 (slot 3): configured for UDMA/133 [ 30.625839] scsi 3:0:0:0: Direct-Access ATA ST8000VN0022-2EL112 SC61 PQ: 0 ANSI: 5 [ 30.635123] got SATA disk[2] [ 30.638100] sd 3:0:0:0: [sata3] 15628053168 512-byte logical blocks: (8.00 T B/7.28 TiB) [ 30.646115] sd 3:0:0:0: [sata3] 4096-byte physical blocks [ 30.651683] sd 3:0:0:0: [sata3] Write Protect is off [ 30.656664] sd 3:0:0:0: [sata3] Mode Sense: 00 3a 00 10 [ 30.656725] sd 3:0:0:0: [sata3] Write cache: enabled, read cache: enabled, s upports DPO and FUA [ 30.718240] sata3: p1 p2 p5 [ 30.721430] sd 3:0:0:0: [sata3] Attached SCSI disk [ 31.229150] ata5 (slot 4): SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 31.239648] ata5.00 (slot 4): disabling queued TRIM support [ 31.239655] ata5.00 (slot 4): ATA-10: ST8000VN0022-2EL112, SC61, max UDMA/13 3 [ 31.246801] ata5.00 (slot 4): 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 31.254799] ata5.00 (slot 4): SN: ZA19ZCYL [ 31.262820] ata5.00 (slot 4): disabling queued TRIM support [ 31.262825] ata5.00 (slot 4): configured for UDMA/133 [ 31.270903] scsi 4:0:0:0: Direct-Access ATA ST8000VN0022-2EL112 SC61 PQ: 0 ANSI: 5 [ 31.280213] got SATA disk[3] [ 31.283256] sd 4:0:0:0: [sata4] 15628053168 512-byte logical blocks: (8.00 T B/7.28 TiB) [ 31.291279] sd 4:0:0:0: [sata4] 4096-byte physical blocks [ 31.296850] sd 4:0:0:0: [sata4] Write Protect is off [ 31.301838] sd 4:0:0:0: [sata4] Mode Sense: 00 3a 00 10 [ 31.301889] sd 4:0:0:0: [sata4] Write cache: enabled, read cache: enabled, s upports DPO and FUA [ 31.372871] sata4: p1 p2 p5 [ 31.376146] sd 4:0:0:0: [sata4] Attached SCSI disk [ 31.743138] ata9 (slot 7): SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 31.753645] ata9.00 (slot 7): disabling queued TRIM support [ 31.753654] ata9.00 (slot 7): ATA-10: ST8000VN0022-2EL112, SC61, max UDMA/13 3 [ 31.760802] ata9.00 (slot 7): 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 31.768798] ata9.00 (slot 7): SN: ZA1D91C1 [ 31.776821] ata9.00 (slot 7): disabling queued TRIM support [ 31.776826] ata9.00 (slot 7): configured for UDMA/133 [ 31.796766] ata7 (slot 5): SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 31.813105] ata7.00 (slot 5): disabling queued TRIM support [ 31.813111] ata7.00 (slot 5): ATA-10: ST8000VN0022-2EL112, SC61, max UDMA/13 3 [ 31.820251] ata7.00 (slot 5): 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 31.828247] ata7.00 (slot 5): SN: ZA1E9QJL [ 31.836276] ata7.00 (slot 5): disabling queued TRIM support [ 31.836281] ata7.00 (slot 5): configured for UDMA/133 [ 31.935131] ata8 (slot 6): SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 31.942106] ata8.00 (slot 6): link online but device misclassified [ 31.942108] ata8 (slot 6): link online but 1 devices misclassified, retrying [ 32.409121] ata8 (slot 6): SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 32.432387] ata8.00 (slot 6): disabling queued TRIM support [ 32.432394] ata8.00 (slot 6): ATA-10: ST8000VN0022-2EL112, SC61, max UDMA/13 3 [ 32.439543] ata8.00 (slot 6): 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 32.447541] ata8.00 (slot 6): SN: ZA1DEE37 [ 32.455576] ata8.00 (slot 6): disabling queued TRIM support [ 32.455580] ata8.00 (slot 6): configured for UDMA/133 [ 41.654370] ata6.01 : disabling queued TRIM support [ 41.654378] ata6.01 : ATA-9: WDC WD80EDBZ-11B0ZA0, 85.00A85, max UDMA/133 [ 41.661204] ata6.01 : 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 41.668512] ata6.01 : SN:VRGG9WKK [ 41.785706] ata6.01 : supports DRM functions and may not be fully accessible [ 41.796897] ata6.01 : disabling queued TRIM support [ 41.796909] ata6.01 : configured for UDMA/133 [ 41.801786] ata6.02 : supports DRM functions and may not be fully accessible [ 53.230709] ata6.02 : disabling queued TRIM support [ 53.230718] ata6.02 : ATA-9: WDC WD80EDBZ-11B0ZA0, 85.00A85, max UDMA/133 [ 53.237537] ata6.02 : 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 53.244848] ata6.02 : SN:VRGKPYGK [ 53.366175] ata6.02 : supports DRM functions and may not be fully accessible [ 53.377354] ata6.02 : disabling queued TRIM support [ 53.377368] ata6.02 : configured for UDMA/133 [ 64.705070] ata6.03 : disabling queued TRIM support [ 64.705078] ata6.03 : ATA-9: WDC WD80EFBX-68AZZN0, 85.00A85, max UDMA/133 [ 64.711894] ata6.03 : 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 64.719204] ata6.03 : SN:VYG7YL5M [ 64.838673] ata6.03 : disabling queued TRIM support [ 64.838685] ata6.03 : configured for UDMA/133 [ 64.843141] ata6 : EH complete [ 64.887912] got SATA disk[4] [ 64.890964] sd 5:0:0:0: [sata5] 15628053168 512-byte logical blocks: (8.00 T B/7.28 TiB) [ 64.899058] sd 5:0:0:0: [sata5] 4096-byte physical blocks [ 64.899447] got SATA disk[5] [ 64.899568] sd 5:1:0:0: [sata6] 15628053168 512-byte logical blocks: (8.00 T B/7.28 TiB) [ 64.899570] sd 5:1:0:0: [sata6] 4096-byte physical blocks [ 64.899614] sd 5:1:0:0: [sata6] Write Protect is off [ 64.899617] sd 5:1:0:0: [sata6] Mode Sense: 00 3a 00 10 [ 64.899636] sd 5:1:0:0: [sata6] Write cache: enabled, read cache: enabled, s upports DPO and FUA [ 64.900217] got SATA disk[6] [ 64.900312] sd 5:2:0:0: [sata7] 15628053168 512-byte logical blocks: (8.00 T B/7.28 TiB) [ 64.900315] sd 5:2:0:0: [sata7] 4096-byte physical blocks [ 64.900354] sd 5:2:0:0: [sata7] Write Protect is off [ 64.900356] sd 5:2:0:0: [sata7] Mode Sense: 00 3a 00 10 [ 64.900372] sd 5:2:0:0: [sata7] Write cache: enabled, read cache: enabled, s upports DPO and FUA [ 64.902306] got SATA disk[7] [ 64.902496] sd 5:3:0:0: [sata8] 15628053168 512-byte logical blocks: (8.00 T B/7.28 TiB) [ 64.902499] sd 5:3:0:0: [sata8] 4096-byte physical blocks [ 64.902541] sd 5:3:0:0: [sata8] Write Protect is off [ 64.902544] sd 5:3:0:0: [sata8] Mode Sense: 00 3a 00 10 [ 64.902561] sd 5:3:0:0: [sata8] Write cache: enabled, read cache: enabled, s upports DPO and FUA [ 64.948472] sata7: p1 p2 p5 [ 64.948844] sd 5:2:0:0: [sata7] Attached SCSI disk [ 64.952790] sata6: p1 p2 p5 [ 64.953307] sd 5:1:0:0: [sata6] Attached SCSI disk [ 64.959030] sata8: p1 p2 p5 [ 64.959475] sd 5:3:0:0: [sata8] Attached SCSI disk [ 65.043995] scsi 6:0:0:0: Direct-Access ATA ST8000VN0022-2EL112 SC61 PQ: 0 ANSI: 5 [ 65.044067] sd 5:0:0:0: [sata5] Write Protect is off [ 65.044070] sd 5:0:0:0: [sata5] Mode Sense: 00 3a 00 10 [ 65.044095] sd 5:0:0:0: [sata5] Write cache: enabled, read cache: enabled, s upports DPO and FUA [ 65.066724] got SATA disk[8] [ 65.069747] sd 6:0:0:0: [sata9] 15628053168 512-byte logical blocks: (8.00 T B/7.28 TiB) [ 65.077824] sd 6:0:0:0: [sata9] 4096-byte physical blocks [ 65.083334] sd 6:0:0:0: [sata9] Write Protect is off [ 65.088317] sd 6:0:0:0: [sata9] Mode Sense: 00 3a 00 10 [ 65.088352] scsi 7:0:0:0: Direct-Access ATA ST8000VN0022-2EL112 SC61 PQ: 0 ANSI: 5 [ 65.088360] sd 6:0:0:0: [sata9] Write cache: enabled, read cache: enabled, s upports DPO and FUA [ 65.096417] sata5: p1 p2 p5 [ 65.096756] sd 5:0:0:0: [sata5] Attached SCSI disk [ 65.113879] got SATA disk[9] [ 65.116898] sd 7:0:0:0: [sata10] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB) [ 65.124997] sd 7:0:0:0: [sata10] 4096-byte physical blocks [ 65.129871] scsi 8:0:0:0: Direct-Access ATA ST8000VN0022-2EL112 SC61 PQ: 0 ANSI: 5 [ 65.130227] got SATA disk[10] [ 65.130328] sd 8:0:0:0: [sata11] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB) [ 65.130331] sd 8:0:0:0: [sata11] 4096-byte physical blocks [ 65.130390] sd 8:0:0:0: [sata11] Write Protect is off [ 65.130393] sd 8:0:0:0: [sata11] Mode Sense: 00 3a 00 10 [ 65.130413] sd 8:0:0:0: [sata11] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 65.131139] got SATA disk[11] [ 65.131225] sd 9:0:0:0: [sata12] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB) [ 65.131228] sd 9:0:0:0: [sata12] 4096-byte physical blocks [ 65.131268] sd 9:0:0:0: [sata12] Write Protect is off [ 65.131271] sd 9:0:0:0: [sata12] Mode Sense: 00 3a 00 10 [ 65.131287] sd 9:0:0:0: [sata12] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 65.152914] sata9: p1 p2 p5 [ 65.153214] sd 6:0:0:0: [sata9] Attached SCSI disk [ 65.184901] sata12: p1 p2 p5 [ 65.185253] sd 9:0:0:0: [sata12] Attached SCSI disk [ 65.187030] sata11: p1 p2 p5 [ 65.187470] sd 8:0:0:0: [sata11] Attached SCSI disk [ 65.232578] sd 7:0:0:0: [sata10] Write Protect is off [ 65.237640] sd 7:0:0:0: [sata10] Mode Sense: 00 3a 00 10 [ 65.237668] sd 7:0:0:0: [sata10] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 65.313113] sata10: p1 p2 p5 [ 65.316415] sd 7:0:0:0: [sata10] Attached SCSI disk [ 65.327751] Write protecting the kernel read-only data: 8192k [ 66.444467] md: bind<sata2p1> [ 66.448683] md: bind<sata3p1> [ 66.451868] md: bind<sata4p1> [ 66.455044] md: bind<sata9p1> [ 66.458187] md: bind<sata10p1> [ 66.461417] md: bind<sata11p1> [ 66.464591] md: bind<sata12p1> [ 66.467808] md: bind<sata1p1> [ 67.814934] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 67.920066] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: prjquota,rootprjquota,barrier=1 [ 72.397396] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 72.715468] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: prjquota,rootprjquota,barrier=1 [ 75.646845] acpi-cpufreq: overriding BIOS provided _PSD data [ 76.484885] md: bind<sata2p2> [ 76.485065] md: bind<sata3p2> [ 76.496051] md: bind<sata4p2> [ 76.499185] md: bind<sata9p2> [ 76.513559] md: bind<sata10p2> [ 76.528022] md: bind<sata11p2> [ 76.540947] md: bind<sata12p2> [ 76.553064] md: bind<sata1p2> [ 79.231405] ata6.00 : failed to read SCR 1 (Emask=0x40) [ 79.236661] ata6.01 : failed to read SCR 1 (Emask=0x40) [ 79.241945] ata6.02 : failed to read SCR 1 (Emask=0x40) [ 79.247199] ata6.03 : failed to read SCR 1 (Emask=0x40) [ 79.252442] ata6.04 : failed to read SCR 1 (Emask=0x40) [ 79.257694] ata6.00 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 79.265046] ata6.01 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 79.272399] ata6.02 : exception Emask 0x1 SAct 0x18 SErr 0x0 action 0x6 froz en [ 79.279654] ata6.02 : failed command: READ FPDMA QUEUED [ 79.284943] ata6.02 : cmd 60/08:18:10:35:7e/00:00:a3:03:00/40 tag 3 ncq 4096 in [ 79.300072] ata6.02 : status: { DRDY } [ 79.303856] ata6.02 : failed command: READ FPDMA QUEUED [ 79.309146] ata6.02 : cmd 60/08:20:e0:5e:44/00:00:01:00:00/40 tag 4 ncq 4096 in [ 79.324268] ata6.02 : status: { DRDY } [ 79.328047] ata6.03 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 79.335386] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 79.342725] ata6.15 : hard resetting link [ 80.061384] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 80.068112] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1) [ 80.073977] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1) [ 81.111316] ata6.01 : hard resetting link [ 81.586887] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 81.593519] ata6.02 : hard resetting link [ 82.066865] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 82.073475] ata6.03 : hard resetting link [ 82.354935] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts : (null) [ 82.549851] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 82.556471] ata6.04 : hard resetting link [ 82.866561] ata6.04 : SATA link down (SStatus 0 SControl 320) [ 82.873815] ata6 : No present pin info for SATA link down event [ 84.886619] ata6.00 : hard resetting link [ 85.363485] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 85.370627] ata6.00 : supports DRM functions and may not be fully accessible [ 85.382217] ata6.00 : disabling queued TRIM support [ 85.385907] ata6.00 : supports DRM functions and may not be fully accessible [ 85.397754] ata6.00 : disabling queued TRIM support [ 85.397759] ata6.00 : configured for UDMA/133 [ 85.402923] ata6.01 : supports DRM functions and may not be fully accessible [ 85.413777] ata6.01 : disabling queued TRIM support [ 85.417148] ata6.01 : supports DRM functions and may not be fully accessible [ 85.428029] ata6.01 : disabling queued TRIM support [ 85.428033] ata6.01 : configured for UDMA/133 [ 85.433071] ata6.02 : supports DRM functions and may not be fully accessible [ 85.443826] ata6.02 : disabling queued TRIM support [ 85.447078] ata6.02 : supports DRM functions and may not be fully accessible [ 85.457837] ata6.02 : disabling queued TRIM support [ 85.457841] ata6.02 : configured for UDMA/133 [ 85.475633] ata6.03 : disabling queued TRIM support [ 85.489499] ata6.03 : disabling queued TRIM support [ 85.489503] ata6.03 : configured for UDMA/133 [ 85.494075] ata6 : EH complete [ 85.567239] ata6.00 : failed to read SCR 1 (Emask=0x40) [ 85.572481] ata6.01 : failed to read SCR 1 (Emask=0x40) [ 85.577726] ata6.02 : failed to read SCR 1 (Emask=0x40) [ 85.582963] ata6.03 : failed to read SCR 1 (Emask=0x40) [ 85.588196] ata6.04 : failed to read SCR 1 (Emask=0x40) [ 85.593426] ata6.00 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 85.600746] ata6.01 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 85.608061] ata6.02 : exception Emask 0x1 SAct 0x30000 SErr 0x0 action 0x6 f rozen [ 85.615546] ata6.02 : failed command: READ FPDMA QUEUED [ 85.620775] ata6.02 : cmd 60/08:80:10:35:7e/00:00:a3:03:00/40 tag 16 ncq 409 6 in [ 85.635972] ata6.02 : status: { DRDY } [ 85.639728] ata6.02 : failed command: READ FPDMA QUEUED [ 85.644959] ata6.02 : cmd 60/08:88:10:35:7e/00:00:a3:03:00/40 tag 17 ncq 409 6 in [ 85.668151] ata6.02 : status: { DRDY } [ 85.671912] ata6.03 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 85.679223] ata6.03 : failed command: READ LOG EXT [ 85.684020] ata6.03 : cmd 2f/00:01:e0:00:00/00:00:00:00:00/00 tag 18 pio 512 in [ 85.699389] ata6.03 : status: { DRDY } [ 85.703145] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 85.710462] ata6.15 : hard resetting link [ 86.430585] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 86.437380] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1) [ 86.443399] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1) [ 87.481231] ata6.01 : hard resetting link [ 87.954126] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 87.960746] ata6.02 : hard resetting link [ 88.434399] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 88.441033] ata6.03 : hard resetting link [ 88.917662] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 88.924252] ata6.04 : hard resetting link [ 89.234390] ata6.04 : SATA link down (SStatus 0 SControl 320) [ 89.240165] ata6 : No present pin info for SATA link down event [ 91.247751] ata6.00 : hard resetting link [ 91.721576] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 91.728645] ata6.00 : supports DRM functions and may not be fully accessible [ 91.740163] ata6.00 : disabling queued TRIM support [ 91.743815] ata6.00 : supports DRM functions and may not be fully accessible [ 91.755420] ata6.00 : disabling queued TRIM support [ 91.755426] ata6.00 : configured for UDMA/133 [ 91.760316] ata6.01 : supports DRM functions and may not be fully accessible [ 91.774572] ata6.01 : disabling queued TRIM support [ 91.777953] ata6.01 : supports DRM functions and may not be fully accessible [ 91.788867] ata6.01 : disabling queued TRIM support [ 91.788871] ata6.01 : configured for UDMA/133 [ 91.793812] ata6.02 : supports DRM functions and may not be fully accessible [ 91.804547] ata6.02 : disabling queued TRIM support [ 91.807858] ata6.02 : supports DRM functions and may not be fully accessible [ 91.818622] ata6.02 : disabling queued TRIM support [ 91.818626] ata6.02 : configured for UDMA/133 [ 91.827375] ata6.03 : disabling queued TRIM support [ 91.834382] ata6.03 : disabling queued TRIM support [ 91.834386] ata6.03 : configured for UDMA/133 [ 91.838954] ata6 : EH complete [ 92.415597] md: bind<sata2p5> [ 92.418784] md: bind<sata3p5> [ 92.421953] md: bind<sata4p5> [ 92.425119] md: bind<sata9p5> [ 92.428277] md: bind<sata10p5> [ 92.431516] md: bind<sata11p5> [ 92.434720] md: bind<sata12p5> [ 92.437988] md: bind<sata1p5> [ 92.516953] md/raid:md2: device sata1p5 operational as raid disk 0 [ 92.523144] md/raid:md2: device sata12p5 operational as raid disk 7 [ 92.529409] md/raid:md2: device sata11p5 operational as raid disk 6 [ 92.535676] md/raid:md2: device sata10p5 operational as raid disk 5 [ 92.541942] md/raid:md2: device sata9p5 operational as raid disk 4 [ 92.548122] md/raid:md2: device sata4p5 operational as raid disk 3 [ 92.554301] md/raid:md2: device sata3p5 operational as raid disk 2 [ 92.560478] md/raid:md2: device sata2p5 operational as raid disk 1 [ 92.579016] disk 0, o:1, dev:sata1p5 [ 92.579019] disk 1, o:1, dev:sata2p5 [ 92.579021] disk 2, o:1, dev:sata3p5 [ 92.579024] disk 3, o:1, dev:sata4p5 [ 92.579026] disk 4, o:1, dev:sata9p5 [ 92.579028] disk 5, o:1, dev:sata10p5 [ 92.579030] disk 6, o:1, dev:sata11p5 [ 92.579032] disk 7, o:1, dev:sata12p5 [ 92.628095] md: bind<sata6p5> [ 92.631269] md: bind<sata7p5> [ 92.634471] md: bind<sata8p5> [ 92.637676] md: bind<sata5p5> [ 92.643302] md/raid:md3: device sata5p5 operational as raid disk 0 [ 92.649498] md/raid:md3: device sata8p5 operational as raid disk 3 [ 92.655695] md/raid:md3: device sata7p5 operational as raid disk 2 [ 92.661886] md/raid:md3: device sata6p5 operational as raid disk 1 [ 92.680062] disk 0, o:1, dev:sata5p5 [ 92.680064] disk 1, o:1, dev:sata6p5 [ 92.680065] disk 2, o:1, dev:sata7p5 [ 92.680067] disk 3, o:1, dev:sata8p5 [ 92.768017] ata6.00 : failed to read SCR 1 (Emask=0x40) [ 92.773264] ata6.01 : failed to read SCR 1 (Emask=0x40) [ 92.778518] ata6.02 : failed to read SCR 1 (Emask=0x40) [ 92.783751] ata6.03 : failed to read SCR 1 (Emask=0x40) [ 92.788982] ata6.04 : failed to read SCR 1 (Emask=0x40) [ 92.794226] ata6.00 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 92.801549] ata6.01 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 92.808861] ata6.02 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 92.816179] ata6.03 : exception Emask 0x1 SAct 0x28 SErr 0x0 action 0x6 froz en [ 92.823403] ata6.03 : failed command: READ FPDMA QUEUED [ 92.828635] ata6.03 : cmd 60/08:18:e8:5e:44/00:00:01:00:00/40 tag 3 ncq 4096 in [ 92.843746] ata6.03 : status: { DRDY } [ 92.847503] ata6.03 : failed command: READ FPDMA QUEUED [ 92.852740] ata6.03 : cmd 60/01:28:e0:5e:44/00:00:01:00:00/40 tag 5 ncq 512 in [ 92.867768] ata6.03 : status: { DRDY } [ 92.871535] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 92.878849] ata6.15 : hard resetting link [ 93.599041] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 93.606078] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1) [ 93.611883] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1) [ 94.649504] ata6.04 : limiting SATA link speed to 1.5 Gbps [ 94.655031] ata6.01 : hard resetting link [ 95.127557] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 95.134424] ata6.02 : hard resetting link [ 95.607316] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 95.614151] ata6.03 : hard resetting link [ 96.087595] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 96.094186] ata6.04 : hard resetting link [ 96.403393] ata6.04 : SATA link down (SStatus 0 SControl 310) [ 96.409155] ata6 : No present pin info for SATA link down event [ 98.416829] ata6.00 : hard resetting link [ 98.890875] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 98.898028] ata6.00 : supports DRM functions and may not be fully accessible [ 98.909648] ata6.00 : disabling queued TRIM support [ 98.913333] ata6.00 : supports DRM functions and may not be fully accessible [ 98.924982] ata6.00 : disabling queued TRIM support [ 98.924986] ata6.00 : configured for UDMA/133 [ 98.930011] ata6.01 : supports DRM functions and may not be fully accessible [ 98.940856] ata6.01 : disabling queued TRIM support [ 98.944310] ata6.01 : supports DRM functions and may not be fully accessible [ 98.955169] ata6.01 : disabling queued TRIM support [ 98.955172] ata6.01 : configured for UDMA/133 [ 98.960238] ata6.02 : supports DRM functions and may not be fully accessible [ 98.970964] ata6.02 : disabling queued TRIM support [ 98.974262] ata6.02 : supports DRM functions and may not be fully accessible [ 98.985025] ata6.02 : disabling queued TRIM support [ 98.985028] ata6.02 : configured for UDMA/133 [ 98.993801] ata6.03 : disabling queued TRIM support [ 99.000813] ata6.03 : disabling queued TRIM support [ 99.000816] ata6.03 : configured for UDMA/133 [ 99.005380] ata6 : EH complete [ 99.929941] ata6.00 : failed to read SCR 1 (Emask=0x40) [ 99.935183] ata6.01 : failed to read SCR 1 (Emask=0x40) [ 99.940415] ata6.02 : failed to read SCR 1 (Emask=0x40) [ 99.945645] ata6.03 : failed to read SCR 1 (Emask=0x40) [ 99.950877] ata6.04 : failed to read SCR 1 (Emask=0x40) [ 99.956111] ata6.00 : exception Emask 0x100 SAct 0x8000 SErr 0x0 action 0x6 frozen [ 99.963686] ata6.00 : failed command: READ FPDMA QUEUED [ 99.968922] ata6.00 : cmd 60/08:78:a8:2a:81/00:00:a3:03:00/40 tag 15 ncq 409 6 in [ 99.984377] ata6.00 : status: { DRDY } [ 99.988164] ata6.01 : exception Emask 0x100 SAct 0x400000 SErr 0x0 action 0x 6 frozen [ 99.995907] ata6.01 : failed command: READ FPDMA QUEUED [ 100.001140] ata6.01 : cmd 60/20:b0:00:00:00/00:00:00:00:00/40 tag 22 ncq 163 84 in [ 100.016689] ata6.01 : status: { DRDY } [ 100.020455] ata6.02 : exception Emask 0x100 SAct 0x40000 SErr 0x0 action 0x6 frozen [ 100.028107] ata6.02 : failed command: READ FPDMA QUEUED [ 100.033336] ata6.02 : cmd 60/20:90:00:00:00/00:00:00:00:00/40 tag 18 ncq 163 84 in [ 100.048881] ata6.02 : status: { DRDY } [ 100.052639] ata6.03 : exception Emask 0x1 SAct 0x1800000 SErr 0x0 action 0x6 frozen [ 100.060296] ata6.03 : failed command: READ FPDMA QUEUED [ 100.065529] ata6.03 : cmd 60/40:b8:20:00:00/00:00:00:00:00/40 tag 23 ncq 327 68 in [ 100.080813] ata6.03 : status: { DRDY } [ 100.084567] ata6.03 : failed command: READ FPDMA QUEUED [ 100.089797] ata6.03 : cmd 60/80:c0:60:00:00/00:00:00:00:00/40 tag 24 ncq 655 36 in [ 100.105077] ata6.03 : status: { DRDY } [ 100.108837] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 100.116150] ata6.15 : hard resetting link [ 100.835139] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 100.841918] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1) [ 100.847720] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1) [ 101.885205] ata6.04 : limiting SATA link speed to 1.5 Gbps [ 101.890714] ata6.01 : hard resetting link [ 102.364629] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 102.371238] ata6.02 : hard resetting link [ 102.846771] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 102.853368] ata6.03 : hard resetting link [ 103.326986] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 103.333596] ata6.04 : hard resetting link [ 103.642870] ata6.04 : SATA link down (SStatus 0 SControl 310) [ 103.648635] ata6 : No present pin info for SATA link down event [ 105.656161] ata6.00 : hard resetting link [ 106.129477] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 106.136828] ata6.00 : supports DRM functions and may not be fully accessible [ 106.148448] ata6.00 : disabling queued TRIM support [ 106.152157] ata6.00 : supports DRM functions and may not be fully accessible [ 106.163773] ata6.00 : disabling queued TRIM support [ 106.163778] ata6.00 : configured for UDMA/133 [ 106.168738] ata6.01 : supports DRM functions and may not be fully accessible [ 106.179587] ata6.01 : disabling queued TRIM support [ 106.182969] ata6.01 : supports DRM functions and may not be fully accessible [ 106.193939] ata6.01 : disabling queued TRIM support [ 106.193943] ata6.01 : configured for UDMA/133 [ 106.198916] ata6.02 : supports DRM functions and may not be fully accessible [ 106.215836] ata6.02 : disabling queued TRIM support [ 106.219083] ata6.02 : supports DRM functions and may not be fully accessible [ 106.229815] ata6.02 : disabling queued TRIM support [ 106.229819] ata6.02 : configured for UDMA/133 [ 106.238628] ata6.03 : disabling queued TRIM support [ 106.245628] ata6.03 : disabling queued TRIM support [ 106.245632] ata6.03 : configured for UDMA/133 [ 106.250081] ata6 : EH complete [ 106.280909] ata6.00 : failed to read SCR 1 (Emask=0x40) [ 106.286144] ata6.01 : failed to read SCR 1 (Emask=0x40) [ 106.291372] ata6.02 : failed to read SCR 1 (Emask=0x40) [ 106.296596] ata6.03 : failed to read SCR 1 (Emask=0x40) [ 106.301821] ata6.04 : failed to read SCR 1 (Emask=0x40) [ 106.307050] ata6.00 : exception Emask 0x100 SAct 0x4000000 SErr 0x0 action 0 x6 frozen [ 106.314875] ata6.00 : failed command: READ FPDMA QUEUED [ 106.320106] ata6.00 : cmd 60/08:d0:a8:2a:81/00:00:a3:03:00/40 tag 26 ncq 409 6 in [ 106.335558] ata6.00 : status: { DRDY } [ 106.339318] ata6.01 : exception Emask 0x100 SAct 0x10000000 SErr 0x0 action 0x6 frozen [ 106.347233] ata6.01 : failed command: READ FPDMA QUEUED [ 106.352461] ata6.01 : cmd 60/20:e0:00:00:00/00:00:00:00:00/40 tag 28 ncq 163 84 in [ 106.368000] ata6.01 : status: { DRDY } [ 106.371756] ata6.02 : exception Emask 0x100 SAct 0x20000000 SErr 0x0 action 0x6 frozen [ 106.379666] ata6.02 : failed command: READ FPDMA QUEUED [ 106.384892] ata6.02 : cmd 60/20:e8:00:00:00/00:00:00:00:00/40 tag 29 ncq 163 84 in [ 106.400431] ata6.02 : status: { DRDY } [ 106.404190] ata6.03 : exception Emask 0x1 SAct 0x40100000 SErr 0x0 action 0x 6 frozen [ 106.411930] ata6.03 : failed command: READ FPDMA QUEUED [ 106.417173] ata6.03 : cmd 60/08:a0:a8:2a:81/00:00:a3:03:00/40 tag 20 ncq 409 6 in [ 106.432367] ata6.03 : status: { DRDY } [ 106.436121] ata6.03 : failed command: READ FPDMA QUEUED [ 106.441350] ata6.03 : cmd 60/80:f0:60:00:00/00:00:00:00:00/40 tag 30 ncq 655 36 in [ 106.456626] ata6.03 : status: { DRDY } [ 106.460382] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 106.467693] ata6.15 : hard resetting link [ 107.185912] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 107.192696] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1) [ 107.198498] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1) [ 108.235948] ata6.04 : limiting SATA link speed to 1.5 Gbps [ 108.241449] ata6.01 : hard resetting link [ 108.714532] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 108.721142] ata6.02 : hard resetting link [ 109.195339] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 109.201965] ata6.03 : hard resetting link [ 109.674810] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 109.681596] ata6.04 : hard resetting link [ 109.990805] ata6.04 : SATA link down (SStatus 0 SControl 310) [ 109.996568] ata6 : No present pin info for SATA link down event [ 112.004547] ata6.00 : hard resetting link [ 112.478329] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 112.485441] ata6.00 : supports DRM functions and may not be fully accessible [ 112.497042] ata6.00 : disabling queued TRIM support [ 112.500761] ata6.00 : supports DRM functions and may not be fully accessible [ 112.512393] ata6.00 : disabling queued TRIM support [ 112.512399] ata6.00 : configured for UDMA/133 [ 112.517470] ata6.01 : supports DRM functions and may not be fully accessible [ 112.528346] ata6.01 : disabling queued TRIM support [ 112.531733] ata6.01 : supports DRM functions and may not be fully accessible [ 112.542758] ata6.01 : disabling queued TRIM support [ 112.542762] ata6.01 : configured for UDMA/133 [ 112.547840] ata6.02 : supports DRM functions and may not be fully accessible [ 112.565180] ata6.02 : disabling queued TRIM support [ 112.568439] ata6.02 : supports DRM functions and may not be fully accessible [ 112.579153] ata6.02 : disabling queued TRIM support [ 112.579157] ata6.02 : configured for UDMA/133 [ 112.587894] ata6.03 : disabling queued TRIM support [ 112.595009] ata6.03 : disabling queued TRIM support [ 112.595017] ata6.03 : configured for UDMA/133 [ 112.599530] ata6 : EH complete [ 112.631163] ata6.00 : failed to read SCR 1 (Emask=0x40) [ 112.636404] ata6.01 : failed to read SCR 1 (Emask=0x40) [ 112.641637] ata6.02 : failed to read SCR 1 (Emask=0x40) [ 112.646866] ata6.03 : failed to read SCR 1 (Emask=0x40) [ 112.652094] ata6.04 : failed to read SCR 1 (Emask=0x40) [ 112.657327] ata6.00 : exception Emask 0x100 SAct 0x400000 SErr 0x0 action 0x 6 frozen [ 112.665071] ata6.00 : failed command: READ FPDMA QUEUED [ 112.670303] ata6.00 : cmd 60/08:b0:a8:2a:81/00:00:a3:03:00/40 tag 22 ncq 409 6 in [ 112.685755] ata6.00 : status: { DRDY } [ 112.689526] ata6.01 : exception Emask 0x1 SAct 0x30000 SErr 0x0 action 0x6 f rozen [ 112.697008] ata6.01 : failed command: READ FPDMA QUEUED [ 112.702238] ata6.01 : cmd 60/40:80:20:00:00/00:00:00:00:00/40 tag 16 ncq 327 68 in [ 112.717519] ata6.01 : status: { DRDY } [ 112.721273] ata6.01 : failed command: READ FPDMA QUEUED [ 112.726502] ata6.01 : cmd 60/80:88:60:00:00/00:00:00:00:00/40 tag 17 ncq 655 36 in [ 112.741779] ata6.01 : status: { DRDY } [ 112.745537] ata6.02 : exception Emask 0x100 SAct 0x2000000 SErr 0x0 action 0 x6 frozen [ 112.753362] ata6.02 : failed command: READ FPDMA QUEUED [ 112.758589] ata6.02 : cmd 60/20:c8:00:00:00/00:00:00:00:00/40 tag 25 ncq 163 84 in [ 112.774126] ata6.02 : status: { DRDY } [ 112.777881] ata6.03 : exception Emask 0x100 SAct 0x8000000 SErr 0x0 action 0 x6 frozen [ 112.785711] ata6.03 : failed command: READ FPDMA QUEUED [ 112.790937] ata6.03 : cmd 60/08:d8:a8:2a:81/00:00:a3:03:00/40 tag 27 ncq 409 6 in [ 112.806387] ata6.03 : status: { DRDY } [ 112.810141] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 112.817453] ata6.15 : hard resetting link [ 113.536554] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 113.543344] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1) [ 113.549164] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1) [ 114.586504] ata6.04 : limiting SATA link speed to 1.5 Gbps [ 114.592003] ata6.01 : hard resetting link [ 115.066195] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 115.072801] ata6.02 : hard resetting link [ 115.544878] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 115.551674] ata6.03 : hard resetting link [ 116.025524] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 116.032150] ata6.04 : hard resetting link [ 116.341605] ata6.04 : SATA link down (SStatus 0 SControl 310) [ 116.347371] ata6 : No present pin info for SATA link down event [ 118.355102] ata6.00 : hard resetting link [ 118.829561] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 118.836686] ata6.00 : supports DRM functions and may not be fully accessible [ 118.848347] ata6.00 : disabling queued TRIM support [ 118.852085] ata6.00 : supports DRM functions and may not be fully accessible [ 118.863710] ata6.00 : disabling queued TRIM support [ 118.863716] ata6.00 : configured for UDMA/133 [ 118.868680] ata6.01 : supports DRM functions and may not be fully accessible [ 118.879517] ata6.01 : disabling queued TRIM support [ 118.882910] ata6.01 : supports DRM functions and may not be fully accessible [ 118.893941] ata6.01 : disabling queued TRIM support [ 118.893945] ata6.01 : configured for UDMA/133 [ 118.898929] ata6.02 : supports DRM functions and may not be fully accessible [ 118.909679] ata6.02 : disabling queued TRIM support [ 118.912984] ata6.02 : supports DRM functions and may not be fully accessible [ 118.923754] ata6.02 : disabling queued TRIM support [ 118.923758] ata6.02 : configured for UDMA/133 [ 118.937590] ata6.03 : disabling queued TRIM support [ 118.951111] ata6.03 : disabling queued TRIM support [ 118.951115] ata6.03 : configured for UDMA/133 [ 118.955565] ata6 : EH complete [ 118.989419] ata6.00 : failed to read SCR 1 (Emask=0x40) [ 118.994651] ata6.01 : failed to read SCR 1 (Emask=0x40) [ 118.999880] ata6.02 : failed to read SCR 1 (Emask=0x40) [ 119.005109] ata6.03 : failed to read SCR 1 (Emask=0x40) [ 119.010336] ata6.04 : failed to read SCR 1 (Emask=0x40) [ 119.015567] ata6.00 : exception Emask 0x100 SAct 0x80000 SErr 0x0 action 0x6 frozen [ 119.023222] ata6.00 : failed command: READ FPDMA QUEUED [ 119.028452] ata6.00 : cmd 60/08:98:a8:2a:81/00:00:a3:03:00/40 tag 19 ncq 409 6 in [ 119.043905] ata6.00 : status: { DRDY } [ 119.047667] ata6.01 : exception Emask 0x1 SAct 0x204000 SErr 0x0 action 0x6 frozen [ 119.055235] ata6.01 : failed command: READ FPDMA QUEUED [ 119.060465] ata6.01 : cmd 60/08:70:a8:2a:81/00:00:a3:03:00/40 tag 14 ncq 409 6 in [ 119.075658] ata6.01 : status: { DRDY } [ 119.079412] ata6.01 : failed command: READ FPDMA QUEUED [ 119.084642] ata6.01 : cmd 60/80:a8:60:00:00/00:00:00:00:00/40 tag 21 ncq 655 36 in [ 119.099921] ata6.01 : status: { DRDY } [ 119.103677] ata6.02 : exception Emask 0x100 SAct 0x800000 SErr 0x0 action 0x 6 frozen [ 119.111416] ata6.02 : failed command: READ FPDMA QUEUED [ 119.116646] ata6.02 : cmd 60/20:b8:00:00:00/00:00:00:00:00/40 tag 23 ncq 163 84 in [ 119.132183] ata6.02 : status: { DRDY } [ 119.135941] ata6.03 : exception Emask 0x100 SAct 0x2000 SErr 0x0 action 0x6 frozen [ 119.143507] ata6.03 : failed command: READ FPDMA QUEUED [ 119.148733] ata6.03 : cmd 60/20:68:88:2a:81/00:00:a3:03:00/40 tag 13 ncq 163 84 in [ 119.164271] ata6.03 : status: { DRDY } [ 119.168026] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 119.175337] ata6.15 : hard resetting link [ 119.894978] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 119.901728] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1) [ 119.907733] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1) [ 120.944926] ata6.04 : limiting SATA link speed to 1.5 Gbps [ 120.950432] ata6.01 : hard resetting link [ 121.424419] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 121.431204] ata6.02 : hard resetting link [ 121.904825] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 121.911436] ata6.03 : hard resetting link [ 122.385493] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 122.392109] ata6.04 : hard resetting link [ 122.701255] ata6.04 : SATA link down (SStatus 0 SControl 310) [ 122.707022] ata6 : No present pin info for SATA link down event [ 124.714904] ata6.00 : hard resetting link [ 125.187571] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 125.194949] ata6.00 : supports DRM functions and may not be fully accessible [ 125.206503] ata6.00 : disabling queued TRIM support [ 125.210181] ata6.00 : supports DRM functions and may not be fully accessible [ 125.221788] ata6.00 : disabling queued TRIM support [ 125.221793] ata6.00 : configured for UDMA/133 [ 125.226838] ata6.01 : supports DRM functions and may not be fully accessible [ 125.237673] ata6.01 : disabling queued TRIM support [ 125.241050] ata6.01 : supports DRM functions and may not be fully accessible [ 125.253857] ata6.01 : disabling queued TRIM support [ 125.253861] ata6.01 : configured for UDMA/133 [ 125.258948] ata6.02 : supports DRM functions and may not be fully accessible [ 125.269687] ata6.02 : disabling queued TRIM support [ 125.272995] ata6.02 : supports DRM functions and may not be fully accessible [ 125.283753] ata6.02 : disabling queued TRIM support [ 125.283757] ata6.02 : configured for UDMA/133 [ 125.292512] ata6.03 : disabling queued TRIM support [ 125.299475] ata6.03 : disabling queued TRIM support [ 125.299478] ata6.03 : configured for UDMA/133 [ 125.304047] ata6 : EH complete [ 125.340647] ata6.00 : failed to read SCR 1 (Emask=0x40) [ 125.345877] ata6.01 : failed to read SCR 1 (Emask=0x40) [ 125.351106] ata6.02 : failed to read SCR 1 (Emask=0x40) [ 125.356334] ata6.03 : failed to read SCR 1 (Emask=0x40) [ 125.361560] ata6.04 : failed to read SCR 1 (Emask=0x40) [ 125.366788] ata6.00 : exception Emask 0x100 SAct 0x8000 SErr 0x0 action 0x6 frozen [ 125.374355] ata6.00 : failed command: READ FPDMA QUEUED [ 125.379582] ata6.00 : cmd 60/08:78:80:20:00/00:00:00:00:00/40 tag 15 ncq 409 6 in [ 125.395033] ata6.00 : status: { DRDY } [ 125.398791] ata6.01 : exception Emask 0x100 SAct 0x41000 SErr 0x0 action 0x6 frozen [ 125.406442] ata6.01 : failed command: READ FPDMA QUEUED [ 125.411671] ata6.01 : cmd 60/20:60:88:2a:81/00:00:a3:03:00/40 tag 12 ncq 163 84 in [ 125.427211] ata6.01 : status: { DRDY } [ 125.430965] ata6.01 : failed command: READ FPDMA QUEUED [ 125.436193] ata6.01 : cmd 60/80:90:60:00:00/00:00:00:00:00/40 tag 18 ncq 655 36 in [ 125.451734] ata6.01 : status: { DRDY } [ 125.455490] ata6.02 : exception Emask 0x1 SAct 0x6000 SErr 0x0 action 0x6 fr ozen [ 125.462903] ata6.02 : failed command: READ FPDMA QUEUED [ 125.468145] ata6.02 : cmd 60/40:68:20:00:00/00:00:00:00:00/40 tag 13 ncq 327 68 in [ 125.483426] ata6.02 : status: { DRDY } [ 125.487181] ata6.02 : failed command: READ FPDMA QUEUED [ 125.492411] ata6.02 : cmd 60/80:70:60:00:00/00:00:00:00:00/40 tag 14 ncq 655 36 in [ 125.507690] ata6.02 : status: { DRDY } [ 125.511446] ata6.03 : exception Emask 0x100 SAct 0x800 SErr 0x0 action 0x6 f rozen [ 125.518922] ata6.03 : failed command: READ FPDMA QUEUED [ 125.524152] ata6.03 : cmd 60/08:58:80:20:00/00:00:00:00:00/40 tag 11 ncq 409 6 in [ 125.539602] ata6.03 : status: { DRDY } [ 125.543359] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 125.550670] ata6.15 : hard resetting link [ 126.270054] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 126.277025] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1) [ 126.282831] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1) [ 127.320013] ata6.04 : limiting SATA link speed to 1.5 Gbps [ 127.325515] ata6.01 : hard resetting link [ 127.798683] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 127.805297] ata6.02 : hard resetting link [ 128.278630] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 128.285252] ata6.03 : hard resetting link [ 128.757301] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 128.763881] ata6.04 : hard resetting link [ 129.073149] ata6.04 : SATA link down (SStatus 0 SControl 310) [ 129.078912] ata6 : No present pin info for SATA link down event [ 131.086600] ata6.00 : hard resetting link [ 131.560841] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 131.567957] ata6.00 : supports DRM functions and may not be fully accessible [ 131.579519] ata6.00 : disabling queued TRIM support [ 131.583209] ata6.00 : supports DRM functions and may not be fully accessible [ 131.594877] ata6.00 : disabling queued TRIM support [ 131.594881] ata6.00 : configured for UDMA/133 [ 131.599979] ata6.01 : supports DRM functions and may not be fully accessible [ 131.610859] ata6.01 : disabling queued TRIM support [ 131.614244] ata6.01 : supports DRM functions and may not be fully accessible [ 131.625124] ata6.01 : disabling queued TRIM support [ 131.625128] ata6.01 : configured for UDMA/133 [ 131.630202] ata6.02 : supports DRM functions and may not be fully accessible [ 131.641035] ata6.02 : disabling queued TRIM support [ 131.646767] ata6.02 : supports DRM functions and may not be fully accessible [ 131.664065] ata6.02 : disabling queued TRIM support [ 131.664069] ata6.02 : configured for UDMA/133 [ 131.672869] ata6.03 : disabling queued TRIM support [ 131.680017] ata6.03 : disabling queued TRIM support [ 131.680021] ata6.03 : configured for UDMA/133 [ 131.684596] ata6 : EH complete [ 131.715913] ata6.00 : failed to read SCR 1 (Emask=0x40) [ 131.721142] ata6.01 : failed to read SCR 1 (Emask=0x40) [ 131.726371] ata6.02 : failed to read SCR 1 (Emask=0x40) [ 131.731596] ata6.02 : NCQ disabled due to excessive errors [ 131.737081] ata6.03 : failed to read SCR 1 (Emask=0x40) [ 131.742310] ata6.04 : failed to read SCR 1 (Emask=0x40) [ 131.747537] ata6.00 : exception Emask 0x100 SAct 0x20000 SErr 0x0 action 0x6 frozen [ 131.755194] ata6.00 : failed command: READ FPDMA QUEUED [ 131.760423] ata6.00 : cmd 60/08:88:80:20:00/00:00:00:00:00/40 tag 17 ncq 409 6 in [ 131.775877] ata6.00 : status: { DRDY } [ 131.779638] ata6.01 : exception Emask 0x100 SAct 0x100000 SErr 0x0 action 0x 6 frozen [ 131.787384] ata6.01 : failed command: READ FPDMA QUEUED [ 131.792614] ata6.01 : cmd 60/20:a0:88:2a:81/00:00:a3:03:00/40 tag 20 ncq 163 84 in [ 131.808156] ata6.01 : status: { DRDY } [ 131.811914] ata6.02 : exception Emask 0x1 SAct 0x204000 SErr 0x0 action 0x6 frozen [ 131.819778] ata6.02 : failed command: READ FPDMA QUEUED [ 131.825018] ata6.02 : cmd 60/08:70:a8:2a:81/00:00:a3:03:00/40 tag 14 ncq 409 6 in [ 131.840208] ata6.02 : status: { DRDY } [ 131.843963] ata6.02 : failed command: READ FPDMA QUEUED [ 131.849188] ata6.02 : cmd 60/80:a8:60:00:00/00:00:00:00:00/40 tag 21 ncq 655 36 in [ 131.864467] ata6.02 : status: { DRDY } [ 131.868225] ata6.03 : exception Emask 0x100 SAct 0x800000 SErr 0x0 action 0x 6 frozen [ 131.875967] ata6.03 : failed command: READ FPDMA QUEUED [ 131.881198] ata6.03 : cmd 60/08:b8:80:20:00/00:00:00:00:00/40 tag 23 ncq 409 6 in [ 131.896654] ata6.03 : status: { DRDY } [ 131.900423] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 131.907733] ata6.15 : hard resetting link [ 132.625943] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 132.633057] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1) [ 132.638898] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1) [ 133.676214] ata6.04 : limiting SATA link speed to 1.5 Gbps [ 133.681723] ata6.01 : hard resetting link [ 134.154550] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 134.161332] ata6.02 : hard resetting link [ 134.634592] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 134.641383] ata6.03 : hard resetting link [ 135.114236] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 135.120858] ata6.04 : hard resetting link [ 135.430775] ata6.04 : SATA link down (SStatus 0 SControl 310) [ 135.436542] ata6 : No present pin info for SATA link down event [ 137.444554] ata6.00 : hard resetting link [ 137.919068] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 137.926356] ata6.00 : supports DRM functions and may not be fully accessible [ 137.937910] ata6.00 : disabling queued TRIM support [ 137.941613] ata6.00 : supports DRM functions and may not be fully accessible [ 137.953276] ata6.00 : disabling queued TRIM support [ 137.953280] ata6.00 : configured for UDMA/133 [ 137.958332] ata6.01 : supports DRM functions and may not be fully accessible [ 137.969200] ata6.01 : disabling queued TRIM support [ 137.972561] ata6.01 : supports DRM functions and may not be fully accessible [ 137.983515] ata6.01 : disabling queued TRIM support [ 137.983519] ata6.01 : configured for UDMA/133 [ 137.988587] ata6.02 : supports DRM functions and may not be fully accessible [ 137.999355] ata6.02 : disabling queued TRIM support [ 138.002606] ata6.02 : supports DRM functions and may not be fully accessible [ 138.013330] ata6.02 : disabling queued TRIM support [ 138.013334] ata6.02 : configured for UDMA/133 [ 138.022167] ata6.03 : disabling queued TRIM support [ 138.034153] ata6.03 : disabling queued TRIM support [ 138.034157] ata6.03 : configured for UDMA/133 [ 138.038729] ata6 : EH complete [ 138.179142] ata6.00 : failed to read SCR 1 (Emask=0x40) [ 138.184374] ata6.01 : failed to read SCR 1 (Emask=0x40) [ 138.189603] ata6.02 : failed to read SCR 1 (Emask=0x40) [ 138.194831] ata6.03 : failed to read SCR 1 (Emask=0x40) [ 138.200056] ata6.03 : NCQ disabled due to excessive errors [ 138.205543] ata6.04 : failed to read SCR 1 (Emask=0x40) [ 138.210774] ata6.00 : exception Emask 0x100 SAct 0x400 SErr 0x0 action 0x6 f rozen [ 138.218252] ata6.00 : failed command: READ FPDMA QUEUED [ 138.223481] ata6.00 : cmd 60/08:50:a8:2a:81/00:00:a3:03:00/40 tag 10 ncq 409 6 in [ 138.238935] ata6.00 : status: { DRDY } [ 138.242703] ata6.01 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 138.250010] ata6.01 : failed command: FLUSH CACHE EXT [ 138.255067] ata6.01 : cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 19 [ 138.269476] ata6.01 : status: { DRDY } [ 138.273231] ata6.02 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 138.280536] ata6.02 : failed command: READ DMA EXT [ 138.285330] ata6.02 : cmd 25/00:08:18:35:7e/00:00:a3:03:00/e0 tag 15 dma 409 6 in [ 138.300779] ata6.02 : status: { DRDY } [ 138.304536] ata6.03 : exception Emask 0x1 SAct 0x60000 SErr 0x0 action 0x6 f rozen [ 138.312015] ata6.03 : failed command: READ FPDMA QUEUED [ 138.317240] ata6.03 : cmd 60/40:88:20:00:00/00:00:00:00:00/40 tag 17 ncq 327 68 in [ 138.332518] ata6.03 : status: { DRDY } [ 138.336272] ata6.03 : failed command: READ FPDMA QUEUED [ 138.341500] ata6.03 : cmd 60/80:90:60:00:00/00:00:00:00:00/40 tag 18 ncq 655 36 in [ 138.356780] ata6.03 : status: { DRDY } [ 138.360538] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 138.367849] ata6.15 : hard resetting link [ 139.086558] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 139.093347] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1) [ 139.099150] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1) [ 140.136370] ata6.04 : limiting SATA link speed to 1.5 Gbps [ 140.141876] ata6.01 : hard resetting link [ 140.616192] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 140.622804] ata6.02 : hard resetting link [ 141.096212] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 141.102830] ata6.03 : hard resetting link [ 141.576284] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 141.582916] ata6.04 : hard resetting link [ 141.892025] ata6.04 : SATA link down (SStatus 0 SControl 310) [ 141.897792] ata6 : No present pin info for SATA link down event [ 143.905718] ata6.00 : hard resetting link [ 144.379761] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 144.386927] ata6.00 : supports DRM functions and may not be fully accessible [ 144.398578] ata6.00 : disabling queued TRIM support [ 144.402298] ata6.00 : supports DRM functions and may not be fully accessible [ 144.413919] ata6.00 : disabling queued TRIM support [ 144.413923] ata6.00 : configured for UDMA/133 [ 144.419008] ata6.01 : supports DRM functions and may not be fully accessible [ 144.429848] ata6.01 : disabling queued TRIM support [ 144.433252] ata6.01 : supports DRM functions and may not be fully accessible [ 144.444298] ata6.01 : disabling queued TRIM support [ 144.444302] ata6.01 : configured for UDMA/133 [ 144.448671] ata6.01 : retrying FLUSH 0xea Emask 0x100 [ 144.454814] ata6.02 : supports DRM functions and may not be fully accessible [ 144.465580] ata6.02 : disabling queued TRIM support [ 144.468833] ata6.02 : supports DRM functions and may not be fully accessible [ 144.479659] ata6.02 : disabling queued TRIM support [ 144.479663] ata6.02 : configured for UDMA/133 [ 144.488398] ata6.03 : disabling queued TRIM support [ 144.495460] ata6.03 : disabling queued TRIM support [ 144.495463] ata6.03 : configured for UDMA/133 [ 144.499988] ata6.01 : device reported invalid CHS sector 0 [ 144.505483] ata6 : EH complete [ 144.539394] ata6.00 : failed to read SCR 1 (Emask=0x40) [ 144.544625] ata6.01 : failed to read SCR 1 (Emask=0x40) [ 144.549853] ata6.02 : failed to read SCR 1 (Emask=0x40) [ 144.555081] ata6.03 : failed to read SCR 1 (Emask=0x40) [ 144.560309] ata6.04 : failed to read SCR 1 (Emask=0x40) [ 144.565541] ata6.00 : exception Emask 0x100 SAct 0x200000 SErr 0x0 action 0x 6 frozen [ 144.573281] ata6.00 : failed command: READ FPDMA QUEUED [ 144.578510] ata6.00 : cmd 60/08:a8:a8:2a:81/00:00:a3:03:00/40 tag 21 ncq 409 6 in [ 144.593961] ata6.00 : status: { DRDY } [ 144.597720] ata6.01 : exception Emask 0x1 SAct 0x18000 SErr 0x0 action 0x6 f rozen [ 144.605201] ata6.01 : failed command: READ FPDMA QUEUED [ 144.610431] ata6.01 : cmd 60/80:78:60:00:00/00:00:00:00:00/40 tag 15 ncq 655 36 in [ 144.625709] ata6.01 : status: { DRDY } [ 144.629459] ata6.01 : failed command: READ FPDMA QUEUED [ 144.634688] ata6.01 : cmd 60/08:80:a8:2a:81/00:00:a3:03:00/40 tag 16 ncq 409 6 in [ 144.649882] ata6.01 : status: { DRDY } [ 144.653638] ata6.02 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 144.660942] ata6.02 : failed command: READ DMA [ 144.665388] ata6.02 : cmd c8/00:08:20:5f:44/00:00:00:00:00/e1 tag 13 dma 409 6 in [ 144.680841] ata6.02 : status: { DRDY } [ 144.684597] ata6.03 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 144.691904] ata6.03 : failed command: READ DMA [ 144.696353] ata6.03 : cmd c8/00:40:20:00:00/00:00:00:00:00/e0 tag 26 dma 327 68 in [ 144.711891] ata6.03 : status: { DRDY } [ 144.715647] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 144.722956] ata6.15 : hard resetting link [ 145.441801] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 145.448988] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1) [ 145.454805] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1) [ 146.492231] ata6.04 : limiting SATA link speed to 1.5 Gbps [ 146.497734] ata6.01 : hard resetting link [ 146.971482] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 146.978096] ata6.02 : hard resetting link [ 147.450675] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 147.457297] ata6.03 : hard resetting link [ 147.931534] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 147.938146] ata6.04 : hard resetting link [ 148.247266] ata6.04 : SATA link down (SStatus 0 SControl 310) [ 148.253029] ata6 : No present pin info for SATA link down event [ 150.260711] ata6.00 : hard resetting link [ 150.734590] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 150.741707] ata6.00 : supports DRM functions and may not be fully accessible [ 150.753270] ata6.00 : disabling queued TRIM support [ 150.756912] ata6.00 : supports DRM functions and may not be fully accessible [ 150.768570] ata6.00 : disabling queued TRIM support [ 150.768576] ata6.00 : configured for UDMA/133 [ 150.773653] ata6.01 : supports DRM functions and may not be fully accessible [ 150.784525] ata6.01 : disabling queued TRIM support [ 150.787968] ata6.01 : supports DRM functions and may not be fully accessible [ 150.798811] ata6.01 : disabling queued TRIM support [ 150.798815] ata6.01 : configured for UDMA/133 [ 150.803866] ata6.02 : supports DRM functions and may not be fully accessible [ 150.814633] ata6.02 : disabling queued TRIM support [ 150.817900] ata6.02 : supports DRM functions and may not be fully accessible [ 150.828636] ata6.02 : disabling queued TRIM support [ 150.828640] ata6.02 : configured for UDMA/133 [ 150.843995] ata6.03 : disabling queued TRIM support [ 150.851016] ata6.03 : disabling queued TRIM support [ 150.851019] ata6.03 : configured for UDMA/133 [ 150.855602] ata6 : EH complete [ 151.197641] ata6.00 : failed to read SCR 1 (Emask=0x40) [ 151.202883] ata6.01 : failed to read SCR 1 (Emask=0x40) [ 151.208111] ata6.01 : NCQ disabled due to excessive errors [ 151.213594] ata6.02 : failed to read SCR 1 (Emask=0x40) [ 151.218820] ata6.03 : failed to read SCR 1 (Emask=0x40) [ 151.224048] ata6.04 : failed to read SCR 1 (Emask=0x40) [ 151.229277] ata6.00 : exception Emask 0x100 SAct 0x1 SErr 0x0 action 0x6 fro zen [ 151.236587] ata6.00 : failed command: READ FPDMA QUEUED [ 151.241816] ata6.00 : cmd 60/08:00:e8:5e:44/00:00:01:00:00/40 tag 0 ncq 4096 in [ 151.257184] ata6.00 : status: { DRDY } [ 151.260949] ata6.01 : exception Emask 0x1 SAct 0x40000008 SErr 0x0 action 0x 6 frozen [ 151.268691] ata6.01 : failed command: READ FPDMA QUEUED [ 151.273921] ata6.01 : cmd 60/08:18:e8:5e:44/00:00:01:00:00/40 tag 3 ncq 4096 in [ 151.289036] ata6.01 : status: { DRDY } [ 151.292790] ata6.01 : failed command: READ FPDMA QUEUED [ 151.298021] ata6.01 : cmd 60/20:f0:60:68:44/00:00:01:00:00/40 tag 30 ncq 163 84 in [ 151.313303] ata6.01 : status: { DRDY } [ 151.317062] ata6.02 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 151.324372] ata6.02 : failed command: READ DMA [ 151.328823] ata6.02 : cmd c8/00:08:e8:5e:44/00:00:00:00:00/e1 tag 2 dma 4096 in [ 151.344195] ata6.02 : status: { DRDY } [ 151.347952] ata6.03 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 151.355258] ata6.03 : failed command: READ DMA [ 151.359707] ata6.03 : cmd c8/00:08:e8:5e:44/00:00:00:00:00/e1 tag 1 dma 4096 in [ 151.375383] ata6.03 : status: { DRDY } [ 151.379146] ata6.04 : exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 fro zen [ 151.386462] ata6.15 : hard resetting link [ 152.105072] ata6.15 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 152.112029] ata6.15 : failed to read PMP GSCR[30] (Emask=0x1) [ 152.117853] ata6.15 : failed to read PMP GSCR[31] (Emask=0x1) [ 153.155064] ata6.04 : limiting SATA link speed to 1.5 Gbps [ 153.160567] ata6.01 : hard resetting link [ 153.634710] ata6.01 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 153.641318] ata6.02 : hard resetting link [ 154.114936] ata6.02 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 154.121557] ata6.03 : hard resetting link [ 154.594757] ata6.03 : SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 154.601367] ata6.04 : hard resetting link [ 154.910537] ata6.04 : SATA link down (SStatus 0 SControl 310) [ 154.916303] ata6 : No present pin info for SATA link down event [ 156.923983] ata6.00 : hard resetting link [ 157.396817] ata6.00 : SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 157.404298] ata6.00 : supports DRM functions and may not be fully accessible [ 157.415883] ata6.00 : disabling queued TRIM support [ 157.419563] ata6.00 : supports DRM functions and may not be fully accessible [ 157.431176] ata6.00 : disabling queued TRIM support [ 157.431181] ata6.00 : configured for UDMA/133 [ 157.436223] ata6.01 : supports DRM functions and may not be fully accessible [ 157.447064] ata6.01 : disabling queued TRIM support [ 157.450490] ata6.01 : supports DRM functions and may not be fully accessible [ 157.461336] ata6.01 : disabling queued TRIM support [ 157.461340] ata6.01 : configured for UDMA/133 [ 157.473017] ata6.02 : supports DRM functions and may not be fully accessible [ 157.483763] ata6.02 : disabling queued TRIM support [ 157.487054] ata6.02 : supports DRM functions and may not be fully accessible [ 157.497816] ata6.02 : disabling queued TRIM support [ 157.497820] ata6.02 : configured for UDMA/133 [ 157.518360] ata6.03 : disabling queued TRIM support [ 157.538642] ata6.03 : disabling queued TRIM support [ 157.538645] ata6.03 : configured for UDMA/133 [ 157.543220] ata6 : EH complete [ 166.183550] ata2.00 (slot 1): disabling queued TRIM support [ 166.186329] ata2.00 (slot 1): disabling queued TRIM support [ 166.186336] ata2.00 (slot 1): configured for UDMA/133 [ 166.191407] ata2 (slot 1): EH complete [ 166.431842] ata3.00 (slot 2): disabling queued TRIM support [ 166.434588] ata3.00 (slot 2): disabling queued TRIM support [ 166.434597] ata3.00 (slot 2): configured for UDMA/133 [ 166.439667] ata3 (slot 2): EH complete [ 166.655168] ata4.00 (slot 3): disabling queued TRIM support [ 166.657962] ata4.00 (slot 3): disabling queued TRIM support [ 166.657968] ata4.00 (slot 3): configured for UDMA/133 [ 166.663033] ata4 (slot 3): EH complete [ 166.864721] ata5.00 (slot 4): disabling queued TRIM support [ 166.867506] ata5.00 (slot 4): disabling queued TRIM support [ 166.867512] ata5.00 (slot 4): configured for UDMA/133 [ 166.872579] ata5 (slot 4): EH complete [ 167.053822] ata10.00 (slot 8): disabling queued TRIM support [ 167.067682] ata10.00 (slot 8): disabling queued TRIM support [ 167.067692] ata10.00 (slot 8): configured for UDMA/133 [ 167.072845] ata10 (slot 8): EH complete [ 167.160612] ata6.00 : supports DRM functions and may not be fully accessible [ 167.172179] ata6.00 : disabling queued TRIM support [ 167.175874] ata6.00 : supports DRM functions and may not be fully accessible [ 167.187479] ata6.00 : disabling queued TRIM support [ 167.187484] ata6.00 : configured for UDMA/133 [ 167.191901] ata6 : EH complete [ 167.276847] ata6.01 : supports DRM functions and may not be fully accessible [ 167.287569] ata6.01 : disabling queued TRIM support [ 167.290916] ata6.01 : supports DRM functions and may not be fully accessible [ 167.304940] ata6.01 : disabling queued TRIM support [ 167.304948] ata6.01 : configured for UDMA/133 [ 167.309374] ata6 : EH complete [ 167.394039] ata6.02 : supports DRM functions and may not be fully accessible [ 167.404740] ata6.02 : disabling queued TRIM support [ 167.415031] ata6.02 : supports DRM functions and may not be fully accessible [ 167.430917] ata6.02 : disabling queued TRIM support [ 167.430925] ata6.02 : configured for UDMA/133 [ 167.435360] ata6 : EH complete [ 167.531718] ata6.03 : disabling queued TRIM support [ 167.544473] ata6.03 : disabling queued TRIM support [ 167.544483] ata6.03 : configured for UDMA/133 [ 167.548919] ata6 : EH complete [ 167.628250] ata7.00 (slot 5): disabling queued TRIM support [ 167.631037] ata7.00 (slot 5): disabling queued TRIM support [ 167.631043] ata7.00 (slot 5): configured for UDMA/133 [ 167.636109] ata7 (slot 5): EH complete [ 167.782435] ata8.00 (slot 6): disabling queued TRIM support [ 167.785192] ata8.00 (slot 6): disabling queued TRIM support [ 167.785198] ata8.00 (slot 6): configured for UDMA/133 [ 167.790262] ata8 (slot 6): EH complete [ 167.900525] ata9.00 (slot 7): disabling queued TRIM support [ 167.903297] ata9.00 (slot 7): disabling queued TRIM support [ 167.903303] ata9.00 (slot 7): configured for UDMA/133 [ 167.908371] ata9 (slot 7): EH complete

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 18, 2025):

and here is the email from the scripts. I assume the times will correlate between scripts and dmesg?
`Task Scheduler has completed a triggered task.

Task: 2 HDD_db
Start time: Thu, 18 Sep 2025 16:47:49 GMT
Stop time: Thu, 18 Sep 2025 16:47:56 GMT
Current status: 0 (Normal)
Standard output/error:
Synology_HDD_db v3.6.111
DS1821+ x86_64 DSM 7.2.2-72806-4
StorageManager 1.0.0-00502

ds1821+_host_v7 version 8062

Using options: -nrpI --autoupdate=1 --ram --ihm -S
Running from: /volume1/scripts/hdd-db/syno_hdd_db.sh

HDD/SSD models found: 4
ST8000VN0022-2EL112,SC61,8001 GB
WD80EDAZ-11TA3A0,81.00A81,8001 GB
WD80EDBZ-11B0ZA0,85.00A85,8001 GB
WD80EFBX-68AZZN0,85.00A85,8001 GB

M.2 drive models found: 2
WD_BLACK SN850X 1000GB,620241WD,1000 GB
WD_BLACK SN850X 1000GB,620281WD,1000 GB

No M.2 PCIe cards found

Expansion Unit models found: 1
DX513

[0;33mST8000VN0022-2EL112 [0m already exists in [0;36mds1821+_host_v7.db [0m
[0;33mST8000VN0022-2EL112 [0m already exists in [0;36mdx513_v7.db [0m
[0;33mWD80EDAZ-11TA3A0 [0m already exists in [0;36mds1821+_host_v7.db [0m
[0;33mWD80EDAZ-11TA3A0 [0m already exists in [0;36mdx513_v7.db [0m
[0;33mWD80EDBZ-11B0ZA0 [0m already exists in [0;36mds1821+_host_v7.db [0m
[0;33mWD80EDBZ-11B0ZA0 [0m already exists in [0;36mdx513_v7.db [0m
[0;33mWD80EFBX-68AZZN0 [0m already exists in [0;36mds1821+_host_v7.db [0m
[0;33mWD80EFBX-68AZZN0 [0m already exists in [0;36mdx513_v7.db [0m
Updated [0;33mWD_BLACK SN850X 1000GB [0m in [0;36mds1821+_host_v7.db [0m
Updated [0;33mWD_BLACK SN850X 1000GB [0m in [0;36mds1821+_host_v7.db [0m

Support disk compatibility already enabled.

Support memory compatibility already disabled.

Max memory already set to 64 GB.

NVMe support already enabled.

M.2 volume support already enabled.

Drive db auto updates already disabled.

Creating pool in UI on drives in M.2 adaptor card already enabled.

Support IronWolf Health Management already enabled.
IronWolf Health Management already updated.

DSM successfully checked disk compatibility.

You may need to [0;36mreboot the Synology [0m to see the changes.`

`Task Scheduler has completed a triggered task.

Task: 1 External Unit Enable
Start time: Thu, 18 Sep 2025 16:47:45 GMT
Stop time: Thu, 18 Sep 2025 16:47:47 GMT
Current status: 0 (Normal)
Standard output/error:
Synology_enable_eunit v3.0.22
DS1821+ DSM 7.2.2-72806-4

StorageManager 1.0.0-00502

Using options: --unit=dx513
Running from: /volume1/scripts/esata/syno_enable_eunit.sh

Connected Expansion Units:
[0;36mDX513 [0m

[0;36mDX517 [0m is enabled in [0;33m/etc/model.dtb [0m
[0;36mDX517 [0m is enabled in [0;33m/etc.defaults/model.dtb [0m
[0;36mDX513 [0m is enabled in [0;33m/etc/model.dtb [0m
[0;36mDX513 [0m is enabled in [0;33m/etc.defaults/model.dtb [0m

DX513 selected

[0;36mDX513 [0m already enabled in [0;33mmodel.dtb [0m
Disable device /dev/sata5 NCQ successfully
Disable device /dev/sata6 NCQ successfully
Disable device /dev/sata7 NCQ successfully
Disable device /dev/sata8 NCQ successfully`

@mervincm commented on GitHub (Sep 18, 2025): and here is the email from the scripts. I assume the times will correlate between scripts and dmesg? `Task Scheduler has completed a triggered task. Task: 2 HDD_db Start time: Thu, 18 Sep 2025 16:47:49 GMT Stop time: Thu, 18 Sep 2025 16:47:56 GMT Current status: 0 (Normal) Standard output/error: Synology_HDD_db v3.6.111 DS1821+ x86_64 DSM 7.2.2-72806-4 StorageManager 1.0.0-00502 ds1821+_host_v7 version 8062 Using options: -nrpI --autoupdate=1 --ram --ihm -S Running from: /volume1/scripts/hdd-db/syno_hdd_db.sh HDD/SSD models found: 4 ST8000VN0022-2EL112,SC61,8001 GB WD80EDAZ-11TA3A0,81.00A81,8001 GB WD80EDBZ-11B0ZA0,85.00A85,8001 GB WD80EFBX-68AZZN0,85.00A85,8001 GB M.2 drive models found: 2 WD_BLACK SN850X 1000GB,620241WD,1000 GB WD_BLACK SN850X 1000GB,620281WD,1000 GB No M.2 PCIe cards found Expansion Unit models found: 1 DX513 [0;33mST8000VN0022-2EL112 [0m already exists in [0;36mds1821+_host_v7.db [0m [0;33mST8000VN0022-2EL112 [0m already exists in [0;36mdx513_v7.db [0m [0;33mWD80EDAZ-11TA3A0 [0m already exists in [0;36mds1821+_host_v7.db [0m [0;33mWD80EDAZ-11TA3A0 [0m already exists in [0;36mdx513_v7.db [0m [0;33mWD80EDBZ-11B0ZA0 [0m already exists in [0;36mds1821+_host_v7.db [0m [0;33mWD80EDBZ-11B0ZA0 [0m already exists in [0;36mdx513_v7.db [0m [0;33mWD80EFBX-68AZZN0 [0m already exists in [0;36mds1821+_host_v7.db [0m [0;33mWD80EFBX-68AZZN0 [0m already exists in [0;36mdx513_v7.db [0m Updated [0;33mWD_BLACK SN850X 1000GB [0m in [0;36mds1821+_host_v7.db [0m Updated [0;33mWD_BLACK SN850X 1000GB [0m in [0;36mds1821+_host_v7.db [0m Support disk compatibility already enabled. Support memory compatibility already disabled. Max memory already set to 64 GB. NVMe support already enabled. M.2 volume support already enabled. Drive db auto updates already disabled. Creating pool in UI on drives in M.2 adaptor card already enabled. Support IronWolf Health Management already enabled. IronWolf Health Management already updated. DSM successfully checked disk compatibility. You may need to [0;36mreboot the Synology [0m to see the changes.` `Task Scheduler has completed a triggered task. Task: 1 External Unit Enable Start time: Thu, 18 Sep 2025 16:47:45 GMT Stop time: Thu, 18 Sep 2025 16:47:47 GMT Current status: 0 (Normal) Standard output/error: Synology_enable_eunit v3.0.22 DS1821+ DSM 7.2.2-72806-4 StorageManager 1.0.0-00502 Using options: --unit=dx513 Running from: /volume1/scripts/esata/syno_enable_eunit.sh Connected Expansion Units: [0;36mDX513 [0m [0;36mDX517 [0m is enabled in [0;33m/etc/model.dtb [0m [0;36mDX517 [0m is enabled in [0;33m/etc.defaults/model.dtb [0m [0;36mDX513 [0m is enabled in [0;33m/etc/model.dtb [0m [0;36mDX513 [0m is enabled in [0;33m/etc.defaults/model.dtb [0m DX513 selected [0;36mDX513 [0m already enabled in [0;33mmodel.dtb [0m Disable device /dev/sata5 NCQ successfully Disable device /dev/sata6 NCQ successfully Disable device /dev/sata7 NCQ successfully Disable device /dev/sata8 NCQ successfully`

kerem commented

Author

Owner

@007revad commented on GitHub (Sep 19, 2025):

@steinreiter See https://github.com/007revad/Synology_enable_eunit/releases/tag/v3.1.23

@mervincm If you use the -e or --email option it will prevent those [0;36m and [0m color codes making the emails harder to read.

-e, --email           Disable colored text in output scheduler emails

@007revad commented on GitHub (Sep 19, 2025): @steinreiter See https://github.com/007revad/Synology_enable_eunit/releases/tag/v3.1.23 @mervincm If you use the -e or --email option it will prevent those [0;36m and [0m color codes making the emails harder to read. ``` -e, --email Disable colored text in output scheduler emails ```

kerem commented

https://www.datasheets360.com/pdf/-1452046245919400795

Author

Owner

@steinreiter commented on GitHub (Sep 19, 2025):

@steinreiter See https://github.com/007revad/Synology_enable_eunit/releases/tag/v3.1.23

@mervincm If you use the -e or --email option it will prevent those [0;36m and [0m color codes making the emails harder to read.
-e, --email           Disable colored text in output scheduler emails

Thx, ich will test it as soon as possible...

I'm just surprised... my DX513 has PCB revision 1.6 and it has the older SIL3726 on it and not the usual and newer SIL3826... WTF...

Here you can see the PCB of a DX510 in revision 1.3 that contains also a SIL3726 and the PCB looks the same as my DX513 PCB.
https://www.smallnetbuilder.com/nas/nas-reviews/synology-dx510-disk-station-expansion-unit-reviewed/

Here you can see the PCB of a DX513 in revision 1.1 and 1.3 that has a sligly newer PCB with a SIL3826...
https://www.mobile01.com/topicdetail.php?f=494&t=4891172&p=3#61322302
https://www.techpowerup.com/review/synology-ds1515plus/7.html

What's strange is that my DX513, with the newer PCB in revision 1.6 isn't based on the new PCB Layout, but rather on the old one. This is clearly visible see the PN 08-04DX51016 on the PCB of my DX513... it seems the DX513 PCB 1.6 based on the DX510 PCB 1.3 (PN 08-04DX51013), just with the newer FAN-interchange-connector to the SATA-PCB and without push-buttons soldered...

!!!Did Synology switch the DX513 from the SIL3826 back to the SIL3726 based on DX510 PCB design... because the SIL3826 might have caused more problems back then???

@mervincm , can you please check what chip your DX513 has... Maybe the SIL3826 is more bitchy than the SIL3726 in terms of stability... and maybe this also explains the different speeds of the LED flashing when booting between yours and mine?!

@mervincm , I don't think you even need to disassemble your DX513. Based on your video we know you have not a very old one with on a DX510 housing and also not a middle aged one with the newer housing and glossy front... the links show that the DX513 with newer housing and matte front that has the SIL3826 based PCB has also a black switch (firmly to switch between manuel power on via button or auto power on with a Diskstation such as by the DX213). This switch is routed out through a hole on the back of the DX513 case next to the fans. But my DX513, based on the SIL3726 PCB, doesn't have a switch, and therefore my DX513 doesn't have a hole for a switch on the back either.

Difference researching... the SIL3826 has no EEPROM configuration support anymore but a another package size with 208 pins instead of the SIL3726 that has a package size with 364 Pins as HSBGA...

https://www.datasheets360.com/pdf/254691204680928743

@steinreiter commented on GitHub (Sep 19, 2025): > [@steinreiter](https://github.com/steinreiter) See https://github.com/007revad/Synology_enable_eunit/releases/tag/v3.1.23 > > [@mervincm](https://github.com/mervincm) If you use the -e or --email option it will prevent those [0;36m and [0m color codes making the emails harder to read. > > ``` > -e, --email Disable colored text in output scheduler emails > ``` Thx, ich will test it as soon as possible... I'm just surprised... my DX513 has PCB revision 1.6 and it has the older SIL3726 on it and not the usual and newer SIL3826... WTF... ![Image](https://github.com/user-attachments/assets/2719a0b9-c8ea-4180-a2cc-711370b041b0) Here you can see the PCB of a DX510 in revision 1.3 that contains also a SIL3726 and the PCB looks the same as my DX513 PCB. https://www.smallnetbuilder.com/nas/nas-reviews/synology-dx510-disk-station-expansion-unit-reviewed/ ![Image](https://github.com/user-attachments/assets/888cda48-4bae-4729-a300-51149db56294) Here you can see the PCB of a DX513 in revision 1.1 and 1.3 that has a sligly newer PCB with a SIL3826... https://www.mobile01.com/topicdetail.php?f=494&t=4891172&p=3#61322302 https://www.techpowerup.com/review/synology-ds1515plus/7.html ![Image](https://github.com/user-attachments/assets/4f5ee253-c8db-40c6-b1db-49849d246781) What's strange is that my DX513, with the newer PCB in revision 1.6 isn't based on the new PCB Layout, but rather on the old one. This is clearly visible see the PN 08-04DX51016 on the PCB of my DX513... it seems the DX513 PCB 1.6 based on the DX510 PCB 1.3 (PN 08-04DX51013), just with the newer FAN-interchange-connector to the SATA-PCB and without push-buttons soldered... !!!Did Synology switch the DX513 from the SIL3826 back to the SIL3726 based on DX510 PCB design... because the SIL3826 might have caused more problems back then??? @mervincm , can you please check what chip your DX513 has... Maybe the SIL3826 is more bitchy than the SIL3726 in terms of stability... and maybe this also explains the different speeds of the LED flashing when booting between yours and mine?! @mervincm , I don't think you even need to disassemble your DX513. Based on your video we know you have not a very old one with on a DX510 housing and also not a middle aged one with the newer housing and glossy front... the links show that the DX513 with newer housing and matte front that has the SIL3826 based PCB has also a black switch (firmly to switch between manuel power on via button or auto power on with a Diskstation such as by the DX213). This switch is routed out through a hole on the back of the DX513 case next to the fans. But my DX513, based on the SIL3726 PCB, doesn't have a switch, and therefore my DX513 doesn't have a hole for a switch on the back either. Difference researching... the SIL3826 has no EEPROM configuration support anymore but a another package size with 208 pins instead of the SIL3726 that has a package size with 364 Pins as HSBGA... https://www.datasheets360.com/pdf/-1452046245919400795 <img width="1102" height="621" alt="Image" src="https://github.com/user-attachments/assets/4a6e934d-c45a-4ea0-85fc-df112d2acbb0" /> https://www.datasheets360.com/pdf/254691204680928743 <img width="1108" height="625" alt="Image" src="https://github.com/user-attachments/assets/dca8468b-6188-429f-8ab5-2a1ac450ef74" />

kerem commented

Author

Owner

@steinreiter commented on GitHub (Sep 19, 2025):

@steinreiter See https://github.com/007revad/Synology_enable_eunit/releases/tag/v3.1.23

@mervincm If you use the -e or --email option it will prevent those [0;36m and [0m color codes making the emails harder to read.
-e, --email           Disable colored text in output scheduler emails

@007revad , I would like to thank you again for implementing this great script. Now I have tested your new script version via the task scheduler with a DX213 and a DX513, each with one hard drive connected. Works as expected, NCQ was disabled for the drive inside the DX213 and DX513. Only in the info message "Connected Expansion Units" there was only listed the DX213 and the DX513 was missing. Also a newline was missing before "DX513 selected", see below.

Synology_enable_eunit v3.1.23
DS1621+ DSM 7.2.2-72806-4

StorageManager 1.0.0-00502

Using options: --email --unit=dx213,dx513
Running from: /volume1/scripts/syno_enable_eunit/syno_enable_eunit.sh

Connected Expansion Units:
DX213

DX517 is enabled in /etc/model.dtb
DX517 is enabled in /etc.defaults/model.dtb
DX513 is enabled in /etc/model.dtb
DX513 is enabled in /etc.defaults/model.dtb
DX213 is enabled in /etc/model.dtb
DX213 is enabled in /etc.defaults/model.dtb

DX213 selected

DX213 already enabled in model.dtb
Disable device /dev/sata1 NCQ successfully
DX513 selected

DX513 already enabled in model.dtb
Disable device /dev/sata4 NCQ successfully

Finished

@steinreiter commented on GitHub (Sep 19, 2025): > [@steinreiter](https://github.com/steinreiter) See https://github.com/007revad/Synology_enable_eunit/releases/tag/v3.1.23 > > [@mervincm](https://github.com/mervincm) If you use the -e or --email option it will prevent those [0;36m and [0m color codes making the emails harder to read. > > ``` > -e, --email Disable colored text in output scheduler emails > ``` @007revad , I would like to thank you again for implementing this great script. Now I have tested your new script version via the task scheduler with a DX213 and a DX513, each with one hard drive connected. Works as expected, NCQ was disabled for the drive inside the DX213 and DX513. Only in the info message "Connected Expansion Units" there was only listed the DX213 and the DX513 was missing. Also a newline was missing before "DX513 selected", see below. ``` Synology_enable_eunit v3.1.23 DS1621+ DSM 7.2.2-72806-4 StorageManager 1.0.0-00502 Using options: --email --unit=dx213,dx513 Running from: /volume1/scripts/syno_enable_eunit/syno_enable_eunit.sh Connected Expansion Units: DX213 DX517 is enabled in /etc/model.dtb DX517 is enabled in /etc.defaults/model.dtb DX513 is enabled in /etc/model.dtb DX513 is enabled in /etc.defaults/model.dtb DX213 is enabled in /etc/model.dtb DX213 is enabled in /etc.defaults/model.dtb DX213 selected DX213 already enabled in model.dtb Disable device /dev/sata1 NCQ successfully DX513 selected DX513 already enabled in model.dtb Disable device /dev/sata4 NCQ successfully Finished ```

kerem commented

Author

Owner

@007revad commented on GitHub (Sep 19, 2025):

@steinreiter Does this command return both connected expansion units?

sudo syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}'

@007revad commented on GitHub (Sep 19, 2025): @steinreiter Does this command return both connected expansion units? ``` sudo syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}' ```

kerem commented

Author

Owner

@steinreiter commented on GitHub (Sep 19, 2025):

sudo syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}'

Of course :)

root@DS1621plus:~# sudo syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}'
DX213
DX513

@steinreiter commented on GitHub (Sep 19, 2025): > `sudo syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}'` Of course :) ``` root@DS1621plus:~# sudo syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}' DX213 DX513 ```

kerem commented

Author

Owner

@007revad commented on GitHub (Sep 19, 2025):

Does this print both eunits?

sudo read -r -a found_eunits <<< "$(syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}')"
for e in "${found_eunits[@]}"; do  echo -e "$e";  done

@007revad commented on GitHub (Sep 19, 2025): Does this print both eunits? ``` sudo read -r -a found_eunits <<< "$(syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}')" for e in "${found_eunits[@]}"; do echo -e "$e"; done ```

kerem commented

Author

Owner

@steinreiter commented on GitHub (Sep 19, 2025):

I've had reports from some people that their DX would not work and it turned out the eSATA cable was not making a reliable connection. Blowing the dust out of the eSATA ports and unplugging then reconnecting the eSATA cable (at both ends) got it working. Last night I was wondering if this may be the cause of the "works for while" issue.

@007revad, I can only confirm this. I've been playing around with the new DX513, and since I hadn't yet found a permanent location in the closet, I had to keep plugging it back into my DS1621+ for all the tests, etc.

Just a moment ago, only this time I was too lazy and just quickly tightened one of the two screws on the connector on the DX513... Everything was fine... put in only a single disk... and after creating a pool and volume... reboot... and an abnormal disk error... I ran through everything again three times, created a pool and volume... and the disk kept showing an abnormal error after rebooting...

Well... until I finally figured it out... screw in the second screw on the connector and tighten it... Well... and what can I say... the error is now gone... 5 reboots later... the pool and volume on the disk are fine...

@mervincm please ensure that all SATA connections on the internal drives and also of the DX513 are clean and making good contact. Next, check the eSATA connections from your DX and DS und bothe cable end for cleanliness and tighten the screws thoroughly, ensuring that the screws, which you screw in with your fingers, are fully seated until the end and flush with no gaps to the end piece.

@steinreiter commented on GitHub (Sep 19, 2025): > I've had reports from some people that their DX would not work and it turned out the eSATA cable was not making a reliable connection. Blowing the dust out of the eSATA ports and unplugging then reconnecting the eSATA cable (at both ends) got it working. Last night I was wondering if this may be the cause of the "works for while" issue. @007revad, I can only confirm this. I've been playing around with the new DX513, and since I hadn't yet found a permanent location in the closet, I had to keep plugging it back into my DS1621+ for all the tests, etc. Just a moment ago, only this time I was too lazy and just quickly tightened one of the two screws on the connector on the DX513... Everything was fine... put in only a single disk... and after creating a pool and volume... reboot... and an abnormal disk error... I ran through everything again three times, created a pool and volume... and the disk kept showing an abnormal error after rebooting... Well... until I finally figured it out... screw in the second screw on the connector and tighten it... Well... and what can I say... the error is now gone... 5 reboots later... the pool and volume on the disk are fine... @mervincm please ensure that all SATA connections on the internal drives and also of the DX513 are clean and making good contact. Next, check the eSATA connections from your DX and DS und bothe cable end for cleanliness and tighten the screws thoroughly, ensuring that the screws, which you screw in with your fingers, are fully seated until the end and flush with no gaps to the end piece.

kerem commented

Author

Owner

@steinreiter commented on GitHub (Sep 19, 2025):

sudo read -r -a found_eunits <<< "$(syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}')"
for e in "${found_eunits[@]}"; do echo -e "$e"; done

Unfortunately no :(

root@DS1621plus:~# sudo read -r -a found_eunits <<< "$(syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}')"
sudo: read: command not found
root@DS1621plus:~# for e in "${found_eunits[@]}"; do  echo -e "$e";  done

The reason is that sudo isn't a shell and can't interpret shell syntax. Simply start a bash and it should work:

sudo bash -c "<your-shell-commands>"

This one is simpler and does as both sudoer or root:

steinreiter@DS1621plus:~$ found_eunits="$(sudo syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}')"
steinreiter@DS1621plus:~$ for e in "${found_eunits[@]}"; do  echo -e "$e";  done
DX213
DX513

root@DS1621plus:~# found_eunits="$(sudo syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}')"
root@DS1621plus:~# for e in "${found_eunits[@]}"; do  echo -e "$e";  done
DX213
DX513

@steinreiter commented on GitHub (Sep 19, 2025): > sudo read -r -a found_eunits <<< "$(syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}')" > for e in "${found_eunits[@]}"; do echo -e "$e"; done Unfortunately no :( ``` root@DS1621plus:~# sudo read -r -a found_eunits <<< "$(syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}')" sudo: read: command not found root@DS1621plus:~# for e in "${found_eunits[@]}"; do echo -e "$e"; done ``` The reason is that sudo isn't a shell and can't interpret shell syntax. Simply start a bash and it should work: ``` sudo bash -c "<your-shell-commands>" ``` This one is simpler and does as both sudoer or root: ``` steinreiter@DS1621plus:~$ found_eunits="$(sudo syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}')" steinreiter@DS1621plus:~$ for e in "${found_eunits[@]}"; do echo -e "$e"; done DX213 DX513 root@DS1621plus:~# found_eunits="$(sudo syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}')" root@DS1621plus:~# for e in "${found_eunits[@]}"; do echo -e "$e"; done DX213 DX513 ```

kerem commented

Author

Owner

@007revad commented on GitHub (Sep 19, 2025):

For some reason, since v2, the script had:

    #found_eunits=($(syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}'))
    read -r -a found_eunits <<< "$(syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}')"

I have no idea why I commented out the first line and added the second line.

@007revad commented on GitHub (Sep 19, 2025): For some reason, since v2, the script had: ``` #found_eunits=($(syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}')) read -r -a found_eunits <<< "$(syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}')" ``` I have no idea why I commented out the first line and added the second line.

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 19, 2025):

@mervincm please ensure that all SATA connections on the internal drives and also of the DX513 are clean and making good contact. Next, check the eSATA connections from your DX and DS and both cable end for cleanliness and tighten the screws thoroughly, ensuring that the screws, which you screw in with your fingers, are fully seated until the end and flush with no gaps to the end piece.

to check my board part number, I just dis-assembled and recleaned it. all internal connections removed contact cleaned and re-plugged. all external cleaner with air and contact cleaner, cable both ends and NAS eSATA port. all tight and no loose connections. No change in that I still get the light dance and the occasional high response time error.

@mervincm commented on GitHub (Sep 19, 2025): > [@mervincm](https://github.com/mervincm) please ensure that all SATA connections on the internal drives and also of the DX513 are clean and making good contact. Next, check the eSATA connections from your DX and DS and both cable end for cleanliness and tighten the screws thoroughly, ensuring that the screws, which you screw in with your fingers, are fully seated until the end and flush with no gaps to the end piece. to check my board part number, I just dis-assembled and recleaned it. all internal connections removed contact cleaned and re-plugged. all external cleaner with air and contact cleaner, cable both ends and NAS eSATA port. all tight and no loose connections. No change in that I still get the light dance and the occasional high response time error.

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 19, 2025):

@mervincm , can you please check what chip your DX513 has... Maybe the SIL3826 is more bitchy than the SIL3726 in terms of stability... and maybe this also explains the different speeds of the LED flashing when booting between yours and mine?!

My PBC looks like your last example. model:dx513 P/N:08-04DX51313 VER:1.3
a BIOS? chip with sticker DX513 V2.0
I have a physical switch that has manual / default options and mine is set to default
my main chip is Sil3826CLUC

@mervincm commented on GitHub (Sep 19, 2025): > [@mervincm](https://github.com/mervincm) , can you please check what chip your DX513 has... Maybe the SIL3826 is more bitchy than the SIL3726 in terms of stability... and maybe this also explains the different speeds of the LED flashing when booting between yours and mine?! My PBC looks like your last example. model:dx513 P/N:08-04DX51313 VER:1.3 a BIOS? chip with sticker DX513 V2.0 I have a physical switch that has manual / default options and mine is set to default my main chip is Sil3826CLUC

kerem commented

Author

Owner

@steinreiter commented on GitHub (Sep 19, 2025):

Thanks for your feedback. Then my suspicion might be correct, and the sil3826 might actually be crappier than ever, which is why Synology switched back to the sil3726 in the last batches of DX513.

We'll never know unless you have the opportunity and can get a DX513 with a sil3726 in the old DX510 housing, or find a more modern DX513 without switch hole in the backsite with a sil3726 to test.

Unfortunately I don't need another DX513, otherwise I would look for a model similar to yours and could test it myself, sorry. :(

In the next few days, I'll take apart the two DX213s here, which also don't cause any problems, and check whether they have a sil3726 or sil3826 installed. According to the internet, they're supposed to have a sil3826 installed. Maybe it's even true this time, because they also have a switch on the back, like your DX513.

We'll see...

@steinreiter commented on GitHub (Sep 19, 2025): Thanks for your feedback. Then my suspicion might be correct, and the sil3826 might actually be crappier than ever, which is why Synology switched back to the sil3726 in the last batches of DX513. We'll never know unless you have the opportunity and can get a DX513 with a sil3726 in the old DX510 housing, or find a more modern DX513 without switch hole in the backsite with a sil3726 to test. Unfortunately I don't need another DX513, otherwise I would look for a model similar to yours and could test it myself, sorry. :( In the next few days, I'll take apart the two DX213s here, which also don't cause any problems, and check whether they have a sil3726 or sil3826 installed. According to the internet, they're supposed to have a sil3826 installed. Maybe it's even true this time, because they also have a switch on the back, like your DX513. We'll see...

kerem commented

Author

Owner

@007revad commented on GitHub (Sep 20, 2025):

For some reason, since v2, the script had:
    #found_eunits=($(syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}'))
    read -r -a found_eunits <<< "$(syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}')"
I have no idea why I commented out the first line and added the second line.

I just remembered why. It was to stop shellcheck complaining:

found_eunits=($(syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}'))
             ^-- SC2207 (warning): Prefer mapfile or read -a to split command output (or quote to avoid splitting).

@007revad commented on GitHub (Sep 20, 2025): > For some reason, since v2, the script had: > > ``` > #found_eunits=($(syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}')) > read -r -a found_eunits <<< "$(syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}')" > ``` > > I have no idea why I commented out the first line and added the second line. I just remembered why. It was to stop shellcheck complaining: ``` found_eunits=($(syno_slot_mapping | grep 'Eunit port' | awk '{print $NF}')) ^-- SC2207 (warning): Prefer mapfile or read -a to split command output (or quote to avoid splitting). ```

kerem commented

Author

Owner

@007revad commented on GitHub (Sep 20, 2025):

New version: https://github.com/007revad/Synology_enable_eunit/releases/tag/v3.1.24

Fixed only listing the 1st expansion unit found when 2 different expansion unit models are connected.
Changed to show port number of connected expansion units.
Fixed missing blank line before 2nd expansion unit "selected" line.

@007revad commented on GitHub (Sep 20, 2025): New version: https://github.com/007revad/Synology_enable_eunit/releases/tag/v3.1.24 - Fixed only listing the 1st expansion unit found when 2 different expansion unit models are connected. - Changed to show port number of connected expansion units. - Fixed missing blank line before 2nd expansion unit "selected" line.

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 20, 2025):

Is there a way to use this advice from earlier combined with the port number you mention here? libata.force=X.Y:1.5G

I know you originally thought that it was bios control but maybe not? I just can't get past the fact that synology dropped the rate of these units to 1.5 and there must be a Reason and it might stabilize my unit. Also in the log I posted earlier there were occurrence of down leveling so it seems
To be something that happens already at least
In some cases.

@mervincm commented on GitHub (Sep 20, 2025): Is there a way to use this advice from earlier combined with the port number you mention here? libata.force=X.Y:1.5G I know you originally thought that it was bios control but maybe not? I just can't get past the fact that synology dropped the rate of these units to 1.5 and there must be a Reason and it might stabilize my unit. Also in the log I posted earlier there were occurrence of down leveling so it seems To be something that happens already at least In some cases.

kerem commented

Author

Owner

@007revad commented on GitHub (Sep 20, 2025):

What brand and model drives do you have in the DX513? Have you tried disabling write caching for those drives?

@007revad commented on GitHub (Sep 20, 2025): What brand and model drives do you have in the DX513? Have you tried disabling write caching for those drives?

kerem commented

Author

Owner

@ctl26481 commented on GitHub (Sep 20, 2025):

Is there a way to use this advice from earlier combined with the port number you mention here? libata.force=X.Y:1.5G

I know you originally thought that it was bios control but maybe not? I just can't get past the fact that synology dropped the rate of these units to 1.5 and there must be a Reason and it might stabilize my unit. Also in the log I posted earlier there were occurrence of down leveling so it seems To be something that happens already at least In some cases.

According to your dmesg log with DS1821+, the ports mapped to eSATA are ata1 and ata6. You're using ata6 for the DX so you should add libata.force=6.00:1.5G into your kernel cmdline. To add other parameters into it you need a comma to separate them like libata.force=6.00:1.5G,6.00:noncq. But this engages on the port itself, not the multiplexed ports so I have no idea if this has to be adapted into 6.0x, 6.0y and 6.0z.

You have to mount the synoboot1(USB DOM) and edit grub/grub.cfg, a little bit dangerous but someone did attempt noncq on their $yno with fine result:
https://www.reddit.com/r/synology/comments/eri5dg/ds1019_ironwolf_8tb_softlocks_high_io_waits/?tl=zh-hant

After that, you reboot and check if the horkage/quirk was enabled from dmesg | grep -i horkage.

Disclaimer: I run XPE but noncq does work on my system, use at your own risk. (There's success story from reddit.)

@ctl26481 commented on GitHub (Sep 20, 2025): > Is there a way to use this advice from earlier combined with the port number you mention here? libata.force=X.Y:1.5G > > I know you originally thought that it was bios control but maybe not? I just can't get past the fact that synology dropped the rate of these units to 1.5 and there must be a Reason and it might stabilize my unit. Also in the log I posted earlier there were occurrence of down leveling so it seems To be something that happens already at least In some cases. According to your dmesg log with DS1821+, the ports mapped to eSATA are ata1 and ata6. You're using ata6 for the DX so you should add `libata.force=6.00:1.5G` into your kernel cmdline. To add other parameters into it you need a comma to separate them like `libata.force=6.00:1.5G,6.00:noncq`. But this engages on the port itself, not the multiplexed ports so I have no idea if this has to be adapted into 6.0x, 6.0y and 6.0z. You have to mount the synoboot1(USB DOM) and edit grub/grub.cfg, a little bit dangerous but someone did attempt noncq on their $yno with fine result: https://www.reddit.com/r/synology/comments/eri5dg/ds1019_ironwolf_8tb_softlocks_high_io_waits/?tl=zh-hant After that, you reboot and check if the horkage/quirk was enabled from `dmesg | grep -i horkage`. Disclaimer: I run XPE but noncq does work on my system, use at your own risk. (There's success story from reddit.)

kerem commented

Author

Owner

@steinreiter commented on GitHub (Sep 20, 2025):

Please dont modify your USB-DOM and brick your DS1821+. That happen to often for testing purproses.There is an alternative...

You need an usb key with modifiable VID/PID. All Synology DOMs have the same, F400 for both. The first usb device with that VID/PID is used to boot from...

Look here: https://xpenology.com/forum/topic/13011-generate-an-original-synology-usb-key/

After modify the VID/PID of the usb key, make an exact copy of the DOM to the usb key. Power of the syno and pull the DOM from the mainboard and put the usb key into a normal synos usb slot. Now the syno should boot from it and you can modify the data on the usb key for testing things...

@steinreiter commented on GitHub (Sep 20, 2025): Please dont modify your USB-DOM and brick your DS1821+. That happen to often for testing purproses.There is an alternative... You need an usb key with modifiable VID/PID. All Synology DOMs have the same, F400 for both. The first usb device with that VID/PID is used to boot from... Look here: https://xpenology.com/forum/topic/13011-generate-an-original-synology-usb-key/ After modify the VID/PID of the usb key, make an exact copy of the DOM to the usb key. Power of the syno and pull the DOM from the mainboard and put the usb key into a normal synos usb slot. Now the syno should boot from it and you can modify the data on the usb key for testing things...

kerem commented

Author

Owner

@007revad commented on GitHub (Sep 20, 2025):

The DS1821+'s model.dtb file contains a libata section for each drive bay in a DX517.

	DX517 {
		compatible = "Synology";
		model = "synology_dx517";

		pmp_slot@1 {

			libata {
				EMID = <0x00>;
				pmp_link = <0x00>;
			};
		};

		pmp_slot@2 {

			libata {
				EMID = <0x00>;
				pmp_link = <0x01>;
			};
		};

		pmp_slot@3 {

			libata {
				EMID = <0x00>;
				pmp_link = <0x02>;
			};
		};

		pmp_slot@4 {

			libata {
				EMID = <0x00>;
				pmp_link = <0x03>;
			};
		};

		pmp_slot@5 {

			libata {
				EMID = <0x00>;
				pmp_link = <0x04>;
			};
		};
	};

For a DX513 the script edits model.dtb to add the code above but replaces DX517 and dx517 with DX513 and dx513.

	DX513 {
		compatible = "Synology";
		model = "synology_dx513";

I'm wondering if there's something we can add to force those "pmp_slot"s to 1.5G.

@007revad commented on GitHub (Sep 20, 2025): The DS1821+'s model.dtb file contains a libata section for each drive bay in a DX517. ``` DX517 { compatible = "Synology"; model = "synology_dx517"; pmp_slot@1 { libata { EMID = <0x00>; pmp_link = <0x00>; }; }; pmp_slot@2 { libata { EMID = <0x00>; pmp_link = <0x01>; }; }; pmp_slot@3 { libata { EMID = <0x00>; pmp_link = <0x02>; }; }; pmp_slot@4 { libata { EMID = <0x00>; pmp_link = <0x03>; }; }; pmp_slot@5 { libata { EMID = <0x00>; pmp_link = <0x04>; }; }; }; ``` For a DX513 the script edits model.dtb to add the code above but replaces DX517 and dx517 with DX513 and dx513. ``` DX513 { compatible = "Synology"; model = "synology_dx513"; ``` I'm wondering if there's something we can add to force those "pmp_slot"s to 1.5G.

kerem commented

Author

Owner

@007revad commented on GitHub (Sep 20, 2025):

Please dont modify your USB-DOM and brick your DS1821+. That happen to often for testing purproses.There is an alternative...

I have backups of all my Synology's USB-DOMs. https://github.com/007revad/Synoboot_backup

You need an usb key with modifiable VID (VendorID). All Synology DOMs have the same. The first usb device with that VID is used to boot from...

You need a tool that can edit your USB key or thumb drive's VID and PID. Set both to F400. Also small USB keys/thumb drives boot faster. If you're using a larger one you can format it to a smaller size. Synology USB-DOMs are 150 MB.

@007revad commented on GitHub (Sep 20, 2025): > Please dont modify your USB-DOM and brick your DS1821+. That happen to often for testing purproses.There is an alternative... I have backups of all my Synology's USB-DOMs. https://github.com/007revad/Synoboot_backup > You need an usb key with modifiable VID (VendorID). All Synology DOMs have the same. The first usb device with that VID is used to boot from... You need a tool that can edit your USB key or thumb drive's VID and PID. Set both to F400. Also small USB keys/thumb drives boot faster. If you're using a larger one you can format it to a smaller size. Synology USB-DOMs are 150 MB.

kerem commented

Author

Owner

@steinreiter commented on GitHub (Sep 20, 2025):

I'm wondering if there's something we can add to force those "pmp_slot"s to 1.5G.

Maybe @mervincm can read out the original values for the DX513 from his DS1815+ dtb? Maybe it contains additional options to force 1.5Gbs?

@steinreiter commented on GitHub (Sep 20, 2025): > I'm wondering if there's something we can add to force those "pmp_slot"s to 1.5G. Maybe @mervincm can read out the original values for the DX513 from his DS1815+ dtb? Maybe it contains additional options to force 1.5Gbs?

kerem commented

Author

Owner

@007revad commented on GitHub (Sep 20, 2025):

Unfortunately only recent Synology models use a device tree blob (model.dtb). Basically '20 series models and newer that use a CPU Synology had not used in older models.

Older models had everything compiled into the kernel.

@007revad commented on GitHub (Sep 20, 2025): Unfortunately only recent Synology models use a device tree blob (model.dtb). Basically '20 series models and newer that use a CPU Synology had not used in older models. Older models had everything compiled into the kernel.

kerem commented

Author

Owner

@steinreiter commented on GitHub (Sep 20, 2025):

Okay we need the kernel code of the newer CPU models, e.g. v1000, to determine if there is an extra option for link speed or something else read from device tree blob...

Maybe we can find something here:
https://archive.synology.com/download/ToolChain/Synology%20NAS%20GPL%20Source/7.2-72806

@steinreiter commented on GitHub (Sep 20, 2025): Okay we need the kernel code of the newer CPU models, e.g. v1000, to determine if there is an extra option for link speed or something else read from device tree blob... Maybe we can find something here: https://archive.synology.com/download/ToolChain/Synology%20NAS%20GPL%20Source/7.2-72806

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 20, 2025):

I originally had 5 WD RED and Seagate iron wolf 6TB. I thought maybe the disks were the issue (old/bad or just too many for the PSU) so I replaced them with 4 8TB disks (will add exact models later) I could put together that were working in other applications. In both situations the problem seemed to affect all disks fairly uniformly. This is partially why I was thinking it’s the link to the enclosure and not a specific disk model item. I had not tried disabling the write cache because I thought that would slow down responses, and I had slow response issue. I will try it though. Thanks for the suggestion. On Sep 20, 2025, at 1:43 AM, steinreiter @.***> wrote:steinreiter left a comment (007revad/Synology_enable_eunit#57)
Please dont modify your USB-DOM and brick your DS1821+. That happen to often for testing purproses.There is an alternative...
You need an usb key with modifiable VID (VendorID). All Synology DOMs have the same. The first usb device with that VID is used to boot from...
After modify the VID, make an exact copy of the DOM to the usb key. Power of the syno and pull the DOM from the mainboard and put the usb key into an normal synos usb slot. Now the syno should boot from it and you can modify the data of the usn key for testing things...

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@mervincm commented on GitHub (Sep 20, 2025): I originally had 5 WD RED and Seagate iron wolf 6TB. I thought maybe the disks were the issue (old/bad or just too many for the PSU) so I replaced them with 4 8TB disks (will add exact models later) I could put together that were working in other applications. In both situations the problem seemed to affect all disks fairly uniformly. This is partially why I was thinking it’s the link to the enclosure and not a specific disk model item. I had not tried disabling the write cache because I thought that would slow down responses, and I had slow response issue. I will try it though. Thanks for the suggestion. On Sep 20, 2025, at 1:43 AM, steinreiter ***@***.***> wrote:steinreiter left a comment (007revad/Synology_enable_eunit#57) Please dont modify your USB-DOM and brick your DS1821+. That happen to often for testing purproses.There is an alternative... You need an usb key with modifiable VID (VendorID). All Synology DOMs have the same. The first usb device with that VID is used to boot from... After modify the VID, make an exact copy of the DOM to the usb key. Power of the syno and pull the DOM from the mainboard and put the usb key into an normal synos usb slot. Now the syno should boot from it and you can modify the data of the usn key for testing things... —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 20, 2025):

Interesting! I will see if there is something on Amazon.ca that has that feature and order a couple just in case. I appreciate the safer options. On Sep 20, 2025, at 1:43 AM, steinreiter @.***> wrote:steinreiter left a comment (007revad/Synology_enable_eunit#57)
Please dont modify your USB-DOM and brick your DS1821+. That happen to often for testing purproses.There is an alternative...
You need an usb key with modifiable VID (VendorID). All Synology DOMs have the same. The first usb device with that VID is used to boot from...
After modify the VID, make an exact copy of the DOM to the usb key. Power of the syno and pull the DOM from the mainboard and put the usb key into an normal synos usb slot. Now the syno should boot from it and you can modify the data of the usn key for testing things...

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@mervincm commented on GitHub (Sep 20, 2025): Interesting! I will see if there is something on Amazon.ca that has that feature and order a couple just in case. I appreciate the safer options. On Sep 20, 2025, at 1:43 AM, steinreiter ***@***.***> wrote:steinreiter left a comment (007revad/Synology_enable_eunit#57) Please dont modify your USB-DOM and brick your DS1821+. That happen to often for testing purproses.There is an alternative... You need an usb key with modifiable VID (VendorID). All Synology DOMs have the same. The first usb device with that VID is used to boot from... After modify the VID, make an exact copy of the DOM to the usb key. Power of the syno and pull the DOM from the mainboard and put the usb key into an normal synos usb slot. Now the syno should boot from it and you can modify the data of the usn key for testing things... —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 20, 2025):

That’s a detail my Google-fu did not locate, thank you. It’s been quite a few years since I ran XPE, glad to hear it’s still around.On Sep 20, 2025, at 1:00 AM, ctl26481 @.***> wrote:ctl26481 left a comment (007revad/Synology_enable_eunit#57)

Is there a way to use this advice from earlier combined with the port number you mention here? libata.force=X.Y:1.5G
I know you originally thought that it was bios control but maybe not? I just can't get past the fact that synology dropped the rate of these units to 1.5 and there must be a Reason and it might stabilize my unit. Also in the log I posted earlier there were occurrence of down leveling so it seems To be something that happens already at least In some cases.

According to your dmesg log with DS1821+, the ports mapped to eSATA are ata1 and ata6. You're using ata6 for the DX so you should add libata.force=6.00:1.5G into your kernel cmdline. To add other parameters into it you need a comma to separate them like libata.force=6.00:1.5G,6.00:noncq.
You have to mount the synoboot1(USB DOM) and edit grub/grub.cfg, a little bit dangerous but someone did attempt noncq on their $yno with fine result:
https://www.reddit.com/r/synology/comments/eri5dg/ds1019_ironwolf_8tb_softlocks_high_io_waits/?tl=zh-hant
After that, you reboot and check if the horkage/quirk was enabled from dmesg | grep -i horkage.
Disclaimer: I run XPE but noncq does work on my system, use at your own risk. (There's success story from reddit.)

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@mervincm commented on GitHub (Sep 20, 2025): That’s a detail my Google-fu did not locate, thank you. It’s been quite a few years since I ran XPE, glad to hear it’s still around.On Sep 20, 2025, at 1:00 AM, ctl26481 ***@***.***> wrote:ctl26481 left a comment (007revad/Synology_enable_eunit#57) Is there a way to use this advice from earlier combined with the port number you mention here? libata.force=X.Y:1.5G I know you originally thought that it was bios control but maybe not? I just can't get past the fact that synology dropped the rate of these units to 1.5 and there must be a Reason and it might stabilize my unit. Also in the log I posted earlier there were occurrence of down leveling so it seems To be something that happens already at least In some cases. According to your dmesg log with DS1821+, the ports mapped to eSATA are ata1 and ata6. You're using ata6 for the DX so you should add libata.force=6.00:1.5G into your kernel cmdline. To add other parameters into it you need a comma to separate them like libata.force=6.00:1.5G,6.00:noncq. You have to mount the synoboot1(USB DOM) and edit grub/grub.cfg, a little bit dangerous but someone did attempt noncq on their $yno with fine result: https://www.reddit.com/r/synology/comments/eri5dg/ds1019_ironwolf_8tb_softlocks_high_io_waits/?tl=zh-hant After that, you reboot and check if the horkage/quirk was enabled from dmesg | grep -i horkage. Disclaimer: I run XPE but noncq does work on my system, use at your own risk. (There's success story from reddit.) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 20, 2025):

Unfortunately I sold my 1815+ soon after I got my 1821+On Sep 20, 2025, at 1:54 AM, steinreiter @.***> wrote:steinreiter left a comment (007revad/Synology_enable_eunit#57)

I'm wondering if there's something we can add to force those "pmp_slot"s to 1.5G.

Maybe @mervincm can read out the original values for the DX513 from his DS1815+ dtb?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@mervincm commented on GitHub (Sep 20, 2025): Unfortunately I sold my 1815+ soon after I got my 1821+On Sep 20, 2025, at 1:54 AM, steinreiter ***@***.***> wrote:steinreiter left a comment (007revad/Synology_enable_eunit#57) I'm wondering if there's something we can add to force those "pmp_slot"s to 1.5G. Maybe @mervincm can read out the original values for the DX513 from his DS1815+ dtb? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

kerem commented

Author

Owner

@007revad commented on GitHub (Sep 21, 2025):

First try disabling the HDDs' write cache. It's a quick and easy test. I saw it mentioned on the truenas forum to solve a similar issue.

@007revad commented on GitHub (Sep 21, 2025): First try disabling the HDDs' write cache. It's a quick and easy test. I saw it mentioned on the truenas forum to solve a similar issue. <img width="951" height="572" alt="Image" src="https://github.com/user-attachments/assets/60dc9f16-e085-4725-9e8f-1ceaf991f931" />

kerem commented

Author

Owner

@steinreiter commented on GitHub (Sep 21, 2025):

I did some research and found the following. By "write cache," we always mean the cache on the drive itself, not any buffering done by the operating system. The use of the internal hard drive cache can be enabled or disabled via an ATA command. The interesting thing is that each HDD manufacturer implements the use of the internal cache according to their own specifications. The data, as well as the commands to the HDD, can be reordered and optimized by the controller in the cache before being written to the hard drive.

With write cache disabled, most single operations can even be faster, see here:
https://medium.com/coccoc-engineering-blog/performance-impact-of-write-cache-for-hard-solid-state-disk-drives-755d01fcce61

Depending on the implementation, enabled write cache can be delays in command responses. This could possibly explain the behavior and the additional delay response to a single disk caused by the SIL3826?!

@mervincm, please try disabling that feature as described above by @007revad and then run a HDD read/write performance test.

@steinreiter commented on GitHub (Sep 21, 2025): I did some research and found the following. By "write cache," we always mean the cache on the drive itself, not any buffering done by the operating system. The use of the internal hard drive cache can be enabled or disabled via an ATA command. The interesting thing is that each HDD manufacturer implements the use of the internal cache according to their own specifications. The data, as well as the commands to the HDD, can be reordered and optimized by the controller in the cache before being written to the hard drive. With write cache disabled, most single operations can even be faster, see here: https://medium.com/coccoc-engineering-blog/performance-impact-of-write-cache-for-hard-solid-state-disk-drives-755d01fcce61 Depending on the implementation, enabled write cache can be delays in command responses. This could possibly explain the behavior and the additional delay response to a single disk caused by the SIL3826?! @mervincm, please try disabling that feature as described above by @007revad and then run a HDD read/write performance test.

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 21, 2025):

Will do

On Sun, Sep 21, 2025 at 3:44 AM steinreiter @.***>
wrote:

steinreiter left a comment (007revad/Synology_enable_eunit#57)
https://github.com/007revad/Synology_enable_eunit/issues/57#issuecomment-3315881308

I did some research and found the following. By "write cache," we always
mean the cache on the drive itself, not any buffering done by the operating
system. The use of the internal hard drive cache can be enabled or disabled
via an ATA command. The interesting thing is that each HDD manufacturer
implements the use of the internal cache according to their own
specifications. The data, as well as the commands to the HDD, can be
reordered and optimized by the controller in the cache before being written
to the hard drive.

With write cache disabled, some operations can even be faster, see here:

https://medium.com/coccoc-engineering-blog/performance-impact-of-write-cache-for-hard-solid-state-disk-drives-755d01fcce61

Depending on the implementation, enabled write cache can be delays in
command responses. This could possibly explain the behavior and the
additional delay caused by the SIL3826?

@mervincm https://github.com/mervincm, please try disabling that
feature as described above by @007revad https://github.com/007revad and
then run a HDD read/write performance test.

—
Reply to this email directly, view it on GitHub
https://github.com/007revad/Synology_enable_eunit/issues/57#issuecomment-3315881308,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMO7QZUWVG6BGJFRL2EWQ3L3TZXPXAVCNFSM6AAAAACC67J5POVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMJVHA4DCMZQHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@mervincm commented on GitHub (Sep 21, 2025): Will do On Sun, Sep 21, 2025 at 3:44 AM steinreiter ***@***.***> wrote: > *steinreiter* left a comment (007revad/Synology_enable_eunit#57) > <https://github.com/007revad/Synology_enable_eunit/issues/57#issuecomment-3315881308> > > I did some research and found the following. By "write cache," we always > mean the cache on the drive itself, not any buffering done by the operating > system. The use of the internal hard drive cache can be enabled or disabled > via an ATA command. The interesting thing is that each HDD manufacturer > implements the use of the internal cache according to their own > specifications. The data, as well as the commands to the HDD, can be > reordered and optimized by the controller in the cache before being written > to the hard drive. > > With write cache disabled, some operations can even be faster, see here: > > https://medium.com/coccoc-engineering-blog/performance-impact-of-write-cache-for-hard-solid-state-disk-drives-755d01fcce61 > > Depending on the implementation, enabled write cache can be delays in > command responses. This could possibly explain the behavior and the > additional delay caused by the SIL3826? > > @mervincm <https://github.com/mervincm>, please try disabling that > feature as described above by @007revad <https://github.com/007revad> and > then run a HDD read/write performance test. > > — > Reply to this email directly, view it on GitHub > <https://github.com/007revad/Synology_enable_eunit/issues/57#issuecomment-3315881308>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AMO7QZUWVG6BGJFRL2EWQ3L3TZXPXAVCNFSM6AAAAACC67J5POVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMJVHA4DCMZQHA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 21, 2025):

What brand and model drives do you have in the DX513? Have you tried disabling write caching for those drives?

I have just disabled disk write cache on the four. Reboot included the multiple rounds of failure/retry light dance, but it completed without incident I can check dmesg later for errors, but no obvious issue/change. Disks are one of each of these. ST8000VN0022-2EL112,SC61,8001 GB
WD80EDAZ-11TA3A0,81.00A81,8001 GB
WD80EDBZ-11B0ZA0,85.00A85,8001 GB
WD80EFBX-68AZZN0,85.00A85,8001 GB

But I used to have 5 identical 6TB WD RED and the behaviour was the same.

@mervincm commented on GitHub (Sep 21, 2025): > What brand and model drives do you have in the DX513? Have you tried disabling write caching for those drives? > > I have just disabled disk write cache on the four. Reboot included the multiple rounds of failure/retry light dance, but it completed without incident I can check dmesg later for errors, but no obvious issue/change. Disks are one of each of these. ST8000VN0022-2EL112,SC61,8001 GB WD80EDAZ-11TA3A0,81.00A81,8001 GB WD80EDBZ-11B0ZA0,85.00A85,8001 GB WD80EFBX-68AZZN0,85.00A85,8001 GB But I used to have 5 identical 6TB WD RED and the behaviour was the same.

kerem commented

Author

Owner

@steinreiter commented on GitHub (Sep 24, 2025):

Does this mean that the alternative to reduce the link speed is, the write cache should be disabled on every hard drive in a DX513 using the script syno_enable_eunit.sh to ensure stable operation on all DX513 variants?! Were you able to test it, @mervincm?

@mervincm, whats about performance degradation on writing with disabled disk cache? Such a benchmark can now also be conveniently performed for a single disk in parallel via the storage manager in the DSM interface:

Best regards and have a nice day

@steinreiter commented on GitHub (Sep 24, 2025): Does this mean that the alternative to reduce the link speed is, the write cache should be disabled on every hard drive in a DX513 using the script syno_enable_eunit.sh to ensure stable operation on all DX513 variants?! Were you able to test it, @mervincm? @mervincm, whats about performance degradation on writing with disabled disk cache? Such a benchmark can now also be conveniently performed for a single disk in parallel via the storage manager in the DSM interface: Best regards and have a nice day <img width="1054" height="741" alt="Image" src="https://github.com/user-attachments/assets/1bc191b7-33dd-4b64-84b0-f07efd392ce5" />

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 24, 2025):

I powered up manually (I have power up / power down jobs) just now and it seems that disabling the disk write cache isn't a fix. It actually let to an issue I only saw one time before ... all my disks in the DX513 are unavailable, and the volume required reassembling. this was quick and straight forward ... no consistency check or anything was required but ....

disk write cache disabled

disk write cache enabled

significant!

@mervincm commented on GitHub (Sep 24, 2025): I powered up manually (I have power up / power down jobs) just now and it seems that disabling the disk write cache isn't a fix. It actually let to an issue I only saw one time before ... all my disks in the DX513 are unavailable, and the volume required reassembling. this was quick and straight forward ... no consistency check or anything was required but .... disk write cache disabled <img width="277" height="259" alt="Image" src="https://github.com/user-attachments/assets/1c846585-40e9-46dd-a09f-234b291cd05f" /> disk write cache enabled <img width="491" height="461" alt="Image" src="https://github.com/user-attachments/assets/17807561-e690-43e3-9574-7952ecb3596d" /> significant!

kerem commented

DS1815
https://global.synologydownload.com/download/ToolChain/Synology%20NAS%20GPL%20Source/7.1.1-42962/avoton/linux-3.10.x.txz

Author

Owner

@steinreiter commented on GitHub (Sep 24, 2025):

Okay, that's sad to hear.

I'm currently trawling through the kernel source code of the

DS1821+
https://global.synologydownload.com/download/ToolChain/Synology%20NAS%20GPL%20Source/7.2-72806/v1000/linux-4.4.x.txz

I'm still digging around, but it's funny to find such comments in the source code

static inline void
syno_pm_enable_powerbtn_pkg_init(unsigned short vendor, unsigned short devid, SYNO_PM_PKG *pPKG)
{
	/* do not check parameters, caller should do it */

	memset(pPKG, 0, sizeof(*pPKG));
	/* DX513 and DX213 use silicon 3826 chip, but its cpld faked 3726 chip */
	if (syno_pm_is_3xxx(vendor, devid)) {
		pPKG->var = GPIO_3826_CMD_ENABLE_POWERBTN;
	} else if (syno_pm_is_9705(vendor, devid)) {
		pPKG->var = GPIO_9705_PKG_INIT(4,0x20);
	}

	/* add other port multiplier here */
}
...
#if defined(MY_ABC_HERE) && defined(MY_ABC_HERE)
	if (1 == g_syno_ds1815p_speed_limit) {
		// We limit DS1815+ internal SiI3132 port to 1.5Gbps to avoid ata error
		if (syno_is_hw_version(HW_DS1815p)) {
			if(ap && (ap->print_id == 7 || ap->print_id == 8)) {
				dev->horkage |= ATA_HORKAGE_1_5_GBPS;
			}
		}
	}
#endif /* MY_ABC_HERE && MY_ABC_HERE */

@steinreiter commented on GitHub (Sep 24, 2025): Okay, that's sad to hear. I'm currently trawling through the kernel source code of the DS1815 https://global.synologydownload.com/download/ToolChain/Synology%20NAS%20GPL%20Source/7.1.1-42962/avoton/linux-3.10.x.txz DS1821+ https://global.synologydownload.com/download/ToolChain/Synology%20NAS%20GPL%20Source/7.2-72806/v1000/linux-4.4.x.txz I'm still digging around, but it's funny to find such comments in the source code ``` static inline void syno_pm_enable_powerbtn_pkg_init(unsigned short vendor, unsigned short devid, SYNO_PM_PKG *pPKG) { /* do not check parameters, caller should do it */ memset(pPKG, 0, sizeof(*pPKG)); /* DX513 and DX213 use silicon 3826 chip, but its cpld faked 3726 chip */ if (syno_pm_is_3xxx(vendor, devid)) { pPKG->var = GPIO_3826_CMD_ENABLE_POWERBTN; } else if (syno_pm_is_9705(vendor, devid)) { pPKG->var = GPIO_9705_PKG_INIT(4,0x20); } /* add other port multiplier here */ } ... #if defined(MY_ABC_HERE) && defined(MY_ABC_HERE) if (1 == g_syno_ds1815p_speed_limit) { // We limit DS1815+ internal SiI3132 port to 1.5Gbps to avoid ata error if (syno_is_hw_version(HW_DS1815p)) { if(ap && (ap->print_id == 7 || ap->print_id == 8)) { dev->horkage |= ATA_HORKAGE_1_5_GBPS; } } } #endif /* MY_ABC_HERE && MY_ABC_HERE */ ```

kerem commented

Author

Owner

@steinreiter commented on GitHub (Sep 24, 2025):

Hello friends,

I've spent several hours studying the source code of the kernels customized by Synology, especially libata-pmp, libata-core, synobios, and libahci.

The code for the DS1815+ does contain special workarounds in the code enabled for the DS1815+ via custom settings in the kernel config. Also the following hard-coded SATA link speed reductions are set, but these only apply to much older DiskStations.

int sata_pmp_attach(struct ata_device *dev)
{
...
#ifdef MY_ABC_HERE
	if (0 == ap->PMSynoEMID) {
		ap->pflags |= ATA_PFLAG_SYNO_BOOT_PROBE;
	}
#endif /* MY_ABC_HERE */
	/* DX510 has {ICRC, ABRT} problem under heavy loading IO, force 1.5Gbps can avoid this problem */
	if (IS_SYNOLOGY_DX510(ap->PMSynoUnique)) {
		target = 1;
		target_limit = (1 << target) - 1;

		if(link->sata_spd_limit != target_limit) {
			ata_dev_printk(dev, KERN_ERR,
					"Enhance DX510 compatibility, limit the speed to 1.5 Gbps\n");

			link->sata_spd_limit = target_limit;
		}
	/*For DS412+, qoriq, 6282 with DX513, the link should be limited to 1.5G*/
	} else if (IS_SYNOLOGY_DX513(ap->PMSynoUnique) &&
			(syno_is_hw_version(HW_DS412p)    ||
			 syno_is_hw_version(HW_DS112)     ||
			 syno_is_hw_version(HW_DS112pv10) ||
			 syno_is_hw_version(HW_DS213pv10) ||
			 syno_is_hw_version(HW_DS413)     ||
			 syno_is_hw_version(HW_DS212pv10) ||
			 syno_is_hw_version(HW_DS212pv20))) {
		target = 1;
		target_limit = (1 << target) - 1;

		if(link->sata_spd_limit != target_limit) {
			ata_dev_printk(dev, KERN_ERR,
					"DX513 workaround, limit the speed to 1.5 GBPS\n");

			link->sata_spd_limit = target_limit;
		}
	/*For DS412+, qoriq, 212p with and DX213, the link should be limited to 1.5G*/
	} else if (IS_SYNOLOGY_DX213(ap->PMSynoUnique) &&
			(syno_is_hw_version(HW_DS412p)     ||
			 syno_is_hw_version(HW_DS213pv10)  ||
			 syno_is_hw_version(HW_DS413)      ||
			 syno_is_hw_version(HW_DS212pv10)  ||
			 syno_is_hw_version(HW_DS212pv20))) {
		target = 1;
		target_limit = (1 << target) - 1;

		if(link->sata_spd_limit != target_limit) {
			ata_dev_printk(dev, KERN_ERR,
					"DX213 workaround, limit the speed to 1.5 GBPS\n");

			link->sata_spd_limit = target_limit;
		}
	}
#endif /* MY_ABC_HERE */
...

Regardless of this, the DX1821+ kernel code only contains the link speed reduction for the DX510.

int sata_pmp_attach(struct ata_device *dev)
{
...
#ifdef MY_ABC_HERE
	/* DX510 has {ICRC, ABRT} problem under heavy loading IO, force 1.5Gbps can avoid this problem */
	if (IS_SYNOLOGY_DX510(ap->PMSynoUnique)) {
		target = 1;
		target_limit = (1 << target) - 1;

		if (link->sata_spd_limit != target_limit) {
			ata_dev_printk(dev, KERN_ERR,
					"Enhance DX510 compatibility, limit the speed to 1.5 Gbps\n");

			link->sata_spd_limit = target_limit;
		}
	}
#endif /* MY_ABC_HERE */
#ifdef MY_ABC_HERE
...

As far as I can see (I'm a software developer for embedded systems and system on chips myself), the link speed cannot be set directly via a device tree property. This is neither provided for in the standard kernel code nor in Synology's additional code.

This means that for the Diskstations with AMD v1000 CPU the hardware SATA controller independently negotiates the appropriate link speed with the SATA PMP (SATA Programmable Multi-Port) of a DX-Expansion.

Alternatively, as described by @ctl26481 , there is only the possibility of setting the link speed during boot for all or individual ATA devices directly via kernel parameters (this is then transferred when the kernel AHCI driver is loaded).

Sorry guys for the bad news, but it looks like you won't be able to avoid cloning the Syno DOM onto a USB key and playing around with the libata boot parameters on a DX1821+/DS1621+ in combination with a DX513 to solve the entire problem of @mervincm .

@steinreiter commented on GitHub (Sep 24, 2025): Hello friends, I've spent several hours studying the source code of the kernels customized by Synology, especially libata-pmp, libata-core, synobios, and libahci. The code for the DS1815+ does contain special workarounds in the code enabled for the DS1815+ via custom settings in the kernel config. Also the following hard-coded SATA link speed reductions are set, but these only apply to much older DiskStations. ``` int sata_pmp_attach(struct ata_device *dev) { ... #ifdef MY_ABC_HERE if (0 == ap->PMSynoEMID) { ap->pflags |= ATA_PFLAG_SYNO_BOOT_PROBE; } #endif /* MY_ABC_HERE */ /* DX510 has {ICRC, ABRT} problem under heavy loading IO, force 1.5Gbps can avoid this problem */ if (IS_SYNOLOGY_DX510(ap->PMSynoUnique)) { target = 1; target_limit = (1 << target) - 1; if(link->sata_spd_limit != target_limit) { ata_dev_printk(dev, KERN_ERR, "Enhance DX510 compatibility, limit the speed to 1.5 Gbps\n"); link->sata_spd_limit = target_limit; } /*For DS412+, qoriq, 6282 with DX513, the link should be limited to 1.5G*/ } else if (IS_SYNOLOGY_DX513(ap->PMSynoUnique) && (syno_is_hw_version(HW_DS412p) || syno_is_hw_version(HW_DS112) || syno_is_hw_version(HW_DS112pv10) || syno_is_hw_version(HW_DS213pv10) || syno_is_hw_version(HW_DS413) || syno_is_hw_version(HW_DS212pv10) || syno_is_hw_version(HW_DS212pv20))) { target = 1; target_limit = (1 << target) - 1; if(link->sata_spd_limit != target_limit) { ata_dev_printk(dev, KERN_ERR, "DX513 workaround, limit the speed to 1.5 GBPS\n"); link->sata_spd_limit = target_limit; } /*For DS412+, qoriq, 212p with and DX213, the link should be limited to 1.5G*/ } else if (IS_SYNOLOGY_DX213(ap->PMSynoUnique) && (syno_is_hw_version(HW_DS412p) || syno_is_hw_version(HW_DS213pv10) || syno_is_hw_version(HW_DS413) || syno_is_hw_version(HW_DS212pv10) || syno_is_hw_version(HW_DS212pv20))) { target = 1; target_limit = (1 << target) - 1; if(link->sata_spd_limit != target_limit) { ata_dev_printk(dev, KERN_ERR, "DX213 workaround, limit the speed to 1.5 GBPS\n"); link->sata_spd_limit = target_limit; } } #endif /* MY_ABC_HERE */ ... ``` Regardless of this, the DX1821+ kernel code only contains the link speed reduction for the DX510. ``` int sata_pmp_attach(struct ata_device *dev) { ... #ifdef MY_ABC_HERE /* DX510 has {ICRC, ABRT} problem under heavy loading IO, force 1.5Gbps can avoid this problem */ if (IS_SYNOLOGY_DX510(ap->PMSynoUnique)) { target = 1; target_limit = (1 << target) - 1; if (link->sata_spd_limit != target_limit) { ata_dev_printk(dev, KERN_ERR, "Enhance DX510 compatibility, limit the speed to 1.5 Gbps\n"); link->sata_spd_limit = target_limit; } } #endif /* MY_ABC_HERE */ #ifdef MY_ABC_HERE ... ``` As far as I can see (I'm a software developer for embedded systems and system on chips myself), the link speed cannot be set directly via a device tree property. This is neither provided for in the standard kernel code nor in Synology's additional code. This means that for the Diskstations with AMD v1000 CPU the hardware SATA controller independently negotiates the appropriate link speed with the SATA PMP (SATA Programmable Multi-Port) of a DX-Expansion. Alternatively, as described by @ctl26481 , there is only the possibility of setting the link speed during boot for all or individual ATA devices directly via kernel parameters (this is then transferred when the kernel AHCI driver is loaded). Sorry guys for the bad news, but it looks like you won't be able to avoid cloning the Syno DOM onto a USB key and playing around with the libata boot parameters on a DX1821+/DS1621+ in combination with a DX513 to solve the entire problem of @mervincm .

kerem commented

Author

Owner

@mervincm commented on GitHub (Sep 24, 2025):

I really appreciate the effort! and the clear understanding. I also agree
that, for myself, with your position on risking the creation of a brick
from my 1821+ :). If I find a USB key for sale with an available tool to
customize VID and PID, I would definitely dig in deeper to see if the
kernel parameters made the difference or not, but for this issue in GIT…we
can consider this closed. A tons of thanks to both of you for the range of
attempts even if things remain unresolved.

On Wed, Sep 24, 2025 at 2:52 PM steinreiter @.***>
wrote:

steinreiter left a comment (007revad/Synology_enable_eunit#57)
https://github.com/007revad/Synology_enable_eunit/issues/57#issuecomment-3330624285

Hello friends,

I've spent several hours studying the source code of the kernels
customized by Synology, especially libata-pmp, libata-core, synobios, and
libahci.

The code for the DS1815+ does contain special workarounds in the code
enabled for the DS1815+ via custom settings in the kernel config. Also the
following hard-coded SATA link speed reductions are set, but these only
apply to much older DiskStations.

int sata_pmp_attach(struct ata_device dev)
{
...
#ifdef MY_ABC_HERE
if (0 == ap->PMSynoEMID) {
ap->pflags |= ATA_PFLAG_SYNO_BOOT_PROBE;
}
#endif / MY_ABC_HERE /
/ DX510 has {ICRC, ABRT} problem under heavy loading IO, force 1.5Gbps can avoid this problem */
if (IS_SYNOLOGY_DX510(ap->PMSynoUnique)) {
target = 1;
target_limit = (1 << target) - 1;
  if(link->sata_spd_limit != target_limit) {
  	ata_dev_printk(dev, KERN_ERR,
  			"Enhance DX510 compatibility, limit the speed to 1.5 Gbps\n");

  	link->sata_spd_limit = target_limit;
  }
/For DS412+, qoriq, 6282 with DX513, the link should be limited to 1.5G/
} else if (IS_SYNOLOGY_DX513(ap->PMSynoUnique) &&
(syno_is_hw_version(HW_DS412p) ||
syno_is_hw_version(HW_DS112) ||
syno_is_hw_version(HW_DS112pv10) ||
syno_is_hw_version(HW_DS213pv10) ||
syno_is_hw_version(HW_DS413) ||
syno_is_hw_version(HW_DS212pv10) ||
syno_is_hw_version(HW_DS212pv20))) {
target = 1;
target_limit = (1 << target) - 1;
  if(link->sata_spd_limit != target_limit) {
  	ata_dev_printk(dev, KERN_ERR,
  			"DX513 workaround, limit the speed to 1.5 GBPS\n");

  	link->sata_spd_limit = target_limit;
  }
/For DS412+, qoriq, 212p with and DX213, the link should be limited to 1.5G/
} else if (IS_SYNOLOGY_DX213(ap->PMSynoUnique) &&
(syno_is_hw_version(HW_DS412p) ||
syno_is_hw_version(HW_DS213pv10) ||
syno_is_hw_version(HW_DS413) ||
syno_is_hw_version(HW_DS212pv10) ||
syno_is_hw_version(HW_DS212pv20))) {
target = 1;
target_limit = (1 << target) - 1;
  if(link->sata_spd_limit != target_limit) {
  	ata_dev_printk(dev, KERN_ERR,
  			"DX213 workaround, limit the speed to 1.5 GBPS\n");

  	link->sata_spd_limit = target_limit;
  }
}
#endif /* MY_ABC_HERE */
...

Regardless of this, the DX1821+ kernel code only contains the link speed
reduction for the DX510.

int sata_pmp_attach(struct ata_device dev)
{
...
#ifdef MY_ABC_HERE
/ DX510 has {ICRC, ABRT} problem under heavy loading IO, force 1.5Gbps can avoid this problem */
if (IS_SYNOLOGY_DX510(ap->PMSynoUnique)) {
target = 1;
target_limit = (1 << target) - 1;
  if (link->sata_spd_limit != target_limit) {
  	ata_dev_printk(dev, KERN_ERR,
  			"Enhance DX510 compatibility, limit the speed to 1.5 Gbps\n");

  	link->sata_spd_limit = target_limit;
  }
}
#endif /* MY_ABC_HERE */
#ifdef MY_ABC_HERE
...

As far as I can see (I'm a software developer for embedded systems and
system on chips myself), the link speed cannot be set directly via a device
tree property. This is neither provided for in the standard kernel code nor
in Synology's additional code.

This means that for the Diskstations with AMD v1000 CPU the hardware SATA
controller independently negotiates the appropriate link speed with the
SATA PMP (SATA Programmable Multi-Port) of a DX-Expansion.

Alternatively, as described by @ctl26481 https://github.com/ctl26481 ,
there is only the possibility of setting the link speed during boot for all
or individual ATA devices directly via kernel parameters (this is then
transferred when the kernel AHCI driver is loaded).

Sorry guys for the bad news, but it looks like you won't be able to avoid
cloning the Syno DOM onto a USB key and playing around with the libata boot
parameters on a DX1821+/DS1621+ in combination with a DX513 to solve the
entire problem of @mervincm https://github.com/mervincm .

—
Reply to this email directly, view it on GitHub
https://github.com/007revad/Synology_enable_eunit/issues/57#issuecomment-3330624285,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMO7QZSV5HXLBC2CXQY3PQ33UMABNAVCNFSM6AAAAACC67J5POVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMZQGYZDIMRYGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

@mervincm commented on GitHub (Sep 24, 2025): I really appreciate the effort! and the clear understanding. I also agree that, for myself, with your position on risking the creation of a brick from my 1821+ :). If I find a USB key for sale with an available tool to customize VID and PID, I would definitely dig in deeper to see if the kernel parameters made the difference or not, but for this issue in GIT…we can consider this closed. A tons of thanks to both of you for the range of attempts even if things remain unresolved. On Wed, Sep 24, 2025 at 2:52 PM steinreiter ***@***.***> wrote: > *steinreiter* left a comment (007revad/Synology_enable_eunit#57) > <https://github.com/007revad/Synology_enable_eunit/issues/57#issuecomment-3330624285> > > Hello friends, > > I've spent several hours studying the source code of the kernels > customized by Synology, especially libata-pmp, libata-core, synobios, and > libahci. > > The code for the DS1815+ does contain special workarounds in the code > enabled for the DS1815+ via custom settings in the kernel config. Also the > following hard-coded SATA link speed reductions are set, but these only > apply to much older DiskStations. > > int sata_pmp_attach(struct ata_device *dev) > { > ... > #ifdef MY_ABC_HERE > if (0 == ap->PMSynoEMID) { > ap->pflags |= ATA_PFLAG_SYNO_BOOT_PROBE; > } > #endif /* MY_ABC_HERE */ > /* DX510 has {ICRC, ABRT} problem under heavy loading IO, force 1.5Gbps can avoid this problem */ > if (IS_SYNOLOGY_DX510(ap->PMSynoUnique)) { > target = 1; > target_limit = (1 << target) - 1; > > if(link->sata_spd_limit != target_limit) { > ata_dev_printk(dev, KERN_ERR, > "Enhance DX510 compatibility, limit the speed to 1.5 Gbps\n"); > > link->sata_spd_limit = target_limit; > } > /*For DS412+, qoriq, 6282 with DX513, the link should be limited to 1.5G*/ > } else if (IS_SYNOLOGY_DX513(ap->PMSynoUnique) && > (syno_is_hw_version(HW_DS412p) || > syno_is_hw_version(HW_DS112) || > syno_is_hw_version(HW_DS112pv10) || > syno_is_hw_version(HW_DS213pv10) || > syno_is_hw_version(HW_DS413) || > syno_is_hw_version(HW_DS212pv10) || > syno_is_hw_version(HW_DS212pv20))) { > target = 1; > target_limit = (1 << target) - 1; > > if(link->sata_spd_limit != target_limit) { > ata_dev_printk(dev, KERN_ERR, > "DX513 workaround, limit the speed to 1.5 GBPS\n"); > > link->sata_spd_limit = target_limit; > } > /*For DS412+, qoriq, 212p with and DX213, the link should be limited to 1.5G*/ > } else if (IS_SYNOLOGY_DX213(ap->PMSynoUnique) && > (syno_is_hw_version(HW_DS412p) || > syno_is_hw_version(HW_DS213pv10) || > syno_is_hw_version(HW_DS413) || > syno_is_hw_version(HW_DS212pv10) || > syno_is_hw_version(HW_DS212pv20))) { > target = 1; > target_limit = (1 << target) - 1; > > if(link->sata_spd_limit != target_limit) { > ata_dev_printk(dev, KERN_ERR, > "DX213 workaround, limit the speed to 1.5 GBPS\n"); > > link->sata_spd_limit = target_limit; > } > } > #endif /* MY_ABC_HERE */ > ... > > Regardless of this, the DX1821+ kernel code only contains the link speed > reduction for the DX510. > > int sata_pmp_attach(struct ata_device *dev) > { > ... > #ifdef MY_ABC_HERE > /* DX510 has {ICRC, ABRT} problem under heavy loading IO, force 1.5Gbps can avoid this problem */ > if (IS_SYNOLOGY_DX510(ap->PMSynoUnique)) { > target = 1; > target_limit = (1 << target) - 1; > > if (link->sata_spd_limit != target_limit) { > ata_dev_printk(dev, KERN_ERR, > "Enhance DX510 compatibility, limit the speed to 1.5 Gbps\n"); > > link->sata_spd_limit = target_limit; > } > } > #endif /* MY_ABC_HERE */ > #ifdef MY_ABC_HERE > ... > > As far as I can see (I'm a software developer for embedded systems and > system on chips myself), the link speed cannot be set directly via a device > tree property. This is neither provided for in the standard kernel code nor > in Synology's additional code. > > This means that for the Diskstations with AMD v1000 CPU the hardware SATA > controller independently negotiates the appropriate link speed with the > SATA PMP (SATA Programmable Multi-Port) of a DX-Expansion. > > Alternatively, as described by @ctl26481 <https://github.com/ctl26481> , > there is only the possibility of setting the link speed during boot for all > or individual ATA devices directly via kernel parameters (this is then > transferred when the kernel AHCI driver is loaded). > > Sorry guys for the bad news, but it looks like you won't be able to avoid > cloning the Syno DOM onto a USB key and playing around with the libata boot > parameters on a DX1821+/DS1621+ in combination with a DX513 to solve the > entire problem of @mervincm <https://github.com/mervincm> . > > — > Reply to this email directly, view it on GitHub > <https://github.com/007revad/Synology_enable_eunit/issues/57#issuecomment-3330624285>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AMO7QZSV5HXLBC2CXQY3PQ33UMABNAVCNFSM6AAAAACC67J5POVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMZQGYZDIMRYGU> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

kerem commented

Author

Owner

@steinreiter commented on GitHub (Sep 25, 2025):

@mervincm I'd also like to thank you for the pleasant exchange. I learned some interesting things about Synology expansion units that I probably would never have discovered without this issue ticket.

I'd also like to thank @007revad for your quick response and uncomplicated implementation regarding the NCQ deactivation. I think this will prevent some older Synology expansion units from ending up in the trash in the future, but will continue to be used. Thanks for your scripts in general.

Take care and have a great time.
Steinreiter

@steinreiter commented on GitHub (Sep 25, 2025): @mervincm I'd also like to thank you for the pleasant exchange. I learned some interesting things about Synology expansion units that I probably would never have discovered without this issue ticket. I'd also like to thank @007revad for your quick response and uncomplicated implementation regarding the NCQ deactivation. I think this will prevent some older Synology expansion units from ending up in the trash in the future, but will continue to be used. Thanks for your scripts in general. Take care and have a great time. Steinreiter

kerem commented

Author

Owner

@ctl26481 commented on GitHub (Jan 31, 2026):

I tested DX513(with SiI3862 PCB)+JMB582(with FBS) on a generic Linux distro and can confirm NCQ error does mess with booting, drive activity LED cycling with FPDMA QUEUED error flooding in text console as people mentioned. Using libata.force=noncq in boot parameter resolved this immediately and booted right up. But the issue is not present when I attach the DX with non-FBS(CBS only) SATA controller.

Assumptions:

NCQ can mess with FBS(FIS based switching)? Requiring noncq or queue=1.
Similar issue was also noted in an old mailing list, original user got better performance by using queue=1 : https://lore.kernel.org/linux-ide/?q=SiI+3726+pmp+doesn%27t+work+with+2.6.38+and+Marvell+88SE9123+AHCI+controller
CBS doesn't cause conflict with NCQ. But $yn definitely used FBS capable SATA controller for optimal performance
Genuine $yn units dodged this by using SiI3132 on older 3Gbps NAS (with customized sata_sil24), which is a non-AHCI compliant part.
Need to investigate further on 6Gbps units without SiI3132 controllers like DS918+ and DS916+. It might also be possible the issue is limited to JMicron controllers(also JMB585 on newer units), not Marvell controllers like on DS918+ with 88SE9215.

@ctl26481 commented on GitHub (Jan 31, 2026): I tested DX513(with SiI3862 PCB)+JMB582(with FBS) on a generic Linux distro and can confirm NCQ error does mess with booting, drive activity LED cycling with FPDMA QUEUED error flooding in text console as people mentioned. Using libata.force=noncq in boot parameter resolved this immediately and booted right up. But the issue is not present when I attach the DX with non-FBS(CBS only) SATA controller. Assumptions: 1. NCQ can mess with FBS(FIS based switching)? Requiring noncq or queue=1. Similar issue was also noted in an old mailing list, original user got better performance by using queue=1 : https://lore.kernel.org/linux-ide/?q=SiI+3726+pmp+doesn%27t+work+with+2.6.38+and+Marvell+88SE9123+AHCI+controller 2. CBS doesn't cause conflict with NCQ. But $yn definitely used FBS capable SATA controller for optimal performance 3. Genuine $yn units dodged this by using SiI3132 on older 3Gbps NAS (with customized sata_sil24), which is a non-AHCI compliant part. Need to investigate further on 6Gbps units without SiI3132 controllers like DS918+ and DS916+. It might also be possible the issue is limited to JMicron controllers(also JMB585 on newer units), not Marvell controllers like on DS918+ with 88SE9215.

kerem commented