b0m541

Members
  • Posts

    101
  • Joined

  • Last visited

Everything posted by b0m541

  1. If you do not see what I am talking about we just have different risk models at hand. That can happen. Good for you.
  2. Yes i could and I have, above and other times before, but its not of use as it contradicts the paradim under which the diags are collected. Concrete examples: user names, group names, drive IDs, ... If you give me diags and you give me a number of physical machines, I will always be able to identify the machine to which the diags belong. As long as we cannot avoid this, some people will not be willing to post diags in public.
  3. Yes i have. They have a lot of non-anon data, e.g. account names, and any combination of that many tech parameters would identify each system individually. It is a catch 22 if you make full diags your primary data source instead of guiding the user by educated questions.
  4. Fair enough and both understandable. I am still not comfy with posting diags in public and never will be.
  5. Ulitmately it is the user's data, maybe the user should decide Or: offer to look the diags that the user puts somewhere by using the URL they provide. There is no technical need to publish the diags publicly basically forever. What about that?
  6. I am sure there are always good intentions behind that, otherwise someone would not take the time to respond. Assuming that each user knows as few as possible and thus to get as much data as possible is a way to reduce back and forth, I get that. Just another example: Have you ever called a technical hotline and been treated like you know as few as possible ("have you turned on the device?", "is the power plug in?"). how does that feel? (I am not saying this is what happened here, but it is emphasizing the underlying assumption that someone doesn't know anything about the problem domain) I guess its impossible to know what someone knows when asking a question, but the person does not know the answer and the person may know a shitload more than you assume. I personally prefer to get targeted questions to provide information on point that is needed. it also ensures that I learn how to solve this problem on my own the next time. Just my 2 cents.
  7. Something I did not know before asking (which is why I asked) is that the parity will be rebuilt after successfully running "New config". Next time I know it. To be honest I do not see what a look at the diags will change about that: The question was how a parity rebuild can be manually triggered. And that can be answered with "run new config" no matter what the diags are saying. I perceive a tendency of some people primarily asking for diags, even if the answer to a question does not depend on the data in the diags, and rather not answering a question that could be answered easily and correctly without looking at the diags. People from different places have different notions of privacy, and for some - including me - needing to publicly post diags to get an answer to a question that can be answered without diags feels not right. To me it seems disproportionate, similar as when asking a physician which side effects a certain medication can have and the physician not answering that question before you "please get undressed except for the underpants". Of course the example is exaggerated, but here everything is public and archived for a long time, so that provision of information requires more consideration. Coming back to the concrete case, providing a screenshot is less of a privacy problem and I would have done that, had I not by then found a solution on my own.
  8. Fair enough, but to be also fair and clear, I also asked how the parity build can be manually triggered. That question could have been answered without access to the diags. That would have been greatly appreciated. Just my feedback.
  9. Due to lack of options I repeated this procedure: https://wiki.unraid.net/index.php/UnRAID_6_2/Storage_Management#Reset_the_array_configuration This time the result was as described in the Wiki, the content of the parity drives was invalidated and a parity rebuild started when I started the array. I do not understand why that did not happen the first time, but now it works.
  10. As far as I can see I can only start a Read Check, which is peculiar. The Wiki says: "A Read Check is also the type of check started if you have disabled drives present and the number of disabled drives is larger than the number of parity drives." (https://wiki.unraid.net/Manual/Storage_Management#Read_check) Since I have 2 parity drives and I unassigned 2 drives I should be able to run a parity check or parity rebuild? This is what my original question was about: May i unassign 2 drives at the same time and then run a parity rebuild once? The answer was positive. Obviously it does not work like that.
  11. I am not a friend of publicly posting a whole lot of data mostly unrelated to the problem. If you let me know in which files to look, I happily do that on my own. The keyword "parity" does not occur in diagnostics files in "logs". The data transfers were not caused by a parity rebuild, I found a container that continuously write to a drive. After stopping this container there are mostly 0 reads and writes -> not a parity rebuild ongoing. So the question is, why unraid did not ask whether the parity is still valid and why it did not start a parity rebuild. Even more important, how would I trigger a parity rebuild now manually?
  12. I executed the procedure as described under the link in my previous post. It went a little bit different as in the description: unraid did not present an option to say "Partity is valid". It just wanted confirmation that I really want to start the array. The array is running now with 2 data drives being unassigned (and showing up in "Unassigned Devices" (just according to my plan). However, in "Array Operation" it says "Started, Array unprotected" In contrast to this it says in the "Main" view: Parity is valid. Reminder: 2 data drives unassigned, and there are 2 parity drives. Observing the Reads and Writes under "Main>Array Devices" it seems like it is doing a parity check or rebuild: it is reading from all drives and writing to the parity drives. But - nowhere on the UI it is saying that a parity rebuild is running. This behavior is - at least to me - confusing (mixed signals: Array unprotected vs Parity is valid; not saying that a parity rebuild is in process). Is it in fact rebuilding the parity now? How can I confirm this? Or do I need to trigger a parity rebuild? How? (6.9.2)
  13. My array uses 2 parity drives. I want to use the data drive removal procedure supported by limetech, not the one involving zeroing the drives. Using the following supported procedure (https://wiki.unraid.net/Manual/Storage_Management#Removing_data_disk.28s.29) to remove data drives, is it mandatory to run the procedure for each single data drive to be removed separately, or is it possible to empty several data drives and then remove them all together in one step to only need to rebuild parity once?
  14. I have been successfully using unbalance in the past, but that is a few years ago. When i tried to activate it today, nothing happened. The server did not start. In the logs I see the command used for starting unbalance and no subsequent errors. Any ideas what could cause this and how to fix it?
  15. The folders with the problem all had a trailing space character in the name. Remove it and it shows normal again via SMB. I guess this is a bug in the SMB server.
  16. I have a number of folders, all belonging to a series of music CDs, which show the correct folder name on the server, but on the SMB clients they show with the DOS 8 character folder names. I guess there must some mapping that works locally but not across SMB. It can be probably fixed by renaming? Any explanations whats happening?
  17. Recently LSIO have released their Readarr container. It would be awesome if we have a Readarr template for Unraid soon, so that not everyone need to make their own template.
  18. two things: (1) the data is not containing any names, but the combination of hardware and setup choices makes each configuration unique as thus trackable (2) the latter cannot be easily circumvented by replacing strings without sacrificing possibly crucial detail privacy always comes at a cost and can be achieved: instead of providing unnecessary data one can reveal necessary pieces of data step by step or to describe the idea what to look for to user so letting them do the actual work themselves, which also helps for future situations as the user learns how to do it but that's just my opinion.
  19. I see what you mean. I suggest to do this using private messages on this forum.
  20. Thanks for the explanation and the suggestion. I continue to disagree with the assessment regarding the diagnostics content. And we have been there before (you may want to go back in this thread and look it up). Its just not worth going in circles.
  21. diagnostics: We won't discuss this again as we did some time ago. I still fail to see why someone would insist on a full overshooting dataset without being willing or able to say what the person is actually looking for. It sure feels like stubbornness. But hey, someone could call me stubborn too, but I call it privacy. Yes, I have the "Plus" plugin installed. One further observation: when writing to the mounted SSD from the shell, unmount actually works, although the button afterwards still says "unmount" and is grey, while I would expect it to be orange and say: mount. However, if I click unmount after writing to the SSD usingg the Krusader container, there will still be some write operations, and then the disk is mounted again. Pressing unmount after this will actually unmount the SSD and the button will be orange and say "mount" as expected. Kind of confusing...
  22. Actually I was looking at the script log (empty), but the disk log says: unraid unassigned.devices: Unmounting '/dev/sdl1'. unraid unassigned.devices: Unmount cmd: /sbin/umount '/dev/sdl1' 2>&1 unraid unassigned.devices: Unmount of '/dev/sdl1' failed: 'umount: /mnt/disks/USB-2T-Vids: not mounted. ' Then why would the unmount button be shown, shouldn't the mount button be shown instead? Also although destructive mode is enabled, there a no buttons to format the SSD.