-
Posts
10,186 -
Joined
-
Last visited
-
Days Won
196
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by limetech
-
-
12 hours ago, peter76 said:
okay thats true for 6.10.0-rc1,
but in 6.9.2 I had user shares enabled - and they where disabled in 6.10.0-rc1:
I could fix the problem - but less experienced users could have the same issue - and they get DOCKER and LIBVIRT (and maybe other) problems without a warning, and without a hint how to fix it.
EDIT: yes this is a bug introduced in a change that set new user shares to not be exported by default - changed one too many share-related settings. But below applies and how it's supposed to work. In your case to solve this to Settings/Global Share Settings and enable user shares. sorry about that.
The "new defaults" only have to do with new configurations, they are not changed by updating to this release with one exception. The issue I see in diags is that your 'config/share.cfg' file is simply absent. Not sure what could have happened to it. Do you see that file in your flash backup?
Exception: on Management Access page, the default for "Use SSL/TLS" is "Auto" but that is incompatible with other changes we made in this area having to do with Let's Encrypt SSL certs. If a server is upgraded to 6.10 and that setting is set to "Auto" and a LE cert does not exist, then we will set the variable to "no" (which is how it behaves with these conditions in 6.9 anyway).
-
-
On the Management Settings page what is the setting for "Use SSL/TLS"?
-
On 7/28/2021 at 6:28 AM, chris0583 said:
I hate silence from tech companies. At least give some BS canned answer like "we are looking into the issue". When you email support they say go to the forums and check.......... 🙄
Sorry I've been head down in development and other responsibilities the last couple of months and didn't see this until a developer we've been working with pointed it out.
We don't always have all the answers but you'll get no B.S. from me and you can always email directly:
-
3 hours ago, bonienl said:
/proc/diskstats
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.
-
3 hours ago, bonienl said:
The current implementation in the GUI is a kind of a hack. Before starting the long self-test it will change the spin-down timer setting to "never" and restores it to original setting once the self-test is completed. Though setting restoral doesn't always work.
If you plan changes, we should address the GUI too and make it a proper solution inline with emhttpd.
I, umm..., ripped that code out, I think for 6.9.1? maybe 6.9.0.
-
7 minutes ago, bonienl said:
Can you enable syslog mirroring to the flash device? This would help capturing the events.
...and be sure to disable at some point since that is going to write to the flash quite a bit.
- 1
-
Could be faulty hardware - can't rule that out.
-
6 hours ago, bonienl said:
Apr 8 12:07:12 vesta emhttpd: read SMART /dev/sdb
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.
-
12 hours ago, John_M said:
The behaviour in Unraid 6.9.2 is the same.
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.
- 1
-
Changed Status to Retest
-
There's a longstanding kernel bug that flags usb flash media as "rotational". We'll try and a get a proper fix in.
-
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
- 1
-
There were some changes in that driver in kernel 5.10.26
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.26
Unraid 6.9.2 will include those changes.
-
7 minutes ago, bonienl said:
There is an interesting kernel bug fix, which looks like our case https://lkml.org/lkml/2021/3/29/499
I don't know if this already available in a linux version for Unraid, perhaps @limetech can tell?
Interesting. Unraid OS 6.9.1 is on kernel 5.10.21 and the referenced patch is not applied. Upcoming 6.9.2 release is on kernel 5.10.27 which does have the patch. Working on finalizing the release now.
- 1
- 4
-
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.
- 1
-
Yes that's a bug. The comments field are what shows up alongside shares when you browse the server via Windows Explorer and are associated with volumes. Parity devices are not volumes.
-
You can run the self-test with array Stopped.
-
1 hour ago, CS01-HS said:
Is there a risk of data corruption if unraid spins down the disk while another partition is being written to? That'd be my only concern.
Shouldn't be. What will happen is disk will spin right back up. Use of multiple partitions is not supported at this time.
- 1
-
Changed Status to Closed
-
Changed Status to Closed
-
Changed Status to Closed
-
We only monitor partition 1.
-
48 minutes ago, Zotarios said:
It's solved in 6.9.1 but, i have aliased "exit" to "e" and when typing "e" it reconnects. Any way to change this behaviour?
Works for me.
Unraid OS version 6.10.0-rc1 available
-
-
-
-
-
in Prereleases
Posted
What URL are you referring to? Also you should be able to go to Update OS page and select to install the previous release.