Hi, I am planning to format an external hdd as ntfs so that it can be used with Windows. I want to encrypt it with bitlocker. Will this setup work with UD?

 

46 minutes ago, luca2 said:

Hi, I am planning to format an external hdd as ntfs so that it can be used with Windows. I want to encrypt it with bitlocker. Will this setup work with UD?

 

UD uses crypto luks for encryption in xfs, btrfs, and zfs disks.  Bitlocker won't work on a ntfs disk.

After updating past Unraid 6.10, I get constant log errors regarding the network share I have mounted. I can't even unmount it because it says it's always busy. Can anyone offer help? This seems to keep crashing my whole server every day or two. 

1 hour ago, QuestForTori said:

Can anyone offer help?

Post diagnostics.  What is the remote server another Unraid?

4 hours ago, dlandon said:

Post diagnostics.  What is the remote server another Unraid?

Sure, here is the output zip from the diagnostics menu from my server (Though this is before has crashed yet on this power-on cycle). Also, the remote server is an x86 Synology NAS on the same network. 

skaianet-diagnostics-20231015-1838.zip

Edited October 16, 20232 yr by QuestForTori

11 hours ago, QuestForTori said:

Sure, here is the output zip from the diagnostics menu from my server (Though this is before has crashed yet on this power-on cycle). Also, the remote server is an x86 Synology NAS on the same network. 

The issue is most likely related to a network issue.  The log messages indicate a file is being closed that was not opened?

 

You are getting a macvlan call trace.  The CIFS log messages occur right after the call trace.

 

Read the 6.12.4 release notes on macvlan call traces and then upgrade to 6.12.4.  The macvlan call traces situation has been improved in 6.12.4.  The releaase notes are here:

 

2 hours ago, dlandon said:

The issue is most likely related to a network issue.  The log messages indicate a file is being closed that was not opened?

 

You are getting a macvlan call trace.  The CIFS log messages occur right after the call trace.

 

Read the 6.12.4 release notes on macvlan call traces and then upgrade to 6.12.4.  The macvlan call traces situation has been improved in 6.12.4.  The releaase notes are here:

 

I already did upgrade to 6.12.4, then I tried downgrading to 6.12.3 to see if it would fix the problem, and it didn't. Is there anything else I could try?

5 minutes ago, QuestForTori said:

I already did upgrade to 6.12.4, then I tried downgrading to 6.12.3 to see if it would fix the problem, and it didn't. Is there anything else I could try?

Did you follow the suggestions on how to stop the macvlan call traces?

2 minutes ago, dlandon said:

Did you follow the suggestions on how to stop the macvlan call traces?

You mean I should just run the command 

umount /var/lib/docker

after upgrading?

3 minutes ago, QuestForTori said:

You mean I should just run the command 

umount /var/lib/docker

after upgrading?

No, try setting Settings->Docker Custom Network Type to ipvlan.

 

Sorry, I thought there was more there on the macvlan call traces issue.

2 minutes ago, dlandon said:

No, try setting Settings->Docker Custom Network Type to ipvlan.

 

Sorry, I thought there was more there on the macvlan call traces issue.

Thanks for the tip, I'll give that a try and I'll report back if I keep getting crashes!

1 hour ago, dlandon said:

No, try setting Settings->Docker Custom Network Type to ipvlan.

 

Sorry, I thought there was more there on the macvlan call traces issue.

Hmm, I'm still seeing these same errors in the logs after switching to ipvlan, should I still be worried?

1 minute ago, QuestForTori said:

Hmm, I'm still seeing these same errors in the logs after switching to ipvlan, should I still be worried?

Post another diagnostics.

2 minutes ago, dlandon said:

Post another diagnostics.

Gotcha, here you go:

skaianet-diagnostics-20231016-1051.zip

29 minutes ago, QuestForTori said:

Gotcha, here you go:

I would do the following:

• Turn off AdGuard.  It makes network changes and might be causing issues.
• Turn off Docker and see if there are any other Docker Containers causing issues.
• Boot into Safe Mode, install CA and Unassigned Devices only and mount your remote share and see if the log messages continue.

22 minutes ago, dlandon said:

I would do the following:

• Turn off AdGuard.  It makes network changes and might be causing issues.
• Turn off Docker and see if there are any other Docker Containers causing issues.
• Boot into Safe Mode, install CA and Unassigned Devices only and mount your remote share and see if the log messages continue.

Looks like turning off AdGuard and rebooting made the errors stop! I'll probably go and ask around specifically about the AdGuard docker, then - this seems like it might be a bug in the container.

I am having an issue with remote sharing.

 

I have a share setup to auto mount to my backup shared folder on another server. But everytime I reboot my unRaid server, it won't auto connect and says that remote server is unavailable. Even though it says that, the remote server is always on and you can always access the shared folder from other computers. Also the mount button is greyed out.

 

I have changed the remote share timer delay to 2 minutes thinking it was a slow connect thing, but it is still happening.

 

I have attached a screenshot of what it shows on the main tab, the settings for the specific mounting, and also settings for the plugin.

 

I hope someone can help me out with this. It happens to all shares I setup, even when I try to connect to shares on other servers/computers.

12 minutes ago, sneville83 said:

I have attached a screenshot of what it shows on the main tab, the settings for the specific mounting, and also settings for the plugin.

UD thinks the remote server is offline - that's why the 'Mount' button is grayed out.  Post diagnostics so I can try to find out why.

1 minute ago, dlandon said:

UD thinks the remote server is offline - that's why the 'Mount' button is grayed out.  Post diagnostics so I can try to find out why.

Here is the file.

olympus-diagnostics-20231017-1441.zip

1 hour ago, sneville83 said:

I hope someone can help me out with this. It happens to all shares I setup, even when I try to connect to shares on other servers/computers.

It looks like the remote server is not responding to a ping.  Be sure the remote server is configured to respond to a ping.

 

Go to a command line and try:

ping OPENMEDIAVAULT

Also try by IP address.

5 hours ago, dlandon said:

It looks like the remote server is not responding to a ping.  Be sure the remote server is configured to respond to a ping.

 

Go to a command line and try:

ping OPENMEDIAVAULT

Also try by IP address.

I attempted to ping the server by its hostname and its says that its unknown. However, when I go to ping the ip address of the server, it works fine.

 

Unsure how to force unRaid server to automatically add openmediavault's IP address to DNS record so I don't have to use the IP address to connect.

22 minutes ago, sneville83 said:

I attempted to ping the server by its hostname and its says that its unknown. However, when I go to ping the ip address of the server, it works fine.

 

Unsure how to force unRaid server to automatically add openmediavault's IP address to DNS record so I don't have to use the IP address to connect.

What ip address shows when you ping by server name?

Just now, dlandon said:

What ip address shows when you ping by server name?

When I ping OPENMEDIAVAULT (Server's hostname), it says Name or Service not known.

 

However, I can ping the server by host name on all my other computers.

23 minutes ago, sneville83 said:

When I ping OPENMEDIAVAULT (Server's hostname), it says Name or Service not known.

Give me the output of the following commands:

arp -a OPENMEDIAVAULT

and

arp -a OPENMEDIAVAULT.local

 

On 10/4/2023 at 1:55 AM, dlandon said:

Post diagnostics.

Sorry this took so long, I had to wait for the problem to occur again. Which it just did:

 

 

 

Edited October 19, 20232 yr by Pri