Pstark

bump

It was not a typo but I have since disabled it.

It's pretty odd that Unraid network settings says the MAC address for the server is 90:e2:ba:2e:01:bd and if I go into my UniFi console and block that device, the server functions normally. But if I block the mystery device that shares the same IP (16:5d:31:7f:75:65) the server becomes unresponsive. Honestly the only reason I'm looking into this is the fact that UniFI Console shows a message that two devices are sharing the same IP.

macvlan is the only way docker containers show up in Unifi so I want to keep that. I did enable bridging and restarted eth0 but I still have two MAC address for the server. Before the server had 02:e1:d6:c9:90:76 (unknown mac I'm trying to figure out) and 90:e2:ba:2e:01:bd (mac address listed in network settings) and now I the first one changed to 16:5d:31:7f:75:65 and 90:e2:ba:2e:01:bd. If I block 16:5d:31:7f:75:65, the UI becomes unresponsive until I unblock it. If I block the MAC address listed in network settings 90:e2:ba:2e:01:bd, it makes not difference.

I was recently going to my UniFi Devices list and noticed that Unraid had two lines listed with the same IP address. I am trying to figure out where this MAC address is coming from. ifconfig shows it listed as "vhost0". vhost0's IP always matches eth0 which is the fiber connection I intend to use. Supermicro MB has three BbE ports and I have a 2 port Intel SFP+ NIC that has only has one fiber connection to the network. I have checked all docker containers and VM for this MAC address but can't be found. tower-diagnostics-20240331-1512.zip

Currently I have a tower that doesn't have any drive bays. I have my HBA cables running out the back and connecting to my 3 HDD enclosures. This is creating issues with disk errors and therefore I am looking to move to my first rack mount solution. I'm thinking I should get a disk shelf for all my drives and a 3 or 4U my server. Currently I have the capacity for 15 drives with the goal of have 20 drive bays. My first question is, would anyone recommend against this or recommend a better solution? Second question is, how would I connect the server to the disk shelf? I want use a single connection for all my drives if possible.

Ok so SAS and SATA drives can use the same cable but the protocol used depends on the drive.

But will the 7 pin SATA connector support 12Gbps when connected to a SAS drive like in my use case? Or does a 12Gbps connection require a different cable? I’m thinking the SATA connector is a “bottle neck”. It’s called SATA for a reason but I don’t know and therefore, the reason I’m making this post.

I am trying to google the answer but I don’t I’m uncertain of what I’m finding. Just because SAS drives physically fit in the cage I’m thinking sellers are saying it supports SAS 12Gbps speeds as in the backplane has a the connector for both SATA and SAS drives.

Can SFF cables like SFF-8643 to SATA breakout cables support a 12Gbps connection? Being they connect using a SATA 7 pin connector, wouldn’t that mean it will “work” but at a 6Gbps speed? This is how mine is currently setup: LSI SAS9300-16i —> SFF-8643 to SATA —-> Samsung MZ-ILS3T80 3.84TB SAS SSD inside a NORCO SS-500

What does the UI use when you change "enable docker" to no in docker manager?

Is there a guide to do this?

I'm attempting to make my own backup script. This is my script: /etc/rc.d/rc.docker stop && sleep 1m && tar -zcf /mnt/remotes/TRUENAS.HOME.ARPA_truenas/appdata_backup_script/appdata_backup-$(date +%Y%m%d_T_%H_%M).tar.gz -C /mnt/user/ PC\ Drive && /etc/rc.d/rc.docker start && sleep 3m && find /mnt/remotes/TRUENAS.HOME.ARPA_truenas/appdata_backup_script/* -mtime +45 -delete This is the output: Tower# /etc/rc.d/rc.docker stop && sleep 1m && tar -zcf /mnt/remotes/TRUENAS.HOME.ARPA_truenas/appdata_backup_script/appdata_backup-$(date +%Y%m%d_T_%H_%M).tar.gz -C /mnt/user/ PC\ Drive && /etc/rc.d/rc.docker start && sleep 3m && find /mnt/remotes/TRUENAS.HOME.ARPA_truenas/appdata_backup_script/* -mtime +45 -delete stopping dockerd ... waiting for docker to die ... starting dockerd ... Tower# It doesn't get past the stoping docker. Can anyone help? This is my first script BTW.

I'm trying to resolve nextcloud.home.arpa locally, to the docker container. I can access nextcloud from anywhere via the my WAN domain. I want an internal domain.

For the past few days I have been attempting to make so that if I type in the browser address bar, for example "nextcloud.home.arpa" pfSense would resolve that domain to a local IP, 10.10.111.3:8666 in this case. I feel it's possible but I can't get it working. I just want to use domains because I can't remember all the IP's and port numbers. Domain override works but you can't enter port numbers.