PeteAsking

Does anyone know how to get a resource pack added to the server?

I did this just yesterday. First check everything is running normally and healthy. Dont do this if something is already missing or running from parity. That would sound like a badn thing to do. I also took a screenshot of the main page of all my disks so I could see what they currently were and double check them. How I did this was by turning off unraid (my array was healthy I just didnt want a disk), then removing the disk I no longer want. Unraid then boots up and does not start the array because of a missing disk. I then chose tools-new config and opted to preserve all the current disk assignments. I could then remove the disk from the new assignments. Once done I then saved that and started the array. All seemed to work fine. P

If this was very important to not lose any data one thing you might consider is cloning the bad drive to another one of identical size and then working on that cloned disk in another linux pc to try fix it. Just saying in case its like data you absolutely cannot lose.

Dont worry it was my side. Apparently you have to set the server to receive from in kiwi syslog server under the "inputs" tab. I had not used this software before so didnt know that.

I setup kiwi syslog server on a pc with IP 192.168.2.192 Checked firewall rules all ok. I set these options in unraid. Nothing ever gets to the syslog server. How is this supposed to work? Pete

Hmm, well thats kind of impossible since I use the system so I cant really leave it in safe mode for days just on the off chance it locks up again. Thanks anyway, if what I posted is not useful I will just move onto the next thing. Not every crash reported can be useful I guess. Just life, not really going to lose sleep over it. I will do the disk removal instead of worrying about this If it happens again I will try take a diagnostics right after like you suggest. Cant really do the safe mode thing though.

Oh no idea. I have never run it before yesterday. I dont even know if it is a bug with unraid beta or not thats kind of why Im asking. Also since I had to reset any logs are lost as its all run from RAM. I couldnt access anything so no way to get any logs.

Cool tnx. Any thoughts on the lockup? I mean currently unraid seems to be "fixing itself" fine so no major harm done.

Hi I had a complete lockup last night. I have been making changes to the system so will detail what I can. Yesterday I replaced 1 disk for a larger one. Process was pretty standard, stopped all dockers/vm's. Shutdown unraid. Changed disk. Started unraid - assigned replacement. Waited for rebuild. Did a parity check. Was using all my vm's etc while this happened fine through the day. No errors. Shutdown unraid again and checked it booted again fine. Did another parity check to be safe. No errors again. Created the boinc-rdp docker to use and assigned it 3GB RAM and 50% CPU. I think that was about all the changes I made. I continued using the vm's and services unraid provides during the day for a few hours and eventually went to sleep. Once I woke up all services were unavailable. Unraid could not be pinged either. On the actual console screen it showed error messages that would dump to the screen every few minutes. I could press return and login but nothing happened when I tried to type "shutdown -h now" - it accepted the command and said system is going down now! but nothing actually happened. After a few more minutes of the erros being dumped to the screen I took a photo and had to reset it. (see image). It has come back up and a parity check is now at 40% with 1 sync error found. In addition to this crash i also want to remove a disk today from the array. As I replaced a disk yesterday, I dont need this additional disk. I have copied off what was on it already to the replaced drive in the array that had enough capacity to accommodate the replaced disk and this one I want to remove now. Are the steps as follows? (taken from faq): Stop the array by pressing "Stop" on the management interface. Un-assign the drive on the Devices page, then return to the unRAID Main page. Stop array Select the 'Utils' tab Choose "New Config" Agree and create a new config Reassign all of the drives you wish to keep in the array Start the array and let parity rebuild Got to keep forging ahead despite the crashes huh? Let me know your thoughts. My fault or unraids? I do abuse the system quite a bit. I dont treat it with the respect of a maiden, I kind of just beat it with a stick until it stops working then try to not batter it so hard until its been stable for a while. I do make a lot of changes to it generally speaking, but it was working fine on the beta until last night when I changed the disk and made the new docker. I believe CPU would have averaged around 60-70% and memory would have been at about 40% all of last night (16GB system). I am now running at 93% RAM and about 80% CPU as I had to spin up a vm to do something and the parity check is running. It hasnt crashed again under this high load. Happy to hear thoughts on this and advice on removing a disk would help. P

Again you are correct. I have tried from a windows machine I also happen to have and it connects. So somehow remmina does not

@Hoopster, @testdasi. Thank you, something has improved somewhat since when I now try to connect with remmina on 33890 it (appears to) makes a connection but then immediately loses connection and reconnecting 1/20 is shown. The screen is always black and never loads anything. Is there some setting I have overlooked? It seems like something is almost there but maybe I am not 100% clear?

Hmm well it said 8080 as default and the spaceinvader video he changed it to 8097 which I also changed it to but if I connect rdp to 8097 then nothing happens?

I have setup rdp-boinc also. Is the only way to access it via a web interface / guacamole or can I rdp somehow to that port it is running on via an rdp client?

Thanks all, glad this got resolved to a workable solution.

The other guy had to use a 2.6 version of q35. Did you also do that?

Yeah thats q35. Use i440 instead.

Opnsense should be fine if you are using i440fx and seabios. What are you using?

That sucks this guy here is having issues also and we are getting stuck trying to fix his problem also. If its similar enough you could mention you are also having issues and hopefully share anything you found with each orher:

Did you try rebooting unraid and recreating the vm xml from scratch? Another guys is also having problems doing something similar on the forums currently

Ok so this is what I did, to upgrade. It wasnt too bad actually. These steps seem alright if you want a way to go back to your old setup quickly. I logged in, shut down all my VM's etc and then stopped the array. I then set the array autostart to NO (so it wont autostart). Took a backup of the flash image at this point so I had a zip just in case (I never used it). Powered off. Clonezilla from this original key to a new key. Powered up the system with the new key. Noted everything boots and is looking fine, but registration says invalid, but Unraid says I can click replace key if I want to and it will fix my key and blacklist the original USB key. As I dont want to do this yet unless I have to revert I power down the system and just put this cloned key in a draw. I can now boot it anytime and use the replace key option if I want to quickly fall back to the old 6.8.3 system. I now put the original key back in and boot. Dont start array yet, first upgrade the system to the beta image of Unraid and set array to autostart, then reboot. Now system boots with 6.9Beta1 and array starts automatically. So far I have just started my 3 VM's and checked they are working as well as a couple of dockers. I thought I may as well run a parity check so I will let that run overnight then copy some large files tomorrow to the array and see if its all working and will report back any issues. I cant really tell any difference from the limited testing so far but maybe some stuff will appear over the next few days. I did check some obvious settings here and there but they all seem exactly what I remember them being from when it was on 6.8.3 so looks like nothing obvious has changed so far. I guess I have to wait and see. Kind regards, P

Sorry I couldnt actually provide an answer. Hopefully you find a workable solution.

Is it similar to this guys issue?

Sorry man thats strange. You could always use a virtual nic in the meantime until you can fix it.

Thanks, advice has been noted. No need to tag me again.

It sounds like something someone can fix if I email them so probably if it comes to it I will just do that. Paying customer after all, so they should be able to sort out my license. Sorry but customer service is expected to a degree and dealing with a request like that is only fair.