Estou com 1 SSD de 500gb e 1 HD de 1tb, o ssd esta montado como a /
e HD de 1Tb em /home
.
A um tempo estou tendo esse problema, estou usando ele normalmente, quando do nada o HD de 1Tb não me deixa escrever nada, e fala que esta em modo read-only:
Até mesmo com o root!
Já o SSD de 500, funciona normalmente:
Ambos estão formatados no sistema BTRFS
Estou usando o Zorin OS 16
Kernel x86_64 Linux 5.13.0-41-generic
Meu /etc/fstab
:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdb1 during installation
UUID=d952e877-f36b-4e79-8061-923331d5f0c4 / btrfs defaults,subvol=@ 0 1
# /home was on /dev/sda1 during installation
UUID=32b48597-2b8f-4aa8-9229-2d5806bfbf9e /home btrfs defaults,subvol=@home 0 2
# swap was on /dev/sdb5 during installation
UUID=d5b57a27-1a9f-48d7-83df-f2ceff4fc6f6 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
Momento no /var/log/kern.log
em que acho q o disco travou no read-only:
...some logs before...
May 17 09:20:26 jarvis kernel: [ 4749.947077] ata1: soft resetting link
May 17 09:20:26 jarvis kernel: [ 4750.121193] ata1.00: configured for UDMA/33
May 17 09:20:26 jarvis kernel: [ 4750.124457] ata1.01: configured for UDMA/133
May 17 09:20:26 jarvis kernel: [ 4750.124502] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
May 17 09:20:26 jarvis kernel: [ 4750.124507] sd 0:0:0:0: [sda] tag#0 Sense Key : Aborted Command [current]
May 17 09:20:26 jarvis kernel: [ 4750.124511] sd 0:0:0:0: [sda] tag#0 Add. Sense: Scsi parity error
May 17 09:20:26 jarvis kernel: [ 4750.124515] sd 0:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 55 21 e1 80 00 07 00 00
May 17 09:20:26 jarvis kernel: [ 4750.124518] blk_update_request: I/O error, dev sda, sector 1428283776 op 0x1:(WRITE) flags 0x5800 phys_seg 117 prio class 0
May 17 09:20:26 jarvis kernel: [ 4750.124686] ata1: EH complete
May 17 09:20:26 jarvis kernel: [ 4750.129788] BTRFS: error (device sda1) in btrfs_run_delayed_refs:2163: errno=-5 IO failure
May 17 09:20:26 jarvis kernel: [ 4750.129794] BTRFS info (device sda1): forced readonly
May 17 09:20:26 jarvis kernel: [ 4750.131725] BTRFS warning (device sda1): Skipping commit of aborted transaction.
May 17 09:20:26 jarvis kernel: [ 4750.131768] BTRFS: error (device sda1) in btrfs_sync_log:3347: errno=-5 IO failure
May 17 09:20:26 jarvis kernel: [ 4750.171570] BTRFS warning (device sda1): csum hole found for disk bytenr range [223342219264, 223342223360)
May 17 09:20:26 jarvis kernel: [ 4750.171580] BTRFS warning (device sda1): csum hole found for disk bytenr range [223342223360, 223342227456)
May 17 09:20:26 jarvis kernel: [ 4750.171584] BTRFS warning (device sda1): csum hole found for disk bytenr range [223342227456, 223342231552)
May 17 09:20:26 jarvis kernel: [ 4750.171587] BTRFS warning (device sda1): csum hole found for disk bytenr range [223342231552, 223342235648)
May 17 09:20:26 jarvis kernel: [ 4750.187089] BTRFS warning (device sda1): csum failed root 256 ino 4366277 off 0 csum 0x38fd4371 expected csum 0x00000000 mirror 1
May 17 09:20:26 jarvis kernel: [ 4750.187140] BTRFS warning (device sda1): csum hole found for disk bytenr range [223342219264, 223342223360)
May 17 09:20:26 jarvis kernel: [ 4750.188452] BTRFS warning (device sda1): csum failed root 256 ino 4366277 off 0 csum 0x38fd4371 expected csum 0x00000000 mirror 1
May 17 09:20:32 jarvis kernel: [ 4756.205466] BTRFS warning (device sda1): csum hole found for disk bytenr range [445233070080, 445233074176)
some logs after...
Já cheguei e rodar o comando btrfs check
sosinho e com o --repair
dando boot em um pendrive externo com o Kali Linux, mas n parece ter resolvido.
Alguma ideia de como resolver?