You are not logged in.
Pages: 1
I wanted to build my own Arch Linux CD with some extra utilities but kept running in to a problem booting. I used the archiso package and the releng configuration. After getting the initial boot menu with the options of i686 and x86_64, etc., I kept getting:
Mounting '/dev/disk/by-label/ARCH_201504' to '/run/archiso/bootmnt'
Waiting 30 seconds for device /dev/disk/by-label/ARCH_201504 ...
Error: Boot device didn't show up after 30 seconds...
Falling back to interactive prompt.
You can try and fix the problem manually, log out when you are finished
I finally got a spare disk and did a clean Arch install including archiso, but the problem persists.
If I wait for the interactive prompt and run:
cd /dev/disk
mkdir by-label #(if the folder is not there)
cd by-label
ln -s ../../sr0 ARCH_201504
mount -t iso9660 /dev/disk/by-label/ARCH_201504 /run/archiso/bootmnt
exit
then the boot process continues and seems to work.
What am I missing that is keeping this mount from happening automatically? The results are the same trying to boot a BIOS as well as a UEFI system.
Last edited by rossboulet (2015-04-06 16:56:40)
I really hate this damn machine,
I wish that they would sell it.
It never does just what I want,
But only what I tell it. -Anonymous
Offline
I think you should just mount in this way:
mount /dev/sdxR /dir
You can just have a try maybe. However, in my opinion, the links under /dev/disk/by-xxxx/ are all soft links, not the device itself.
Offline
Thanks but no dice. I tried just mounting /dev/sr0 to /run/archiso/bootmnt/ but something is still looking for the soft link in /dev/disk/by-label. The only way I get it to work is by creating the soft link and then using the soft link in the mount.
I really hate this damn machine,
I wish that they would sell it.
It never does just what I want,
But only what I tell it. -Anonymous
Offline
Just a sanity check, but is the disk actually labeled ARCH_201504? lsblk --output=NAME,LABEL should tell you for sure.
Offline
MSC - your question put me on the right track. I got inconsistent results trying to read the disk label. While I had created the iso on an Arch Linux box, the only burner I had available was on my Windows 7 machine. I copied the iso to the Windows box and verified the copy with md5sum. Windows said it burned and verified the disk just fine and Windows read the label too. I finally put a burner in my Arch box and used it to burn the image. Now it works just fine. Thanks.
I really hate this damn machine,
I wish that they would sell it.
It never does just what I want,
But only what I tell it. -Anonymous
Offline
Pages: 1