Apparently whenever my weekly SnapRAID sync job configured via the SnapRAID plugin runs, it causes one LUKS volume on a USB HDD to unmount.
The LUKS volume in question (A) is part of a mergerFS pool with another, smaller drive (B). SnapRAID is set up to sync both data drives (A & B) to a third parity drive (C).
I found this thread describing pretty much the same issue with no apparent solution. According to info in this thread, the issue might be that the drive goes to sleep or gets disconnected because of disk I/O from the SnapRAID sync. But since the drive seems to work reliably in regular operation (frequent disk I/O), this doesn't seem very plausible to me.
Similar to their issue, I consistently get the software issue page from OMV after manually reloading the mergerFS pool after manually unlocking the LUKS volumes after a reboot; however, after simply reloading the page the pool works as expected and shows up correctly in the OMV webGUI.
However, I found these log entries:
journalctl -o short-precise -k
Okt 23 13:05:35.305443 OMV kernel: usb 2-4: reset SuperSpeed USB device number 2 using xhci_hcd
Okt 23 13:05:35.329429 OMV kernel: sd 2:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
Okt 23 13:05:35.330472 OMV kernel: sd 2:0:0:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 02 78 75 65 10 00 00 00 88 00 00
Okt 23 13:05:35.330904 OMV kernel: I/O error, dev sdc, sector 10610894096 op 0x0:(READ) flags 0x80700 phys_seg 17 prio class 2
...
Okt 25 10:17:41.647963 OMV kernel: I/O error, dev sdc, sector 25959428936 op 0x0:(READ) flags 0x80700 phys_seg 32 prio class 2
Okt 25 10:18:15.905742 OMV kernel: usb 2-4: reset SuperSpeed USB device number 2 using xhci_hcd
Okt 25 10:18:15.925459 OMV kernel: sd 2:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
Okt 25 10:18:15.926522 OMV kernel: sd 2:0:0:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 06 0b 53 55 40 00 00 01 00 00 00
Okt 25 10:18:15.927299 OMV kernel: I/O error, dev sdc, sector 25959814464 op 0x0:(READ) flags 0x80700 phys_seg 18 prio class 2
...
Okt 26 11:14:36.112416 OMV kernel: I/O error, dev sdc, sector 26601962464 op 0x0:(READ) flags 0x80700 phys_seg 32 prio class 2
Okt 27 03:06:34.385435 OMV kernel: mce: CMCI storm detected: switching to poll mode
Okt 27 03:11:35.001719 OMV kernel: mce: CMCI storm subsided: switching to interrupt mode
Okt 27 04:15:55.081580 OMV kernel: usb 2-4: USB disconnect, device number 2
Okt 27 04:15:55.389821 OMV kernel: usb 2-4: new SuperSpeed USB device number 5 using xhci_hcd
Okt 27 04:15:55.409543 OMV kernel: usb 2-4: New USB device found, idVendor=1058, idProduct=25a3, bcdDevice=10.29
Okt 27 04:15:55.411286 OMV kernel: usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Okt 27 04:15:55.412229 OMV kernel: usb 2-4: Product: Elements 25A3
Okt 27 04:15:55.413066 OMV kernel: usb 2-4: Manufacturer: Western Digital
Okt 27 04:15:55.413963 OMV kernel: usb 2-4: SerialNumber: [redacted]
Okt 27 04:15:55.414803 OMV kernel: usb-storage 2-4:1.0: USB Mass Storage device detected
Okt 27 04:15:55.415801 OMV kernel: scsi host5: usb-storage 2-4:1.0
Okt 27 04:15:56.446151 OMV kernel: scsi 5:0:0:0: Direct-Access WD Elements 25A3 1029 PQ: 0 ANSI: 6
Okt 27 04:15:56.447874 OMV kernel: sd 5:0:0:0: Attached scsi generic sg2 type 0
Okt 27 04:15:56.448881 OMV kernel: sd 5:0:0:0: [sde] Very big device. Trying to use READ CAPACITY(16).
Okt 27 04:15:56.450000 OMV kernel: sd 5:0:0:0: [sde] 27344699392 512-byte logical blocks: (14.0 TB/12.7 TiB)
Okt 27 04:15:56.451044 OMV kernel: sd 5:0:0:0: [sde] 4096-byte physical blocks
Okt 27 04:15:56.451955 OMV kernel: sd 5:0:0:0: [sde] Write Protect is off
Okt 27 04:15:56.452843 OMV kernel: sd 5:0:0:0: [sde] Mode Sense: 47 00 10 08
Alles anzeigen
Which seem to point to disconnect issues on that drive (sde = A, the drive causing problems). I'm also a bit confused regarding the errors for sdc, my mounts at the moment are sda, sdb, sdd and sde.
LUKS is setup to decrypt sdb, sdd and sde. I'm not sure why one of the drives wasn't automatically mounted as sdc in the first place. After a reboot, the drives mount as sda,b,c and d as expected, so I currently regard this as a side effect of the frequent disconnects and remounts.
I have OMV6 installed on a small x64 PC with 3 externally powered USB HDDs connected and a SATA SSD as boot drive. A few weeks ago, I scrapped my old OMV6 (software) setup due to boot drive failure and started from scratch (complete reinstall, no restoration of backup) with the exact same hardware setup (except a new boot drive). This wasn't an issue before with pretty much the identical setup.
Does anybody have an idea what the issue here could be?