[SOLVED] Cannot clone USB ARCH Installation

Jofre · 2015-12-21 20:16:25

I am running Archlinux from a 32 GB pendrive with very good results so far . I wanted to make a clone of this pendrive and followed instructions on the wiki by two ways one as ORIG => IMG => CLONE and also directly from original device to the clone. In both cases the problem is the same, the clone cannot boot and says that it cannot find the device UUID=XXX, however if I do blkid , the exact same UUID value is shown. So the clone is perfect , it has same partition table, same UUID, but the bootloader cannot find it.

I've also chroot on it and re run grub-install, mkcpio -p linux and grub config and yet same results, the boot loaders says it cannot find that UUID which blkid correctly reports. Below are the errors at the boot screen:

ERROR: device 'UUID=f8698026-3165-4173-97ce-0dc84111c1d4'not found . skipping fsck
ERROR: Unable to find root device 'f8698026-3165-4173-97ce-0dc84111c1d4'
You are being dropped to a recovery shell
type exit to try and continue booting
sh: can't access tty: job control turned off
[ 21.696672] usb 2-5: device descriptor read/64, error -71
[ 22,023339] usb 2-5: device descriptor read/64, error -71
[ 22.243339] usb 2-5: device descriptor read/64, error -71
[ 22.866671] usb 2-5 device not accepting address 5, error -71
[ 23.386672] usb 2-5 device not accepting address 6, error -71
[ 23.386947]usb usb2-port5: unable to enumerate USB device

The result of blkid is
# blkid
/dev/sdd1: UUID="f8698026-3165-4173-97ce-0dc84111c1d4" TYPE="ext4"

I would appreciate any help or guidance.

Last edited by Jofre (2016-01-06 19:49:29)

boban_dj · 2015-12-21 20:34:33

your /etc/fstab from the clone should not be the same from your cloned system (it now probaly is) , you must change it to match it with the UUID from the clone in the /etc/fstab of the clone

tom.ty89 · 2015-12-21 20:48:47

boban_dj wrote:

your /etc/fstab from the clone should not be the same from your cloned system (it now probaly is) , you must change it to match it with the UUID from the clone in the /etc/fstab of the clone

Why not? As he's mentioned, the UUID of the filesystems will not change since he did a dd(-ish) clone.

Whether he should change the UUID of the filesystems to avoid conflict to allow both drives exist in the system is another story though.

FWIW, /etc/fstab will not be read before / is mounted, since it's inside /. Therefore it's always the UUID specified for the root= option in the kernel command line that matters.

I don't think the problem has anything to do with the UUID anyway. It's more likely the driver for the clone drive does not exist in the initramfs, or the driver is not working. Try initramfs-linux-fallback.img instead.

Since there are some USB errors popped up, they might matter if your clone drive is a USB drive as well.

P.S. In any case, you better not to have the original and clone connected at the same time, since they have filesystems with same UUIDs (and also paritions with the same PARTUUIDs). So only have them co-exists AFTER you changed the ACTUAL UUIDs/PARTUUIDs (and then of course, the fstab and the bootloader entry).

Last edited by tom.ty89 (2015-12-21 20:53:28)

boban_dj · 2015-12-21 21:11:13

@tom.ty89 the OP says:

Jofre wrote:

In both cases the problem is the same, the clone cannot boot and says that it cannot find the device UUID=XXX, however if I do blkid , the exact same UUID value is shown. So the clone is perfect , it has same partition table, same UUID, but the bootloader cannot find it.

So I assumed he had both disks connected at the same time.

Last edited by boban_dj (2015-12-21 21:20:53)

Head_on_a_Stick · 2015-12-21 22:24:54

@OP: Please post the *exact* command used to transfer the system.

I have cloned an Arch system from a USB stick to an internal drive and it worked without modification but I copied the entire device.

Did you only copy the partition?

Jofre · 2015-12-22 03:15:32

First of all guys THANKS for the fast responses ! Now I am obliged to answer in spite leaving somehow late for work !!!

@ boban_dj: Negative, the UUID is EXACTLY the same . As a matter of fact, I've also recreated with genfstab to noa avail. My bad as I did not mentioned I've used dd

@tom.ty89 I agree with you on the definition of the problem, but I did not have both together , even more, I tried DIFFERENT (but exact same model laptops).

@Head_on_Stick:

The last time:
# dd if=/dev/sdc of=/dev/sdd bs=512 conv=noerror,sync

It took 5,000 seconds in a 32 GB stick.

Previously with same results:

# dd if=/dev/sdX conv=sync,noerror bs=64K | gzip -c > /path/to/backup.img.gz

ans restored with:
# gunzip -c /path/to/backup.img.gz | dd of=/dev/sdX

Before posting here all google for the usb error -71 returned hits related to the usb keyboard and mouse. Could it be my second stick is damaged? Let have in mind that still if I mount and see, it is an EXACT copy all partitions data files etc. bklkid is responding the same, everything is the SAME !!!

Now to tom, How I force grub to use inittrans fallback? I need to mention in one of my attempts, I chrooted , erased everything in /etc/grub and redid grub install , mkcpio etc ,etc with exact same errors at booting.

Should I try pacman -S grub to get a fresh grub install?

Thanks in advance !

tom.ty89 · 2015-12-22 04:35:02

To switch the initramfs being used you only need to select on the grub menu, or in case you cannot find/see the entry, just press "e" to edit the initrd line by adding "-fallback" before ".img".

Last edited by tom.ty89 (2015-12-22 04:35:43)

Jofre · 2015-12-22 13:36:23

Tom,

Thanks, I've just tried that , then hit F10 to boot and exact issue . Very weird, I will do some more tries before making a manual Arch install in order to confirm the drive may have an issue ( which I do not think so!).

Onr more thing, does anybody know if I copy the partitions ( i have just two, root an /home), then chroot and reinstall grub , config , genfstab , etc may work as a clone?

Other, thing, to disregard grub issue, is it possible to use LILO ?

boban_dj · 2015-12-22 14:01:40

@Jofre, I had before issues with arch live iso on usb sticks (with dd). Some older sticks did not work, when I changed to a newer, everything worked fine. So maybe try another usb.

tom.ty89 · 2015-12-22 16:14:48

Jofre wrote:

I've also chroot on it and re run grub-install, mkcpio -p linux and grub config and yet same results,

So I assume you can boot an Arch Live Medium when the clone is also connected. Can you mount the clone's root in Arch Live with `mount UUID=f8698026-3165-4173-97ce-0dc84111c1d4 /mnt`? (without any other clone or the original connected)

Then, can you run `journalctl -p 3` to check whether you see the same USB errors? (If you have multiple machines for testing, try boot the clone once again to confirm you see the USB errors on this machine, and then cross check)

Also, can you paste `lsusb` and `lsusb -t`? It's better to be full output, so if you have network there I would like you to paste with the following commands:

lsusb | curl -F c=@- https://ptpb.pw/
lsusb -t | curl -F c=@- https://ptpb.pw/

and post the returned URLs.

Jofre · 2015-12-22 19:09:15

tom.ty89

First let me tell I've worsened the situation a litlle messing up grub. While in chroot, I've unistalled grub, then I could not pacman because wrong architecture or so, then I've changed pacman.cfg from architecture=auto to i686; it worked and then I configured grub with some errors, the thing is it now it boots to a grub prompt waiting for some input which I do not know. Anyway, not a big deal i should be able to solve this later.

1. cannot mount because that UUID is not in fstab. This is an live cd , fstab is empty. So in order to have an easy way to make your other commands, I've mounted with mount /dev/sda2 /mnt , created an user teo and ssh into it , then I've added > somefile.txt to all your commands so i can copy from the ssh terminal ( by the way is there some root pasw for archiso???).

for journalctl -p 3 returns

2.-- Logs begin at Tue 2015-12-22 16:16:24 UTC, end at Tue 2015-12-22 16:31:08 UT$
Dec 22 16:16:50 archiso kernel: kvm: disabled by bios
Dec 22 16:16:50 archiso kernel: kvm: disabled by bios
Dec 22 16:27:59 archiso sshd[688]: error: Received disconnect from 192.168.20.2$
Dec 22 16:27:59 archiso sshd[688]: PAM service(sshd) ignoring max retries; 4 > 3
Dec 22 16:29:48 archiso sudo[716]:      teo : user NOT in sudoers ; TTY=pts/0 ;$

The last three lines belongs to my ssh and user teo.

for susb | curl -F c=@- https://ptpb.pw/

digest: e383c67dc28280ff3870bf1e7b4c5fdcf92adb8f
long: AOODxn3CgoD_OHC_HntMX9z5KtuP
short: KtuP
status: already exists
url: https://ptpb.pw/KtuP

for susb -t | curl -F c=@- https://ptpb.pw/

digest: ac92a83f3ac65cbc4a12b8cfbb1cf6fcf83ac735
long: AKySqD86xly8ShK4z7sc9vz4Osc1
short: Osc1
status: created
url: https://ptpb.pw/Osc1
uuid: 111675d6-8fb1-40df-9a54-715a74789771

in addition I've run blkid

/dev/sr0: UUID="2015-11-01-08-35-56-00" LABEL="ARCH_201511" TYPE="iso9660" PTUU$
/dev/sda1: UUID="f8698026-3165-4173-97ce-0dc84111c1d4" TYPE="ext4" PARTUUID="7b$
/dev/sda2: UUID="5f62a6ea-6c21-4b1d-8b7f-e739e7c75302" TYPE="ext4" PARTUUID="7b$
/dev/loop0: TYPE="squashfs"

thanks for all your efforts, if you have some idea of what do i need to enter at the boot prompt, let me know.

tom.ty89 · 2015-12-22 20:36:06

You do not need the UUID to be in fstab to use it with `mount`, you just need to specify a target ("/mnt"), which I have shown in the previous post:

[tom@localhost ~]$ ls -Al /mnt/
total 0
[tom@localhost ~]$ cat /etc/fstab 
# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
[tom@localhost ~]$ sudo mount UUID=B06C-A589 /mnt/
[tom@localhost ~]$ ls -Al /mnt/
total 4
drwxr-xr-x 3 root root 2048 Dec 19 00:57 EFI
drwxr-xr-x 6 root root 2048 Dec 19 00:58 grub

See? (FWIW my fstab has ALWAYS been empty, I didn't just edit it and test) And you didn't even bother to try?

If you still cannot mount with a target specified, then it might actually give you a hint on why you can't boot it.

I have no idea why you need all this ssh complication anyway. Actually I am almost totally lost about what you've been doing. Apparently for some reason, or in some way, you totally screwed up grub and maybe even your system. In almost no cases you should change architecture in pacman.conf. Reinstalling grub, no matter in the sense of package or `grub-install`, is totally pointless to your problem as well, since grub has already done its job and everything depends on the kernel and initramfs when your problem comes up. The only thing you could have try is to not boot with UUID (but for example with root=/dev/sda2), which you haven't done, and that only requires you to edit your grub.cfg at most.

Also, the journalctl / lsusb output only mean something if you can actually cross check with the result of a "successful grub boot", that is the experience you post at first, kernel and initramfs loaded, but root filesystem cannot be found, and some USB errors shows up, and now they are meaningless.

So I don't really know if I can help you further, unless you clone your drive and start there again. In that case maybe you can boot the Arch ISO with the original and the new clone connected at DIFFERENT TIME, and try to mount it in the way I mentioned above RESPECTIVELY, and see if any of the trial succeed or fail.

Last edited by tom.ty89 (2015-12-22 20:42:46)

Jofre · 2015-12-23 14:04:18

Tom,

You are absolutely right, I am firing in the dark , so yes, I've messed up the system to the point pacman broke. So, yes I remade the clone and I am at page one again.

I did the mount command exactly as you said and the answer was about that fstab do not mention it or so. I cannot recall the exact message but I will try again with the new clone. But as you said , that could be an indication of the problem. How can I bother to try edit fstab if the CD is Read Only ??? Remember, I run archiso to examine the clone . Now, if you think it is better to put arhciso in a pendrive I will do !

I've started the ssh demon in order to copy and paste the command results to post here using putty.

I am working on this since the last week. If you see, it is faster to manually replicate the installation !!! So, I am doing my best , but as I said at the beginning I may be firing in the dark due to ignorance on what to do.

This is my plan forward and I will strictly follow indications after.

1. Reclone and test ( Done yesterday, recloned and showed similar initial problem booting)
2. Try again mount UUID=f8698026-3165-4173-97ce-0dc84111c1d4 /mnt and report back.
3. Edit grub.cfg as per your last post and see if it boots

The last dd was done gzipping the image . I can look for the way to share that image if you think it may help.

Sorry if i create confusion.

Jofre · 2015-12-23 20:19:28

OK here again.

1.mount UUID=f8698026-3165-4173-97ce-0dc84111c1d4 /mnt/ Worked OK
2. journalctl -p 3

 Logs begin at Wed 2015-12-23 17:23:05 UTC, end at Wed 2015-12-23 17:37:45 UT$
Dec 23 17:23:37 archiso kernel: kvm: disabled by bios

3. lsusb

Bus 007 Device 003: ID 0781:5583 SanDisk Corp.
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

4. lsusb -t

/:  Bus 07.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
    |__ Port 6: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 480M
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
    |__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/4p, 480M

5. lsusb | curl -F c=@- https://ptpb.pw/

digest: 98a33aa7c03bd1207b18449f939bbf1011616845
long: AJijOqfAO9EgexhEn5ObvxARYWhF
short: YWhF
status: already exists
url: https://ptpb.pw/YWhF

6. lsusb -t | curl -F c=@- https://ptpb.pw/

digest: 9d1070d462230b86ffe8d3f1d890ff399c4dca7a
long: AJ0QcNRiIwuG_-jT8diQ_zmcTcp6
short: Tcp6
status: created
url: https://ptpb.pw/Tcp6
uuid: ca5d7396-dbeb-4636-8d3b-d645c32daee9

Finally, I edited grub. cfg , but below is what I've found the UUID is different, however the error message is the same as at the beginning with the UUID that correctly mounts the pendrive . See this part og grub.cfg

set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  ad4103fa-d940-47ca-8506-301d8071d467
else
  search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-ad4103fa-d940-47ca-8506-30$
        load_video
        set gfxpayload=keep

Could it be grup probes for above UUID , but when it must sent the error message use some UUID identifier function which obtains the correct value , but just to display the error?
Please let me know as I do not want to modify anything until you have a look !

Thanks in advance !

Jofre · 2015-12-23 20:42:26

In the meanwhile , i've saved a copy of the grub.cfg and edited the UUID lines shown above with the correct one. It is like 7 or 8 times inside the file . But, exactly same problem continues. I really do not know what is wrong.

tom.ty89 · 2015-12-26 01:52:17

Mount the clone's root to /mnt and paste the output of:

lsinitcpio /mnt/boot/initramfs-linux.img | grep .ko | curl -F c=@- https://ptpb.pw/

Try use your original grub.cfg but ONLY change any

root=UUID=f8698026-3165-4173-97ce-0dc84111c1d4

to

root=/dev/sda1

Jofre · 2016-01-01 09:13:37

Tom.ty89

I had been out of my system from last week. Here the results :

lsinitcpio /mnt/boot/initramfs-linux.img | grep .ko | curl -F c=@- https://ptpb.pw/


digest: 69026fbdb2c17d8161286f342033f007c4faa196
long: AGkCb72ywX2BYShvNCAz8AfE-qGW
short: -qGW
status: created
url: https://ptpb.pw/-qGW
uuid: 3e545ff2-3bda-4e1a-ae22-bea895f1ec55

I've changed the cases as you mentioned wherever there is root=UUID=f8..... But there are a LOT of lines containing f8698026-3165-4173-97ce-0dc84111c1d4 for example after --set=root

so root=UUID=f8.... is only a couple of times and I've replaced as:

root=/dev/sda1 rw quiet

Upon attempting booting , Issue remains the same:

ERROR: device '/dev/sda1' not found skipping fcsk
ERROR: Unable to find root device '/dev/sda1'
you are being dropped to a recovery shell

The recovery shell cannot do much as fdisk, cfdisk is "not found". But blkid works and it only reports /dev/sr0. So the pendrive is not mounted ! is that why it is never found? Do you know at what stage grub is supposed to mount the the pendrive filesystem?

Unless you've got a better idea. I will do a complete manual install on the pendrive in order to see if it is somehow hardware related. But yet I do believe something is wrong during the cloning with dd. If I found a similar pendrive I will try the cloning as another way to verify or discard a hardware issue. Thanks !

tom.ty89 · 2016-01-02 06:05:37

Of course it's not mounted. That's why you're getting the error. As I've said that's not the job of grub, but kernel and initramfs.

I don't have an idea tbh. lsinitcpio seems to tell that you have all the necessary driver modules in the initramfs. Can you try `ls /dev/sd*` and `ls /dev/disk/*` in the recovery shell to see if anything's there? Also try `lsmod` to see if all the modules listed by lsinitcpio are loaded (especially ehci-*, sd_mod, usb-storage and ext4).

Jofre · 2016-01-02 17:46:17

Tom,

Thanks after days and days of testing it seems to be it is a hardware issue. Today since the morning, I even tried the way explained in this thread:

https://bbs.archlinux.org/viewtopic.php?id=139680

Just copying the partitions one by one then chroot , run grub-install, config etc which did not work. So, just one hour ago I did a manual install using the live CD to produce exactly same problem. It seems to be I was very lucky with the original pendrive, because I did all these testing with a another (a second ) pendrive (3 pendrives , one original , two I've used for cloning). It is possible this hardware issue is not happening with all of them and only the original was OK. Or (unlikely) I've killed them with dd ? Let say the original pendrive is "dd free".

Just for documentation, these pendrives are SanDisk 32GB Ultrafit.

About 6 months ago, when I was using puppy linux (Quirky) , I did notice some flash drive issues when the installation on a 16GB usb drive worked OK and similar installation in same SanDisk drive, but 32GB did not boot all all. This was different though, the screen just showed a blinking hyphen. In this thread case, grub shows the screen etc.

In conclusion, the cloning is not a problem at all with this. Hence, I may then consider the topic as "solved"...

Thanks a lot for all your help. I will now try a manual installation one more time with the second 32GB pendrive, then again with a 16GB in order to see if the size is the problem which was my conclusion with Puppy.

Jofre · 2016-01-02 18:17:24

Tom,

Sorry, I did not include your questions:
`ls /dev/sd*` and `ls /dev/disk/*`

There is no sdXY at all under /dev/ and under disk is two sub folders by-id and by-path , there is an UUID related to the DVD drive in both cases. For lsmod:

Module                    Size      Used by
sr_mod
cdrom
ata_generic
atkbd
libps2
sdhci_pci
sdhci
led_class
mmc_core
firewire_ohci
ata_piix
firewire_core
crc_itu_t
i8042
serio
pata_acpi
ehci_pci
uhci_hcd
ehci_hcd   
libata
usbcore
usb_common
scsi_mod

Whoever must mount the USB is not doing it at all !!

Thanks.

tom.ty89 · 2016-01-02 18:50:20

Well the usb-storage module is not even loaded. Maybe you can try to load it in the shell, or instead, boot with the kernel param:

earlymodules=ehci-pci,usb-storage,sd-mod,ext4

Jofre · 2016-01-06 19:45:54

It seems to be I have this now solved and it was NOT a hardware issue as inferred above. I believe I did try this much earlier but perhaps I've made some mistakes or not sure. For the purpose of documenting the solution in case anyone else run into this issue while cloning this is how I re-did the cloning successfully:

1. Create gzipped image:

# dd if=/dev/sdX conv=sync,noerror bs=64K | gzip -c  > /path/to/backup.img.gz

2. Create clone.

# gunzip -c /path/to/backup.img.gz | dd of=/dev/sdX

If attempted to reboot at this point , all above described problem will occur.

3. Recreate initrams images and re-install grub

Boot the laptop with the Archlinux Live cd then

archiso# mount /dev/sda  /mnt

archiso# arch-chroot  /mnt

# mkinitcpio -p linux

# grub-install /dev/sda

# grub-mkconfig /boot/grub/grub.cfg

# exit

archiso# umount /mnt

archiso# reboot

I did this twice with the two pendrives and both are booting OK. Thanks for the tips and advice

boban_dj · 2016-01-14 06:37:10

Thanks for explaining solution

Arch Linux

#1 2015-12-21 20:16:25

[SOLVED] Cannot clone USB ARCH Installation

#2 2015-12-21 20:34:33

Re: [SOLVED] Cannot clone USB ARCH Installation

#3 2015-12-21 20:48:47

Re: [SOLVED] Cannot clone USB ARCH Installation

#4 2015-12-21 21:11:13

Re: [SOLVED] Cannot clone USB ARCH Installation

#5 2015-12-21 22:24:54

Re: [SOLVED] Cannot clone USB ARCH Installation

#6 2015-12-22 03:15:32

Re: [SOLVED] Cannot clone USB ARCH Installation

#7 2015-12-22 04:35:02

Re: [SOLVED] Cannot clone USB ARCH Installation

#8 2015-12-22 13:36:23

Re: [SOLVED] Cannot clone USB ARCH Installation

#9 2015-12-22 14:01:40

Re: [SOLVED] Cannot clone USB ARCH Installation

#10 2015-12-22 16:14:48

Re: [SOLVED] Cannot clone USB ARCH Installation

#11 2015-12-22 19:09:15

Re: [SOLVED] Cannot clone USB ARCH Installation

#12 2015-12-22 20:36:06

Re: [SOLVED] Cannot clone USB ARCH Installation

#13 2015-12-23 14:04:18

Re: [SOLVED] Cannot clone USB ARCH Installation

#14 2015-12-23 20:19:28

Re: [SOLVED] Cannot clone USB ARCH Installation

#15 2015-12-23 20:42:26

Re: [SOLVED] Cannot clone USB ARCH Installation

#16 2015-12-26 01:52:17

Re: [SOLVED] Cannot clone USB ARCH Installation

#17 2016-01-01 09:13:37

Re: [SOLVED] Cannot clone USB ARCH Installation

#18 2016-01-02 06:05:37

Re: [SOLVED] Cannot clone USB ARCH Installation

#19 2016-01-02 17:46:17

Re: [SOLVED] Cannot clone USB ARCH Installation

#20 2016-01-02 18:17:24

Re: [SOLVED] Cannot clone USB ARCH Installation

#21 2016-01-02 18:50:20

Re: [SOLVED] Cannot clone USB ARCH Installation

#22 2016-01-06 19:45:54

Re: [SOLVED] Cannot clone USB ARCH Installation

#23 2016-01-14 06:37:10

Re: [SOLVED] Cannot clone USB ARCH Installation

Board footer