public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hard drive change
Date: Mon, 12 Nov 2012 12:14:55 +0000	[thread overview]
Message-ID: <201211121215.21425.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20121108194601.57d11af6@echoes>

[-- Attachment #1: Type: Text/Plain, Size: 1476 bytes --]

On Thursday 08 Nov 2012 19:46:01 john wrote:
> On Thu, 08 Nov 2012 19:17:25 +0100
> 
> Florian Philipp <lists@binarywings.net> wrote:
> > Am 08.11.2012 17:37, schrieb Paul Hartman:
> > > On Thu, Nov 8, 2012 at 7:03 AM, Volker Armin Hemmann
> > > 
> > > <volkerarmin@googlemail.com> wrote:
> > >> Am 08.11.2012 12:12 schrieb <jdm@jdm.myzen.co.uk>:
> > >>> I am about to change my hard drive on my machine from a 500GB to
> > >>> 2tb.
> > >>> 
> > >>> To transfer I  intend to dd the partitions across and then resize
> > >>> using lvm as home swap var are located on lvm.
> > >>> 
> > >>> Is this the right approach or would you recommend another method?
> > >>> 
> > >>> John D Maunder.
> > >> 
> > >> 2tb drive  probably different sector size. cp -auv recommended.
> > > 
> > > I agree, best approach is to partition and format the new drive as
> > > new, and then copy the files. This will also help you start your new
> > > disk with a lack of fragmentation.
> > 
> > +1
> > 
> > Of course, a simple cp -auv /* /new_root won't suffice because of
> > proc, sys and friends. I prefer
> > mount --bind / /real_root
> > cp -auv /real_root/* /new_root
> > 
> > Regards,
> > Florian Philipp
> 
> Thanks all for advice. Nice work with the mounting.

I often use star with the -copy option (faster and more advanced than tar, 
although I have not timed it), or rsync.  dd and friends for iso copying and 
fs recovery.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-11-12 12:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-08 11:08 [gentoo-user] Hard drive change jdm
2012-11-08 11:51 ` Neil Bothwick
2012-11-08 13:03 ` Volker Armin Hemmann
2012-11-08 14:12   ` Srdjan Rakic
2012-11-08 15:23     ` mindrunner
2012-11-08 15:37       ` Neil Bothwick
2012-11-08 18:33         ` mindrunner
2012-11-08 20:37       ` Volker Armin Hemmann
2012-11-09 12:00         ` mindrunner
2012-11-09 12:25           ` Bruce Hill
2012-11-09 13:56           ` Mark Knecht
2012-11-09 14:37             ` Bruce Hill
2012-11-13 21:10             ` Lukas Elsner
2012-11-09 14:00           ` Philip Webb
2012-11-09 15:07             ` Bruce Hill
     [not found]         ` <509C5091.4040903@ccube.de>
2012-11-09 15:14           ` Volker Armin Hemmann
2012-11-09 15:40             ` Bruce Hill
2012-11-09 17:56             ` Chris Walters
2012-11-08 15:10   ` Neil Bothwick
2012-11-08 16:37   ` Paul Hartman
2012-11-08 18:17     ` Florian Philipp
2012-11-08 19:46       ` john
2012-11-12 12:14         ` Mick [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-11-08 12:08 jdm

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=201211121215.21425.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --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