Hello community!

 

First time posting here for me, despite reading this forum quite a bit.
I have recently updated my OS to 6.12.6 and added a new cache disk. My intention was for this second disk to be a mirror of the disk that is in place.

The existing disk has been reporting sector failures for some time now.
The issue is that I am unable to convert the two disks to RAID1 mode. I get the error I pasted below.

Does anyone know what to do?

Thanks for your help 😃

 

Dec 17 10:36:32 Tower ool www[32444]: /usr/local/emhttp/plugins/dynamix/scripts/btrfs_balance 'start' '/mnt/cache' '-dconvert=raid1,soft -mconvert=raid1,soft'
Dec 17 10:36:32 Tower kernel: BTRFS info (device sdc1): balance: start -dconvert=raid1,soft -mconvert=raid1,soft -sconvert=raid1,soft
Dec 17 10:36:32 Tower kernel: BTRFS info (device sdc1): relocating block group 254498832384 flags data
Dec 17 10:36:33 Tower kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Dec 17 10:36:33 Tower kernel: ata2.00: irq_stat 0x40000001
Dec 17 10:36:33 Tower kernel: ata2.00: failed command: READ DMA EXT
Dec 17 10:36:33 Tower kernel: ata2.00: cmd 25/00:00:00:64:81/00:0a:1d:00:00/e0 tag 7 dma 1310720 in
Dec 17 10:36:33 Tower kernel:         res 51/40:00:c8:6a:81/00:00:1d:00:00/e0 Emask 0x9 (media error)
Dec 17 10:36:33 Tower kernel: ata2.00: status: { DRDY ERR }
Dec 17 10:36:33 Tower kernel: ata2.00: error: { UNC }
Dec 17 10:36:33 Tower kernel: ata2.00: supports DRM functions and may not be fully accessible
Dec 17 10:36:33 Tower kernel: ata2.00: supports DRM functions and may not be fully accessible
Dec 17 10:36:33 Tower kernel: ata2.00: configured for UDMA/133
Dec 17 10:36:33 Tower kernel: sd 3:0:0:0: [sdc] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Dec 17 10:36:33 Tower kernel: sd 3:0:0:0: [sdc] tag#7 Sense Key : 0x3 [current] 
Dec 17 10:36:33 Tower kernel: sd 3:0:0:0: [sdc] tag#7 ASC=0x11 ASCQ=0x4 
Dec 17 10:36:33 Tower kernel: sd 3:0:0:0: [sdc] tag#7 CDB: opcode=0x28 28 00 1d 81 64 00 00 0a 00 00
Dec 17 10:36:33 Tower kernel: I/O error, dev sdc, sector 495020744 op 0x0:(READ) flags 0x84700 phys_seg 7 prio class 2
Dec 17 10:36:33 Tower kernel: ata2: EH complete
Dec 17 10:36:33 Tower kernel: ata2.00: Enabling discard_zeroes_data
Dec 17 10:36:33 Tower emhttpd: read SMART /dev/sdb
Dec 17 10:36:33 Tower emhttpd: read SMART /dev/sdc
Dec 17 10:36:33 Tower kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Dec 17 10:36:33 Tower kernel: ata2.00: irq_stat 0x40000001
Dec 17 10:36:33 Tower kernel: ata2.00: failed command: READ DMA EXT
Dec 17 10:36:33 Tower kernel: ata2.00: cmd 25/00:08:c8:6a:81/00:00:1d:00:00/e0 tag 9 dma 4096 in
Dec 17 10:36:33 Tower kernel:         res 51/40:00:c8:6a:81/00:00:1d:00:00/e0 Emask 0x9 (media error)
Dec 17 10:36:33 Tower kernel: ata2.00: status: { DRDY ERR }
Dec 17 10:36:33 Tower kernel: ata2.00: error: { UNC }
Dec 17 10:36:33 Tower kernel: ata2.00: supports DRM functions and may not be fully accessible
Dec 17 10:36:33 Tower kernel: ata2.00: supports DRM functions and may not be fully accessible
Dec 17 10:36:33 Tower kernel: ata2.00: configured for UDMA/133
Dec 17 10:36:33 Tower kernel: sd 3:0:0:0: [sdc] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Dec 17 10:36:33 Tower kernel: sd 3:0:0:0: [sdc] tag#9 Sense Key : 0x3 [current] 
Dec 17 10:36:33 Tower kernel: sd 3:0:0:0: [sdc] tag#9 ASC=0x11 ASCQ=0x4 
Dec 17 10:36:33 Tower kernel: sd 3:0:0:0: [sdc] tag#9 CDB: opcode=0x28 28 00 1d 81 6a c8 00 00 08 00
Dec 17 10:36:33 Tower kernel: I/O error, dev sdc, sector 495020744 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Dec 17 10:36:33 Tower kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 4069, flush 0, corrupt 0, gen 0
Dec 17 10:36:33 Tower kernel: ata2: EH complete
Dec 17 10:36:33 Tower kernel: ata2.00: Enabling discard_zeroes_data
Dec 17 10:36:33 Tower kernel: BTRFS info (device sdc1): balance: ended with status: -5

 

Attach Diagnostics to your NEXT post in this thread. 

Thanks for your swift reply, here is the requested Diagnostics zip file 😃

tower-diagnostics-20231217-1101.zip

sdc is apparently failing, so the balance aborts, run an extended SMART test.

Thanks for your reply @JorgeB!
I have attached here the extended SMART test results.

 

Is there a way to "force" the creation of a RAID1 setup?

Samsung_SSD_870_EVO_1TB_S6PUNS0RB05821W-20231217-1333.txt

The device failed and needs to be replaced, you cannot create a raid1 with a failed device, since it will abort on the read errors, copy what you can from that pool, then create a new raid1 pool with new devices.

Thanks for your help!
I will remove this drive ASAP!