trott
Members
-
Joined
-
Last visited
Everything posted by trott
-
the btrfs send in schedule setup is not working, log as below, it might because I select snap send incremental, but it is the first time the schedule run and no snapshot has been created before: Jul 2 10:51:47 Tower snapshots: btrfs subvolume snapshot -r '/mnt/ssd/backup/wei' '/mnt/ssd/.snapshot/wei_20220702105147.daily' OK Create a readonly snapshot of '/mnt/ssd/backup/wei' in '/mnt/ssd/.snapshot/wei_20220702105147.daily' Jul 2 10:51:47 Tower snapshots: btrfs snapshot send -p / /mnt/ssd/.snapshot/wei_20220702105147.daily To /mnt/disk10/.snapshot/ Error ERROR: empty stream is not considered valid screenshot of the setting:
-
你设置的docker mirror没有？国内的几个mirror现在好像都不行
-
thanks for this great plugin, I used to manually create subvol on each disk for my share, then do the snap via script; I played this plugin yesterday, it works well and below is my findings 1. when you click the button to create the snapshot, it will allow you to select to create a read-only snapshot, but there is no such selection in schedule setup 2. I had though the read only selection on the page is the option used for snapshot, but actually it is not, when you select it, it actually will put the whole user share to read-only, it is better to have a remind here, or it will surprise people
-
same here, anyone know how to fix this?
-
I have a 3 disk btrfs cache with raid1, I'd like to remove one disk from the cache, can I simple use btrfs device delete 3 /mnt/cache or I need to stop the array, remove one disk from the cache pool and start the array again?
-
usually for wireguard, you only need to forwarder the wirguard port on UDM Pro to urnaid IP, all other port are still close to public
-
Guys, when I using the VF on VM, it cannot talk to the VM on br0, do you guys has this issue?
-
如果主要为了moments，你第一时间就没必要选择unraid
-
thanks for the how-to, is it possible to assign the VF to docker container?
-
check your bios setup, I believe the fan control setting in bios should be smartfan, I using the same board and plugin works without issue
-
-
not sure what's the issue here, but after update to beta25, I just notice fstrim -v /mnt/cache take forever to complete; the iotop shows it take 100% with 0 bype read/write
-
yeah, this is also my concerns, I just ordered another 14t HDD, and plan to convert the pool to raid 10
-
since 6.9 has multi-pool support, I setup a btrfs raid-5 pool with three 14T HDD, the issue I find is the slow scrub speed, only around 40MB/s, it might take 3 days for a single scrub if I have 10T data on it, is it normal?
-
Hi, when the plugin will be updated to use the data from emhttp?
-
I'm mix sata ssd, hdd and sas hdd on the same lsi 3408 with an expander without any issue
-
Can we have different HDD groups to control the fan speed instead of only the max temp
-
I think I just wait for the 5.9-rc1, I'm on ryzen, I need 5.4 kernel to test ECC
-
RC8 ha revert kernel back to 4.19, so it might be the issue
-
try to change the Power Supply Idle Control in bios to typical current idle, I'm fine with that using x470+3700x
-
thanks, I think I might try later; what this plugin will modify the system when active the tunnle? like iptables ...
-
ok, I add a peer with remote to Lan access, the tunnel can be activated(with mobile data connection), but I cannot connect the server by IP; I disconnect the tunnel, now I cannot even connect to server on the laptop in the same lan, enven ping cannot be reached; now I totally lost connection to the sever(web or ssh)
-
it will be great if this plugin support running custom scripts before and after the mover, so we can have script to stop vm/docker before mover running and restart them after mover is finished
-
-
I just updated to 6.8-RC1, with ryzen 3700x and ECC ram, I got following error in log, it suppose to be a kernel issue root@Tower:~# dmesg | grep EDAC [ 0.505230] EDAC MC: Ver: 3.0.0 [ 21.472853] EDAC amd64: Node 0: DRAM ECC enabled. [ 21.473283] EDAC amd64: F17h detected (node 0). [ 21.473715] EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) [ 21.474154] EDAC amd64: Error: Error probing instance: 0 [ 21.496227] EDAC amd64: Node 0: DRAM ECC enabled. [ 21.496659] EDAC amd64: F17h detected (node 0). [ 21.497100] EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) [ 21.497537] EDAC amd64: Error: Error probing instance: 0 [ 21.517185] EDAC amd64: Node 0: DRAM ECC enabled. [ 21.517620] EDAC amd64: F17h detected (node 0). [ 21.518067] EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) [ 21.518504] EDAC amd64: Error: Error probing instance: 0 [ 21.537210] EDAC amd64: Node 0: DRAM ECC enabled. [ 21.537643] EDAC amd64: F17h detected (node 0). [ 21.538090] EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) [ 21.538527] EDAC amd64: Error: Error probing instance: 0 [ 21.558282] EDAC amd64: Node 0: DRAM ECC enabled. [ 21.558716] EDAC amd64: F17h detected (node 0). [ 21.559166] EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) [ 21.559603] EDAC amd64: Error: Error probing instance: 0 [ 21.579233] EDAC amd64: Node 0: DRAM ECC enabled. [ 21.579666] EDAC amd64: F17h detected (node 0). [ 21.580114] EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) [ 21.580552] EDAC amd64: Error: Error probing instance: 0
