Ender Wiggin
-
Posts
10 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Ender Wiggin
-
-
I am not sure i will try and see if i can stop those messages.
The flag I put in the quoted text...? Can you not see it?
It is the last thing on this FAQ.
https://github.com/binhex/documentation/blob/master/docker/faq/preclear.md -
On 12/5/2022 at 8:47 PM, dlandon said:
The docker script is not the same script as the plugin. What parameter did you have to pass and how did you do it?
Post your server diagnostics.
For some reason the alignment is not getting chosen automatically. Justed add the flag and it started normally. If i did not add the flag it would not start in binhex preclear or UD preclear.
From Binhex-preclear: Preclear Docker FAQ
QuoteAlignment Options (-a and -A flags)
Below is the logic built into the preclear script when determining the starting sector for the partition:-
if preclear -a option chosen and drive < 2.2TB then will set to 63.
if preclear -a option chosen and drive > 2.2TB then will set to 64.
if preclear -A option chosen and drive < 2.2TB then will set to 64.
if preclear -A option chosen and drive > 2.2TB then will set to 64.
if preclear -a or -A not defined then 63 or 64 will be chosen based on unraid config, UNLESS the drive is > 2.2TB, in which case it will always be 64. -
Did you look at the time that had passed?
17 hours had passed till I decided to stop it and realized it was not working.
This happen before and list time I add to pass a parameter that is not exposed in the user interface.
I believe this is what i had to do last time to get it to start:
From Binhex-preclear: Preclear Docker FAQ
Alignment Options (-a and -A flags) Below is the logic built into the preclear script when determining the starting sector for the partition:- if preclear -a option chosen and drive < 2.2TB then will set to 63. if preclear -a option chosen and drive > 2.2TB then will set to 64. if preclear -A option chosen and drive < 2.2TB then will set to 64. if preclear -A option chosen and drive > 2.2TB then will set to 64. if preclear -a or -A not defined then 63 or 64 will be chosen based on unraid config, UNLESS the drive is > 2.2TB, in which case it will always be 64.For some reason the aliment is not getting chosen automatically
-
Have not been able to get pre-clear to work with a brand new drive.
Got a new drive wanted to stress test it before adding it to my system and i can't seem to get it to start.
I solved it last time with using the docker container and adding a Prompt but can remember what it was.
How do i pre-clear a brand new drive using the pre-clear plugin?
This is what the log shows and the it never gets past starting.
Preclear script invoked as: /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh --cycles 3 --no-prompt /dev/sdkSays success then never starts.
Both drivers appear to meet the requirements and give me a start prelear button.
-
Thank you! That fixed it. I think the Hot swap capabilities of the Disk Shelf are not has good or stable as i would have hopped. In the future i will just just do the move while shut down.
Thank you! Again. That got a bit scary for a sec there.
-
1
-
-
So I realized i did not need a SAS interposer in my disk shelf so today i wanted to switch all my drives from SAS to SATA.
I had already done a similar process of switching the drives from STAT to SAS when i got the Disk shelf. I followed the same process i followed last time.
- use Tools >> New Config to reset the array. Use the option to retain current assignments.
- go back to the Main tab and select the ‘Parity is Good’ option and start the array. Everything should come back up OK.
I then manually added the hard drives back to there specific location. Even though the names of the drives are basically the same Unraid can not tell the difference between a SAS hard drive and the same SATA drive. Now when i started up the array with with the "Parity is good" all my data drives show up as Unmountable: Unsupported or no file system. Also i had a drive i think got bumped and is disabled when i started this. The drive is fine but my cables and PCIe can sometimes be unstable causing write errors.
Is there any way to get the drives to mount without having to format them? Did I do something wrong in the process of switching everything over.
Before removing the SAS interposer:
After removing SAS interposer and restarting the array
Here is my diagnostics. Any help would be greatly appreciated!
wamred-diagnostics-20220830-1202.zip
I am planning to also add 2 more 14Tb drives so i will have to rebuild the parity at some point anyway. During the Preclear process is when my Disk 2 got the error. I think it had to do with me bumped the disk shelf when i inserted the drives.
-
On 3/9/2021 at 3:12 AM, binhex said:
So, Sonarr v3 is FINALLY here, its out of beta and is now the latest release, if you want to switch from Sonarr v2 to v3 then simply pull down the 'latest' tagged image.
However, if you want to stick on Sonarr v2 then please do the following:-
- Go to unRAID Web UI/Docker/left click Sonarr/Edit and change the value for 'Repository' to:-
binhex/arch-sonarr:2.0.0.5344-1-04-
Click apply to pull down v2 image.
Note:- There will be NO further development on v2 going forward.
If you are using the tag name of 'v3' then please do the following to switch back to 'latest' (now v3):-
- Go to unRAID Web UI/Docker/left click Sonarr/Edit and change the value for 'Repository' to:-
binhex/arch-sonarr:latestNote:- the 'v3' tag is now deprecated and will NOT be updated.
Can you update the FAQ with this info. It is the first place I looked before i can here to ask and it needs to be updated.
-
On 1/12/2022 at 10:32 AM, ljm42 said:
It sounds like you need to generate a set of private and public keys, hopefully when you give them the public key they will give you a full config file and not just an ip addess.
There are many ways to generate a set of keys, probably the easiest would be to go into the webgui and create a dummy wireguard tunnel and peer, and then press "Generate Keypair". You can delete this dummy tunnel and peer, but be sure to keep a copy of the public and private keys.
Once you get the config file from the provider you would import it per the instructions on the first post of this thread. Then add the public and private keys you created earlier as the "Local" public and private keys.
If they expect you to build the config file on your own I would probably move on to a different provider.
This is what i had thought has well. I went through the process and did not get a config files they only gave me an IP. They do give detailed instructions on how to add wireguard to a linux in this specific manner but i do not know how to apply this to the unraid wireguard setup. Here are some instrutions : https://www.ivpn.net/setup/linux-wireguard-netman/
-
I am using IVPN and they do not provide a configuration file to import into unraid.
They expect you to give them the public key then they assign you an IP address.
How can i use the unraid wireguard VPN tunneled access if i do not have a config file from my preferred VPN provider?
Here is the relavent documentaion: Not public.
Here is what i could find IVPN Wireguard
This also applies to trying to setup a docker container like delugevpn that requires a config file.
Here is what i could find
Unassigned Devices Preclear - a utility to preclear disks before adding them to the array
in Plugin Support
Posted
Well I have no idea what was wrong and nothing was showing in the logs but removing UNASSIGNED DEVICES and UD PRECLEAR and reinstalling them they are now working.
It had been working before and must have stopped working when I updated. I did not see anything in the logs that would have indicated a problem it would just refuse to start. I think the flag was a red herring but not sure.