- Solved
- Urgent
Noticed I hadn't updated for a while, seen 7.1.4 was available followed the on-screen prompts. When the WEBUI was available noticed all drives in array had the above error.
I would really appreciate help getting this back up and running ASAP I don't want to try and tinker and make it worse!
unraid-7.1.4.txt domain.cfg nvme.cfg downvme.cfg docker.cfg i915.conf editor.cfg super.dat ident.cfg network.cfg go.txt disk.cfg listen.txt ST18000NM001J-2TV113_ZR59A5XV-2025-02-25 disk1 (sdb).txt Fanxiang_S501Q_2TB_FXS501Q234930374-2025-02-25 nvme (nvme0).txt Fanxiang_S500PRO_2TB_FXS500PRO231536919-2025-02-25 downvme (nvme2).txt ST16000NM001J-2TW113_ZRS0DHXZ-2025-02-25 disk3 (sdd).txt SanDisk_Cruzer_Blade_03002220032024074030-0-0-2025-02-25 flash (sda).txt ST16000NM001J-2TW113_ZR5311X9-2025-02-25 disk2 (sdc).txt Fanxiang_S660_2TB_FX2318018638-2025-02-25 nvme2 (nvme1).txt nvme.1e4b-46585335303151323334393330333734-46616e7869616e6720533530315120325442-00000001-2025-02-25 nvme (nvme0).txt nvme.1e4b-465832333138303138363338-46616e7869616e67205336363020325442-00000001-2025-02-25 nvme2 (nvme1).txt nvme.1e4b-46585335303050524f323331353336393139-46616e7869616e67205335303050524f20325442-00000001-2025-02-25 downvme (nvme2).txt ST18000NM000J-2TV103_ZR5292PZ-2025-02-25 parity (sde) - DISK_INVALID.txt cmdline.txt btrfs-usage.txt gpujson.txt drm.txt plugins.txt motherboard.txt iommu_groups.txt ntp.txt aspm-status.txt ethtool.txt folders.txt sshd.txt lsmod.txt lsscsi.txt loads.txt testparm.txt memory.txt lspci.txt meminfo.txt lsusb.txt urls.txt top.txt servers.conf.txt vars.txt lscpu.txt lsof.txt df.txt ifconfig.txt graphql-api.txt syslog-previous.txt syslog.txt appdata.cfg domains.cfg n--------------p.cfg isos.cfg system.cfg d--a.cfg shareDisks.txt n-------d.cfg p-----------h.cfg n------n.cfg