to put it very briefly, i spent close to a month trying to get 2 of my new drives to behave, they just contain steam games so nothing critical
no the disks are not bad, turns out both just had bad sata cables, i also checked on a test bench and both drives are fine hardware wise
yet weirdly still, every now n then on the odd reboot, one of the two panics and goes into read only mode
you can still see the files, a reboot or shutdown and come back later fixes it, but it is annoying that it keeps happening, and its not sata port dependant
both have btrfs, in fact my entire system does, and the rest of the other 17 disks in my systems have no issues, its only the two ssds i have mounted in the back of my pc
does anyone know why this is happening if all the hardware is verified as good? even checked the psu
dmesg isnt very happy about whats happening either, and tries to reset the sata link when this happens, repeatedly, where its suddenly unresponsive
2386.358895] sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[ 2386.358897] sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 0e 19 c0 00 00 20 00
[ 2386.358898] I/O error, dev sdc, sector 924096 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 2
[ 2386.358899] BTRFS error (device sdc1 state EA): bdev /dev/sdc1 errs: wr 14, rd 2931, flush 0, corrupt 0, ge
n 0
[ 2433.645390] scsi_io_completion_action: 815 callbacks suppressed
[ 2433.645396] sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[ 2433.645399] sd 6:0:0:0: [sdc] tag#0 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 0
0 00 e5 00
and then that spams for a billion lines