Unable to make Roon work on QNAP HS-453DX 8GB

@dylan

Okay, switching to my PC. But that isn’t running 24/7.

I’ll let it import the library and connect to Tidal, switch of for the weekend and report back next week.

Is there anything you want me to do? I’ll try to crash Roon as before. :wink:

Edit: 1st thing I notice is Chromecast not working. Unable to enable. The rest will have to wait.

Best regards

Hi @DPV,

Does it show up at all?

Any change if you temporarily disable firewall on the PC?

@dylan

Been away for a few days. When I switched on the PC, everything was fine. But nothing was done in the mean time. Chromecast was fine.

I did a new setup, factory settings and reinitialized the NAS, so a fresh start. The NAS is only a few months old and everything is brand new and QNAP compatible. Tried the setup wich Roon advises. Roon and database on a SSD and the library in a RAID on the HDD’s. Used one SSD for cache acceleration and used overprovisioning on both SSD’s. (encouraged by the fact the tests revealed no hardware failures)

QNAP issued a firmware update.

Played music from my library and TIDAL via QNAP HDMI/RAAT/Pioneer SC-LX58. Everything fine.
The problems started after a restart of the NAS, ending with lost storage. As a partner of QNAP and a advertisment companion, this looks like something on your side, QNAP and/or Roon.

So, because I’ve got nothing better to do (…), reinitialized the NAS one last time to set it up as a QTier (the NAS puts the system and apps on the SSD) and without overprovisioning as in @crieke his setup. The only thing I did since is removing the corrupted files from my library and loading the library. Roon is analyzing as we speak, no TIDAL yet.

Can you please take a look at the logs from just after the crash and the most recent from a few hours ago when everything is stil okay? It looks like a problem in the way/sequence QNAP shuts down Roon when busy. The same happened earlier after a manual back-up, so a restart of the core. Do you now if somebody else is using Roon with this NAS (HS-453DX 8GB)?

I can reach out to QNAP, but it looks like everything is working fine, except Roon. What do I ask them?

Still a lot of questions. This is my final attempt. I’m willing to help, you’ve build a beautifull program. Just not for this combi, it seems. And that was just what pushed me towards this NAS…

Best regards,

Dimitri

Edit: The new update is installed and because I’ve got a license for one device, the core is now again back on the NAS.

Edit2: In the System Resources app the RoonAppliance process is showing as a System Proces, after some installs it was grouped as a bunch of Roon Processes, with it’s own Roon icon.

1 Like

This behaviour is expected. If Roon Server is stopped and started (or updated) by the web ui, it is listed as a system process (because it is started by the apache web server). It should not have any side effects as it is still running with the same privileges.

I looked for the previous error in your newest log. It is still in there:

02/20 08:35:29 Critical: Library.EndMutation: LevelDb.Exception: Corruption: corrupted compressed block contents
  at LevelDb.Database._CheckError (System.IntPtr err) [0x00037] in <dbf120087cd44b7b920c7dc48eaa36c9>:0 
  at LevelDb.Database.Write (LevelDb.WriteBatch batch) [0x00050] in <dbf120087cd44b7b920c7dc48eaa36c9>:0 
  at LevelDb.Transaction.Commit (System.Boolean trace) [0x000f8] in <dbf120087cd44b7b920c7dc48eaa36c9>:0 
  at Sooloos.Broker.Music.MusicDatabase.Flush () [0x00101] in <35eecd34a6204c77b42e44a40369c4ea>:0 
  at Sooloos.Broker.Music.MusicDatabase.EndMutation () [0x00000] in <35eecd34a6204c77b42e44a40369c4ea>:0 
  at Sooloos.Broker.Music.Library.EndMutation () [0x0022d] in <35eecd34a6204c77b42e44a40369c4ea>:0 

I also noticed again lots of corrupt music files:

02/20 08:21:32 Warn: [storage] [directory] Failed to extract audio format from '/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Muziek/Various Artists/Top 2000 19 Jaar/0195 - Rowwen Hèze - Limburg (Kwestie Van Geduld).flac': CorruptFile
02/20 08:21:32 Warn: [storage] [directory] Failed to extract audio format from '/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Muziek/Various Artists/Top 2000 19 Jaar/0207 - Beatles - The Fool On The Hill.flac': CorruptFile
02/20 08:21:33 Warn: [storage] [directory] Failed to extract audio format from '/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Muziek/Various Artists/Top 2000 19 Jaar/0222 - Don Mclean - Vincent.flac': CorruptFile
02/20 08:21:34 Warn: [storage] [directory] Failed to extract audio format from '/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Muziek/Various Artists/Top 2000 19 Jaar/0254 - Iron Butterfly - In-A-Gadda-Da-Vida.flac': CorruptFile
02/20 08:21:35 Warn: [storage] [directory] Failed to extract audio format from '/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Muziek/Various Artists/Top 2000 19 Jaar/0267 - De Kast - In Nije Dei.flac': CorruptFile
02/20 08:21:40 Warn: [storage] [directory] Failed to extract audio format from '/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Muziek/Various Artists/Top 2000 19 Jaar/0357 - Frankie Goes To Hollywood - The Power Of Love.flac': CorruptFile
02/20 08:21:42 Warn: [storage] [directory] Failed to extract audio format from '/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Muziek/Various Artists/Top 2000 19 Jaar/0382 - Eagles - Lyin' Eyes.flac': CorruptFile
02/20 08:21:46 Warn: [storage] [directory] Failed to extract audio format from '/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Muziek/Various Artists/Top 2000 19 Jaar/0449 - Earth, Wind & Fire - September.flac': CorruptFile
02/20 08:21:49 Warn: [storage] [directory] Failed to extract audio format from '/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Muziek/Various Artists/Top 2000 19 Jaar/0475 - Nina Simone - Ain't Got No, I Got Life.flac': CorruptFile
02/20 08:21:51 Warn: [storage] [directory] Failed to extract audio format from '/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Muziek/Various Artists/Top 2000 19 Jaar/0500 - Abba - Fernando.flac': CorruptFile
02/20 08:21:59 Warn: [storage] [directory] Failed to extract audio format from '/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Muziek/Various Artists/Top 2000 19 Jaar/0588 - David Bowie - China Girl.flac': CorruptFile
02/20 08:22:01 Warn: [storage] [directory] Failed to extract audio format from '/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Muziek/Various Artists/Top 2000 19 Jaar/0617 - Barry Mcguire - Eve Of Destruction.flac': CorruptFile
02/20 08:32:42 Warn: [storage] [directory] Failed to extract audio format from '/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Muziek/Various Artists/Top 2000 19 Jaar/4128 - Lemon Pipers - Green Tambourine.flac': CorruptFile

I am currently wondering, if your music files really contains that many corrupted files or if these get corrupted as well… :thinking:

Would it be possible to check if Roon Server works fine, without your local files (only setup TIDAL or Qobuz). If this works, without new corruption to the Roon Server database, it’ll give a hint where to look. You could afterwards add music little by little back to the database.

1 Like

@crieke

Thanks for looking. Can you tell me what you see in the first part of the log you copied? I’m a user not a develloper.

I deleted the corrupt files. They all came from the same import and didn’t show any meta-data, unlike the rest. Question: if I disable the storage location, will that be sufficient and will Roon have to analyze all songs again?

Other strange behavior: 16318 Tracks imported and analysis is counting on both sides 12898/20521 as we speak. :thinking: And don’t forget, I didn’t do anything yet with any Roonremote but initiate everything.

Thanks,

Dimitri

Sorry Dimitri, I was not very specific regarding the posted error message in my previous post. It is the same error as your logs showed before and indicate (again) a corrupt database. :frowning:

My suggestions was, to stop Roon Server, delete the database again and start over with only streaming services (the music files can remain on the NAS, but don’t add them in the storage settings of Roon yet). If this causes no issues, I’d add some music, then add some more until issues reoccur…

I have not heard of issues in general with the HS-453DX model. If I remember correctly QNAP also used this model in Munich at the Audio High End exhibition in May last year.

Hi @DPV,

As we mentioned before, it’s looking like there is specific to this hardware that is causing the issue we’re seeing here, but the test that @crieke mentioned above is definitely a good suggestion:

This would help to rule out any potential issues stemming from the media on the drive.

@dylan @crieke

Contacted QNAP. Send my logs to them and I’m running all the tests and checks available in their environment.

Waiting for the feedback.

After the checks, I’ll run Roon without local files.

Thanks for the update, @DPV — Let us know what QNAP says!

@dylan @crieke

This is what I’ve got so far. No reply from QNAP yet.

Installed everything again. Two storage pools, one SSD, one HDD. Both in RAID1. The Roon core didn’t see NAS audio output, did a re-install from the Roon app (little package icon) and thereafter no audio devices where founs at all… Only TIDAL connected.


It just doesn’t make sense. The rest is working fine.

Hi Dimitri,
This time there are no signs of database corruption in the logs.
The issue of no audio devices seem to be caused by missing ALSA libraries.
These are bundled with the Qnap system software.
I just made a small change to the qpkg to better cope with this situation. I’ll send you a link via pm.

1 Like

Hi @crieke and @dylan,

(I haven’t used your qpkg Christopher)

Same problem occurs with only Tidal connected.

The audio devices reappeared and I played Tidal yesterday, a few hours no problems. Stopped Roon. Went to bed. Left the NAS on.

This morning Started Roon, worked fine. After one song did a restart of the NAS and lost Roon again. I could connect with the core, but that’s it, nothing else. No overview, no Tidal. Wen I switch to the album page, the storage location warning appears again. The restart messes everything up.

Hope this helps a bit.

Best regards,

Dimitri

Edit: when I remove and install Roon, with the same (untouched) RoonServer folder, the problem is still there. I need to remove the (contents of the) RoonServer folder to make it work again. Maybe that’s why I’m unable to put back a back-up.

Hi Dimitri,
the error from previous logs is back in the log files. :frowning:

I took a look at the QNAP logs, you’ve provided yesterday. Found several data errors there. I am not an expert in this area, but I’d advise to wait for the Qnap team to take a look.
(I also looked at my own Qnap logs for comparison and could not find any of these here…)

QNAP system logs
<3>[29383.692552] ata2.00: irq_stat 0x08000000, interface fatal error
<4>[29383.698656] ata_issue_link_err_event:(1:0:0:0)
<3>[29383.698659] ata2: SError: { UnrecovData Handshk }
<3>[29383.707979] ata2.00: failed command: WRITE FPDMA QUEUED
<3>[29383.713262] ata2.00: cmd 61/00:00:88:93:4f/04:00:14:00:00/40 tag 0 ncq dma 524288 out
<3>[29383.713262]          res 40/00:0c:88:97:4f/00:00:14:00:00/40 Emask 0x10 (ATA bus error)
<3>[29383.729140] ata2.00: status: { DRDY }
<3>[29383.732826] ata2.00: failed command: WRITE FPDMA QUEUED
<3>[29383.738078] ata2.00: cmd 61/00:08:88:97:4f/04:00:14:00:00/40 tag 1 ncq dma 524288 out
<3>[29383.738078]          res 40/00:0c:88:97:4f/00:00:14:00:00/40 Emask 0x10 (ATA bus error)
<3>[29383.753935] ata2.00: status: { DRDY }
<3>[29383.757623] ata2.00: failed command: WRITE FPDMA QUEUED
<3>[29383.762877] ata2.00: cmd 61/00:e8:88:8b:4f/04:00:14:00:00/40 tag 29 ncq dma 524288 out
<3>[29383.762877]          res 40/00:0c:88:97:4f/00:00:14:00:00/40 Emask 0x10 (ATA bus error)
<3>[29383.778825] ata2.00: status: { DRDY }
<3>[29383.782512] ata2.00: failed command: WRITE FPDMA QUEUED
<3>[29383.787765] ata2.00: cmd 61/00:f0:88:8f:4f/04:00:14:00:00/40 tag 30 ncq dma 524288 out
<3>[29383.787765]          res 40/00:0c:88:97:4f/00:00:14:00:00/40 Emask 0x10 (ATA bus error)
<3>[29383.803709] ata2.00: status: { DRDY }
<6>[29383.807396] ata2: hard resetting link
<4>[29383.811092] ata2: Found Burst Error 400100 at 4324051106. cur_index 0
<6>[29384.280155] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
<6>[29384.289402] ata2.00: configured for UDMA/133
<6>[29384.293771] ata2: EH complete
<4>[29384.298851] Check proc_name[ahci].
<3>[29897.330319] ata1.00: exception Emask 0x0 SAct 0x6fffffff SErr 0x0 action 0x0
<3>[29897.337407] ata1.00: irq_stat 0x40000001
<4>[29897.341365] ata_issue_link_err_event:(0:0:0:0)
<3>[29897.341368] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.351096] ata1.00: cmd 61/00:00:88:93:0c/04:00:15:00:00/40 tag 0 ncq dma 524288 out
<3>[29897.351096]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.366808] ata1.00: status: { DRDY ERR }
<3>[29897.370854] ata1.00: error: { ABRT }
<3>[29897.374455] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.379719] ata1.00: cmd 61/00:08:88:97:0c/04:00:15:00:00/40 tag 1 ncq dma 524288 out
<3>[29897.379719]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.395409] ata1.00: status: { DRDY ERR }
<3>[29897.399450] ata1.00: error: { ABRT }
<3>[29897.403052] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.408308] ata1.00: cmd 61/00:10:88:9b:0c/04:00:15:00:00/40 tag 2 ncq dma 524288 out
<3>[29897.408308]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.424005] ata1.00: status: { DRDY ERR }
<3>[29897.428046] ata1.00: error: { ABRT }
<3>[29897.431655] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.436920] ata1.00: cmd 61/00:18:88:9f:0c/04:00:15:00:00/40 tag 3 ncq dma 524288 out
<3>[29897.436920]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.452619] ata1.00: status: { DRDY ERR }
<3>[29897.456663] ata1.00: error: { ABRT }
<3>[29897.460264] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.465529] ata1.00: cmd 61/00:20:88:a3:0c/04:00:15:00:00/40 tag 4 ncq dma 524288 out
<3>[29897.465529]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.481255] ata1.00: status: { DRDY ERR }
<3>[29897.485287] ata1.00: error: { ABRT }
<3>[29897.488885] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.494133] ata1.00: cmd 61/00:28:88:a7:0c/04:00:15:00:00/40 tag 5 ncq dma 524288 out
<3>[29897.494133]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.509823] ata1.00: status: { DRDY ERR }
<3>[29897.513857] ata1.00: error: { ABRT }
<3>[29897.517451] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.522702] ata1.00: cmd 61/00:30:88:ab:0c/04:00:15:00:00/40 tag 6 ncq dma 524288 out
<3>[29897.522702]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.538386] ata1.00: status: { DRDY ERR }
<3>[29897.542418] ata1.00: error: { ABRT }
<3>[29897.546017] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.551280] ata1.00: cmd 61/00:38:88:af:0c/04:00:15:00:00/40 tag 7 ncq dma 524288 out
<3>[29897.551280]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.566971] ata1.00: status: { DRDY ERR }
<3>[29897.571004] ata1.00: error: { ABRT }
<3>[29897.574603] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.579860] ata1.00: cmd 61/00:40:88:b3:0c/04:00:15:00:00/40 tag 8 ncq dma 524288 out
<3>[29897.579860]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.595556] ata1.00: status: { DRDY ERR }
<3>[29897.599594] ata1.00: error: { ABRT }
<3>[29897.603193] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.608456] ata1.00: cmd 61/00:48:88:b7:0c/04:00:15:00:00/40 tag 9 ncq dma 524288 out
<3>[29897.608456]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.624146] ata1.00: status: { DRDY ERR }
<3>[29897.628179] ata1.00: error: { ABRT }
<3>[29897.631773] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.637026] ata1.00: cmd 61/00:50:88:bb:0c/04:00:15:00:00/40 tag 10 ncq dma 524288 out
<3>[29897.637026]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.652803] ata1.00: status: { DRDY ERR }
<3>[29897.656864] ata1.00: error: { ABRT }
<3>[29897.660472] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.665732] ata1.00: cmd 61/00:58:88:bf:0c/04:00:15:00:00/40 tag 11 ncq dma 524288 out
<3>[29897.665732]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.681542] ata1.00: status: { DRDY ERR }
<3>[29897.685582] ata1.00: error: { ABRT }
<3>[29897.689184] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.694441] ata1.00: cmd 61/00:60:88:c3:0c/04:00:15:00:00/40 tag 12 ncq dma 524288 out
<3>[29897.694441]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.710225] ata1.00: status: { DRDY ERR }
<3>[29897.714266] ata1.00: error: { ABRT }
<3>[29897.717871] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.723131] ata1.00: cmd 61/00:68:88:c7:0c/04:00:15:00:00/40 tag 13 ncq dma 524288 out
<3>[29897.723131]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.738931] ata1.00: status: { DRDY ERR }
<3>[29897.742969] ata1.00: error: { ABRT }
<3>[29897.746565] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.751817] ata1.00: cmd 61/00:70:88:cb:0c/04:00:15:00:00/40 tag 14 ncq dma 524288 out
<3>[29897.751817]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.767617] ata1.00: status: { DRDY ERR }
<3>[29897.771651] ata1.00: error: { ABRT }
<3>[29897.775265] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.780529] ata1.00: cmd 61/00:78:88:cf:0c/04:00:15:00:00/40 tag 15 ncq dma 524288 out
<3>[29897.780529]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.796361] ata1.00: status: { DRDY ERR }
<3>[29897.800398] ata1.00: error: { ABRT }
<3>[29897.803997] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.809256] ata1.00: cmd 61/00:80:88:d3:0c/04:00:15:00:00/40 tag 16 ncq dma 524288 out
<3>[29897.809256]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.825038] ata1.00: status: { DRDY ERR }
<3>[29897.829075] ata1.00: error: { ABRT }
<3>[29897.832675] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.837925] ata1.00: cmd 61/00:88:88:d7:0c/04:00:15:00:00/40 tag 17 ncq dma 524288 out
<3>[29897.837925]          res 41/04:00:88:d7:0c/00:04:15:00:00/40 Emask 0x401 (device error) <F>
<3>[29897.854220] ata1.00: status: { DRDY ERR }
<3>[29897.858281] ata1.00: error: { ABRT }
<3>[29897.861881] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.867134] ata1.00: cmd 61/00:90:88:db:0c/04:00:15:00:00/40 tag 18 ncq dma 524288 out
<3>[29897.867134]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.882917] ata1.00: status: { DRDY ERR }
<3>[29897.886951] ata1.00: error: { ABRT }
<3>[29897.890547] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.895796] ata1.00: cmd 61/00:98:88:df:0c/04:00:15:00:00/40 tag 19 ncq dma 524288 out
<3>[29897.895796]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.911568] ata1.00: status: { DRDY ERR }
<3>[29897.915601] ata1.00: error: { ABRT }
<3>[29897.919210] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.924459] ata1.00: cmd 61/00:a0:88:e3:0c/04:00:15:00:00/40 tag 20 ncq dma 524288 out
<3>[29897.924459]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.940232] ata1.00: status: { DRDY ERR }
<3>[29897.944273] ata1.00: error: { ABRT }
<3>[29897.947875] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.953127] ata1.00: cmd 61/00:a8:88:e7:0c/04:00:15:00:00/40 tag 21 ncq dma 524288 out
<3>[29897.953127]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.968932] ata1.00: status: { DRDY ERR }
<3>[29897.972973] ata1.00: error: { ABRT }
<3>[29897.976597] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.981857] ata1.00: cmd 61/00:b0:88:eb:0c/04:00:15:00:00/40 tag 22 ncq dma 524288 out
<3>[29897.981857]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.997632] ata1.00: status: { DRDY ERR }
<3>[29898.001666] ata1.00: error: { ABRT }
<3>[29898.005276] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29898.010541] ata1.00: cmd 61/00:b8:88:ef:0c/04:00:15:00:00/40 tag 23 ncq dma 524288 out
<3>[29898.010541]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29898.026321] ata1.00: status: { DRDY ERR }
<3>[29898.030356] ata1.00: error: { ABRT }
<3>[29898.033950] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29898.039204] ata1.00: cmd 61/00:c0:88:f3:0c/04:00:15:00:00/40 tag 24 ncq dma 524288 out
<3>[29898.039204]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29898.054981] ata1.00: status: { DRDY ERR }
<3>[29898.059022] ata1.00: error: { ABRT }
<3>[29898.062630] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29898.067896] ata1.00: cmd 61/00:c8:88:f7:0c/04:00:15:00:00/40 tag 25 ncq dma 524288 out
<3>[29898.067896]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29898.083667] ata1.00: status: { DRDY ERR }
<3>[29898.087710] ata1.00: error: { ABRT }
<3>[29898.091312] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29898.096562] ata1.00: cmd 61/00:d0:88:fb:0c/04:00:15:00:00/40 tag 26 ncq dma 524288 out
<3>[29898.096562]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29898.112346] ata1.00: status: { DRDY ERR }
<3>[29898.116385] ata1.00: error: { ABRT }
<3>[29898.119980] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29898.125230] ata1.00: cmd 61/00:d8:88:ff:0c/04:00:15:00:00/40 tag 27 ncq dma 524288 out
<3>[29898.125230]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29898.141009] ata1.00: status: { DRDY ERR }
<3>[29898.145042] ata1.00: error: { ABRT }
<3>[29898.148650] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29898.153905] ata1.00: cmd 61/00:e8:88:8b:0c/04:00:15:00:00/40 tag 29 ncq dma 524288 out
<3>[29898.153905]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29898.169674] ata1.00: status: { DRDY ERR }
<3>[29898.173706] ata1.00: error: { ABRT }
<3>[29898.177308] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29898.182560] ata1.00: cmd 61/00:f0:88:8f:0c/04:00:15:00:00/40 tag 30 ncq dma 524288 out
<3>[29898.182560]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29898.198335] ata1.00: status: { DRDY ERR }
<3>[29898.202376] ata1.00: error: { ABRT }
<6>[29898.213757] ata1.00: configured for UDMA/133
<6>[29898.218180] ata1: EH complete
<4>[29898.224189] Check proc_name[ahci].
<3>[31336.816337] ata1.00: exception Emask 0x0 SAct 0x7f81ffff SErr 0x0 action 0x0
<3>[31336.823450] ata1.00: irq_stat 0x40000001
<4>[31336.827411] ata_issue_link_err_event:(0:0:0:0)
<3>[31336.827415] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31336.837156] ata1.00: cmd 61/08:00:d8:03:bc/00:00:13:00:00/40 tag 0 ncq dma 4096 out
<3>[31336.837156]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31336.852685] ata1.00: status: { DRDY ERR }
<3>[31336.856722] ata1.00: error: { ABRT }
<3>[31336.860324] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31336.865579] ata1.00: cmd 61/08:08:30:04:bc/00:00:13:00:00/40 tag 1 ncq dma 4096 out
<3>[31336.865579]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31336.881093] ata1.00: status: { DRDY ERR }
<3>[31336.885126] ata1.00: error: { ABRT }
<3>[31336.888723] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31336.893972] ata1.00: cmd 61/08:10:50:04:bc/00:00:13:00:00/40 tag 2 ncq dma 4096 out
<3>[31336.893972]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31336.909483] ata1.00: status: { DRDY ERR }
<3>[31336.913514] ata1.00: error: { ABRT }
<3>[31336.917113] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31336.922362] ata1.00: cmd 61/10:18:b0:85:bb/00:00:13:00:00/40 tag 3 ncq dma 8192 out
<3>[31336.922362]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31336.937878] ata1.00: status: { DRDY ERR }
<3>[31336.941907] ata1.00: error: { ABRT }
<3>[31336.945509] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31336.950762] ata1.00: cmd 61/10:20:d8:85:bb/00:00:13:00:00/40 tag 4 ncq dma 8192 out
<3>[31336.950762]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31336.966278] ata1.00: status: { DRDY ERR }
<3>[31336.970306] ata1.00: error: { ABRT }
<3>[31336.973915] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31336.979165] ata1.00: cmd 61/08:28:28:8e:bb/00:00:13:00:00/40 tag 5 ncq dma 4096 out
<3>[31336.979165]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31336.994672] ata1.00: status: { DRDY ERR }
<3>[31336.998722] ata1.00: error: { ABRT }
<3>[31337.002317] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31337.007567] ata1.00: cmd 61/10:30:40:8e:bb/00:00:13:00:00/40 tag 6 ncq dma 8192 out
<3>[31337.007567]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31337.023074] ata1.00: status: { DRDY ERR }
<3>[31337.027105] ata1.00: error: { ABRT }
<3>[31337.030708] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31337.035965] ata1.00: cmd 61/10:38:68:8e:bb/00:00:13:00:00/40 tag 7 ncq dma 8192 out
<3>[31337.035965]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31337.051476] ata1.00: status: { DRDY ERR }
<3>[31337.055533] ata1.00: error: { ABRT }
<3>[31337.059130] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31337.064379] ata1.00: cmd 61/08:40:f8:8e:bb/00:00:13:00:00/40 tag 8 ncq dma 4096 out
<3>[31337.064379]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31337.079900] ata1.00: status: { DRDY ERR }
<3>[31337.083936] ata1.00: error: { ABRT }
<3>[31337.087545] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31337.092806] ata1.00: cmd 61/10:48:a8:9b:bb/00:00:13:00:00/40 tag 9 ncq dma 8192 out
<3>[31337.092806]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31337.108317] ata1.00: status: { DRDY ERR }
<3>[31337.112353] ata1.00: error: { ABRT }
<3>[31337.115953] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31337.121202] ata1.00: cmd 61/08:50:e8:3c:bc/00:00:13:00:00/40 tag 10 ncq dma 4096 out
<3>[31337.121202]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31337.136801] ata1.00: status: { DRDY ERR }
<3>[31337.140830] ata1.00: error: { ABRT }
<3>[31337.144432] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31337.149684] ata1.00: cmd 61/10:58:b0:53:bc/00:00:13:00:00/40 tag 11 ncq dma 8192 out
<3>[31337.149684]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31337.165281] ata1.00: status: { DRDY ERR }
<3>[31337.169307] ata1.00: error: { ABRT }
<3>[31337.172904] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31337.178159] ata1.00: cmd 61/10:60:18:54:bc/00:00:13:00:00/40 tag 12 ncq dma 8192 out
<3>[31337.178159]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31337.193765] ata1.00: status: { DRDY ERR }
<3>[31337.197804] ata1.00: error: { ABRT }
<3>[31337.201403] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31337.206654] ata1.00: cmd 61/28:68:38:54:bc/00:00:13:00:00/40 tag 13 ncq dma 20480 out
<3>[31337.206654]          res 41/04:28:38:54:bc/00:00:13:00:00/40 Emask 0x401 (device error) <F>
<3>[31337.222863] ata1.00: status: { DRDY ERR }
<3>[31337.226896] ata1.00: error: { ABRT }
<3>[31337.230493] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31337.235748] ata1.00: cmd 61/08:70:68:54:bc/00:00:13:00:00/40 tag 14 ncq dma 4096 out
<3>[31337.235748]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31337.251346] ata1.00: status: { DRDY ERR }
<3>[31337.255378] ata1.00: error: { ABRT }
<3>[31337.258975] ata1.00: failed command: READ FPDMA QUEUED
<3>[31337.264139] ata1.00: cmd 60/10:78:28:21:48/00:00:01:00:00/40 tag 15 ncq dma 8192 in
<3>[31337.264139]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31337.279653] ata1.00: status: { DRDY ERR }
<3>[31337.283686] ata1.00: error: { ABRT }
<3>[31337.287286] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31337.292551] ata1.00: cmd 61/08:80:60:76:7c/00:00:09:00:00/40 tag 16 ncq dma 4096 out
<3>[31337.292551]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31337.308153] ata1.00: status: { DRDY ERR }
<3>[31337.312186] ata1.00: error: { ABRT }
<3>[31337.315783] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31337.321036] ata1.00: cmd 61/10:b8:58:8f:5f/00:00:09:00:00/40 tag 23 ncq dma 8192 out
<3>[31337.321036]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31337.336640] ata1.00: status: { DRDY ERR }
<3>[31337.340668] ata1.00: error: { ABRT }
<3>[31337.344272] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31337.349526] ata1.00: cmd 61/08:c0:a8:8f:5f/00:00:09:00:00/40 tag 24 ncq dma 4096 out
<3>[31337.349526]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31337.365129] ata1.00: status: { DRDY ERR }
<3>[31337.369164] ata1.00: error: { ABRT }
<3>[31337.372785] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31337.378034] ata1.00: cmd 61/08:c8:c8:51:76/00:00:09:00:00/40 tag 25 ncq dma 4096 out
<3>[31337.378034]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31337.393633] ata1.00: status: { DRDY ERR }
<3>[31337.397667] ata1.00: error: { ABRT }
<3>[31337.401265] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31337.406513] ata1.00: cmd 61/08:d0:98:44:77/00:00:09:00:00/40 tag 26 ncq dma 4096 out
<3>[31337.406513]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31337.422112] ata1.00: status: { DRDY ERR }
<3>[31337.426143] ata1.00: error: { ABRT }
<3>[31337.429740] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31337.434995] ata1.00: cmd 61/08:d8:a0:d0:77/00:00:09:00:00/40 tag 27 ncq dma 4096 out
<3>[31337.434995]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31337.450594] ata1.00: status: { DRDY ERR }
<3>[31337.454630] ata1.00: error: { ABRT }
<3>[31337.458228] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31337.463482] ata1.00: cmd 61/08:e0:70:4e:b6/00:00:13:00:00/40 tag 28 ncq dma 4096 out
<3>[31337.463482]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31337.479080] ata1.00: status: { DRDY ERR }
<3>[31337.483113] ata1.00: error: { ABRT }
<3>[31337.486716] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31337.491975] ata1.00: cmd 61/08:e8:48:55:b6/00:00:13:00:00/40 tag 29 ncq dma 4096 out
<3>[31337.491975]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31337.507573] ata1.00: status: { DRDY ERR }
<3>[31337.511604] ata1.00: error: { ABRT }
<3>[31337.515200] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31337.520467] ata1.00: cmd 61/40:f0:50:27:b9/00:00:13:00:00/40 tag 30 ncq dma 32768 out
<3>[31337.520467]          res 41/04:fa:27:49:5f/00:ff:09:00:00/40 Emask 0x1 (device error)
<3>[31337.536159] ata1.00: status: { DRDY ERR }
<3>[31337.540194] ata1.00: error: { ABRT }
<6>[31337.551581] ata1.00: configured for UDMA/133
<6>[31337.555926] ata1: EH complete
<4>[31337.559178] Check proc_name[ahci].
<3>[31344.338173] ata1.00: exception Emask 0x10 SAct 0x4000000 SErr 0x400100 action 0x6 frozen
<3>[31344.346309] ata1.00: irq_stat 0x08000000, interface fatal error
<4>[31344.352279] ata_issue_link_err_event:(0:0:0:0)
<3>[31344.352283] ata1: SError: { UnrecovData Handshk }
<3>[31344.361490] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[31344.366758] ata1.00: cmd 61/08:d0:68:76:7c/00:00:09:00:00/40 tag 26 ncq dma 4096 out
<3>[31344.366758]          res 40/00:c4:18:fd:60/00:00:73:00:00/40 Emask 0x10 (ATA bus error)
<3>[31344.382537] ata1.00: status: { DRDY }
<6>[31344.386231] ata1: hard resetting link
<4>[31344.389935] ata1: Found Burst Error 400100 at 4326011685. cur_index 0
<6>[31344.856171] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
<6>[31344.865390] ata1.00: configured for UDMA/133
<6>[31344.869722] ata1: EH complete

Hi @DPV,

Thanks for the continued updates here. Since this error occurred even without any of your media added that rules out potential media corruption issues, so this is likely related to the hardware. Definitely let us know what QNAP says about this.

@dylan @crieke

Tomorrow the QNAP guy will remotly go into the NAS again, this time with me present at the other end. Till now no findings and he’s pointing (carefully) in your direction.

Can you please take a look at the last log_files. This time Roon looked very stable, but crashed after a WOL of the NAS. Since there was no stable moment for Roon.

Thanx.

Best regards,

Dimitri

Hi Dimitri,
please ask the QNAP support if these error messages in your QNAP log can be ignored. I have to admit, I am no expert in this area. But these got my attention, when I studied your QNAP logs:

SATA Errors
<3>[29383.684156] ata2.00: exception Emask 0x10 SAct 0x60000003 SErr 0x400100 action 0x6 frozen
<3>[29383.692552] ata2.00: irq_stat 0x08000000, interface fatal error
<4>[29383.698656] ata_issue_link_err_event:(1:0:0:0)
<3>[29383.698659] ata2: SError: { UnrecovData Handshk }
<3>[29383.707979] ata2.00: failed command: WRITE FPDMA QUEUED
<3>[29383.713262] ata2.00: cmd 61/00:00:88:93:4f/04:00:14:00:00/40 tag 0 ncq dma 524288 out
<3>[29383.713262]          res 40/00:0c:88:97:4f/00:00:14:00:00/40 Emask 0x10 (ATA bus error)
<3>[29383.729140] ata2.00: status: { DRDY }
<3>[29383.732826] ata2.00: failed command: WRITE FPDMA QUEUED
<3>[29383.738078] ata2.00: cmd 61/00:08:88:97:4f/04:00:14:00:00/40 tag 1 ncq dma 524288 out
<3>[29383.738078]          res 40/00:0c:88:97:4f/00:00:14:00:00/40 Emask 0x10 (ATA bus error)
<3>[29383.753935] ata2.00: status: { DRDY }
<3>[29383.757623] ata2.00: failed command: WRITE FPDMA QUEUED
<3>[29383.762877] ata2.00: cmd 61/00:e8:88:8b:4f/04:00:14:00:00/40 tag 29 ncq dma 524288 out
<3>[29383.762877]          res 40/00:0c:88:97:4f/00:00:14:00:00/40 Emask 0x10 (ATA bus error)
<3>[29383.778825] ata2.00: status: { DRDY }
<3>[29383.782512] ata2.00: failed command: WRITE FPDMA QUEUED
<3>[29383.787765] ata2.00: cmd 61/00:f0:88:8f:4f/04:00:14:00:00/40 tag 30 ncq dma 524288 out
<3>[29383.787765]          res 40/00:0c:88:97:4f/00:00:14:00:00/40 Emask 0x10 (ATA bus error)
<3>[29383.803709] ata2.00: status: { DRDY }
<6>[29383.807396] ata2: hard resetting link
<4>[29383.811092] ata2: Found Burst Error 400100 at 4324051106. cur_index 0
<6>[29384.280155] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
<6>[29384.289402] ata2.00: configured for UDMA/133
<6>[29384.293771] ata2: EH complete
<4>[29384.298851] Check proc_name[ahci].
<3>[29897.330319] ata1.00: exception Emask 0x0 SAct 0x6fffffff SErr 0x0 action 0x0
<3>[29897.337407] ata1.00: irq_stat 0x40000001
<4>[29897.341365] ata_issue_link_err_event:(0:0:0:0)
<3>[29897.341368] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.351096] ata1.00: cmd 61/00:00:88:93:0c/04:00:15:00:00/40 tag 0 ncq dma 524288 out
<3>[29897.351096]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.366808] ata1.00: status: { DRDY ERR }
<3>[29897.370854] ata1.00: error: { ABRT }
<3>[29897.374455] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.379719] ata1.00: cmd 61/00:08:88:97:0c/04:00:15:00:00/40 tag 1 ncq dma 524288 out
<3>[29897.379719]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.395409] ata1.00: status: { DRDY ERR }
<3>[29897.399450] ata1.00: error: { ABRT }
<3>[29897.403052] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.408308] ata1.00: cmd 61/00:10:88:9b:0c/04:00:15:00:00/40 tag 2 ncq dma 524288 out
<3>[29897.408308]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.424005] ata1.00: status: { DRDY ERR }
<3>[29897.428046] ata1.00: error: { ABRT }
<3>[29897.431655] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.436920] ata1.00: cmd 61/00:18:88:9f:0c/04:00:15:00:00/40 tag 3 ncq dma 524288 out
<3>[29897.436920]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.452619] ata1.00: status: { DRDY ERR }
<3>[29897.456663] ata1.00: error: { ABRT }
<3>[29897.460264] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.465529] ata1.00: cmd 61/00:20:88:a3:0c/04:00:15:00:00/40 tag 4 ncq dma 524288 out
<3>[29897.465529]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.481255] ata1.00: status: { DRDY ERR }
<3>[29897.485287] ata1.00: error: { ABRT }
<3>[29897.488885] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.494133] ata1.00: cmd 61/00:28:88:a7:0c/04:00:15:00:00/40 tag 5 ncq dma 524288 out
<3>[29897.494133]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.509823] ata1.00: status: { DRDY ERR }
<3>[29897.513857] ata1.00: error: { ABRT }
<3>[29897.517451] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.522702] ata1.00: cmd 61/00:30:88:ab:0c/04:00:15:00:00/40 tag 6 ncq dma 524288 out
<3>[29897.522702]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.538386] ata1.00: status: { DRDY ERR }
<3>[29897.542418] ata1.00: error: { ABRT }
<3>[29897.546017] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.551280] ata1.00: cmd 61/00:38:88:af:0c/04:00:15:00:00/40 tag 7 ncq dma 524288 out
<3>[29897.551280]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.566971] ata1.00: status: { DRDY ERR }
<3>[29897.571004] ata1.00: error: { ABRT }
<3>[29897.574603] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.579860] ata1.00: cmd 61/00:40:88:b3:0c/04:00:15:00:00/40 tag 8 ncq dma 524288 out
<3>[29897.579860]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.595556] ata1.00: status: { DRDY ERR }
<3>[29897.599594] ata1.00: error: { ABRT }
<3>[29897.603193] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.608456] ata1.00: cmd 61/00:48:88:b7:0c/04:00:15:00:00/40 tag 9 ncq dma 524288 out
<3>[29897.608456]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.624146] ata1.00: status: { DRDY ERR }
<3>[29897.628179] ata1.00: error: { ABRT }
<3>[29897.631773] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.637026] ata1.00: cmd 61/00:50:88:bb:0c/04:00:15:00:00/40 tag 10 ncq dma 524288 out
<3>[29897.637026]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.652803] ata1.00: status: { DRDY ERR }
<3>[29897.656864] ata1.00: error: { ABRT }
<3>[29897.660472] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.665732] ata1.00: cmd 61/00:58:88:bf:0c/04:00:15:00:00/40 tag 11 ncq dma 524288 out
<3>[29897.665732]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.681542] ata1.00: status: { DRDY ERR }
<3>[29897.685582] ata1.00: error: { ABRT }
<3>[29897.689184] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.694441] ata1.00: cmd 61/00:60:88:c3:0c/04:00:15:00:00/40 tag 12 ncq dma 524288 out
<3>[29897.694441]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.710225] ata1.00: status: { DRDY ERR }
<3>[29897.714266] ata1.00: error: { ABRT }
<3>[29897.717871] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.723131] ata1.00: cmd 61/00:68:88:c7:0c/04:00:15:00:00/40 tag 13 ncq dma 524288 out
<3>[29897.723131]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.738931] ata1.00: status: { DRDY ERR }
<3>[29897.742969] ata1.00: error: { ABRT }
<3>[29897.746565] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.751817] ata1.00: cmd 61/00:70:88:cb:0c/04:00:15:00:00/40 tag 14 ncq dma 524288 out
<3>[29897.751817]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.767617] ata1.00: status: { DRDY ERR }
<3>[29897.771651] ata1.00: error: { ABRT }
<3>[29897.775265] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.780529] ata1.00: cmd 61/00:78:88:cf:0c/04:00:15:00:00/40 tag 15 ncq dma 524288 out
<3>[29897.780529]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.796361] ata1.00: status: { DRDY ERR }
<3>[29897.800398] ata1.00: error: { ABRT }
<3>[29897.803997] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.809256] ata1.00: cmd 61/00:80:88:d3:0c/04:00:15:00:00/40 tag 16 ncq dma 524288 out
<3>[29897.809256]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.825038] ata1.00: status: { DRDY ERR }
<3>[29897.829075] ata1.00: error: { ABRT }
<3>[29897.832675] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.837925] ata1.00: cmd 61/00:88:88:d7:0c/04:00:15:00:00/40 tag 17 ncq dma 524288 out
<3>[29897.837925]          res 41/04:00:88:d7:0c/00:04:15:00:00/40 Emask 0x401 (device error) <F>
<3>[29897.854220] ata1.00: status: { DRDY ERR }
<3>[29897.858281] ata1.00: error: { ABRT }
<3>[29897.861881] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.867134] ata1.00: cmd 61/00:90:88:db:0c/04:00:15:00:00/40 tag 18 ncq dma 524288 out
<3>[29897.867134]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.882917] ata1.00: status: { DRDY ERR }
<3>[29897.886951] ata1.00: error: { ABRT }
<3>[29897.890547] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.895796] ata1.00: cmd 61/00:98:88:df:0c/04:00:15:00:00/40 tag 19 ncq dma 524288 out
<3>[29897.895796]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.911568] ata1.00: status: { DRDY ERR }
<3>[29897.915601] ata1.00: error: { ABRT }
<3>[29897.919210] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.924459] ata1.00: cmd 61/00:a0:88:e3:0c/04:00:15:00:00/40 tag 20 ncq dma 524288 out
<3>[29897.924459]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.940232] ata1.00: status: { DRDY ERR }
<3>[29897.944273] ata1.00: error: { ABRT }
<3>[29897.947875] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.953127] ata1.00: cmd 61/00:a8:88:e7:0c/04:00:15:00:00/40 tag 21 ncq dma 524288 out
<3>[29897.953127]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.968932] ata1.00: status: { DRDY ERR }
<3>[29897.972973] ata1.00: error: { ABRT }
<3>[29897.976597] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29897.981857] ata1.00: cmd 61/00:b0:88:eb:0c/04:00:15:00:00/40 tag 22 ncq dma 524288 out
<3>[29897.981857]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29897.997632] ata1.00: status: { DRDY ERR }
<3>[29898.001666] ata1.00: error: { ABRT }
<3>[29898.005276] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29898.010541] ata1.00: cmd 61/00:b8:88:ef:0c/04:00:15:00:00/40 tag 23 ncq dma 524288 out
<3>[29898.010541]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29898.026321] ata1.00: status: { DRDY ERR }
<3>[29898.030356] ata1.00: error: { ABRT }
<3>[29898.033950] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29898.039204] ata1.00: cmd 61/00:c0:88:f3:0c/04:00:15:00:00/40 tag 24 ncq dma 524288 out
<3>[29898.039204]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29898.054981] ata1.00: status: { DRDY ERR }
<3>[29898.059022] ata1.00: error: { ABRT }
<3>[29898.062630] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29898.067896] ata1.00: cmd 61/00:c8:88:f7:0c/04:00:15:00:00/40 tag 25 ncq dma 524288 out
<3>[29898.067896]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29898.083667] ata1.00: status: { DRDY ERR }
<3>[29898.087710] ata1.00: error: { ABRT }
<3>[29898.091312] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29898.096562] ata1.00: cmd 61/00:d0:88:fb:0c/04:00:15:00:00/40 tag 26 ncq dma 524288 out
<3>[29898.096562]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29898.112346] ata1.00: status: { DRDY ERR }
<3>[29898.116385] ata1.00: error: { ABRT }
<3>[29898.119980] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29898.125230] ata1.00: cmd 61/00:d8:88:ff:0c/04:00:15:00:00/40 tag 27 ncq dma 524288 out
<3>[29898.125230]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29898.141009] ata1.00: status: { DRDY ERR }
<3>[29898.145042] ata1.00: error: { ABRT }
<3>[29898.148650] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29898.153905] ata1.00: cmd 61/00:e8:88:8b:0c/04:00:15:00:00/40 tag 29 ncq dma 524288 out
<3>[29898.153905]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29898.169674] ata1.00: status: { DRDY ERR }
<3>[29898.173706] ata1.00: error: { ABRT }
<3>[29898.177308] ata1.00: failed command: WRITE FPDMA QUEUED
<3>[29898.182560] ata1.00: cmd 61/00:f0:88:8f:0c/04:00:15:00:00/40 tag 30 ncq dma 524288 out
<3>[29898.182560]          res 41/04:eb:87:8b:0c/00:ff:15:00:00/40 Emask 0x1 (device error)
<3>[29898.198335] ata1.00: status: { DRDY ERR }
<3>[29898.202376] ata1.00: error: { ABRT }
<6>[29898.213757] ata1.00: configured for UDMA/133
<6>[29898.218180] ata1: EH complete

@crieke

thanks for looking.

About the errors I’ll translate his answer. "This are HDD sata errors and messages uit de kernel logs. They are coming from the HDD’s themself. Checked the backplane errors and they seem fine. "

He did an install himself and luckily after an hour or so Roon crashed. (again after a restart of the NAS, done from the PC) These are the latest Roon logs.

Don’t know what to do next. QNAP is not convinced yet.

Dimitri

@crieke

Hi Christopher,

can I ask you one more question? Now everything is running fine, after a clean install for about a half hour or so… but there is no audio coming from the HDMI output from the NAS.

Can you explane why Roon is showing 5 HDMI ports for my NAS, when there are only two? (this has allways been) And no of the HDMI outlets are giving audio at all. (this is new)

Another day, another problem.

Thank you

Dimitri

@dylan @crieke

Hi guys,

this is the end of the line for me. I’m getting of the Roon train, unfortunately. QNAP was very helpfull, you need to give them some time, but in the end I’m convinced it is a problem for you to solve. This is what happend (without repeating everything we allready went over).

  • QNAP looked at their logs, no faults found
  • Hardware tests all without faults, HDD’s, SSD’s, MemTest etc
  • Via Teamviewer and PuTTY a thourough analysis of the behavior of the NAS i.c.w. Roon, nothing found. The QNAP guy did not understand everything Roon did in the shutdown and start-up sequence, the termination of the library was one of these things.

Because the entire NAS environment works fine, Plex and Kodi included, I keep coming back to you guys… I’m over my head in the details and learned a lot in the meantime, but without any good results. Even though the NAS is build in the for Roon optimised way.

If there is anything I can do for you, just let me know. As soon as you found a solution, definitely let me know.

Best regards,

Dimitri