Installing Arch in a chroot via chroagh

I figured you guys could still help me since I am installing the x86 version of Arch, just in a chroot. I had it working before but I upgraded some packages and removed a few and then when I rebooted my Chromebook later and then tried to start up KDE, X wouldn't start. I removed the Arch chroot and tried to set it up again but now it's failing to set up the chroot. I've tried going in and out of developer mode (which wipes settings) and that didn't work, I even tried to powerwash it but that didn't fix it either.
This is the tool I'm using to install Arch
Here's the error I run into:
+ env -i TERM=xterm chroot /var/run/crouton/usr/local/chroots/arch /prepare.sh
+ export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
+ PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
+ '[' '!' unspecified = unspecified -a unspecified = unspecified ']'
+ PKGEXT=tar.xz
+ DISTROAKA=arch
+ bootstrappkglist=/crouton-bootstrap-pkg
+ '[' -r /crouton-bootstrap-pkg ']'
+ '[' -n 'http://mirrors.kernel.org/archlinux/$repo/os/$arch' -a 'http://mirrors.kernel.org/archlinux/$repo/os/$arch' '!=' unspecified ']'
+ echo 'Server = http://www.example.com/'
++ cat /crouton-bootstrap-pkg
+ pacman -S --nodeps --nodeps --asdeps --noconfirm --force bash gawk pacman grep util-linux readline glibc mpfr libarchive curl gpgme pacman-mirrorlist archlinux-keyring pcre pam shadow coreutils ncurses linux-api-headers tzdata filesystem gmp acl attr bzip2 expat lzo2 openssl xz zlib krb5 libssh2 libgpg-error pth gnupg db cracklib libtirpc pambase libcap iana-etc gcc-libs libldap keyutils libksba libgcrypt libassuan pinentry dirmngr libgssglue libsasl
pacman: error while loading shared libraries: libcom_err.so.2: cannot open shared object file: No such file or directory
+ ret=127
+ [ 2 = 2 ]
+ [ 127 = 0 -a -f /var/run/crouton/usr/local/chroots/arch/prepare.sh ]
+ [ ! 127 = 0 ]
+ error 127 Failed to complete chroot setup.
+ local ecode=127
+ shift
+ echo Failed to complete chroot setup.
Failed to complete chroot setup.
+ exit 127
+ set +e
+ trap - INT HUP TERM 0
+ sh -e /home/chronos/user/Downloads/drinkcat-chroagh-9f3926e/host-bin/unmount-chroot -yc /usr/local/chroots arch
Unmounting /usr/local/chroots/arch...
+ stty echo
+ set +e
+ trap - INT HUP TERM 0
+ umount -l /tmp/main.sh.yFY
+ rm -rf --one-file-system /tmp/main.sh.yFY
+ sh installer/../host-bin/unmount-chroot -y -c /usr/local/chroots arch
+ stty echo
I can paste more if necessary, it's easily reproducible.
Last edited by brando56894 (2014-01-22 02:26:57)

https://wiki.archlinux.org/index.php/In … ting_Linux

Similar Messages

Install Arch on hard disk connected via USB

Hi,
anyone tried this?
I had Arch Linux installed on hdd in my desktop, now I've connected this hdd to laptop via USB and I want to start system from it. I need to reinstall lilo, because I get kernel panic after booting from USB.
I don't know how to do this, I boot laptop from Archie Live CD and:
mount /dev/sda2 /mnt/m
chroot /mnt/m
editing /etc/lilo.conf
lilo
and I get error: Failed stat("/dev/dsa2")
Anyone know how to install lilo on hdd connected via USB?
thanks for any help

i know it's an old thread, but perhaps it'll help someone else later...
i first tried installing from cd, with some problems, using an arch 0.7 cd.
then i tried it with a newer one (arch 0.7.1) which did'nt recognize the external harddisk and my network device...
so i tried a ftp install from 0.7 cd - without problems.
then after trying to boot i got also this kernel panic, because the usb drive wasn't accessible like this.
with following steps i got it running:
boot from live cd (e.g. archie)
create a folder in /mnt/
mount usb drives partition with the installation there
chroot to mounted folder
edit /etc/mkinitrd.conf
configure it (usb,scsi,ide), there are useful comments in the file...
save it and run mkinitrd -auto
then edit and save /etc/lilo.conf as described in the wiki: http://wiki.archlinux.org/index.php/Initrd
installing lilo from the chrooted system doesn't work. so do this:
type exit (to leave chroot)
cd /
mv /etc/ /etcold/
mv /boot/ /bootold/
ln -s /mnt/yourmountfolder/boot
ln -s /mnt/yourmountfolder/etc
lilo
(if there's an other, easyer way to install lilo, let me know)
and then reboot...

Installing arch - internet via openVPN

Hi guys,
I finally want to install arch. However, I can only establish a internet connection via openVPN (the university provides internet service at my dorm). So how do i do this?
How I would do it:
Stop dhcpcd service (necessary?)
Identify Ethernet controller and activate it (both steps according to this.
Install openVPN from USB stick if necessary (I read somewhere that openVPN is available on the install media?)
Establish openVPN connection according to uni's instructions
But what do I do once I installed the base system and chrooted? Which one of the following is the correct one? Plus I need to install openVPN via pacman -S openvpn, right?
Thanks for your help, I hope I can finally use arch soon!

I just wanted to report back, I performed the above and was able to install Arch remotely via SSH. Thank you for your confirmation, it was what I needed.
--nixIT

Failure to install Arch Linux via netinstall AIF; PGP key issues

Hello,
I'm am attempting a fresh install Arch Linux on a clean machine: Dell 1420, 4GB RAM. I am using the archlinux-2012.02.09_04-00-01-netinstall-dual.iso installer.
Installation progresses nicely through the package selection (I choose core, core-dev, xfce, and xorg packages only, to keep it simple for now). The packages download quickly, and then the installation fails during installation indicating that none of the PGP keys are known for any of the downloaded files. The process essentially aborts and I press 'Continue' returning me to the main menu. I have repeated this process several times.
What needs to be done to install Arch Linux?
Thanks.

Hi,
Thanks, I have been through the Beginners Guide. I just want to get Arch Linux to "start" with a very basic GUI. during one of my installation iterations I did install only 'core' files, but the same failure occurred. so I'm at a loss as to how to get even a basic installation to take hold. Thoughts on the pgp key issues?
Thanks.
Update: I've switched to using the default net installer (2011.08.19) and the installation succeeded!
Last edited by zaleksf (2012-02-12 05:12:32)

Installing Arch on MacBook Air - EFI issues

Hi, all.
I have a mid-2012 13" Air and I want to install Arch on it as the only OS.
Now, I've tried following guides on the wiki and in the forum, and I tried to install it with grub2-efi loader, but after numerous attempts I either got nothing, or got a system that had a big delay with the bootloader. There are two or three articles on the topic: GRUB2, MacBook guide and EFI guide, but no straightforward guide, just these three pages that crossreference each other in all the wrong places What is the best way to install Arch on a Mac?
I understand that installing rEFIt can simplify things, but I want to find a way around it, since I'll only be using one OS, and I really dislike the Qt3 looks of rEFIt.
Some articles say that LILO is simpler to setup that grub on an EFI machine - is that true?
Furthermore, some discussions here mention that I should use archboot rather than the default installation image.
So, could anyone please give me a simple list of steps?
Last edited by ilembitov (2012-11-04 00:45:48)

Hi,
I'm using also Arch on a MacBook, but with rEFIt. Never tried to to remove OS X complete, because I want to have the chance to upgrade EFI and Firmware itself via Mac OS X Update.
But for a clean grub_efi installation you have to create and mount an "efi partition" and install some boot files here. Check for detailed information those 2 wiki pages:
https://wiki.archlinux.org/index.php/UEFI
https://wiki.archlinux.org/index.php/UEFI_Bootloaders
Afterwards you can start with the grub installation.
Simple Steps:
create partitions on disk
mount partitions
Install arch system ( https://wiki.archlinux.org/index.php/Beginners%27_Guide )
prepare chroot environment
jump into crhoot environment
configure system
configure grub2_efi (default files /etc/default/grub)
prepare efi partition (dir and files)
install grub2_efi
That should it be...
As I already said, never tried it without rEFIt, but its not simple, because Apple is not using a standard UEFI, so some futures won't work or will work differently. If I have some free time and money, I will try it on a second harddisk. That will be my next private project :-)

Installing Arch Linux on USB key: error while booting

Hello,
first of all, I must say I've followed the steps from this article on arch wiki to install archlinux on my USB key: https://wiki.archlinux.org/index.php/In … _a_USB_key
So what I did is to use one of my 2 usb keys to INSTALL linux, and the second one to RUN linux. I used dd to write on the 1st usb, eveything worked fine when booting, then I do install arch on the my second usb following the stept from the link above, everything works until I get this error while booting (at the middle):
Waiting 10 seconds for device /dev/sdc/
Root device '/dev/sdc' doesn't exist. Attempting to create it.
ERROR: Unable to determine major/minor number of root device '/dev/disk/by-uuid/lotsofnumbers'
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
/bin/sh: Can't contact tty; job control turned off
[ramfs /]#
To summarize I'll show you my conf files that could help you to resolve my problem:
/etc/fstab.conf
/dev/sdc1 /boot ext2 defaults 0 1
/dev/sdc2 / ext3 defaults 0 1
/dev/sdc3 /home ext3 defaults 0 1
So here I've sdc1 boot 32MB partition; sdc2 root 3GB partition; sdc3 home 978MB partition for a total of 4GB USB key~
I didn't make a swap partition as in the tutorial they are writing it's unnecessary for some kind of reasons.
/etc/mkinitcpio.conf
HOOKS="base udev usb autodetect pata scsi sata filesystems"
I've added to here, "usb" to the hooks
installed GRUB on my sdc, here is the menu.ist:
# (0) Arch Linux
title Arch Linux (USB)
root (hd0,0)
kernel /vmlinuz26 root=/dev/sdc ro vga=773
initrd /kernel26.img
So, I boot GRUB without problems, start Arch Linux, but then I got this error above.
I've searched alot on some forums and read many stuffs, but sitll can't fix it and it seems complicated.
I've tried to boot with UUID, also, but didn't make difference. I tried to remove some parameter from the hooks, but unfortunately this wasn't working still. I've read somewhere to use chroot, but I didn't catch on how to do that and what was the use of chroot, I'm still noob user of arch linux and currently learning. Maybe it's the problem, as some forum were talking about creating a new image, but I still don't know how to make it. By the way, I'm not sure this could have fixed my current problem. I've also read somewhere it could be due to my lack of space, but I wrote you how I did partition my USB key, let me know if you have any suggestion please.

1. What I did is re-installing entirely from my installation disk or USB to test out different setting in my config files, because I don't know how to edit my .conf as I can't really finish to boot to the end and get in terminal mode? If there is a quicker way to edit files from any terminal to go into my current USB sdc to modify directly my file from there, I'd enjoy probably. So rebuilding the initpio, no, I just re-installed to test out different configs.
2. Yes, same error.
3. Tested out by-id/by-path and uuid = no difference
4. Didn't know about larch, it seems to be a nice tool, I'll check it out

Install arch on a virtual machine

I am following a tutorial to install arch linux on my virtual box, oracle.
when it comes to the command mkinitcpio, it gives me an error, command not found.
#arch-chroot /mnt
#mkinitcpio -p linux
sh: mkinitcpio: command not found
I added /sbin to my path, but that had no effect.
could anyone guide me please.

saman_artorious wrote:Yes, it is the UUID, but I don't know how to check it.
I think this is the way to do that-
To list basic information about the partitions, run:
$ lsblk -f
or, if you like a gui, I'm partial to "gparted" where you right click on a partition and then click 'information'
Somewhat off topic, but are there preconfigured appliances for download that are recommended? It would be nice to not have to go through the whole instillation routine.
I found this one, and it seems to be one of the few out there from the systemd era:
Archlinux-2013.08.01.ova.torrent
For the OP, you may consider working backwords. Load up a preinstalled appliance, and remove packages you don't want.
Just thinking out loud.
Last edited by browntown (2014-01-14 15:56:48)

Installed Arch on external usb drive: Drive errors after reboot

I installed Arch on my external usb hard drive and everything seemed to be working fine. After rebooting though, I had a bunch of filesytem errors (ext3) and the system was unstable. I am guessing that this has to do with the unloading of the usb modules at shutdown. If this happens to early, then the root drive doesn't have a chance to shutdown properly, hence the filesystem errors.
Anyone know how to solve this?
Thanks!

EtreCheck looks at your log files for any kernel I/O errors. That is what it is reporting. EtreCheck just reports what it finds and tries to avoid judgements exception the most extreme cases. The drive might be OK. I am seeing more reports of this than I would have expected. It may just be a problem with Yosemite. It really prefers SSD disks in all cases. On my own machine, I have seen a slow external drive exhibit classic failure symptoms and sounds when connected via USB2. But then when I switched to FW800, it was fine. Other people are reporting that when they downgraded back to Mavericks, their disk errors went away.
So, I don't have a good answer for you. The drive might be bad, and it might be fine. Yosemite is definitely having problems with it. You may experience performance problems with that drive attached.

Installing Arch on a MacBook Pro Retina

I've spent many hours trying to install Arch on my macbook pro to no avail (over 14 times I've tried), I've learned a lot through this process, but apparently not enough. I get the system installed and blessed (in OSX), but when I try to boot into it I get stuck on "loading initial ram disk." (Previous errors were a read-only file system, but this one is latest) My hunch tells me it has something to do with the mkinitcpio.conf (I was told to add "ahci" to MODULES and "keyboard" after "autodetect" in "HOOKS") and I know the mkinitcpio -p linux command creates the initial ram disk environment (thanks to the docs).
Here are my steps, the bash scripts I created to do all this. Does anything look out of the ordinary to anyone?
cgdisk /dev/sda #(setup partitions as below, sda1-3 not shown)
#partitions: (sda4 == 128MB Hfs+, sda5 == 256MB Linux (boot), sda6 == 30GB Linux (root), sda7 == 70GB #Linux Home)
#first script
mkfs.ext2 /dev/sda5
mkfs.ext4 /dev/sda6
mkfs.ext4 /dev/sda7
mount /dev/sda6 /mnt
mkdir /mnt/boot && mount /dev/sda5 /mnt/boot
mkdir /mnt/home && mount /dev/sda7 /mnt/home
pacstrap /mnt base base-devel
genfstab -p /mnt >> /mnt/etc/fstab
arch-chroot /mnt /bin/bash
#second script
#install wifi (dmesg | grep firmware still says no firmware tho...)
pacman -S wget b43-fwcutter
wget https://aur.archlinux.org/packages/b4/b … are.tar.gz
tar -zxf b43-firmware.tar.gz
cd b43-firmware
makepkg -si --asroot #kosher?
rmmod b43 && modprobe b43
echo arch > /etc/hostname
ln -s /usr/share/zoneinfo/US/Central /etc/localtime
hwclock --systohc --utc
useradd -m -g users -G wheel -s /bin/bash dmj && passwd dmj
sudo pacman -S sudo
nano /etc/sudoers #comment out wheel portion
sudo nano /etc/locale.gen #pick locale
locale-gen
echo LANG=en_US.UTF-8 > /etc/locale.conf
export LANG=en_US.UTF-8
mkinitcpio -p linux #someone said i need "ahci" in modules?
#make boot loader, copy to usb
pacman -S grub-efi-x86_64
grub-mkconfig -o boot/grub/grub.cfg
grub-mkstandalone -o boot.efi -d usr/lib/grub/x86_64-efi -O x86_64-efi -C xz boot/grub/grub.cfg
mkdir /mnt/usbdisk && mount /dev/sdc1 /mnt/usbdisk
cp boot.efi /mnt/usbdisk/
umount /mnt/usbdisk/
sudo pacman -S dialog wpa_supplicant iw
exit
umount /mnt/home
umount /mnt/root
umount /mnt/
sudo reboot
I finally got a descriptive error message and am very excited to show everyone.
https://dl.dropboxusercontent.com/u/10021156/arch.jpg
Moderator Edit: Converted over sized in-line picture to link - ewaller
Last edited by dmj (2013-06-25 02:59:00)

Ok, so I managed to boot into arch. The issue was my fstab. The custom settings I was using were incorrect. Going with the defaults helped. Also, the version of grub I was using was broken. See this link for the fix: https://bbs.archlinux.org/viewtopic.php?id=164101
So after I tar -xvJf xxx.tar.xz the fixed version I was able to generate a boot.efi, copy it onto the 128MB HFS+ on OSX and then bless and boot.
A whole new slew of errors occurred.
First, the video mode error occurs "No suitable video mode" (and something about a font).
I found a fix for it here: (but it didn't work) https://wiki.archlinux.org/index.php/GR … d.22_error
I added
cp /usr/share/grub/unicode.pf2 ${GRUB_PREFIX_DIR}
Then add:
UEFI systems:
insmod efi_gop
insmod efi_uga
After that add the following code (common to both BIOS and UEFI):
insmod font
if loadfont ${prefix}/fonts/unicode.pf2
then
insmod gfxterm
set gfxmode=auto
set gfxpayload=keep
terminal_output gfxterm
fi
Gist: Add these few lines to your grub.cfg, result: no luck still this error
What I'm not sure is if if this is affecting my ability to start the xorg-server.
Then after that the network became unreachable (which is strange because the ethernet worked ootb on install)
systemctl enable dhcpcd@enp0s10
systemctl start dhcpcd@enp0s10
allows me to ping -c 3 google.com
Lastly, I cannot start the xorg server. Says the nvidia module is bad. I installed bumblebee, and ran startx (not from root) and I get a black screen. This is after installing: xorg-server xorg-xinit xorg-server-utils xf86-input-synaptics nvidia acpid
Then running: systemctl enable acpid nvidia-xconfig
My graphics card is a Geforce 650M and I've read I should be using the nvidia module, not the open source noveau module.
startx just boots into a blank screen now and I'm unsure why.
Any speculations, ideas, or thoughts would be gladly welcome.
Thanks ahead of time!
Last edited by dmj (2013-06-26 03:05:26)

Problems after installing Arch [SOLVED]

Hello,
I attempted to follow the installation instructions to install Arch Linux. I followed those since they are faster than the Beginners Guide and didn’t meet some of my needs.
For example, I was also wanting to install an LVM partition (and I'll backup and set up dm-crypt+LUKS later after I get this issue solved), which the Beginner Guide didn't mention and there were a few other minor tweaks I wanted.
In my partition layout I have a 400MB boot (extra room for other kernels). followed by an LVM volume, which has one volume group with 4 logical partitions, these are: /, /home, /tmp, and /var.
The problem:
GRUB is not working, or at least it's not installed and configured correctly. When I boot up my computer, it says exactly, "GRUB", in the top-left corner of my screen and nothing happens. I have a poor understanding of the init/bootloader process in computers, which I am trying to learn slowly but steadily. I was re-reading the instructions for GPT specific partitions, which is what I use, and it says here:
http://www.gnu.org/software/grub/manual … stallation
That I'm supposed to have a "BIOS partition". This is interesting because I have no idea what this is for. Something came to mind when I was using cgdisk or gdisk, it would automatically allocate the first 2000-ish sectors (instead of 34 like the documentation was hinting), so this probably means something.... I don't know.
And then I read that the BIOS installation for GPT is supposed to be done before you install Arch Linux. Whoops! So can I fix this without having to reinstall Arch? I can probably mount all of my directories and chroot inside again after creating the BIOS partition so GRUB can be configured and reinstalled correctly. Maybe I can fix this. I don't know.
So I am trying to troubleshoot this problem, but is there anything I am understanding wrongly here? Is there some other reason why GRUB won't boot up? I tried Super GRUB 2 disk and that didn't work, there was just a blank screen when booting from grub.cfg. Any help or suggestions?
I am using x86_64 Arch Linux with the installed 3.6.4-1-ARCH Linux kernel.
Last edited by mrrhq (2012-11-08 22:31:49)

mrrhq wrote:In my partition layout I have a 400MB boot (extra room for other kernels). followed by an LVM volume, which has one volume group with 4 logical partitions, these are: /, /home, /tmp, and /var.
Be aware that logical partitions are a construct of the Master Boot Record (MBR) partitioning system; however, the title of your thread, and some of the specifics, suggest that you're using the GUID Partition Table (GPT) system, which doesn't use logical partitions. If you're certain you used gdisk or cgdisk, and not fdisk or cfdisk, then you're using GPT and I'd simply accept your use of the word "logical" as an error. If there's any doubt in your mind about this, though, you should investigate further, since some of the issues and solutions depend greatly on which partitioning system you used.
That I'm supposed to have a "BIOS partition". This is interesting because I have no idea what this is for.
The BIOS Boot Partition holds a portion of the GRUB code. It's used on GPT disks but not on MBR disks -- on MBR, the equivalent code goes in an officially-unallocated area immediately after the MBR. The BIOS Boot Partition can sometimes be just a few kibibytes in size, but it's usually either 1MiB or 2MiB. (I've seen reports that some configurations now require over 1MiB, but I haven't investigated this claim.)
Something came to mind when I was using cgdisk or gdisk, it would automatically allocate the first 2000-ish sectors (instead of 34 like the documentation was hinting), so this probably means something.... I don't know.
No, these are unrelated issues. Most partitioning tools today, including gdisk and its siblings, align all partitions on 2048-sector (1MiB) boundaries so as to avoid performance penalties that can be incurred on Advanced Format disks, SSDs, and some types of RAID arrays. See this article I wrote on the topic some time ago.
That said, if you have nowhere else to put it, you could try creating a BIOS Boot Partition in that space. You'd need to change the alignment policy in gdisk or cgdisk to align on 1-sector boundaries to do so, although an 8-sector alignment would be safer for future changes if you've got an Advanced Format disk. The BIOS Boot Partition isn't really greatly affected by the alignment issues, so I wouldn't worry about leaving it unaligned. OTOH, if GRUB wants more then 1MiB on your system, this space would be too small, so it might be better to resize a partition to make room for the BIOS Boot Partition.
WonderWoofy wrote:From what I understand (I have not tried this though) grub2 is actually lvm aware. So you can put all partitions within the lvm, including boot. If this is the case, I see no reason why you would not also be able to put the 2MB bios boot partition in there as well.
GRUB 2 is LVM-aware, and it is possible to put your Linux /boot directory inside the LVM. If you want to do this, though, there's really no point to split /boot off into a separate logical volume (the LVM equivalent of a partition); you might as well just make it a normal directory off of the root (/) filesystem. I'm pretty sure it is not possible to put the BIOS Boot Partition inside the LVM. That's because the code to parse the LVM data structures is contained within the BIOS Boot Partition, thus creating a chicken-and-egg situation if you were to attempt it. Furthermore, the code to write to the BIOS Boot Partition looks for the partition type code in the disk's partition table, and there's no equivalent to that in the LVM data structures. (All this said, in principle you might be able to get something like this to work, but the result would be something similar, but not identical, to a BIOS Boot Partition.)
Although GRUB 2 can read a kernel from within an LVM, I still prefer to keep a separate /boot partition. The reason is that you might not always use GRUB 2. If you wanted or needed to switch to another boot loader in the future, it might not be LVM-aware, and might need /boot to be on a true partition, not in an LVM. (This is true of every EFI boot loader except for GRUB 2, for instance.) In fact, I routinely create two or three smallish partitions on my computers so that I can create multiple /boot partitions for multi-boot configurations or to help transition to a new installation should the need arise. This can help simplify things when the time comes to start fresh.

[SOLVED} Arch refuses to chroot due to missing libreadline.so.6

I got a new laptop today and decided to put 64-bit Arch on a 240GB Kingston V300 SSD (with Windows 8 on the other partition - this laptop uses a legacy BIOS-MBR) using a USB stick as the install medium. When I install, everything works without incident until I go to chroot into the newly installed base system on the SSD. The following error occurs:
# arch-chroot /mnt /bin/bash
/bin/bash: error while loading shared libraries: libreadline.so.6: cannot open shared object file: No such file or directory
The package readline 6.3.006-1 is currently installed and libreadline.so, libreadline.so.6 and libreadline.so.6.3 are all present within /usr/lib
I've tried installing Arch three times without any success, tried chrooting after installing, no dice. Tried different USB sticks, same issue and also tried the previous ISO from April 2015 and the same error comes up.
Not sure where to go from here.
Thanks in advance.
Last edited by tghe-retford (2015-05-23 14:55:38)

Lone_Wolf wrote:tghe-retford, latest version of readline is 6.3.008-1 , is the mirror you selected up to date ?
https://www.archlinux.org/mirrors/status/
Finally managed to update it to 6.3.008-1, still gives the same error:
root@archiso ~ # pacman -Q readline
readline 6.3.008-1
root@archiso ~ #arch-chroot /mnt /bin/bash
/bin/bash: error while loading shared libraries: libreadline.so.6: cannot open shared object file: No such file or directory :(
127 root@archiso ~ #

[SOLVED] external USB HDD fails to install arch w/boot device ERROR

I've been working on installing arch linux via an external USB harddrive (specifically seagate free agent go 320GB) for 1 week now, and everytime I failed - until TODAY! thankfully I found this post, where user Dieter@be references this link, which displays BUG ID#17231 at the top titled "Can't boot LiveCDs 2009.08 (/dev/archiso doesn't show up)". the bug report states ::
I can't boot the LiveCDs 2009.08, neither netinstall nor core.
When it tries to access /dev/archiso it shows these messages:
:: Waiting for boot device ...
Waiting 30 seconds for device /dev/archiso ...
ERROR: boot device didn't show up after 30 seconds ...
Falling back to interactive prompt
You can try to fix the problem manually, logout when you are finished
ramfs$
reading further thru this bug report, I found a very insightful post by Heiko Baums (cyberpatrol) where he says the following, and I quote ::
Problem found. The link /dev/archiso wasn't created.
After
ramfs$ cd /dev
ramfs$ ln -s sr0 archiso
ramfs$ exit
it continued booting correctly.
And sg was also loaded after this. ;-)
as you see, the bug report was for the CD version, not the USB version - yet, my issue with the USB bootdisk was the same, (no matter which boot disk I tried = netinstall, core, .img, .iso, etc) meaning I got the EXACT same error = "ERROR: boot device didn't show up after 30 seconds ..." ! well, I figured that I'd try one of the new fancy ISOs found @ http://build.archlinux.org/isos/ - specifically I use/used archlinux-2010.03.04-netinstall-x86_64.iso.
upon running Unetbootin from windows 7, and choose to install the ISO archlinux-2010.03.04-netinstall-x86_64.iso to my first partition on my USB harddrive (that first partition being FAT32, and had already been set as bootable previously), that completed successfully. I rebooted, and choose to boot from USB drive, the ISOlinux bootloader came up as normal, I choose DEFAULT and off it went.... sure enough, it errored out at the same place as listed in the bug report ::
:: Waiting for boot device ...
Waiting 30 seconds for device /dev/archiso ...
ERROR: boot device didn't show up after 30 seconds ...
Falling back to interactive prompt
You can try to fix the problem manually, logout when you are finished
ramfs$
this time though, I issued the following 2 commands ::
ln -s /dev/sdb1 /dev/archiso
exit
from there, EVERYTHING worked as it should!
to recap: the solution for me was create a symbolic link pointing /dev/archiso => to my partition which held the archlinux netinstall (which is where I told Unetbootin to install it to)! done and done. I felt this needed to be posted here, as I could not find this solution after MANY google searches, archlinux wiki searches, forum searches, etc. honestly, I think it would be prudent to have this tidbit of information added to the Install from USB stick archwiki page as a side note to those that may run into this issue.
this is not the FIRST time I have run into this problem with a USB install of archlinux, but this is the FIRST time I found a fix! thanks to all the great posts I reference here, without this information I dont think I would have been able to install archlinux on my new alienware m11x laptop.
-peace-
PS: no amount of rootdelay=XX nor pmedia=usb nor usbdelay=XX would work in my above attempts either.
Last edited by fnord0 (2010-03-12 04:54:26)

FAT16 here. Parted Magic sees my USB drive as sdd. I tried your way and surprise, surprise, it didn't work.
ln -sf /dev/sdd /dev/archiso
mount -t vfat /dev/archiso /bootmnt
mount : Invalid argument
I thought maybe you meant mount -f vfat /dev/archiso /bootmnt instead. I tried it too, it resulted in a kernel panic.
What else can I try besides installing from a IDE/SATA CD drive ? Because this issue is NOT solved. At least not for me. Wonder if "archlinux-2010.04.05-netinstall-i686.iso" from the here will solve it (really hope so).
SOLVED IT HERE (with yet another image): http://bbs.archlinux.org/viewtopic.php?id=93645
Last edited by DSpider (2010-04-17 14:21:27)

What would be the best way to install Arch, if I have Broadcom wifi?

I can boot into an Arch USB disk, but I can't connect to the Internet, since my laptop doesn't have ethernet and the wifi card is Broadcom, which requires the `broadcom-wl` package. What would be the easiest way of proceeding with this install? On IRC, I was advised to either: (1) boot into another distro, connect to the Internet there, then chroot into the Arch USB image, and download the additional packages from there, or (2) download the `broadcom-wl` package from the AUR, and a build environment, transfer these files to the USB system, and then compile and install the module there. Both of these solutions seems rather complicated to me. With (1), I was having difficulty mounting the arch .img as a drive using Ubuntu, since Ubuntu's `mount` command needs a filetype, and didn't seem to like any of the filetypes I tried. With (2), I have a feeling this would be fairly complicated--I'm not sure which binaries I can install for my system, or how to install packages that I downloaded offline.

I was having difficulty mounting the arch .img as a drive using Ubuntu, since Ubuntu's `mount` command needs a filetype
Not sure what you mean?
I too had issues with my internet, eventually I installed arch from Ubuntu. I used bootstrap image and it worked as advertized in the wiki.
EDIT: If you using Ubuntu then don't forget to create '/run/shm' otherwise pacstrap will fail.
Last edited by fantab (2014-10-29 04:17:46)

Cannot install Arch on raid0 (kernel panics)

I followed the Howto in the wiki to install Arch on a Raid 0 array, but when trying to boot I keep getting errors that boil down to "no filesystem could mount root" followed by a kernel panic.
I modified the howto to my needs:
- created a Raid 0 array using mdadm from logical partitions /dev/sda7 and /dev/sdb7. /dev/sda6 will be /boot and /dev/sdb6 will be swap (both not in raid, of course)
- Put filesystems in place (tried Reiserfs and ext3 for the array; ext2 for /boot seems to be fine as the boot does initialize)
- mounting of array to /mnt
- Edit configfiles. Mkinitcpio is the important one, I feel:
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="pata_jmicron ata_generic ahci ata_piix sata_sil24 raid0"
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect ide scsi sata filesystems"
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev ide scsi sata usb filesystems"
# This setup assembles an ide raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev ide raid encrypt filesystems"
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata scsi sata raid usbinput keymap filesystems"
md=0,/dev/sda7,/dev/sdb7
I also tried adding reisferfs to 'modules' and using rootfstype=reiserfs as a kernel parameters.
- Install kernel
- Chrooting into the basesystem and run mdadm -D -scan >> /etc/mdadm.conf
- Editing menu.lst of an existing installation (Ubuntu, in which incidentally raid0 runs fine)
title Arch Linux
root (hd0,5)
kernel /vmlinuz26 root=/dev/md0 ro md=0,/dev/sda7,/dev/sdb7
What am I doing wrong? I know there's something about creating nodes, but I cannot find any useful information on it. Also, perhaps I am simply missing a module?
Last edited by crakie (2007-06-05 17:31:09)

Still no dice I cannot find anything out of order.
lshdw:
00:00.0 Host bridge: Intel Corporation|Memory Controller Hub (unknown)
00:01.0 PCI bridge: Intel Corporation|PCI Express Root Port (unknown)
00:1a.0 USB Controller: Intel Corporation|USB UHCI Controller #4 (unknown)
00:1a.1 USB Controller: Intel Corporation|USB UHCI Controller #5 (unknown)
00:1a.7 USB Controller: Intel Corporation|USB2 EHCI Controller #2 (unknown)
00:1b.0 Audio device: Intel Corp.|ICH8 HD Audio DID (snd-hda-intel)
00:1c.0 PCI bridge: Intel Corporation|PCI Express Port 1 (unknown)
00:1c.2 PCI bridge: Intel Corporation|PCI Express Port 3 (unknown)
00:1c.3 PCI bridge: Intel Corporation|PCI Express Port 4 (unknown)
00:1c.4 PCI bridge: Intel Corporation|PCI Express Port 5 (unknown)
00:1c.5 PCI bridge: Intel Corporation|PCI Express Port 6 (unknown)
00:1d.0 USB Controller: Intel Corporation|USB UHCI Controller #1 (unknown)
00:1d.1 USB Controller: Intel Corporation|USB UHCI Controller #2 (unknown)
00:1d.2 USB Controller: Intel Corporation|USB UHCI Controller #3 (unknown)
00:1d.7 USB Controller: Intel Corporation|USB2 EHCI Controller #1 (unknown)
00:1e.0 PCI bridge: Intel Corp.|82820 815e (Camino 2) Chipset PCI (hw_random)
00:1f.0 ISA bridge: Intel Corporation|LPC Interface Controller (unknown)
00:1f.2 IDE interface: Intel Corporation|SATA Controller 1 cc=IDE (ata_piix)
00:1f.3 SMBus: Intel Corporation|SMBus Controller (i2c-i801)
00:1f.5 IDE interface: Intel Corporation|SATA Controller 2 cc=IDE (ata_piix)
01:00.0 VGA compatible controller: nVidia Corp.|GeForce 7600 GT (vesa)
03:00.0 Ethernet controller: Realtek Semiconductor|RTL-8168 PCI-E Gigabit Ethernet (r8169)
04:00.0 Mass storage controller: Silicon Image Inc.|SiI 3132 PCI-X Serial ATA Controller (sata_sil24)
05:00.0 Ethernet controller: Realtek Semiconductor|RTL-8168 PCI-E Gigabit Ethernet (r8169)
06:00.0 SATA controller: JMicron Technologies, Inc.|JMicron 20360/20363 AHCI Controller (ahci)
06:00.1 IDE interface: JMicron Technologies, Inc.|JMicron 20360/20363 AHCI Controller (ahci)
07:02.0 FireWire (IEEE 1394): Texas Instruments|TSB43AB22 IEEE1394a-2000 OHCI PHY/Link-Layer Ctrlr (ohci1394)
07:05.0 Multimedia video controller: Conexant Inc.|iTVC15 MPEG Coder (ivtv)
005:001 USB Hub: Virtual|Hub (hub)
005:002 USB Human Interface Devices: USB Gaming Mouse [/dev/input/mice] (usbhid)
002:001 USB Hub: Virtual|Hub (hub)
007:001 USB Hub: Virtual|Hub (hub)
006:001 USB Hub: Virtual|Hub (hub)
001:001 USB Hub: Virtual|Hub (hub)
004:001 USB Hub: Virtual|Hub (hub)
003:001 USB Hub: Virtual|Hub (hub)
---:--- Mouse: PS/2 Mouse port [/dev/psaux] (msintellips/2)

Install Arch from 2007.05 "base" iso or the "current" iso?

My old Arch install (0.7.2, upgraded in Nov. 06) may be broken, and I'm thinking of doing a fresh install of 2007.05. For the old install, I'd followed the recommended procedure of installing just the base system from the CD iso image, then installed the xorg and kde metapackages via pacman and then built the system from there.
At present, Arch offers a 2007.05-Duke.current iso of 550 MB that includes Xorg plus other things (but not KDE), on top of the base package. What exactly is the virtue of this bigger iso over the base package iso (150 MB). Why are the devs offering this bigger "current" iso, and is this the preferred way of installing Arch now?

You could also take it one step further, and use the ftp iso (a mere 27MB for i686, 35MB for x86_64) - that basically provides the installer only, and downloads everything else from the repos. Of course, as with slackhack's "base + upgrade" suggestion, a decent net connection is essential for an ftp install.

Installing Arch in a chroot via chroagh

Similar Messages

Maybe you are looking for