nimble_bitz

Excellent thanks for the reply.

Is it at purchase or when activated as a key? If I buy for a buddy and he doesn't build for 6 months did he burn the time? The black Friday/Cyber Monday has me itching to get him into the hobby.

I would recommend shutting down. Double check cabling, and then restart the array and attempt parity build again. If it continues, post your diagnostics. Quick question how is your new parity attached to your motherboard? Direct to a port on the board or through a riser card or backplane?

Are any docker's using the GPU? I can't remember if the Epyc chips had integrated graphics. So if docker is using it you have to unmap that as it can't live in both worlds local to the kernel and as passthrough to a VM. If not verify passthrough in the tools> system devices and check the boxes next to the card and card audio. Reboot I think is required afterwards. Word of warning, you may not get a display until you assign to the VM and turn the VM on. IOMMU passthrough without a secondary GPU can be "weird" for lack of better words.

Remember if you swapped your USB in under 1 year you'll have to contact support for help with the key activation against the new GUID.

The squashfs is the liveusb feature (the booted USB). It's having issues writing. Dumb question when you swapped drives, did your full USB get copied over or just the config folder? Slight chance a bad interaction and more likely the flash drive.

Thank you much for the advice.

Worth the effort to swap again? I have another spare I could throw in. Was having a hell of a time getting the array up with the swapped drive due to the L2arc SSD issue. Picked less of 2 evils at the time. Protect my data or remove the SSD that croaked.

Was done through cli, drive was a dead number and ran a zpool replace zpool NUMBER sdb (as the /dev/ didn't work) Original was encrypted, not sure why this one didn't. tower-backup-diagnostics-20241127-1140.zip

So when I replaced a failed drive it resilvered however it doesn't look right. /mapper/ is missing, how did this happen and how do I correct? Relatively new to zfs even though my day job is a NAS administrator, more accustomed to WAFL.

Got it had to remove the /dev/ then it worked. Any idea how to fix the issue with the /dev/mapping/sdb1 actually being /dev/sdb ? I can make a new topic if needed, but your help is much appreciated!

Okay I got the order to change so /dev/sdg1 doesn't exist in the array as it's an assignment that can move. However I can't remove /dev/sdg1 pool: zpool state: ONLINE status: One or more devices could not be used because the label is missing or invalid. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Replace the device using 'zpool replace'. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J scan: scrub canceled on Wed Nov 27 07:04:16 2024 config: NAME STATE READ WRITE CKSUM zpool ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 sdc1 ONLINE 0 0 0 sdd1 ONLINE 0 0 0 sdb ONLINE 0 0 0 sdf1 ONLINE 0 0 0 sde1 ONLINE 0 0 0 cache sdg1 UNAVAIL 0 0 0 errors: No known data errors root@Tower-backup:~# zpool remove zpool /dev/sdg1 cannot remove /dev/sdg1: no such device in pool

Do you have an example syntax to use? Where I run into concern is this: zpool ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 sdd1 ONLINE 0 0 0 sde1 ONLINE 0 0 0 sdc ONLINE 0 0 0 sdf1 ONLINE 0 0 0 sdg1 ONLINE 0 0 0 <--- (actual array drive) cache sdg1 FAULTED 0 0 0 corrupted data (was bad ssd but it assigned to the same device number)

Created a subpool and I can't get rid of it, as the dev identified as another device when the ssd failed. Need to remove this to properly fix a device rebuild of sdc which should be sdc1 but it was brought in weird. Would love some help as I'm new to zfs. root@Tower-backup:~# zpool status -v pool: cache state: ONLINE scan: scrub canceled on Tue Nov 26 16:25:47 2024 config: NAME STATE READ WRITE CKSUM cache ONLINE 0 0 0 nvme0n1p1 ONLINE 0 0 0 errors: No known data errors pool: zpool state: ONLINE status: One or more devices could not be used because the label is missing or invalid. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Replace the device using 'zpool replace'. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J scan: scrub canceled on Wed Nov 27 07:04:16 2024 config: NAME STATE READ WRITE CKSUM zpool ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 sdd1 ONLINE 0 0 0 sde1 ONLINE 0 0 0 sdc ONLINE 0 0 0 sdf1 ONLINE 0 0 0 sdg1 ONLINE 0 0 0 cache sdg1 FAULTED 0 0 0 corrupted data

Anyone else having issues with ARC and Tone mapping hardware transcoding with 7.0 beta2? I've added in --device=/dev/dri:/dev/dri also did the Device passthrough. All other types of transcoding work and 4k works with hardware transcoding with tone mapping turned off.