LimeB

Just to confirm. I can do this by just copying everything off, for mat, than copy it back over?

After my last post, system booted up and went into a bad state probably within minutes but I didn't notice for a few hours. I went ahead and ran a memtest and no errors with 9 passes. I have moved the memory into dual channel, and I am still having issues. Now what I am seeing is within minutes of the array being started, my docker containers will crash, and can't start. I am seeing my cache drive being unmountable as per my other post. I can run the command you suggested, it gets me running again. Maybe I am running into multiple issues here because I'm not seeing the initial UI problem anymore but now more just docker keeps failing because of my cache drive. Attached is a diag after the latest boot and crash. This last time I did disable docker, started the array, then enabled docker. diagnostics-20240204-0119.zip

Maybe the macvlan inadvertently got changed when I was then messing with some other settings for working on something else. I felt like it was staying stable after I initially changed to ipvlan but thinking back, it must have got changed back and I became unstable again. Now it is changed again and I'll see how it holds up, along with running a memtest.

I think I am still having related issues, or maybe it is something else. I again had hard reset the box, and after that I had an issue which I created another post about with my cache drive which it is working again. Twice though docker containers were not running, stopped I guess at some point, and wouldn't start until I rebooted. Currently this was happening, I am trying to stop the array but it is not stopping. Attached is the current diag and I have tried physically rebooting it yet. Maybe this is a separate issue from before but i'm not certain. diagnostics-20240127-2005.zip

Awesome. I am back in business! Thank you.

I had an unclean shutdown and coming back up, my cache drive is not mountable. Attached are my diags. Unmountable disk present: Cache • Samsung_SSD_970_EVO_Plus_2TB_S59CNM0RA30351D (nvme0n1) btrfs check with -n [1/7] checking root items [2/7] checking extents [3/7] checking free space tree free space info recorded 5227 extents, counted 5237 wanted offset 50535092224, found 50535088128 cache appears valid but isn't 50487885824 free space info recorded 1388 extents, counted 1398 There are still entries left in the space cache cache appears valid but isn't 59077820416 [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/mapper/nvme0n1p1 UUID: 511844b9-b3cc-4da0-bac2-e4c2d3fcff7f found 1031122690048 bytes used, error(s) found total csum bytes: 646066272 total tree bytes: 1119682560 total fs tree bytes: 158973952 total extent tree bytes: 107642880 btree space waste bytes: 243970093 file data blocks allocated: 5365445775360 referenced 955935105024 btrfs check with no modifier [1/7] checking root items [2/7] checking extents [3/7] checking free space tree free space info recorded 5227 extents, counted 5237 wanted offset 50535092224, found 50535088128 cache appears valid but isn't 50487885824 free space info recorded 1388 extents, counted 1398 There are still entries left in the space cache cache appears valid but isn't 59077820416 [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/mapper/nvme0n1p1 UUID: 511844b9-b3cc-4da0-bac2-e4c2d3fcff7f found 1031122690048 bytes used, error(s) found total csum bytes: 646066272 total tree bytes: 1119682560 total fs tree bytes: 158973952 total extent tree bytes: 107642880 btree space waste bytes: 243970093 file data blocks allocated: 5365445775360 referenced 955935105024 btrfs check with -L [1/7] checking root items [2/7] checking extents [3/7] checking free space tree free space info recorded 5227 extents, counted 5237 wanted offset 50535092224, found 50535088128 cache appears valid but isn't 50487885824 free space info recorded 1388 extents, counted 1398 There are still entries left in the space cache cache appears valid but isn't 59077820416 [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/mapper/nvme0n1p1 UUID: 511844b9-b3cc-4da0-bac2-e4c2d3fcff7f found 1031122690048 bytes used, error(s) found total csum bytes: 646066272 total tree bytes: 1119682560 total fs tree bytes: 158973952 total extent tree bytes: 107642880 btree space waste bytes: 243970093 file data blocks allocated: 5365445775360 referenced 955935105024 While it is not critical if I have to format the drive but hate to do it. Any thoughts on what I can try to fix it? diagnostics-20240124-0800.zip

Appreciate the suggestion. Yesterday the UI died on me a few times, once while stopping docker. I made the change and so far it has been holding since yesterday. It is possible that maybe docker wasn't failing on me except that one time which I posted this 2 days ago but I was assuming it also had been.

A few times since upgrading my parity drive to a larger one, I am having issues with my server going into a bad state. I feel like this is similar to what I initially saw happening when I switched from Intel to AMD but the issues went away after I change some recommended settings but I think I recall I even changed the BIOS back to defaults. It has been fine for a few years now. It seems like if I have to hard reset the system, it will boot up, run file while parity check is happening, but then later in the day, or next, the UI becomes unresponsive. I am able to SSH in and reset the UI. And say right now, I see that my docker containers are all but 1 stopped and the stopped ones are throwing an error. VMs will throw an error if I try to start them. Attached is my diags. diagnostics-20240108-1437.zip

I ended up stumbling on this video and went with using the -L flag. After doing so, all is well again it seems. I also just realized I ran into corruption a few years ago and read through that thread as well. That one I also went through the repair with -L.

I also did -n and this came up: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... sb_fdblocks 1348690186, counted 1369121098 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 inode 6892288466 - bad extent starting block number 4503567551069610, offset 0 correcting nextents for inode 6892288466 bad data fork in inode 6892288466 would have cleared inode 6892288466 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 6 - agno = 3 - agno = 5 - agno = 7 - agno = 1 - agno = 8 - agno = 9 - agno = 10 - agno = 4 entry "2013-11-28 002.JPG" at block 0 offset 128 in directory inode 6892288464 references free inode 6892288466 would clear inode number in entry at offset 128... inode 6892288466 - bad extent starting block number 4503567551069610, offset 0 correcting nextents for inode 6892288466 bad data fork in inode 6892288466 would have cleared inode 6892288466 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... entry "2013-11-28 002.JPG" in directory inode 6892288464 points to free inode 6892288466, would junk entry bad hash table for directory inode 6892288464 (no data entry): would rebuild would rebuild directory inode 6892288464 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting.

I did that through the GUI method and this came up immediately: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.

A few days ago I noticed that my server was acting up which the GUI was kind of working but then when I was trying to navigate to a few areas it just all together stopped working. I ended up having to do a hard reset on the box and now it is back up the main data disk I care about comes up as "Unmountable: Unsupported or no file system". Attached is the diagnostics after booting up now.

Giving myself a bump. How would I try the other suggestions above?

Kind of put this to the side and forgot about it but now I want to try to get this figured out. I am not sure how to do either of these suggestions.

Appreciate the quick reply. I tried using the updated virtio drivers you linked but Windows says it was unable to install. Since it is my E drive I have tried: E:\ E:\vioscsi\ E:\vioscsi\w11\ E:\vioscsi\w11\amd64 And selected to include subfolders.

I am having a hard time getting an optical drive to passthrough. I had it working just fine for years with Windows 10. I have since built a new VM with Windows 11, pretty sure it was working when initially set it up but many months later trying to use this VM again, it's not working. I am trying to passthrough this drive: SCSI Devices [1:0:0:0]cd/dvd HL-DT-ST BD-RE WH16NS40 1.02 /dev/sr0 Here is my XML: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>HomeVM</name> <uuid>3654d69a-1687-4e8f-17ce-f95c65879313</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='10'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='12'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-6.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/3654d69a-1687-4e8f-17ce-f95c65879313_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='2' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/cache/Virtual Machines/BrianVM/vdisk2.im'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/nvme1n1'/> <target dev='hdd' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Win11_English_x64v1.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.225-2.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='scsi' index='0' model='lsilogic'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <controller type='scsi' index='1' model='lsilogic'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='bridge'> <mac address='52:54:00:e7:bb:c2'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> </tpm> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='scsi' managed='no'> <source> <adapter name='scsi_host1'/> <address bus='0' target='0' unit='0'/> </source> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> Not sure if this matters or not but I also have in Device Manager 2 SCSI Controllers showing without drivers. Other device SCSI Controller SCSI Controller But if I select the drive for virtio-win-0.1.225, it it unable to find the drivers

I have a VM (Windows 11) which seems to work okay when I select the video as vnc but when I change it to a dedicated card, it fails to boot. It did boot the first few times but then after a reboot, it not longer boots. I currently don't have a monitor to plug into it so I'm not sure what it would show. Here is a link to the log: https://1drv.ms/u/s!AqMvaDEKz3nnlconBp2VZhctiTR5VA?e=sgHLnH Any thoughts to what is wrong?

Should this allow to copy the files to any other system and able to play them? And are the recordings in a chronological order?

I am impressed. I don't really know much using Linux so this for sure not something I would have figured out. It would be interesting if you could move the video files over to an existing drive would work. I did read there is a DB and would assume that helps with having multiple cameras.

Sounds like it may not be a simple way to just have it in the Unraid system and extract the video. I was really hoping to use pop the drive in, run say Unifi Protect Remux, and would be good to go. I ended up shipping my Pro and for now put in a different drive into my SE. The chances are pretty slim that I will need the prior recordings. I have had to use some before for a legally issue but I think for the most part, as of about a week or so ago when a judge made an oral ruling, I don't think any prior recordings could be used in court if I needed. Or it might be after July 14th when the judge actually signs the orders. Seems like such a big issue not to have a way to extract the video. You can't just hand the drive to someone, say the police. Or what if there was a fire and the hardware died but the drive was intact?

I think going forward I’ll try that with the SE. The situation I’m in I actually may need to often keep a duplicate drive offsite as there is a chance the SE would get damaged, or stolen. But for the moment I need to make sure I can unload the files from my Pro as I want to sell off the Pro and not have it laying around.

I currently have a Unifi UDM Pro but am swapping it out for a UDM SE. It is my understanding that I can't just move the HDD from the Pro to the SE and keep my current recordings for Protect. And Unifi UI within the UI is not very good on downloading recordings and the files are for Unfi are a proprietary so they can't just be accessed from another system. But one tool that was suggested to me is Unifi Protect Remux. Aside from this tool, does anyone have any suggestions either using unRAID or another on extracting the videos from the UDM Pro? And does anyone have any suggestions on how to get Unifi Protect Remux to run off of unRAID? While I work in IT, i don't work with Linux and am very basic, needing to look everything up and figure it out. I'm just not sure how to get Remux to work on unRAID which seems to likely be an easy solution on getting the videos off of the HDD. Or maybe any other suggestions/guides that could help me? For legal reasons, I need to keep the videos for some period and would prefer not keeping the UDM Pro laying around.

For the moment, my living situation is that I am in a rental and it isn't known yet when I will be back into my house, hopefully just a few more months. I have my server in the garage in the rental. I am using UniFi and I have an AP in the living room and have another AP in the garage plugged directly into my server and setup as a bridge. It works but would prefer using wifi directly from the server.

Enabling SSL on the server didn't help but doing option 2 from https://www.technipages.com/google-chrome-bypass-your-connection-is-not-private-message did. Option 2 – Prevent Warning Click a blank section of the denial page. Using your keyboard, type thisisunsafe. This will add the website to a safe list, where you should not be prompted again. I thought I also had tried this before my original post but maybe I kept mistyping.

I think that likely would resolve it. But I'd imagine there is a way not to have to enable this and still view on. I just can't figure it out.