Re: [arch-general] Re-install of Arch on a larger drive

2018-03-17 Thread Ralf Mardorf
On Sun, 18 Mar 2018 04:03:41 +0100, Ralf Mardorf wrote:
>On Sat, 17 Mar 2018 18:40:33 -0400, Trey Sizemore wrote:  
>>On Sat, 2018-03-17 at 23:24 +0100, Jens John wrote:
>>> Do not reinstall but migrate your file system contents 1:1 to the
>>> new disk using rsync.
>
>Why using such an advanced tool for a simple copy?
>
>Run a Linux from a live media and simply do a
>
>  sudo cp -a /from/source/mountpoint /to/target/mountpoint
>  
>>But does the fact that I'm going from a 250GB to 500GB (and different
>>partition sized) complicate this procedure?
>
>It doesn't matter, don't confuse the copy (or any sync) command, with
>something like the dd command.
>
>Since you don't migrate to other hardware, appart from the drive, you
>even don't need to fix a graphics driver or something like that, you
>only need to reinstall the bootloader after coping all files.  

Oops, perhaps you need to fix fstab, your bootloader's config and
similar files, assuming you are one of those UUID users. If you tend to
use labels instead of UUIDs, you even don't need to fix those
files. After copying the files just use the same label for the new
partition, you used for the partition on the old drive.


Re: [arch-general] Re-install of Arch on a larger drive

2018-03-17 Thread Ralf Mardorf
On Sat, 17 Mar 2018 18:40:33 -0400, Trey Sizemore wrote:
>On Sat, 2018-03-17 at 23:24 +0100, Jens John wrote:
>> Do not reinstall but migrate your file system contents 1:1 to the
>> new disk using rsync.

Why using such an advanced tool for a simple copy?

Run a Linux from a live media and simply do a

  sudo cp -a /from/source/mountpoint /to/target/mountpoint

>But does the fact that I'm going from a 250GB to 500GB (and different
>partition sized) complicate this procedure?

It doesn't matter, don't confuse the copy (or any sync) command, with
something like the dd command.

Since you don't migrate to other hardware, appart from the drive, you
even don't need to fix a graphics driver or something like that, you
only need to reinstall the bootloader after coping all files.


Re: [arch-general] Re-install of Arch on a larger drive

2018-03-17 Thread Fons Adriaensen
On Sat, Mar 17, 2018 at 05:25:36PM -0400, Trey Sizemore via arch-general wrote:
 
> pacman -Qqe > pkglist.txt
> 
> and then on the new install, I can use the pkglist.txt generated
> previously to:
> 
> pacman -S - < pkglist.txt
> 
> In addition, by backing up and migrating much of my /home partition (to
> include 'hidden' config files, anything else I could do to make the
> process fast and as close to the current install as possible?

The trick with pkglist may work, but I never tried it.

If you do a fresh install, you can copy over you /home partition
and any others that only contain user data and nothing related
to the system.

To save some download time, and assuming your current system is
up to date, you can copy /var/cache/pacman/pkg to your new system
after the basic install (just before you do the pacman -Syu and
eventually pacman -S - < pkglist.txt).

Ciao,

-- 
FA


Re: [arch-general] Re-install of Arch on a larger drive

2018-03-17 Thread Trey Sizemore via arch-general
On Sat, 2018-03-17 at 23:24 +0100, Jens John wrote:
> On Sat, Mar 17, 2018 at 05:25:36PM -0400, Trey Sizemore via arch-
> general wrote:
> > anything else I could do to make the process fast and as close to
> > the 
> > current install as possible?
> 
> Yes. Do not reinstall but migrate your file system contents 1:1 to
> the 
> new disk using rsync. The advantage is that the file system contents
> and 
> therefore system configuration stay the same and you don't have to
> waste 
> time putting stuff together afterwards.
> 
> I used/recommend a procedure similar to [1]. The principle is
> basically 
> the same as a reinstall but instead of bootstrapping from a bare
> bones 
> system you substitute your existing file systems. I don't see any 
> benefit of doing it differently unless your existing install is
> broken 
> in some way.
> 
> The most time was taken up by copying 512G of file system contents
> over 
> a SATA<>USB3 bridge to the new SSD. If you can put both the old and
> the 
> new drive on a SATA bus, you'll be done in no time.
> 
> [1] https://wiki.archlinux.org/index.php/migrate_installation_to_new_
> hardware#Top_to_Bottom

Thanks Jens.  But does the fact that I'm going from a 250GB to 500GB
(and different partition sized) complicate this procedure?


Re: [arch-general] Re-install of Arch on a larger drive

2018-03-17 Thread Jens John

On Sat, Mar 17, 2018 at 05:25:36PM -0400, Trey Sizemore via arch-general wrote:
anything else I could do to make the process fast and as close to the 
current install as possible?


Yes. Do not reinstall but migrate your file system contents 1:1 to the 
new disk using rsync. The advantage is that the file system contents and 
therefore system configuration stay the same and you don't have to waste 
time putting stuff together afterwards.


I used/recommend a procedure similar to [1]. The principle is basically 
the same as a reinstall but instead of bootstrapping from a bare bones 
system you substitute your existing file systems. I don't see any 
benefit of doing it differently unless your existing install is broken 
in some way.


The most time was taken up by copying 512G of file system contents over 
a SATA<>USB3 bridge to the new SSD. If you can put both the old and the 
new drive on a SATA bus, you'll be done in no time.


[1] 
https://wiki.archlinux.org/index.php/migrate_installation_to_new_hardware#Top_to_Bottom


Re: [arch-general] Re-install of Arch on a larger drive

2018-03-17 Thread Trey Sizemore via arch-general
On Sat, 2018-03-17 at 17:59 -0400, Dorian C via arch-general wrote:
> I'm just curious really, but any particular reason you can't back up
> your
> personal files and do a clean install?
> 

I will be doing a clean install.  I want to mirror the same setup as
the current install, just on a bigger hard drive.


Re: [arch-general] Re-install of Arch on a larger drive

2018-03-17 Thread Dorian C via arch-general
I'm just curious really, but any particular reason you can't back up your
personal files and do a clean install?

On Sat, Mar 17, 2018 at 5:25 PM, Trey Sizemore via arch-general <
arch-general@archlinux.org> wrote:

> Hi all-
>
> I currently have Arch running on a 250GB drive, and I'm going to be
> moving to a 500GB drive.
>
> I'm looking for 'best practices' when it comes to the migrating as much
> as possible during the re-install.
>
> It appears that I can migrate my installed packages (standard and AUR
> repos) via:
>
> pacman -Qqe > pkglist.txt
>
> and then on the new install, I can use the pkglist.txt generated
> previously to:
>
> pacman -S - < pkglist.txt
>
> In addition, by backing up and migrating much of my /home partition (to
> include 'hidden' config files, anything else I could do to make the
> process fast and as close to the current install as possible?
>
> Thanks!
>


[arch-general] Re-install of Arch on a larger drive

2018-03-17 Thread Trey Sizemore via arch-general
Hi all-

I currently have Arch running on a 250GB drive, and I'm going to be
moving to a 500GB drive.

I'm looking for 'best practices' when it comes to the migrating as much
as possible during the re-install.

It appears that I can migrate my installed packages (standard and AUR
repos) via:

pacman -Qqe > pkglist.txt

and then on the new install, I can use the pkglist.txt generated
previously to:

pacman -S - < pkglist.txt

In addition, by backing up and migrating much of my /home partition (to
include 'hidden' config files, anything else I could do to make the
process fast and as close to the current install as possible?

Thanks!