DarkMan83

Members
  • Posts

    97
  • Joined

  • Last visited

Everything posted by DarkMan83

  1. Hi there, i upgraded from Unraid v6.8.3 to v6.9.0-beta22 for testing. After that upgrade all my Shares disappeard in GUI under Shares. In the Server log i get errors like: emhttpd: error: get_filesystem_status, 6475: Operation not supported (95): getxattr: /mnt/user/... Those errors appear also for new Shares, never created before. I have no custom mounts under "/usr/mnt" and i have not modified any files. I can get it working again, if i create a share with the same name as before and than reboot. After that all shares are back again. But if i reboot several times they disappear again and i have to redo this procedure again. The SMBD log has no errors or stacktraces. Currently i have it working, but it could go to the "no shares" state again on reboot. If this happens again, i will provide a diagnostics.zip here... Greetings Dark thebeast-diagnostics-20200706-2101-shares-visible.zip
  2. Is this still worked on? How to set driver to use for sensors? I have to use the LAN_2_0 instead of LAN....
  3. Don't worry, i fixed it! Had to rename all Share CFG's on the flash, so they get recreated!
  4. Where do the share configs go for the new unraid version? When i upgrade to 6.9-22 all my shares are gone...
  5. Du kannst die Konformität aber nicht beibehalten, wenn es vom Layout her nicht passt und wir die Ansage haben, dass an dem Layout nichts gemacht wird (Breite, usw.) Ich hatte das Thema schon angesprochen, dass es schlecht ist, das Layout an Englisch zu orientieren, da die Wörter in Englisch meist viel kürzer, als in anderen Sprachen sind. Aber lässt sich halt nix dran ändern, Vorgaben sind Vorgaben. Gruß Dark
  6. Ich war mal so frech und habe einen Pull-Request gemacht, vielleicht ergeben meine Änderungen ja SINN!
  7. Oh, ganz schön was los hier... Und da immer geschrieben wird "Professional translator" und hier schon so viele sind, fühle ich mich nun nicht angesprochen **Update** Und nun hab ich mir die Übersetzungen Mal angeschaut, besser als nichts. Vieles passt halt noch nicht ganz, denn man darf nicht immer wortwörtlich übersetzen, aber das wird schon werden.
  8. Format the stick with fat32 with default windows dialog and name it UNRAID Download zip from unraid site and unzip to stick. Than execute make bootable in usb folder on stick.
  9. Yeah, i see. I investigated further, but couldn't find where the disks.ini is generated. Maybe a user script updatiung the temps in that ini file would temp fix this problem, until it gets picked up and worked on... Or modify the rc.diskinfo php script for writing that info into the ini file.
  10. Was there ever an solotion? Im still facing this problem...
  11. I have the same problem with an WD40EFAX, which is clearly identified as a SMR drive by me, which cloud/should have in it's SMART data the TRIM command listed as available. I dunno whats the method for checking if it's actually an SSD used by this plugin, but this could be the problem? Greetings Dark
  12. Good diggin dude. I'm currently facing the same problem, also found another topic in the search results, which seems to be no more existant. So, this seems to be true for all custom controller types... And this is really bad, if you use some control mechs, like hdd temp dependant functions to be executed... If there's no other topic about this problem, do we need to push it to bugs? This is freaking me out like hell, im just a few days on unRaid and for my old QNAP the IT-Chip not workin, but the hdd temps are there. And for my HP DL380p the hdd temps not working, this one frustrates even more. If there would be any source code for this, i would digg it together my self But for now i just have to go to sleep, because the next day is monday! YAY! Work work work...Coding to rule the World.
  13. Hi, i have QNAP TS-1677x with AMD inside. I was trying to get all those temps and other things working, i did some google digging and found, that it must be using the IT8528 chip/board, because sensors-detect ist complaining. But it seems unRaid did not activate the kernel modules on compile, hopefully. If the iManager driver would be baked into the kernel, it could get me the: Temps, GPIO (LCD), FANS and LED's control - Maybe not until 6.9 unRaid release. sensors-detect showed this: Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): Probing for Super-I/O at 0x2e/0x2f Trying family National Semiconductor/ITE'... Yes Found unknown chip with ID 0x8528 So after soe Gooling i found: https://lore.kernel.org/patchwork/patch/634176/ https://lwn.net/Articles/705319/ https://github.com/rvido/iManager Would be so nice, if these QNAP Hardware would work on unRaid, so i could beat them on e.g. Facebook, as they refused to give me support for their product and only said: Use compatible NVME -> which is in QNAP case never updated since 2018 and the fastest NVME's are 530 MB/s, this made the NVME's obsolete, as my normal SATA SSD already got 560 MB/s 😞 I would be so thankfully, if someone has any idea on getting this working, or bring it to the next unRaid version or the dynamix temperature plugin, i would buy you a beer 🙂 Greetings Dark
  14. Doesn't the CA Plugin "Mover Tuning" do what you want?
  15. Heyho folks, today after restarting the server i get the following, which tells me nothing from user perspective...
  16. Hi there, this is gonna be my first post. My problem seems similiar to this Problem: I have 3 docker running (Plex, AdGuardHome, CrushFtp9) which are set to use br0 and set to autostart. However each time i restart the unRaid-Server my dockers stop working. I get that "No Container" problem mentioned in that Topic. If i go into the container settings i noticed, that the br0 disappeared from the dropdown for the networking mode of that container. Than i can restart the docker service, which gets me rid of the "No Container" problem. But after that i get "Bad Arguments" error for each docker mentioned. To fix that, i have to go into settings and reassign br0, which is available again in the dropdown, after restarting the docker service. For me it seems, that the docker service is started before the networking initialized, could that be? I can't seem to find any solution in that other topic or in the Forums. P.S. I got stalled devices after restarting, because they use the AdGuardHome DNS, which refuses to start. Greetings Dark