Lukáš Řádek

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

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

Lukáš Řádek's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Thanks. A situation that I feared with parity system is how to know if the parity error actually means that there is bad data on the parity drive (for example due to unclean shutdown) or on the data drive since that is the one that has been corrupted.
  2. Sure. But can I consider this case fixed by running the xfs file system repair? Or does it somehow affect parity?
  3. It sure does... but how about file system corruption? Or whatever might have happened to me.
  4. Alright, that fixed it, thank you 🙂. Follow up: What to do now? Can I just carry on since file system is not included in parity (don't know it that is the case) or can the parity be potentially affected? In that case should I trust parity or the data and rebuild?
  5. I got an alert saying "Disk 3 returned to a normal utilization level" which surprised me since it was quite high before and I didn't delete anything (substantial) from it. I have done some writes and deletes to a share that is located on that drive (among others). I checked the WebUI's Main page which said that the disk is at 2 TB used out of 8 TB total, which alarmed me quite a bit because before it was somewhere around 7 TB used. Since I have just one main share that holds all my data, I went to Shares page and computed the share's size. That turned out to show the correct disk space used - Disk 3 has 7.06 TB used (which is correct) BUT 5.97 TB free (which is impossible since it is 8 TB drive). Windows (via Samba) and Krusader also show the correct disk space used. BUT when inspecting disk's properties in Krusader, it shows the incorrect values again (in contrast to the Size in the same dialog). SMART short test of the disk ran without a problem. Other disks behave as normal. What do you make of this and what do you suggest I do? I assume this might not neccessarily be an UnRAID bug, but at least UnRAID could handle such situations and notify user that the filesystem is corrupted... possibly??? I am marking this as urgent since it can lead to false alarms and possible overreactions presuming data loss.
  6. It would be greatly appretiated to have access log for different features (VNC, samba, web UI). I know some can be probably read from syslog, but at least for the VNC, I haven't seen anything there. The use case for me is that I have had a security issue where somebody logged into my VM using VNC and while I managed to catch that pretty soon (for that specific session), I am not sure whether it is possible he logged in at some other point in the past. VNC log would help greatly in this case.
  7. I am on a 6.12.3 and the VNC Console Password is saved but when the VM is edited again, it is missing and if saved again, there is no password protection now... ie. you have to retype the password every time you edit the VM in order to be protected.
  8. Hello, I have had a possible malicious login to my UnRAID management (I can see a Share that I do not remember creating) and I am wondering how to get more info about what was happening. The supposed misuse came through VNC to my Windows WM running on UnRAID. I know he was logged in to my WM (using VNC), yet I do not know whether he was inside the management. 1) Is there any VNC login log, where I would be able to see when and how many time somebody logged in? 2) Is it possible to see details about Share creation and such. Thanks