Jump to content

trurl

Moderators
  • Posts

    44,363
  • Joined

  • Last visited

  • Days Won

    137

Everything posted by trurl

  1. Instead of SMART post your Diagnostics. Diagnostics includes SMART for all attached disks, syslog, and many other things that give us a more complete understanding of your configuration and situation. Go to Tools-Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.
  2. Obviously not unique so can't be licensed. You must use a different Flash.
  3. The disadvantage of this approach is you may not get support from most users on this forum, and will have to rely on the smaller number of users in this subforum.
  4. So are you saying that you edited the error message from rsync that you posted earlier and condensed that error message by replacing the serial number with "Drive"? Or are you saying that you think you have successfully changed the mount name to "Drive"? What do you get from the command line with this? ls -lah /mnt/disks
  5. I have merged your threads to keep the responses coordinated.
  6. Until you get your networking issues resolved it won't help to have CA installed since it won't be able to download anything anyway
  7. This thread isn't about docker it's about trying to download plugins. Is that your problem?
  8. Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post.
  9. Nothing obviously wrong or misconfigured. Syslog is in diagnostics, but it resets on reboot. To get syslog saved so you can post it after a crash, setup Syslog Server:
  10. Reboot into Unraid, then Go to Tools - Diagnostics and attach the complete Diagostics ZIP file to your NEXT post in this thread.
  11. It will keep going until you stop it. How long have you been running it?
  12. Lots of errors in syslog from this device: Jul 31 13:04:02 Tower kernel: sr 10:0:0:0: [sr0] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jul 31 13:04:02 Tower kernel: sr 10:0:0:0: [sr0] tag#5 Sense Key : 0x5 [current] Jul 31 13:04:02 Tower kernel: sr 10:0:0:0: [sr0] tag#5 ASC=0x64 ASCQ=0x0 Jul 31 13:04:02 Tower kernel: sr 10:0:0:0: [sr0] tag#5 CDB: opcode=0x28 28 00 00 00 00 01 00 00 01 00 Jul 31 13:04:02 Tower kernel: print_req_error: I/O error, dev sr0, sector 4 Any idea what that's about? I don't think it is a disk. SMART for disk2 looks OK, but it is showing as still disabled in those diagnostics. They are a few days old though. You said you rebuilt? Also those diagnostics are with the array not started, so there are some things they don't tell us, but nothing related to your question.
  13. Mover can't move open files, and it won't move duplicates. Go to Settings - Scheduler - Mover Settings and turn on Mover Logging and it may log why it isn't moving.
  14. Keeping appdata (and system) on cache is the usual way. If you have those on the array dockers will have performance impacted by the slower parity writes, and will also keep array disks spinning since those files will be open.
  15. Go to Tools - Diagnostic and attach the complete Diagnostics ZIP file to your NEXT post in this thread.
  16. Each user share has its own settings for whether and how it uses cache. You have some user shares that are not using cache and others that are. That is why I questioned whether you were actually writing to cache and not directly to the array. And I still don't know since you didn't really say. Also, your dockers are not configured to live on cache. Their performance will be impacted by slower parity writes, and they will keep array disks spinning since they will always have open files. Maybe same could be said for your VMs, I didn't check.
  17. You only need the config folder from the backup, except keep your new .key file.
  18. trurl

    Better Defaults

    Already split into this thread:
  19. You don't specifically mention if you are copying to a cached user share so there is still some question. By default, normal user shares are not cached.
  20. Looks like you scrolled some important information off the top of your screenshot, so we can't see parity or disk1. From diagnostics it looks like disk1 is unmountable and disk4 is disabled but emulated disk4 is mounted. SMART for disk1 looks OK but you do seem to be having connection issues with it. Are you sure it has good power? Did you capture the output of the filesystem check on disk1? Can you tell us any more about that?
  21. This thread is a few months old now. Since your problem is the "same" have you tried any of the suggestions in this thread?
×
×
  • Create New...