trurl

Moderators
  • Posts

    37300
  • Joined

  • Last visited

  • Days Won

    125

trurl last won the day on September 22

trurl had the most liked content!

About trurl

  • Birthday 12/26/1954

Retained

  • Member Title
    Constructor

Converted

  • Gender
    Male
  • Location
    North Carolina
  • Personal Text
    http://paypal.me/trurtle

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

trurl's Achievements

Grand Master

Grand Master (14/14)

2.4k

Reputation

146

Community Answers

  1. Attach Diagnostics to your NEXT post in this thread
  2. So what you really meant to say was "the parity IS rebuilding"? Bad connections are much more common than bad disks, but when a write to a disk fails, Unraid has to kick it out of the array since it is out-of-sync. To get a disk enabled again it has to be rebuilt so it is in-sync. Attach diagnostics to your NEXT post in this thread and we will see where to go from here
  3. Mover won't replace files, so if any of those files already exist on the destination they won't be moved. You can examine in Dynamix File Manager
  4. So you don't mean it stopped by itself, you just mean it didn't autostart? Post new diagnostics
  5. So appdata does have those folders on disk1 and disk2. And rechecking your diagnostics from the first post in this thread, I see appdata had files on those 2 array disks then. If you disable Docker in Settings and run mover, they should get moved to cache_appdata.
  6. Parity cannot rebuild any data disk that was not in the array when parity was built. (how could it?) Just replace and rebuild, one at a time, keeping the original disks as backups until you are satisfied with the results. That is the normal way to upsize disks, I have done it many, many times, and it works very well. Your way is needlessly complicated, more prone to mistakes or other problems, and won't save any time.
  7. What do you get from command line with this? ls -lah /mnt/disk1/appdata and this? ls -lah /mnt/disk2/appdata
  8. Your appdata has some files on the array now. Also looked like domains had incorrect permissions. Do you have any VMs? What do you get from command line with this? ls -lah /mnt/user0/appdata
  9. Diagnostics already includes SMART for all attached disks so no need to attach it separately. SMART for new disk looks fine. I guess we can let rebuild test the disk and its connections. Follow these instructions carefully. If things don't seem to work as described, or you have questions, let us know. We will check some things along the way to see how well things are working. Go to Tools - Diagnostics, Retain All, Apply Reassign disk1, assign new disk as disk2 Check BOTH parity valid box AND maintenance mode box Then start the array and post new diagnostics and a screenshot of Array Devices Those steps will get disk1 back into the array, a new disk in disk2 slot, all other disks as is, and without actually mounting anything so parity and all disks are unchanged. The next steps (after we get diagnostics and screenshot) will disable disk2 so it can be rebuilt on the new disk.
  10. You mean transferring data from an array disk mounted read-only outside the array, onto another disk in that same array, while that same array is missing the disk ? ? ? Unless you have dual parity, an array with a missing disk has no parity protection.
  11. Makes absolutely no sense regardless of which disk you mean, which you don't even mention.
  12. Might depend on how the USB3 connection is implemented. Many USB enclosures won't even pass SMART data, and some can even affect the apparent size of a disk
  13. It will allow a 6TB parity drive as long as no data drives are larger than 6TB. You would have to New Config to get it to accept the smaller replacement. In order to avoid rebuilding both parity, you would have to New Config without that parity drive and check the parity valid box so it will accept the existing parity as is, then add that smaller parity disk so it can be rebuilt.
  14. To make this even clearer, even mounting an array disk as writeable outside the array will invalidate parity and require a full parity rebuild when you put it back in the array. Why do you want to do this anyway?