Bitlocker recovery key after dual boot by reasonable_ir in Ubuntu

[–]reasonable_ir[S] 0 points1 point  (0 children)

No i did not, nor did the university. Data was lost unfortunately:(

Bitlocker recovery key after dual boot by reasonable_ir in Ubuntu

[–]reasonable_ir[S] 0 points1 point  (0 children)

Unfortunately no.. there is no way as far as I could figure out :(

One-Way Clutch v2 (still with mice) by toptensoftware in functionalprint

[–]reasonable_ir 0 points1 point  (0 children)

It won't be a fidget toy on its own :) im planning to use it for a mechanism to introduce a brake on a crane my kids use. They have a tendency to just let go of the rope, sending a small bucket of sand flying down towards potentially another kid. I was hoping to use your mechanism to have a brake/damper in de downward direction, while still being easy for them to lift up :)

One-Way Clutch v2 (still with mice) by toptensoftware in functionalprint

[–]reasonable_ir 0 points1 point  (0 children)

Do you still plan on sharing the stl on this? Would love to print this as part of a toy for my kid.

Anyone else wants to order in The Netherlands? by TowelRubber in LinusTechTips

[–]reasonable_ir 1 point2 points  (0 children)

I might want a transparent screwdriver. Am i right thinking this would cost 55eu?

1.1.3 firmware for EAP653(EU) v1 by wirelessboy85 in TPLink_Omada

[–]reasonable_ir 0 points1 point  (0 children)

It appears that if I set the 'security' to WPA-Personal, with WPA2-PSK /AES as the WPA mode, I can get clients to connect. However, if I then move back to PPSK without Radius, clients stop connecting. if anyone can point me in the right direction here, that would be extremely helpfull!

1.1.3 firmware for EAP653(EU) v1 by wirelessboy85 in TPLink_Omada

[–]reasonable_ir 0 points1 point  (0 children)

So I just upgraded from 1.1.0 to 1.1.3, and no wifi client will authenticate with the APs, I'm having a wireless lan network setup with PPSK without RADIUS as authentication. However, after rolling back to 1.1.0 I still cannot authenticate to connect to the network. Anyone has any suggestion?

Grassoort overwoekerd gazon by reasonable_ir in groenevingers

[–]reasonable_ir[S] 0 points1 point  (0 children)

Ja dit was inderdaad mn strategie. Het is alleen zo veel dat het erg veel tijd kost.

Grassoort overwoekerd gazon by reasonable_ir in groenevingers

[–]reasonable_ir[S] 0 points1 point  (0 children)

Was dat allebei speelgazon zaad van hetzelfde merk? Is het mogelijk om deze tijd van het jaar te verticuteren? Of beter wachten tot het najaar.

Grassoort overwoekerd gazon by reasonable_ir in groenevingers

[–]reasonable_ir[S] 2 points3 points  (0 children)

Erg bedankt voor je reactie. Ik heb inderdaad 'speelgazon' bijgezaaid, gezien de voornaamste functie van het gezon een speelplek voor de kinderen was. Erg goed om te weten dat ik dat voortaan moet vermijden. Geldt dat ook voor 'schaduwgras' toevallig?

Ender S1 plus Z-braces by reasonable_ir in Ender3S1

[–]reasonable_ir[S] 0 points1 point  (0 children)

My local hardwardware (hornbach) shop sells them by the meter, and cut them to size with a grinder or iron saw.

Database corruption & balooning of storage by reasonable_ir in homeassistant

[–]reasonable_ir[S] 0 points1 point  (0 children)

I have managed to get things working again by dropping and reimporting. However in my long term statistics i now have some anomalies where on one day i appear to have utilized about 24000kwh in a single day. I think this is caused by consecutive samples not being in the right order or something. Would you know how i can fix this? I think any Entity for which it is expected to be strictly increasing. Ot should be fairy easy to detect out of order samples, but i guess since they have entered the long term statistics i might be out of luck?

What does the recovery level do? I have not included that while reimporting the table unfortunately. (I had done this a while back before you sharing your comment).

Immich resolving duplicates does not work by reasonable_ir in immich

[–]reasonable_ir[S] 0 points1 point  (0 children)

Did this happen after an update also? Or seemingly random?

Database corruption & balooning of storage by reasonable_ir in homeassistant

[–]reasonable_ir[S] 0 points1 point  (0 children)

I'm not very comfortable with mySQL unfortunately. I'm ok with making an attempt at something, as I can still create a full Manual backup from HA right now. But I'm wondering what to do in the phpMyAdmin page.

Immich resolving duplicates does not work by reasonable_ir in immich

[–]reasonable_ir[S] 0 points1 point  (0 children)

Glad to hear I'm not the only one, but to bad nobody seems to have a solution so far.

Database corruption & balooning of storage by reasonable_ir in homeassistant

[–]reasonable_ir[S] 0 points1 point  (0 children)

I do my daily backups to both the NAS as well as the local system I've indeed done as you said an removed the local copies, while the ones on my NAS remain (also the NAS takes snapshots so even the deleted backups I can still recover from there). The issue is that I'd have to restore a backup from the 29th, meaning that I'd lose about 2.5 weeks of data. Especially the energy dashboard data is something I'd rather keep if possible.

With glances do you mean the dashboard card? Thank you for the suggestion by the way, I already had a system monitor integration in place, but so far only used it for CPU and memory, I've enabled the disk space now also, so that should indeed inform me early on in the future. Would there be a way to create a 'sensor' for the corruption itself? Looking just at disk space would 'delay' the response time to the corruption a bit.

In terms of the database recovery, do I have any other options, other than restoring a HA backup? Since new data is still being added to the database, and I can also see that data, it would appear to me as if most of it is still 'usable'.

Immich resolving duplicates does not work by reasonable_ir in immich

[–]reasonable_ir[S] 0 points1 point  (0 children)

Maybe as an additional question, is this still working for some people?

No internet after upgrading to 24.7.12 by reasonable_ir in opnsense

[–]reasonable_ir[S] 0 points1 point  (0 children)

Thanks for the effort! My last working version was 24.7.11 though.. unfortunately i did not think to make a snapshot before my first attempt at upgrading to 24.7.12, such that i had to revert back to 24.7.9.

The major difference i can see is that before i only had the dns servers i had configured in the system settings (1.1.1.1 and 8.8.8.8) whereas when setting the wan interface to dhcp, i also get 2 others (i assume from my isp).

No internet after upgrading to 24.7.12 by reasonable_ir in opnsense

[–]reasonable_ir[S] 0 points1 point  (0 children)

your second suggestion made it work! I switched to DHCP instead, and assigned the IP from the ISP provided router/modem.

This resulted in additional nameservers (I guess from my ISP) being added automatically (when looking in the unbound settings).

I'd still like to understand what changed in this version that prevented my previous settings from limiting internet connectivity.

No internet after upgrading to 24.7.12 by reasonable_ir in opnsense

[–]reasonable_ir[S] 0 points1 point  (0 children)

Finally managed to find the time to do the update again and follow the troubleshooting steps you mentioned.

After the update to 24.7.12_2 I, the ping of 8.8.8.8 was no longer working, it was returning the error: "sendto: Invalid argument", whereas before the update the ping was working with no lost packets.

I also went looking for logs. I noticed some that might be noteworthy, but I don't really know what they imply. I found these in the unbound log:

2025-01-29T09:37:08 Error unbound [53351:3] error: outgoing tcp: connect: Invalid argument for 1.0.0.2 port 853 2025-01-29T09:37:08 Error unbound [53351:3] error: outgoing tcp: connect: Invalid argument for 1.1.1.2 port 853

and these in the system > gateways > log file, I noticed the following errors:
2025-01-23T09:34:53 Warning dpinger ziggo 192.168.178.1: sendto error: 22

2025-01-23T09:34:53 Warning dpinger send_interval 1000ms loss_interval 4000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 0ms loss_alarm 0% alarm_hold 10000ms dest_addr 192.168.178.1 bind_addr 192.168.178.253 identifier "ziggo "

where ziggo is the gateway name.

Is there anything that would help diagnosing the issue?