Re: How to fix "BTRFS error (device dm-3): error writing primary super block to device 1"?

[Kai Stian Olstad <btrfs+list@olstad.com>]

On 12.04.2025 00:10, Qu Wenruo wrote:
> 在 2025/4/12 01:18, Kai Stian Olstad 写道:
>> Kubuntu 24.04
>> Kernel 6.8.0-57-generic
>> 
>> 2 day ago I got a sector error on one of the BTRFS disk
>> 
>> $ journalctl -k -S 2025-04-09 | grep -A 20 mpt3sas_cm0
>> Apr 09 03:16:26 cb kernel: mpt3sas_cm0: log_info(0x31080000): 
>> originator(PL), code(0x08), sub_code(0x0000)
>> Apr 09 03:16:26 cb kernel: mpt3sas_cm0: log_info(0x31080000): 
>> originator(PL), code(0x08), sub_code(0x0000)
>> Apr 09 03:16:26 cb kernel: sd 4:0:1:0: [sdd] tag#5552 FAILED Result: 
>> hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=6s
>> Apr 09 03:16:26 cb kernel: sd 4:0:1:0: [sdd] tag#5552 Sense Key : 
>> Illegal Request [current]
>> Apr 09 03:16:26 cb kernel: sd 4:0:1:0: [sdd] tag#5552 Add. Sense: 
>> Logical block address out of range
>> Apr 09 03:16:26 cb kernel: sd 4:0:1:0: [sdd] tag#5552 CDB: Write(16) 
>> 8a 08 00 00 00 00 00 00 10 80 00 00 00 08 00 00
>> Apr 09 03:16:26 cb kernel: critical target error, dev sdd, sector 4224 
>> op 0x1:(WRITE) flags 0x23800 phys_seg 1 prio class 0
> 
> This error is completely from the lower layer (the block device).
> 
> Btrfs nor the LUKS upon the disk can do anything to it.

Thank you for the response.

This disk support scterc

$ sudo smartctl -l scterc /dev/sdd
SCT Error Recovery Control:
            Read:     70 (7.0 seconds)
           Write:     70 (7.0 seconds)

Doesn't that mean that the disk gives up after 7 seconds, and then the 
sector i mapped to a spare.
So if Btrfs does a write to the sector again it will be written to the 
spare?

I've experienced numerous sector errors throughout the years with mdadm 
and they have been fixed with a check.
Also a few with Btrfs I think, but they have been fixed automatically.

So why not this time?
To me this looks like an ordinary faulty sector that can be "fixed" with 
a write?

-- 
Kai Stian Olstad