Jaybau

Okay...I might have to do that. I have a few custom dockers that I created via Portainer that don't make it quick/easy. I may need to learn how to create custom containers the Unraid way. Thank you.

I ran a BTRFS scrub on the docker image/volume/file docker.img. I received checksum errors, and the log provided the offending file path, presumably within the docker.img file. How do I know which container has the problem, so I can connect to the container to fix the file? Or where is this file with the error? Bonus question: Are there instructions for creating a BTRFS snapshot of the docker.img volume so I can have BTRFS self-correct the errors in the future? UUID: f5d16644-b1de-4be0-be96-754d644a9601 Scrub started: Wed Dec 20 14:35:19 2023 Status: finished Duration: 0:04:57 Total to scrub: 39.49GiB Rate: 136.17MiB/s Error summary: csum=2 Corrected: 0 Uncorrectable: 0 Unverified: 0 Dec 20 14:36:35 Tower kernel: BTRFS warning (device loop2): checksum error at logical 9904988160 on dev /dev/loop2, physical 10450247680, root 3978, inode 10459, offset 8192, length 4096, links 1 (path: usr/lib/python3.11/unittest/result.py) Dec 20 14:36:35 Tower kernel: BTRFS warning (device loop2): checksum error at logical 9904988160 on dev /dev/loop2, physical 10450247680, root 3977, inode 10459, offset 8192, length 4096, links 1 (path: usr/lib/python3.11/unittest/result.py) Dec 20 14:36:35 Tower kernel: BTRFS warning (device loop2): checksum error at logical 9904988160 on dev /dev/loop2, physical 10450247680, root 3976, inode 10459, offset 8192, length 4096, links 1 (path: usr/lib/python3.11/unittest/result.py) Dec 20 14:36:35 Tower kernel: BTRFS warning (device loop2): checksum error at logical 9904988160 on dev /dev/loop2, physical 10450247680, root 3975, inode 10459, offset 8192, length 4096, links 1 (path: usr/lib/python3.11/unittest/result.py) Dec 20 14:36:35 Tower kernel: BTRFS warning (device loop2): checksum error at logical 9904988160 on dev /dev/loop2, physical 10450247680, root 3974, inode 10459, offset 8192, length 4096, links 1 (path: usr/lib/python3.11/unittest/result.py) Dec 20 14:36:35 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 7, gen 0 Dec 20 14:36:43 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 8, gen 0 Thank you. tower-diagnostics-20231220-1444.zip

Thanks. I updated the Network Settings below:

I was hoping the macvlan issue was fixed: https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces The reason why I am using macvlan is so my router can assign IP addresses based on MAC address and use DHCP. Otherwise if I use ipvlan, I have to hardcode the IP addresses, and make sure I don't assign an already used IP. But if macvlan is truly still unstable, I can manage ipvlan. Thank you.

Every few days Unraid is hard crashing and locks-up requiring a hard reset. Display monitor is dead (can't see dumps), keyboard is dead, machine is totally unresponsive. It looks to me something happened between 12/16/2023 7:58 AM thru 8:30 AM in the log. I wasn't paying 100% attention when this was happening, but here are some suspicions: Docker containers causing instability to the host. I'm very suspicious a docker container (or something related) can take down a host. VNC'd into a docker container. Docker container network traffic (I run a lot of network traffic through multiple containers). Docker container + network traffic + macvlan = crashing host? Dec 16 08:30:39 Tower kernel: Call Trace: Dec 16 08:30:39 Tower kernel: <IRQ> Dec 16 08:30:39 Tower kernel: ? __warn+0xab/0x122 Dec 16 08:30:39 Tower kernel: ? report_bug+0x109/0x17e Dec 16 08:30:39 Tower kernel: ? nf_nat_setup_info+0x8c/0x7d1 [nf_nat] Dec 16 08:30:39 Tower kernel: ? handle_bug+0x41/0x6f Dec 16 08:30:39 Tower kernel: ? exc_invalid_op+0x13/0x60 Dec 16 08:30:39 Tower kernel: ? asm_exc_invalid_op+0x16/0x20 Dec 16 08:30:39 Tower kernel: ? nf_nat_setup_info+0x8c/0x7d1 [nf_nat] Dec 16 08:30:39 Tower kernel: ? nf_nat_setup_info+0x44/0x7d1 [nf_nat] Dec 16 08:30:39 Tower kernel: ? xt_write_recseq_end+0xf/0x1c [ip_tables] Dec 16 08:30:39 Tower kernel: ? __local_bh_enable_ip+0x56/0x6b Dec 16 08:30:39 Tower kernel: ? ipt_do_table+0x575/0x5ba [ip_tables] Dec 16 08:30:39 Tower kernel: ? xt_write_recseq_end+0xf/0x1c [ip_tables] Dec 16 08:30:39 Tower kernel: __nf_nat_alloc_null_binding+0x66/0x81 [nf_nat] Dec 16 08:30:39 Tower kernel: nf_nat_inet_fn+0xc0/0x1a8 [nf_nat] Dec 16 08:30:39 Tower kernel: nf_nat_ipv4_local_in+0x2a/0xaa [nf_nat] Dec 16 08:30:39 Tower kernel: nf_hook_slow+0x3d/0x96 Dec 16 08:30:39 Tower kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Dec 16 08:30:39 Tower kernel: NF_HOOK.constprop.0+0x79/0xd9 Dec 16 08:30:39 Tower kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Dec 16 08:30:39 Tower kernel: ip_sabotage_in+0x52/0x60 [br_netfilter] Dec 16 08:30:39 Tower kernel: nf_hook_slow+0x3d/0x96 Dec 16 08:30:39 Tower kernel: ? ip_rcv_finish_core.constprop.0+0x3e8/0x3e8 Dec 16 08:30:39 Tower kernel: NF_HOOK.constprop.0+0x79/0xd9 Dec 16 08:30:39 Tower kernel: ? ip_rcv_finish_core.constprop.0+0x3e8/0x3e8 Dec 16 08:30:39 Tower kernel: __netif_receive_skb_one_core+0x77/0x9c Dec 16 08:30:39 Tower kernel: process_backlog+0x8c/0x116 Dec 16 08:30:39 Tower kernel: __napi_poll.constprop.0+0x2b/0x124 Dec 16 08:30:39 Tower kernel: net_rx_action+0x159/0x24f Dec 16 08:30:39 Tower kernel: __do_softirq+0x129/0x288 Dec 16 08:30:39 Tower kernel: do_softirq+0x7f/0xab Dec 16 08:30:39 Tower kernel: </IRQ> Dec 16 08:30:39 Tower kernel: <TASK> Dec 16 08:30:39 Tower kernel: __local_bh_enable_ip+0x4c/0x6b Dec 16 08:30:39 Tower kernel: netif_rx+0x52/0x5a Dec 16 08:30:39 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Dec 16 08:30:39 Tower kernel: ? _raw_spin_unlock+0x14/0x29 Dec 16 08:30:39 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Dec 16 08:30:39 Tower kernel: process_one_work+0x1ab/0x295 Dec 16 08:30:39 Tower kernel: worker_thread+0x18b/0x244 Dec 16 08:30:39 Tower kernel: ? rescuer_thread+0x281/0x281 Dec 16 08:30:39 Tower kernel: kthread+0xe7/0xef Dec 16 08:30:39 Tower kernel: ? kthread_complete_and_exit+0x1b/0x1b Dec 16 08:30:39 Tower kernel: ret_from_fork+0x22/0x30 Dec 16 08:30:39 Tower kernel: </TASK> Dec 16 08:30:39 Tower kernel: ---[ end trace 0000000000000000 ]--- Thank you tower-diagnostics-20231216-0859.zip

I just installed the docker container and got an error. Any ideas to try? [2023-11-07 06:08:02 +0000] [15] [INFO] Booting worker with pid: 15 [2023-11-07 06:08:05 +0000] [15] [ERROR] Exception in worker process Traceback (most recent call last): File "/usr/local/lib/python2.7/site-packages/gunicorn/arbiter.py", line 586, in spawn_worker worker.init_process() File "/usr/local/lib/python2.7/site-packages/gunicorn/workers/base.py", line 135, in init_process self.load_wsgi() File "/usr/local/lib/python2.7/site-packages/gunicorn/workers/base.py", line 144, in load_wsgi self.wsgi = self.app.wsgi() File "/usr/local/lib/python2.7/site-packages/gunicorn/app/base.py", line 67, in wsgi self.callable = self.load() File "/usr/local/lib/python2.7/site-packages/gunicorn/app/wsgiapp.py", line 52, in load return self.load_wsgiapp() File "/usr/local/lib/python2.7/site-packages/gunicorn/app/wsgiapp.py", line 41, in load_wsgiapp return util.import_app(self.app_uri) File "/usr/local/lib/python2.7/site-packages/gunicorn/util.py", line 350, in import_app __import__(module) File "/app/syncserver/wsgi_app.py", line 2, in <module> application = syncserver.main() File "/app/syncserver/__init__.py", line 281, in main config = get_configurator(global_config, **settings) File "/app/syncserver/__init__.py", line 273, in get_configurator config.include(includeme) File "/usr/local/lib/python2.7/site-packages/pyramid/config/__init__.py", line 676, in include c(configurator) File "/app/syncserver/__init__.py", line 158, in includeme config.include("syncstorage", route_prefix="/storage") File "/usr/local/lib/python2.7/site-packages/pyramid/config/__init__.py", line 676, in include c(configurator) File "/usr/local/lib/python2.7/site-packages/syncstorage/__init__.py", line 18, in includeme config.include("syncstorage.storage") File "/usr/local/lib/python2.7/site-packages/pyramid/config/__init__.py", line 676, in include c(configurator) File "/usr/local/lib/python2.7/site-packages/syncstorage/storage/__init__.py", line 576, in includeme storage = load_storage_from_settings("storage", settings) File "/usr/local/lib/python2.7/site-packages/syncstorage/storage/__init__.py", line 600, in load_storage_from_settings return klass(**section_settings) File "/usr/local/lib/python2.7/site-packages/syncstorage/storage/sql/__init__.py", line 137, in __init__ self.dbconnector = DBConnector(sqluri, **dbkwds) File "/usr/local/lib/python2.7/site-packages/syncstorage/storage/sql/dbconnect.py", line 385, in __init__ collections.create(self.engine, checkfirst=True) File "/usr/local/lib/python2.7/site-packages/sqlalchemy/sql/schema.py", line 860, in create bind._run_visitor(ddl.SchemaGenerator, self, checkfirst=checkfirst) File "/usr/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 2032, in _run_visitor with self._optional_conn_ctx_manager(connection) as conn: File "/usr/local/lib/python2.7/contextlib.py", line 17, in __enter__ return self.gen.next() File "/usr/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 2024, in _optional_conn_ctx_manager with self._contextual_connect() as conn: File "/usr/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 2226, in _contextual_connect self._wrap_pool_connect(self.pool.connect, None), File "/usr/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 2266, in _wrap_pool_connect e, dialect, self File "/usr/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1536, in _handle_dbapi_exception_noconnection util.raise_from_cause(sqlalchemy_exception, exc_info) File "/usr/local/lib/python2.7/site-packages/sqlalchemy/util/compat.py", line 383, in raise_from_cause reraise(type(exception), exception, tb=exc_tb, cause=cause) File "/usr/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 2262, in _wrap_pool_connect return fn() File "/usr/local/lib/python2.7/site-packages/sqlalchemy/pool/base.py", line 363, in connect return _ConnectionFairy._checkout(self) File "/usr/local/lib/python2.7/site-packages/sqlalchemy/pool/base.py", line 760, in _checkout fairy = _ConnectionRecord.checkout(pool) File "/usr/local/lib/python2.7/site-packages/sqlalchemy/pool/base.py", line 492, in checkout rec = pool._do_get() File "/usr/local/lib/python2.7/site-packages/mozsvc/metrics.py", line 183, in timed_func return func(*args, **kwds) File "/usr/local/lib/python2.7/site-packages/syncstorage/storage/sql/dbconnect.py", line 305, in _do_get return QueuePool._do_get(self) File "/usr/local/lib/python2.7/site-packages/sqlalchemy/pool/impl.py", line 139, in _do_get self._dec_overflow() File "/usr/local/lib/python2.7/site-packages/sqlalchemy/util/langhelpers.py", line 68, in __exit__ compat.reraise(exc_type, exc_value, exc_tb) File "/usr/local/lib/python2.7/site-packages/sqlalchemy/pool/impl.py", line 136, in _do_get return self._create_connection() File "/usr/local/lib/python2.7/site-packages/sqlalchemy/pool/base.py", line 308, in _create_connection return _ConnectionRecord(self) File "/usr/local/lib/python2.7/site-packages/sqlalchemy/pool/base.py", line 437, in __init__ self.__connect(first_connect_check=True) File "/usr/local/lib/python2.7/site-packages/sqlalchemy/pool/base.py", line 639, in __connect connection = pool._invoke_creator(self) File "/usr/local/lib/python2.7/site-packages/sqlalchemy/engine/strategies.py", line 114, in connect return dialect.connect(*cargs, **cparams) File "/usr/local/lib/python2.7/site-packages/sqlalchemy/engine/default.py", line 453, in connect return self.dbapi.connect(*cargs, **cparams) OperationalError: (sqlite3.OperationalError) unable to open database file (Background on this error at: http://sqlalche.me/e/e3q8) [2023-11-07 06:08:05 +0000] [15] [INFO] Worker exiting (pid: 15) [2023-11-07 06:08:05 +0000] [7] [INFO] Shutting down: Master [2023-11-07 06:08:05 +0000] [7] [INFO] Reason: Worker failed to boot.

Might someone have made a flash drive swap script? I read through this document, and thought it would have been nice if there was a script to do the steps with both the current and the news USB drive plugging in. https://docs.unraid.net/unraid-os/getting-started/manual-install-method/ I figure it would have been simple because I could have both the old and the new USB flash drive plugged in, and the script would do the swap automatically. At the moment I'm trying to figure out the steps using Linux (unraid), without messing something up.

I received this error when trying to create a hard link: ln: failed to create hard link '[target]' => '[source]': Operation not permitted I believe this error is caused by the file being immutable. This is unfortunate because I wanted to: 1) Keep my media collection safer (mainly prevent accidental changes/deletions). 2) Use Sonarr/Radarr to organize my media library via hard links. So it looks like I'll need to make the files immutable after I import into Sonarr/Radarr.

Is there functionality to manually force a move of a folder/files? I have the mover configured to ignore/exclude and wait X days until a file is moved. But sometimes I want to manually force/push a file/folder to the array.

I cannot access the Unraid Docker webGUI http://tower/Docker. Web page error message: Docker Service failed to start. No Docker containers installed. Syslog: Oct 1 10:07:49 Tower unraid-api[24376]: ✔️ UNRAID API started successfully! Oct 1 10:07:50 Tower unraid-api[24376]: ⚠️ Caught exception: connect ECONNREFUSED /var/run/docker.sock Oct 1 10:07:50 Tower unraid-api[24376]: ⚠️ UNRAID API crashed with exit code 1 However, all my docker containers appear to be working fine, and I can access the docker containers. Since this happened around the 1st of the month, I assume this might have something to do with some scheduled tasks (i.e. backing up appdata). I was able to workaround and resolve the issue by running the command: /etc/rc.d/rc.docker start But, I would like to try and prevent this from happening in the future or to someone else. tower-diagnostics-20231001-1049.zip

Is there a way to tune the "mover" to: Do not move recently modified files. Only move if file hasn't been modified/created after X days/time. Exclude file extensions / folders. Only move file extension (or file, or folder) when mover is run from command line. Thank you.

I've been experiencing strange boot errors from a USB device, and can't get the error message because the boot screen scrolls off the screen too quickly. Are the boot messages logged somewhere? Is there a way to test my Unraid USB boot drive? I tried dosfsck and noticed some strange messages: # dosfsck -av /dev/sdb1 fsck.fat 4.2 (2021-01-31) Checking we can access the last sector of the filesystem There are differences between boot sector and its backup. This is mostly harmless. Differences: (offset:original/backup) 65:01/00 Not automatically fixing this. Boot sector contents: System ID "SYSLINUX" Media byte 0xf8 (hard disk) 512 bytes per logical sector 16384 bytes per cluster 32 reserved sectors First FAT starts at byte 16384 (sector 32) 2 FATs, 32 bit entries 7830016 bytes per FAT (= 15293 sectors) Root directory start at cluster 2 (arbitrary size) Data area starts at byte 15676416 (sector 30618) 1956999 data clusters (32063471616 bytes) 63 sectors/track, 255 heads 0 hidden sectors 62654593 sectors total Reclaiming unconnected clusters. Dirty bit is set. Fs was not properly unmounted and some data may be corrupt. Automatically removing dirty bit. Checking free cluster summary. *** Filesystem was changed *** Writing changes. /dev/sdb1: 4618 files, 67350/1956999 clusters # dosfsck -av /dev/sdb1 fsck.fat 4.2 (2021-01-31) Checking we can access the last sector of the filesystem Boot sector contents: System ID "SYSLINUX" Media byte 0xf8 (hard disk) 512 bytes per logical sector 16384 bytes per cluster 32 reserved sectors First FAT starts at byte 16384 (sector 32) 2 FATs, 32 bit entries 7830016 bytes per FAT (= 15293 sectors) Root directory start at cluster 2 (arbitrary size) Data area starts at byte 15676416 (sector 30618) 1956999 data clusters (32063471616 bytes) 63 sectors/track, 255 heads 0 hidden sectors 62654593 sectors total Reclaiming unconnected clusters. Checking free cluster summary. /dev/sdb1: 4618 files, 67350/1956999 clusters Thank you. tower-diagnostics-20230920-2304.zip

When trying to install the docker app "LibrePhotos", the install is stuck on "Extracting" (for hours). Perhaps something to do with the 3GB layer size. Filesystem Size Used Avail Use% Mounted on /dev/loop2 42G 28G 15G 66% /var/lib/docker Maybe the problem is: upstream timed out (110: Connection timed out) while reading upstream I don't know if I have a successful install. tower-diagnostics-20230919-1419.zip

Symptoms: Docker containers stop working. Cannot stop docker, the docker.img file in use. I noticed BTRFS errors in the log. BTRFS scrubs do not detect errors. Tried restarting docker, but couldn't umount the docker.img file. Forced the umount: umount /dev/loop2 This is happening weekly. Sometimes the docker.img file is corrupted according to BTRFS scrub. Not all configuration settings are restored when recreating the file (custom networks, delay start). I've done 5 memory test passes. I've done the extended tests on all my hard drives, several times. No hardware issues detected, except for one pool with a bunch of junk drives that have a SMART error. I don't care about these drives or the data. I also am doing a lot of I/O on my unassigned drives and the junk pool (old external USB drives), that I use for temporary torrents. Another symptom showed up where Unraid froze, keyboard unresponsive, requiring a forced/unclean reboot. Sep 13 12:35:13 Tower emhttpd: spinning down /dev/sdm Sep 13 12:41:06 Tower kernel: BTRFS critical (device loop2): corrupt node: root=7 block=13634125824 slot=47, bad key order, current (18446744073709551606 128 7868407808) next (9300072153669959670 136 7885029375) Sep 13 12:41:06 Tower kernel: BTRFS info (device loop2): node 13634125824 level 1 gen 4979 total ptrs 336 free spc 157 owner 7 Sep 13 12:41:06 Tower kernel: #011key 0 (18446744073709551606 128 7183642624) block 13587808256 gen 4942 Sep 13 12:41:06 Tower kernel: #011key 1 (18446744073709551606 128 7193964544) block 13587857408 gen 4942 ... ... Sep 13 15:00:49 Tower emhttpd: shcmd (535023): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 42 Sep 13 15:00:49 Tower avahi-daemon[20138]: Server startup complete. Host name is Tower.local. Local service cookie is 1906093824. Sep 13 15:00:49 Tower root: '/mnt/user/system/docker/docker.img' is in-use, cannot mount Sep 13 15:00:49 Tower emhttpd: shcmd (535023): exit status: 1 Attaching my logs. I'm using the syslog server, but still looks like the log isn't saved. I've attached a log before the reboot, and the one after. Logs are not private/anonymous. The log will capture files from my BTRFS subvolume/snaprshots. If files/photos have lables, they are identifiable PII information. In my logs I've seen appdata backups, drive spindowns, one of the pools has a SMART error, and BiglyBT (not a docker container) is doing a lot of I/O on the non-array pool over the network (from another machine). Maybe I'm just stressing my machine out too much, and it can't handle it. Or my machine is too old. But it seems to happen when BiglyBT is pushing a lot of I/O. And none of that should be related to docker containers or non-array pools. tower-diagnostics-20230913-1858.zip tower-diagnostics-20230913-1711.zip

Same problem. Version: 6.12.4 This problem has been happening frequently and recently for me. Docker works for a while, and then something crashes all my conatainers. Then the cannot start Docker service because the mount is busy. Try: umount /dev/loop2

Problem: Recreating the docker.img does not recreate my customer docker networks. Situation: After deleting and having Unraid recreate the docker.img file, custom docker networks are lost. When reinstalling apps/dockers from CA Previous Apps, the docker containers that used a custom docker network are reset to "none". I have to re-create the docker custom network, and then assign the custom network to the containers. Request: Is there a way to have Unraid and/or CA Previous app configuration/template recreate my custom networks?

memtest = 1 pass, 0 errors.

I have been getting frequent occurrences of my docker.img file becoming corrupt. No other drive or filesystem errors. SMART tests do not report error. I don't know if the constant problem is my cache drive, docker, Unraid, or ZFS. My guess: My cache drive is ZFS. The docker file is BTRFS vDisk. Maybe there's a conflict? # zpool status -xv pool: cache state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A scan: scrub repaired 0B in 00:15:38 with 3 errors on Sun Aug 27 12:39:33 2023 config: NAME STATE READ WRITE CKSUM cache ONLINE 0 0 0 sdi1 ONLINE 0 0 128 errors: Permanent errors have been detected in the following files: /mnt/cache/system/docker/docker.img tower-diagnostics-20230827-1425.zip

Is there a way to preserve the syslog between reboots/restarts? Also, is there a setting to rotate the log (daily, every N day, weekly, etc)? My system has recently become unstable and becomes unresponsive, so I cannot generate diagnostics or view the last syslog entries. I had to do a hard restart/reboot. Thank you.

Might need to delete the appdata folders. Might need to "update stack" for the changes.

I received this unRAID error notification: unRAID file corruption: 30-07-2023 04:50 Notice [TOWER] - bunker verify command Found 1 file with BLAKE3 hash key corruption No other information was provided. No information of which file or which drive. No information on what to do next. I now have to do my own research into what's going on, at a stressful time of presumed data corruption. The Main tab doesn't show any errors: Fortunately I was using btrfs, so I can do a scrub to look for corruption. But I have no idea what "csum=2" means. # btrfs dev stats /mnt/disk1 [/dev/md1p1].write_io_errs 0 [/dev/md1p1].read_io_errs 0 [/dev/md1p1].flush_io_errs 0 [/dev/md1p1].corruption_errs 11 [/dev/md1p1].generation_errs 0 I did another btrfs scrub, and now there's no errors: # btrfs scrub start -B /mnt/disk1 scrub done for 28221102-46bb-4fa0-8602-e436c1cab5f6 Scrub started: Sun Jul 30 16:01:10 2023 Status: finished Duration: 3:26:52 Total to scrub: 920.57GiB Rate: 64.84MiB/s Error summary: no errors found I also looked into my log. It doesn't tell me what that "1 corruption" is. I don't know if the entire drive's data is rubbish. I don't know if the drive needs to be replaced. Jul 30 04:50:39 Tower bunker: verified 10677 files from /mnt/disk1. Found: 0 mismatches, 1 corruption. Duration: 04:50:38. Average speed: 47.1 MB/s Jul 30 10:30:52 Tower kernel: BTRFS warning (device md1p1): checksum verify failed on logical 1053360128 mirror 1 wanted 0x8cb7f8d8 found 0x9c0da989 level 0 Jul 30 10:30:53 Tower emhttpd: read SMART /dev/sdh Jul 30 10:31:04 Tower kernel: BTRFS info (device md1p1): read error corrected: ino 0 off 1053360128 (dev /dev/md1p1 sector 2073728) Jul 30 10:31:04 Tower kernel: BTRFS info (device md1p1): read error corrected: ino 0 off 1053364224 (dev /dev/md1p1 sector 2073736) Jul 30 10:31:04 Tower kernel: BTRFS info (device md1p1): read error corrected: ino 0 off 1053368320 (dev /dev/md1p1 sector 2073744) Jul 30 10:31:04 Tower kernel: BTRFS info (device md1p1): read error corrected: ino 0 off 1053372416 (dev /dev/md1p1 sector 2073752) bunker -v -b3 "/mnt/user/media/Movies/[movie_name]"/ Finished - verified 1 file, skipped 0 files. Found: 0 mismatches, 0 corruptions. Duration: 00:04:56. Average speed: 18.0 MB/s I haven't done anything else, but appears the error disappeared, and I don't have specific information on a file that is corrupt to initiate a restore from backup. However, my data quality confidence is low, and may be considering a complete move to a technology that has integrated data integrity; most likely ZFS.

When I tried creating unraid non-array pools (with different drive sizes), unraid would remove my existing partition. So I then assume pools have to be zfs or btrfs. It is confusing me because unraid has something called pools (non-array), but perhaps unraid is just managing a zfs/btrfs pools, not creating it's own.

I ran into the problem with v6.12.3. Ran into the problem yesterday, and I forced the shutdown, which I believe caused me a parity sync error (which I have not fixed yet). Problem has returned today. The symptoms first start with not being able to check updates for Docker or Plugins. This pointed me to another problem with DNS problems (e.g. I couldn't ping google.com from terminal). I also run docker containers pretty heavility and wonder if that contributed to some of the problem. The instructions above resolved the array shutdown issue, but the root cause for me needing to restart Docker remains a mystery: root@Tower:~# losetup NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO LOG-SEC /dev/loop1 0 0 1 1 /boot/bzfirmware 0 512 /dev/loop2 0 0 1 0 /mnt/cache/system/docker/docker.img 0 512 /dev/loop0 0 0 1 1 /boot/bzmodules 0 512 root@Tower:~# /etc/rc.d/rc.docker status status of dockerd: stopped root@Tower:~# umount /dev/loop2 tower-diagnostics-20230727-1517.zip

I think I finally figured it out...you need to use either btrfs or zfs for the actual filesystem pooling. I added an Unraid Pool. I used btrfs as the filesystem, as "single" (because I have drives of different size). This will combine the storage of muliple drives into a single disk/pool. zfs didn't have the option "single", for different drive sizes. This was not without quirks... I needed to format the drives (I had to move the data off the drives I was formatting because I was using xfs). When I started the Array, the filesystem wasn't recognized, and needed to reformat (but I "erased" in the prior step where I was doing the configuration). Need to make sure you get the expected pool size. I didn't the first time, so needed to redo something. I think this had to do with something Unraid setting the filesystem to auto, even after erasing. So double check.

I wanted to create a new Unraid pool under the "Pool Devices" (not part of the array). I have a bunch of disks with mixed filesystems. Pool JBOD, with different filesystems, and the pool/share would look like one big drive. EDIT: I just read this: