trurl

Moderators
  • Posts

    43637
  • Joined

  • Last visited

  • Days Won

    137

Everything posted by trurl

  1. These seem to be local IPs. Do you know what computer this is? Mar 14 16:08:45 VicTower login: FAILED LOGIN 1 FROM laptop-7gmqkf7u.lan FOR , Authentication failure
  2. Don't know what else to suggest. Does the monitor have controls you can use to adjust the resolution?
  3. You can maximize the Firefox browser window, and use the browsers builtin settings to zoom the display to however large you want. The terminal window can also be maximized, don't know how to zoom it. But, there is also the webUI terminal ( >_ ) on the main bar
  4. You should never format a disk that contains data you want to keep. Format is a write operation. It writes an empty filesystem to the disk. When you format a disk in the array, Unraid treats this write operation just as it does any other, by updating parity. So, after formatting a disk in the array, the only thing it can rebuild is an empty filesystem. Not enough information at this late date to know exactly what happened. If you had asked for help when you were having problems maybe we could have saved your data.
  5. User shares allow folders to span disks. Each file is contained completely on a single disk.
  6. I suspect disk2 is the disk you replaced, and it doesn't have much data on it. Probably you did something wrong with rebuild. Format is NEVER part of rebuild, for example. The current documentation is available from links at the top and bottom of the forum, and from the "manual" link in the lower right corner of your Unraid webUI.
  7. That is correct. Not sure what you read in my comment that would make you think otherwise. Each data disk is an independent filesystem that can be read all by itself on any Linux. Parity disk contains parity bits, which is all of the redundancy needed to allow the contents of one disk to be calculated from the contents of all the other disks. Parity is not magic or even complicated. See the link I gave.
  8. Understanding parity can help make some sense of this confusion. It isn't magic or even complicated. Since I just posted about this on another thread, I link it here:
  9. Parity contains none of your data. Parity is just an extra bit that allows a missing bit to be calculated from all the other bits. Parity by itself can rebuild nothing. All bits of all other disks must be reliably read to reliably rebuild a disk. This is basically the way parity works everywhere. Unraid just has its own implementation that allows each data disk to be accessed independently and so allows different sized disks in the parity array. https://docs.unraid.net/unraid-os/manual/what-is-unraid/#parity-protected-array
  10. You did this on the physical disks again? I ask because repairing the emulated disks is the usual method. If the physical disks are mountable then yes. Do they have lost+found folders after this additional repair?
  11. No trace of that plugin remaining. And I don't see any FSCK files on your flash drive that might indicate corruption. I don't see any reference to br0 in your diagnostics, but I'm a little out of my depth on complex networks
  12. Replacing parity is basically the same as replacing a data disk. Rebuild is all the same parity calculation across all the other disks. New Config not required at all.
  13. Do you have another copy of anything important and irreplaceable? Parity is not a substitute for backups. Plenty of ways to lose data besides failed disks, including user error.
  14. Rebuild makes the physical disks have the exact same contents as the emulated disks. That is all it can do.
  15. No, you have made them unmountable by trying to rebuild them. You will have to try to repair them again after rebuild finishes.
  16. What exactly do you mean by this? If you starting rebuilding on the physical disks, you have already altered their contents and they are most likely unmountable now.
  17. And you must allow it to rebuild parity, because parity is out-of-sync with the changes filesystem repair made to the physical disks.
  18. If you are happy with the physical contents of the disks, just go with that.
  19. There were actually 2 approaches to your problem fix the filesystems on the emulated disks and rebuild. fix the filesystems on the physical disks and New Config them back into the array. I would have recommended 1, but since you had already started doing 2, I just went ahead with that. It is still possible to do 1 if you want, and in some ways that would be more correct, Rebuild would recover any emulated writes, but since the filesystems were unmountable, it probably doesn't make much difference.
  20. The direct link I posted is exactly what I intended. Lots of things in the contents.