hendeeze

I am having an issue with my parity crashing following upgrading my discs. Previously, I had 13 drives driven by an HBA, I've consolidated those 13 drives to 5 drives run off onboard sata. During the data transfer I had both the HBA and onboard sata all populated. Using unbalance to move over my files to my new discs. This took forever (about 3 weeks), during which time everything ran smoothly. Now that the data is on the new drives, I followed the disc upgrade process and parity syncing the new discs for the first time. I've had several crashes during this time, where my unraid would hang and would be unreachable via IP or GUI and since these are large discs the parity never completed. First I thought it may be heat, so I ran incremental parity syncs by running 2-4 hours at a time, and pausing for 2 hours at a time to let the chipset cool down. Even pointed a room fan at the MB directly. Got to about 75% and it crashed overnight. When I did the data transfer I didn't have any external cooling source and it ran fine. The only hardware change other than the HDD's would be swapping from HBA to onboard sata. (Previously I used these onboard sata to run unassigned devices without issue) Bios, unraid version etc are all the same as the previous configuration. Included is my diagnostic files. Any help would be appreciated. tower-diagnostics-20260124-1421.zip

I am having trouble linking prowlarr to a deluge instance on my seedbox. Using the same settings as my sonarr/radarr on my local device prowlarr (local) refuses to connect. I am getting "Failed to test connection: Not authenticated (code 1) errors in the log". Any ideas?

I believe this happened after an unclean shutdown. The result of the error is I am unable to write to my dockerfile and thus unable to upgrade apps. Looking through the log it says something about a csum error and elsewhere a btrfs error any idea where to start? tower-diagnostics-20220909-0652.zip

@InVisibleGoD did you change the resolution in the bios and hardstop it after to make it stick?

@1812 ya might want to remove it from your quote as well @RSQtech wait for the prompt and type exit. then change the resolution as per SIO's video. Force stop the VM and then hit exit again when at the prompt but this time load the clover volume in the boot options. edit: actually you need to change the type='raw' to 'qcow2' <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/MacOS Mojave/clover.qcow2'/> <target dev='hdc' bus='sata'/> and also like @1812 said change 'virtio' to 'vmxnet3' </controller> <interface type='bridge'> <mac address='52:54:00:9b:26:09'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface>

ok I see makes sense, maybe they changed something in the update. Formally I was able to run the webui from my portrait monitor and the ui would be max width. Now however I get that annoying horizontal scroll.

I thought so too when I did it, however I've rebooted several times and its still sticking?

Allow unRaid's webUI to utilize the full width of your browser instead of being limited to 1920px #!/bin/bash sed -i 's/max-width:1920px;//g' /usr/local/emhttp/plugins/dynamix/styles/*.css i typed that into terminal and i just wanted to reverse it

thats the only complete content in my /boot/config/go file nothing with sed in it.

this is the contents of my go file #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & if i comment out the /usr/ line the webui doesnt come up.

How would I go about reversing this?