Opawesome

Hi, Since I upgraded from UNRAID 6.10.X et 6.11.X, I cannot edit anymore shares with a 'dot' in their name. When I hit "apply", a popup appears in the GUI saying that "hidden shares are not allowed". I emphasise that the name of the share is "domains.appdata", and does not begin with a 'dot'. Is that intended behaviour ? Why would a dot in the middle of the name of a share make it a "hidden share" ? Many thanks,

UPDATE: After starting the array in normal mode, the following log entries seem to indicate which disk is device "DM-12". Mar 9 10:02:32 MOZART emhttpd: shcmd (15306197): mkdir -p /mnt/nvme Mar 9 10:02:32 MOZART emhttpd: shcmd (15306198): mount -t xfs -o noatime,nouuid /dev/mapper/nvme0n1p1 /mnt/nvme Mar 9 10:02:32 MOZART kernel: XFS (dm-12): Mounting V5 Filesystem Mar 9 10:02:32 MOZART kernel: XFS (dm-12): Ending clean mount Mar 9 10:02:32 MOZART kernel: xfs filesystem being mounted at /mnt/nvme supports timestamps until 2038 (0x7fffffff) But is there an easier way to check for that info ?

Hi all, Sorry for the dumb question but, how can I identify which disk the error below is coming from ? Many thanks, OP Feb 28 05:02:23 MOZART CA Backup/Restore: Using command: cd '/mnt/user/appdata/' && /usr/bin/tar -cvaf '/mnt/user/backups/MOZART/appdata/[email protected]/CA_backup.tar.gz' --exclude ".Recycle.Bin" --exclude "plex/Library/Application Support/Plex Media Server/Cache" --exclude "plex/Library/Application Support/Plex Media Server/Media" --exclude "plex/Library/Application Support/Plex Media Server/Metadata" * >> /var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log 2>&1 & echo $! > /tmp/ca.backup2/tempFiles/backupInProgress Feb 28 05:02:28 MOZART kernel: XFS (dm-12): Metadata corruption detected at xfs_buf_ioend+0xa9/0x386 [xfs], xfs_inode block 0x5a00e810 xfs_inode_buf_verify Feb 28 05:02:28 MOZART kernel: XFS (dm-12): Unmount and run xfs_repair Feb 28 05:02:28 MOZART kernel: XFS (dm-12): First 128 bytes of corrupted metadata buffer: Feb 28 05:02:28 MOZART kernel: 00000000: f9 8a ef 69 56 bd 88 0d d0 0f 0d e5 99 69 8e 43 ...iV........i.C Feb 28 05:02:28 MOZART kernel: 00000010: 99 d0 50 ad 03 4c 0d 6a 4b a0 d8 25 36 f6 fc 98 ..P..L.jK..%6... Feb 28 05:02:28 MOZART kernel: 00000020: f1 d8 9f ae ef 2e 6b bf 7b ab 83 4b 35 fc 59 aa ......k.{..K5.Y. Feb 28 05:02:28 MOZART kernel: 00000030: 02 9d 0b 2f 3f da 12 bc 3c 0f 1a 0f 67 52 48 6f .../?...<...gRHo Feb 28 05:02:28 MOZART kernel: 00000040: 88 2e 79 53 06 c2 ac 5e 18 4e 17 a8 55 e5 e4 9f ..yS...^.N..U... Feb 28 05:02:28 MOZART kernel: 00000050: 7c ab 27 bd 27 bf 02 78 ca 9e e1 e6 1d 61 6b ef |.'.'..x.....ak. Feb 28 05:02:28 MOZART kernel: 00000060: 2c 96 e2 1c 0b 65 8b d6 82 39 6d 50 e5 b1 93 76 ,....e...9mP...v Feb 28 05:02:28 MOZART kernel: 00000070: a7 2e 8e bb 92 31 e5 82 8b 34 0f 21 79 14 d3 cf .....1...4.!y... Feb 28 05:02:28 MOZART kernel: XFS (dm-12): metadata I/O error in "xfs_imap_to_bp+0x50/0x70 [xfs]" at daddr 0x5a00e810 len 32 error 117 Feb 28 05:12:24 MOZART CA Backup/Restore: Backup Complete Feb 28 05:12:24 MOZART CA Backup/Restore: Verifying backup Feb 28 05:12:24 MOZART CA Backup/Restore: Using command: cd '/mnt/user/appdata/' && /usr/bin/tar --diff -C '/mnt/user/appdata/' -af '/mnt/user/backups/MOZART/appdata/[email protected]/CA_backup.tar.gz' > /var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log & echo $! > /tmp/ca.backup2/tempFiles/verifyInProgress Feb 28 05:14:58 MOZART webGUI: Successful login user root from 192.168.92.185

Using the "-I" parameter (insert) instead of the "-A" parameter (append) in the iptables rule did not change anything. iptables -t nat -I POSTROUTING -s 172.16.92.32/28 -o br0 -j MASQUERADE nor did changing "-o br0" to "-o tun0".

Bellow are the Unraid system's IP tables: iptables -t nat -L POSTROUTING -n -v --line-numbers Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes) num pkts bytes target prot opt in out source destination 1 0 0 MASQUERADE all -- * !docker0 172.17.0.0/16 0.0.0.0/0 2 40005 4759K LIBVIRT_PRT all -- * * 0.0.0.0/0 0.0.0.0/0 3 0 0 MASQUERADE all -- * !br-cbbb49f832df 172.18.92.0/28 0.0.0.0/0 4 0 0 MASQUERADE all -- * !br-3bd25e3311ca 172.18.78.128/25 0.0.0.0/0 5 0 0 MASQUERADE all -- * !br-5a02f5b4da16 172.18.1.0/28 0.0.0.0/0 6 0 0 MASQUERADE all -- * !br-3dddbe93782f 172.18.92.128/25 0.0.0.0/0 7 0 0 MASQUERADE all -- * !br-290de52ddc5f 172.18.21.0/28 0.0.0.0/0 8 0 0 MASQUERADE all -- * !br-186a42eed74c 172.18.1.128/25 0.0.0.0/0 9 0 0 MASQUERADE all -- * !br-b706fef8052b 172.18.92.64/26 0.0.0.0/0 10 0 0 MASQUERADE all -- * !br-8e76e168fd6b 172.18.21.128/25 0.0.0.0/0 11 0 0 MASQUERADE all -- * !br-8a6ec4e64534 172.18.78.0/28 0.0.0.0/0 12 0 0 MASQUERADE all -- * br0 172.16.92.32/28 0.0.0.0/0 and ip route: ip -4 route ls default via 192.168.92.1 dev shim-br0 default via 192.168.92.1 dev br0 proto dhcp src 192.168.92.100 metric 1 172.16.92.32/28 dev tun0 proto kernel scope link src 172.16.92.33 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.1.0/28 dev br-5a02f5b4da16 proto kernel scope link src 172.18.1.1 linkdown 172.18.1.128/25 dev br-186a42eed74c proto kernel scope link src 172.18.1.129 linkdown 172.18.21.0/28 dev br-290de52ddc5f proto kernel scope link src 172.18.21.1 linkdown 172.18.21.128/25 dev br-8e76e168fd6b proto kernel scope link src 172.18.21.129 linkdown 172.18.78.0/28 dev br-8a6ec4e64534 proto kernel scope link src 172.18.78.1 linkdown 172.18.78.128/25 dev br-3bd25e3311ca proto kernel scope link src 172.18.78.129 linkdown 172.18.92.0/28 dev br-cbbb49f832df proto kernel scope link src 172.18.92.1 linkdown 172.18.92.64/26 dev br-b706fef8052b proto kernel scope link src 172.18.92.65 linkdown 172.18.92.128/25 dev br-3dddbe93782f proto kernel scope link src 172.18.92.129 linkdown 192.168.1.0/24 via 172.18.1.2 dev br-5a02f5b4da16 linkdown 192.168.92.0/25 dev shim-br0 scope link 192.168.92.0/24 dev br0 proto dhcp scope link src 192.168.92.100 metric 1 192.168.92.128/25 dev shim-br0 scope link

Hi all, I have an OpenVPN server running on my Unraid 6.11.5 system. OpenVPN is using the 172.16.92.32/28 CIDR and my Unraid server's local IP address is 192.168.92.100. (on the 192.168.92.0/24 CIDR) I would like Unraid to masquerade packets coming out from the OpenVPN clients, so I added the following in the IP tables: iptables -t nat -A POSTROUTING -s 172.16.92.32/28 -o br0 -j MASQUERADE However, when I set a machine to capture packets incoming from the OpenVPN clients, they are still showing as coming from the IP 172.16.92.34, and not from 192.168.92.100. Do you know why ? Many thanks, OP PS: I know I can add a route in my router to achieve a similar result but I want to have the option of not having a "prosumer" configurable router.

I did that. Will the error message just pop on the screen or should I enter some command to display some log in real time ?

I am soooooo tired with these crashes. I feel they are even more frequent since I upgraded from 6.10.x to 6.11.x. I also disabled VT-d changed plex docker path to /mnt/cache instead of /mnt/user switched to IPVLAN and still get crashes (several during the same week). I don't know what to do. My diagnostics file is attached in any case (downloaded after a power cycle, since the GUI is unresponsive when a crash occurs). The time where I was under 6.8.3 was so stable in comparison, I could keep my server running for months. Please @limetech, do something, please 🙂

Thank you @JorgeB. My array is encrypted so clicking the button result in a "Missing encryption key" error, as no field is available to enter the passphrase. I rebooted the server once again and the START/STOP buttons are now showing, along with the passphrase field. Very weird indeed I wish you a good day. OP

Hi all, After a server crash I performed a parity check and rebooted. Now I cannot start my array. The button is not even shown in the WEBGUI (see attached screenshot). I also noticed strange errors on the Docker page: Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (No such file or directory) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 712 Couldn't create socket: [2] No such file or directory Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 898 Attached are my diagnostics files. Many thanks for your help. With regards, OP

I confirm that new version 2023.02.11 seems to work again. Is there a way to recover files deleted while the version 2023.02.10 (the one with the bug) was running on my system ?

Many thanks. The NVME drive is showing back after a power cycle. I will now see if the problem happens again. I wish you a very nice day. OP

Hi @JorgeB, Thank you so much. While I was waiting, I restarted (without making the change you suggest) and now my NVME drive is shown as "missing" by unraid. Would that be still useful to try and perform the changes to the syslinux config that you suggest ? FYI mine is as follows: default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot label Unraid OS GUI Mode kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot,/bzroot-gui label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest Thank you very much. OP

Hi all I just saw that my log were filled with errors mentioning BTRFS. I am bit lost and hope someone could help me identify the problem. The NVME drive is using XFS and is set as "cache", and I have 2 SATA SSDs using BTRFS set up as a separate cache "sata-raid" pool. Note that for now, TRIM fails on the 2 SATA SSDs because my HBA card does not support it. Below are the first occurrences of the errors. The diagnostics files are also attached. Thank you so much for you help. OP Jan 31 08:44:57 MOZART emhttpd: spinning down /dev/sdb Jan 31 08:45:28 MOZART kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1 Jan 31 08:45:28 MOZART kernel: nvme nvme0: Abort status: 0x371 Jan 31 08:45:28 MOZART kernel: nvme nvme0: Abort status: 0x371 Jan 31 08:45:28 MOZART kernel: nvme nvme0: Abort status: 0x371 Jan 31 08:45:28 MOZART kernel: nvme nvme0: Abort status: 0x371 Jan 31 08:46:29 MOZART kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1 Jan 31 08:46:29 MOZART kernel: nvme nvme0: Removing after probe failure status: -19 Jan 31 08:47:29 MOZART kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1 Jan 31 08:47:29 MOZART kernel: nvme0n1: detected capacity change from 2000409264 to 0 Jan 31 08:47:29 MOZART kernel: blk_update_request: I/O error, dev nvme0n1, sector 1061649312 op 0x1:(WRITE) flags 0x8800 phys_seg 12 prio class 0 Jan 31 08:47:29 MOZART kernel: blk_update_request: I/O error, dev nvme0n1, sector 1062183136 op 0x1:(WRITE) flags 0x8800 phys_seg 12 prio class 0 Jan 31 08:47:29 MOZART kernel: blk_update_request: I/O error, dev nvme0n1, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Jan 31 08:47:29 MOZART kernel: blk_update_request: I/O error, dev nvme0n1, sector 1061659456 op 0x1:(WRITE) flags 0x8800 phys_seg 12 prio class 0 Jan 31 08:47:29 MOZART kernel: blk_update_request: I/O error, dev nvme0n1, sector 18836248 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0 Jan 31 08:47:29 MOZART kernel: blk_update_request: I/O error, dev nvme0n1, sector 1509999680 op 0x1:(WRITE) flags 0x800 phys_seg 7 prio class 0 Jan 31 08:47:29 MOZART kernel: blk_update_request: I/O error, dev nvme0n1, sector 1013529432 op 0x1:(WRITE) flags 0x8800 phys_seg 1 prio class 0 Jan 31 08:47:29 MOZART kernel: blk_update_request: I/O error, dev nvme0n1, sector 7064120 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0 Jan 31 08:47:29 MOZART kernel: blk_update_request: I/O error, dev nvme0n1, sector 7064080 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0 Jan 31 08:47:29 MOZART kernel: blk_update_request: I/O error, dev nvme0n1, sector 1013686704 op 0x1:(WRITE) flags 0x8800 phys_seg 1 prio class 0 Jan 31 08:47:29 MOZART kernel: dm-12: writeback error on inode 15528150, offset 1048576, sector 18801432 Jan 31 08:47:29 MOZART kernel: dm-12: writeback error on inode 15528150, offset 1052672, sector 18801440 Jan 31 08:47:29 MOZART kernel: dm-12: writeback error on inode 15528150, offset 1056768, sector 18801448 Jan 31 08:47:29 MOZART kernel: dm-12: writeback error on inode 1620304068, offset 0, sector 1509964864 Jan 31 08:47:29 MOZART kernel: dm-12: writeback error on inode 7026833, offset 49152, sector 7029264 Jan 31 08:47:29 MOZART kernel: dm-12: writeback error on inode 7026833, offset 53248, sector 7029304 Jan 31 08:47:29 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Jan 31 08:47:29 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0 Jan 31 08:47:29 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0 Jan 31 08:47:29 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0 Jan 31 08:47:29 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 5, rd 0, flush 0, corrupt 0, gen 0 Jan 31 08:47:29 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 6, rd 0, flush 0, corrupt 0, gen 0 Jan 31 08:47:29 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 7, rd 0, flush 0, corrupt 0, gen 0 Jan 31 08:47:29 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 8, rd 0, flush 0, corrupt 0, gen 0 Jan 31 08:47:29 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 9, rd 0, flush 0, corrupt 0, gen 0 Jan 31 08:47:29 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 10, rd 0, flush 0, corrupt 0, gen 0 Jan 31 08:47:29 MOZART kernel: dm-12: writeback error on inode 15053696, offset 581632, sector 24232304 Jan 31 08:47:29 MOZART kernel: dm-12: writeback error on inode 547072497, offset 4096, sector 510551288 Jan 31 08:47:29 MOZART kernel: XFS (dm-12): log I/O error -5 Jan 31 08:47:29 MOZART kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2438: errno=-5 IO failure (Error while writing out transaction) Jan 31 08:47:29 MOZART kernel: BTRFS: error (device loop2) in __btrfs_free_extent:3069: errno=-5 IO failure Jan 31 08:47:29 MOZART kernel: BTRFS info (device loop2): forced readonly Jan 31 08:47:29 MOZART kernel: BTRFS: error (device loop2) in btrfs_run_delayed_refs:2150: errno=-5 IO failure Jan 31 08:47:29 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [34803916800, 34803920896) Jan 31 08:47:29 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [34803916800, 34803920896) Jan 31 08:47:29 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [34803916800, 34803920896) Jan 31 08:47:29 MOZART rsyslogd: file '/mnt/user/logs/syslog/syslog-192.168.92.100.log'[10] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: Input/output error [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jan 31 08:47:29 MOZART rsyslogd: file '/mnt/user/logs/syslog/syslog-192.168.92.100.log': open error: Input/output error [v8.2102.0 try https://www.rsyslog.com/e/2433 ] Jan 31 08:47:29 MOZART kernel: XFS (dm-12): Log I/O Error (0x2) detected at xlog_ioend_work+0x50/0x6e [xfs] (fs/xfs/xfs_log.c:1377). Shutting down filesystem. Jan 31 08:47:29 MOZART kernel: BTRFS warning (device loop2): Skipping commit of aborted transaction. Jan 31 08:47:29 MOZART kernel: XFS (dm-12): Please unmount the filesystem and rectify the problem(s) Jan 31 08:47:29 MOZART kernel: dm-12: writeback error on inode 15880868, offset 5332992, sector 511744744 Jan 31 08:47:29 MOZART kernel: BTRFS: error (device loop2) in cleanup_transaction:2011: errno=-5 IO failure Jan 31 08:47:29 MOZART kernel: dm-12: writeback error on inode 15880868, offset 5337088, sector 511744752 Jan 31 08:47:29 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [20687400960, 20687405056) Jan 31 08:47:29 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [20687405056, 20687409152) Jan 31 08:47:29 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [20687409152, 20687413248) Jan 31 08:47:29 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [20687400960, 20687405056) Jan 31 08:47:29 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [17793519616, 17793523712) Jan 31 08:47:29 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [17793523712, 17793527808) Jan 31 08:47:29 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [17793519616, 17793523712) Jan 31 08:47:29 MOZART rsyslogd: file '/mnt/user/logs/syslog/syslog-192.168.92.10.log'[2] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: Input/output error [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jan 31 08:47:29 MOZART rsyslogd: file '/mnt/user/logs/syslog/syslog-192.168.92.10.log': open error: Input/output error [v8.2102.0 try https://www.rsyslog.com/e/2433 ] Jan 31 08:48:04 MOZART kernel: print_req_error: 99 callbacks suppressed Jan 31 08:48:04 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 1249656 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0 Jan 31 08:48:04 MOZART kernel: btrfs_dev_stat_print_on_error: 77 callbacks suppressed Jan 31 08:48:04 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 47, rd 41, flush 0, corrupt 0, gen 0 Jan 31 08:48:04 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 1249672 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0 Jan 31 08:48:04 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 41, flush 0, corrupt 0, gen 0 Jan 31 08:48:12 MOZART kernel: btrfs_lookup_bio_sums: 18 callbacks suppressed Jan 31 08:48:12 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [21088358400, 21088362496) Jan 31 08:48:12 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 36485992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Jan 31 08:48:12 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 42, flush 0, corrupt 0, gen 0 Jan 31 08:48:12 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [21088358400, 21088362496) Jan 31 08:48:12 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 36485992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Jan 31 08:48:12 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 43, flush 0, corrupt 0, gen 0 Jan 31 08:48:12 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [21088358400, 21088362496) Jan 31 08:48:12 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 36485992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Jan 31 08:48:12 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 44, flush 0, corrupt 0, gen 0 Jan 31 08:48:12 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [21088358400, 21088362496) Jan 31 08:48:12 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 36485992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Jan 31 08:48:12 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 45, flush 0, corrupt 0, gen 0 Jan 31 08:48:12 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [21088358400, 21088362496) Jan 31 08:48:12 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 36485992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Jan 31 08:48:12 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 46, flush 0, corrupt 0, gen 0 Jan 31 08:48:12 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [21088358400, 21088362496) Jan 31 08:48:12 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 36485992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Jan 31 08:48:12 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 47, flush 0, corrupt 0, gen 0 Jan 31 08:48:12 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [21088358400, 21088362496) Jan 31 08:48:12 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 36485992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Jan 31 08:48:12 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 48, flush 0, corrupt 0, gen 0 Jan 31 08:48:12 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [21088358400, 21088362496) Jan 31 08:48:12 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 36485992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Jan 31 08:48:12 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 49, flush 0, corrupt 0, gen 0 Jan 31 08:48:12 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [21088358400, 21088362496) Jan 31 08:48:12 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 36485992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Jan 31 08:48:12 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 50, flush 0, corrupt 0, gen 0 Jan 31 08:48:12 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [21088358400, 21088362496) Jan 31 08:48:12 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 36485992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Jan 31 08:48:12 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 51, flush 0, corrupt 0, gen 0 Jan 31 08:50:07 MOZART kernel: print_req_error: 2 callbacks suppressed Jan 31 08:50:07 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 37026528 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 Jan 31 08:50:07 MOZART kernel: btrfs_dev_stat_print_on_error: 2 callbacks suppressed Jan 31 08:50:07 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 54, flush 0, corrupt 0, gen 0 Jan 31 08:50:07 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 37550816 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 Jan 31 08:50:07 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 55, flush 0, corrupt 0, gen 0 Jan 31 08:50:07 MOZART kernel: btrfs_lookup_bio_sums: 2 callbacks suppressed Jan 31 08:50:07 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [17946841088, 17946845184) Jan 31 08:50:07 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [17946845184, 17946849280) Jan 31 08:50:07 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [17946849280, 17946853376) Jan 31 08:50:07 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [17946853376, 17946857472) Jan 31 08:50:07 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [17946857472, 17946861568) Jan 31 08:50:07 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [17946861568, 17946865664) Jan 31 08:50:07 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [17946865664, 17946869760) Jan 31 08:50:07 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [17946869760, 17946873856) Jan 31 08:50:07 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [17946873856, 17946877952) Jan 31 08:50:07 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [17946877952, 17946882048) Jan 31 08:50:07 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 34544520 op 0x0:(READ) flags 0x80700 phys_seg 14 prio class 0 Jan 31 08:50:07 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 34544520 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Jan 31 08:50:07 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 56, flush 0, corrupt 0, gen 0 Jan 31 08:50:07 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 37182624 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 Jan 31 08:50:07 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 57, flush 0, corrupt 0, gen 0 Jan 31 08:50:07 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 37706912 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 Jan 31 08:50:07 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 58, flush 0, corrupt 0, gen 0 Jan 31 08:50:07 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 37184224 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 Jan 31 08:50:07 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 59, flush 0, corrupt 0, gen 0 Jan 31 08:50:07 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 37708512 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 Jan 31 08:50:07 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 60, flush 0, corrupt 0, gen 0 Jan 31 08:50:07 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 37186080 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 Jan 31 08:50:07 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 61, flush 0, corrupt 0, gen 0 Jan 31 08:50:07 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 37710368 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 Jan 31 08:50:07 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 62, flush 0, corrupt 0, gen 0 Jan 31 08:50:07 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 63, flush 0, corrupt 0, gen 0 Jan 31 08:51:22 MOZART kernel: btrfs_lookup_bio_sums: 5 callbacks suppressed Jan 31 08:51:22 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [21088358400, 21088362496) Jan 31 08:51:22 MOZART kernel: print_req_error: 4542 callbacks suppressed Jan 31 08:51:22 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 36485992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Jan 31 08:51:22 MOZART kernel: btrfs_dev_stat_print_on_error: 4541 callbacks suppressed Jan 31 08:51:22 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 4605, flush 0, corrupt 0, gen 0 Jan 31 08:51:22 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [21088358400, 21088362496) Jan 31 08:51:22 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 36485992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Jan 31 08:51:22 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 4606, flush 0, corrupt 0, gen 0 Jan 31 08:51:22 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [21088358400, 21088362496) Jan 31 08:51:22 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 36485992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Jan 31 08:51:22 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 4607, flush 0, corrupt 0, gen 0 Jan 31 08:51:22 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [21088358400, 21088362496) Jan 31 08:51:22 MOZART kernel: blk_update_request: I/O error, dev loop2, sector 36485992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Jan 31 08:51:22 MOZART kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 48, rd 4608, flush 0, corrupt 0, gen 0 Jan 31 08:51:22 MOZART kernel: BTRFS warning (device loop2): csum hole found for disk bytenr range [21088358400, 21088362496)

I checked all commands of https://wiki.unraid.net/Console#Console_Commands_for_Hard_Drives as well as the lsblk command, but without any success.

After updating to Unraid 6.11.5, I finally get the same results as you: I was able to start the array in maintenance mode after deleting only the LUKS keys. I was able to wipe the LUKS header completely with "wipefs -a /dev/md1" (but I had to restart the array in maintenance mode). I was able to restore the LUKS header on /dev/mdX (i.e. with the array started in maintenance mode) I did not get any error after a performing a parity check after all that. I opened a new thread here to get additional help regarding how to obtain the SERIAL_ID of the disk hosting a certain dev/mdX managed partition.

Hi @itimpi, many thanks. I did indeed test that with @Kilrah in this thread, and the results are inconsistent. With the LUKS key missing on one drive, the array can start on @Kilrah's system, bit on mine the array fails to start. However, with the LUKS header completely removed (not just the key), it seems that I can start the array.

Hi all, How can I identify, via command line, which /dev/sdX1 partition corresponds to the /dev/mdYp1 managed partition? The info is on the WebGUI main page but I need to get that info in the context of a script. Many thanks. OP

I tried on my system and had parity errors...: root@BEETHOVEN:/boot/luks# cryptsetup erase /dev/md1 WARNING! ======== This operation will erase all keyslots on device /dev/md1. Device will become unusable after this operation. Are you sure? (Type 'yes' in capital letters): YES root@BEETHOVEN:/boot/luks# wipefs -a /dev/md1 wipefs: error: /dev/md1: probing initialization failed: Device or resource busy root@BEETHOVEN:/boot/luks# dd if=/dev/zero of=/dev/md1 bs=1 count=16777216 16777216+0 records in 16777216+0 records out 16777216 bytes (17 MB, 16 MiB) copied, 17.0588 s, 983 kB/s root@BEETHOVEN:/boot/luks# cryptsetup luksHeaderRestore /dev/md1 --header-backup-file "QEMU_HARDDISK_QM00011.bin" WARNING! ======== Device /dev/md1 does not contain LUKS2 header. Replacing header can destroy data on that device. Are you sure? (Type 'yes' in capital letters): YES root@BEETHOVEN:/boot/luks# Last check completed on Sat 21 Jan 2023 03:14:40 PM CET (today) Finding 63 errors Duration: 13 seconds. Average speed: 247.8 MB/sec

Likewise.

On my former test I used "cryptsetup erase /dev/sdx1". So I did like you: array started in normal mode run backup script cryptsetup erase /dev/md1 (variation in my testing) stop array reboot (new step in my testing) > the array fails to start, as with "cryptsetup erase /dev/sdx1" Our results are clearly different.. FYI I use Unraid 6.9.2 on my testing VM.

I did further testing: If I run "cryptsetup erase" on an encrypted drive to clear the LUKS encryption key on that drive (but maintaining the LUKS header) then the array won't start, even if I tick "maintenance mode". If I run "cryptsetup erase" on an encrypted drive to clear the LUKS encryption key on that drive and then also "wipefs -a /dev/sdX1" to erase the LUKS remaining header (as instructed here), then the array will start, as on your system.

Yes. But in any case, I think that the encryption key is in the LUKS header, and is not the passphrase, which is only a way to decipher the actual encryption key in the LUKS header. Also, I think the encryption keys in the LUKS header are different on each drive.

I opened a new General support thread to obtain additional info here and did some testing. It seems that it is not possible to write to /dev/mdX if the array is not started, and starting the array with one bad LUKS header is not possible. So I guess that in the scenario of a bad LUKS header preventing the start of the array, a rebuild of the parity would be needed. Do you concur ?

I checked and the array does not start (even in maintenance mode) if one data drive doesn't have the proper LUKS key is its header: Jan 21 11:24:29 BEETHOVEN kernel: mdcmd (117): set md_num_stripes 1280 Jan 21 11:24:29 BEETHOVEN kernel: mdcmd (118): set md_queue_limit 80 Jan 21 11:24:29 BEETHOVEN kernel: mdcmd (119): set md_sync_limit 5 Jan 21 11:24:29 BEETHOVEN kernel: mdcmd (120): set md_write_method Jan 21 11:24:29 BEETHOVEN kernel: mdcmd (121): start STOPPED Jan 21 11:24:29 BEETHOVEN kernel: unraid: allocating 20870K for 1280 stripes (4 disks) Jan 21 11:24:29 BEETHOVEN kernel: md1: running, size: 2097120 blocks Jan 21 11:24:29 BEETHOVEN kernel: md2: running, size: 2097120 blocks Jan 21 11:24:29 BEETHOVEN emhttpd: shcmd (5231): udevadm settle Jan 21 11:24:29 BEETHOVEN emhttpd: Opening encrypted volumes... Jan 21 11:24:29 BEETHOVEN emhttpd: shcmd (5234): /usr/sbin/cryptsetup luksOpen /dev/md1 md1 --allow-discards Jan 21 11:24:29 BEETHOVEN emhttpd: shcmd (5237): /usr/sbin/cryptsetup luksOpen /dev/md2 md2 --allow-discards Jan 21 11:24:31 BEETHOVEN emhttpd: shcmd (5240): /usr/sbin/cryptsetup luksOpen /dev/sdc1 sdc1 --allow-discards Jan 21 11:24:33 BEETHOVEN emhttpd: Missing encryption key Jan 21 11:24:33 BEETHOVEN emhttpd: shcmd (5241): /usr/sbin/cryptsetup luksClose md2 Jan 21 11:24:33 BEETHOVEN emhttpd: shcmd (5242): /usr/sbin/cryptsetup luksClose sdc1 Jan 21 11:24:33 BEETHOVEN kernel: mdcmd (122): stop Jan 21 11:24:33 BEETHOVEN kernel: md1: stopping Jan 21 11:24:33 BEETHOVEN kernel: md2: stopping So the operations should be performed on /dev/sdX1 I guess.