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

jeypeyy · 2009-11-01 10:55:57

no one?

blueviper · 2009-11-06 15:40:19

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!

Just tried this but I'm getting this

ramfs$ ln-sf /dev/sd[x] /dev/archiso
ramfs$ mount -t vfat /dev/archiso /bootmnt
mount: No such file or directory

is x supposed the be the usb drive letter? if so how do I find out what mine is?

skiffcz · 2009-11-08 02:28:22

Solution for USB dongle install from winXP on EeePC 901 using 2009.08-core:

1, download .img version compatible with dd method, unetbootin and gparted live
2, format your dongle to fat32 and use unetbootin to install gparted on it
3, copy your archlinux-whatever.img to the dongle (you may use existing partitions somewhere in your computer instead ofc)
4, reboot to USB into gparted in "ram" mode (so the dongle can be unmounted)
5, mount your dongle and copy arch image to gparted virtual partition (so you can use it later)
6, unmount dongle and use gparted to format it to ext3
7, dd the image onto our freshly formatted dongle
8, reboot to USB again and enjoy

Hope this helps someone

lustikus · 2009-11-10 11:57:29

I also had this problem on my new notebook, but finally solved it.
Here are my experiences, I hope it helps someone:

My other Desktop is a Win7 64bit System and I tried the following to build a USB install (2009.08 x86_64 netinstall):

1. unetbootin
I tried both .img and .iso files (x86_64), didn't work.
I also let netbootin directly download an .iso, tried with formatting the stick and without it, no success.

2. I tried almost all the suggestions in this thread, ..fail

3. I downloaded DD for Windows, executed in a CMD Prompt (as admin of course) and followed the instructions in the arch install guide.... fail (machine hangs at grub start)

4. I downloaded Disk Imager (as suggested in the install guide), but this sh** completely f*cked up my USB Stick... DO NOT USE THIS
my stick was 4gb and now is 200mb after this..

5. my last hope: "The Flashnul Way"
I hesitated to download this program because its site looks somewhat suspicious and the program seems outdated, but IT WORKED LIKE A CHARM and I finally got a working install USB Stick with no problem!

So if you have problems with your usb install, definitely try this!

prometej · 2009-12-20 10:12:48

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 know this is an older post, just wanted to thank for this tip.
This helped me too while installing Arch (2009.08 - x86_64) from my Pioneer DVR-216DBK (SATA) DVD-RW on Gigabyte MA770-UD3 (rev 2.0) motherboard.

Thanx.

kank · 2010-01-30 14:27:19

brain0 wrote:

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

Is this really worth all the problems it's been causing?
There's a number of ways proposed here (http://wiki.archlinux.org/index.php/Ins … lash_drive) for an USB install, not all of them use dd. I always used unetbootin when using windows for some reason - that's useless now.

pistol-mcgee · 2010-02-08 17:35:21

Tried everything in this gude via CD and USB. Nothing worked

Both .img and .iso (for usb and cd respectively) Alas nothing worked, just keeps saying it cant find the iso img.

anything else i can try??

Nothing special about hardware:
Q6600 @ 3ghz
EVGA 750i SLI FTW
4gb corsair ram
3 SATA HDD's
1 EIDE CD Rom
1 SATA DVD-RW drive (A POS i dont use it)
Nvidia 8800 GTS 512
Creative X-fi Titanium PCI-E

Halp?

madcircle · 2010-05-09 20:15:32

lustikus wrote:

I also had this problem on my new notebook, but finally solved it.
Here are my experiences, I hope it helps someone:
My other Desktop is a Win7 64bit System and I tried the following to build a USB install (2009.08 x86_64 netinstall):
1. unetbootin
I tried both .img and .iso files (x86_64), didn't work.
I also let netbootin directly download an .iso, tried with formatting the stick and without it, no success.
2. I tried almost all the suggestions in this thread, ..fail
3. I downloaded DD for Windows, executed in a CMD Prompt (as admin of course) and followed the instructions in the arch install guide.... fail (machine hangs at grub start)
4. I downloaded Disk Imager (as suggested in the install guide), but this sh** completely f*cked up my USB Stick... DO NOT USE THIS
my stick was 4gb and now is 200mb after this..
5. my last hope: "The Flashnul Way"
I hesitated to download this program because its site looks somewhat suspicious and the program seems outdated, but IT WORKED LIKE A CHARM and I finally got a working install USB Stick with no problem!
So if you have problems with your usb install, definitely try this!

Thank you, thank you, thank you!

Sitting on a NAS with an intel d510 motherboard with atom 330 cpu, no optical devices so usb was my best bet, had the exact same issues as you had. DD for Win with USB image didn't work, GRUB loaded but froze, unetbootin gave me a boot menu with the isolinux bootloader but half way through booting it couldn't find the archiso and dropped me into $ramfs. The Flashnul way however worked like a charm, GRUB worked and the system booted into live arch without a hitch! So I second that flashnul recommendation if anyone is having problems installing from USB!

echeddar · 2010-05-27 03:18:07

Hi, I'm very much a newb, so please excuse my utter ignorance of what I'm doing.

I've tried the suggestions from Chiong without getting past the 30-second timeout.

I think my problem is the label thing mentioned by cwjiof et al; I created my USB iso using
1st) UNetBootin and
2nd) redid it with flashnul when I saw that many people who had the timeout problem had used UNetBootin

I'm not sure how to ask the linux system what it thinks the label on the USB drive is. Is it the same as the label in Vista? (the USB is simply labeled E: in Vista; if I click on the properties, there's a blank where I can put a volume label, but there's nothing there.) If by "label," I'm supposed to tell it sd[x] I'm a bit at a loss there. I searched around and found this out:

echo /dev/sd* gives me six answers for this netbook (Dell Mini 10v): sda sda1 sda2 sdb sdb1 sdc

cat /proc/scsi/scsi gives three devices, scsi0 is ATA (hdd), scsi2 is USB, and scsi3 is Multi-card, (SD reader)

ls -lF /dev/disk/by-uuid gives me some long names, but still doesn't make it clear which drive is which.
Is there a modifier for ls or echo which will let me see the size of the drives? That would be one way to tell them apart. The USB is only 8GB.

Anyway, since I couldn't tell, I set about manually editing the syslinux.cfg file on the USB six times, each time setting it to a different sd* drive, and then booting it to see what happened. About the 5th time through, I noticed that there are two instances of "archisolabel=" in the file, one under unetbootindefault, and one under ubnentry0. I had only been changing the latter.

Incidentally, I don't know why my USB syslinux file still says netbootin in it after i ran flashnul on it, perhaps I failed to do that properly.

So I changed _both_ references to archisolabel in the syslinux.cfg file on the USB to =sdb1, and still no joy.

Thanks in advance for any ideas.

echeddar · 2010-05-28 12:02:28

Solution: well, it might not really be a solution for everyone, but I eventually installed Linux Mint, which "just works." The GUI, wireless and touch pad all work with the default install on the Dell Mini 10v. I'd like to get my Linux legs under myself a bit, then maybe come back to Arch, but for now I'm up and running. Thanks!
echeddar

KlavKalashj · 2010-06-22 15:39:59

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

Thank you very much! I used this command, only changed /dev/sr0 to /dev/sdb1 and now I have a working arch-i586 on my Via C3

gdw · 2010-07-04 20:46:38

Adjusting the label parameter on the grub boot screen worked for me.

Armon · 2010-08-23 01:01:17

Hey, I've tried most of the commands in this topic and no go.

I'm sure there's an easy way to get this boot rolling along, but I am not too familiar with booting new OS's. I'm determined though, Arch seems wonderful.

The .iso file (archlinux-2010.05-netinstall-x86_64) is located on my C drive: "C:\Documents and Settings\Administrator\My Documents\Downloads" If that matters.

http://img444.imageshack.us/img444/6258/pic0068l.jpg

http://img413.imageshack.us/img413/5271/pic0067is.jpg

So I tried 'ln -sf /dev/scsi0 /dev/archiso' as well as a few others, but none work! What am I doing wrong!?

darknean · 2010-09-11 19:16:34

Here's what I did to make it work.

- I formatted my USB flash drive in FAT32 and labelled it ARCH_201005
- I used the following tool on Win7: unetbootin-windows-471.exe
- I used the following ISO: archlinux-2010.05-core-x86_64.iso
- Boot my linux box with my USB flash drive.

The fix is the label name as I found that it was doing a by-label search when it failed.

Hope this can help someone.

cesura · 2010-09-11 19:22:18

echeddar wrote:

Solution: well, it might not really be a solution for everyone, but I eventually installed Linux Mint, which "just works." The GUI, wireless and touch pad all work with the default install on the Dell Mini 10v. I'd like to get my Linux legs under myself a bit, then maybe come back to Arch, but for now I'm up and running. Thanks!
echeddar

Please, it's obvious that you are trying to advertise for Linux Mint. Arch isn't meant to "just work".

natostanco · 2010-09-27 14:42:58

darknean wrote:

Here's what I did to make it work.
- I formatted my USB flash drive in FAT32 and labelled it ARCH_201005

This.

nucleuswizard · 2010-10-01 20:33:30

darknean wrote:

Here's what I did to make it work.
- I formatted my USB flash drive in FAT32 and labelled it ARCH_201005
- I used the following tool on Win7: unetbootin-windows-471.exe
- I used the following ISO: archlinux-2010.05-core-x86_64.iso
- Boot my linux box with my USB flash drive.
The fix is the label name as I found that it was doing a by-label search when it failed.
Hope this can help someone.

Thanks,this solved

Silence · 2010-10-15 19:07:23

At the ramfs$ prompt:
[ramfs /]# udevadm trigger
[ramfs /]# exit

seehymeh · 2010-10-21 02:47:52

natostanco wrote:

darknean wrote:
Here's what I did to make it work.
- I formatted my USB flash drive in FAT32 and labelled it ARCH_201005
This.

This is definitely the part that fixed it for me. Except, i was already sitting at the terminal so I typed:

ramfs$ mv /dev/disk/by-label/[name of your device] /dev/disk/by-label/ARCH_201005
ramfs$ exit

and that's it. None of the rest of the commands in this thread made a difference for me. I even restarted the install to try it again and simply renaming the device to ARCH_201005 does it.

ps. Installed from USB device on eeepc 901

Meskarune · 2011-04-28 02:15:30

I was just having this problem trying to install arch on my netbook. The solution was to change the name of the usb device to ARCH_201005 and I no longer at any issues or errors. (posting this just in case someone else runs into the same problem)

murr4y · 2011-05-22 00:42:04

Hi,

I'm trying to install Arch to my netbook but I get the same error.
I tried every solution here but none of them works.
When I do "ln -s /dev/disk/by-label/ARCH... /dev/archiso" and "exit" I get the kernel panic.
(I also set the label to ARCH_201005)
I tried installing with Flashnul but that seems to 'break' the stick because there's just unallocated space afterwards.
The same happens when I try to dd the image to usb.
I already installed a distro with the usb stick so it's not totally useless.

Something else I might try?

jimmiebtlr · 2011-09-18 22:35:10

Silence wrote:

At the ramfs$ prompt:
[ramfs /]# udevadm trigger
[ramfs /]# exit

This was the only one that worked for me, thanks slience.

dreadz · 2011-11-23 21:42:58

Hi
I experienced same problem as the titles describes after following the arch wiki guide on how to install on usb (Old Method from ISO, deprecated) using Fedora 15.
After changing archisolabel= to appropriate name (usbdisk) i've got it up and running.

Many Thanks !!!

p.s. i had the problem occure on a EEEPC 1215n with a Win7 primary installed.

lothar_m · 2012-02-19 17:50:59

darknean wrote:

Here's what I did to make it work.
- I formatted my USB flash drive in FAT32 and labelled it ARCH_201005
- I used the following tool on Win7: unetbootin-windows-471.exe
- I used the following ISO: archlinux-2010.05-core-x86_64.iso
- Boot my linux box with my USB flash drive.
The fix is the label name as I found that it was doing a by-label search when it failed.
Hope this can help someone.

thanks for this info.
that has saved my day.

installing arch201108 netinstall iso in a eeepc 901.

fsckd · 2012-02-19 19:33:42

I'm closing this. My reasons are,

Thread is old. It was marked solved in 2009. While no necro-bumping has taken place, several posts are no longer relevant.
For USB install images, the solution (changing the label) is mentioned in the wiki.
The last few comments are just notes of thanks. There's no harm in that but it's not a sufficient reason to keep this thread alive.

Arch Linux

#26 2009-11-01 10:55:57

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

#27 2009-11-06 15:40:19

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

#28 2009-11-08 02:28:22

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

#29 2009-11-10 11:57:29

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

#30 2009-12-20 10:12:48

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

#31 2010-01-30 14:27:19

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

#32 2010-02-08 17:35:21

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

#33 2010-05-09 20:15:32

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

#34 2010-05-27 03:18:07

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

#35 2010-05-28 12:02:28

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

#36 2010-06-22 15:39:59

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

#37 2010-07-04 20:46:38

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

#38 2010-08-23 01:01:17

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

#39 2010-09-11 19:16:34

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

#40 2010-09-11 19:22:18

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

#41 2010-09-27 14:42:58

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

#42 2010-10-01 20:33:30

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

#43 2010-10-15 19:07:23

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

#44 2010-10-21 02:47:52

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

#45 2011-04-28 02:15:30

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

#46 2011-05-22 00:42:04

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

#47 2011-09-18 22:35:10

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

#48 2011-11-23 21:42:58

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

#49 2012-02-19 17:50:59

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

#50 2012-02-19 19:33:42

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

Board footer