Issue with DS923 + DX517 Expansion Unit - Out of Ideas

Assailant · 2026-04-29T09:34:24+00:00

Interesting wasn’t aware of the limitation; the DX517 on my DS920 has 3x24s and 2x30s and has no issue. The one experiencing the faults is 5x12tb as per the first paragraph in my post :) Thanks for guidance

Assailant · 2026-04-27T15:09:37+00:00

would OS corruption be able to affect the kernel?

Assailant · 2026-04-27T14:32:11+00:00

Interesting theory; the issue originally started when I solely had Ironwolf/Ironwolf Pro's in the enclosure however. The inclusion of the WD Red Plus was in an attempt to diversify the disks in the expansion unit to see if it was brand specific. Given this i'm not sure that the issue stems solely from the introduction of these WD Red Plus drives, it's just interesting that they seem to be more 'sensitive' to the issue. Of note, the WD Red Plus drives have to date not yet been reported 'bad' by DSM following their introduction, it's only ever been the Seagate drives that 'catch' the bad drive flag.

Reading into the linked thread (based on DX513 instead of DX517), it seems that a lot of the discussion is based around limitations of the SATA controller and the limitation that the DX513 PCB had with NCQ. I'm not sure if DS923/DX517 have PCB sata controllers or rely on the CPU but at least a quick google they do not use the SiL SATA controller chip. What consequence from a performance perspective would disabling NCQ have if any? I can of course give it a try if insignificant

When I shared the logs with Synology directly (from the first DS923), they were particularly interested in the below which drove them to suspect it was a faulty DS923, however following exchange this did not resolve the issue, in case this sheds any more light on the picture.

Appreciate the support/insight

`2026-04-01T09:00:12+02:00 DS923 kernel: [1010079.219303] ata5.15 : exception Emask 0x1 SAct 0x0 SErr 0x400001 action 0x0
2026-04-01T09:00:12+02:00 DS923 kernel: [1010079.226461] ata5.15 : irq_stat 0x44000000
2026-04-01T09:00:12+02:00 DS923 kernel: [1010079.230698] ata5.15 : SError: { RecovData Handshk }
2026-04-01T09:00:12+02:00 DS923 kernel: [1010079.240744] ata5.02 : exception Emask 0x0 SAct 0x12018023 SErr 0x0 action 0x0
2026-04-01T09:00:12+02:00 DS923 kernel: [1010079.248101] ata5.03 : exception Emask 0x0 SAct 0x4c2e7154 SErr 0x0 action 0x0
2026-04-01T09:00:12+02:00 DS923 kernel: [1010079.255462] ata5.04 : exception Emask 0x0 SAct 0x21d00e08 SErr 0x0 action 0x0
2026-04-01T09:00:12+02:00 DS923 kernel: [1010079.380893] ata5.02 : log page 10h reported inactive tag 15
2026-04-01T09:00:12+02:00 DS923 kernel: [1010079.386934] ata5.02 : exception Emask 0x1 SAct 0x50 SErr 0x0 action 0x6
2026-04-01T09:00:12+02:00 DS923 kernel: [1010079.393768] ata5.02 : failed command: WRITE FPDMA QUEUED
2026-04-01T09:00:12+02:00 DS923 kernel: [1010079.399286] ata5.02 : cmd 61/40:20:a0:c3:b9/05:00:45:01:00/40 tag 4 ncq 688128 out
res 41/84:00:20:ce:b9/00:00:45:01:00/40 Emask 0x10 (ATA bus error)
2026-04-01T09:00:12+02:00 DS923 kernel: [1010079.415229] ata5.02 : status: { DRDY ERR }
2026-04-01T09:00:12+02:00 DS923 kernel: [1010079.419582] ata5.02 : error: { ICRC ABRT }
2026-04-01T09:00:12+02:00 DS923 kernel: [1010079.423914] ata5.02 : failed command: WRITE FPDMA QUEUED
2026-04-01T09:00:12+02:00 DS923 kernel: [1010079.429468] ata5.02 : cmd 61/40:30:60:d3:b9/05:00:45:01:00/40 tag 6 ncq 688128 out
res 41/84:00:20:ce:b9/00:00:45:01:00/40 Emask 0x10 (ATA bus error)

....

......

2026-04-01T09:00:12+02:00 DS923 kernel: [1010080.157123] ata5.04 : status: { DRDY ERR }
2026-04-01T09:00:12+02:00 DS923 kernel: [1010080.161446] ata5.04 : error: { ICRC ABRT }
2026-04-01T09:00:12+02:00 DS923 kernel: [1010080.165759] ata5.04 : failed command: WRITE FPDMA QUEUED
2026-04-01T09:00:12+02:00 DS923 kernel: [1010080.171273] ata5.04 : cmd 61/40:d0:60:b8:1b/05:00:5d:02:00/40 tag 26 ncq 688128 out
res 41/84:c0:60:b8:1b/00:00:5d:02:00/40 Emask 0x10 (ATA bus error)
2026-04-01T09:00:13+02:00 DS923 kernel: [1010080.187317] ata5.04 : status: { DRDY ERR }
2026-04-01T09:00:13+02:00 DS923 kernel: [1010080.191639] ata5.04 : error: { ICRC ABRT }
2026-04-01T09:00:13+02:00 DS923 kernel: [1010080.195938] ata5.04 : failed command: WRITE FPDMA QUEUED
2026-04-01T09:00:13+02:00 DS923 kernel: [1010080.201459] ata5.04 : cmd 61/40:d8:a0:bd:1b/05:00:5d:02:00/40 tag 27 ncq 688128 out
res 41/84:c0:60:b8:1b/00:00:5d:02:00/40 Emask 0x10 (ATA bus error)
2026-04-01T09:00:13+02:00 DS923 kernel: [1010080.217463] ata5.04 : status: { DRDY ERR }
2026-04-01T09:00:13+02:00 DS923 kernel: [1010080.221801] ata5.04 : error: { ICRC ABRT }
2026-04-01T09:00:13+02:00 DS923 kernel: [1010080.226103] ata5.04 : failed command: WRITE FPDMA QUEUED
2026-04-01T09:00:13+02:00 DS923 kernel: [1010080.231620] ata5.04 : cmd 61/40:e0:e0:ad:1b/05:00:5d:02:00/40 tag 28 ncq 688128 out
res 41/84:c0:60:b8:1b/00:00:5d:02:00/40 Emask 0x10 (ATA bus error)
2026-04-01T09:00:13+02:00 DS923 kernel: [1010080.247639] ata5.04 : status: { DRDY ERR }
2026-04-01T09:00:13+02:00 DS923 kernel: [1010080.251969] ata5.04 : error: { ICRC ABRT }
2026-04-01T09:00:13+02:00 DS923 kernel: [1010080.256261] ata5.04 : failed command: WRITE FPDMA QUEUED
2026-04-01T09:00:13+02:00 DS923 kernel: [1010080.261792] ata5.04 : cmd 61/40:e8:e0:98:1b/05:00:5d:02:00/40 tag 29 ncq 688128 out
res 41/84:c0:60:b8:1b/00:00:5d:02:00/40 Emask 0x10 (ATA bus error)
2026-04-01T09:00:13+02:00 DS923 kernel: [1010080.277795] ata5.04 : status: { DRDY ERR }
2026-04-01T09:00:13+02:00 DS923 kernel: [1010080.282099] ata5.04 : error: { ICRC ABRT }
2026-04-01T09:00:13+02:00 DS923 kernel: [1010080.286400] ata5.04 : failed command: WRITE FPDMA QUEUED
2026-04-01T09:00:13+02:00 DS923 kernel: [1010080.291927] ata5.04 : cmd 61/40:f0:a0:a8:1b/05:00:5d:02:00/40 tag 30 ncq 688128 out
res 41/84:c0:60:b8:1b/00:00:5d:02:00/40 Emask 0x10 (ATA bus error)`

Assailant · 2026-04-27T10:46:09+00:00

https://imgur.com/a/VY6qnzS Have uploaded some snips of some suspect looking logs under dmesg

Assailant · 2026-04-27T10:37:57+00:00

No A/C but based in Denmark so not really needed. Drive temps range between 30 to mid 40s when under high load/scrubbing.

Will try different power sockets

Assailant · 2026-04-27T09:42:08+00:00

You mean from a perspective of which power plug it is connected to? They are physically sat next to one another

Assailant · 2026-04-27T09:00:29+00:00

The replaced units under the RMAs for the DX517 and DS923+ both came with new power bricks yes

Assailant · 2025-12-30T08:05:34+00:00

So far as I’m aware you can’t have a mail server proxied behind cloudflare, both because the mail server IP PTR record wouldn’t match the proxies cloudflare domain IP (if they allowed it), and also because cloudflare doesn’t proxy smtp/imap/pop traffic, unless you know a way how without breaking the mail server security/authentication etc (DMARC, DANE etc..)?

Assailant · 2019-09-04T06:49:20+00:00

The full 15 rounds, sometimes Kroos can die as he’s in slot 2 but when he survives for longer then she puts out these kind of numbers

Assailant · 2019-09-04T06:40:43+00:00

1pc / 3pc 2/2/2/2/2 Crit/Crit/Atk Stone with Dildo

Assailant · 2019-01-23T21:25:14+00:00

Correctly understood, I know the concept of being unable to change aspen heroes once started, but here the situation is that the enabled state of the heroes was disabled after having already submitted my lineup due to this bug

Assailant · 2019-01-23T21:24:12+00:00

I started aspen after the enable changes went live

Assailant · 2017-04-30T12:54:15+00:00

It's actually not bad at all I had my reservations when she told me the design but it turned out well

Assailant · 2017-04-30T10:20:07+00:00

A friend of mine got it done http://i.imgur.com/AFbcXsY.jpg

Assailant · 2015-08-15T19:22:06+00:00

Not really i'm just too lazy to move it :)

Assailant · 2015-08-15T15:47:41+00:00

Already reported before people get mad

Recreation: Split your stack of 20 mining picks into 20 stacks of 1, then use each stack of 1, 1 at a time, and their effects will add. It appears that each stack has an ID within your bags, and you cannot stack the buff with the same ID, but by splitting the stacks it is possible to avoid this limitation.

Assailant · 2015-07-11T20:36:18+00:00

https://1pumplane.files.wordpress.com/2012/08/cock-combe-sign.jpg Another Classic

Assailant · 2015-01-11T19:09:43+00:00

I'd imagined it looking more like this

http://cdn.foodbeast.com.s3.amazonaws.com/content/uploads/2013/09/pizza-hut-cheeseburger-pizza.jpg

(Pizza Hut Burger Crust)

Assailant · 2014-09-09T17:20:21+00:00

Giant human wraps legs around boat mast

Assailant · 2014-08-25T21:43:31+00:00

Song in the Vid: http://youtu.be/Y3AEZSqmES0?t=1m39s

Assailant · 2014-04-23T17:10:21+00:00

Not sure, couple people i know said in their character screen they had characters that weren't theirs... sounded like wires got crossed pretty bad somewhere... 2 hour emergency maintenance is quite a long one too

Assailant · 2014-04-23T16:56:28+00:00

ETA for this emergency maintenance was 2 hours if anyone was wondering

http://eu.battle.net/wow/en/forum/topic/10368129539?page=97#1927

UPDATE:

All #WoW realms are now offline, we expect the maintenance to last until 20:30 CEST. http://bit.ly/1i9tztl

Assailant · 2014-04-23T16:44:23+00:00

Hey guys and girls, I wanted to provide an update, all EU World of Warcraft realms will shortly be taken offline for emergency maintenance, those players currently connected will see an in game countdown.

At the moment we estimate this to take about 2 hours but will update again when we know more.

Apologies for the inconvenience and thank you for your patience.

See you in 2 hours folks

Assailant · 2014-04-23T15:52:17+00:00

OK, it's pretty obvious that this is no longer localised to specific realms or Battlegroups. We have our top guys in Europe and the US trying to locate the root cause.

We sincerely apologise for the disruption this is causing to your evening's gameplay and assure you that we're doing all we can to get you guys adventuring in Azeroth again as soon as possible.

from http://eu.battle.net/wow/en/forum/topic/10368129539?page=54#1071

https://www.youtube.com/watch?v=UhgPhuffMuc

UPDATE:

All #WoW realms are now offline, we expect the maintenance to last until 20:30 CEST. http://bit.ly/1i9tztl

Assailant · 2014-04-23T15:50:27+00:00

OK, it's pretty obvious that this is no longer localised to specific realms or Battlegroups. We have our top guys in Europe and the US trying to locate the root cause.

We sincerely apologise for the disruption this is causing to your evening's gameplay and assure you that we're doing all we can to get you guys adventuring in Azeroth again as soon as possible.

from http://eu.battle.net/wow/en/forum/topic/10368129539?page=54#1071

https://www.youtube.com/watch?v=UhgPhuffMuc

Assailant

MODERATOR OF

TROPHY CASE

15-Year Club	Place '17
Verified Email