StratoGh0st

The workaround for the cache worked! The behavior of the array disks is strange. Yesterday i could mount them in unraid (cryptsetup luksOpen, etc...), now (i just shut the pc down yesterday) the luksOpen works but the ext4 is not accessible. I connected on of the drives to my mac and tried to mount it, but with the same result. I can understand, that one of these USB drives fails, but two at the same time? I will try to repair one drive or at least get the data out of it. The two USB drives has only backup data on it, not critical but strange. Big thanks for the help to get the cache back online!

I dont know how that happened. I just hit shutdown from the ui and waited until the power led turned off. Thats how i can mount the zfs: root@earth:~# zpool status no pools available root@earth:~# zpool import pool: cache id: 4300929232344889756 state: ONLINE action: The pool can be imported using its name or numeric identifier. config: cache ONLINE mirror-0 ONLINE nvme1n1p1 ONLINE nvme0n1p1 ONLINE root@earth:~# zpool import cache root@earth:~# zpool status pool: cache state: ONLINE config: NAME STATE READ WRITE CKSUM cache ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 nvme1n1p1 ONLINE 0 0 0 nvme0n1p1 ONLINE 0 0 0 errors: No known data errors root@earth:~# zfs list NAME USED AVAIL REFER MOUNTPOINT cache 66.5G 384G 136K /mnt/cache cache/appdata 4.31G 384G 4.31G /mnt/cache/appdata cache/domains 6.16G 384G 136K /mnt/cache/domains cache/domains/k3s-master 158M 384G 158M /mnt/cache/domains/k3s-master cache/domains/k3s-worker-1 158M 384G 158M /mnt/cache/domains/k3s-worker-1 cache/domains/k3s-worker-2 158M 384G 158M /mnt/cache/domains/k3s-worker-2 cache/domains/talos-cp-1 2.03G 384G 2.03G /mnt/cache/domains/talos-cp-1 cache/domains/talos-w-1 1.78G 384G 1.78G /mnt/cache/domains/talos-w-1 cache/domains/talos-w-2 1.89G 384G 1.89G /mnt/cache/domains/talos-w-2 cache/isos 1.17G 384G 1.17G /mnt/cache/isos cache/kubernetes 124K 384G 124K /mnt/cache/kubernetes cache/media 44.7G 384G 44.7G /mnt/cache/media cache/system 10.1G 384G 10.1G /mnt/cache/system

Thanks for your reply! root@earth:~# fdisk -l /dev/md1p1 Disk /dev/md1p1: 1.82 TiB, 2000393486336 bytes, 3907018528 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes root@earth:~# fdisk -l /dev/md2p1 Disk /dev/md2p1: 465.76 GiB, 500102422528 bytes, 976762544 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes

Hi everyone, today I moved my Unraid server to a new location. Before the move, I shut the system down cleanly and without any errors. About 6 hours later, I powered it back on, but now I can no longer start the array. System setup: Array disks: 2× USB drives (used for years without issues) File system: EXT4 encrypted Cache: 2× NVMe in ZFS mirror, encrypted Everything was working perfectly before the shutdown and move Current situation: Unraid refuses to start the array and shows the error: “Unmountable: wrong or no file system” (see screenshot) The ZFS cache pool works fine: I can manually import the pool using zpool import cache I can access all data without any issues The EXT4 encrypted array disks also seem intact: I can manually mount them The data is accessible So it looks like the file systems themselves are not damaged, but Unraid no longer recognizes them correctly when starting the array. What I’m trying to understand: Why Unraid suddenly thinks the array disks have no or the wrong file system Whether this could be related to the move, USB device enumeration, encryption, or disk assignment What the safest way is to get the array running again without risking data loss Any help or guidance would be greatly appreciated. Thanks in advance! earth-diagnostics.zip

Hallo, ich bin neu in der Unraid-Welt und spiele aktuell mit meinem Intel NUC10i7FNB herum. Container und VMs (Debian, Ubuntu, Windows) laufen soweit top. Jetzt wollte ich die integrierte iGPU an meine Win10-VM durchreichen, was nicht geklappt hat. Entweder meldete Unraid, dass das PCI-Device bereits verwendet wird, eben von Unraid selbst, was sich jedoch auch nicht über das "markieren" für vifo unter "Tools -> Devices" ändern lies. Die iGPU wurde weiter von Unraid verwendet. Danach habe ich "PCIe ACS override: Both" aktiviert und in der Syslinux Config (ich weis die Parameter leider nicht mehr) die Bildausgabe deaktiviert. Somit wurde nach dem Unraid-Start die iGPU auch deaktivert, konnte sie aber keiner VM zuweisen, da die iGPU nicht mehr unter "Tools -> Devices" gelistet wird. Auch wird jetzt nach dem booten ca. 10 Sekunden die Unraid-Shell auf dem Monitor angezeigt, danach geht dieser einfach aus. Der System-Log meint folgendes Dazu: Oct 2 12:01:21 unraid root: -----------------Loading Kernel Module 'i915'------------------ Oct 2 12:01:21 unraid kernel: Linux agpgart interface v0.103 Oct 2 12:01:21 unraid kernel: Setting dangerous option force_probe - tainting kernel Oct 2 12:01:21 unraid kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access Oct 2 12:01:21 unraid kernel: checking generic (4000000000 7e9000) vs hw (6022000000 1000000) Oct 2 12:01:21 unraid kernel: checking generic (4000000000 7e9000) vs hw (4000000000 10000000) Oct 2 12:01:21 unraid kernel: fb0: switching to inteldrmfb from EFI VGA Oct 2 12:01:21 unraid kernel: Console: switching to colour dummy device 80x25 Oct 2 12:01:21 unraid kernel: i915 0000:00:02.0: vgaarb: deactivate vga console Oct 2 12:01:21 unraid kernel: i915 0000:00:02.0: Direct firmware load for i915/gvt/vid_0x8086_did_0x9bca_rid_0x04.golden_hw_state failed with error -2 Oct 2 12:01:21 unraid kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Oct 2 12:01:21 unraid kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Oct 2 12:01:21 unraid kernel: [drm] Initialized i915 1.6.0 20200917 for 0000:00:02.0 on minor 0 Oct 2 12:01:21 unraid kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) Oct 2 12:01:21 unraid kernel: acpi device:0f: registered as cooling_device16 Oct 2 12:01:21 unraid kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8 Oct 2 12:01:21 unraid kernel: fbcon: i915drmfb (fb0) is primary device Oct 2 12:01:21 unraid kernel: Console: switching to colour frame buffer device 240x67 Oct 2 12:01:21 unraid kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device Oct 2 12:01:21 unraid kernel: i915 0000:00:02.0: MDEV: Registered