Cor4eyh

This is what I'm seeing so far.

It's been going for a few minutes I will let it run.

I assume thats by clicking the check filesystem button next to the unassigned drive correct? How long does that take? It's going currently waiting for a finish to post the results.

While I was worried about the format I have disk 4 attached it’s just needing a file system repair. I attempted fixed without going into maintenance mode with no success yet. I know I made mistakes here and I’ll accept my own faults for that. In the future things will go differently. I still have the drive it appears to still power on and show it’s connected just unable to mount it in unassigned

I do have the old disk it’s intact and attached as an unassigned device that’s unmountable. Currently parity is rebuilding parity due to the parity disk error. Should I stop parity. I will only have 1 parity drive at the moment. And try maintenance mode to repair the unassigned disk 4 file system?

I tried to run check filesystem with unassigned and got that photo back of the drive. When starting the array it said a drive was unmount able format to continue. Since I have disk 4 and it’s still attached I clicked yes to format. Then saw it format disk 4. Would maintance mode help with unassigned disk 4? I tried to mount and get an error. If I could mount disk 4 I could put its contents back in the array.

Disk 4 was nearly full. At least I think so. I can’t answer if it was. When I click on disk 4’s contents via Krusader it has 2 folders with nothing in them. wierd that emulation would save 2 folders but not the other data correct? I have disk 4 still attached but in unassigned devices because it has data on it. I cannot mount disk 4 through maintenance the screen shot is of disk 4’s log. What should I do to mount that drive and hopefully save the data?

They are after shut down and start up with drives back to normal. I’m in normal mode.

This is the current mission disk. It’s in unassigned devices. I cannot mount it. I am attempting xfs_repair to fix the file system. Anything else I can do? The data that was on this disk in the array was being emulated. When the parity had errors it began to rebuild without disk 4 now there is no data on disk4 that data is sitting on the errored drive and unable to be rebuilt by parity since it doesn’t exist. New diagnostics attached tower-diagnostics-20260414-0041.zip

I wouldn't have restarted the array if things weren't working well. Just seems coincidental the timing to a drive that was bad being replaced to potentially some cables being bad as well. Just wondering if I should let the parity finish before installing new cables and such hoping some of the issues will go away. Like the one parity with errors. Its still plugged in and saying there's no errors using SMART Any directions?

I forgot to mention in my post that everything was Gucci after installing the replacement drive. Upon finishing rebuild the second drive failed. I thought it was a bit crazy but not unheard of multiple drives failing. Yes I’m using some splitters but following max power limits of each line from the PSU. Definitely under max power limits. But the splitter is used for length more than extra power. I have 3 separate lines coming out and one of them has a splitter for power to extend it. Also want to mention it’s been this way for 4 years working just fine. Not saying that nothing can go wrong.

Here are the diags tower-diagnostics-20260413-1105.zip

Couple of days ago I replaced a drive that had errors. I had to remove all the drives to get to the 1 drive so that meant moving cables sata and power cables a bit. Nothing crazy. I installed the new disk and began to rebuild it. As it started another disk had shown errors. I waited for the rebuild to finish and once it finished my parity drive began to show errors. After some googling I'm guessing I have a cable issue meaning some cables may have been damaged or something during the moving. I am awaiting new cables but at the moment one parity drive is working the second has errors the drive that second drive that needed to be replaced I tried it in another pc just to check the drive seems fine. I didn't want to format it because of the parity failure. Now parity is rebuilding but without a drive. So -1 Parity drive -1 data drive 2nd parity drive is rebuilding. Ordered new cables for the hba card and some new power cables. Also have another drive on the way for the last data drive. Looking for suggestions of operations here. Parity should be done in 2 days. Should I wait for parity to finish? I'm wondering if that missing disk is still being emulated. I have the missing disk and it has data on it so I may not be totally screwed. Should I stop the parity and shut down and fix all the cables and see if I get no errors back? Thank you for any and all info.

I followed @SpaceInvaderOne video to the t everything. And didn’t see an option or easy way to use a bare metal ssd to install on. It only installs on the array correct? im also having some trouble reinstalling after fixing/messing up XML files. Im getting an error when it downloads macOS onto the purposed 500g hdd I used in the template. my system is a i9 9900 non k with 64gb ram a 6600xt and hoping to utilize all of that pretty well. if I can get Mac to run I sometimes have issue without passing through the video card that my onboard video is very low so the whole MacOS system runs super slow. anyone who’s playing with this as well feel free to assist. If not I will edit this as I continue to learn and figure it out and leave the information for the next person. I also read the article tips for baremetal macOS. I didn’t see any best bios for hackintoshish. thank you for any help and hopefully I solve all the problems on my own ;)

The only thing I havent tried is the Vbios. Does the config look ok though? these last lines appear wether i use vnc or video card I'm using an rx 6600xt. Its a 9900 non k as well. 2022-06-21 21:13:00.858+0000: starting up libvirt version: 8.2.0, qemu version: 6.2.0, kernel: 5.15.46-Unraid, hostname: StreamingMACPC LC_ALL=C \ PATH=/bin:/sbin:/usr/bin:/usr/sbin \ HOME='/var/lib/libvirt/qemu/domain-1-Macinabox BigSur' \ XDG_DATA_HOME='/var/lib/libvirt/qemu/domain-1-Macinabox BigSur/.local/share' \ XDG_CACHE_HOME='/var/lib/libvirt/qemu/domain-1-Macinabox BigSur/.cache' \ XDG_CONFIG_HOME='/var/lib/libvirt/qemu/domain-1-Macinabox BigSur/.config' \ /usr/local/sbin/qemu \ -name 'guest=Macinabox BigSur,debug-threads=on' \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-1-Macinabox BigSur/master-key.aes"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ -blockdev '{"driver":"file","filename":"/etc/libvirt/qemu/nvram/b73727e7-8fb6-49ef-91b9-a5ab62b8c222_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}' \ -machine pc-q35-4.2,usb=off,dump-guest-core=off,mem-merge=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format,memory-backend=pc.ram \ -accel kvm \ -cpu host,migratable=on,host-cache-info=on,l3-cache=off \ -m 24064 \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":25232932864}' \ -overcommit mem-lock=off \ -smp 8,sockets=1,dies=1,cores=4,threads=2 \ -uuid b73727e7-8fb6-49ef-91b9-a5ab62b8c222 \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=36,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=utc,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device pcie-root-port,port=16,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \ -device pcie-root-port,port=17,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \ -device pcie-root-port,port=18,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \ -device pcie-root-port,port=19,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \ -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Macinabox BigSur/macos_disk.img","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-1-storage"}' \ -device ide-hd,bus=ide.2,drive=libvirt-1-format,id=sata0-0-2,bootindex=1,write-cache=on \ -netdev tap,fd=37,id=hostnet0,vhost=on,vhostfd=39 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:68:03:51,bus=pci.1,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0,index=0 \ -chardev socket,id=charchannel0,fd=35,server=on,wait=off \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -audiodev '{"id":"audio1","driver":"none"}' \ -device vfio-pci,host=0000:03:00.0,id=hostdev0,bus=pci.3,addr=0x0 \ -device usb-host,hostdevice=/dev/bus/usb/001/004,id=hostdev1,bus=usb.0,port=2 \ -device usb-host,hostdevice=/dev/bus/usb/001/007,id=hostdev2,bus=usb.0,port=3 \ -device usb-host,hostdevice=/dev/bus/usb/001/009,id=hostdev3,bus=usb.0,port=4 \ -usb \ -device usb-kbd,bus=usb-bus.0 \ -device '************************' \ -smbios type=2 \ -cpu Penryn,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+avx2,+aes,+fma,+fma4,+bmi1,+bmi2,+xsave,+xsaveopt,+rdrand,check \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/0 (label charserial0) 2022-06-21T21:13:01.008331Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2022-06-21T21:13:01.009064Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2022-06-21T21:13:01.009556Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2022-06-21T21:13:01.010095Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2022-06-21T21:13:01.010602Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2022-06-21T21:13:01.011134Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2022-06-21T21:13:01.011652Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2022-06-21T21:13:01.012206Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2022-06-21T21:13:02.697948Z qemu-system-x86_64: vfio: Cannot reset device 0000:03:00.0, depends on group 14 which is not owned. 2022-06-21T21:13:02.701920Z qemu-system-x86_64: vfio: Cannot reset device 0000:03:00.0, depends on group 14 which is not owned. 2022-06-21T21:13:59.852969Z qemu-system-x86_64: terminating on signal 15 from pid 3234 (/usr/sbin/libvirtd) 2022-06-21 21:14:02.655+0000: shutting down, reason=destroyed