[[Plugin] Parity Check Tuning]

Thanks for that feedback.

 

Given that extra information I was able to recreate the issue and will put a fix into the next release of the plugin.  I need to initialise a variable that the CustomMerge script expects to already have been loaded before it is called.   The error will occur anytime you make a change under Settings->Disk Settings away from the defaults.

[Wrong SSD total size after upgrade to 6.12.0]

You should post your system's diagnostics zip file in your next post in this thread to get more informed feedback.  It is always a good idea to post this if your question might involve us seeing how you have things set up or to look at recent logs.

[Help with reducing the number of drives in an array configuration]

The New Config tool is covered here in the the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.

[Help with reducing the number of drives in an array configuration]

It depends on whether you are prepared to take any risks with the current data.

 

The simplest and probably quickest way would be to use the New Config tool and via that assign the disks that you want to finish up with removing the surplus drives; start the array;  format the new disks;  and then build parity based on those.    You could then mount each of the drives removed in turn via Unassigned Devices and copy their data back to the array.   This has the risk, though, of one of the removed drives failing before you can copy their data back to the array (thus losing the contents).

 

Any other approach is going to be more laborious but it should be possible to keep parity protection in place so you are protected against a single drive failure, but it will take longer and put more overall stress on the drives.

[Can no longer build Docker images after update to 6.12.8]

2 hours ago, mbush78 said:

 

Nope, not a peep yet.

 

If you did not get an automated acknowledgement then my guess is it did not get through.   I would suggest trying again via the contact support form.

[Unraid freezing - sometimes getting kernel panics]

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted.  You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to a crash.  The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field. 

['Parity is invalid' message, 2 hours, almost empty data drive]

3 hours ago, YaSo said:

Is it alright to stop the array in mid 'parity work' and then use the Tuning plugin you mentioned? And do you know if it will do this parity check each time I add a drive?

You can install the plugin with the check already running.   Not much point in stopping the current check as you would just need to start again from the beginning.   The plugin is not responsible for initiating the operation (which is Unraid’s responsibility), it just adds better management of what happens after it is started.

 

3 hours ago, YaSo said:

Also, is it alright to copy data to the data drive while the parity check is running?

Yes, but it will run much slower than when the check is not running (and also slow down the Check while they are both running) due to contention on the drives.  You should therefore avoid doing large amounts of writes to the data drives while a check/sync is running as doing them separately would end up being faster, but small amounts would be fine.

 

3 hours ago, YaSo said:

And do you know if it will do this parity check each time I add a drive?

When you add a drive, parity is not regenerated.   Instead the drive is Cleared (if not pre-cleared) to avoid it affecting parity.   You can find a discussion of Clear v Preclear here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. 
 

 

 

 

 

[Unraid to Unraid using builtin Wireguard]

Have you read this section of the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page that covers using WireGuard?  The Unraid OS->Manual section in particular covers most features of the current Unraid release.

[Unraid Shutting Down]

1 hour ago, SeaPanda117 said:

My Unraid starting shutting down today. I updated the OS to the latest update as well as migrated to a new case yesterday. Can someone help walk me through getting the diagnostic files and stuff run that I need? This is shutting down about twice a day and is already frustrating. You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

 

The syslog in the diagnostics is the RAM copy and only shows what happened since the reboot.   It could be worth enabling the syslog server to get a log that survives a reboot so we can see what happened prior to the reboot. The mirror to flash option is the easiest to set up, but if you are worried about excessive wear on the flash drive you can put your server’s address into the Remote Server field.

 

Do you by any chance have the S3Sleep plugin installed?   That has been known to spuriously shutdown servers.  

[Question about upgrading parity drive]

If you read that link carefully you will see that despite its name it is NOT for replacing an existing parity drive with a larger one.   For that you simply follow the procedure for Upgrading parity disks.

['Parity is invalid' message, 2 hours, almost empty data drive]

Parity sync time is not determined by how much data you think is there but by the size of the parity drive as it works at the raw sector level and works through every sector on the parity drive.    My experience I’d something like 1-2 hours per TB of the largest parity drive size s not atypical.   You might want to read this section of the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page to get a better idea of how parity works.   The Unraid OS->Manual section in particular covers most features of the current Unraid release.

 

While a parity sync/check is active performance of the array is significantly reduced and since parity checks/syncs take so long with large modern drives you might want to consider using the Parity Check Tuning plugin to offload the check to running in increments outside prime time.

[[Noob] Issue with permissions from a docker]

8 minutes ago, Vladcik said:

Thanks a lot for the support, glad to see I was not too crazy T-

You could use the User Scripts plugin to periodically set the permissions to Unraid default.   Under the covers the New Permissions tool invokes the ‘newperms’ binary that can be used in a script.

[[Noob] Issue with permissions from a docker]

Then you would need to get the author of the container to provide a way to set permissions correctly.   Typically this is done by exposing the unmask setting in the container

[Wireguard Tunnel + Access Docker/VM with different IP than Host + Router does not support static routes]

Under the Peer Allowed IPs field you need to put entries for each subnet you want to be able to access via WireGuard.

[Share specific path of a pool with SMB]

It is not clear if you intend to have a pool called Main or not or if you intend these files to be on the Unraid array?

 

You should start by setting up User Shares for “Data”, “Download” and “Data”, specify where you want them stored as the Primary Storage setting, and then make sure that for these shares you have the SMB Export setting to something other than the default of “No” so they are accessible as shares across the network. 
 

It is not clear to me if you also need “Main” as share?    
If you are and you are using the main Unraid array then you could install  the Unassigned Devices plugin and use its feature for a ‘root’ share and call it Main to expose the whole of the array as the “Main” share.

if you are using a pool rather than the main array then you could call that pool “Main” and export that instead.

[[Noob] Issue with permissions from a docker]

1 minute ago, Vladcik said:

Well i'm confused here. The docker settings of TubeSync is just 99/100 ? 
And I already did the Tools => New Permissions a few time to just be back to that state ?

Those are correct to get the user and group but is not sufficient.   Is there anything that mentions Umask which is used to get the correct permissions.

[UNRAID kernel: BTRFS error]

Have you tried running a scrub on disk2 (which is the drive the errors mention)?

 

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

[[Noob] Issue with permissions from a docker]

That shows there is an issue with the docker setting the permissions correctly, not with the owner being ‘nobody’ and the group being ‘users’

 

on a directory I would expect them to be

drwxrwxrwx

and on a file

	-rw-rw-rw-

These are the permissions you would get if you ran Tools->New Permissions on the share to set them to standard Unraid defaults.

[Mover Issues]

What share is it that you think is a problem?   None of the shares you have set up to move files from cache to array have any files on the cache so there is nothing for mover to do.

[[Noob] Issue with permissions from a docker]

52 minutes ago, Vladcik said:

Heyah !

Well it's by default, but it makes any file (for example on my Windows) not usable at all. I'm registered with my user account, and I say I don't have any right because well it's nobody that owns everything.

Would not be an issue if nobody's right was duplicate with my user / all users in Windows but here, it's just the default nobody user not allowing me to do anything with the files created from this docker

 

Thanks o/

I suggest you post the result of 

ls -l

command to show the full permissions of the file in question.    It could well be something other than the username that is the issue.

 

i have all my Unraid files owned by ‘nobody’ and can access them with no issues from all my systems with no problems which is why I suspect some other issue.

[[Noob] Issue with permissions from a docker]

Not quite sure why you think you have a problem?  The "nobody" user is the standard default in Unraid.

[Notifactions not sending the right time]

1 hour ago, Gragorg said:

So when I did my parity check this month I had an issue with a drive connection resetting so it took longer than normal.  When i completed the parity check it send a notification (telegram) that said it took "1 day, 9 hr, 4 min, 14 sec".  In reality it took "1 day, 17 hr, 29 min, 10 sec" and I can see that clearly in the history.  Yesterday I went to address the drive that was resetting  connection but since I had a warm spare already in my machine I just used it to rebuild.  The rebuild notification reported "1 day, 17 hr, 29 min, 10 sec" was the completion time.  In reality it took "8 hr, 20 min, 35 sec" as it is clearly listed in the history.  It seems to be sending the previous time.  Is this a known bug?

Yes, and has been present for the several releases now.

[pool or array?]

21 minutes ago, userano218n said:

Would the 2nd parity be the same as doing raidz2?

 

Not really as the Unraid approach to parity is very different to a traditional RAID system.   As an example the Unraid array has each disk as a separate file system (that can be read on another system by itself if needed), and you can use a mix of the supported file systems in the Unraid array.  It WOULD, however, allow for any 2 disks failing in the Unraid array and being able to recover their contents.

[Simulating RAID1 with Two 4TB Disks and a 1TB Disk]

1 hour ago, skynet11 said:

Just one more question: does it matter which drive I designate as the parity drive, or can I choose any of the three drives for this role?

No parity drive can be smaller than the largest data drive so you would need one of the 4TB drives to be a parity drive.

there is a description of how Unraid parity works here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. The Unraid OS->Manual section in particular covers most features of the current Unraid release.

 

[Unsupported or no filesystem]

59 minutes ago, polishprocessors said:

formatted the two new drives

This would have also formatted the emulated drive thus wiping its data.    You would have needed to run the procedure for fixing disk1 to make it mountable before attempting any format.