I got a warning telling me that:
 

**/var/log is getting full (currently 100 % used)**

 

Looking at my syslog I have many entries telling me that:
 

Tower kernel: sd 7:0:0:0: [sdg] tag#1 access beyond end of device

 

Although there are many of these entries on the 23rd of October along with lots of other BTRFS errors such as:

 

Tower kernel: BTRFS warning (device sdg1): lost page write due to IO error on /dev/sdg1 (-5)
Tower kernel: BTRFS error (device sdg1): error writing primary super block to device 2

 

...I suddenly get no entries in my syslog at all after the 23rd which seems odd. "sdg" is one of my two cache drives and looking at my cache it is only about 50% full.

 

I can't really tell if:

1. Perhaps my cache just got full on the 23rd leading to these errors and then whatever filled it up was deleted, so the errors stopped. But I find it odd that I no longer have any syslog entries after the 23rd.
2. Or my sdg drive is somehow defective and I should replace it.

 

I'd appreciate any insight anyone can give on this (diagnostics attached), thanks!

tower-diagnostics-20221025-0943.zip

Cache device dropped offline:

 

Oct 23 06:21:46 Tower kernel: ata7: reset failed, giving up
Oct 23 06:21:46 Tower kernel: ata7.00: disabled
Oct 23 06:21:46 Tower kernel: ata7: EH complete

 

Check/replace cables.

5 hours ago, JorgeB said:

Check/replace cables.

 

Thanks, I will as soon as I get access to my server. The drive does appear to be back online as I can see reads & writes to & from it. Do you think it is unlikely that after that there has been nothing at all in my syslog since, for two days now?

16 minutes ago, writablevulture said:

Do you think it is unlikely that after that there has been nothing at all in my syslog since, for two days now?

Sorry, don't understand the question.

After the entries in my syslog.1 file on the 23rd of October, my syslog file is totally empty. So, no log entries for 48 hours.

 

That just seems odd to me, I was wondering if you (or anyone else) think that's unusual.

It happens if there's a lot of spam.

I tried unseating/reseating the cable, changing the cable and using an alternative SATA port without success - so I guess the drive is genuinely dead. I have removed it from the pool and ordered a replacement. Thanks!