Talk:USB flash installation media
I was not able to boot my Thinkpad X31 from USB stick without the lilo part first. I understood it like that: syslinux puts a bootloader at the beginning of the first partition, but nothing in the MBR, so when you try booting from the stick, the bootloader cannot be found.
Shouldn't the info that you need to select boot from usbdisk in BIOS be selected for this to work be mentioned? Or isn't it needed to be able to boot from an usb disk? If it's needed perhaps one could get grub and/or lilo to bootup an usb disk if the BIOS didn't support it and so how one would do that would also be needed as information.
What about merging this article with Usb Drive Arch Install?
Does not work anymore...
I was unable to run the new "live" arch-core-install-2008.04-rc-i686.iso off the USB stick. I've copied the kernel, initrd, and .squashfs files to the stick, and added a minimal entry in syslinux.cfg. Kernel + initrd boot fine, I even saw that the USB disk is detected, partitions parsed, and /dev/ entries created, but then init halts with something like 'unable to find /dev/cd/*'. I've spent few minutes reading the initialisation code, but didn't find a kernel commandline option to override it. I'm sure there is some easy way to make it work, but the process of mounting the CD-ROM should probably be implemented in a more robust way, so the initrd code finds and mounts the compressed filesystem even when booting from USB HDD.
Verifying the USB
Before and after having performed the dd onto the USB disk, check that the md5sums are correct. For example:
$ md5sum archlinux-2008.06-core-x86_64.img && echo && cat md5sums.x86_64 0c587f747646723f75c64c2317e8d651 archlinux-2008.06-core-x86_64.img
0c587f747646723f75c64c2317e8d651 archlinux-2008.06-core-x86_64.img 0c5b426e9cf7628aece3d76c4ded3912 archlinux-2008.06-core-x86_64.iso 81918cbb55026645df065526faba982e archlinux-2008.06-ftp-x86_64.img 921fed8e94c7432410a0b246dddfc0c4 archlinux-2008.06-ftp-x86_64.iso
The next command will give similar results, but will also let you confirm that the data was written correctly and can be read correctly: $ dd if=/dev/sdb count=661159 status=noxfer | md5sum && echo && cat md5sums.x86_64
--Zatricky 06:45, 22 January 2009 (EST)