trurl

Moderators
  • Content count

    12362
  • Joined

  • Last visited

  • Days Won

    5

trurl last won the day on June 28

trurl had the most liked content!

Community Reputation

150 Very Good

3 Followers

About trurl

  • Rank
    Constructor
  • Birthday 12/26/54

Converted

  • Gender
    Male
  • Location
    North Carolina
  • Personal Text
    Constructor
  1. File System Explanation

    You should not be removing the drives. Removing a drive requires rebuilding parity. Formatting a drive while it is in the array preserves parity, since format is a write operation and unRAID updates parity any time an array disk is written. All format does (and all it means) is writing an empty root folder to the disk. To format a disk in the array after you have emptied it, stop the array, click on the drive to get to its settings page, and change its filesystem. unRAID will format the drive to the new filesystem when you start the array.
  2. Cache Drive Question

    Sounds like a good use case for Unassigned Device.
  3. Cache Drive Question

    You can only have one cache pool, which will treat all cache drives as one storage. An alternative is to use Unassigned Devices to mount a drive outside the array and use that as separate storage for dockers. Why exactly do you want to keep your temp data on a separate drive from your dockers? You can create shares on cache and keep the files separate that way. User shares are really just top level folders on the drives. See here for a more complete understanding of how user share cache settings work:
  4. The unassign-start steps are only needed to rebuild to the same disk, no need to forget when replacing. To rebuild to a new disk just stop-replace-assign new disk to same slot. It is not even necessary to clear the replacement, though many do just for testing.
  5. Parity typically will not help with corruption.
  6. Are you sure you don't want the data on disk6? With dual parity, it should be possible to rebuild it also. And it wasn't really necessary to copy files from the emulated disks to other disks in the array. You could have just rebuilt to save that data. Writing to other drives in the array while it's unprotected, or just reading other drives in the unprotected array to rebuild a disk. Which is more risky? I'm not sure. In the end though, you rebuilt anyway. so you have done both. I would have considered copying the data to drives not in the array (or to another system completely) instead of writing to drives in the unprotected array.
  7. What you're telling us doesn't really make any sense to us, so maybe post some screenshots of Main - Array Devices and Main - Array Operation to show us what you mean. Also post your complete diagnostics zip.
  8. Anytime you write to an md device, parity is maintained.
  9. Upgrade parity drive and then each disc in array

    1. You can't preclear a drive in the array, but you can preclear a drive while using the array for whatever, including rebuilding. 2. Changing filesystems will format the drive, so if you want to keep the files you must move them elsewhere first. This is unrelated to the process of replacing drives. Rebuilds can only rebuild to the same filesystem.
  10. If "everything is being duplicated onto the other drives" that should be fairly easy to demonstrate. Your screenshot doesn't.
  11. Since you said you have no parity, it should be simple and quick to just go to Tools - New Config and assign whatever disks you want to the array. You can copy files from the USB-HDD to the other disks before or after you New Config. If you do it after then you will need to use the Unassigned Devices plugin to mount the USB-HDD outside the array. As for the user shares, they are just the aggregate of the top level folders on cache and array disks. So whether you create the shares or not, they will exist if the top level folders exist. You must not mix user shares and disks when copying/moving or you can lose data. I always ssh and use mc (Midnight Commander) to move/copy between disks.
  12. Copy/paste from CA Config Editor to syntax-aware editor of choice. When finished editing, copy/paste from syntax-aware editor of choice to CA Config Editor. Etc.
  13. Make the appdata share private. That way only specified users have access. You can also make it hidden to prevent anyone else from even seeing it, but you can still get to it by specifying its path. As for managing plex plugins, the approach I always take is to just copy them to somewhere else on my server, then ssh and use mc (Midnight Commander) to move them where they belong. And another possibility for editing files directly on your server is to use Squid's own plugin, CA Config Editor.
  14. HELP!! CAN'T REPLACE BAD ARRAY DISK

    The "reported errors" is too vague to know what you mean. And you only posted SMART. You should always post the complete diagnostics zip unless we specifically ask for something less. Maybe you already know and aren't likely to make this mistake, but since you said something in your OP about formatting a replacement disk I will give you this additional warning. You absolutely must NOT format a disk as part of the rebuild process, even if unRAID says it is unformatted. Formatting a disk (or even the emulated disk) writes an empty filesystem to the disk. unRAID treats this write just like any other, by updating parity. So after a format of a disk (or emulated disk) in the array, parity agrees it has an empty filesystem. Obviously a bad thing if you were planning to rebuild its data.
  15. how to know exactly which HD failed?

    The Main page shows the serial number for each drive. The serial number is printed on the drive label.
Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.