nathan909

I'm also having the same issue Same here

Sorry for my ignorance Jorge, but is the drive bad or is there something preventing it from being attached to the array or readable from unassigned devices? I couldn't get drive attributes until a replace drive on array, and when I stop the array, it shows "array" likes it wants to be attached to an array

As soon as I put a new drive in place of it on the array, the old (sdf) drive became accessible: is they anything i can do to add it back or copy the files off it?

How do I remove this disk so it doesn't show that it's part of an array?

OK, if that's the case. Unfortunately, I have no one to blame but myself. I also sent you a cup of coffee, I appreciate you helping out

Here ya go nas-diagnostics-20240722-0849.zip

FYI, this drive was spun down, so I'm confident nothing was being written to it. It was FULL, with about 14tb of only media movies & tv shows. I would like to put it back online and rebuild the parity. Thanks again Nathan

Hope this helps?! nas-diagnostics-20240721-1729.zip

So I was playing with some power management wires (which I should not have been doing while the array was on). Nothing was being written, and drives were spun down, but I heard one spin up as unpledged power. I'm sure I've messed things up by trying to read the forms and not know exactly what I was doing using New Config and started the array which started to rebuild the parity drive with the drive not in place. It won't let me assign the drive back to its original assignment (not in drop down) it listed in unassigned I guess in short how can I bring the drive back on and rebuild the parity? here some of the drive log: Jul 21 14:08:01 NAS kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jul 21 14:08:01 NAS kernel: ata5.00: irq_stat 0x40000001 Jul 21 14:08:01 NAS kernel: ata5.00: failed command: READ DMA EXT Jul 21 14:08:01 NAS kernel: ata5.00: cmd 25/00:08:80:ff:df/00:00:5d:06:00/e0 tag 24 dma 4096 in Jul 21 14:08:01 NAS kernel: ata5.00: status: { DRDY SENSE ERR } Jul 21 14:08:01 NAS kernel: ata5.00: error: { UNC } Jul 21 14:08:01 NAS kernel: ata5.00: supports DRM functions and may not be fully accessible Jul 21 14:08:01 NAS kernel: ata5.00: Read log 0x13 page 0x00 failed, Emask 0x1 Jul 21 14:08:01 NAS kernel: ata5.00: Read log 0x12 page 0x00 failed, Emask 0x1 Jul 21 14:08:01 NAS kernel: ata5.00: supports DRM functions and may not be fully accessible Jul 21 14:08:01 NAS kernel: ata5.00: Read log 0x13 page 0x00 failed, Emask 0x1 Jul 21 14:08:01 NAS kernel: ata5.00: Read log 0x12 page 0x00 failed, Emask 0x1 Jul 21 14:08:01 NAS kernel: ata5.00: configured for UDMA/133 Jul 21 14:08:01 NAS kernel: sd 5:0:0:0: [sdf] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jul 21 14:08:01 NAS kernel: sd 5:0:0:0: [sdf] tag#24 Sense Key : 0x3 [current] Jul 21 14:08:01 NAS kernel: sd 5:0:0:0: [sdf] tag#24 ASC=0x11 ASCQ=0x4 Jul 21 14:08:01 NAS kernel: sd 5:0:0:0: [sdf] tag#24 CDB: opcode=0x88 88 00 00 00 00 06 5d df ff 80 00 00 00 08 00 00 Jul 21 14:08:01 NAS kernel: I/O error, dev sdf, sector 27344764800 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Jul 21 14:08:01 NAS kernel: Buffer I/O error on dev sdf, logical block 3418095600, async page read Jul 21 14:08:01 NAS kernel: ata5: EH complete

I would like to track drive Start Stop counts, power on hours, and read/writes. Is there a tool that does this? Seems it would be beneficial stat tool for someone who wants to optimize spin down to save on power and heat without inflicting unneeded cycles.

OK perfect, THANKS! That did bring them both online and they are balancing So when complete, I am going about this the right way, or is there a better way? Stop Array, Shutdown PC Remove NVMe Install New NVMe boot unraid btrsf format new NVMe add new NVMe to pool with SSD start pool balance it remove SSD from pool balance it again now that I write this out there's gotta be a better way

I have home assistant running on a VM, my nortek zwave USB mounts upon boot 90% of the time. I uncheck the optional checkbox, not sure if that helps?

Thanks for your help Jorge, this is way above my head

root@NAS:~# btrfs-select-super -s 1 /dev/sdg1 using SB copy 1, bytenr 67108864 root@NAS:~# btrfs fi show Label: none uuid: 7a650073-3aaa-4476-ae27-7429a5b8c663 Total devices 1 FS bytes used 412.00KiB devid 1 size 1.00GiB used 126.38MiB path /dev/loop2 Label: none uuid: 3385c42f-7bc2-4191-ae99-8f03ddf305ab Total devices 2 FS bytes used 263.81GiB devid 1 size 465.76GiB used 430.03GiB path /dev/nvme0n1p1 devid 2 size 476.94GiB used 430.03GiB path /dev/sdg1

Yes, I mistakenly started to pool with the NVMe instead of the mirrored SSD, that is when i tried to reverse it and bring up the pool with the mirrored SSD, but that is when things went south. root@NAS:~# btrfs-select-super -s 1 /dev/nvme0n1p1 warning, device 2 is missing using SB copy 1, bytenr 67108864