00:01:05 <jaredj> humph! how do you split a line in ed
00:01:36 <jaredj> you can join
00:10:57 <rdr> hey, running 15.1 w/amdgpu (RX570 iirc) after a while I'm getting corruption of Xorg video, seems to be triggered randomly by firefox playing videos?  any ideas where I should start troubleshooting?
00:11:56 <jaredj> can you play videos not-in-firefox?
00:12:08 <rdr> oh, i can play videos in firefox for a while
00:12:14 <rdr> i'm thinking maybe it's overheating?
00:12:24 <rdr> but it's not very stressful
00:12:32 <jaredj> that's what i was thinking
00:12:57 <jaredj> no i mean can you play videos not-in-firefox and does that corrupt your video after a while
00:13:04 <rdr> ooh good idea to try
00:13:05 <jaredj> like using mpv or vlc or something
00:13:21 <rdr> i was playing a video in YT Music, and had another FF window open, opened a new tab, and BAM corruption
00:13:30 <rdr> but i'll try mpv
00:23:02 <jaredj> nyarr, it doesn't seem trivially easy to upgrade to CURRENT using pkg-base
00:35:56 <rdr> hmm... unplugged my unused DualSense controller (PS5), no corruption yet :D
00:38:44 <jaredj> rdr: ???
00:39:21 <rdr> I don't know if it's related
00:39:36 <jaredj> i want your problem to make more sense than that :P
00:45:18 <rdr> haha me too
00:45:24 <rdr> but stranger things have happened
00:45:39 <jaredj> it is true
00:56:47 <jaredj> ... ok, off we go building CURRENT with -j8
04:26:11 <kevans> rdr: how much ram?
04:27:26 <CrtxReavr> All the RAMs.
04:27:40 <kevans> rdr: we've fixed some problems in main with page cacheability that could be triggered by driving the system to lowmem so that it tries to reclaim pages for the various subsystems
04:28:09 <kevans> rdr: i found a way to trigger it reliably, but I never could both trigger it and observe any foiw-up shenanigans
04:28:17 <kevans> follow-up
04:29:57 <kevans> i think mostly because my testing was too artificial, I had to drop usable memory pretty low but then it was tough to daily drive
04:31:54 <kevans> anywho,
04:31:58 * kevans &
04:36:18 <CrtxReavr> sudo kill -1 `cat /var/run/kevans.pid`
06:39:43 <runxiyu_> jails/capsicum folks, would appreciate if someone has the time to look at https://reviews.freebsd.org/D58082, thanks!
07:36:43 <rdr> kevans: I have 16GB of old DDR3(?) RAM, 8GB VRAM in the AMD RX 570 card
07:47:31 <rdr> hmmm, just caused it again. i'm gonna try and see if a different browser or even a change of firefox settings will help
07:51:09 <rdr> hmmmm seems to reliably happen when opening a github link
07:51:26 <rdr> https://github.com/B00merang-Project/Windows-Whistler
08:00:51 <rdr> oooh picom wasn't running :O
10:41:15 <polarian> kevans: I switched from uefi boot to bios.
10:41:29 <polarian> problem is one of my other servers uses seabios, which is bios-only
10:41:35 <polarian> and I did want to replicate this on that...
10:44:54 <polarian> anyways I can simply switch it back, and hopefully it just works
10:45:01 <polarian> however not getting this working with bios boot is going to be problematic
10:45:24 <polarian> worth asking on bugzilla/mailing list to see if anyone else has done it?
10:46:07 <polarian> rdr: nice card, I have an rx 580
10:46:14 <polarian> sitting in a box somewhere
10:46:22 <polarian> rx 500 series were powerhouses and were so cheap!
10:46:33 <polarian> those were the days!!!
11:47:47 <rdr> polarian: too true!  I hope having picom enabled solves the graphical corruption stuff :<
16:46:59 <polarian> im starting to wonder if its even worth emailing the freebsd mailing list or just to put issues onto bugzilla and hope I dont make a fool of myself
16:47:35 <polarian> I cant get IPv6 working inside vnet jails, host drops packet unless I ping the jail and then it works fine
16:51:09 <polarian> it makes no sense ughhhhhhh
16:51:25 <polarian> I am considering just posting it to bugzilla and if I make a cock of myself by missing some essential networking knowledge, then so be it
16:51:40 <polarian> I honestly cant figure out _why_ its happening
16:52:59 <mason> polarian: Do both! Mailing list first and then a bug after a day or so if you don't get useful bites.
16:53:20 <polarian> I hate making a fool of myself though :c
16:53:29 <polarian> at least if its IRC most people forget when it happens :p
16:53:51 <mason> polarian: It's the only way to learn. And we remember. We're like Pepperidge Farm. We remember.
16:54:22 <polarian> memory through embarrassment :p
16:54:58 <rtprio> so the host has a routable ipv6 and it's not routing to the vnet?
16:55:05 <mason> polarian: The shame gives you extra neural paths to the learning.
16:56:53 <polarian> rtprio: come to think about it explaining this is gonna be hard
16:57:00 <polarian> so I have public IPv6 addresses being routed via LLA
16:57:05 <polarian> all the routes are there
16:57:23 <polarian> when the jail tries to ping say google.com
16:57:28 <polarian> or anything, even the host addr
16:57:30 <polarian> it doesnt work
16:57:39 <polarian> it can ping the host LLA and then it will work
16:57:49 <polarian> for some reason a packet must be sent to the LLA first...
16:57:50 <mason> polarian: Have you done a packet capture?
16:57:54 <polarian> mason: yes
16:58:15 <polarian> echo request goes out, echo response comes back to the host via the phy, and then is dropped
16:58:25 <mason> oh, interesting
16:58:26 <polarian> its not passed back to the jail
16:58:31 <polarian> BUT
16:58:33 <polarian> if I leave that ping going
16:58:35 <polarian> then ping the jail
16:58:38 <polarian> boom, it now works
16:58:45 <mason> messed up arp table?
16:58:52 <polarian> this is IPv6, it would be NDP
16:58:56 <polarian> and I dont think so... NDP looks fine
16:59:06 <mason> What else could it be though?
16:59:15 <mason> Unless it's some kind of funny stateful firewall issue.
16:59:16 <polarian> mason: exactly, see why its hurting my head
16:59:21 <polarian> pf is passing quick on inet6
16:59:28 <polarian> its the first rule, no log to pflog0
16:59:42 <mason> polarian: Does that matter at all if it's going through NAT though?
16:59:48 <mason> Or is it not NAT?
16:59:48 <polarian> mason: no NAT :)
16:59:51 <mason> kk
16:59:57 <polarian> its IPv6, I am routing addresses over LLA
17:00:00 <mason> kk
17:00:14 <polarian> I might write it to freebsd-questions
17:00:31 <polarian> issue is I am currently scratching my head with trying to figure out why bhyve is being pissy
17:00:38 <polarian> I swear I waste so much time trying to get things working on freebsd :p
17:01:11 <rtprio> LLA = local link address, like fe80:: ?
17:02:16 <polarian> yes
17:04:10 <rtprio> is "public IPv6 addresses being routed via LLA" a common thing? because it sounds very weird, like something a lazy cloud provider would do
17:05:38 <mason> rtprio: How else is IPv6 routed? Honest question - I'm, again, an IPv6 noob.
17:08:13 <rtprio> the provider would give you a /48 or /56, and you'd put your jailer on :1 and route ipv6. give out addresses with rtadvd
17:08:43 <rtprio> or manually if you were so inclined
17:13:17 <polarian> rtprio: routing IPv6 over LLA is how you are meant to do it lol
17:13:41 <polarian> thats the joy of IPv6
17:14:08 <polarian> unlike IPv4 where you have to keep hopping packets over a larger subnet, you can just hop packets over LLA with IPv6
17:18:24 <polarian> https://bpa.st/PEQA
17:18:44 <polarian> I cant for the life of me to get OpenBSD to boot in bhyve either, tried 7.8 and 7.9
17:18:55 <polarian> > wrmsr to register 0xc0011029(0x3) on vcpu 0
17:18:59 <polarian> after this line it just exits
17:19:21 <polarian> exit code 0
17:19:34 <polarian> makes no sense
17:19:51 <polarian> vortexx: iirc you use OpenBSD in bhyve, you got any idea why this could be?
17:19:55 <polarian> (sorry for th eping)
17:21:36 <rtprio> iirc i had to set the console to the serial port
17:25:17 <polarian> rtprio: yeah I completely forgot that
17:25:20 <polarian> I was just thinking that haha
17:25:26 <polarian> lemme test that real quick
17:25:37 <polarian> I have been playing with tooo much arm64 openbsd, where tty is default
17:25:57 <rtprio> it's kinda silly it doesn't default to tty either
17:27:23 <polarian> indeed
17:27:27 <polarian> but freebsd doesnt either xDDDD
17:30:12 <rtprio> freebsd makes an attempt to autodetect
17:30:20 <rtprio> and the loader menu makes it less of a pain in the ass
17:31:52 <polarian> oh it does O.O
17:31:54 <polarian> shocking
17:32:02 <polarian> ive had such a pain in the arse with freebsd and serial
17:32:07 <polarian> but it works just fine when doing it via bhyve
17:32:24 <polarian> talking about that I need to bugzilla decrypt geli with bios boot via serisal
17:32:32 <polarian> because I will need it for another server
17:53:25 <rwp> rtprio, In IPv6 the expected route is using an LLA route.  But IPv6 1= IPv4 and so almost every we learn from IPv4 and try to apply to IPv6 has been changed.  Negative transference of learning.
17:53:31 <rwp> In IPv6 the expected route is an LLA-on-a-device.  So for example on a server with an Intel NIC then in /etc/rc.conf setting ipv6_defaultrouter="fe80::1%em0" is typical, where fe80::1 is the LLA router class address any/all routers on that device segment.
17:54:28 <rwp> It took me a while to realize and understand that in IPv6 the LL address is always associated with a device name.  So it is never just fe80::1 the router LL address but fe80::1%em0 down that device segment.
17:58:12 <polarian> you can think of LLA as /31 in IPv4
17:58:28 <polarian> it was messy and well, doesn't work full stop on FreeBSD
17:58:50 <polarian> LL is probably one of my most loved features of IPv6
17:59:18 <rtprio> i get LL but i guess i've never heard them just magically translate to a real public ip address
17:59:21 <polarian> alright setting up my poudriere build server rn :)
18:02:07 <rwp> The LL is not a public address.  It does not translate to a public address.  But for example fe80::1%em0 is a LL address which addresses any and all routers that are on that network segment.  It does not need to be public.  It's like 192.168.0.1 for a router address which is also not public.
18:02:49 <polarian> rwp: when I compared it to /31 I assumed that you would be using RFC1918 addresses :)
18:03:43 <rwp> But in the case of 192.168.0.1 it needs to be routed using the routing table and normally works because the device has an address on that network and so packets will route there.
18:03:59 <polarian> the way you would route a public IPv4 over a "Link layer" without IPv6 would be a /31 range in RFC1918 and then add the IPv4 public address to lo, however on FreeBSD there is no src priority
18:04:02 <polarian> unlike Linux
18:04:05 <polarian> so this doesn't work full stop
18:04:14 <rtprio> was the jail polarian setting up ipv6 lla local only?
18:04:29 <polarian> rtprio: depends what you mean
18:04:35 <polarian> the epair host side is LLA only
18:04:46 <rwp> OVH and some other hosting providers like to assign a gateway that is not routable, it's in another subnet, and so packets there have no way to route there, requiring a host route to be added to the host table on that network segment.  IPv6 bypasses that by including the device in the route.
18:04:47 <polarian> the epair jail side, has the IPv6 address, and a LLA (obv)
18:05:06 <polarian> rwp: this isnt OVH, this is my own network
18:05:13 <rtprio> and was the jail supposed to be be publicly accessable?
18:05:19 <polarian> yes
18:05:31 <rwp> polarian, I never said your network was OVH.  Why would you think that?
18:05:35 <polarian> ohhh
18:05:38 <polarian> you werent replying to me
18:05:44 <polarian> or you were
18:05:46 <polarian> idk
18:05:48 <polarian> im so confused :p
18:06:07 <polarian> I will write up the issue im having with IPv6 and jails to the ML shortly, because its hurting my brain to comprehend it myself, so nobody in an IRC chat will understand either
18:06:11 <rtprio> so if the jail is supposed to be be publicly accessable, and it only has a lla address, then there has to be some translation
18:06:16 <rtprio> or it wouldn't be reachable
18:06:26 <rwp> Correct.
18:07:00 <rwp> If the jail is supposed to be publicly accessible then I think it should have a public address.  Or NAT.  But a public address is just more sensical.
18:07:18 <rtprio> which is why i was wondering why use LLA in this case
18:07:30 <polarian> rtprio: no because the packet is ROUTED over LAA
18:07:32 <polarian> LLA*
18:08:10 <polarian> the src header is still the IPv6 address, the route simply says send it to fe80::1%jail0 for example
18:08:17 <polarian> the scope is important here too
18:08:25 <rwp> You have to transport your mind back to the 1990s when IPv6 authors were developing things.  They didn't like any centralization.  So almost everything is decentralized and configured on the client.  By using an LLA for the route the client can pretty much do it independent of any centralized DHCP daemon or whatever.
18:08:38 <polarian> I usually use fe80::1 for host, and fe80::2 for jail/vm
18:08:39 <rtprio> well, yeah, i can not fathom how that would work without the jail having a real ipv6 address
18:08:46 <rtprio> but rwp claims it should work
18:09:01 <polarian> rtprio: there is an IPv6 address in the vm
18:09:04 <polarian> you have two addresses
18:09:26 <rtprio> i guess i don't see the point
18:09:35 <rwp> rtprio, I didn't say the jail did not need an IPv6 address.  I said the jail routes over an LL address.  I think the jail needs a public IPv6 address.  Or some complexity such as NAT.
18:09:40 <polarian> you have the LLA address, and the IPv6 address attached to the vm, host side however, I have only a LLA address on the host epair, this is because the host already has an IPv6, why would I use more on the host?
18:09:48 <polarian> instead I can route IPv6 to containers and vms using LLA and static routes
18:10:03 <rtprio> polarian: that might be true, if it worked
18:10:09 <polarian> rtprio: it does work
18:10:16 <polarian> and its how IPv6 was designed lol
18:10:47 <rtprio> polarian: this conversation started when you said it only works if you ping it first?
18:10:57 <polarian> yes...
18:11:01 <rtprio> so it doesn't work
18:11:07 <polarian> well not flawlessly :p
18:11:16 <polarian> but this isn't down to the theory being wrong
18:11:25 <rtprio> your truck "Doesn't work" if you have to open the hood and start it with a screw driver
18:11:44 <rtprio> can you drive to the autoparts store? yes. but it doesn't work
18:11:53 <polarian> alright fine, if you want to be fussy
18:11:55 <polarian> it doesn't work
18:12:00 <polarian> but it should, because this is expected behaviour
18:12:09 <polarian> happy?
18:12:12 <rwp> I am reading that your configuration is not working.
18:12:24 <polarian> so its either A: I configured it wrong or B: theres a bug
18:12:41 <rtprio> i've done some wacky thigns with ipv6 routing, and its' worked on the first try but none of it involved lla
18:12:53 <polarian> you dont route over LLA?
18:12:55 <polarian> yikes.
18:13:12 <rtprio> you missed the part where i said it worked
18:13:21 <polarian> sure it works not to use LLA
18:13:42 <rtprio> in this case, these hosts were not local
18:13:48 <polarian> but you really should, the added benefit is you can change the IPv6 addresses and not the routes. :p
18:13:57 <polarian> hm?
18:15:31 <rwp> It's not required that the route be over an LL address.  That's just the expected configuration.  But routing over a public IPv6 address also works.  And again some hosting providers only document that configuration too.  (I won't mention one so that you don't think I think you are hosting there.)
18:18:52 <rtprio> it's hard for me to give a shit about ipv6 right now since my network is in shambles and my provider doesn't know what it ipv6 is
18:18:53 <polarian> slightly offtopic but who here uses linkedin? people keep bashing me for not using it and saying its the only way to get employed these days
18:19:13 <polarian> I feel deeply uncomfortable putting my face on a profile, with all my info fed right into a big tech slop machin e
18:19:23 <rtprio> i have an account, but linked in is insufferable to use these days
18:19:48 <polarian> my cv gets ignored, my emails get ignored, my applications get ignored, and people tell me its because linkedin is the ONLY way these days
18:20:23 <rtprio> i can't say that's true, the market is shite
18:20:42 <rtprio> all cold applications suck
18:21:52 <polarian> welp I guess I can make one again, leave it up 3-6 months, if I get hired then cool, if not then maybe I can consider deleting it after.
18:22:20 <polarian> I know this is more of an openbsd thing to say, because freebsd people arent insanely paranoid, but linkedin is so good for being socially engineered
18:22:30 <polarian> people attack your connections, get info on you through that, and then exploit that info to pwn you
18:23:10 <polarian> if I cant keep myself secure, because $JOBS demand not to, how do I keep my services secure? is security just impossible!?!?
18:23:32 <polarian> also for the record, asking me to use linkedin is like asking me for nudes... genuinely.
18:24:26 <rtprio> i did see a llm script to brute force apply for any and all jobs matching particular keywords, via linkedin
18:25:51 <polarian> At the age of 21 I have turned into a fucking 80 year old I swear
18:25:56 <polarian> I just moan about all modern stuff :p
18:25:59 <boru> I recommend getting offline for a while. Do your networking in real life. This is the magic sauce these days.
18:26:30 <dnp1> polarian: Nah, not 80 at all.
18:27:01 <polarian> boru: literally just came back from a cybersec conf
18:27:20 <boru> People hiring (myself included) aren't going to go though the 500 resumes they get after 2 days. There's just no time for that. You just get lost in the noise if you apply the classic way.
18:27:39 <polarian> boru: I know that, but nobody is hiring full stop in person either... unless I hit a gold mine by asking the right person at a conf
18:27:42 <boru> Networking is king again.
18:28:13 <polarian> I have met many MANY people :)
18:28:28 <polarian> idk I feel like networking in open source is a waste of time for employment
18:28:46 <polarian> most people I bump into are either unemployed or funded through some nlnet fund
18:28:47 * rdr firmly handshakes boru
18:28:49 <boru> Probably. If you're looking for a paying job, you should probably look for companies that pay you to work.
18:29:01 <polarian> boru: harder and harder to find these days
18:29:16 <polarian> maybe this is just a UK issue?
18:29:27 <polarian> I heard BSD folks in other countries, even younger ones have no issue finding work
18:29:29 <boru> No, it's not really. It's the just methods to get a job that have worked for a coupled of decades don't work anymore.
18:29:40 <boru> So, change tactics.
18:29:48 <polarian> I have tried all the tactics lol
18:30:11 <boru> It probably feels that way, but really, networking is king these days again.
18:30:12 <polarian> asked IRL, I have spent ages optimising my CV to get pass HR, different platforms etc
18:30:18 <polarian> well networking is always best
18:30:27 <boru> Therein is your problem, you want to go direct to engineers, not through HR.
18:30:34 <polarian> I have shot off tons of emails to firms which I match best, and none of those are hiring ever...
18:30:52 <polarian> boru: also I find it rather humliating crying at conferences about work
18:31:21 <boru> Well yes, it should feel that way. No one is going to hire someone that cries about work.
18:31:29 <polarian> but excl self employment (which isnt enough to put food on the table) I havent worked in 1.5 years now...
18:31:40 <polarian> well I have non-profit positions but those arent hard to get
18:31:46 <polarian> people dont say no to free labour (usually)
18:32:06 <polarian> boru: alright I dont cry... but I feel like even bringing it up can be a big red flag
18:32:11 <boru> That's nice, but it's energy wasted on not finding a paying job.
18:32:12 <rtprio> my last three jobs have all been word of mouth
18:32:17 <polarian> and I get uncomfortable when people are like "oh so what do you work as"
18:32:24 <polarian> and I panic and try to dodge the questi0on
18:32:44 <rtprio> those resumes are on the top of the 200-500 others
18:33:24 <polarian> welp just gotta keep trying ig... everyone I know got hired via being messaged on linkedin
18:33:40 <polarian> and I have resisted it for 1.5 years, but at this point, it cant hurt
18:33:47 <polarian> contracts have dried up too
18:33:52 <boru> Yeah, you're already fighting a losing battle there. Better off focusing your effort on what you want to do; "I hear you guys are hiring for X. I can do that with my eyes closed. Want to grab a beer?"
18:34:10 <polarian> boru: bribe with beer you say? :p
18:34:17 <polarian> get em drunk enough to think you are actually smart!
18:34:19 <polarian> xD
18:34:20 <boru> Don't be obtuse.
18:34:30 <polarian> (im kidding btw)
18:34:49 <boru> If you're good at what you do, then present that face, not "I am desperate for a job please hire me"
18:34:59 <polarian> I dont do the latter though
18:35:04 <polarian> I just get uncomfortable about the topic
18:35:12 <boru> It's your opportunity to interview _them_ to see if _you_ want to work there.
18:35:19 <rdr> the only thing worse than having a job is looking for one...
18:35:26 <polarian> lol
18:35:34 <boru> Well, the sooner you get over being uncomfortable, the better. That's a you problem.
18:35:40 <polarian> I swear employment is like rocket science
18:36:06 <polarian> so many ifs and buts, and conflicting info
18:36:41 <rdr> i installed freebsd yesterday, got a job offer today 300k starting ;)
18:36:55 <rdr> just kidding, it's hard out there
18:37:04 <boru> "I installed FreeBSD and my wife loves me again!"
18:37:15 <rdr> :D
18:37:39 <boru> Yeah, on a serious note, the market is shite at the moment. I understand that it's demotivating, but honestly, the jobs are there, you just need to change tactics.
18:38:29 <boru> People hiring are also exhausted with all of these LLM applications from very specific places. A lot of jobs (IME) don't get listed anymore unless there's no choice.
18:38:47 <boru> Network first, go external as a last resort.
18:39:20 * rdr sets up a home network and then doesn't know what to do next. Networking...
18:39:38 <boru> Yeah, sorry, I'm also off topic now. I will be quiet.
18:39:49 <rdr> yeah sorry about that
18:40:18 <boru> Final say: don't waste you time on linkedin. It's for muppets.
18:40:38 <polarian> oh for fuck sake, Linkedin has ID checks now?
18:40:48 <polarian> and it requires a mobile phone? this aint going to work on a custom rom
18:42:11 <polarian> boru: what more do you want to network, I am regularly at events and meet many MANY people, you know how many have been able to hire people? 0
18:42:13 <polarian> not a single one
18:42:20 <polarian> actually thats a lie
18:42:30 <polarian> there has been, I just dont talk to them as I have no way to approach them
18:43:32 <boru> "Is your hiring manager here? Can you introduce them to me?"
18:43:42 <boru> That will be 500€. My fees are quite reasonable.
18:44:16 <boru> If you want to streamline things, talk to the people actually doing the hiring, not some rando.
18:44:36 <boru> It's good to talk to engineers to find out what it's actually like there, though.
18:44:52 <boru> You don't want to jump from the frying pan into the fire, and all that.
18:44:59 <polarian> right
18:45:09 <polarian> so hiring managers put a big sign on the head and say "HIRING MANAGER, COME HARASS ME"
18:45:30 <polarian> in fact I lied I spoke to one on Sunday, and he said outright, no hiring manager makes themself known
18:46:37 <boru> Obviously. But people will introduce you if you play your cards right.
18:47:32 <polarian> this feels like playing a game of chess
18:47:32 <sbr> After having linkedIn being the only social media I was on for the last ~10 years or whatever it was, I deleted my account last year. Its such a waste of life and devoid of any real value.
18:47:40 <polarian> checkmate being speaking to a hiring manager lol
18:48:01 <rdr> got steam running yay
18:48:02 <boru> You're right. It's too hard. Best to give up.
18:48:10 <rdr> oops crashed
18:48:29 <polarian> boru: well its not like I have a choice eh? :p
18:48:37 <polarian> rdr: you using linuxator?
18:48:48 <rdr> yes'm
18:48:50 <polarian> I hope you jailed steam?
18:49:00 <polarian> it likes to shit over your system :p
18:49:01 <rdr> it's it's own user at least
18:49:23 <polarian> ah that works
18:49:41 <rdr> just followed the instructions
18:49:45 <rdr> that tends to work most of the time ;)
18:50:05 <polarian> theres instructions?
18:50:10 <polarian> I wish I read those for once :p
18:50:35 <rdr> haha, combination of gemini feeding mostly true (but somewhat wrong) info and then the package when installed gave the correct info
19:18:00 <mosaid> Hi
19:20:07 <mosaid> I have little problem here, for 3 years now.. any ntfs partition I mount in my system, just get broke when copy/move files to it.
19:21:03 <mosaid> and need to reformat to get it workable again
19:21:28 <mosaid> I mostly use ntfs 3g
19:23:56 <rtprio> i didn't know ntfs-3g supported writes, i've only used it for reads
19:24:03 <rtprio> i would suggest, not writing to it anymore
19:29:58 <mosaid> I used to think the drive is died, but I tested another drive 100% health still the same
19:35:47 <mosaid> now, I will just use my winxp vm to copy files
19:38:14 <mosaid> but I need fix, to safely mount my new drive in rw mode
19:54:15 <polarian> rtprio: ntfs-3g works fine for writes
19:54:31 <polarian> I have written to ntfs-3g befor eafaik
19:54:35 <polarian> unless I am misremembering
19:56:14 <mosaid> polarian: then could you help me?
19:58:38 <polarian> mosaid: did you mount with rw as the option?
19:58:48 <mosaid> yes
19:59:06 <polarian> https://www.freshports.org/filesystems/ntfs
19:59:13 <polarian> and you did install this port right?
19:59:51 <polarian> iirc the driver and the tool are in different packages or something
19:59:57 <polarian> I believe you need ntfs and ntfs-3g
20:00:01 <polarian> but ntfs pulls in ntfs-3g as a dep
20:02:53 <mosaid> yes installed them well
20:03:45 <polarian> hmmm
20:03:49 <polarian> not too sure sorry :/
20:03:54 <polarian> I remember it working for me
20:04:02 <polarian> im not really smart enough for this :p
20:06:47 <mosaid> it gives mostly i/o errors, which gives the feel of failing drive.. but after deep test everything is fine
20:07:22 <polarian> whats the smart output?
20:07:27 <polarian> can you show the output of smartctl -a
20:07:37 <polarian> you are free to redact identifiable data like the serial number
20:07:51 <mosaid> and need reformat it to get the partition in workable state
20:07:55 <mosaid> Ok
20:08:12 <mosaid> but I used two new drives still the same
20:08:42 <mosaid> impossible to be the problem in drives not ntfs 3g
20:15:13 <mosaid> polarian: see https://dpaste.com/3JRVRTS8A
20:17:21 <polarian> yeah disk looks fine
20:18:43 <mosaid> ntfs 3g is the problem
21:13:35 <rtprio> mosaid: are you dualbooting with it?
22:05:16 <mosaid> rtprio: no
23:29:39 <rtprio> those of you who use unbound as a local resolver; do you also have bind or some other primary dns or do you have a lot of local-data lines for some local names?
23:30:22 <mosaid> Look like I destroyed my drive using dd :'(
23:31:07 <mosaid> first sector now unreadable
23:33:55 <luser> rtprio: I used NSD for my local DNS authority and unbound as the resolver, which either forwards to NSD for local resolution, or DoT for external.
23:37:10 <rtprio> wait what were you doing with dd ?
23:37:35 <rtprio> luser: i guess i'm lazy and kind of don't want a second service?
23:38:04 <luser> rtprio: and that's fine.
23:38:27 <rtprio> i haven't cleaned up bind yet, but haven't fully migrated yet either
23:38:48 <luser> I have considered consolidating to unbound, but I have multiple NSD services for redundancy and it syncs between, so I only update the primary.
23:39:29 <rtprio> i manage my zone files with puppet, so i don't have to use primary/secondary of the nameserver
23:40:22 <luser> That's a good method.
23:43:34 <dnp1> rtprio: I just use bind here.  Leveraged kea to keep a dynamic zone updated.
23:45:23 <rtprio> ah, i forgot all about dhcp/dns updates
23:50:03 <mosaid> I am so stupid :P saw a howto wipe disk, so I can partitioning on solid ground.. he used dd to wipe begining and end
23:50:13 <mosaid> for ntfs
23:50:57 <mosaid> but due to my low expernice in drives world, I am made wrong
23:51:04 <rdr> uh oh, why did you need to wipe it?  couldn't you just reformat the drive?
23:52:09 <mosaid> I used my winxp vm, but as I said to when I used ntfs-3g the drive completly corrupted alot of I/O errors
23:52:30 <mosaid> I tried just format didn't work, so need to wipe the disk
23:53:00 <rdr> oh
23:53:10 <rdr> sounds rough
23:54:08 <mosaid> drive is so healthy 100%, just ntfs-3g
23:55:08 <Macer> Took a look to see if an arc a310 was supported in fbsd and it seems arcs still have issues
23:55:23 <Macer> But then again it’s using the drm-kmod stuff
23:57:17 <mosaid> Wipe the beginning: dd if=/dev/zero of=/dev/da0 bs=1m count=1
23:57:18 <mosaid> The end: dd if=/dev/zero of=/dev/da0 bs=1m oseek=`diskinfo da0 | awk '{print int($3 / (1024*1024)) - 4;}'`
23:58:03 <mosaid> Is this right
23:58:26 <mosaid> see also https://chieflemming.wordpress.com/2020/01/08/formatting-partitioning-and-mounting-drives-for-ntfs-with-freebsd-and-mac-os-x/
23:58:44 <mosaid> talking about some bug in ubilo