lankanmon Posted January 7, 2020 Share Posted January 7, 2020 I am getting a BTRFS error spamming my logs and there appears to be other issued. SDB1 is my cache drive. I have Fix common problems installed and it is detecting that the drive is read only or full. But the drive is 480GB and it is only using 78GB, so there is plenty of space. I have attached the diagnostics to this post This is a snippet of the message being spammed: Jan 6 05:12:23 LKNServer kernel: __btrfs_lookup_bio_sums: 10 callbacks suppressed Jan 6 05:12:23 LKNServer kernel: BTRFS info (device sdb1): no csum found for inode 988745 start 0 Jan 6 05:12:23 LKNServer kernel: sd 1:0:0:0: [sdb] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 6 05:12:23 LKNServer kernel: sd 1:0:0:0: [sdb] tag#5 CDB: opcode=0x28 28 00 03 d0 92 b8 00 00 08 00 Jan 6 05:12:23 LKNServer kernel: print_req_error: I/O error, dev sdb, sector 64000696 Jan 6 05:12:23 LKNServer kernel: BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 43, rd 254421, flush 0, corrupt 0, gen 0 Your help is much appreciated. Thanks! lknserver-diagnostics-20200107-0159.zip Quote Link to comment
trurl Posted January 7, 2020 Share Posted January 7, 2020 No SMART for cache in those but looks like it may be a problem with the device instead of just the filesystem. Quote Link to comment
lankanmon Posted January 7, 2020 Author Share Posted January 7, 2020 So, I need to replace the cache drive? Quote Link to comment
JorgeB Posted January 7, 2020 Share Posted January 7, 2020 Cache device dropped offline: Jan 6 01:01:01 LKNServer kernel: ata1: hard resetting link Jan 6 01:01:07 LKNServer kernel: ata1: link is slow to respond, please be patient (ready=0) Jan 6 01:01:11 LKNServer kernel: ata1: COMRESET failed (errno=-16) Jan 6 01:01:11 LKNServer kernel: ata1: hard resetting link Jan 6 01:01:17 LKNServer kernel: ata1: link is slow to respond, please be patient (ready=0) Jan 6 01:01:22 LKNServer kernel: ata1: COMRESET failed (errno=-16) Jan 6 01:01:22 LKNServer kernel: ata1: hard resetting link Jan 6 01:01:27 LKNServer kernel: ata1: link is slow to respond, please be patient (ready=0) Jan 6 01:01:57 LKNServer kernel: ata1: COMRESET failed (errno=-16) Jan 6 01:01:57 LKNServer kernel: ata1: limiting SATA link speed to 3.0 Gbps Jan 6 01:01:57 LKNServer kernel: ata1: hard resetting link Jan 6 01:02:02 LKNServer kernel: ata1: COMRESET failed (errno=-16) Jan 6 01:02:02 LKNServer kernel: ata1: reset failed, giving up Jan 6 01:02:02 LKNServer kernel: ata1.00: disabled With SSDs this is usually a cable/connection problem Quote Link to comment
trurl Posted January 7, 2020 Share Posted January 7, 2020 After checking cables/connections post a new diagnostic. Quote Link to comment
lankanmon Posted January 8, 2020 Author Share Posted January 8, 2020 Here is the diagnostics after I made sure the cables a plugged in correctly. lknserver-diagnostics-20200107-2359.zip Quote Link to comment
trurl Posted January 8, 2020 Share Posted January 8, 2020 Looks OK to me. Are you having any problems now? Quote Link to comment
lankanmon Posted January 8, 2020 Author Share Posted January 8, 2020 (edited) I waited about a day after and it seems to be back. Fix common problems shows: Unable to write to cache and the log is about 34% full now. I do not have docker and vms running so it is just system messages causing the errors. I have attached diagnostics. Also do I need to balance my cache? and if so, what command should I use? lknserver-diagnostics-20200108-2158.zip Edited January 8, 2020 by lankanmon Quote Link to comment
trurl Posted January 9, 2020 Share Posted January 9, 2020 No SMART for cache again. Quote Link to comment
lankanmon Posted January 9, 2020 Author Share Posted January 9, 2020 (edited) Okay, I will try swapping the cable and if that does not work, I will swap the drive... Can you think of anything else it could be? Edited January 9, 2020 by lankanmon Quote Link to comment
trurl Posted January 9, 2020 Share Posted January 9, 2020 16 hours ago, lankanmon said: Can you think of anything else it could be? The way I usually put it is: Check connections, SATA and power, both ends, including any power splitters. Could also be a bad cable, SATA or power. Could be a bad port. I usually defer to more knowledgeable people on controller issues that involve multiple drives. Could be bad drive but the SMART we got earlier seemed OK. It's not always clear to me how to interpret those in the case of SSDs of various manufacture though. Quote Link to comment
lankanmon Posted January 25, 2020 Author Share Posted January 25, 2020 Hey thanks for this. I swapped out a bunch of SATA cables and it seems to have stopped the messages. I will keep an eye on it for now. Good to know that the drive is okay. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.