PikkonMG

eth1 is only port I can somewhat get to work. I've also taken and deleted the network-rules.cfg and reset the network.cfg were eth1 in logs above is eth0 and it gets stuck in this bonded mode and still have same overall issue. Booted safe mode here is logs from a backup I just tried to restore from Generate Flash Backup dated 12/05/2022 reset the network.cfg ezra-diagnostics-20221218-1005.zip

Having issues with network. Unable to connect to server. I have 4 ethernet ports and none of them are wanting to work. I don't know if an update broke it or if network card is going out. Was able to connect and get logs by changing port and plugin direct into my modem. ezra-diagnostics-20221218-0120.zip

Safe mode no change but im starting to learn towards this might be a Windows issue.

I don't understand? You want same info from safe mode boot?

Scroll up a little! lol

Sorry was in maintenance mode. drwxrwxrwx 1 nobody users 131 Sep 22 10:46 ./ drwxr-xr-x 13 root root 260 Sep 24 10:19 ../ drwxrwxrwx 1 nobody users 31 Aug 21 18:10 .Trash-99/ drwxrwxrwx 1 nobody users 6 Apr 25 2017 Backup_Settings/ drwxrwxrwx 1 nobody users 66 Sep 2 01:31 ESG_Misc/ drwxrwxrwx 1 nobody users 17 Aug 14 14:43 Education/ drwxrwxrwx 1 nobody users 23 Aug 21 11:57 Gaming/ drwxrwxrwx 1 nobody users 21 Sep 8 02:21 Machine\ Backups/ drwxrwxrwx 1 nobody users 59 Sep 19 20:48 MyMedia/ drwxrwxrwx 1 nobody users 230 Mar 4 2022 Pepto/ drwxrwxrwx 1 nobody users 191 Feb 23 2022 Pursuit/ drwxrwxrwx 1 nobody users 4096 Feb 17 2021 SavedApps/ drwxrwxrwx 1 nobody users 186 Sep 19 22:14 appdata/ drwxrwxrwx 1 nobody users 24 Nov 9 2018 domains/ drwxrwxrwx 1 nobody users 4096 Sep 8 02:17 isos/ drwxrwxrwx 1 nobody users 26 Nov 9 2018 system/

/bin/ls: cannot access '/mnt/user': No such file or directory ezra-diagnostics-20220924-0111.zip

Have an issues with my share. Started when I upgraded a few of my drive on my Unraid server. If I reboot the server the login info for my Shares Access users fails. I have to go to just one share any one doesn't matter and go to SMB User Access switch user from Read/Write to Read Only hit apply then switch it back to Read/Write. After this login will work with network shares till next reboot. Sounds like some kind of permission issues but no idea how to mess with it.

Have a 120 GB SSD that holds nothing important, most just a cache drive for video files from the encoder. In Attributes tab it giving 187 Reported uncorrect with a count of 1 been this way for a few weeks, Every SMART test I have ran comes back with no issues.

Trying to move a file to my server that is 476GB. I have 240GB cache drives. Since the file is larger than any free space I have on my cache drives should it just skip them and add file straight to my pool? Im unable to move file because it keeps trying to send it to cache then move it over but file is to large for that. How can I work around this?

Question on disk limit for Unraid Basic. I know it's set to 6 but is that system limited or array limited? Mean could I have 6 disk in my array and 1 set to Unassigned Devices plugin for a total of 7 disk in the system but only 6 to the array?

It wont download the game after the docker is installed unless my network type is set to bridged. How do I post log?

Trying to setup the v rising container but im having few issues mainly with network. My Unraid server has 2 network cards in it. eth0-br0 is primary and eth1-br1 is what I run dockers ect on and is on a totally different network. If I select custom-br1 as my network type it wont run, goes for 17-18 sec and crashes. Never even downloads. Now I can go in and download say Barotrauma or about any other server files and select my network type as custom br1 and they will run fine.

Can't figure it out, after update I can no longer access by host name but IP works fine so that's what i've been doing now.

My Windows 10 PC updated on Nov 8th and since im no longer able to access any shares properly. I can access say Pursuit share by going to \\EZRA\disk1\Pursuit\ but not by going to \\EZRA\Pursuit\ This share is private and doing \\EZRA\disk1\Pursuit\ allows access without user info and \\EZRA\Pursuit\ gives error in attached screenshot. Everything worked fine before this update install. ezra-diagnostics-20181109-0354.zip