Zonediver

Members
  • Posts

    1467
  • Joined

  • Last visited

Everything posted by Zonediver

  1. Meines Wissens nach ist das garnicht möglich...
  2. Is this problem with "no reaction" after wakeup from sleep already solved at 6.10.3?
  3. Zonediver

    NVME error

    What is "Gloway"? Use Samsung-NVMEs - they are working.
  4. Changed Status to Open Changed Priority to Minor
  5. FYI: 6.10.2 still doesn't work with sleep - will this be fixed?
  6. Don't think so - did't try yet...
  7. As mentioned: The latest "clean/stable" iGPU supported is 10th gen...
  8. Normal time for a parity check is 8h/4TB. So 16TB takes ~32h My parity check with a 12TB parity disk takes ~24h
  9. Thats not what i need... My "need" looks like this: If all disks are spun down, send the server to sleep or shutdown. A specific time is not helpful because a lot of family-members outside are watching Plex - so i cant shutdown at a specific time... And THAT is my problem! With the sleep plugin and v6.9.2 all is working fine, with 6.10.1, nothing works anymore...
  10. The button in the GUI is working, but i dont have a script to do this automaticly...
  11. ...because the auto-shutdown is not working, if the disk are all "idle" and not "standby"...
  12. Thats not the point... After a reboot, all disk are active, and then went to "idle" and not "standby" - and if the disks are only "idle", the server is doing nothing. But you NEED the status "standby" to send the server to sleep or shutdown... I tried this several times... only a manual "push the button <spin down>" sends all disk to "standby". This propblem exists since more then 5 or 6 years and isn't fixed... and i guess will never been fixed... And this happens "always after a reboot". So after "every" reboot, you have to push this f.... button "only once" to send the disks to "standby" - then all is working... If you know a script, which can do this "push the button" trick, let me know 😉
  13. Interesting idea... i did not try this because the server-boot take ages - but i will try 👍 EDIT: There is an other problem: When the server boot up, it is necessary to send all disks to standby "by hand". If i dont do this, the server never went to sleep or in this case did not shutdown... So a shutdown is not an option.
  14. FYI: Sleep function (or Plugin) under unraid 6.10.1 not working properly. I did a Bug report but some told me, thats not a unraid-problem... Description of the problem: Under unraid 6.10.1, the server went to sleep as normal - no problems so far. After a wakeup, nothing is reachable... no ping, no GUI, no SSH. Only a poweroff and a reboot bring the server back to life. The problem: Electricity costs increased to 50 eurocent/kWh and this Sleep-function is essential! So i reverted back to 6.9.2
  15. Thanks for this Info - i thought "something after wakup" can maybe solve this problem... Will test this command 👍
  16. May 23 14:35:47 Horus kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) May 23 14:35:47 Horus kernel: ACPI Error: Aborting method \_PR.PR07._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
  17. At a price of 50(!) Euro-Cent for 1 kWh, it's ABSOLUTELY NECESSARY to have a sleep function. And by the way: It is working since 2010... Conclusion: v6.10 is not ready to work (yet) and must be refined... i go back to 6.9.2 and end this "experiment" now! My sys is a "life-sys" and this "must be run"... no time and desire to test...
  18. Only a poweroff and a reboot can fix this - and its reproducible...
  19. My server crashed again tonight... Machine was running, but no GUI, no SSH and no ping... Only a poweroff (over power supply switch) was possible...
  20. Did some tests... changing everything... eth0, eth1, general info, network traffic, 10s/30s/1m/2m... nothing... I was not able to reproduce this error - everything is working so far... The only thing is the scaling of the network graph - if the traffic was hjgh (20-70Mbit) and then low (below 1MBit), the graph did not properly scale back to a lower value... EDIT: Takes a little bit of time but then, also the low Bitrates are shown correctly
  21. So - reinstalled 6.10.1 - all is running and i cant reproduce this error... What i did (bevore it crashed), was to change the "interface" from "General Info" to "Network traffic" and then the GUI crashed. Maybe it happened, because i have two interfaces (eth0/eth1)