peter76
-
Posts
44 -
Joined
-
Last visited
peter76's Achievements
Rookie (2/14)
4
Reputation
-
My ZFS-HDD Pool containing 3 HDDs works well and HDDs sleep correctly. Problem: When I open the Unraid-Dashboard in Browser, all HDDs wake up instantly. => they should stay sleeping!! HOW TO REPRODUCE: - Close Browser - Wait until HDDs sleep - Open WEB UI Dashboard in Browser - HDDs wake up instantly now How I found the reason for HDDs waking up: - reboot Server in SAFE MODE => no problem, HDDs stay spun down, even when loading Web-UI - reboot Server to normal mode - remove Plugins, one by one ===>>> ZFS MASTER and Dynamix File Manager Plugins were the reason for spinning up HDDs (every time loading MAIN tab of Web-UI) <<<=== tower-diagnostics-20231214-0951.zip
-
Limiting a Share size should be a basic feature on a Data Server. please!! make this (simple) feature available asap
-
user should get informed about this 10% ( the 0 showen is not correct in this case). user should also get informed about the reason, when creating the share fails. "add share" button should be deactive when there is to less space available..
-
thank you for the hint, I think now I can explain what's happened: -- creating new share on zfs pool with low free space GOES WRONG: - having "Minimum free space" in zfs pool settings set to 1 KB - leave "Minimum free space" in share settings at standard value ( = 0 ) -- creating new share on zfs pool with low free space SUCCEEDS: - having "Minimum free space" in zfs pool settings set to 1 KB - set "Minimum free space" in share settings to a low value ( 1 KB ) => having in mind I have to fill in a value other than 0 creating new share succeeds now! => maybe the default value "0" should be explained in corresponding help text... ?
-
In case you mean "Minimum free space" with "share floor": I have set "Minimum free space:" to 1 KB and free space on corresponding zfs pool is 1.57TB Observation: when trying to create new share, there is no error message, but in status line of WebUI it shows "Array Started • Starting services..." I get rid of this message creating a new share on a pool with much free space so creation succeeds.
-
Changed Status to Solved
-
thanks for this information, now I understand what was happening, makes sense.. my learning: we have to be careful when operating manually in the deep of Unraids filesystem 🙂
-
I have a share "SysLog", shared via samba and used for Syslog-Server. I accidentialy created a Folder "Syslog/backups" (with "l" and not "L" !) calling "mkdir -p /mnt/user/Syslog/backups" now the were two folders: "/mnt/user/SysLog" and "/mnt/user/Syslog" on disk and showen in shares-tab. Samba Server now used the new (wrong) folder "Syslog" instead of "SysLog". This seems to be a bug and should be prevented in some way. My solution was stopping all Services (Docker, VM), the I was able to delete "/mnt/user/Syslog" via shares-tab (deleting in cli was not possible for me). After restarting Services everything was fine again 🙂 tower-diagnostics-20230716-1734.zip
-
I have the same issue on 6.12.3 creating new share on zfs pool with low free space (zfs_hdd in my case) still not possible. creating new share on zfs pool with much free space (zfs_ssd in my case) there is no problem. tower-diagnostics-20230716-1734.zip
-
hello, I'm having this issue now on Unraid 6.10.0-rc2 and UD 2022.01.02a. After 5 Minutes WebUI is accessible. ryzen7-x5750g-diagnostics-20220102-2332.zip
-
Bug Report: on Unraid 6.9.2 the Array doesn't start after replacing a (pre-attached) disk while preclear is running on another disk (I was waiting about 3 minutes). Server was not shut down, only Array was stopped while preclear was running on a non-array-disk. After stopping preclear (killing process via CLI) the array startet correctly and data-rebuild started correctly. A manual restart of preclear also was successfull. Solution suggestion: Unraid: Unraid should start the array even when a non-array disk is preclearing AND/OR Preclear Plugin: should stop work, when array is stopped (or started) tower-diagnostics-20210819-0926.zip
-
For me it's workin now - all Dockers are listed. Thank you for fixing!
-
no - this file doesn't exist, not on my running Server and not in older Backups.. 🙂
-
I'm having an issue where some Docker Containers are not listed in "Docker Auto Update Settings" - looking at "nextcloud_mariadb" which I had to update manually: => Why is "nextcloud_mariadb" not available in the list of "Docker Auto Update Settings" in the Plugin ?? => For me it seems to be a bug tower-diagnostics-20210808-1427.zip
-
I looks like I'm having the same bug - can't delete the "ugly" entrys:
