Jump to content

Kir

Members
  • Content Count

    125
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Kir

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

537 profile views
  1. Totally uneventful upgrade, thank you!
  2. It's actually quite the opposite - nothing changes when I stop all dockers. These writes stop only when I disable the docker engine altogether. That's what makes it so puzzling...
  3. So... umm... nobody knows?
  4. Hi guys, Just realized that the number of writes on my cache pool drives keeps on rising up even when there is no activity. So I stopped all my dockers - no change. Only if I disable docker, this strange behavior stops. Any ideas? Thank you
  5. Now I feel stupid for misreading the version number 😏
  6. I think he meant that the latest version of Dynamix Syststats does not run on this release version of unRaid 6.7.0 - it requires a RC1 or higher. I observed the same behavior.
  7. I managed to do secure erase instead following this guide
  8. Damn, and I always thought it was working 😕 Since I can't move it to another controller (Supermicro cage), is there another command to issue?
  9. It's connected to the same controller as the other SSD, and I'm seeing this in the syslog: root: /var/lib/docker: 6.8 GiB (7294545920 bytes) trimmed
  10. blkdiscard: /dev/sdi: BLKDISCARD ioctl failed: Remote I/O error In log: Dec 18 16:31:12 Storage kernel: sd 1:0:8:0: [sdi] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Dec 18 16:31:12 Storage kernel: sd 1:0:8:0: [sdi] tag#3 Sense Key : 0x5 [current] Dec 18 16:31:12 Storage kernel: sd 1:0:8:0: [sdi] tag#3 ASC=0x21 ASCQ=0x0 Dec 18 16:31:12 Storage kernel: sd 1:0:8:0: [sdi] tag#3 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Dec 18 16:31:12 Storage kernel: print_req_error: critical target error, dev sdi, sector 998244232
  11. So open topics: 1. What's the consensus on overprovisioning of encrypted SSD cache drives? 2. Should I pre-clear a SSD?
  12. I can't believe nobody's done it before?
  13. And what about TRIM and overprovisioning?
  14. Hi guys, After going through encrypting my data drives and moving data back and forth, I'm ready for the next step- cache drive encryption. I have read some discussion on it, including the fact that TRIM is not supported at the dm-layer, so overprovisioning is the only option at the moment. I currently have the following: 1. 512Gb cache SSD drive with dockers only formatted btrfs 2. Empty 512Gb SSD drive, newly purchased, not added to the config Desired outcome: 2 mirrored cache drive formatted btrfs-enc Could somebody be so kind to list the steps of what needs to be done? Thank you
  15. That was it... Used "du -sh" to find one file that got partially moved, deleted it since it was still present in the source, and array is back online! Thank you, that was quite a scare 🙄