tuxbass

Members
  • Posts

    162
  • Joined

  • Last visited

Converted

  • Gender
    Male
  • Location
    Europe

Recent Profile Visitors

3031 profile views

tuxbass's Achievements

Apprentice

Apprentice (3/14)

7

Reputation

  1. There's a possible duplication under 'Share activity' tab: ** /mnt/user/backup ** Mar 25 05:19:00 OPEN => /mnt/disk1/backup/repo/config Mar 25 05:19:00 OPEN => /mnt/disk1/backup/repo/data/6/62605 Mar 25 05:19:00 OPEN => /mnt/disk1/backup/repo/data/6/62606 Mar 25 05:19:00 DELETE => /mnt/disk1/backup/repo/data/6/62605 ** /mnt/user/data ** Mar 25 05:18:56 OPEN => /mnt/disk1/backup/repo/data/6/62660 Mar 25 05:19:00 OPEN => /mnt/disk1/backup/repo/data/6/62605 Mar 25 05:19:00 OPEN => /mnt/disk1/backup/repo/data/6/62606 Mar 25 05:19:00 DELETE => /mnt/disk1/backup/repo/data/6/62605 Listing said shares: # ls -lt /mnt/user/data total 4.0K drwxrwxrwx 1 tuxbass users 92 Jul 24 2023 win-10-user-setting-backups drwxr-xr-x 1 tuxbass users 28 Aug 25 2022 media drwxr-xr-x 1 nobody users 158 Aug 5 2021 Documents drwxrwxrwx 1 root root 0 Mar 4 2021 vm_backups drwxrwxrwx 1 tuxbass users 194 Aug 23 2020 win10-bt-drivers # ls -lt /mnt/user/backup/ total 0 drwx------ 1 root root 92 Mar 25 05:19 repo drwx------ 1 root root 32 Jul 12 2023 vms Note data share doesn't show any modifications as of late. The activity above is expected to be under the backup share alone. Any idea as to why above activity is listed also for /mnt/user/data share?
  2. DNS images such as the bind9 usually ask to start the container in host network. This however is blocked by dnsmasq service used by KVM. What is odd is I've already been running bind (and VMs) for years, but only now stumbled upon this problem. 1. how is this possible I haven't been affected by this problem before? Haven't changed any settings, containers nor VMs in months, and this config (roughly speaking) is 6+ years old on my system. 2. what's the correct way to go about standing up bind9? Use br0 network instead of host and ask for its own static IP from the router? Running Unraid 6.12.6
  3. Hence my question regarding installing Windows onto the unassigned m2 drive. Yup, which I tried to solve some few years back with no luck, and decided to just turn a blind eye on.
  4. Yes, agreed. My point was - could the Windows installation in this dual-boot setup have caused it, or it's just a coincidence and I'm really looking at another drive failure here? The timing is just too close for a coincidence, in my experience.
  5. I believe that is a red herring. The cache drive has been showing those errors for over a year now. Have tried changing the cables to no avail. It's not a show-stopper of an error so I've just learnt to live with it. Including diagnostics from ~ year ago when cache mounted just fine: tower-diagnostics-20220606-2221.zip
  6. System has following drives: - 3x4TB HDDs (array) - 500GB SSD (cache, sdb) - 512GB unassigned nvme m.2 Installed Windows 11 directly onto the nvme and all looked fine. While in windows, the other drives weren't even listed in the 'My Computer' section, but I disabled SATA controller just in case. Now when I booted back into Unraid, the cache drive no longer mounts: 1477:Jul 26 15:58:52 srvr emhttpd: shcmd (42): mount -t xfs -o noatime,nouuid /dev/sdb1 /mnt/cache 1479:Jul 26 15:58:52 srvr kernel: XFS (sdb1): Mounting V5 Filesystem 1581:Jul 26 15:58:54 srvr root: mount: /mnt/cache: can't read superblock on /dev/sdb1. What gives? Is it just a coincidence or windows managed to write something on that drive? srvr-diagnostics-20230726-1603.zip
  7. Amazing that docker is even capable of affecting the array in this manner. Another beautiful waterfall release 👏
  8. Upgraded from 6.11.X, and got same error as this user when trying to start docker container that binds to port 443 on host: As with OP, I had to change 'HTTPS port' to some random value under Settings/ManagementAccess, although 'Use SSL/TLS' has always been set to No. Is this an intentional change or a regression?
  9. Ha, fair question! Think I was confused about the interaction of webmin and bare bind9 and what the implications are. I just amended the config files manually and all's well. Thanks!
  10. GUI is rather confusing to me. Is it okay to largely copy the config files over from the old instance? There also are multiple db files missing compared to the old version - is this expected? These are files such as db.local, db.127, db.0, db.255 referenced from named.conf.default-zones: // prime the server with knowledge of the root servers zone "." { type hint; file "/etc/bind/db.root"; // !! note this one is equivalent to db.cache in your version! }; // be authoritative for the localhost forward and reverse zones, and for // broadcast zones as per RFC 1912 zone "localhost" { type master; file "/etc/bind/db.local"; }; zone "127.in-addr.arpa" { type master; file "/etc/bind/db.127"; }; zone "0.in-addr.arpa" { type master; file "/etc/bind/db.0"; }; zone "255.in-addr.arpa" { type master; file "/etc/bind/db.255"; }; And last, was it your decision to depart from the old convention of splitting named.conf into separate files as $ cat named.conf include "/etc/bind/named.conf.options"; include "/etc/bind/named.conf.local"; include "/etc/bind/named.conf.default-zones" if so, how come?
  11. I'm running an old bind version from sameersbn/bind image that was last updated 3y ago: BIND 9.16.1-Ubuntu (Stable Release) <id:d497c32> webmin ver: 1.941 Is there a straight-forward enough way to upgrade to your image instead? Note current bind installation configuration/appdata bound to /data in the container looks like: ┌─[server]─[/mnt/user/appdata/bind] └──╼ + tree -L 3 . |-- bind | |-- etc | | |-- bind.keys | | |-- db.0 | | |-- db.127 | | |-- db.255 | | |-- db.empty | | |-- db.local | | |-- db.root | | |-- named.conf | | |-- named.conf.default-zones | | |-- named.conf.local | | |-- named.conf.local~ | | |-- named.conf.options | | |-- rndc.key | | `-- zones.rfc1918 | `-- lib | |-- mydomain.eu.hosts | `-- mydomain2.eu.hosts `-- webmin `-- etc |-- acl |-- adsl-client |-- ajaxterm |-- apache |-- at |-- ...etc Second, 2 years ago (near beginning of this thread) it was stated '- changed network mode to bridge as default' -- now it still defaults back to host network. Does it mean we should be running it in host network again?
  12. Likely just a coincidence, but my unraid box just shut down without my input over night for the first time in 6-7 years. Available logs suggest it happened during time when docker images were being updated (could see Authelia instance restarting after which I got an Authelia configuration log due to updated image). Also seems to be a clean shutdown as there was no parity check upon starting up again. Running v6.11.5
  13. This particular drive has been showing occasional read error for a while now. Now looks like it's also erroring on writes. Time to discard of it? Adding 2 diagnostics - one prior to reboot (~month uptime), one after. srvr-diagnostics-20230114-1709.zip srvr-diagnostics-20230115-1239.zip
  14. Ye not complaining, just taking a note. I'm relatively new user myself, only been with unraid since 2016. The releases used to be rare, same with patching. Now the patches follow minor version releases in rapid succession. Have really vanilla needs though, so haven't been affected.
  15. Is it just me or does it seem like QA is slipping with the 6.11? Last few releases feel like putting out fires.