alucarddelta

So I after unknowingly living on the max drive limit for Unraid Plus, I was forced to get a new drive as my array was at 97%. When I installed the new Drives (had to upgrade the parity drive at the same time) I was greeted with this msg. "Too many attached devices. Please consider upgrading your registration key." I don't know about everyone else, but I didn't even think about it, and I just forked over the money for the Pro key upgrade. Unraid has done me well since I switched over from using Synology a few years back and I don't intend on going back. I was happy to support the devs of unraid instead of trying to use freenas or try and build my own clone gone wrong version of unraid with ubuntu. Just wanted to say Thanks Unraid Team and Community!

Hi, A few weeks ago I posted this where my system would lock up. Turns out it was hardware as now my system will no longer post. I have a few questions has my new hardware has rocked up and I would like to get it up and running with the least amount of headaches. I am going from a C2750D4I to a Asus Prime Z370-A/ Intel CPU Core i5 (8 series) with a raid Card (9217-8i) for the extra Sata ports build. (extra RAM is also being installed) 1. As a fix attempt I had started an upgrade ,and I was doing the reboot when the system did not recover. Should I have any issues with the upgrade as I am switching hardware mid upgrade. 2. Im switching from build in Sata ports to a raid card. Should I have any issues with hard drives with the switch of systems. 3. If I do have to start from scratch, Will my current unraid lic be ok or will I need to buy a new one cause of the system change and being unable to recover the old setting for what ever reason.

Ok I have disabled Logging, and I have found that post form RobJ, Cheers for the help

Hey, My I have been moving some files around with MC and using the cache mover which created a lot of logs in Syslog. Reading though it all I have confirmed that it there is no errors and its just the moving of files that is creating the large file size. Is there any harm in running following command to zero out the file? or should I just keep increasing the log size (currently at 384~mb) cat /dev/null > syslog