• 0 Posts
  • 167 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle


  • Not really with mdadm raid5. But it sounds like you like to live dangerously. You could always go the BTRFS route. Yeah, I know BTRFS Raid56 “will eat your data”, but you said it’s nothing that important anyways. There are some things to keep in mind when running BTRFS in Raid5, e.g. scrub each disk individually, use Raid1c3 for metadata for example.

    But basically, BTRFS is one of the only filesystems that allows you to add disks of any size or number, and you can convert the profile on the fly, while in use. So in this case, you could format the new disk with BTRFS as a single disk. Copy over stuff from one of your other disks, then once that disk is empty, add it as a additional device to your existing BTRFS volume. Then do the same with the last disk. Once that is done, you can run a balance convert to convert the single profile into a raid5 data profile.

    That being said, there are quite a few caveats to be aware of. Even though it’s improved a lot, BTRFS’s Raid56 implementation is still not recommended for production use. https://lore.kernel.org/linux-btrfs/20200627032414.GX10769@hungrycats.org/

    Also, I would STRONGLY recommend against connecting disks via USB. USB HD adapters are notorious for causing all kinds of issues when used in any sort of advanced setup, apart from temporary single disk usage.










  • Windows, in the past has been known to sometimes overwrite the Linux boot loader after a windows update, so be careful with that, since windows assumes no other os exists in the universe. Depending on your windows version, it might not be a bad idea to backup the license key. Recent versions store your computer’s information in the cloud, so unless you change a lot of components, it should reinstall without much hassle. But it doesn’t hurt to extract the key just in case. Microsoft gonna Microsoft. There are tools for this. E.g. jellybean key finder (or something like that).

    Depending on the distro, it might help to disable secure boot in the uefi bios.

    That being said, take it one step at a time. Don’t try to recreate everything you were doing in windows right off the bat. Get comfortable with the desktop first. Try different apps for certain tasks. If you have an Nvidia GPU, the experience can vary greatly between different distros. As others have mentioned, most distros have a “live environment” on the installation cd, which you can test to see if your hardware is recognised straight away. That being said, don’t feel like you’re married to a specific distro. Most Linux users will distro hop quite a bit, before they settle on one that just feels right. And even then they might change again after a while, if they get bored.



  • If you don’t know, or aren’t sure. Backup everything if you have the space. Once you’ve hit a couple of disaster scenarios, it will become apparent what stuff is really important.

    Obviously, the stuff you can’t recreate otherwise is most important. But apart from that, even the stuff you can recreate from other sources might be worth backing up because of time savings. E.g. faster to restore from backup than to recreate.





  • Mislabeled files, not so much. Since there isn’t really a way to verify the content until it’s downloaded. You can adjust things like which file sizes are considered a certain quality, e.g. HD or 4k. But one approach could be that you define tags for release groups which you know and trust. And give those tags a higher score. This should lead to releases by those groups being preferred.

    You can of course add multiple tags with positive and negative scores. For example I use tags to give a higher score to releases that have 5.1 audio, or which are non-hdr.