SeanJW
Members
-
Joined
-
-
But cache pool only can use the btrfs which performance is so poooor.
-
Yes, that you saied is why I need multi arrays. One array WITHOUT parity, can instead of poor performance pool. And one array with parity can be used for important data. I can get a saft array and a performance array at the same time, don't need to choose the safe or the performance.
-
Cache pool's IO performens is so poor, I think btrfs cause that
-
You can check the license before starting those VMs. It is so crazy to assign every function with array starting. When I try to modify some small configure, like server name, I should stop all my docker container and all my vm (someone are router and dns server, so the remote connecting will be lost), and then I can stop array, for what I want to do. But they obviously don't need array.
-
mutli Arrays +1 I want to use some disks for write-heavy tasks without parity, because it works so slow with parity. And the other disks are protected by parity for my important data. I have tried to create a cache pool for write-heavy tasks, but the IO performence is so poor. At last, I abanden the parity disk, put all disk in one arrary, and create shares only in some disks for write-heavy tasks. I'm afraid about my data in other disks, so I have to backup them weekly..
-
I had to uninstall it sadly, hope it will be fixed soon.
-
I find a file named super.old in flash, may I can move old file to instead the corrupted file? What have be configed in the super.cfg? Or I can delete it?
-
重新挪动docker和vm文件后，其他硬盘可以休眠，有一个硬盘一直不行。 这个硬盘接sata口可以休眠。其他硬盘接HBA卡也可以休眠，但是这个硬盘接HBA卡，就是不行。
-
The system crashes in a few days (about 1-7 days). Unable to Ping when crashing, can only press the button to reset. This problem has appeared several times this month. I mirror the syslog to the flash and get the following log. The file < syslog > is a crash log selected between 05:36:32 and 08:13:20 on December 22 when crash. The file < syslog-all > is all logs between opening the syslog mirror and reseting system . File < unraid-diagnostics-20211222-1004.zip > is a diagnostic. syslog syslog-all unraid-diagnostics-20211222-1004.zip
-
in old system (8100,z370m), all harddisks connect to motherboard sata port and harddisk(all are sata disk) spindown work well in new system(10900 z490m), some harddisks connect to a HBA card(ASR-78165, work in HBA/direct mode), others connect to motherboard which disks connect to motherboard spindown works well as in old system but which(1 disk without read/write) connect to HBA spindown, then spinup by read SMART operation quickly those disks' [Spin down delay] are all set to 1 hour Sep 18 15:53:41 unraid emhttpd: read SMART /dev/sde Sep 18 16:02:58 unraid emhttpd: spinning down /dev/sde Sep 18 16:09:05 unraid emhttpd: read SMART /dev/sde Sep 18 17:09:02 unraid emhttpd: spinning down /dev/sde Sep 18 17:10:26 unraid emhttpd: read SMART /dev/sde unraid-syslog-20210918-0952.zip
-
我也是一样的问题，6.92 不过我可以确定100%是6.92和HBA卡的兼容性问题。 在旧硬件系统直连主板sata，可以正常休眠 而在新硬件系统上，连接主板sata的硬盘可以正常休眠。但连接HBA卡（ASR78165）的硬盘，就无法休眠。 LOG上可以看到在spindown硬盘后马上读了smart，导致硬盘无法休眠 所有硬盘是sata硬盘
