Re: Adding an SSD
Hi,
Take note, i have the same type of disk but a 256GB variant. If you plan
on compiling software keep the 750GB disk in your system and do the
compiling from/on that disk.
If migrating a linux system i mostly copy /etc to a backup medium and
that's it. Moving /home can be done at any time.
One warning, take care with copying /etc/passwd /etc/passwd- /etc/group /
etc/group- /etc/shadow /etc/shadow- /etc/gshadow /etc/gshadow- on your
freshly installed system. This can cause annoyances and at times trouble.
For all purposes, the most important part is partitioning the disk. Make
sure the parition are aligned. This has a noticeable or even drastic
impact on performance for the better, at least it had for me. This is no
longer a worry if you plan on running and installing from Wheezy.
For sure, check out this page, yes Debian does have documentation ;-)
https://wiki.debian.org/SSDOptimization?
action=show&redirect=SSDoptimization
or check this page http://www.oxitech.info/helpdesk/tweaks.html
I attempt at dumbing down this kind of information into copy-past like
information, this page has just been started and is far from complete but
i assume it's enough to get you started.
I hope this answers some or most of your questions.
On Thu, 26 Dec 2013 12:32:58 -0500, Brad Alexander wrote:
> What is the best approach for adding an SSD to an existing system? This
> is on my desktop, with a 750GB spinning HD, and I am adding a 120GB
> Kingston ssdNow 300. Is the backup/nuke'n'pave the best or most reliable
> approach from a Debian perspective, or is there a way to partition the
> SSD and transfer the existing contents of the filesystems on the
> spinning HD to the SSD without overwriting things like the UUIDs of the
> partitions on the SSD?
> What are best practices now that SSDs (and the kernel's handling of
> SSDs)
> have theoretically gotten "better" over the last couple of years?
>
> I have paid peripheral attention to the whole SSD discussion, but not
> enough to be an expert. Then, a coworker made me a deal I couldn't pass
> up,
> so I bought it. I've been looking through articles for about the last
> bit,
> but a lot of them are from 2012 or before, and I'm wondering if they are
> out of date, and if so, how far.
>
> Finally, I plan to run encrypted partitions, with lvm containers within.
>>From what I have seen in my reading, this is not a problem for SSDs. The
> encryption layer sits above the filesystem writes, it doesn't actually
> write to the drive any more than regular writes. So the plan is, due to
> practical necessity, to have two encrypted volumes, and separate LVM
> containers within them. On the SSD, the system partitions, like /, /usr,
> /var, /tmp, /usr/local, etc. On the 750GB drive, /data, ~/.PlayOnLinux,
> /opt. I'm not sure which way to go with /home. There is plenty of room
> on the SSD for it, but I am trying to walk the line between the speed of
> the SSD and "beating it up." So any practical experience or advice from
> those who have done this would be appreciated.
>
> Thanks,
> --b <div dir="ltr"><div><div><div><div>What is the best approach for
> adding an SSD to an existing system? This is on my desktop, with a 750GB
> spinning HD, and I am adding a 120GB Kingston ssdNow 300. Is the
> backup/nuke'n'pave the best or most reliable approach from a
> Debian perspective, or is there a way to partition the SSD and transfer
> the existing contents of the filesystems on the spinning HD to the SSD
> without overwriting things like the UUIDs of the partitions on the SSD?
> What are best practices now that SSDs (and the kernel's handling of
> SSDs) have theoretically gotten "better" over the last couple
> of years?<br>
>
> <br></div>I have paid peripheral attention to the whole SSD discussion,
> but not enough to be an expert. Then, a coworker made me a deal I
> couldn't pass up, so I bought it. I've been looking through
> articles for about the last bit, but a lot of them are from 2012 or
> before, and I'm wondering if they are out of date, and if so, how
> far.<br>
>
> <br></div>Finally, I plan to run encrypted partitions, with lvm
> containers within. From what I have seen in my reading, this is not a
> problem for SSDs. The encryption layer sits above the filesystem writes,
> it doesn't actually write to the drive any more than regular writes.
> So the plan is, due to practical necessity, to have two encrypted
> volumes, and separate LVM containers within them. On the SSD, the system
> partitions, like /, /usr, /var, /tmp, /usr/local, etc. On the 750GB
> drive, /data, ~/.PlayOnLinux, /opt. I'm not sure which way to go
> with /home. There is plenty of room on the SSD for it, but I am trying
> to walk the line between the speed of the SSD and "beating it
> up." So any practical experience or advice from those who have done
> this would be appreciated.<br>
> <br></div>Thanks,<br></div>--b<br></div>
Reply to: