Downloader Issue

[Kayman42]

I'm not sure if these are related but I thought I would post it all together just in case.

 

The first Issue I noticed was that my downloader apps(Sonarr, Radarr and Lidarr) weren't functioning and I couldn't access the web gui.  They all have the same error in the log. 

 

 

 

[v2.0.0.5344] NzbDrone.Core.Datastore.CorruptDatabaseException: Database file: /config/nzbdrone.db is corrupt, restore from backup if available. See: https://github.com/Sonarr/Sonarr/wiki/FAQ#i-am-getting-an-error-database-disk-image-is-malformed ---> System.Data.SQLite.SQLiteException: database disk image is malformed

 

In the process of looking into this I also noticed this from my syslog.

 

Sep 6 16:52:01 Cosmere kernel: ata7.00: irq_stat 0x40000001
Sep 6 16:52:01 Cosmere kernel: ata7.00: failed command: FLUSH CACHE EXT
Sep 6 16:52:01 Cosmere kernel: ata7.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 27
Sep 6 16:52:01 Cosmere kernel: res 51/04:00:00:00:00/00:00:00:00:00/00 Emask 0x1 (device error)
Sep 6 16:52:01 Cosmere kernel: ata7.00: status: { DRDY ERR }
Sep 6 16:52:01 Cosmere kernel: ata7.00: error: { ABRT }
Sep 6 16:52:01 Cosmere kernel: ata7.00: configured for UDMA/33
Sep 6 16:52:01 Cosmere kernel: ata7.00: device reported invalid CHS sector 0
Sep 6 16:52:01 Cosmere kernel: ata7: EH complete
Sep 6 16:52:01 Cosmere kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

 

I'm not sure if they are related or if the syslog messages are even cause for concern.  I have included the diagnostics from my server.  Please let me know if I need to include anything else, thanks!

 

 

cosmere-diagnostics-20200906-1555.zip

[JorgeB]

Check/replace cables on the parity disk, but likely unrelated to your other issue.

[Kayman42]

Cable replacement seemed to have done the trick thanks!  Out of curiosity what clued you into it being the parity drive?

[JorgeB]

In the syslog you can see which drive corresponds to the ATA#

[Kayman42]

On 9/9/2020 at 1:44 PM, JorgeB said:

In the syslog you can see which drive corresponds to the ATA#

Ah ha, thanks!