trurl
-
Posts
43882 -
Joined
-
Last visited
-
Days Won
137
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by trurl
-
-
8 minutes ago, doma_2345 said:
i ahve it set to '0' so my expectation is that it fills the cache drive right up, but that doesnt seem to happen it gets to 500gb
You are lucky it doesn't work as expected, you don't want to fill cache completely or you might corrupt it.
If it were working as you want, then 0 would never overflow since it will always have more than Minimum when it chooses a disk for a new file.
-
Doesn't happen to me, same version of chrome.
Do you have any adblockers or anything else that might interfere? You should always whitelist your server.
-
Share permissions only apply to users you have created for network access to shares. Do you mean you actually created a user named Nobody?
-
-
-
Those diagnostics are incomplete. Did you edit them?
Are you sure the files are not getting copied? Or do you maybe have Hide "dot" files set?
-
Probably a docker host path created that. Check all your dockers
-
You should always include Diagnostics in bug reports
-
2 minutes ago, jsc0 said:
Replace <user> with a valid user on your Unraid box
The only valid ssh user on Unraid is root.
-
-
13 minutes ago, limetech said:
Along with diagnostics.zip please
Already in first post, kind of hard to notice at bottom of screenshot.
SMART folder in diagnostics seems to think Gloway had been assigned as disk5 but is now missing.
Can you provide more details about that?
-
3 minutes ago, D.Romeleitis said:
I tried the stable 6.10.1. And now next version 6.10.2-RC3.
I have always the same effect since 6.10.0-RC3. 6.10.0-RC2 was the last version where I had no problem. Something must have been changed from RC2 to RC3.
As far as I know there is no rc3 for 6.10.2
3 minutes ago, D.Romeleitis said:Stock is the go file
Only this:
#!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp &
-
1 hour ago, D.Romeleitis said:
edited the go file
Use the stock go file
-
Post saved syslog anyway
-
Have you done memtest?
-
Can you post new diagnostics with the array started? Also setup syslog server so you can get us syslog after crash
-
2 hours ago, Michael Ganrer said:
Diagnostics zip for above comment
Not much to see without the array started.
-
Looks like something about your disk controller(s) changed the way the drives were identified.
How are these drives connected?
-
-
-
1 hour ago, Monteroman said:
So does this mean that I will indeed have to restore the array from a backup?
If you formatted disk2 and cache that is gone, but each of the other disks still has its data.
-
Format is NEVER part of rebuild. Format is a write operation. When you format a disk in the parity array, that write operation is treated just like any other, parity is updated. So after formatting a disk in the parity array, the only thing that can result from rebuilding that disk is a formatted disk.
Your diagnostics indicated filesystem corruption on disk2, cache, and the unassigned disk. None of these disks were missing or offline in your diagnostics, just corrupt.
Seems extremely unlikely upgrade related.
You should have asked for help in General Support before doing anything. Rebuilding was entirely the wrong approach to fixing your issues, and formatting any drive with data you want to keep is always a mistake.
-
-
1 hour ago, jbquintal said:
had to rollback
Not helpful without diagnostics
BTFRS bug turns the array disk into a mirror of the cache drive
in Stable Releases
Posted
Seems like it might be another manifestation of the problem mentioned here: