I found this near the end of your syslog:

Mar  5 10:03:19 Tower nmbd[1946]:   Samba name server TOWER is now a local master browser for workgroup WORKGROUP on subnet 10.0.0.15
Mar  5 10:03:19 Tower nmbd[1946]:   
Mar  5 10:03:19 Tower nmbd[1946]:   *****
Mar  5 10:15:01 Tower nmbd[1946]: [2021/03/05 10:15:01.397785,  0] ../../source3/nmbd/nmbd_incomingdgrams.c:302(process_local_master_announce)
Mar  5 10:15:01 Tower nmbd[1946]:   process_local_master_announce: Server ASUS-PC at IP 10.0.0.241 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
Mar  5 10:15:01 Tower nmbd[1946]: [2021/03/05 10:15:01.398032,  0] ../../source3/nmbd/nmbd_become_lmb.c:150(unbecome_local_master_success)
Mar  5 10:15:01 Tower nmbd[1946]:   *****
Mar  5 10:15:01 Tower nmbd[1946]:   
Mar  5 10:15:01 Tower nmbd[1946]:   Samba name server TOWER has stopped being a local master browser for workgroup WORKGROUP on subnet 10.0.0.15
Mar  5 10:15:01 Tower nmbd[1946]:   

This line from that section is showing that your server does have access to the network at the time when you captured the Diagnostics:

Mar  5 10:15:01 Tower nmbd[1946]:   process_local_master_announce: Server ASUS-PC at IP 10.0.0.241 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election

 

The diagnostics confirmed that your server does have an IP address of 10.0.0.15  and you should be able to ping that address.  Can you get to the server from Windows Explorer (the Windows file manager) in the Network folder?

opened up windows explorer win10 , clicked on network, only computer I see is the ASUS-PC(win10) under the computer line.

 

I dont know if this is messing things up, but the only way i have found to get the zipfile off is to save it to the flash drive that i use for booting up. then shut down the server, plug it into the win10 machine and upload it to here.

 

so i left the server up all night, and the ip address is back to 169.

23 hours ago, ThirstyPenguin said:

dont know if this is messing things up, but the only way i have found to get the zipfile off is to save it to the flash drive that i use for booting up. then shut down the server, plug it into the win10 machine and upload it to here.

 No. not a problem.  Be sure that you are getting a clean shutdown.  Either use the command   poweroff    (as I recall) or push the power button on the case fro about one second.

 

47 minutes ago, ThirstyPenguin said:

so i left the server up all night, and the ip address is back to 169.

 

I would suspect that you have a hardware problem at this point.  I hope you haven't rebooted the server.   IF not, get another Diagnostics file to upload before doing so.  

 

NOTE:    A 169.xxx.xxx.xxx address means that the DHCP query for an IP address from your Unraid server has failed.

 

Am I correct in assuming that you have had periods where you can access the server?

 

You can also conduct a test by trying to 'ping' your computer from the server when things look like theyare working

 

Do you have another Ethernet card?

 

Do you know what caused the power outage?  Any possibility there was a big power surge that accompanied it? 

Nope I didnt reboot it this time here is the zip

I didn't actually access it when it was uip and running, but when i first loaded it up it connected fine, i got the trial ky and everything.

I haven't had it it working since the power outage, i dont know if there was a power surge afterwards, i wasnt home at the time.

 i don't have another Ethernet card, the Ethernet port its connected to it on the motherboard

tower-diagnostics-20210306-1056.zip

OK, try the Safe Mode.  It is a boot menu option.

 

I am going to ping  @Squid  and @bonienl  to see if they have some insight as to what is going on. 

Mar  5 13:51:20 Tower dhcpcd[1598]: br0: soliciting a DHCP lease
Mar  5 13:51:20 Tower dhcpcd[1598]: br0: offered 10.0.0.15 from 10.0.0.1
Mar  5 13:51:25 Tower dhcpcd[1598]: br0: probing for an IPv4LL address
Mar  5 13:51:30 Tower dhcpcd[1598]: br0: using IPv4LL address 169.254.148.36
Mar  5 13:51:30 Tower dhcpcd[1598]: br0: adding route to 169.254.0.0/16

 

Not really a network guy but looks like a network problem, it's being offered a DHCP address but it's not getting that and using a private IP address instead.

On 3/6/2021 at 11:30 AM, Frank1940 said:

OK, try the Safe Mode.  It is a boot menu option.

 

I am going to ping  @Squid  and @bonienl  to see if they have some insight as to what is going on. 

i booted it in safe mode with GUI, im getting the same results, still 169. ip

i unplugged my unraid machine from my network and hooked up my ubuntu machine with the same cables and it connects fine, i can get to the internet.

At this point, I would be suspicious of the NIC in the server.  Do you have a NIC card that you could try?  Could you borrow one from a friend (or vendor with a liberal return policy)?

 

If the current NIC is an onboard one, be sure to disable it in the BIOS.

yeah, im going to pick one up tomorrow from a buddy and give it a try.

Thanks everyone for the help on this. I did pick up the nic, and now everything seems to be working! thanks again for helping me figure this out!