d3m3zs

I have ASRock Z690 PG Riptide and bios date 2024/10/7, latest bios 2025/5/13 I can see changelog "Update CPU Microcode to 0x12F." so not sure that will fix it. But thank you, of course I will update bios today just in case. Executed lsusb -vt /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/16p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 006: Dev 002, If 0, Class=Human Interface Device, Driver=usbfs, 12M ID 0463:ffff MGE UPS Systems UPS |__ Port 008: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub |__ Port 010: Dev 004, If 0, Class=Mass Storage, Driver=usb-storage, 480M ID 8644:8303 Intenso GmbG |__ Port 013: Dev 005, If 0, Class=Human Interface Device, Driver=usbhid, 12M ID 26ce:01a2 /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/9p, 20000M/x2 ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 009: Dev 002, If 0, Class=Hub, Driver=hub/4p, 5000M ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M ID 1d6b:0003 Linux Foundation 3.0 root hub I have physically connected only 2 USB devices : UPS and USB stick with unRaid:

Changing USB port didn`t help, so I replaced Flash Drive, transferred license, I have no errors "critical medium error, dev sda" anymore, but still have these: May 25 00:21:39 BlackBox kernel: usb usb3: root hub lost power or was reset May 25 00:21:39 BlackBox kernel: usb usb4: root hub lost power or was reset May 25 00:21:40 BlackBox kernel: usb usb3: root hub lost power or was reset May 25 00:21:40 BlackBox kernel: usb usb4: root hub lost power or was reset May 25 00:21:41 BlackBox kernel: usb usb3: root hub lost power or was reset May 25 00:21:41 BlackBox kernel: usb usb4: root hub lost power or was reset May 25 00:21:42 BlackBox kernel: usb usb3: root hub lost power or was reset May 25 00:21:42 BlackBox kernel: usb usb4: root hub lost power or was reset May 25 00:21:43 BlackBox kernel: veth4a691f0: renamed from eth0 May 25 00:21:47 BlackBox kernel: eth0: renamed from vethb8aa064 May 25 00:22:05 BlackBox kernel: eth0: renamed from vethe06ff99 May 25 00:22:05 BlackBox kernel: vethe06ff99: renamed from eth0 May 25 00:22:19 BlackBox kernel: usb usb3: root hub lost power or was reset May 25 00:22:19 BlackBox kernel: usb usb4: root hub lost power or was reset May 25 00:22:20 BlackBox kernel: usb usb3: root hub lost power or was reset May 25 00:22:20 BlackBox kernel: usb usb4: root hub lost power or was reset May 25 00:22:38 BlackBox kernel: usb usb3: root hub lost power or was reset May 25 00:22:38 BlackBox kernel: usb usb4: root hub lost power or was reset May 25 00:22:39 BlackBox kernel: usb usb3: root hub lost power or was reset May 25 00:22:39 BlackBox kernel: usb usb4: root hub lost power or was reset May 25 00:22:39 BlackBox kernel: usb usb3: root hub lost power or was reset May 25 00:22:39 BlackBox kernel: usb usb4: root hub lost power or was reset May 25 00:22:57 BlackBox kernel: eth0: renamed from veth8cc70b2 May 25 00:22:57 BlackBox kernel: veth8cc70b2: renamed from eth0 May 25 00:23:57 BlackBox kernel: eth0: renamed from veth5b50cf8 May 25 00:23:58 BlackBox kernel: veth5b50cf8: renamed from eth0 Should I worry about them?

Thank you, I will do.

Thanks, here it is.

May 24 02:25:00 BlackBox kernel: usb usb4: root hub lost power or was reset May 24 02:25:01 BlackBox kernel: usb usb3: root hub lost power or was reset May 24 02:25:01 BlackBox kernel: usb usb4: root hub lost power or was reset May 24 02:25:27 BlackBox kernel: usb usb3: root hub lost power or was reset May 24 02:25:27 BlackBox kernel: usb usb4: root hub lost power or was reset May 24 02:25:28 BlackBox kernel: usb usb3: root hub lost power or was reset May 24 02:25:28 BlackBox kernel: usb usb4: root hub lost power or was reset May 24 02:26:03 BlackBox kernel: veth22a3f0c: renamed from eth0 May 24 02:26:04 BlackBox kernel: eth0: renamed from vethbda7fa4 May 24 02:26:30 BlackBox kernel: vethc664554: renamed from eth0 May 24 02:26:43 BlackBox kernel: usb usb3: root hub lost power or was reset May 24 02:26:43 BlackBox kernel: usb usb4: root hub lost power or was reset May 24 02:26:44 BlackBox kernel: usb usb3: root hub lost power or was reset May 24 02:26:44 BlackBox kernel: usb usb4: root hub lost power or was reset May 24 02:26:51 BlackBox kernel: eth0: renamed from veth42a22a6 May 24 02:27:15 BlackBox kernel: eth0: renamed from veth172f1a3 May 24 02:28:12 BlackBox kernel: usb usb3: root hub lost power or was reset May 24 02:28:12 BlackBox kernel: usb usb4: root hub lost power or was reset May 24 02:28:12 BlackBox kernel: usb usb3: root hub lost power or was reset May 24 02:28:12 BlackBox kernel: usb usb4: root hub lost power or was reset May 24 02:28:14 BlackBox kernel: usb usb3: root hub lost power or was reset May 24 02:28:14 BlackBox kernel: usb usb4: root hub lost power or was reset May 24 02:28:15 BlackBox kernel: usb usb3: root hub lost power or was reset May 24 02:28:15 BlackBox kernel: usb usb4: root hub lost power or was reset May 24 02:28:20 BlackBox kernel: usb usb3: root hub lost power or was reset May 24 02:28:20 BlackBox kernel: usb usb4: root hub lost power or was reset May 24 02:28:21 BlackBox kernel: usb usb3: root hub lost power or was reset May 24 02:28:21 BlackBox kernel: usb usb4: root hub lost power or was reset May 24 02:28:22 BlackBox kernel: usb usb3: root hub lost power or was reset May 24 02:28:22 BlackBox kernel: usb usb4: root hub lost power or was reset May 24 02:28:23 BlackBox kernel: usb usb3: root hub lost power or was reset May 24 02:28:23 BlackBox kernel: usb usb4: root hub lost power or was reset May 24 02:28:24 BlackBox kernel: usb usb3: root hub lost power or was reset May 24 02:28:24 BlackBox kernel: usb usb4: root hub lost power or was reset May 24 02:28:25 BlackBox kernel: usb usb3: root hub lost power or was reset May 24 02:28:25 BlackBox kernel: usb usb4: root hub lost power or was reset May 24 02:28:26 BlackBox kernel: usb usb3: root hub lost power or was reset May 24 02:28:26 BlackBox kernel: usb usb4: root hub lost power or was reset May 24 02:28:37 BlackBox kernel: veth172f1a3: renamed from eth0 May 24 02:28:41 BlackBox kernel: vethbda7fa4: renamed from eth0 Can anyone explain what is going on?

Ok, removed plugin and forget, author`s behavior like small school girl.

I completely removed this plugin. Manual Mover by pressing Move button doesn`t work, doesn`t matter "Disable Mover running on a schedule:" YES or NO, plugin blocks mover work. Thanks for your attention, I have no time and mood for fixing other's bugs and being beta tester.

Ah, thanks! So, if I selected first day of month, that means only during this day it will trigger plugin and decide what to do?!

Can anyone explain me this? 1. Setting calls "Disable Mover running on a schedule:" but when select YES - plugin will be disabled... Don`t get this logic. but schedule is not plugin, it is default mover settings. 2. Also how to really disable default "Mover schedule:", it seems redundant if I use plugin? 3. "Free down/prime up to this level of used Primary (cache) space:" am I right that this setting should stop mover when reach this usage %? So, 0 is fine? By default my cache utilization is 20% (dockers, VM`s etc), will it affect when I choose 0 in plugin?

If you have more than 8 parallels transcoding streams from your server at the same time. For example I have 2-4 maximum.

According to your prices I would not even think about 12600k, usual non-K 12600 looks better or 13400, depends on your needs, need more transcoding power - 12600, more threads and more future proof - 13400.

You are right, thanks, but come on, even 12100 can do 8 parallel 4K transcoding, 770 iGPU theoretically can do 16 streams.

13400, 13500.

Design issue only on top segment cpu and it is related to bios when motherboard sends 1.55V+ for core instead of 1.2-1.3, that's why update microcode helped. And also this issue didn`t affect any CPU, I have 13700KF on my gaming rig with zero issues and all my friends have 13900K and 14900KS with zero issues and only on reddit and from few YouTubers we hear about "design issue". https://community.intel.com/t5/Processors/Advise-for-New-CPU-Purchase-avoiding-any-stability-issues/td-p/1624979 https://community.intel.com/t5/Processors/Are-all-13th-gen-cpu-affected/m-p/1617824 I suppose it is really hard to at least read little bit about issues instead of listening some forum gossip and YouTubers. We need more hype

My upgrades for last few years: 4770 -> 5600G -> 12100 -> 13400 And probably will never try AMD again for server, powerful iGPU but lack of support from programs like jellyfin. I would say now best option is 12100 or 13100 - prices are almost the same, 13400 is great also - 50% expensive and performance 2 times more. 13400 is more like "just in case CPU if I would like to do ...", no difference in power consumption compared to 12100. 40 docker containers, 8 x HDD (14-18TB), 3 x nvme, when disks are spin down I have 50W power consumption, when array starts for few seconds I see 180W from socket (I use tasmota monitor plugin). Example of big rsync job when 2 x HDD work I didn`t turn off hyperthreading or turbo boost, decided use in auto, only enabled all power save features. Changing PL1 and PL2 to 65W will cut performance drastically, with such "undervolt" would be better to use some old hardware instead, result will be the same. PS Forgot to mention 13400 is 12600k, but with power limits, so technically you can buy any of them, but I would recommend install good air tower

Great plugin, thank you! Why do you need it? Ram has life warranty now, it should be tested once and forget until you decided to sell it.

You mean this ZFS drive that shows degraded? Should I check zfs in pool settings or leave all settings as auto? Because auto I have xfs in settings.

Thank you! So, instruction like you mentioned here? Stop array, add pool via GUI like from the scratch, don`t touch format, start array and wait?

Hi, everyone! I had pool zfs_mirror from two 18TB drives. Let`s call them driveA and driveB. I deleted pool and took one of this drive (driveB), formatted in XFS and used it for few days, writing a lot of data on this driveB. And now I would like to add this driveB back to the deleted pool. I can see that data on driveA is still present and I can see the pool status: zpool status pool: zfs_mirror state: DEGRADED status: One or more devices could not be used because the label is missing or invalid. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Replace the device using 'zpool replace'. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J scan: scrub repaired 0B in 08:53:51 with 0 errors on Tue Jan 14 00:28:23 2025 config: NAME STATE READ WRITE CKSUM disk_zfs DEGRADED 0 0 0 mirror-0 DEGRADED 0 0 0 sde1 ONLINE 0 0 0 15814078930758616689 UNAVAIL 0 0 0 was /dev/md1p1 errors: No known data errors Of course driveB is not /dev/md1p1, technically it is /dev/sdx for example. According to ZFS I need to run next command: zpool replace zfs_mirror /dev/md1p1 /dev/sdx But question - unraid, how to do this properly? I need to mount both drives when array stopped, then run this replace command and somehow add this as zfs_mirror pool in config? And then wait until data will be rebuild on driveB, should I start array or I should wait?

Today I received U6 Pro AP and connected it to my network via a PoE switch. My network controller automatically detected and adopted it, even without the 'Inform Host' checkbox enabled. It worked flawlessly out of the box – incredibly smooth integration! I'm glad I canceled my UCG-Ultra order, as it appears to be unnecessary for my needs. All the necessary configurations can be easily managed within Docker. Thank you all for your advice and support!

@bmartino1 thank you! 11notes/unifi is a very interesting project, taking into account that it is only one container, I can setup (theoretically) on my mikrotik router, need to try, but later.

@PeteAsking @Hoopster Thank you, going to cancel my order, tomorrow will get U6 pro and will try to adopt it. Already setup containers, according to guide, it seems for one year nothing changed in instruction. It even works and recognizes my old unifi account, was able to login and saw "No Access Points Found" what expected: BTW, does it have the same awesome features? And also if containers are offline wifi will continue working? So, containers are only for setup and monitoring, but don`t affect work?

Sorry for up this, but need advice. I have mikrotik router RB5009 and decided to buy Unifi 6pro AP (now I have grandstream AP and previously had Unifi U6-lite), thinking about buying Cloud Gateway Ultra, previously I had this device, I didn`t like this as the main gateway, I had a few times issues with failover function, but now planning to install after mikrotik just for managing AP and also as DHCP for all my clients at home, I love their informative dashboard and GUI overall. I see here many controversial messages, some people write how great and free to have docker-unifi-network-application on Unraid, but others after some time anyway buy physical device. It is not big amount of money, but is it worth purchasing separate device or is running in docker fine? Or maybe run in docker will be painful in long term perspective? That`s the question. Thanks.

Thank you, I suppose it is only format change for output, according to time format, in java that would be // Convert the input string to a LocalDate object DateTimeFormatter inputFormatter = DateTimeFormatter.ofPattern("M/d/yyyy"); LocalDate date = LocalDate.parse(inputDate, inputFormatter); // Format the date to the desired format: 21-01-2025 DateTimeFormatter outputFormatter = DateTimeFormatter.ofPattern("dd-MM-yyyy"); String formattedDate = date.format(outputFormatter); I suppose it will be smt similar on PHP // Create a DateTime object from the input date $date = DateTime::createFromFormat('m/d/Y', $inputDate); // Format the date to the desired format: 21-01-2025 $formattedDate = $date->format('d-m-Y'); But you know that better.