• 0 Posts
  • 77 Comments
Joined 3 years ago
cake
Cake day: July 4th, 2023

help-circle


  • I used to do this as well, and tell Linux to never overcommit, but for a desktop system normal programs are not built for this scenario. Firefox will crash with 15% system ram usage because it requests a ton of virtual memory for each process on startup.

    Swap can also be important if you want to get the most out of your ram because without swap, pages that are holding unimportant parts of the system can’t move out of the way for a large number of data pages that need processing. My latest memory revelation is zswap, which seems to be better than actual compressed memory. So far it’s served me well running ML loads on old hardware.







  • Afaik, those by-* paths are symlinks created by udev during boot (before switching to the real root fs) The kernel creates the actual device files directly in /dev. My guess is that Windows left an NTFS volume in an unmountable state or something and udev got stuck processing this disk before processing rules for your boot disk. This probably requires you to have a fstab entry for mounting your windows disk, but I’m not sure.

    When you boot into a live distro again (I know you’re done, but maybe someone else has this problem) check if the disk has a block device file directly in /dev. Maybe check the other disk, see if you can mount it or remove references to it in fstab or unplug the device entirely.


  • Totally unrelated, but I just want to say that my 14 TB sas drive (exos?) was brought back to life in a 12 TB configuration after failure by using openseachest to deactivate one side of one of the platters (the failing one, it was the only one with errors) after I told it to start it took 4 days to reformat, most of that time reporting no progress, but finally finished and now it works great!



  • The easy thing is to just format them ext4 and use them as extra data storage.

    Edit 2: don’t delete the efi partition!!! Unless you want to learn how to rebuild it :) unless you’re using Windows boot manager you can remove the Microsoft folder from the efi partition as well

    The good news is your system partition is small so you can delete the first two partitions. Make a small boot partition if you want, make a new system partition second ( bigger than your current one), copy the existing system partition into the new one (without deleting the old one), boot into the new system partition, test that it works, then expand the fs to fill the partition. Then you can move your home partition if you want or just make your system partition huge to fill the space up to your existing home partition, then delete the last partitions an grow your home partition to fill the disk

    Edit: once you know the new system partition works you delete the old one.