public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: tuxic@posteo.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Copying root to SSD in one go...a good idea...or?
Date: Sun, 5 Apr 2020 20:39:37 +0200	[thread overview]
Message-ID: <20200405183937.y556nlxrlzn34ugf@solfire> (raw)
In-Reply-To: <c2d73b97-a22f-d631-4749-41b2b805fd82@gmail.com>

On 04/05 01:08, Dale wrote:
> tuxic@posteo.de wrote:
> > On 04/05 10:33, Mark Knecht wrote:
> >> On Sun, Apr 5, 2020 at 10:13 AM <tuxic@posteo.de> wrote:
> >>> Hi,
> >>>
> >>> currentlu I am preparing a new Gentoo Linux by compiling all
> >>> the application I had on my old system.
> >>>
> >>> Due to delivery problems (corona) my SSD was delivered today
> >>> (or yesterday...it depends...;) .
> >>>
> >>> When the whole compilation has finished and the system boots it
> >>> needs to be transfered to the SSD.
> >>>
> >>> The SSD has a heat spreader...so it gets hot, when used.
> >>>
> >>> Is it wise to copy the whole root system to the SSD in one go
> >>> in respect to a not so healthy heat increase?
> >>>
> >>> And if not...how can I copy the root system in portions
> >>> to the SSD and do not miss anything?
> >>>
> >>> Are there SDD-friendly and SSD-unfriendlu methods of copying
> >>> greater chunks of data to a SSD (rsync, tar-pipe, cp....)?
> >>> What is recommended here?
> >>>
> >>> Thanks a lot for any help for a SSD newbie in advance!
> >>>
> >>> Cheers! And stay heathy!
> >>> Meino
> >>>
> >> Just my 2 cents...
> >>
> >> If the SSD cannot survive having data copied to it there's something
> >> seriously wrong with the drive. I don't think you should be overly worried
> >> about this but I do understand it's new technology so you want to be
> >> careful. Bravo for that.
> >>
> >> Possibly to ease your concerns a little bit use smartctl -a /dev/SSD and
> >> get to know your drive that way. You can most likely watch the drive temp
> >> as recorded by the drive.
> >>
> >> Best wishes,
> >> Mark
> > Hi Mark,
> >
> > Yes, if a SSD could not survive writes, something is wrong with the
> > SSD. But that was not my point.
> > Copying about 100GB (roughly guessed) data in one go to the SSD is a
> > use case, which is not common. And therefore possibly not taken into
> > account by the company, which create that SSD.
> > SSDs can create noticeable heat (mine has a minimalistic heat
> > spreader therefore. Faster SSDs come with a substancial heatspreader).
> >
> > Smartctl will report problems when they are already there.
> > I want to prevent problems beforehand.
> >
> > So -- does copying about 100 GB creates so much heat in the sillicone
> > of the SSD, that it ages more than preferred?
> >
> > And if so, how can I prevent it by appluing other techniques to copy
> > the data? 
> > See additional questions in my initial posting for that.
> >
> > Thanks a lot for any helpful advice in advance!
> > Cheers!
> > Meino
> >
> 
> If you are using rsync or cp -u you could start the copy then stop at it
> certain points to let the SSD cool, then start it again.  It will
> basically pick up where it left off.  You could monitor the temps while
> doing that.  I use smartctrl and then grep temp on the end so I only get
> the temp readings.  Something similar to this might help:
> 
> 
> smartctl -a /dev/sdd | grep Temp
> 
> 
> Another option, temporarily place a fan close to the drive to help cool
> it.  Once you get everything copied, remove the fan and carry on. 
> 
> Dale
> 
> :-)  :-) 
> 

Hi Dale,

I have become a fan of your idea with the fan... :)

Yes, of course! Great...after uears of thinking on software
level such things, which provide a solution, which exists in
the phusical world does not pop up in my head...

Will do that! :)
Cheers!
Meino



  parent reply	other threads:[~2020-04-05 18:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-05 17:12 [gentoo-user] Copying root to SSD in one go...a good idea...or? tuxic
2020-04-05 17:33 ` Mark Knecht
2020-04-05 17:54   ` tuxic
2020-04-05 18:08     ` Dale
2020-04-05 18:29       ` Neil Bothwick
2020-04-05 19:09         ` Dale
2020-04-05 19:28           ` Neil Bothwick
2020-04-05 19:43             ` Dale
2020-04-05 18:39       ` tuxic [this message]
2020-04-05 19:19         ` Dale
2020-04-05 18:12     ` Mark Knecht
2020-04-05 18:37       ` tuxic
2020-04-05 19:25         ` Dale
2020-04-05 19:29         ` Neil Bothwick
2020-04-05 20:05       ` [gentoo-user] " Grant Edwards
2020-04-05 18:22     ` [gentoo-user] " Michael
2020-04-05 19:03       ` tuxic
2020-04-05 19:31         ` Neil Bothwick
2020-04-05 18:41 ` J. Roeleveld
2020-04-05 20:12   ` tuxic
2020-04-06  6:06 ` William Kenworthy
2020-04-06 13:35   ` [gentoo-user] " Grant Edwards
2020-04-06 14:19     ` Jack
2020-04-06 14:34       ` Grant Edwards

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200405183937.y556nlxrlzn34ugf@solfire \
    --to=tuxic@posteo.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox