gerard6110

Members
  • Content Count

    87
  • Joined

  • Last visited

Community Reputation

2 Neutral

About gerard6110

  • Rank
    Newbie

Converted

  • Gender
    Male

Recent Profile Visitors

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

  1. same here on all my 3 servers.
  2. Now on 6.9.2. Issue not solved. Still not spinning down due to read SMART .. May 19 13:23:56 Stacker emhttpd: read SMART /dev/sdh May 19 13:24:02 Stacker emhttpd: read SMART /dev/sdi May 19 13:24:11 Stacker emhttpd: read SMART /dev/sdl May 19 13:24:17 Stacker emhttpd: read SMART /dev/sdm May 19 13:48:48 Stacker emhttpd: spinning down /dev/sdf May 19 13:48:53 Stacker emhttpd: spinning down /dev/sdm May 19 13:54:27 Stacker emhttpd: spinning down /dev/sdl May 19 13:54:42 Stacker emhttpd: spinning down /dev/sdg May 19 13:56:36 Stacker emhttpd: spinning down /dev/sdi May
  3. Now on 6.9.2. Issue not solved. Still not spinning down due to read SMART .. May 19 13:23:56 Stacker emhttpd: read SMART /dev/sdh May 19 13:24:02 Stacker emhttpd: read SMART /dev/sdi May 19 13:24:11 Stacker emhttpd: read SMART /dev/sdl May 19 13:24:17 Stacker emhttpd: read SMART /dev/sdm May 19 13:48:48 Stacker emhttpd: spinning down /dev/sdf May 19 13:48:53 Stacker emhttpd: spinning down /dev/sdm May 19 13:54:27 Stacker emhttpd: spinning down /dev/sdl May 19 13:54:42 Stacker emhttpd: spinning down /dev/sdg May 19 13:56:36 Stacker emhttpd: spinning down /dev/sd
  4. As SpaceInvaderOne's excellent videos will cover 6.9.x from now on, I decided to put all my three servers on it, despite one of them without WOL (and basically having to run up and down as it is a media - and main backup server not running all the time). So today I went in deep trying to fix it. Which I found / did! Apparently, the command "Custom commands before sleep:" in the Sleep plugin "ethtool -s eth0 wol g" is not being executed. By just removing the command from the Sleep plugin, and creating a bash script to run at each array start the WOL is operational again
  5. As SpaceInvaderOne's excellent videos will cover 6.9.x from now on, I decided to put all my three servers on it, despite one of them without WOL (and basically having to run up and down as it is a media - and main backup server not running all the time). So today I went in deep trying to fix it. Which I found / did! Apparently, the command "Custom commands before sleep:" in the Sleep plugin "ethtool -s eth0 wol g" is not being executed. By just removing the command from the Sleep plugin, and creating a bash script to run at each array start the WOL is operational again
  6. You are absolutely right. It happened to me too. Changing time outs didn't help. Just by coincidence I played around with the vm-guest additon after updating to the latest virtio driver. It then worked. For this server it was important as it is one with a daily VM and basically shutdown after use (I believe sleep didn't work). But not on my other server, where no windows VM is running; only an XPEnology NAS - for which I don't think there is a guest VM addition. There I still have a parity check after controlled rebooting from dashboard. Fortunately that (small) ser
  7. Without VM running new boot after shutdown is fine - no parity check. With VM running and then shutdown and then boot always parity check; no matter the time-out value in disk settings; tried upto 300 seconds. So also this server back to 6.8.3 again as 6.9.1 is not bringing me anything useful, except problems.
  8. It was / is working fine in 6.8.3 so back to that again. But dad to format during write because syncing indefinitely, and then use make_bootable to fix it.
  9. Already complained with earlier 6.9 versions, but still broken. Apparently no one uses wake on lan on unraid with 6.9.x?!
  10. Hi, before trying again, is wake-on-lan fixed with this release? I've tried beta22 and beta25, both not working and thus returning to 6.8.3 with the hassle of re-allocating the drives (with the risk of losing data if done wrong).
  11. After upgrading to above beta version I can no longer WOL that server. The g WOL option was enabled in the "Sleep" plugin (as before). The ethtool ... instruction was never required before, but after upgrading it was there in the box Custom commands before sleep. This did not help. Than I removed it (to restore the situation as before). Again to no avail. Then re-added the instruction to both the before and after box. Again to no avail. Note: Instead of sleep I had to use shutdown, because of an SAS addon card which would otherwise not initialize and thus missing a num
  12. After problems with beta22 I thought to give 25 a go. Bad idea! VM's running 100% on all 10 cores! but no display. Lights on AMD cooler gone. Not happy at all. I hope it is only a matter of restoring the flash drive, like with 25.
  13. Hi ViproXX, could you share your script for issuing the nvidia-smi -pm 1 command, particularly as I have two identical GTX 1660 super videocards used for two separate gaming VMs (for in-home streaming) and a normal VM (but not always running). Does one use its UUID or how does one send the command to the correct GPU? Note: As at least one GPU is used for one gaming VM or the normal VM, I already have scripts (to run in the background) to shutdown one VM, wait for 30 secs and then start another VM. This works perfectly. And then it would be nice to have in the same script add t
  14. To Johnnie: Thanks for the explanation. As going back to pre 6.9 is therefore quite an issue (because of the major system changes), my suggeston would be that upgrading to 6.9 would only be allowed after a backup of the flash drive; at least a big warning to be displayed, like "WARNING: If you have a cache pool, a flash backup is mandatory, because if going back to pre 6.9 after upgrading to 6.9 you WILL loose your cache pool and therefore possibly all your dockers and VMs (if you have setup your system following our advice; on the cache only)".
  15. To piyper: I did not try that and was not the purpose of the thread. My purpose was only to have the license key on a separate USB (or at least at User's option) that in case that USB would become read-only, as happened to me two times now (albeit on two different systems), I would not have to go to Limetech to ask for a replacement license key, particularly as the 2nd time my USB become read-only it was already within 4 months (still don't know why this has happened and no tool available to fix it, because USB hardware issue). For Limetech it would not matter as the key is and shall remain li