[arch-general] Unable to Install Arch on Server
I have a Dell server (Power Edge 1855) blade that I am trying to install Arch Linux on. I have no problems installing / running Debian, CentOS, or Ubuntu on this hardware but when I try to boot from Arch CD (2009.08 Netinst or Core), I get an error: Waiting for boot device... 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're finished. ramfs$ I also built a new PC from home with parts purchased from Newegg.com. The machine runs perfect with almost any flavor of Linux / Windows but when I go to install Arch Linux as above, I get the same error. I have done md5 sum check on my ISO image and used the CD on other servers fine. I know the disk / image is not the problem. Anyone know how I can resolve this? Here is a link to the screenshot of the error: http://img691.imageshack.us/img691/6127/errorua.png
On Wed, Dec 2, 2009 at 12:59, Carlos Williams <carloswill@gmail.com> wrote:
I have a Dell server (Power Edge 1855) blade that I am trying to install Arch Linux on. I have no problems installing / running Debian, CentOS, or Ubuntu on this hardware but when I try to boot from Arch CD (2009.08 Netinst or Core), I get an error:
Waiting for boot device... 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're finished. ramfs$
I also built a new PC from home with parts purchased from Newegg.com. The machine runs perfect with almost any flavor of Linux / Windows but when I go to install Arch Linux as above, I get the same error. I have done md5 sum check on my ISO image and used the CD on other servers fine. I know the disk / image is not the problem. Anyone know how I can resolve this?
Here is a link to the screenshot of the error:
I think that usually means that your grub+initrd combo is broken somewhere. Post your configs?
On Wed, Dec 2, 2009 at 1:10 PM, Daenyth Blank <daenyth+arch@gmail.com> wrote:
I think that usually means that your grub+initrd combo is broken somewhere. Post your configs?
There are no configs. I am trying to do a fresh install. There are no Grub configs...yet. I just downloaded the 2009.08 netinst ISO and burned it to a CDROM. The error you see is when I boot from the CDROM.
On Wed, Dec 2, 2009 at 13:15, Carlos Williams <carloswill@gmail.com> wrote:
On Wed, Dec 2, 2009 at 1:10 PM, Daenyth Blank <daenyth+arch@gmail.com> wrote:
I think that usually means that your grub+initrd combo is broken somewhere. Post your configs?
There are no configs. I am trying to do a fresh install. There are no Grub configs...yet. I just downloaded the 2009.08 netinst ISO and burned it to a CDROM. The error you see is when I boot from the CDROM.
Ah.. Hmm. I don't really know. That looks like grub has passed and you're into the initrd though. What type of cdrom device are you using? It looks like it can't find the cd to mount it, and that's what's failing. You may be able to manually mount it past that, I'm not sure. Could also try booting from a usb image instead of a cd image.
On Wed, Dec 2, 2009 at 1:15 PM, Carlos Williams <carloswill@gmail.com> wrote:
On Wed, Dec 2, 2009 at 1:10 PM, Daenyth Blank <daenyth+arch@gmail.com> wrote:
I think that usually means that your grub+initrd combo is broken somewhere. Post your configs?
There are no configs. I am trying to do a fresh install. There are no Grub configs...yet. I just downloaded the 2009.08 netinst ISO and burned it to a CDROM. The error you see is when I boot from the CDROM.
Try the ISOLINUX ISO and see if that boots. Your machine might not like booting from a CD via GRUB.
On Wed, Dec 2, 2009 at 1:30 PM, Ray Kohler <ataraxia937@gmail.com> wrote:
Try the ISOLINUX ISO and see if that boots. Your machine might not like booting from a CD via GRUB.
Boots fine.
Am Wed, 2 Dec 2009 13:30:43 -0500 schrieb Ray Kohler <ataraxia937@gmail.com>:
On Wed, Dec 2, 2009 at 1:15 PM, Carlos Williams <carloswill@gmail.com> wrote:
On Wed, Dec 2, 2009 at 1:10 PM, Daenyth Blank <daenyth+arch@gmail.com> wrote:
I think that usually means that your grub+initrd combo is broken somewhere. Post your configs?
There are no configs. I am trying to do a fresh install. There are no Grub configs...yet. I just downloaded the 2009.08 netinst ISO and burned it to a CDROM. The error you see is when I boot from the CDROM.
Try the ISOLINUX ISO and see if that boots. Your machine might not like booting from a CD via GRUB.
Maybe I should add here that the problem is that the link /dev/archiso which points to the CD/DVD drive is not created by a udev rule. Executing `udevadm trigger` at the ramfs$ prompt creates this link, which should be created automatically. Executing `exit` at the ramfs$ prompt after that continues booting. So I don't think that this has anything to do with the grub+initrd combo. I guess it has something to do with udev, some hooks or the kernel modules. Heiko
Am Wed, 2 Dec 2009 12:59:24 -0500 schrieb Carlos Williams <carloswill@gmail.com>:
I have a Dell server (Power Edge 1855) blade that I am trying to install Arch Linux on. I have no problems installing / running Debian, CentOS, or Ubuntu on this hardware but when I try to boot from Arch CD (2009.08 Netinst or Core), I get an error:
Waiting for boot device... 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're finished. ramfs$
I also built a new PC from home with parts purchased from Newegg.com. The machine runs perfect with almost any flavor of Linux / Windows but when I go to install Arch Linux as above, I get the same error. I have done md5 sum check on my ISO image and used the CD on other servers fine. I know the disk / image is not the problem. Anyone know how I can resolve this?
Here is a link to the screenshot of the error:
I have the same problem. See my bug report: http://bugs.archlinux.org/task/17231 Heiko
Am Mittwoch 02 Dezember 2009 schrieb Heiko Baums:
Am Wed, 2 Dec 2009 12:59:24 -0500
schrieb Carlos Williams <carloswill@gmail.com>:
I have a Dell server (Power Edge 1855) blade that I am trying to install Arch Linux on. I have no problems installing / running Debian, CentOS, or Ubuntu on this hardware but when I try to boot from Arch CD (2009.08 Netinst or Core), I get an error:
Waiting for boot device... 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're finished. ramfs$
I also built a new PC from home with parts purchased from Newegg.com. The machine runs perfect with almost any flavor of Linux / Windows but when I go to install Arch Linux as above, I get the same error. I have done md5 sum check on my ISO image and used the CD on other servers fine. I know the disk / image is not the problem. Anyone know how I can resolve this?
Here is a link to the screenshot of the error:
I have the same problem. See my bug report: http://bugs.archlinux.org/task/17231
Heiko
You could try archboot isos linked here: ftp://ftp.archlinux.org/iso/archboot greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
Am Thu, 3 Dec 2009 20:09:36 +0100 schrieb Tobias Powalowski <t.powa@gmx.de>:
You could try archboot isos linked here: ftp://ftp.archlinux.org/iso/archboot
This iso boots fine. But this doesn't fix the problem with the other isos. ;-) And the previous core and netinstall LiveCDs (2009.02 and before) booted fine, too. So this is an issue with this LiveCD version. I assume the problem is either with the hooks, udev, the udev rules or the init scripts of the initrd. Heiko
Am Freitag 04 Dezember 2009 schrieb Heiko Baums:
Am Thu, 3 Dec 2009 20:09:36 +0100
schrieb Tobias Powalowski <t.powa@gmx.de>:
You could try archboot isos linked here: ftp://ftp.archlinux.org/iso/archboot
This iso boots fine. But this doesn't fix the problem with the other isos. ;-)
And the previous core and netinstall LiveCDs (2009.02 and before) booted fine, too. So this is an issue with this LiveCD version. I assume the problem is either with the hooks, udev, the udev rules or the init scripts of the initrd.
Heiko
Sure but at least you can install arch now :) greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
Am Sat, 5 Dec 2009 07:48:13 +0100 schrieb Tobias Powalowski <t.powa@gmx.de>:
Sure but at least you can install arch now :)
I can install Arch with the core and netinstall isos, too. I just need to execute `udevadm trigger` and `exit` at the ramfs$ prompt. Then it continues booting. ;-) I looked at the hooks and udev rules of the LiveCDs initrd but couldn't find anything wrong. But they are quite different to the hooks and udev rules of the LiveCDs 2009.02 which worked for me. Somehow I still suspect a missing module. Greetings, Heiko
On 05.12.2009 07:48, Tobias Powalowski wrote:
Am Freitag 04 Dezember 2009 schrieb Heiko Baums:
Am Thu, 3 Dec 2009 20:09:36 +0100
schrieb Tobias Powalowski <t.powa@gmx.de>:
You could try archboot isos linked here: ftp://ftp.archlinux.org/iso/archboot
This iso boots fine. But this doesn't fix the problem with the other isos. ;-)
And the previous core and netinstall LiveCDs (2009.02 and before) booted fine, too. So this is an issue with this LiveCD version. I assume the problem is either with the hooks, udev, the udev rules or the init scripts of the initrd.
Heiko
Sure but at least you can install arch now :) greetings tpowa
You could try this one (http://phraktured.net/archlinux-2009.12-netinstall-x86_64.iso) we are currently preparing for the next release. It uses a newer kernel and isolinux. Please tell us the results. That image I linked is experimental of course. -- Sven-Hendrik
Am Sat, 05 Dec 2009 14:30:10 +0100 schrieb Sven-Hendrik Haase <sh@lutzhaase.com>:
You could try this one (http://phraktured.net/archlinux-2009.12-netinstall-x86_64.iso) we are currently preparing for the next release. It uses a newer kernel and isolinux. Please tell us the results. That image I linked is experimental of course.
Unfortunately the same problem. It waits 30 seconds for /dev/archiso and switches to ramfs$ prompt. The workaround with `udevadm trigger` and `exit` still works. Greetings, Heiko
Am Sat, 05 Dec 2009 14:30:10 +0100 schrieb Sven-Hendrik Haase <sh@lutzhaase.com>:
You could try this one (http://phraktured.net/archlinux-2009.12-netinstall-x86_64.iso) we are currently preparing for the next release. It uses a newer kernel and isolinux. Please tell us the results. That image I linked is experimental of course.
Could you, please, tell me how I can build the iso myself? I tried it with the method djgera explained to me on flyspray (http://bugs.archlinux.org/task/17231?project=6): # mkarchroot /tmp/coco base git cdrkit squashfs-tools devtools make pwgen # mkarchroot -r /bin/bash /tmp/coco edit the mirrorlist for pacman # cd /tmp # git clone git://projects.archlinux.org/archiso.git # cd archiso/archiso # make install # cd ../configs/install-iso # make net-iso Last step stops with an error, because it can't find isolinux.img or something like this. I forgot to copy the message. I want to test something because I have a new suspicion. It could be the lines ACTION!="add...", GOTO="..." I once tried to write two udev rules to set two different links to /dev depending on which stick was plugged in. One stick should be added as /dev/usbkey and only as /dev/usbkey and any other stick should be added as /dev/usbstick and only as /dev/usbstick. So I've created a file 00-usbkey.rules with this rule: SUBSYSTEMS=="usb", KERNEL=="sd?1", ATTRS{serial}=="241F44065F1F0032", NAME="%k", SYMLINK+="usbkey" and a file 01-usbstick.rules with this rule: SUBSYSTEMS=="usb", KERNEL=="sd?[0-9]", ATTRS{serial}!="<serial number>", NAME="%k", SYMLINK+="usbstick%n" Now the stick which should added only as /dev/usbkey is added as /dev/usbkey but also as /dev/usbstick1. Any other stick is added only as /dev/usbstick1. I was always able to use my scanner with my unprivileged user. Now I wanted to scan something after a longer time but xsane and scanimage -L couldn't find the scanner. It could only be found by root. During the search for the reason I found the file /lib/udev/rules.d/53-sane.rules.d which contains the line: ACTION!="add", GOTO="libsane_rules_end" After commenting this line and running `udevadm trigger` the unprivileged user can find the scanner again. But it still can be found after commenting out this line again and rebooting the system. So I have the suspicion that "!=" in udev rules don't work or at least not as expected. I'd like to build the iso by myself and remove the lines ACTION!="add...", GOTO="..." from the udev rules. I can be completely wrong and it's possible that I made a mistake in my udev rules but I think it's worth testing it. Greetings, Heiko
On 05.12.2009 17:39, Heiko Baums wrote:
Am Sat, 05 Dec 2009 14:30:10 +0100 schrieb Sven-Hendrik Haase <sh@lutzhaase.com>:
You could try this one (http://phraktured.net/archlinux-2009.12-netinstall-x86_64.iso) we are currently preparing for the next release. It uses a newer kernel and isolinux. Please tell us the results. That image I linked is experimental of course.
Could you, please, tell me how I can build the iso myself?
I tried it with the method djgera explained to me on flyspray (http://bugs.archlinux.org/task/17231?project=6):
# mkarchroot /tmp/coco base git cdrkit squashfs-tools devtools make pwgen # mkarchroot -r /bin/bash /tmp/coco edit the mirrorlist for pacman # cd /tmp # git clone git://projects.archlinux.org/archiso.git # cd archiso/archiso # make install # cd ../configs/install-iso # make net-iso
Last step stops with an error, because it can't find isolinux.img or something like this. I forgot to copy the message.
I want to test something because I have a new suspicion.
It could be the lines ACTION!="add...", GOTO="..."
I once tried to write two udev rules to set two different links to /dev depending on which stick was plugged in. One stick should be added as /dev/usbkey and only as /dev/usbkey and any other stick should be added as /dev/usbstick and only as /dev/usbstick.
So I've created a file 00-usbkey.rules with this rule: SUBSYSTEMS=="usb", KERNEL=="sd?1", ATTRS{serial}=="241F44065F1F0032", NAME="%k", SYMLINK+="usbkey"
and a file 01-usbstick.rules with this rule: SUBSYSTEMS=="usb", KERNEL=="sd?[0-9]", ATTRS{serial}!="<serial number>", NAME="%k", SYMLINK+="usbstick%n"
Now the stick which should added only as /dev/usbkey is added as /dev/usbkey but also as /dev/usbstick1. Any other stick is added only as /dev/usbstick1.
I was always able to use my scanner with my unprivileged user. Now I wanted to scan something after a longer time but xsane and scanimage -L couldn't find the scanner. It could only be found by root.
During the search for the reason I found the file /lib/udev/rules.d/53-sane.rules.d which contains the line: ACTION!="add", GOTO="libsane_rules_end"
After commenting this line and running `udevadm trigger` the unprivileged user can find the scanner again. But it still can be found after commenting out this line again and rebooting the system.
So I have the suspicion that "!=" in udev rules don't work or at least not as expected.
I'd like to build the iso by myself and remove the lines ACTION!="add...", GOTO="..." from the udev rules.
I can be completely wrong and it's possible that I made a mistake in my udev rules but I think it's worth testing it.
Greetings, Heiko
Why of course, just follow my guide: http://wiki.archlinux.org/index.php/Archiso I always update that guide with most recent upstream info so you should be good. Just go to configs/syslinux and "make" and it should work right away without further stuff you have to do. You can change the files in the overlay dir to make your udev changes. Please report any errors and any success. -- Sven-Hendrik
participants (6)
-
Carlos Williams
-
Daenyth Blank
-
Heiko Baums
-
Ray Kohler
-
Sven-Hendrik Haase
-
Tobias Powalowski