Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

How to remove a failing cache drive from a pool and just use the one

caelar900
in General Support

Featured Replies

Ive got a pool of cache drives and one is failing I'd like to remove the failing drive and just use the single drive going forward if possible but am a little unsure how to go about this I'm getting an error that says too many BTRFS profiles on my pool.

 

Output from btrfs fi df /mnt/cache is:

 

Data, single: total=742.01GiB, used=71.04GiB
Data, RAID1: total=886.00GiB, used=103.21GiB
System, RAID1: total=32.00MiB, used=240.00KiB
Metadata, RAID1: total=5.00GiB, used=1.25GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
WARNING: Multiple block group profiles detected, see 'man btrfs(5)'
WARNING:    Data: single, raid1

 

When I balance Im gettin these errors 

 

Quote

Mar 23 11:33:12 Tower kernel: I/O error, dev sdn, sector 1655866328 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2
Mar 23 11:33:12 Tower kernel: sd 8:0:5:0: [sdn] tag#747 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 23 11:33:12 Tower kernel: sd 8:0:5:0: [sdn] tag#747 Sense Key : 0x3 [current] 
Mar 23 11:33:12 Tower kernel: sd 8:0:5:0: [sdn] tag#747 ASC=0x11 ASCQ=0x0 
Mar 23 11:33:12 Tower kernel: sd 8:0:5:0: [sdn] tag#747 CDB: opcode=0x28 28 00 62 b2 79 d8 00 0a 00 00
Mar 23 11:33:12 Tower kernel: critical medium error, dev sdn, sector 1655863768 op 0x0:(READ) flags 0x84700 phys_seg 20 prio class 2
Mar 23 11:33:12 Tower kernel: repair_io_failure: 1350 callbacks suppressed
Mar 23 11:33:12 Tower kernel: BTRFS info (device dm-11): read error corrected: ino 1115 off 577507328 (dev /dev/mapper/sdn1 sector 1655823880)
Mar 23 11:33:12 Tower kernel: BTRFS info (device dm-11): read error corrected: ino 1115 off 577523712 (dev /dev/mapper/sdn1 sector 1655823912)
Mar 23 11:33:12 Tower kernel: BTRFS info (device dm-11): read error corrected: ino 1115 off 577527808 (dev /dev/mapper/sdn1 sector 1655823920)
Mar 23 11:33:12 Tower kernel: BTRFS info (device dm-11): read error corrected: ino 1115 off 577536000 (dev /dev/mapper/sdn1 sector 1655823936)
Mar 23 11:33:12 Tower kernel: BTRFS info (device dm-11): read error corrected: ino 1115 off 577544192 (dev /dev/mapper/sdn1 sector 1655823952)
Mar 23 11:33:12 Tower kernel: BTRFS info (device dm-11): read error corrected: ino 1115 off 577540096 (dev /dev/mapper/sdn1 sector 1655823944)
Mar 23 11:33:12 Tower kernel: BTRFS info (device dm-11): read error corrected: ino 1115 off 577548288 (dev /dev/mapper/sdn1 sector 1655823960)
Mar 23 11:33:12 Tower kernel: BTRFS info (device dm-11): read error corrected: ino 1115 off 577552384 (dev /dev/mapper/sdn1 sector 1655823968)
Mar 23 11:33:12 Tower kernel: BTRFS info (device dm-11): read error corrected: ino 1115 off 577556480 (dev /dev/mapper/sdn1 sector 1655823976)
Mar 23 11:33:12 Tower kernel: BTRFS info (device dm-11): read error corrected: ino 1115 off 577572864 (dev /dev/mapper/sdn1 sector 1655824008)
Mar 23 11:33:12 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 11:33:12 Tower kernel: sd 8:0:5:0: [sdn] tag#763 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s
Mar 23 11:33:12 Tower kernel: sd 8:0:5:0: [sdn] tag#763 CDB: opcode=0x28 28 00 62 b2 9d d8 00 08 00 00
Mar 23 11:33:12 Tower kernel: I/O error, dev sdn, sector 1655872984 op 0x0:(READ) flags 0x80700 phys_seg 17 prio class 2
Mar 23 11:33:12 Tower kernel: sd 8:0:5:0: [sdn] tag#762 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 23 11:33:12 Tower kernel: sd 8:0:5:0: [sdn] tag#762 Sense Key : 0x3 [current] 
Mar 23 11:33:12 Tower kernel: sd 8:0:5:0: [sdn] tag#762 ASC=0x11 ASCQ=0x0 
Mar 23 11:33:12 Tower kernel: sd 8:0:5:0: [sdn] tag#762 CDB: opcode=0x28 28 00 62 b2 93 d8 00 0a 00 00
Mar 23 11:33:12 Tower kernel: critical medium error, dev sdn, sector 1655870424 op 0x0:(READ) flags 0x84700 phys_seg 21 prio class 2
Mar 23 11:33:12 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 11:33:12 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 11:33:12 Tower kernel: sd 8:0:5:0: [sdn] tag#711 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s
Mar 23 11:33:12 Tower kernel: sd 8:0:5:0: [sdn] tag#711 CDB: opcode=0x28 28 00 62 b2 b3 d8 00 0a 00 00
Mar 23 11:33:12 Tower kernel: I/O error, dev sdn, sector 1655878616 op 0x0:(READ) flags 0x84700 phys_seg 21 prio class 2
Mar 23 11:33:12 Tower kernel: sd 8:0:5:0: [sdn] tag#712 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s
Mar 23 11:33:12 Tower kernel: sd 8:0:5:0: [sdn] tag#712 CDB: opcode=0x28 28 00 62 b2 bd d8 00 08 00 00
Mar 23 11:33:12 Tower kernel: I/O error, dev sdn, sector 1655881176 op 0x0:(READ) flags 0x80700 phys_seg 16 prio class 2
Mar 23 11:33:12 Tower kernel: sd 8:0:5:0: [sdn] tag#710 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 23 11:33:12 Tower kernel: sd 8:0:5:0: [sdn] tag#710 Sense Key : 0x3 [current] 
Mar 23 11:33:12 Tower kernel: sd 8:0:5:0: [sdn] tag#710 ASC=0x11 ASCQ=0x0 
Mar 23 11:33:12 Tower kernel: sd 8:0:5:0: [sdn] tag#710 CDB: opcode=0x28 28 00 62 b2 a9 d8 00 0a 00 00
Mar 23 11:33:12 Tower kernel: critical medium error, dev sdn, sector 1655876056 op 0x0:(READ) flags 0x84700 phys_seg 94 prio class 2
Mar 23 11:33:13 Tower kernel: sd 8:0:5:0: [sdn] tag#712 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 23 11:33:13 Tower kernel: sd 8:0:5:0: [sdn] tag#712 Sense Key : 0x3 [current] 
Mar 23 11:33:13 Tower kernel: sd 8:0:5:0: [sdn] tag#712 ASC=0x11 ASCQ=0x0 
Mar 23 11:33:13 Tower kernel: sd 8:0:5:0: [sdn] tag#712 CDB: opcode=0x28 28 00 62 b5 df b0 00 0a 00 00
Mar 23 11:33:13 Tower kernel: critical medium error, dev sdn, sector 1656086448 op 0x0:(READ) flags 0x84700 phys_seg 20 prio class 2
Mar 23 11:33:14 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 11:33:14 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 11:33:14 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 11:33:14 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 11:33:14 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 11:33:14 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 11:33:14 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 11:33:14 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 11:33:14 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 11:33:14 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 11:33:14 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 11:33:14 Tower kernel: sd 8:0:5:0: [sdn] tag#729 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s
Mar 23 11:33:14 Tower kernel: sd 8:0:5:0: [sdn] tag#729 CDB: opcode=0x28 28 00 62 b5 ff b0 00 0a 00 00
Mar 23 11:33:14 Tower kernel: I/O error, dev sdn, sector 1656094640 op 0x0:(READ) flags 0x84700 phys_seg 21 prio class 2
Mar 23 11:33:14 Tower kernel: sd 8:0:5:0: [sdn] tag#730 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s
Mar 23 11:33:14 Tower kernel: sd 8:0:5:0: [sdn] tag#730 CDB: opcode=0x28 28 00 62 b6 09 b0 00 0a 00 00
Mar 23 11:33:14 Tower kernel: I/O error, dev sdn, sector 1656097200 op 0x0:(READ) flags 0x84700 phys_seg 21 prio class 2
Mar 23 11:33:14 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)

______________________________________________________________

Mar 23 11:45:49 Tower kernel: BTRFS info (device dm-11): relocating block group 3014026919936 flags data|raid1
Mar 23 11:46:04 Tower kernel: BTRFS info (device dm-11): found 95673 extents, stage: move data extents
Mar 23 11:46:12 Tower kernel: BTRFS info (device dm-11): found 95673 extents, stage: update data pointers
Mar 23 11:46:19 Tower kernel: BTRFS info (device dm-11): relocating block group 1215497764864 flags data
Mar 23 11:46:20 Tower kernel: scsi_io_completion_action: 16 callbacks suppressed
Mar 23 11:46:20 Tower kernel: sd 8:0:5:0: [sdn] tag#908 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 23 11:46:20 Tower kernel: sd 8:0:5:0: [sdn] tag#908 Sense Key : 0x3 [current] 
Mar 23 11:46:20 Tower kernel: sd 8:0:5:0: [sdn] tag#908 ASC=0x11 ASCQ=0x0 
Mar 23 11:46:20 Tower kernel: sd 8:0:5:0: [sdn] tag#908 CDB: opcode=0x28 28 00 5c 21 37 90 00 00 38 00
Mar 23 11:46:20 Tower kernel: blk_print_req_error: 16 callbacks suppressed
Mar 23 11:46:20 Tower kernel: critical medium error, dev sdn, sector 1545680784 op 0x0:(READ) flags 0x80700 phys_seg 7 prio class 2
Mar 23 11:46:20 Tower kernel: sd 8:0:5:0: [sdn] tag#915 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 23 11:46:20 Tower kernel: sd 8:0:5:0: [sdn] tag#915 Sense Key : 0x3 [current] 
Mar 23 11:46:20 Tower kernel: sd 8:0:5:0: [sdn] tag#915 ASC=0x11 ASCQ=0x0 
Mar 23 11:46:20 Tower kernel: sd 8:0:5:0: [sdn] tag#915 CDB: opcode=0x28 28 00 5c 21 37 c0 00 00 08 00
Mar 23 11:46:20 Tower kernel: critical medium error, dev sdn, sector 1545680832 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Mar 23 11:46:20 Tower kernel: BTRFS info (device dm-11): balance: ended with status: -5

 

And when I scrub Im getting these.

 

Quote

Mar 23 12:48:55 Tower kernel: I/O error, dev sdn, sector 447547912 op 0x0:(READ) flags 0x800 phys_seg 1 prio class 2
Mar 23 12:48:55 Tower kernel: sd 8:0:5:0: [sdn] tag#3014 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 23 12:48:55 Tower kernel: sd 8:0:5:0: [sdn] tag#3014 Sense Key : 0x3 [current] 
Mar 23 12:48:55 Tower kernel: sd 8:0:5:0: [sdn] tag#3014 ASC=0x11 ASCQ=0x0 
Mar 23 12:48:55 Tower kernel: sd 8:0:5:0: [sdn] tag#3014 CDB: opcode=0x28 28 00 1a ac e6 88 00 00 08 00
Mar 23 12:48:55 Tower kernel: critical medium error, dev sdn, sector 447538824 op 0x0:(READ) flags 0x800 phys_seg 1 prio class 2
Mar 23 12:48:55 Tower kernel: BTRFS error (device dm-11): unable to fixup (regular) error at logical 229122052096 on dev /dev/mapper/sdn1
Mar 23 12:48:55 Tower kernel: BTRFS error (device dm-11): bdev /dev/mapper/sdn1 errs: wr 0, rd 351, flush 0, corrupt 0, gen 0
Mar 23 12:48:55 Tower kernel: BTRFS error (device dm-11): unable to fixup (regular) error at logical 229126705152 on dev /dev/mapper/sdn1
Mar 23 12:48:55 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 12:48:55 Tower kernel: sd 8:0:5:0: [sdn] tag#2974 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 23 12:48:55 Tower kernel: sd 8:0:5:0: [sdn] tag#2974 Sense Key : 0x3 [current] 
Mar 23 12:48:55 Tower kernel: sd 8:0:5:0: [sdn] tag#2974 ASC=0x11 ASCQ=0x0 
Mar 23 12:48:55 Tower kernel: sd 8:0:5:0: [sdn] tag#2974 CDB: opcode=0x28 28 00 1a ac f1 88 00 00 08 00
Mar 23 12:48:55 Tower kernel: critical medium error, dev sdn, sector 447541640 op 0x0:(READ) flags 0x800 phys_seg 1 prio class 2
Mar 23 12:48:55 Tower kernel: BTRFS error (device dm-11): bdev /dev/mapper/sdn1 errs: wr 0, rd 353, flush 0, corrupt 0, gen 0
Mar 23 12:48:55 Tower kernel: BTRFS error (device dm-11): unable to fixup (regular) error at logical 229123493888 on dev /dev/mapper/sdn1
Mar 23 12:48:55 Tower kernel: sd 8:0:5:0: Power-on or device reset occurred
Mar 23 12:49:29 Tower kernel: sd 8:0:5:0: [sdn] tag#1690 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 23 12:49:29 Tower kernel: sd 8:0:5:0: [sdn] tag#1690 Sense Key : 0x3 [current] 
Mar 23 12:49:29 Tower kernel: sd 8:0:5:0: [sdn] tag#1690 ASC=0x11 ASCQ=0x0 
Mar 23 12:49:29 Tower kernel: sd 8:0:5:0: [sdn] tag#1690 CDB: opcode=0x28 28 00 28 7e 86 68 00 01 00 00
Mar 23 12:49:29 Tower kernel: critical medium error, dev sdn, sector 679380584 op 0x0:(READ) flags 0x0 phys_seg 5 prio class 3
Mar 23 12:49:29 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)

__________________

Mar 23 12:55:48 Tower kernel: critical medium error, dev sdn, sector 1546039288 op 0x0:(READ) flags 0x800 phys_seg 1 prio class 2
Mar 23 12:55:48 Tower kernel: BTRFS warning (device dm-11): i/o error at logical 1215682310144 on dev /dev/mapper/sdn1, physical 791554289664, root 5, inode 194051, offset 44256493568, length 4096, links 1 (path: system/docker/docker.img)
Mar 23 12:55:48 Tower kernel: BTRFS error (device dm-11): bdev /dev/mapper/sdn1 errs: wr 0, rd 627, flush 0, corrupt 0, gen 0
Mar 23 12:55:48 Tower kernel: BTRFS error (device dm-11): unable to fixup (regular) error at logical 1215682310144 on dev /dev/mapper/sdn1
Mar 23 12:55:48 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 12:55:48 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 12:55:48 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 12:55:48 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 12:55:48 Tower kernel: sd 8:0:5:0: [sdn] tag#309 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 23 12:55:48 Tower kernel: sd 8:0:5:0: [sdn] tag#309 Sense Key : 0x3 [current] 
Mar 23 12:55:48 Tower kernel: sd 8:0:5:0: [sdn] tag#309 ASC=0x11 ASCQ=0x0 
Mar 23 12:55:48 Tower kernel: sd 8:0:5:0: [sdn] tag#309 CDB: opcode=0x28 28 00 5c 26 af 40 00 00 08 00
Mar 23 12:55:48 Tower kernel: critical medium error, dev sdn, sector 1546039104 op 0x0:(READ) flags 0x800 phys_seg 1 prio class 2
Mar 23 12:55:48 Tower kernel: BTRFS warning (device dm-11): i/o error at logical 1215682215936 on dev /dev/mapper/sdn1, physical 791554195456, root 5, inode 194051, offset 44256399360, length 4096, links 1 (path: system/docker/docker.img)
Mar 23 12:55:48 Tower kernel: BTRFS error (device dm-11): bdev /dev/mapper/sdn1 errs: wr 0, rd 628, flush 0, corrupt 0, gen 0
Mar 23 12:55:48 Tower kernel: BTRFS error (device dm-11): unable to fixup (regular) error at logical 1215682215936 on dev /dev/mapper/sdn1
Mar 23 12:55:49 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 12:55:49 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 12:55:49 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 12:55:49 Tower kernel: mpt2sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Mar 23 12:55:49 Tower kernel: sd 8:0:5:0: [sdn] tag#286 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Mar 23 12:55:49 Tower kernel: sd 8:0:5:0: [sdn] tag#286 Sense Key : 0x3 [current] 
Mar 23 12:55:49 Tower kernel: sd 8:0:5:0: [sdn] tag#286 ASC=0x11 ASCQ=0x0 
Mar 23 12:55:49 Tower kernel: sd 8:0:5:0: [sdn] tag#286 CDB: opcode=0x28 28 00 5c 26 af 58 00 00 08 00
Mar 23 12:55:49 Tower kernel: critical medium error, dev sdn, sector 1546039128 op 0x0:(READ) flags 0x800 phys_seg 1 prio class 2
Mar 23 12:55:49 Tower kernel: BTRFS warning (device dm-11): i/o error at logical 1215682228224 on dev /dev/mapper/sdn1, physical 791554207744, root 5, inode 194051, offset 44256411648, length 4096, links 1 (path: system/docker/docker.img)

 

Based on this my docker image is part of the problem so I probably need to recreate that. But it also seems there is something happening with the drive itself (possible the metadata?). If that is the case Im not entirely sure how to proceed. 

 

Any help would be appreciated

 

Thanks so much. 

Tower Diagnostics Mar 22.zip

Tower Diagnostics Mar 23 (3).zip

Edited by caelar900
Updating with more information

  • Quote
    • Community Expert

    Since one of the profiles is single you cannot remove a device, and unfortunately the single part of the data, and also most of it, is on the failed device (sdn):

      

                        Data      Data      Metadata System                             
Id Path             single    RAID1     RAID1    RAID1     Unallocated Total   Slack
-- ---------------- --------- --------- -------- --------- ----------- ------- -----
 1 /dev/mapper/sdn1 742.01GiB 104.00GiB  2.00GiB  64.00MiB  1014.93GiB 1.82TiB     -
 2 /dev/mapper/sdj1         - 104.00GiB  2.00GiB  64.00MiB     1.71TiB 1.82TiB     -
-- ---------------- --------- --------- -------- --------- ----------- ------- -----
   Total            742.01GiB 104.00GiB  2.00GiB  64.00MiB     2.71TiB 3.64TiB 0.00B
   Used              39.45GiB  99.04GiB  1.18GiB 128.00KiB

     

    I suggest that you try to copy what you can elsewhere and recreate the pool

  • Quote
    • Author

    Damn alright, that is pretty much what I feared. Appreciate you taking a look. 

    Whats the best way to get the data out of the pool and to the array in this case? Can I just use the mover for that or should i be doing it manually? 

     

    Also given the logs are making it look like my docker image is corrupted should I deal with that first before moving it anywhere or will that not really matter. 

    Edited by caelar900

  • Quote
    • Author
    10 hours ago, JorgeB said:

    Since one of the profiles is single you cannot remove a device, and unfortunately the single part of the data, and also most of it, is on the failed device (sdn):

      

                        Data      Data      Metadata System                             
Id Path             single    RAID1     RAID1    RAID1     Unallocated Total   Slack
-- ---------------- --------- --------- -------- --------- ----------- ------- -----
 1 /dev/mapper/sdn1 742.01GiB 104.00GiB  2.00GiB  64.00MiB  1014.93GiB 1.82TiB     -
 2 /dev/mapper/sdj1         - 104.00GiB  2.00GiB  64.00MiB     1.71TiB 1.82TiB     -
-- ---------------- --------- --------- -------- --------- ----------- ------- -----
   Total            742.01GiB 104.00GiB  2.00GiB  64.00MiB     2.71TiB 3.64TiB 0.00B
   Used              39.45GiB  99.04GiB  1.18GiB 128.00KiB

     

    I suggest that you try to copy what you can elsewhere and recreate the pool

    Ive been plugging away at it all day and I think I might have solved the issue without needing to move everything off. Does this look right? Would it be safe to remove the drive now?

    Tower Diagnostics Mar 24 (1).zip

    Edited by caelar900

  • Quote
    • Community Expert
    57 minutes ago, caelar900 said:

    Would it be safe to remove the drive now?

    Should be OK now since it's only using raid1.

  • Quote
    • Like 1

    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.

    Guest
    Reply to this topic...
    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.