https://wiki.archlinux.org/api.php?action=feedcontributions&user=Xyon&feedformat=atomArchWiki - User contributions [en]2018-03-20T03:11:22ZUser contributionsMediaWiki 1.30.0https://wiki.archlinux.org/index.php?title=User:Xyon&diff=169333User:Xyon2011-11-09T15:02:18Z<p>Xyon: Created page with &quot;I'm called Xyon everywhere except in places someone else beat me to the name, where I'm usually something different. Yay.&quot;</p>
<hr />
<div>I'm called Xyon everywhere except in places someone else beat me to the name, where I'm usually something different.<br />
<br />
Yay.</div>Xyonhttps://wiki.archlinux.org/index.php?title=Talk:USB_flash_installation_media&diff=169329Talk:USB flash installation media2011-11-09T14:57:02Z<p>Xyon: </p>
<hr />
<div>== Universal USB Installer ==<br />
<br />
This method works fine for me though I got a little stuck when Arch tried to get at the boot device and couldn't find it. Turns out UUSBI's default trick is to label your device &quot;PENDRIVE&quot; if it formats it during the process (user-selectable). I'd like to add a note about this to the section on this page which covers the tool, but as it'd be my first change here I want to be sure I'm not going to be shouted at...<br />
<br />
[[User:Xyon|Xyon]] 09:57, 9 November 2011 (EST)<br />
<br />
== unetbootin ==<br />
I was unable to get my usb drive bootable with the steps provided. I ended up using UNetbootin, a small application which made my USB drive bootable without a charm. The application doesn't require any installation procedure.<br />
<br />
--[[User:Serpent|Serpent]] 04:22, 25 March 2009 (EDT)<br />
<br />
== General ==<br />
I was not able to boot my Thinkpad X31 from USB stick without the lilo part first.<br />
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.<br />
-anonymous<br />
<br />
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.<br />
-nut543<br />
<br />
What about merging this article with [[Usb Drive Arch Install]]?<br />
-Thujone<br />
<br />
== Does not work anymore... ==<br />
<br />
I was unable to run the new &quot;live&quot; 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.<br />
<br />
== Verifying the USB ==<br />
<br />
Before and after having performed the dd onto the USB disk, check that the md5sums are correct. For example:<br />
<br />
- $ md5sum archlinux-2008.06-core-x86_64.img &amp;&amp; echo &amp;&amp; cat md5sums.x86_64<br />
<br />
The next command will give similar results, but will also let you confirm that the data was written correctly and can be read correctly:<br />
- dd if=/dev/sdb count=661159 status=noxfer | md5sum &amp;&amp; echo &amp;&amp; cat md5sums.x86_64<br />
<br />
--[[User:Zatricky|Zatricky]] 06:45, 22 January 2009 (EST)<br />
<br />
== dd for Windows ==<br />
<br />
There is also '''dd''' for Windows. I tried it and it works perfectly: [http://www.chrysocome.net/dd]<br />
<br />
dd if=file.img of=\\.\e:<br />
<br />
where '''e:''' is your USB drive letter.<br />
<br />
--[[User:Liquen|Liquen]] 14:55, 4 April 2009 (EDT)<br />
<br />
== But I don't want to overwrite the entire USB stick... ==<br />
<br />
''I'll add this into the article soonish; recording here for reference.''<br />
<br />
So you don't have to. The easier way is to download the ISO image, mount, then copy and install GRUB manually (a la &quot;old method&quot;).<br />
<br />
However, I already downloaded the IMG file and don't want to waste time. Then:<br />
<br />
sfdisk -l -uS /path/to/img<br />
<br />
outputs:<br />
<br />
?<br />
<br />
Note the starting sector of the first partition (63, in this example). Then:<br />
<br />
dd if=/path/to/img of=arch.img skip=63<br />
<br />
Now, I can mount the .img file without issue:<br />
<br />
mount -o loop arch.img /mnt/usb/<br />
<br />
== Remove Unetbootin ==<br />
<br />
Can we remove the Unetbootin paragraph? AFAIK, unetbootin has not been working with arch isos for a long time. [[User:Serpent|Serpent]] reported above to have made an install with it in May 2009, but I suspect he used an archboot image (which still works with unetbootin). <br />
In my experience, the kernel boots fine but it somehow fails to mount the usb drive and therefore can't load the fs overlay stuff. Often people also report on bbs that they tried Unetbootin without luck. Just tried with the new 2010.05 isos, same problem. <br />
If someone else can confirm this, I suggest removing Unetbootin altogether since it only adds confusion.<br />
<br />
Similary, is the third option (Gujin) still working? [[User:Hokasch|Hokasch]] 07:04, 18 May 2010 (EDT)<br />
<br />
: Ahh, understood why it is failing and updated the instructions. Still unsure if it wouldn't be better to remove it. [https://bugs.launchpad.net/unetbootin/+bug/582213 Bug report] [[User:Hokasch|Hokasch]] 07:33, 18 May 2010 (EDT)</div>Xyon