Omri
-
Posts
96 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Omri
-
-
Thanks for the response
The PC/DAS I referenced are just an example, but they are in my budget.
Regarding the PCIE card, I thought I just need a cable from the 8611 oculink to dual 8643 mini sas.
Something like this
How do I use PCIE card with a mini PC?
It's encouraging to hear USB case working fine for you
I can consider it too
I'm a little bit afraid of the reliability of USB storage.
What device do you use with the UM 790 pro?
-
Essentially I'm asking if oculink to 2x sff-8088/8643 will work
-
It's 600$ at Amazon
QNAP TL-D800S 8 Bay SATA 6Gbps JBOD Storage Enclosure. PCIe SATA Interface Card (QXP-800eS-A1164) Included https://a.co/d/84BZgpS
-
Hi
Currently my unraid server sits in a fractal design define 7. I would like to switch to something more compact and convenient.
Thought about buying a mini PC with oculink like this (only announced but not released yet)
And attach it to an expension unit like this
https://www.qnap.com/en/product/tl-d800s
Will that work? Is there an oculink cable that can connect 2xsff-8088/8643?
Thanks
-
Any news regarding the crash with the new bios?
-
I have 10th gen Intel with macvlan problem...
It's also (likely) not router related
Happens with asus router but also with OPNsense
And it's happening with different nics on same PC
One of them is Intel i-225v and the other Aquantia 10G.
Out of ideas...
-
Besides the problem with NPB7
can you elaborate about using unraid with OWC Thunderbay 8? Is it "plug and play"? Do you see performance issues?
I also have NPB7 on the way
-
After few weeks of using eth0 network for docker with bridging disabled, with no sign of macvlan traces, I had a lockup and after hard reset of the server, macvlan traces are back to system logs (after few hours of uptime).
I need macvlan for setting the IPV6 address based on the Mac address, so switching to IPvlan is not a good solution. Tried using a second nic, which didn't help.
Anything else to try?
-
The only solution that worked for me is:
Disable bridging
Docker use macvlan through eth0
Optional:
Second network interface is passthrough to VM
Thanks to @bonienl
- 1
-
At least on 6.12 you can get to GUI
Just type slim in terninal
- 1
-
Been trying this method since his post, so far no macvlan traces
-
" Docker network as IPvlan..."
- 1
-
Linuxserver has their advantages
docker mods is defiently one of them
-
Linuxserver's image requires special parameters
-
Just a silly question
Why the official one and not linuxserver, any benefits?
- 1
-
Do these settings might be related to the problem?
-
Yes, of course
-
On 3/26/2023 at 2:16 PM, JorgeB said:
This issue appears to be limited to LSI SAS2 models, SAS2008 and SAS2308 chips, don't remember seeing anyone with a SAS3 model like the 9300-8i (SAS3008 chip) having the same problem.
I have this problem with 9300-8i
this solution didn't help
Now the Seagate drive (only one) is attached to motherboard and all other drives (WD) to the LSI
-
Well, it took longer than usual (~4 days)
But I got macvlan call traces again.
all containers are one br1.
bummer
-
So far this method seems to work
Two days+ and no macvlan traces
Before, it would take few hours to get the first error (although it never crashed my server I think)
Thanks
-
Well, hostnames work automaticly by docker name if no other host defined.
In my case, DNS working fine without br0 (eth0 bridging set to no) but I'll verify.
Thanks for the response
-
what does "Docker DHCP allows for labels" mean?
and why do you need --dns in every container?
Thanks
-
-
Don't use auto IPV4/IPV6 on eth0 - use static and define IP/gateway/dns
than you need to feel the subnets in docker settings under br1 (but don't check the pool - just the subnet and gateway)
Mini PC with expension DAS?
in Hardware
Posted · Edited by Omri
I understand, I still need the sata controller
why USB4 related?
Thanks