Moving ALARM from flash drive to HD?

[Waynosan]

I found a small 2.5" USB HD and I'd like to move my install from the slow 4GB flash drive that I have it installed on now. I looked at the Archlinux disk cloning wiki and it looks like there's a number of different ways to go about this. Any suggestions on which is easiest (cause a noobie least amount of trouble)?... Or am I better off reinstalling from scratch? I already have SAMBA configured and started playing with CUPS so I'd rather go with the first option if possible. Thanks!

[WarheadsSE]

It's a matter of rsyncing off, and changing the rootfs (/) mount.

Which device is this on?

[Waynosan]

$this->bbcode_second_pass_quote('WarheadsSE', 'I')t's a matter of rsyncing off, and changing the rootfs (/) mount.

Which device is this on?

[moonman]

In dorsn't really matter. I've done "cp -a" in the past too as root (not sudo). No bootloader in mbr so dd seems like a waste of time as it will copy even empty blocks

[WarheadsSE]

Which ARM device is this on?

[Waynosan]

Pogoplug v2 Pink (ARM v5 Marvell Kirkwood)

[Waynosan]

OK, I cloned the USB drive onto the HD and so far everything looked good. I created a 2MB swap partition also. I tried to change the rootfs mount using the procedure outlined here:

https://wiki.archlinux.org/index.php/change_root

However I got stuck at the "Using arch-chroot" phase as Linux Mint doesn't have this command....

Guess next I'll try booting the PPv2 back up using the USB drive, then I'll connect the HD, and then follow the steps in the wiki... does that sound correct?

[moonman]

Those instructions assume you are on x86. All you need to do is create partitions on the new drive whatever way you like. Format first partition (as ext3 with old bootloader or ext4 if you are using new mainline uboot). Then become root (sudo su) and run "cp -a <old root mountpoint> <new root mount point> then run "sync". Umount all drives. Done.

[Waynosan]

@moonman,
OK, thanks. Tried doing that but pogoplug doesn't seem to want to boot off of the HD and I can't SSH back into it.

Boots OK when I put the USB drive in (and I can SSH in again). Wondering if the HD enclosure might be causing issues...

I'll try this to the new (faster) USB drive that I bought to try to isolate the issue.

To install ALARM I used the procedure (and bootloader) as described here:

http://archlinuxarm.org/platforms/armv5 ... 2-pinkgray

Here's the commands that I ran in case you see an issue with those in the meantime (ran in Linux Mint with both USB and HD attached). UIDs are almost identical since I initially created an image of the USB drive and then wrote that image to the HD drive:

$this->bbcode_second_pass_code('', '
zbyszko@zbyszko-EX58-UD4P ~ $ sudo su
[sudo] password for zbyszko:
zbyszko-EX58-UD4P zbyszko # cp -a /media/zbyszko/b635b2b5-5db7-4139-8a9c-6607532da371/root /media/zbyszko/b635b2b5-5db7-4139-8a9c-6607532da3711/root
zbyszko-EX58-UD4P zbyszko # sync
zbyszko-EX58-UD4P zbyszko # sync
zbyszko-EX58-UD4P zbyszko # umount /media/zbyszko/b635b2b5-5db7-4139-8a9c-6607532da371
zbyszko-EX58-UD4P zbyszko # umount /media/zbyszko/b635b2b5-5db7-4139-8a9c-6607532da3711
')

UPDATE:
cp command (from USB stick to new USB stick) didn't quite work properly... made a directory with the UID of the source disk and then put all the files in there... doing a "cp --help" shows that the -a switch copies files into an archive (which is what it apparently did).

$this->bbcode_second_pass_code('', 'zbyszko-EX58-UD4P arch # cd /media/zbyszko/ALARM
zbyszko-EX58-UD4P ALARM # ls
b635b2b5-5db7-4139-8a9c-6607532da3711 lost+found
zbyszko-EX58-UD4P ALARM # cd b635b2b5-5db7-4139-8a9c-6607532da3711/
zbyszko-EX58-UD4P b635b2b5-5db7-4139-8a9c-6607532da3711 # ls
bin ca-certificates extracted lost+found opt run sys usr
boot dev home media proc sbin tmp var
bsdtar etc lib mnt root srv T_xc3_x9c_x42_xC4_xB0TAK_UEKAE_K_xC3_xB6k_Sertifika_Hizmet_Sa_xC4_x9Flay_xc4_xb1_x63_xc4_xb1s_xc4_x
')

[Waynosan]

I confirmed that simply using cp to copy the contents of the original ALARM USB flash drive to another USB flash drive works fine (ALARM loads up and I'm able to SSH into it using the new USB flash drive). However doing the same to a USB HD drive, does not work (I cannot SSH into the pogoplug when I only have the USB HD drive with ALARM connected).

Guessing that the bootloader is looking for a USB flashdrive mount-point and not a USB HD drive?