-
_Random
I hope you guys are not offended, may I ask for some support on a Truenas core Dasboard issue. I'm new to the freebsd from linux, I hope that you guy's who have experience with Truenas can help me, please!
-
_Random
the disk "/dev/da0" is present I've creted it with gpart using the command " gpart add -f freebsd-zfs /dev/da0 ", but its not showing up in disks in dashboard.
dpaste.org/eTtci please are you guys able suggest why this maybe the case and a possible solution, thanks kindly!
-
VimDiesel
Title: dpaste/eTtci (Python)
-
meena
_Random: does the dashboard have logs?
-
crb
can someone suggest a way to performance test my connection between two hosts? I've got a zfs send | receive that's been running for like a week or more
-
bradd
crb, maybe use iperf3 on both hosts to test the network speed?
-
crb
ok so that seems to show 8.5 Gb/s
-
crb
when ZFS prints out a line for a send receive: 21:59:38 188K rz2_pool/homes@2023_04_21 that means 188K transferred per second right? That would be like 1 mbit/sec WTF?
-
_Random
meena: truenas core ix system R C 2023
-
_xor
-
VimDiesel
Title: GitHub - JosephLai241/nomad: 🌳 The customizable next gen tree command with Git integration and TUI.
-
_xor
RhodiumToad: Any interest in using that?
-
meena
_Random: that's not a log, that's an OS Version
-
meena
_Random: the dashboard is a (Web) application, and it has to have logs. you should look at those logs to figure out what it's doing (wrong)
-
_Random
I just rebooted the machines & swwaped the drives over, now all3 are showing in the dashboard. sorry to trouble you, but your help is appreciated ! :)
-
rtprio
crb: yeah that looks a bit slow
-
rtprio
over ssh? ssh -C ? nc ?
-
crb
rtprio, just plain ssh
-
crb
zfs send -v rz2_pool/homes@2023_04_21 | ssh crb@eclipse recv -uv rz2_pool/homes
-
preyalone
when did bmake add support for the != shell macro assignment operator?
-
meena
preyalone: that feels like it should have been long long ago
-
ghoti
crb: perhaps sysutils/pv might help confirm the speed of the copy. you will have to do some meth to feed pv optionw to let it estimate better,
-
ghoti
crb: also, `ssh crb@eclipse recv -uv rz2_pool/homes` doesn't appear to include a zfs command.
-
crb
ghoti: you're correct, but killing it and adding zfs before recv doesn't seem to change the output or rate
-
ghoti
I would expect a rate of 0 if there is no valid processs to receive data. In a pinch, perhaps try `zfs send foo/bar | ssh crb@eclipse "cat > zfsrecvtemp"`, then see if you get data in that file.'
-
crb
ghost so that last one was interesting, I don't see the file zfstmp even being created on the destination
-
ghoti
Can you at least `ssh crb@eclipse hostname` ?
-
crb
yep, I get the right hostname back
-
crb
but that was very helpful
-
crb
it waits for the password, whereas since ZFS was printing that line continuously every second I thought when the password prompt came up, it was picking it up from my .ssh or something
-
crb
Thank you, that's help a LOT!
-
ghoti
woot!
-
ghoti
crb: to make things easier for this task without setting up keys, you might want to add this to your ~/,ssh/config:
sprunge.us/wkVCrZ
-
typicat
ps -A -U joe9 -o start,time,etime,command | sed -ne '1p;/[f]irefox/p'
-
ghoti
(and of course, make the directory too)
-
typicat
ops
-
crb
ghoti, thank you now I just need to understand why it won't accept the snapshot
-
mrelcee
I have been googling the heck out of getting intel quicksync firing on my server for ffmpeg use. Not sure anything i am finding is current info.. maybe someone here has clues...
-
mrelcee
Have the drm-kmod package installed. The i915kms kernel module is being loaded.. and i find nothing in /dev representing it. Ffpmeg compiled from ports with the quicksync bits enabled. It fails to locate a device when run with hwaccell..
-
mrelcee
New server upgrade going from an anxhient xeon system to an i7 9700k. Figured itd be handy putting that iGPU to use. Its supposed to be pretty capable in 9th gen core processors.
-
yuripv
does the driver attach (check dmesg)? is your user in 'video' group?
-
mrelcee
User is in video group, lemme check on dmesg
-
mrelcee
I do not see anything video related in that output.
-
mrelcee
Module being loaded but isnt happy i guess.
-
RhodiumToad
if you do pciconf -lv and look for the video device, what do you see?
-
mrelcee
Its in there.
-
RhodiumToad
is the driver listed as none@, or...?
-
RhodiumToad
and what's the pci ids, and what freebsd version?
-
mrelcee
-
VimDiesel
Title: vgapci0@pci0:0:2:0: class=0x030000 rev=0x02 hdr=0x00 vendor=0x8086 device=0x - Pastebin.com
-
mrelcee
Vga
-
mrelcee
Im on 13.2
-
RhodiumToad
and which driver exactly is loaded?
-
mrelcee
I915kms.so
-
RhodiumToad
kldstat -v will show the full path
-
RhodiumToad
also the version of the drm-kmod packages?
-
mrelcee
lcraft@persephone /u/h/lcraft> kldstat -v |grep -i 915
-
mrelcee
8 1 0xffffffff83214000 1858b8 i915kms.ko (/boot/modules/i915kms.ko)
-
mrelcee
520 i915kms
-
mrelcee
lcraft@persephone /u/h/lcraft [1]> pkg info drm-kmod
-
mrelcee
drm-kmod-20220907_1
-
RhodiumToad
there should be another drm-* package
-
RhodiumToad
and also a gpu-firmware* package
-
mrelcee
Dont have those. This is kab6nlake
-
mrelcee
Kaby lake? I think
-
mrelcee
gpu-firmware-intel-kmod-kabylake-20230210_1 Firmware modules for kabylake Intel GPUs
-
RhodiumToad
drm-kmod should have installed them
-
RhodiumToad
pkg info drm\* says what?
-
mrelcee
Pkg said the gpu package is already installed.,
-
RhodiumToad
pkg info drm\* says what?
-
mrelcee
Ah there is another one
-
mrelcee
drm-510-kmod-5.10.163_7
-
mrelcee
drm-kmod-20220907_1
-
RhodiumToad
ok, well the code definitely seems to have an entry for your pci id
-
mrelcee
Shouldnt that be generating an entry in /dev then?
-
RhodiumToad
were there any messages from the module when it loaded?
-
RhodiumToad
and have you tried booting in verbose mode?
-
mrelcee
I have not tried verbose mode. It runs headless.
-
mrelcee
So i havent seen if its popping up a notice when the kld loads - i keep reading that happens.
-
RhodiumToad
are you loading it in kld_list in rc.conf?
-
mrelcee
Yes
-
RhodiumToad
any messages would be in dmesg or /var/run/dmesg.boot
-
mrelcee
It is showing vgapcie0 in there
-
mrelcee
-
VimDiesel
Title: ---<<BOOT>>---Copyright (c) 1992-2021 The FreeBSD Project.Copyright (c) 1979 - Pastebin.com
-
RhodiumToad
that log seems to show the driver loaded ok
-
RhodiumToad
what's in /dev ?
-
mrelcee
-
VimDiesel
Title: lcraft@persephone /dev> ls -ltotal 6crw-rw-r-- 1 root operator 0x2d May - Pastebin.com
-
RhodiumToad
anything in /dev/dri or /dev/drm ?
-
mrelcee
./dri shows a card0 and a renderD128
-
RhodiumToad
there you go then
-
mrelcee
I must be missing the memo on how to access that device with software then. But this confirms i am having an ffmpeg problem not a freebsd problem.
-
mrelcee
More likely a between keyboard and chair issue.
-
RhodiumToad
right. I have less experience with that, I only use GPUs for actual displays rather than other software use
-
RhodiumToad
but the existence of that device, and the log messages from boot, confirms that the drm driver has recognized the GPU and attached to it
-
mrelcee
This is the first time ive had any use for a gpu on a server or a gpu up
-
mrelcee
Worth using
-
RhodiumToad
the devices should be accessible to the video group, btw, and the user accessing them obviously also needs to be in that group (or root)
-
mrelcee
I tried TrueOS for a while a long time ago. Not having Lightroom and Photoshop was a deal breaker for itTrying to run that under Bhyve was painful.
-
_xor
Does x11/nvidia-driver not build the drm module yet?
-
RhodiumToad
huh?
-
_xor
nvidia-drm.ko
-
RhodiumToad
dunno
-
_xor
525.xx was the first version used to add drm support on FreeBSD for the nvidia driver.
-
_xor
I built it before previously based on
github.com/amshafer/nvidia-driver and it did work (though it was a bit flakey)
-
VimDiesel
Title: GitHub - amshafer/nvidia-driver: Fork of the Nvidia FreeBSD driver to port the nvidia-drm.ko module from Linux
-
_xor
525 is in main now, so I wanted to build it, but no nvidia-drm.ko was produced and the Wayland DE I was trying to start failed with the same message it had before when it couldn't use drm.
-
_xor
Before assuming that the main port hasn't yet been updated to produce nvidia-drm.ko (didn't see it in OPTIONS), I wanted to make sure it wasn't something on my end or if it was combined with nvidia.ko or something.
-
_xor
Oooh
-
» _xor just noticed the recent commits
-
_xor
Though don't see anything related to the drm kmod :/
-
last1
I have a zfs pool on debian with some features that FreeBSD doesn't have yet
-
last1
can I still zfs send receive it, without those features ?
-
parv
"zfs-recv" may show a warning, never tried that. The "dry run"option, of zfs-recv, is also useless
-
parv
There was either a PR or a comment in bugzilla about the uselessness IIRC
-
» parv remembers the context: "zfs recv -n" could not show what would have been done due to lack of existing child(ren) dataset(s)
-
rtprio
last1: i'm going to go with "i doubt it" '
-
crb
I have two 13.1 systems with ZFS. On one when I type zfs list I get a list of all file systems, on the other I get filesystems AND snapshots. What am I missing is there a zfs property or environment var that is set?
-
rtprio
i wasn't aware zfs-list reacted to environment variables
-
parv
crb, you have set the "make snapshot generally visible" option
-
crb
parv, ah thank you!
-
rtprio
where is that setting? on the pool?
-
parv
Check dataset "snapdir" option
-
parv
Also, zfsprops(8)
-
rtprio
so if it's not hidden, it reveals .zfs/snapshots and clutters up zfs-list with them?
-
parv
Nope, "snap(dir|dev)=visible" did not cause snapshots to appear in "zfs-list" output
-
parv
... on 13/stable
-
parv
crb, all I could suggest is to compare the all the properties to find the difference
-
crb
it's probably snapdir
-
parv
That did not work for me
-
crb
oh, ok
-
parv
crb, Try: for pool in one other; do zfs get all "$pool" >"$pool.opt" ; done ; diff -u one.opt other.opt
-
crb
What about snapdev
-
parv
See my comment of 5 minute old. Also, you could try yourself
-
parv
crb, Are you sure that you did not use "-t snapshot" option?
-
crb
part yes
-
parv
Ok
-
parv
Rebooting 13-stable after setting "snap(dir|dev)=visible" also did not cause plain "zfs list" to list snapshots
-
last1
rtprio: would it be just a matter of disabling the unsupported feature on the debian side ?
-
last1
or the fact that that zfs has other features would make it not work