-
Content Count
9808 -
Joined
-
Last visited
-
Days Won
157
limetech last won the day on April 7
limetech had the most liked content!
Community Reputation
2274 HeroAbout limetech
-
Rank
Advanced Member
Converted
-
Gender
Undisclosed
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
With 6.9 it is possible to have plugins install modules, no need to recompile the kernel or the root file system.
-
[6.9.2] Parity Drive will not spin down via GUI
limetech commented on SimonF's report in Stable Releases
Try using /sys/block/sdX/stat # for the entire device /sys/block/sdX/sdX1/stat # for partition 1 on the device The smartctl command definitely increments both read command count and sectors read count for the entire device. I cannot reproduce this issue, which is to say, works for me. -
[6.9.0, 6.9.1, 6.9.2] Extended SMART self-test does not prevent spin-down
limetech commented on John_M's report in Stable Releases
I, umm..., ripped that code out, I think for 6.9.1? maybe 6.9.0. -
We're working on a design that lets driver plugins be automatically updated when we issue a release.
-
limetech started following [6.9.2] Parity Drive will not spin down via GUI and 6.9.1 network card instability
-
Could be faulty hardware - can't rule that out.
-
[6.9.2] Parity Drive will not spin down via GUI
limetech commented on SimonF's report in Stable Releases
That message is output as a result of seeing I/O on partition 1 of the device. That is, code has detected I/O counters have incremented since the last time they were checked (polled every second). If there has been I/O to partition 1 then we assume the device must be spun-up. The 'read SMART' command is then issued to get the device temperature. Specifically it looks at /sys/block/sdb/sdb1/stat Then adds the 3rd and 7th values (sectors read and sectors written). I don't see this happening on my test servers, but I don't have any SAS devices. -
[6.9.0, 6.9.1, 6.9.2] Extended SMART self-test does not prevent spin-down
limetech commented on John_M's report in Stable Releases
Ok we can check if self-test is in progress when we think it's time to spin-down and reset spin-down timer instead of spinning down. I'll add that to work queue for next release. -
[6.9.1] Setting warning/critical temperature in SMART settings not possible
limetech commented on hawihoney's report in Stable Releases
Changed Status to Retest -
limetech started following Unraid OS version 6.9.2 available
-
This release contains bug fixes and minor improvements. To upgrade: First create a backup of your USB flash boot device: Main/Flash/Flash Backup If you are running any 6.4 or later release, click 'Check for Updates' on the Tools/Update OS page. If you are running a pre-6.4 release, click 'Check for Updates' on the Plugins page. If the above doesn't work, navigate to Plugins/Install Plugin, select/copy/paste this plugin URL and click Install: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer.plg Bugs: If you discover a bu
- 105 replies
-
- 32
-
-
-
unRAID 6.9 trying to spindown Unassigned Thumb drives
limetech commented on GeneM's report in Stable Releases
There's a longstanding kernel bug that flags usb flash media as "rotational". We'll try and a get a proper fix in. -
Network Half Speed in one direction only
limetech commented on adolfotregosa's report in Stable Releases
For upcoming 6.9.2 we updated the realtek r8125 to version 9.005.01 (from 9.003.05). Might fix this, but since Realtek, might not -
limetech started following [6.8.3] [6.9.0] [6.9.1] shfs seems to ignore permissions
-
[6.8.3] [6.9.0] [6.9.1] shfs seems to ignore permissions
limetech commented on ken-ji's report in Stable Releases
Very interesting. To fix, open a Terminal window and type: echo 'shfsExtra="-o default_permissions"' > /boot/config/extra.cfg Then you must Stop/Start array. Also this will persist across reboots, hence to undo you must delete the file. This is a mount option that tells FUSE to let the kernel handle file system permissions. This used to be how FUSE worked by default and somewhere along the line it got changed, probably in transition from FUSE v2 to v3. This bug will get fixed in Unraid OS 6.10 where we can have a little beta testing before wider deployment.