Solverz
Members
-
Joined
-
Last visited
Everything posted by Solverz
-
In Debian 12.9 Kernal 6.1. If you enable the tunable for the I226-V (connected or unconnected), nothing hangs and it all works fine. In Rocky 9.5 Kernel 5.14. If you enable the tunable for the I226-V (connected or unconnected), nothing hangs and it all works fine. In UNRAID 7 Kernel 6.6.68. If you enable the tunable for the I226-V, where the NIC is unconnected, the system hangs... But if you have the NIC connected and enable the tunable, nothing hangs. Starting to think there is something specific to UNRAID causing this.
-
Is there a config file somewhere which lists all the drives in the array? Reason is because I am creating a simple script which uses the highest temp of the array drives for fan control.
-
Hey all, Does anyone know how to log to UNRAIDs notification system to trigger custom notifications?
-
For 4Kn drives I have noticed that if you add a new drive to the array and let it format it as xfs, the sector size in xfs is set to 512 instead of 4096. If you do the same via the pool, the sector size is 4096, great. If you format the drive via the cli with mkfs.xfs, the sector size is 4096, great. Please can explain why the 4Kn drives in the array seem to format with a default 512 sector size using xfs? Here is my tests, ignore the fact these examples use a 4Kn nvme ssd, I get the same results for 4Kn hdd, but did not have one to hand when writing this. As you can see the drive is 4Kn: root@Tower:/etc# lsblk -o NAME,LOG-SEC,PHY-SEC,SIZE NAME LOG-SEC PHY-SEC SIZE nvme0n1 4096 4096 931.5G └─nvme0n1p1 4096 4096 931.5G Created via array, sector size is 512. root@Tower:/etc# xfs_info /dev/nvme0n1p1 meta-data=/dev/nvme0n1p1 isize=512 agcount=4, agsize=61047597 blks = sectsz=512 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=1 = reflink=1 bigtime=1 inobtcount=1 nrext64=1 = exchange=0 data = bsize=4096 blocks=244190385, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1, parent=0 log =internal log bsize=4096 blocks=119233, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 Created via pool, sector size is 4096. root@Tower:/etc# xfs_info /dev/nvme0n1p1 meta-data=/dev/nvme0n1p1 isize=512 agcount=4, agsize=61047596 blks = sectsz=4096 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=1 = reflink=1 bigtime=1 inobtcount=1 nrext64=1 = exchange=0 data = bsize=4096 blocks=244190384, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1, parent=0 log =internal log bsize=4096 blocks=119233, version=2 = sectsz=4096 sunit=1 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 Created via cli, sector size is 4096. root@Tower:/etc# mkfs.xfs /dev/nvme0n1p1 meta-data=/dev/nvme0n1p1 isize=512 agcount=4, agsize=61047597 blks = sectsz=4096 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=1 = reflink=1 bigtime=1 inobtcount=1 nrext64=1 = exchange=0 data = bsize=4096 blocks=244190388, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1, parent=0 log =internal log bsize=4096 blocks=119233, version=2 = sectsz=4096 sunit=1 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 Discarding blocks...Done. You can see in the C source the default for mkfs.xfs is actually to use the physical sector of the drive, and for a 4Kn drive, this is 4096. https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/tree/mkfs/xfs_mkfs.c#n2130 Comment from source: /* * Unless specified manually on the command line use the * advertised sector size of the device. We use the physical * sector size unless the requested block size is smaller * than that, then we can use logical, but warn about the * inefficiency. * * Some architectures have a page size > XFS_MAX_SECTORSIZE. * In that case, a ramdisk or persistent memory device may * advertise a physical sector size that is too big to use. */
-
`Enable SATA link power management for...` So this tunable is to configure the LPM level? `Runtime PM for port ataX of PCI Device:... ` This tunable is to enable LPM for specific ports? `Runtime PM for disk sdX` Then what is this one for? Appreciate the help, thank you!
-
What does the below tunables actually do for the drives? I read online that they allow for the drives to enter idle Device states like D3 Hot and D3 Cold. But wouldn't this be spinning down the drives? If so, is it not better to prevent this and allow UNRAID to spin down the drives after the idle time you set? As if not, I worry these tunables will spin down the drives too quickly. Or do I misunderstood what these tunables do for drives? `Runtime PM for disk sdX` `Runtime PM for port ataX of PCI Device:... `
-
My friend, read what the warnings say 😅. The syntax you are using in the config files is deprecated and may not work in future versions. Solution: read the borgmatic docs and use the new syntax.
-
grep for the borg process so you do not have to look through all the lines manually. ps -aux | grep borg
-
Borgbackup, backs up to a repo. You can choose what you want to be backed up to this repo. So what what do you need to use rsnapshot for that borgbackup is not doing already.
-
So you have two repos, each on a separate external hard drive? Got that. Not sure what you mean on the rest? What do you mean here?
-
Please just say what you exactly want to do without using prolonged sentences and fancy words. Your post is like a riddle that we'd need to break down to understand what you are talking about.
-
/mnt/borg makes sense in normal distros but for unraid, it is best to put it in /mnt/disks/borg
-
The compaction feature has been out since Borg 1.2+, so if you only now aware of this, I would definitely recommend reading through the borgmatic and borg documentation as quite a few new features and changes have been added which may trigger you to change your method using borgmatic. For example, the syntax you use to specify remote repos and the consistency checks scheduling.
-
No worries! Yeah healthchecks is my favourite out of the options definitely and bonus it can be self hosted ☺ Oh BTW, I correct the cron schedule expression syntax, there was an extra few spaces I noticed. So it should be like the below: 0 6 * * 3
-
0 1,13 * * * borgmatic prune create -v 1 --stats 2>&1 0 6 * * 3 borgmatic check -v 1 2>&1 Hope that helps!
-
FYI, if anyones backups are failing since the latest update to this container 2 days ago, please see below: The borgmatic binary is no longer at /usr/bin/borgmatic it is now in /usr/local/bin/borgmatic. Of course, this this will only affect you if you are specifiying the full path to the borgmatic binary in your cronjob. /usr/local/bin is actually and to no surpise in the PATH env so you do not need to actually specifiy the full path to borgmatic and you can instead just put write "borgmatic" and if this path ever changes in the future you should not be affected.
-
As I like to say, "it depends". There are advantages and disadvantages to both, for instance, UD devices can be removed and installed adhoc where a pool cannot and unraid will complain if it goes "missing" Pools allow you to have redundancy, UD devices do not from the gui (as far as I am aware, please correct me if otherwise) UD can mount network shares etc and not just local media, pools is for local media only. Etc etc etc, just way up the pros and cons and see what suits your situation and setup the best and use that. ☺
-
No problem! It was probably set to read only in the template by default so that the container can only read data from your mapped directory and not modify or delete it or its contents, security hardening.
-
The error says read only file system, so the file system you are restoring too is read only. Have you checked the directory permissions or the docker path mapping? Are these read only or read/write?
-
Does the "compose pull" button, just issue the command docker compose pull or is there some way for it to also issue docker compose build? For locally created images?
-
Personally, I use borg by itself to backup everything including docker containers. As long as you use borgmatics database backup tool for the containers that have a supported database, it should be fine. ☺
-
Stop using CA-Backup and use borg exclusively.
-
Unsure, "should" be possible as it just has borg installed, however do not know enough about how the container was buikt to confirm this. BUT, you can install borgbackup directly to unraid using the nerd pack plugin and then set a script or somthing to run the borg backup server command on boot or array start.
-
Is there a way to exclude a custom file using the complete path instead of the just file name as if I just use the filename like how it is set up now then if multiple files are named the same it would skip them all when I only want it to skip the file from a specific path. for example I do not want to skip test.txt from every single directory available, I only want to skip it from a specific directory like /path/to/file/test.txt
-
Awesome, yeah not every cron supports 7 as Sunday, they usually use 0.
