March 30, 20197 yr I keep getting cache drive errors in my system log like this Mar 29 19:04:27 BracServUltra kernel: loop: Write error at byte offset 6786011136, length 4096. Mar 29 19:04:27 BracServUltra kernel: print_req_error: I/O error, dev loop3, sector 13253928 Mar 29 19:04:27 BracServUltra kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Mar 29 19:31:01 BracServUltra kernel: nzbget[3958]: segfault at 18 ip 00000000007dad27 sp 000015351fe9a810 error 4 in nzbget[400000+644000] Mar 29 19:31:01 BracServUltra kernel: Code: 89 24 24 e9 4d f9 ff ff 49 8b 75 08 49 89 f7 49 83 e7 f8 4c 39 fd 0f 87 98 02 00 00 49 8b 45 10 4d 89 fc 49 8b 55 18 49 29 ec <48> 8b 48 18 49 39 cd 0f 85 fd 00 00 00 4c 3b 6a 10 0f 85 f3 00 00 Mar 29 19:36:39 BracServUltra kernel: nzbget[32053]: segfault at 0 ip 000000000080ba8f sp 000014a540cd7f08 error 4 in nzbget[400000+644000] Mar 29 19:36:39 BracServUltra kernel: Code: bc d1 f3 0f 7f 27 f3 0f 7f 6f 10 f3 0f 7f 77 20 f3 0f 7f 7f 30 49 83 c0 0f 49 29 d0 48 8d 7c 17 31 e9 95 0b 00 00 66 0f ef c0 <f3> 0f 6f 0e f3 0f 6f 56 10 66 0f 74 c1 66 0f d7 d0 49 83 f8 11 0f Mar 29 21:16:08 BracServUltra ool www[6217]: /usr/local/emhttp/plugins/dynamix/scripts/btrfs_balance 'start' '/mnt/cache' '' Mar 29 21:16:08 BracServUltra kernel: BTRFS info (device sdd1): 467 enospc errors during balance root@BracServUltra:~# btrfs fi show /mnt/cache Label: none uuid: fcf0f6cd-2637-4166-87d9-cba4ec5a7d38 Total devices 2 FS bytes used 927.60GiB devid 1 size 931.51GiB used 465.76GiB path /dev/sdd1 devid 2 size 465.76GiB used 465.76GiB path /dev/sdc1 root@BracServUltra:~# btrfs fi df /mnt/cache Data, RAID0: total=925.46GiB, used=925.46GiB System, RAID1: total=32.00MiB, used=96.00KiB Metadata, RAID1: total=3.00GiB, used=2.14GiB GlobalReserve, single: total=512.00MiB, used=96.00KiB root@BracServUltra:~# btrfs device stats /mnt/cache [/dev/sdd1].write_io_errs 0 [/dev/sdd1].read_io_errs 0 [/dev/sdd1].flush_io_errs 0 [/dev/sdd1].corruption_errs 0 [/dev/sdd1].generation_errs 0 [/dev/sdc1].write_io_errs 0 [/dev/sdc1].read_io_errs 0 [/dev/sdc1].flush_io_errs 0 [/dev/sdc1].corruption_errs 0 [/dev/sdc1].generation_errs 0 I had a total of 3 cache drives one was a sandisk 480G I removed it because I thought it was faulty. bracservultra-diagnostics-20190330-0121.zip
March 30, 20197 yr Community Expert There are some strange errors, possibly related to the controller, connect all SSDs to the Intel SATA ports, if nothing else it will enable trim support.
March 30, 20197 yr Author 5 hours ago, johnnie.black said: There are some strange errors, possibly related to the controller, connect all SSDs to the Intel SATA ports, if nothing else it will enable trim support. My other drives are fine with the card though? I had an error for SDC i got replacement coming
March 30, 20197 yr Community Expert 2 minutes ago, MrBrac said: My other drives are fine with the card though? No, there are errors with all the SSDs: Mar 29 10:48:19 BracServUltra kernel: sd 7:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Mar 29 10:48:19 BracServUltra kernel: sd 7:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 13 a0 45 80 00 00 c0 00 Mar 29 10:48:19 BracServUltra kernel: print_req_error: I/O error, dev sdb, sector 329270656 Mar 29 10:55:07 BracServUltra kernel: sd 7:0:1:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Mar 29 10:55:07 BracServUltra kernel: sd 7:0:1:0: [sdc] tag#0 Sense Key : 0x5 [current] Mar 29 10:55:07 BracServUltra kernel: sd 7:0:1:0: [sdc] tag#0 ASC=0x21 ASCQ=0x0 Mar 29 10:55:07 BracServUltra kernel: sd 7:0:1:0: [sdc] tag#0 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Mar 29 10:55:07 BracServUltra kernel: print_req_error: critical target error, dev sdc, sector 975175744 Mar 29 10:55:04 BracServUltra kernel: sd 7:0:2:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Mar 29 10:55:04 BracServUltra kernel: sd 7:0:2:0: [sdd] tag#0 Sense Key : 0x5 [current] Mar 29 10:55:04 BracServUltra kernel: sd 7:0:2:0: [sdd] tag#0 ASC=0x21 ASCQ=0x0 Mar 29 10:55:04 BracServUltra kernel: sd 7:0:2:0: [sdd] tag#0 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Mar 29 10:55:04 BracServUltra kernel: print_req_error: critical target error, dev sdd, sector 1952448576 And like mentioned, trim won't work on the LSI, so not the recommended place to connect SSDs anyway.
March 30, 20197 yr Author Just now, johnnie.black said: No, there are errors with all the SSDs: Mar 29 10:48:19 BracServUltra kernel: sd 7:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Mar 29 10:48:19 BracServUltra kernel: sd 7:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 13 a0 45 80 00 00 c0 00 Mar 29 10:48:19 BracServUltra kernel: print_req_error: I/O error, dev sdb, sector 329270656 Mar 29 10:55:07 BracServUltra kernel: sd 7:0:1:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Mar 29 10:55:07 BracServUltra kernel: sd 7:0:1:0: [sdc] tag#0 Sense Key : 0x5 [current] Mar 29 10:55:07 BracServUltra kernel: sd 7:0:1:0: [sdc] tag#0 ASC=0x21 ASCQ=0x0 Mar 29 10:55:07 BracServUltra kernel: sd 7:0:1:0: [sdc] tag#0 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Mar 29 10:55:07 BracServUltra kernel: print_req_error: critical target error, dev sdc, sector 975175744 Mar 29 10:55:04 BracServUltra kernel: sd 7:0:2:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Mar 29 10:55:04 BracServUltra kernel: sd 7:0:2:0: [sdd] tag#0 Sense Key : 0x5 [current] Mar 29 10:55:04 BracServUltra kernel: sd 7:0:2:0: [sdd] tag#0 ASC=0x21 ASCQ=0x0 Mar 29 10:55:04 BracServUltra kernel: sd 7:0:2:0: [sdd] tag#0 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Mar 29 10:55:04 BracServUltra kernel: print_req_error: critical target error, dev sdd, sector 1952448576 And like mentioned, trim won't work on the LSI, so not the recommended place to connect SSDs anyway. Ok if I connect my drives to LSI will unraid lose them? like the placement.
March 30, 20197 yr Community Expert Just now, MrBrac said: Ok if I connect my drives to LSI will unraid lose them? like the placement. No, devices are tracked by their serial number, not by controller and/or port where they are connected.
March 30, 20197 yr Author Just now, johnnie.black said: No, devices are tracked by their serial number, not by controller and/or port where they are connected. Ok thank you I will re organize my drives.
March 31, 20197 yr Author Ok It was minor pain lost 2 disks but I got em all back now SSDS all 3 are on my sata intels. I am gonna delete docker and do fresh test.
Archived
This topic is now archived and is closed to further replies.