truenas NIC problem

[breek]

This is probably ignorance but i cannot for the life of me figure out what to do. So here we go: 

 

I started tinkering with truenas. I had some old hardware laying around so i figured, why not.  I have it set up through a powerline adaptor to the attic. Created some pools with SMB share for my streaming pleasure. I noticed transfers weren't great. So i bought a new PCI-e 1Gb NIC and made me some brand spanking new CAT6 UTP cables. 

 

At the start all was fine, truenas detects said NIC but since I'm a novice at best i try to figure out how multiple NIC's work and start just doing stuff, looking things up. Which ends up in my deleting of the NIC in the webinterface.

 

Since then, i cannot make it reappear. It just doesnt show up either on the server or http portal. 

 

I've reset the whole thing to defaults, I've reseated it (using other slots and the same) and to verify it was still working, I put it in my desktop and in that it works fine. I've tried asking in the truenas discord but noone is answering, probably because either im dumb or it could be 1000 things. 

 

 

[AbydosOne]

3 minutes ago, breek said:

I have it set up through a powerline adaptor to the attic.

FWIW, no amount of new NICs is going to fix this bottleneck. Powerline is horrible.

 

4 minutes ago, breek said:

I've reset the whole thing to defaults, I've reseated it (using other slots and the same) and to verify it was still working, I put it in my desktop and in that it works fine. I've tried asking in the truenas discord but noone is answering, probably because either im dumb or it could be 1000 things. 

What is the rest of your hardware? (full list)

 

Are you using TrueNAS Core or Scale?

[breek]

2 minutes ago, AbydosOne said:

8 minutes ago, breek said:

I have it set up through a powerline adaptor to the attic.

FWIW, no amount of new NICs is going to fix this bottleneck. Powerline is horrible.

Well for now I've had no real issues. It reached around 12MB/s peak. hoped it could do better since populating a server takes a while like that. 

 

4 minutes ago, AbydosOne said:

What is the rest of your hardware? (full list)

 

Are you using TrueNAS Core or Scale?

Truenas Core (free ofc, home use mainly to have some fun, centralize storage)

 

 Technical data

Compare in category

CPU series	Intel® Core™ i7
Processor/type	i7-4770
Processor generation	4th Gen (Haswell)
Processor cores (No.)	4 x
CPU speed	3.4 GHz
RAM	8 GB
Graphics card type	Nvidia GeForce
Graphics card type	GTX760
Graphics memory	1.5 GB
SSD size (total)	128 GB
SSD 1 type	SSD
SSD	128 GB
SSD connection	SSD SATA II (300 MB/s)
HDD capacity (total)	2048 GB

 

 

I upgraded the RAM tho to 16Gb

 

[FloRolf]

40 minutes ago, breek said:

Well for now I've had no real issues. It reached around 12MB/s peak. hoped it could do better since populating a server takes a while like that. 

 

Truenas Core (free ofc, home use mainly to have some fun, centralize storage)

 

 Technical data

 

Compare in category

CPU series	Intel® Core™ i7
Processor/type	i7-4770
Processor generation	4th Gen (Haswell)
Processor cores (No.)	4 x
CPU speed	3.4 GHz
RAM	8 GB
Graphics card type	Nvidia GeForce
Graphics card type	GTX760
Graphics memory	1.5 GB
SSD size (total)	128 GB
SSD 1 type	SSD
SSD	128 GB
SSD connection	SSD SATA II (300 MB/s)
HDD capacity (total)	2048 GB

 

 

I upgraded the RAM tho to 16Gb

 

Well as mentioned Powerline is horrible. 12mb/s is pretty much 100mbit so I think your Powerline adapter or some other part in your network chain is limited to 100mbit.your PC's internal NIC will do 10x that no problemo. 

[Windows7ge]

I'm not all too familiar with TrueNAS but I am familiar with FreeBSD. I assume we're looking at the re0 interface? Check your /etc/rc.conf file and see if it has an entry for that interface. Should look something like this.

ifconfig_vtnet0="inet 192.168.0.238 netmask 255.255.255.0"

I don't know if TrueNAS reads from the /etc/rc.conf file though so it may be irrelevant.

[Ralphred]

1 hour ago, AbydosOne said:

Powerline is horrible.

This is very much "YMMV", I've set up PL adaptors that do what they say on the tin, whilst having set up others on the same power strip that refuse to "pair" with each other, it's a proper shitshow, but good results are worth a week of work from a good sparkie running cat6 and lots of filler/paint.

 

1 hour ago, breek said:

it could be 1000 things.

Indeed, though it's most likely to be 2 or 3 "usual suspects", try to cut down on variables by moving the NAS around so it can benefit from direct connections etc. as Re0 reads as "onboard".

Making the assumption that something in /etc is suppressing the interface, a `grep -i "<new interface name (if you remember it)>" /etc -R` may find whatever is "blacklisting" it, or you may have to go deeper into device discovery software (FreeBSD gurus pls reply...).

 

Either way, with this type of OS there is nothing you can do that cannot be "undone", no matter how far "off piste" the answer is, persist my friend, persist!

[breek]

21 hours ago, Windows7ge said:

I'm not all too familiar with TrueNAS but I am familiar with FreeBSD. I assume we're looking at the re0 interface? Check your /etc/rc.conf file and see if it has an entry for that interface. Should look something like this.

ifconfig_vtnet0="inet 192.168.0.238 netmask 255.255.255.0"

I don't know if TrueNAS reads from the /etc/rc.conf file though so it may be irrelevant.

it appears as truenas doesn't. there's a couple rc.conf(....) in there but nothing really helpful in there.

thanks for the comment!

[breek]

21 hours ago, Ralphred said:

This is very much "YMMV", I've set up PL adaptors that do what they say on the tin, whilst having set up others on the same power strip that refuse to "pair" with each other, it's a proper shitshow, but good results are worth a week of work from a good sparkie running cat6 and lots of filler/paint.

 

Indeed, though it's most likely to be 2 or 3 "usual suspects", try to cut down on variables by moving the NAS around so it can benefit from direct connections etc. as Re0 reads as "onboard".

Making the assumption that something in /etc is suppressing the interface, a `grep -i "<new interface name (if you remember it)>" /etc -R` may find whatever is "blacklisting" it, or you may have to go deeper into device discovery software (FreeBSD gurus pls reply...).

 

Either way, with this type of OS there is nothing you can do that cannot be "undone", no matter how far "off piste" the answer is, persist my friend, persist!

I'm pretty sure it just defaulted the second one to "re1". The shell in truenas doesn't seem to want to do a grep though. or its taking insanely long

 

[breek]

22 hours ago, FloRolf said:

Well as mentioned Powerline is horrible. 12mb/s is pretty much 100mbit so I think your Powerline adapter or some other part in your network chain is limited to 100mbit.your PC's internal NIC will do 10x that no problemo.

for i'd just  like get it to work so I can confirm that, that's basically the reason why i bought it in the first place.

[Windows7ge]

2 hours ago, breek said:

for i'd just  like get it to work so I can confirm that, that's basically the reason why i bought it in the first place.

Tonight or tomorrow I'll work on spinning up a TrueNAS Core VM. If we can replicate the problem perhaps we can figure out how to reverse it.

[breek]

On 5/7/2022 at 12:33 AM, Windows7ge said:

Tonight or tomorrow I'll work on spinning up a TrueNAS Core VM. If we can replicate the problem perhaps we can figure out how to reverse it.

any luck? I'm probably gonna return the NIC and try another. it's just not worth the hassle 

thx anyway 

[Windows7ge]

2 minutes ago, breek said:

any luck? I'm probably gonna return the NIC and try another. it's just not worth the hassle 

thx anyway 

I'm not all that familiar with the TrueNAS UI. More of a CLI guy myself so unfortunately no. When you say you deleted it I take it you're not sure what you did? The NIC just kind of disappeared while you were tinkering?

 

I would assume if you powered off the system. Removed the NIC. Powered on the system. Powered off the system. Then re-installed it that it aught to recognize it as a new network device and add it back into the WebUI.

[breek]

I ended up removing the battery from my motherboard and it found it again. 

 

so not sure what happened there