Struck
Members
-
Joined
-
Last visited
-
Finished upgrading 7.1.4 to 7.2.0. Seems to be running fine. however after the reboot it started a parity sync, for some reason.
-
I have a server that has given me some problems past few weeks with hard lockups of various degrees. This morning, it happened again, but not a full lockup. I could still access parts of the webui, terminal, and I saw some of the dockers still running in the active processes, but samba shares did not work. If I opened a terminal and wanted to list the /mnt directory, the terminal froze. After this, I tried to create the diagnostics, but it stalled halfway. And after this, the webui also did not work, but the web terminal was still awake. Here is what the screen showed when creating the diagnostics: Failure of the diagnostics creation Before rebooting, I used the web terminal to copy the incomplete diagnostics dump to a persistent location, together with the /var/syslog, as it is not included in the diagnostics dump because the dump stalled before reaching that step. Diagnostics.zip I rebooted and extracted the diagnostics shown above. Looking at the syslog, it complains about a kernel bug in btrfs Jun 13 06:01:24 Hotbox kernel: kernel BUG at fs/btrfs/ctree.c:4107! Jun 13 06:01:24 Hotbox kernel: Oops: invalid opcode: 0000 [#1] PREEMPT SMP PTIIt seems to have happened right when the docker auto update is running at 6am. Once rebooted I setup the external syslog server to hopefully catch more information when it happens again. Only 2 hours later, it stopped working again, but this time, neither webui nor SMB was working. The tower still responded to pings, and had an IP. syslog.zip I had to hard reboot the tower. This second syslog points towards some memory allocation issues, but I am not too familiar with it. Jun 13 10:11:07 Hotbox kernel: Trying to vfree() bad address (00000000846bd043) Jun 13 10:11:07 Hotbox kernel: WARNING: CPU: 6 PID: 147932 at mm/vmalloc.c:3226 remove_vm_area+0x3b/0x70Any idea what could be wrong, or how to fix it. Maybe I am facing hardware issues? Bonus information: I recently added an RTX 5070 to the server, with the 570.144 open-source driver. The card is used in the folding@home docker. I have power limited the card to 175W. The addition has put more heat and stress on the ageing hardware, but I am not sure if it's the root cause.
-
Okay. Thank you for the answer. I see forward to a new release, whenever it is ready.
-
I am having trouble updating to 2.2.0 I am still on 2.1.4 and the docker page shows that there is no update, and the docker being not available.
-
I finally got a breakthrough. I tried many different settings. But when I switched the USB Controller from 2.0 EHCI to 3.0 (qemu XHCI) It suddently appeared as a bootable device I didn't try this earlier, since i expected 2.0 to work better for boot than 3.0. Thanks for all your guys help so far
-
Cant really find anything about the USB in the Logs for the VM: Unraid Host logs tells me this:
I tried creating the USB with the manual way, of, but I still have the same error.I actually used the USB media creation tool to create the media, but altered the drive label and edited the files afterwards, Maybe this is not the way to do it. EFI folder is named as is default, when using the media creation tool.
Host is using a HP w165 usb, VM is using a Sandisk extreme USB. So different vendor and model.Using the USB Manager shown in the video. I have also tried to assign it using the normal method in the VM settings.Thanks for the informatiopn. This solved my initial problem. I followed the video, but the USB does not appear as a boot device in the VM. I edited the files on thje USB drive, and ran the make_bootable file without any problems.Hello everyone. I am trying to combine two unraid machienes I have been running. But since Unraid still does not support multiple arrays in a single install, I am trying to run the second unraid in a VM. But when i plug a new unraid USB into the already running system, the USB is not available to be assigned to a VM. As unassigned disks plugin, says the USB is "array" The Log tells me what happens: It seems like the existing unraid picks up the USB unraid, and locks the device, as it now is the active license. The USB i am using is using a new blank unraid 6.10.3 install, until i know if this would work or not. I already own the two unraid pro licenses. The host unraid system is currently running Unraid 6.9.2 I can post diagnostics, but i don't know if that would help anyway.
I realize i never replied to this topic. I tried reformattig the disk, and it seems to be working. But i later changed the filesystem to xfs, and ever since i haven't had a problem with corrupt data or full disk.Just to confirm. I don't HAVE to use a cold wallet address, for chia and alt-coins to work properly, right? My Flax farm, haven't caught any blocks for 5-6 weeks at this point. My estimated time to win is 8-10 days. But i know that is only an estimate, and should count on that. My current setup, does not use a cold address for rewards, and i have about 40 XFX already, but hasn't gained any for the last month and a half. Machinaris does not report any problems, Only have a few (0-3( skipped SP's a day. and a search time average, under 0.5s.
