Release Engineering

Tasklist

FS#19480 - Booting 2010.05.13-core from USB fails unless volume name is ARCHLINUX_201005

Attached to Project: Release Engineering
Opened by Clemens (clesch) - Sunday, 16 May 2010, 13:32 GMT
Last edited by Thomas Bächler (brain0) - Sunday, 16 May 2010, 16:21 GMT
Task Type Bug Report
Category ArchISO
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 2010.05.07-testbuild
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

I’ve installed archlinux-2010.05.13-core-x86_64.iso to a USB stick using Unetbootin which has always worked well for all the previous arch iso releases.
With the latest 2010.05.13 build however I had to make sure that the USB stick’s volume name was set to ARCH_201005 or else arch would time out trying to find the volume.

This should be easily reproducible by creating a 2010.05.13 USB stick with Unetbootin and booting from that. I’ll try to add a log of the error later on today if required.
This task depends upon

Closed by  Thomas Bächler (brain0)
Sunday, 16 May 2010, 16:21 GMT
Reason for closing:  Not a bug
Comment by Ionut Biru (wonder) - Sunday, 16 May 2010, 14:24 GMT
why Unetbootin when you can use directly dd to write the iso on usb?

dd if=arch.iso of=/dev/sdx
Comment by Thomas Bächler (brain0) - Sunday, 16 May 2010, 16:21 GMT
This is not a bug, it is a feature. The boot process has to identify which device to mount. It does this by comparing the volume label of the device with a predefined string.

Old versions used to mount all available volumes, which is stupid and can cause unexpected errors. When you use unetbootin instead of dd'ing the image, you can modify the isolinux configuration to match the label of your stick.

Loading...