Posts by Telesphoreo

    @StevenNL2000#11435 I have no idea how to. macOS Big Sur removed any hierarchy explaining how the disk works. Now it’s just a list of my partitions (or volumes or containers or however the hell APFS works)


    Edit: nevermind found it. I ran first aid on the drive itself and it reported no errors

    It says that it does not support SMART which is kind of odd if you ask me

    So I have an external WD Black drive thats 5TB. It's partitioned so that one partition is a normal APFS volume and the other is a 1TB partition for backups


    A few days after I got the drive (back in February), I got this message

    I thought it was a fluke and reformatted the drive and it worked fine. However, just earlier today, this message has come back up. There is nothing on the disk that is showing up, despite that there should be many backups


    I tried running First Aid in Disk Utility and this is what I got

    I could erase it and try it, but what's the point of having a backup disk if all the data on it is going to magically disappear. This drive is brand new, maybe a month old.


    I've never force ejected it before, I've always safely ejected it. However, the drive sometimes does make noise even after I've ejected it like stuff is still happening, but macOS showed no warnings or indications that it was still being used.


    This is what Disk Utility > Info has to say about the partition


    Any ideas?

    Quote

    @wild1145#11085 These issues are nothing to do with the bot or the scripts hanging... It's because CoreProtect being the piece of shit it is prevents a graceful shut down until all roll backs are completed, and then all data is pushed to MySQL... I've said this time and time again. That's why you have to run stop multiple times, because what ultimately happens is no different to if you ran tf!kill

    to be fair, 19.4 and 19.5 have improved performance with this significantly, and TF is still on 19.3 (I believe). you should try updating coreprotect fwiw

    @StevenNL2000#11043 that's really nice compared to namemc. not saying you're a software publisher now and are obligated to fix every little bug, but this doesn't actually work when two different people have used the same name (see PurpleGirl12500 or markbryon for example)

    @Panaghioti#11070 LTSB 2015 is by far the worst version mainly due to it being the RTM release and having many glaring performance issues and lack of security measures that were mostly introduced in 1607.


    there's literally nothing wrong with LTSC 2019. it runs really good and i've tried following those "disable these services to optimize windows" guides but they end up removing half the functionality. this is useful for a POS system or terminal, and in that case it's probably a fantastic guide. but for an average desktop person disabling random services without understanding the consequences can screw you over

    how the turntables


    i vouch mainly bc you can have one central panel to manage all the servers you have now (freedom, hub, smp, blah blah blah). eventually, it's going to become impractical to have to ssh into a bunch of different servers, make separate discord channels for separate bots, and you get the whole idea

    i vouch as i think this will make shit better


    it's unfair to say a forum software is bad and doesn't meet your needs if you don't even put in any effort to try and make it meet your needs.


    i think the most important thing we need is for wild to wake up and fix the forums being extremely slow. no one cares if it's fast for exclusively wild. other people use the forums too

    So this had nothing to do with cron. It was with the pteroq.service file. I had to change /usr/bin/php to /usr/bin/php7.4


    I also had to chown the /var/www/pterodactyl/storage to www-data:www-data. For some reason some of the files were owned by root:root and it was throwing a permission error.