said phiebie@xxxxxxx: | SSD's have a wear-levelling algorithm. That means, very very short | explained, *all* cells get written to the same amount of times and | therefore wear out evenly. Put swap on it. | But to extend the lifespan | of the SSD, don't partition the total 500GB, stop at let's say 475GB. | These 25GB can then be used by the fault-detection of the SSD to | compensate for "rotten" cells in the workspace. So, then, its spare sectors come from unpartitioned, unformatted space? | Put everything, that is executable or needed by other programs on the | SSD! Only the pure data (photos aso.) should stay on the harddrives. My plan is to put everything except /home there. I'm a little puzzled as to the partitioning map, in part because of my switch to a 6gb boot drive earlier this year, which required creation of an efi partition (which I still don't much understand). I'm hoping to create a single partition, mount it as / , and call it a day, with /home and other stuff on traditional drives. I further hope to keep my existing boot drive, but not boot from it. In the happy days of yore, it would show up on the GRUB menu at boot, so if I wanted I could boot from it. But since the switch to the bigger boot drive and upgrade to 20.04-LTS I no longer have a grub menu. Might this be because I no longer have a dual-boot system? (I nuked the XP partition because I hadn't booted to it in years.) | Maybe you find another, better solution, but I would suggest: | Make one harddrive bootable | Install on the SSD backintime with as backup-medium that harddrive | After having apt-upgraded run backintime and the harddrive should be a | mirror of the SSD. Ah. Makes sense. This would work, then, with my existing boot drive to make a good fallback, presuming I can recover my GRUB menu, no? | When you're about adjusting the fstab: don't use the old driveletters | anymore, a pita sometimes, take partition-UUID's, they stay the same | whatever you shuffle drives around. Also makes sense -- means among other things that I wouldn't need a different one for the bootable backup. Also obviates another question I had (but figured I'd figure out), which is whether a drive's physical location in the SATA system mattered in assigning drive designations. If I read you accurately, by using UUIDs this wouldn't matter (if it did to begin with -- I wasn't paying a lot of attention when we switched from IDE to SATA, and since then all I've done is replace existing drives with bigger drives). -- dep Pictures: http://www.ipernity.com/doc/depscribe/album Column: https://ofb.biz/author/dep/ ____________________________________________________ tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx
