trurl

Moderators
  • Content count

    10808
  • Joined

  • Last visited

Community Reputation

10 Good

About trurl

  • Rank
    Constructor
  • Birthday 12/26/54

Converted

  • Gender
    Male
  • Location
    North Carolina
  • Personal Text
    Constructor
  1. Update your sig, it says 5.0rc16b
  2. If you copy the files from the emulated drive to other drives in the array, it will be reading all disks to calculate the emulated data, then writing the array disk you are copying to plus writing the parity disk to update parity due to the write on that array disk. Another approach would be to copy the emulated data to another system on your network, or to another disk outside the array mounted with Unassigned Devices. This avoids further writing to your array and its parity drive until that data is safely copied elsewhere. You are still unprotected until New Config and parity resync, but perhaps less opportunity for another disk to fail. And copying the data back to the array would be done after New Config and parity resync.
  3. Seems to me you are doing the User Share Copy Bug, since /mnt/cache/domains is part of the user share at /mnt/user/domains.
  4. Normally, raid1 is what you get, which is what you are asking for. How did you manage to get it to raid0? See the V6 FAQ sticky at the top of this subforum. Lots there about managing cache.
  5. See Upgrading wiki linked in my sig, in particular, the section labeled: Files on flash drive
  6. The green up-arrow at the right of the post.
  7. Lots of lines similar to this in syslog Feb 26 00:03:44 Tower kernel: md: disk12 read error, sector=1000 Feb 26 00:03:44 Tower kernel: md: disk13 read error, sector=1000 Feb 26 00:03:44 Tower kernel: md: disk14 read error, sector=1000 Feb 26 00:03:44 Tower kernel: md: disk17 read error, sector=1000 Feb 26 00:03:44 Tower kernel: md: disk18 read error, sector=1000 Feb 26 00:03:44 Tower kernel: md: disk20 read error, sector=1000 Feb 26 00:03:44 Tower kernel: md: disk21 read error, sector=1000 Feb 26 00:03:44 Tower kernel: md: disk22 read error, sector=1000 Are these on the same controller?
  8. I still use this without problem.
  9. They shouldn't, but some make mistakes, and some don't really understand volume mapping.
  10. Misconfigured dockers.
  11. It will restore the drive to the emulated data, which isn't necessarily the same as the old data since it is possible to write to the emulated disk.
  12. I have my flash share set private and hidden so only I have access (I have other users on my network) and nobody can see it, I have to specify the path to access it. I would be fine with making the default to not share the flash. Anybody that needs to access it needs to know why and what they are going to do with it.
  13. Why do you care how fast your backup runs? Isn't it unattended? I don't cache much because most of my new data is either from downloads that are unattended, or from scheduled backups that are unattended. Much of it happens in the middle of the night and the data has parity-protection immediately.
  14. Will it boot without the new drive?
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.