trurl
-
Posts
43889 -
Joined
-
Last visited
-
Days Won
137
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by trurl
-
-
That has log entries between
Feb 3 11:03:54
and
Feb 3 13:31:41
Were you experiencing the problem between those times?
-
That is just the syslog since boot. We need syslog saved by syslog server that includes the timestamps when the problem occurs.
-
-
btrfs seems to be especially prone to break if you fill it up too much. In general, whatever the filesystem, you should always keep some free space on each of your disks/pools.
You have no Minimum Free set for either of your pools. If a pool has less than Minimum Free, it will overflow to the array for shares that have Secondary storage.
-
The filesystem can be thought of as data about the data, or "metadata". It is not really the contents of the files, but instead, data about how the folders and files are organized and represented as bytes on the disks.
When files are written, this metadata is also updated so it can be used to retrieve the files. If something causes disk writes to fail, such as a bad connection or bad disk, not only can the file be wrong, but the metadata can be wrong. Wrong metadata is usually what is meant by corruption. It can cause problems retrieving existing files, and problems writing new files. Often the filesystem will be made readonly to prevent further damage.
Your diagnostics were without the array started, so I couldn't see anything about where your appdata was. Possibly some of it wasn't on the "disk share" you looked at. You can see how much of each disk/pool is used by each user share by clicking Compute... for the share on the User Shares page.
An automatic parity check when you boot is due to "unclean shutdown". Here is a link to a post which explains this in more detail:
and another link to the sticky thread in General Support discussing things to do if you are having problems shutting down cleanly:
https://forums.unraid.net/topic/69868-dealing-with-unclean-shutdowns/
-
You should consider the appdata backup plugin.
Also
7 hours ago, JorgeB said:a good idea to run memtest.
did you?
-
Moderators are just unpaid volunteers, not much different from your other fellow unraid users who try to help people on this forum, except we also volunteered for the extra work of moderation.
Sometimes we don't see your post immediately because we are in different time zones, and life gets in the way.
I hadn't seen any of this until just now. If you had requested additional explanation, and waited for it, you probably would have gotten it. Maybe sometimes you have to ask again
We read a lot of posts and might be busy with someone else with even bigger problems. I know I have been lately.
Glad you got it sorted out.
-
Have you done memtest?
-
1
-
-
Diagnostics required for bug reports.
https://forums.unraid.net/bug-reports/stable-releases/report-guidelines-r68/
USB not recommended for array or pools for many reasons
-
Quote
have Syslog server enabled and a share created to store the logs, but no files have been logged
You have to also specify the server you want them sent to
-
-
Browser cache?
-
Bug reports require diagnostics taken when the problem occurs. Technically, you should also test in SAFE mode.
-
Since you can expect it to display differently on different browsers due to resolution, etc., seems like you would want it to work this way.
-
4 hours ago, dopeytree said:
compile the backup USB stick in RAM
I think it does. Most things on Unraid try to avoid writing to flash drive.
-
Why is it using 1.6G? My flash drive only has 443M used
-
-
Changed Status to Closed
-
This seems to be about the Unassigned Devices plugin. Plugin issues do not belong in bug reports.
You can go directly to the correct support thread for any of your plugins by clicking its Support link on the Plugins page of your Unraid webUI.
Go to the Unassigned Devices plugin thread, explain your problem, and include your diagnostics in your post there.
-
/lib is in RAM like the rest of the OS so changes there won't survive reboot.
Reapplying those changes at each boot in the go file might be too late in the boot, I don't know.
-
1 hour ago, frodr said:
Docker icons go grey
Screenshot?
-
- If you don't use ZFS, existing array and pools continue as before.
- I haven't used ZFS yet. Might consider converting my 2x500G btrfs pool named 'cache' to ZFS. Everything would have to be copied off so the pool could be recreated as ZFS.
- Primary is where new files get written. Secondary is where overflow goes. A separate setting controls which direction mover moves (pool <--> array). When you upgrade, it all still works as before since these settings are functionally the same as what we already had. See my earlier posts about this in the rc4 thread
-
2
-
3 hours ago, Ctek said:
When I check for plugins or new docker updates it says unavailable..
The connect beta also has an api error. Is there a way to resolve?
Checking connectivity ...
No response, aborting! -
6 minutes ago, foux said:
those ports for my reverse proxy
That's a good reason
Upgrade to 6.12.6 Results in lost connection with GUI
in Stable Releases
Posted
What do you get from command line with this?