[solved] Boot device didn't show up after 30 seconds...

RichSelian · 2009-08-11 13:37:14

Cannot install archlinux-2009.08-core-i686.img. It says "Boot device didn't show up after 30 seconds" and throws me into ramfs$.

Last edited by RichSelian (2009-08-12 00:38:56)

GerBra · 2009-08-11 21:22:27

Could you please test in ramfs$:
cat /proc/scsi/scsi
if your USB Device is there?

If so: please try also a
do a: exit or STRG+D directly in ramfs so it starts a second one directly.
Other way is in ramfs$:
ln -sf /dev/sdc /dev/archiso (if your USB device is sdc)

brain0 · 2009-08-11 21:22:28

Could you look a bit closer? There should be messages about your hard drives being detected, can you see those? Are you installing from CD or USB (or from CD connected via USB)? In the ramfs shell, can you run 'echo /dev/sd*' or 'echo /dev/sr*' to see if hard drives/CD drives have been detected? Can you run 'cat /proc/scsi/scsi' to see which devices have been detected?

Also, for debugging purposes, could you run 'cat /lib/udev/rules.d/00-archiso-device.rules' and paste the output here?

If the device is detected after the timeout is over, you can simply log out and it will try again. If it doesn't work, but your CD drive is detected, you can run 'ln -s /dev/sr0 /dev/archiso' and then log out and it'll work as well.

EDIT: Oh, gerhard was faster. Anyway, you're not using a CD but USB (I overlooked that), so gerbra's hints might be more accurate for you.

Last edited by brain0 (2009-08-11 21:24:02)

RichSelian · 2009-08-12 00:37:15

Thanks, "ln -s /dev/sdb1 /dev/archiso" solved my problem.

jaf777 · 2009-08-12 04:00:28

Hi-
Same error for me booting from usb...
cat /proc/scsi/scsi shows that device is detected...

did:
ln -sf /dev/sdb1 /dev/archiso

but now a new error:
"ERROR: /dev/archiso found but the filesystem type is unkown"

Sorry about ridiculous pic but it does show kernel panic, just trying to help... couldn't copy output. I can post dmesg from prior to kernel panic if you want (but it doesn't include errors).

Thank you for your help.

brain0 · 2009-08-12 09:02:19

jaf777 wrote:

did:
ln -sf /dev/sdb1 /dev/archiso
but now a new error:
"ERROR: /dev/archiso found but the filesystem type is unkown"

Whatever is on /dev/sdb1, it is not our image. How did you create the installation media?

cwjiof · 2009-08-12 11:59:08

RichSelian wrote:

Thanks, "ln -s /dev/sdb1 /dev/archiso" solved my problem.

Me too. And it seems a bug for the USB image.

RichSelian · 2009-08-12 12:38:26

Are you booting the installation from an FAT32 file system? I try booting from an FAT32 file system and get the same error. But everything works fine when the installation is on an EXT3/EXT4 file system.

brain0 · 2009-08-12 13:11:05

If you re-create the file system instead of dd'ing it to the USB drive, you MUST make sure the label is correct. If the label is too long (we use 16 character labels, so this might be too long for FAT32, no idea), then you must change the archisolabel= command line option during boot. The label is used to identify the archiso-image inside the initramfs.

EDIT: Forgot to mention: The boot process is now made such that logging out from the ramfs-shell will always retry to open the archiso-device. This means that even with such a problem, you can still boot the drive if you are able to create the correct /dev/archiso-symlink manually. On previous ISOs, the boot process always failed and paniced in such a case.

Last edited by brain0 (2009-08-12 13:13:48)

jaf777 · 2009-08-12 17:02:50

Thank you very much for all the responses. My issue is resolved.
I was booting from a fat16 formatted usb; I had used UNetBootin under windows to write the img to usb.

So I created a new partition / new ext3 filesystem on usb stick under linux (RIPLinux) in GParted.
Then wrote the img using "dd bs=8M if=image.img of=/dev/sd[x]" per wiki documentation (i.e. /dev/sdb not /dev/sdb1).

Boots perfectly with no hiccups, no dropping to ramfs$ prompt, boot device archiso is found without manual linking. Boots to "login as root to begin installation".

Thanks again!

Last edited by jaf777 (2009-08-12 17:03:34)

cwjiof · 2009-08-13 03:29:59

brain0 wrote:

If you re-create the file system instead of dd'ing it to the USB drive, you MUST make sure the label is correct……then you must change the archisolabel= command line option during boot. The label is used to identify the archiso-image inside the initramfs.……

Thank you very much.

I noticed the menu.lst on my USB drive, it has:
kernel /boot/vmlinuz26 lang=en locale=en_US.UTF-8 archisolabel=ARCHISO_OINGAE2I ramdisk_size=75%

I had thought it's a bug, but when I changed the default archisolabel=ARCHISO_OINGAE2I command line option to archisolabel=abcd (where abcd is my USB drive label), it works!

brain0 · 2009-08-13 11:43:58

cwjiof wrote:

I noticed the menu.lst on my USB drive, it has:
kernel /boot/vmlinuz26 lang=en locale=en_US.UTF-8 archisolabel=ARCHISO_OINGAE2I ramdisk_size=75%
I had thought it's a bug, but when I changed the default archisolabel=ARCHISO_OINGAE2I command line option to archisolabel=abcd (where abcd is my USB drive label), it works!

We should include that in our documentation, as it seems rather common that people remaster their USB images instead of dd'ing them (judging from the number of reports about this).

Some clarification: This was done so archiso wouldn't mount every single filesystem to look for the right image. Also, we are more flexible with respect to scan times on USB busses: We are able to check once a second if the archiso-device appeared, so if it takes 2 seconds, we can start booting after 2 seconds, and if it happens after 20 seconds, we won't abort before that. I sincerely hope that all reports of failures were due to people remastering the images and not setting the label in menu.lst properly.

References:
http://projects.archlinux.org/?p=archis … 995f33820e
http://projects.archlinux.org/?p=archis … c8274578b0

rael · 2009-08-14 14:44:05

The methods to write the USB image on Windows using a USB stick formatted with FAT32 didn't work for me.

Both dd for windows and flashnul gave me a GRUB ERROR 17.
I used Unetbootin and I got the Kernel Panic mentioned above.

In order to get the installation to work I had to use a Linux Live CD, format the USB there (I used FAT32) and finally dding.

Last edited by rael (2009-08-14 20:31:18)

farkenell · 2009-08-15 10:45:39

I had this problem from a cdrom for some reason.

I had 2x 1.5 tb disks I recently bought i wanted to setup as a raid.

anyway. I just did
#ln -sf /dev/sr0 /dev/archiso

and then typed exit

brain0 · 2009-08-15 22:13:53

farkenell wrote:

I had this problem from a cdrom for some reason.
I had 2x 1.5 tb disks I recently bought i wanted to setup as a raid.
anyway. I just did
#ln -sf /dev/sr0 /dev/archiso
and then typed exit

Hmm, that should never happen. Anything special about your hardware?

Chade · 2009-08-18 15:27:28

farkenell wrote:

I had this problem from a cdrom for some reason.
I had 2x 1.5 tb disks I recently bought i wanted to setup as a raid.
anyway. I just did
#ln -sf /dev/sr0 /dev/archiso
and then typed exit

I also had the same issue using either USB or CD. This trick was the only way to get the arch installer to run.

Curiously I also have two hard drives, but they aren't set up as a raid.

Casper21 · 2009-08-20 01:35:58

I had this problem also. I was booting from an external DVD-RW via USB. The drive was connected through a USB port on a monitor (probably not the best idea for a DVD-RW). Connecting the drive to a USB port on the mainboard got rid of the problem.

Nexu$ · 2009-08-24 17:05:50

Hey you guys.
First of all thank you for a great forum and great help.

I am writing an image to a USB flash drive according to the installation guide, but when i enter the dd if=.... command as the manual says, it says:
dd: opening ´/dev/sdc': Read-only file system, and nothing is written to the flash disk. Am I supposed to change the file system, if yes, how is this done?
Should the device be mounted or unmounted, when I make the command?
Thank you

Nexu$ · 2009-08-24 17:50:43

Hey..
Found another way to make it work..
In my oppinion its a bit complicated way the installation is now, but I can understand the argumentation. I have also learned alot, so it's cool.
Archlinux simply rules..

tiny.ian · 2009-09-05 03:17:36

I was having a similar issue with the 2009.08 netinst. image running on an Asus EEEPC 1000HE (unetbootin to USB fat32, pata image)- but I got it working like this;

ramfs$ ln -sf /dev/sd[x] /dev/archiso
ramfs$ mount -t vfat /dev/archiso /bootmnt

Login prompt and EVERTHANG!

Fou · 2009-09-27 13:47:01

Hi all,

First of all, i'm a french guy from Quebec so my english is not very well.

I have the same error when i boot from the cd of Arch Linux 2009.08 core x86_64.
"Boot deveice didn't show up after 30 seconds"

cat /proc/scsi/scsi show me my hard drive and my cd-rom, so it look ok.

ln -sf /dev/sda3 /dev/archlinux does not work for me. It said "mounting was successful, but the isomounts file does not exist"

on my hard drive i got 1 ntfs partition for vista, the second is in ext3 for the current installation.

I really want ArchLinux. I need your help.

Is it because of my Vista on the first partition ? I'll keep vista just for playing games like Call of Duty 5, Crysis, modern warfare, etc....

Thanks a lot

depierce · 2009-10-01 05:25:14

I'm not about to try duplicating my results, but here's what happened for me:

First time through, booting from burned ISO of archlinux-2009.08-core-i686, got the 30-second timeout and failure to find archiso at whatever the archisolabel defaults to.
Second time through, tried "ln -s /dev/sr0 /dev/archiso", exited ramfs to continue, got a kernel panic.
Third time through, edited grub boot line for kernel to point to /dev/sr0 (archisolabel=/dev/sr0). Kernel again failed to filed it and exec'd ramfs shell, so tried "ln -s /dev/sr0 /dev/archiso" anyway. *That worked* but I have no clue why.

A symlink should've worked. Editing the archisolabel to point directly to /dev/sr0 should've worked. The fact that neither worked by itself but worked when used together could drive Cthulu insane. If anyone can explain this, please do.

P.S. My hardware isn't exotic. I've got one 1.44 floppy drive, one SATA CD/DVD R/W/RW, two SATA WD Raptors, and two Seagate Cheetahs on an Ultra 160 SCSI (yes, I know, the Cheetahs can do 320 but I can't afford the controller).

Last edited by depierce (2009-10-01 05:32:47)

Xiong Chiamiov · 2009-10-15 22:57:50

tiny.ian wrote:

I was having a similar issue with the 2009.08 netinst. image running on an Asus EEEPC 1000HE (unetbootin to USB fat32, pata image)- but I got it working like this;
ramfs$ ln -sf /dev/sd[x] /dev/archiso
ramfs$ mount -t vfat /dev/archiso /bootmnt
Login prompt and EVERTHANG!

This was the one that worked for me. Thank god for helpful responses, and Google to find them.

noesc · 2009-10-21 21:34:27

This was really interesting! I got the 30sec-timer and dropped to ramfs$
I tried out:
rebooting <- No result
rebooting + changing harddrive <- No good
rebooted + 'ln -s /dev/[my-cd] /dev/archiso' <- No good, kernelpanic!
<--- same as above ---> <- Still kernelpanic! :'(
Searched the forum some more.. found this thread and was going to go:
ln -sf /dev/[my-cd] /dev/archiso ... As I said, I were GOING TO! Didn't happened! I went straight into archiso login prompt!
Anyone got a clue why that happend after 4 fails? *Maby I forgot some retries, but that's not the point*

jeypeyy · 2009-10-30 13:04:24

I have the same problem with the Netinstall CD. I would like to fix the problem, but it's very hard when the keymap isn't right. I have a swedish keyboard, can I change the keymap in ramfs?

It's sad, I've been using mainstream Linux-distros (primarly ubuntu) in almost two years now and wanted to go further a little bit. But when I try there is a problem with it. But I guess I'll be really happy when it's solved. The idea with Arch is awesome.

Arch Linux

#1 2009-08-11 13:37:14

[solved] Boot device didn't show up after 30 seconds...

#2 2009-08-11 21:22:27

Re: [solved] Boot device didn't show up after 30 seconds...

#3 2009-08-11 21:22:28

Re: [solved] Boot device didn't show up after 30 seconds...

#4 2009-08-12 00:37:15

Re: [solved] Boot device didn't show up after 30 seconds...

#5 2009-08-12 04:00:28

Re: [solved] Boot device didn't show up after 30 seconds...

#6 2009-08-12 09:02:19

Re: [solved] Boot device didn't show up after 30 seconds...

#7 2009-08-12 11:59:08

Re: [solved] Boot device didn't show up after 30 seconds...

#8 2009-08-12 12:38:26

Re: [solved] Boot device didn't show up after 30 seconds...

#9 2009-08-12 13:11:05

Re: [solved] Boot device didn't show up after 30 seconds...

#10 2009-08-12 17:02:50

Re: [solved] Boot device didn't show up after 30 seconds...

#11 2009-08-13 03:29:59

Re: [solved] Boot device didn't show up after 30 seconds...

#12 2009-08-13 11:43:58

Re: [solved] Boot device didn't show up after 30 seconds...

#13 2009-08-14 14:44:05

Re: [solved] Boot device didn't show up after 30 seconds...

#14 2009-08-15 10:45:39

Re: [solved] Boot device didn't show up after 30 seconds...

#15 2009-08-15 22:13:53

Re: [solved] Boot device didn't show up after 30 seconds...

#16 2009-08-18 15:27:28

Re: [solved] Boot device didn't show up after 30 seconds...

#17 2009-08-20 01:35:58

Re: [solved] Boot device didn't show up after 30 seconds...

#18 2009-08-24 17:05:50

Re: [solved] Boot device didn't show up after 30 seconds...

#19 2009-08-24 17:50:43

Re: [solved] Boot device didn't show up after 30 seconds...

#20 2009-09-05 03:17:36

Re: [solved] Boot device didn't show up after 30 seconds...

#21 2009-09-27 13:47:01

Re: [solved] Boot device didn't show up after 30 seconds...

#22 2009-10-01 05:25:14

Re: [solved] Boot device didn't show up after 30 seconds...

#23 2009-10-15 22:57:50

Re: [solved] Boot device didn't show up after 30 seconds...

#24 2009-10-21 21:34:27

Re: [solved] Boot device didn't show up after 30 seconds...

#25 2009-10-30 13:04:24

Re: [solved] Boot device didn't show up after 30 seconds...

Board footer