johntdyer

Also FWIW when I woke up the next morning things seem to have subsided... so the problem seems intermittent and transient in nature ... we'll see how today goes

What does UD mean ?

New diag, also a bunch of new 5xx errors and unresponsive UI tower-diagnostics-20250511-1940.zip replaced cables, and even replaced drives

so still struggling with a ton of issues I can only equate to "locking up" in the UI. Unable to stop and start containers or even get to the docker control panel... Updated diag log... All and all this has been a giant stuggle since I went back to booting of a USB vs running it under proxmox as a VM... tower-diagnostics-20250509-1334.zip

Are these ok ? [Fri May 9 11:39:28 2025] sd 1:0:35:0: Power-on or device reset occurred [Fri May 9 11:39:58 2025] sd 1:0:35:0: Power-on or device reset occurred [Fri May 9 11:40:23 2025] sd 1:0:35:0: Power-on or device reset occurred [Fri May 9 11:40:35 2025] sd 1:0:35:0: [sdd] tag#12 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0 [Fri May 9 11:40:35 2025] sd 1:0:35:0: Power-on or device reset occurred [Fri May 9 11:41:06 2025] sd 1:0:33:0: [sdb] tag#2645 BRCM Debug mfi stat 0x2d, data len requested/completed 0x2000/0x0 [Fri May 9 11:41:06 2025] sd 1:0:33:0: Power-on or device reset occurred [Fri May 9 11:41:23 2025] sd 1:0:35:0: Power-on or device reset occurred [Fri May 9 11:41:53 2025] sd 1:0:33:0: Power-on or device reset occurred [Fri May 9 11:42:23 2025] sd 1:0:35:0: [sdd] tag#60 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0 [Fri May 9 11:42:23 2025] sd 1:0:35:0: Power-on or device reset occurred [Fri May 9 11:42:35 2025] sd 1:0:35:0: [sdd] tag#17 BRCM Debug mfi stat 0x2d, data len requested/completed 0xd6000/0x0 [Fri May 9 11:42:35 2025] sd 1:0:35:0: Power-on or device reset occurred [Fri May 9 11:43:05 2025] sd 1:0:35:0: Power-on or device reset occurred [Fri May 9 11:49:39 2025] sd 1:0:35:0: Power-on or device reset occurred [Fri May 9 11:50:09 2025] sd 1:0:33:0: Power-on or device reset occurred [Fri May 9 11:53:11 2025] sd 1:0:35:0: [sdd] tag#2655 BRCM Debug mfi stat 0x2d, data len requested/completed 0x100000/0x0 [Fri May 9 11:53:11 2025] sd 1:0:35:0: Power-on or device reset occurred [Fri May 9 12:02:55 2025] sd 1:0:35:0: [sdd] tag#51 BRCM Debug mfi stat 0x2d, data len requested/completed 0xc000/0x0 [Fri May 9 12:02:55 2025] sd 1:0:35:0: Power-on or device reset occurred [Fri May 9 12:05:39 2025] sd 1:0:35:0: Power-on or device reset occurred

moved the drives to a new cable, finished `btrfs balance`, upgraded to 7.1.1, restarted and got new diagnostic tower-diagnostics-20250509-1056.zip

gave up and just restored from backup, thanks

I am constantly getting 5xx errors when trying to access the UI. May 9 09:48:15 Tower nginx: 2025/05/09 09:48:15 [error] 408616#408616: *57570 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.100.58, server: , request: "GET /Main HTTP/2.0", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php-fpm.sock", host: "192.168.100.13" May 9 09:48:15 Tower nginx: 2025/05/09 09:48:15 [error] 408616#408616: *57570 auth request unexpected status: 504 while sending to client, client: 192.168.100.58, server: , request: "GET /Main HTTP/2.0", host: "192.168.100.13" I can still access services running in Docker on the server. I am also still able to access shares from other hosts... I have tried restarting nginx but didnt help tower-diagnostics-20250509-0945.zip

Also tried mounting the volume via unassigned devices and got the following error Then in syslog I see the following ``` May 7 15:28:22 Tower unassigned.devices: Mounting partition 'sdb1' at mountpoint '/mnt/disks/QEMU_QEMU_HARDDISK'... May 7 15:28:22 Tower unassigned.devices: Mount cmd: /sbin/mount -t 'btrfs' -o rw,relatime,space_cache=v2,discard '/dev/sdb1' '/mnt/disks/QEMU_QEMU_HARDDISK' May 7 15:28:22 Tower kernel: BTRFS info (device sdd1): first mount of filesystem 04c41cfb-a8db-4caf-9fe5-32087da8fc68 May 7 15:28:22 Tower kernel: BTRFS info (device sdd1): using crc32c (crc32c-generic) checksum algorithm May 7 15:28:22 Tower kernel: BTRFS info (device sdd1): turning on sync discard May 7 15:28:22 Tower kernel: BTRFS info (device sdd1): using free space tree May 7 15:28:22 Tower kernel: BTRFS error (device sdd1): devid 2 uuid c6645f6d-39cf-4efc-94fe-2f730c9023d6 is missing May 7 15:28:22 Tower kernel: BTRFS error (device sdd1): failed to read the system array: -2 May 7 15:28:22 Tower kernel: BTRFS error (device sdd1): open_ctree failed May 7 15:28:23 Tower unassigned.devices: Mount of 'sdb1' failed: 'mount: /mnt/disks/QEMU_QEMU_HARDDISK: mount system call failed: No such file or directory. dmesg(1) may have more information after failed mount system call.' May 7 15:28:23 Tower unassigned.devices: Partition 'QEMU QEMU_HARDDISK' cannot be mounted. there is nothing in dmesg

tower-diagnostics-20250507-1623.zip Diagnostics file

argh, tried creating a new temp cache pool and moving the odler 256gb drive into it, shows as unmountable

hey folks, so am trying to upgrade my cache pool from two 256gb SSD's to 2 1TB SSDs.... Suggestions I found online was to stop the array, remove a drive, add the new larger drive and let it buil;d... Well I did this and now its unmountable fs.... I still have the second 256gb SSD unassigned but not sure how to proceed here

Care to share that container ?

/mnt/user/appdata/Unraid-API/servers.json ``` { "https://unraid.xxxxx.xxxxx": { "serverDetails": { "arrayStatus": "Started", "moverRunning": true, "parityCheckRunning": true, "title": "vault", "cpu": "Common KVM @ 2000 MHz", "memory": "32 GiB RAM Multi-bit ECC ", "motherboard": " ", "diskSpace": "24.1 TB used of 58 TB (41.5 %)", "cacheSpace": "26.6 GB used of 265 GB (10.0 %)", "version": "6.12.3", "arrayUsedSpace": "24.1 TB", "arrayTotalSpace": "58 TB", "arrayFreeSpace": "33.9 TB", "cacheUsedSpace": "26.6 GB", "cacheTotalSpace": "265 GB", "cacheFreeSpace": "238.4 GB", "on": true }, "docker": { "details": { "images": { "245078241b19": { "imageUrl": "/webGui/images/disk.png", "imageId": "245078241b19", "created": "Created 2 days ago" }, "2ddd2e111d89": { "imageUrl": "/webGui/images/disk.png", "imageId": "2ddd2e111d89", "created": "Created 2 days ago" }, "df91f6deadde": { "imageUrl": "/webGui/images/disk.png", "imageId": "df91f6deadde", "created": "Created 1 year ago" }, "2154b5734a30": { "imageUrl": "/webGui/images/disk.png", "imageId": "2154b5734a30", "created": "Created 1 year ago" } }, "containers": { "f2cbb7d93588": { "imageUrl": "/state/plugins/dynamix.docker.manager/images/proxmox-backup-server-icon.png", "name": "proxmox-backup-server", "status": "stopped", "containerId": "f2cbb7d93588", "tag": "v2.3.2", "uptoDate": "up-to-date" }, "ac662b94a351": { "imageUrl": "/state/plugins/dynamix.docker.manager/images/Unraid-API-RE-icon.png", "name": "Unraid-API-RE", "status": "started", "containerId": "ac662b94a351", "tag": "6.12-no-vm", "uptoDate": "up-to-date" } } } }, "vm": { "details": {} }, "pciDetails": [], "status": "offline", "usbDetails": [] } } ```

hrm, where do I find this file ?