Evedoescomputerstuff

First. Do VMs work with no GPU and VNC selected? If they do, PCI ACS Override + Multifunction. ACS override is a GUI setting, multifunction can only be enabled for the VM by editing the XML. You may have to play with which ACS override setting to use and the multifunction setting in the XML.

I'd love an explanation, this has been plaguing me for like a week out of the blue and since it's not *actually* broken I haven't waded through all the forum posts to find out why this happens but I am curious! Mainly since I get errors in the log before I even launch the VNC viewer in my browser, yet everything works.... It's just interesting.

At this point since it's fixed, surely you don't want to mess around. However, i'm very curious about the processor now. Since unRAID was unable to boot did you ever try another OS during this process? Mainly just wondering if the processor somehow went bad or theres actually an incompatibility with unRAID? Been planning on trying unRAID with some Ryzen builds (you know the drill, old desktop becomes another server) now that the prices keep falling.

Can we try to see if this is some weird hardware problem unrelated to unraid? Have you ever been able to boot another OS or live image on this machine?

This is probably not the right answer but can you try re-creating your VMs (not their vdisks ) from scratch?

Rad. It's not *exactly* a bug but definitely not intuitive as it could be. The addition of 'optional' devices is sweet.

Yeah, you need to pass through the NVMe PCI-E device directly, not just map the vdisk location to it. In other words, you don't want to be using a vdisk.

That's strange. Can you try CRU to force the resolution / refresh? Display Port? If none of this works, for sanity, do you have another 4K 60hz capable display you can try? Anything to get a different EDID will be helpful.

Did a reboot fix it and allow you to boot the VM again? With USB I agree things can be finnicky, a slightly more surefire system (and one that supports hotplug) is finding a 'group' of USB ports on your unRAID machine that can be passed through as a USB controller. Those ports will become unavailable to unRAID or other things on your server, but will in ideal circumstances, function as regular hotpluggable USB ports to the VM. I highly recommend considering copying the 'xml' (you don't need to use XML for most VM config tasks) at each stage as you're working through making the VM. It makes it much easier to revert to something that did work. Furthermore, as you're figuring this out, copying the vdisk image file for your VM at various stages is useful as well. It's a snapshot of the computer essentially and makes trying something out hassle free as you can always restore the working image. This is actually one of the reasons I *really* like the VM system (once it works, passing stuff through is always going to be a bit of trial and error), snapshotting and quickly switching through images can be helpful if you're trying things liable to break an OS, or if you're developing something for a specific config. As mentioned by others, passing through an iGPU isn't as trivial as it you'd think due to how IOMMU assignments get sliced up and parted out so to speak. That's why a supported dGPU is often easier to make work in a VM.

I'm not an expert, hopefully one of the more seasoned unRAID VM users will chime in. The only other thing I noticed was "pc-i440fx-6.2" . I've been using QXL with much better results when dealing with physical hardware. Try that. Searching on the forums leads to a few other people dealing with the same error.

I have a p400 in one of my unraid builds passed through to a VM for basic desktop accel (it used to be for transcoding). Works great. The vBios is probably what you're missing since you didn't mention it and it's easy to overlook. I just grabbed a vbios from TechPowerUp. The Quadro cards aren't as 'AIB'd' to death like consumer cards so finding a compatible vbios is easy. If you for some reason can't find your card on TechPowerUp, you might have to dump the vBios yourself. There's a script that allegedly works but hasn't for me in the past. The *easiest* way to reliably extract it is to toss it in a computer, boot up windows and use GPU-Z to save it to a file. Place the resulting file on your server in one of your shares (like isos alongside your OS install images), then on the VM config GUI in the GPU section, locate your bios file. If you're using it for transcode that means the GPU works (in theory) and that you probably have the same nvidia drivers for Unraid as I do. I don't *think* you need the Unraid nvidia plugin just to pass the GPU through but I figured I'd mention it since it is running in my setup. The p400 I have is most likely the same as yours and I was actually blown away at how easy it was to get working with a tiny bit of tinkering. As for passing iGPUs? I haven't played with it but that sounds like way too much of a headache. GPU prices are crashing so depending on what your goal is for pass through, something cheap might work wonders and be significantly easier to get working. I tried TrueNAS Scale on the first RC (so please take this with a grain of salt) and didn't like it. Docker configuration sucked, charts were meh, portainer helped a bit. I was getting really bizarre slow downs and lockups without much logic behind them and felt as though with my more 'JBOD' storage arrangement that it wasn't right for me. If you don't need ZFS and you already use unRAID, I can't think of a major reason to switch over IMO.

Curious too as i'm looking at Epyc builds.

Not an expert by any stretch but multifunction may help you here. The GUI doesn't have an option for it (so you'll have to edit XML, and if you use the GUI to make any changes, re-edit your XML) . In the XML, you're looking for the address block below your rom file, add to the end of it before the /> multifunction='on' <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/vm/Gigabyte.GT610.1024.130107.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> should be <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/vm/Gigabyte.GT610.1024.130107.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> Do you need the built in VNC? I've found having it as a device causes problems for my VMs with real GPUs occasionally.

I've had random SMB issues like this before, especially dealing with specific hardware / software combos. Can you try to make another unraid user with read access to the media share?

AVAHI is harder than it seems to get running on some containers, at least with the tiny bit I played with it. Sucks but what can you do. Sort of related, a docker that can essentially act as an internal reverse proxy that supports broadcasting a bunch of .local mDNS domains and then routing said requests would be absurdly useful. Does that exist?

Going to test.domain.nl (ignoring the :123) doesn't work?

Kernel 5.19.3 + Mesa drivers from ppa:oibaf/graphics-drivers seems to work with the newest ubuntu LTS at least provisionally. Haven't tested anything heavy but my screen works and apparently I have hw accel. If you're trying to get this to work, try this. Install Ubuntu in GPU safe mode with just the VNC passed. Get it installed and do the kernel upgrade + mesa drivers. Then pass your GPU + HDMI audio, manually adding in multifunction. As a bonus, edit grub to allow the menu display by default, this will give you an easy road back in to 'recovery' / cli mode if a change breaks your GPU. Can't get both mouse and keyboard passed (either by doing the GUI config, and then re-editing the xml) and ALSO have display show up no idea why? I get conflicts over ports and stuff. Mouse and Keyboard sucessfully passed to other VMs however. It's not a *massive* deal since I don't plan on having physical HID devices connected in the long run. RealVNC server is my choice for control with a passed through GPU. Install it, then "libcanberra-gtk-module" (for some reason it's missing for me after these steps) , then configure it, then disable Wayland. Wayland presents major issues for RealVNC and on the KB+M control front (like synergy / barrier) there isn't a decent option yet. EDIT: Correct Kernel is 5.19.3 sorry for the confusion. https://github.com/pimlie/ubuntu-mainline-kernel.sh is what I used. You're probably better to do it yourself but this worked for me. Uniengine benchmarking works. GPU still shows up as a non specific AMD device in lshw but presents correctly to software I guess? Driver: amdgpu OpenGL 4.6 OS: Ubuntu 22.04.1 LTS Kernel: 5.19.3-051903-generic

pci=noaer works *more*, the 6500xt has a problem on Ubuntu but I'm getting closer. https://gitlab.freedesktop.org/drm/amd/-/issues/1933 Displays the exact error as this. Working on it now to see what I can do on a newer kernel / mesa version I assume this is beyond the Unraid community's help but do let me know if there's another option.

I should have mentioned unsafe interrupts, already have those on. I haven't tried pci=noaer though.

Alright, I've been trying for 2 days now to get my 6500XT passed through to VMs successfully (and reliably). I've tried various fixes like multifunction, hiding the relevant devices from VFIO, etc. Tried 6.9 and now 6.10 . I've been able to get video out of the GPU to boot specific OSes (Debian 11 worked for example, but no hardware acceleration) and occasionally I've been able to get it to show up in LSPCI in said VM. I've dumped the bios on an actual windows machine as well, the card does indeed work. I figured okay, Ubuntu LTS has AMD driver support so I'll try that. VM boots, and gives me ubuntu's boot options (through the GPU's video out), however hitting "try / install" causes a VFIO error which leaves the screen on "Tianocore" (the last frame is always left hanging on the GPU's output). Doing safemode, I obviously get further but that isn't going to really help my situation as the notification I get as safemode launches is that the AMD drivers won't be loaded. qemu-system-x86_64: vfio_err_notifier_handler(0000:05:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest qemu-system-x86_64: vfio_err_notifier_handler(0000:05:00.1) Unrecoverable error detected. Please collect any data possible and then kill the guest What else can I try? I can post VM configs but I've tried a bunch of different ones by this point. Also, curiously, there's 4 relevant devices for my GPU in VFIO, but only 2 have little check boxes. I did attempt to add the remaining 2 manually (following the style of the 2 which I was able to enable via the GUI) to my vfio config file but it didn't make a difference. First 2 here, the "Upstream" and "Downstream" have no checkbox. IOMMU group 31:[1002:1478] 03:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev c1) IOMMU group 32:[1002:1479] 04:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch IOMMU group 33: [1002:743f] 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400 / 6500 XT] (rev c1) IOMMU group 34: [1002:ab28] 05:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller Is it possible I need to write the xml config for the VM to include the first 2 devices? How would that look? X99 Jingyue board if that helps. 12c V3 Xeon. This isn't my primary GPU (I have an old AMD card in there and it seems to only output console to that, not the 6500xt so I believe Unraid's OS is correctly preferring the crappy card)

I guess theres some 12TB externals on sale, I'll grab one. I wonder if its even worth it to waste my time repairing it? I'll probably try to mount it on another machine (there's some software which claims it'll let me browse an unmountable xfs disk) just to make sure there isn't anything terribly important on there but I doubt it.

smartctl -a /dev/sdp smartctl 7.1 2019-12-30 r5022 [x86_64-linux-4.19.107-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda Compute Device Model: ST8000DM004-2CX188 Serial Number: ZCT1C93J LU WWN Device Id: 5 000c50 0c33b4041 Firmware Version: 0001 User Capacity: 8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5425 rpm Form Factor: 3.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Wed Oct 7 09:30:08 2020 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED See vendor-specific Attribute list for marginal Attributes. General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 0) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: (1004) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x30a5) SCT Status supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 074 053 006 Pre-fail Always - 118910377 3 Spin_Up_Time 0x0003 092 091 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 436 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 083 061 045 Pre-fail Always - 197121477 9 Power_On_Hours 0x0032 093 093 000 Old_age Always - 6622 (10 66 0) 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 105 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 023 023 000 Old_age Always - 77 188 Command_Timeout 0x0032 100 018 000 Old_age Always - 1643755 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 061 039 040 Old_age Always In_the_past 39 (Min/Max 31/41 #1) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 169 193 Load_Cycle_Count 0x0032 097 097 000 Old_age Always - 6768 194 Temperature_Celsius 0x0022 039 061 000 Old_age Always - 39 (0 20 0 0 0) 195 Hardware_ECC_Recovered 0x001a 081 064 000 Old_age Always - 118910377 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 24 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 24 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 4455 (233 194 0) 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 130086748120 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 192229983405 SMART Error Log Version: 1 ATA Error Count: 72 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 72 occurred at disk power-on lifetime: 6621 hours (275 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 ff ff ff 4f 00 17:30:47.161 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 17:30:47.120 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 17:30:47.120 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 17:30:47.120 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 17:30:47.119 READ FPDMA QUEUED Error 71 occurred at disk power-on lifetime: 6621 hours (275 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 ff ff ff 4f 00 17:30:11.115 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 17:30:11.102 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 17:30:11.090 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 17:30:11.074 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 17:30:11.055 READ FPDMA QUEUED Error 70 occurred at disk power-on lifetime: 6620 hours (275 days + 20 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 ff ff ff 4f 00 16:50:14.086 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 16:50:14.046 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 16:50:14.045 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 16:50:14.045 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 16:50:14.045 READ FPDMA QUEUED Error 69 occurred at disk power-on lifetime: 6620 hours (275 days + 20 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 ff ff ff 4f 00 16:49:37.963 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 16:49:37.951 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 16:49:37.939 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 16:49:37.922 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 16:49:37.904 READ FPDMA QUEUED Error 68 occurred at disk power-on lifetime: 6610 hours (275 days + 10 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 05:57:40.379 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 05:57:40.372 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 05:57:40.366 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 05:57:22.568 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 05:57:22.561 READ FPDMA QUEUED SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 778 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. So there are some errors lol I mean I don't want to retire it since I frankly dont give a fuck about the data on the drives as long as theres nothing under 24 hours old that gets lost (all my shit backs up to GSuite) but that is kind of worrisome.

Hey, I had an unclean shutdown due to a power outage and an 8TB XFS disk I use with unassigned devices and mergerfs refuses to mount. Yesterday I ran xfs_repair on it and eventually after scanning I got Sorry, could not find valid secondary superblock Exiting now. Mounting throws these errors into the log Oct 7 08:58:42 Tower kernel: XFS (sdp1): log mount/recovery failed: error -117 Oct 7 08:58:42 Tower kernel: XFS (sdp1): log mount failed Oct 7 08:58:42 Tower unassigned.devices: Mount of '/dev/sdp1' failed. Error message: mount: /mnt/disks/media36: mount(2) system call failed: Structure needs cleaning. Oct 7 08:58:42 Tower unassigned.devices: Partition 'ST8000DM004-2CX188_ZCT1C93J' could not be mounted. Running the file system check from webgui returns something like FS: xfs /sbin/xfs_repair -n /dev/sdp1 2>&1 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_ifree 3094, counted 3087 sb_fdblocks 266597848, counted 271434282 - 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 imap claims a free inode 119939202 is in use, would correct imap and clear inode - agno = 1 - agno = 2 Metadata CRC error detected at 0x45c2d9, xfs_dir3_data block 0x1802bbfe0/0x1000 bad directory block magic # 0x241a9c92 in block 10 for directory inode 4294967424 corrupt block 10 in directory inode 4294967424 would junk block Metadata corruption detected at 0x435c33, xfs_inode block 0x1802bbfe8/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x1802bc008/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x1802bc028/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x1802bc048/0x4000 - agno = 3 bad CRC for inode 6445318144 bad magic number 0x241a on inode 6445318144 bad version number 0x6d on inode 6445318144 inode identifier 1575615604729810958 mismatch on inode 6445318144 bad CRC for inode 6445318145 bad magic number 0x241a on inode 6445318145 bad version number 0x6d on inode 6445318145 inode identifier 1575615604729810958 mismatch on inode 6445318145 bad CRC for inode 6445318146 bad magic number 0x241a on inode 6445318146 bad version number 0x6d on inode 6445318146 inode identifier 1575615604729810958 mismatch on inode 6445318146 bad CRC for inode 6445318147 bad magic number 0x241a on inode 6445318147 bad version number 0x6d on inode 6445318147 inode identifier 1575615604729810958 mismatch on inode 6445318147 bad CRC for inode 6445318148 bad magic number 0x241a on inode 6445318148 bad version number 0x6d on inode 6445318148 inode identifier 1575615604729810958 mismatch on inode 6445318148 bad CRC for inode 6445318149 bad magic number 0x241a on inode 6445318149 bad version number 0x6d on inode 6445318149 inode identifier 1575615604729810958 mismatch on inode 6445318149 bad CRC for inode 6445318150 bad magic number 0x241a on inode 6445318150 bad version number 0x6d on inode 6445318150 Eventually leading to xfs_repair: read failed: Input/output error bad magic # 0 in inode 8594108579 (data fork) bmbt block 887796852 bad data fork in inode 8594108579 would have cleared inode 8594108579 bad nblocks 4162550 for inode 8595177059, would reset to 4162374 bad nblocks 4022773 for inode 8595177060, would reset to 4022594 - agno = 5 - agno = 6 What are my options? Id love to figure out a way to repair it without losing the data on it and not needing to pull it. Barring that I guess its pull the disk, buy another 8TB and try to copy the data or just wipe it and start fresh? I'd lose a bunch of torrents but I'm pretty sure it's just all long term seed stuff I have cloud backups of obviously.

I'm at 57% full. Anyone know what command would be best to run that would exclude anything in /mnt and I guess any other folders (like maybe /var/lib/docker (I don't think that's on the virtual filesystem right?) ? Thanks

Yep. This is my problem. If it filled up quickly, I could probably pin things down. Also okay I can do that. Out of curiosity, say I catch it at like 90% full, is there a command I could run to see what the largest files on this unmounted storage are, I just don't know which directories to exclude and stuff? P.s. all dockers seem to function correctly when this happens. It's only the web interface that freaks out