blackf0rk

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About blackf0rk

  • Rank
    Newbie
  1. Reporting on some unexpected behavior. Unraid version 6.8.3 Parity Check Tuning version 2021.01.19 See screenshot for my settings. What happened Parity check started early this morning as it was the 1st of the month. However, it's now 9am and the check is still going. I would've expected it to be paused. This is the first time I've noticed this happening. Since my initial installation of the plugin, I haven't changed its settings. I've always had it set up this way and it's been fine.
  2. To be clear, it seems like TRIM is working - just not all the way (I think). When I run a fstrim -a -v, I get this... root@Tower:~# fstrim -a -v /etc/libvirt: 920.6 MiB (965332992 bytes) trimmed on /dev/loop3 /var/lib/docker: 17.9 GiB (19178844160 bytes) trimmed on /dev/loop2 fstrim: /mnt/cache: FITRIM ioctl failed: Remote I/O error
  3. The SMART extended self-test completed without error tower-smart-20200223-1440.zip
  4. I'm getting the following errors and warnings when the trim service runs. I'm using the SSD as my cache device. Feb 22 08:46:08 Tower kernel: sd 7:0:5:0: [sdg] tag#2572 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 22 08:46:08 Tower kernel: sd 7:0:5:0: [sdg] tag#2572 Sense Key : 0x5 [current] Feb 22 08:46:08 Tower kernel: sd 7:0:5:0: [sdg] tag#2572 ASC=0x21 ASCQ=0x0 Feb 22 08:46:08 Tower kernel: sd 7:0:5:0: [sdg] tag#2572 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Feb 22 08:46:08 Tower kernel: print_req_error: critical target error, dev sdg, sector 1950394402 Feb 22