[SOLVED] Encrypted root, /boot on USB, cryptkey issue

Well to the topic. Followed this guide.
Usb flash drive with GRUB and a keyfile on it. Encrypted root.
grub.cfg
linux /vmlinuz-linux root=UUID=<uuid> ro cryptdevice=/dev/disk/by-id/<id>:luks cryptkey=/dev/disk/by-uuid/<uuid>:ext2:/key ipv6.disable=1 quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
mkinitcpio.conf
MODULES="ata_generic ata_piix nls_cp437 ext2 i915"
HOOKS="base udev autodetect modconf block encrypt filesystems keyboard fsck consolefont"
Result: "Meh can't read a keyfile. Please input a passphrase om nom nom."
Tried:
1. Quadruple-checked UUID's, used /dev/sdX instead of them.
2. Using different modules, like nls_utf8, removing ata_* stuff.
3. Playing with <path> and <keyfile> strings, slashes, e t c.
4. A barrel roll.
Is it actually possible to make that filesystem key reading work? If not, how can I get physical offset of keyfile in a filesystem?
UPDATE:
Trouble in device detection speed. Any other usb media get's recognized instantly, while the one I booted from is slow like hell.
Last edited by wfoojjaec (2013-08-14 14:37:11)

Marked as solved.
It seems that origin of a bug was somewhere in a kernel. After a recent update, done today of a 'linux' package a /boot usb device is properly recognized after about 5 seconds passed from poweron (instead of a full initialization at ~270 sec and hanging udev before).
A hack with fstab & noauto is not required now. <_<

Similar Messages

[SOLVED] Encrypted root on USB drive problem

Hi,
I have encrypted root on external USB harddrive. On one machine it works just fine, LUKS ask for password and system starts.
On second it does not work. I tryed nearly all possible combinations of modules and hooks. I can also access my usb drive if I use break=y. I am using current kernel & utils, I definitely use right paths...
Machine is an Dell with Intel chipset. My USB drive is like this:
/dev/sdb1 - big fat32
/dev/sdb2 - ext2 boot with Grub, kernel and initrd image
/dev/sdb3 - root fs, reiserfs encrypted with LUKS
I made little debuging and it seems that encrypt hook was launched, but did not make anything. Before I digg deeper I wonder that someone had same problem, or can give me advice.
Kernel panic screenshot:
PS: how can I put busybox to initrd image? echo * sucks.
Thanks
Last edited by Trained.Monkey (2007-10-10 09:42:13)

I solved, problem is that encrypt is running BEFORE usb drive is fully initialized. Encrypted partition is not found and not used.
Solotion:
put sleep 5 at beggining of encrypt hook. You must also add sleep binary at installer.

[solved] Encrypted root partition decrypts, not recognised on boot

Hello everyone
As per the wiki entry on system encryption with LUKS, I have an unencrypted boot partition (sda1) and a second encrypted partition (sda2) containing everything else, including root. This is on an eeepc 901 (I'm posting here, though, as I understand this as a mounting issue rather than laptop/netbook specific).
I have just done a full system upgrade, including moving to kernel 2.6.34-ARCH. Now, although I am prompted for the passphrase, which is accepted. I subsequently see the following:
::Checking Filesystems [BUSY] fsck.ext2: No such file or directory while trying to open /dev/mapper/root
/dev/mapper/root:
The superblock could not be read or does not describe a correct ext2 filesystem.
If the device is valid and it really does contain an ext2 filesystem (and not swap or
ufs or something else), then the superblock is corrupt, and you might try running
e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Runnig ecfsck -b 8193 /dev/mapper/root simply results in that error message being repeated. Googling and searching the forum only really found this thread to be anything similar. As per the suggestions there, the encrypted partition is last in /etc/fstab and the <options> value is populated:
/dev/sda1 /boot ext2 defaults 0 1
/dev/sdb1 /mnt/sdb1 vfat rw #This is an sdhc card permanently inserted
/dev/mapper/root / ext2 defaults 0 1
/etc/crypttab is entirely commented out, as it advises the root partition needs to be defined in the initramfs.
I can decrypt and open the partition using systemrescuecd, and fsck confirms the partition is clean. Equally, I can access the decrypted partition from the maintenance shell I get dumped into.
I'd be very grateful for any suggestions.
Last edited by Sagittar (2010-07-17 03:40:49)

Thanks for responding. I can confirm /dev/sda2 is ext2: after mounting both partitions with the -r flag, df -T reports ext2 file systems. (The theory is that ext2 helps prolong the life of the SSD in the eee pc. Not that that's entirely relevant here.)
I can't see a way of booting off sysresccd with root=/dev/sda2 without decrypting /dev/sda2 first. I am able to do that from Grub. Is there something I'm missing?
However, when I pay more attention to what happens on sysresccd when I decrypt the partition, I get the following:
% cryptsetup luksOpen /dev/sda2 root
Enter passphrase for /dev/sda2:
device-mapper: remove ioctl failed: Device or resource busy
Key slot 0 unlocked.
So, although I can then mount /dev/sda2 (or, to be precise, /dev/mapper/root) as normal, my guess is that the third line is a big clue as to why my normal boot process fails. I am pursuing that now.

[SOLVED] Unable to boot Archiso USB in UEFI mode

Hello Everyone !
I'm trying to create an UEFI bootable USB from the latest ISO : 2012.10.06. I first tried following this section of the wiki : https://wiki.archlinux.org/index.php/Un … B_from_ISO with an usb key formatted as an EFI System (of type "ef00" in gdisk) and with a FAT32 partition on it.
All steps went right but when i try to boot with this key from the EFI menu, i get an infinite black screen and the usb key led isn't blinking so i suppose it's not loading.
I have refind already installed on my system. When i try booting the key from refind, I get the same result but with a clue : it stays blocked at loading bootx64.efi.
I just tried another way of creating my bootable usb key by following the archiso README : https://projects.archlinux.org/archiso. … EADME#n237
It results in the same situation.
I've tried the two ways a few times and with two different usb keys so i think i didn't miss any step. (The filesystem label is right)
The section of the wiki I mentionned is changing every day so maybe it's not ready ? Moreover, a new command has been added about removing a [BOOT] file, i don't have this file when extracting with bsdtar.
The md5sum of the iso is ok.
My computer is an ASUS N56VM.
Everything worked fine with the previous iso of archlinux.
I didn't find anyone on the forum with the same problem so if anybody knows how I should do or where I could get more information, I would be grateful.
PS : I'm sorry for the mistakes in english, this is not my mother tongue .
Last edited by Takeo (2012-10-14 21:19:32)

Takeo wrote:All steps went right but when i try to boot with this key from the EFI menu, i get an infinite black screen and the usb key led isn't blinking so i suppose it's not loading.
I got the same issue. After hours of debugging I finally understand the problem: gummiboot doesn't detect any menu entry, and goes into a bug that hangs it. I have a patch to fix that particular bug, but instead of hanging you will see a proper error.
The real problem is in gnu-efi, which is not wrapping the Windows x86 calls correctly, so it's a matter of luck if the compiler manages to organize the code in a proper way.
You can try with this package: http://felipec.org/arch-linux/gummiboot … pkg.tar.xz

[SOLVED] Arch Linux Boot from USB fails while loading kernel

I am attempting to get arch linux booting off my usb. I use cfdisk to create a /dev/sdb1 partition then use mkfs.ext4 /dev/sdb1, mount the usb, pacstrap it, use install-syslinux_update -iam, generate fstab and then attempt to boot from it.
The boot extracts the kernel but then complains that DEVICE is missing in the option APPEND root=DEVICE (in syslinux.cfg). I looked in /dev/disk (on the temporary filesystem shell), it showed my ssd and cd drive but not the usb. Does anyone know what could be causing the USB to not load in that particular section of the kernel?
Last edited by afree10 (2013-12-11 14:28:14)

afree10 wrote:
Due to my situation I have to type the file in from scratch so I will only type uncommented lines:
MODULES=""
BINARIES=""
FILES=""
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
I will reboot and get that lsmod output.
Since you'll probably want to boot from different computers (portable USB system), you want to remove 'autodetect' from that line. This is the same as always booting the initramfs-linux-fallback.img image. To save some space, you could remove 'autodetect' from the configuration file, disable the fallback image in /etc/mkinitcpio.d/linux.preset and delete initramfs-linux.img (otherwise, you'll get two identical images).
Of course, run mkinitcpio -P when you're done.

[SOLVED] Attempting to boot from USB key in UEFI mode

I am attempting to boot from a USB Key in UEFI mode to dual boot windows 8 and arch linux. I'm unsuccessful in getting the USB key to boot in UEFI mode.
I am following the guide on page: https://wiki.archlinux.org/index.php/Un … _Interface due to the fact that I am receiving error " No loader found. Configuration files in /loader/entries/*.conf are needed."
I am attempting to use the archiso media and have created refind.conf according to https://bugs.archlinux.org/task/31894#comment102233 in (USB)/EFI/boot/refind.conf
However, I'm stuck on the initial step from the wiki: Install refind-efi pkg. In the usb's filesystem, overwrite the file EFI/boot/bootx64.efi with /usr/lib/refind/refind_x64.efi.
My question is: How do I install the refind-efi package onto the USB key using an arch linux host machine and the USB plugged into the machine.
Last edited by tonysoprano (2013-02-13 04:09:56)

swordfish wrote:1. Might be possible, that the uefi integration is pretty bad. Have you already looked for an update of the uefi bios?
This is my thought, too. The "memory map has changed" message sounds like the firmware is messing with the way memory is laid out in the middle of the boot process. A firmware update, if available, is likely to be the best way to deal with this problem. If not, trying Fedora's patched GRUB Legacy and GRUB 2 are also worth doing; it's conceivable that one of them includes a workaround for the problem.
2. In your first posting you mention Windows 8 on this machine. Is W8 starting in uefi mode?
This is important, but if the disk uses GPT partitioning, then Windows is starting in EFI mode.
3. If W8 is starting in uefi mode, are you sure that secure boot is disabled?
It is; if it weren't, neither rEFInd nor ELILO could start -- or even if they were configured to start in Secure Boot mode, ELILO doesn't launch its kernels in a way that respects Secure Boot, so the ELILO failure can't be caused by Secure Boot. Also, when launched with Secure Boot active, rEFInd returns a clear error message about a security violation and then returns to its main menu; it doesn't hang the computer.
One possible workaround occurs to me if all else fails: Have rEFInd launch a BIOS version of GRUB. The setup procedure, in outline, is as follows:
Create a BIOS Boot Partition on the disk.
Install the BIOS version of GRUB 2.
Configure rEFInd to include a scan for BIOS-mode boot loaders by uncommenting the "scanfor" line in refind.conf and adding "hdbios" to it.
Thereafter, you'll see a new "generic" icon, which should launch GRUB, which should launch Linux in BIOS mode, even though Windows launches in EFI mode. This will work on most modern UEFI-based computers with a single hard disk, but things get trickier with multiple disks and with some UEFI implementations that lack the necessary firmware features. If a future firmware update fixes the problem, or if a future kernel's EFI stub loader includes a workaround, the EFI-mode booting will become an option once again.

[SOLVED]Unable to boot from SATA, but it works from USB

I have strange problem. I made an Arch installation in VMware virtual computer and then I copied the virtual disk to new SSD. When I install the disk into the real hardware (Intel Canoe Creek D2500CC board), i get the "ERROR: Unable to find root device '/dev/sda1'." error.
The strange thing is, that the computer can boot correctly, when I connect the SSD using SATA->USB bridge.
In the recovery shell there are no disk devices (/dev/sd*) so I think it is not a problem of changed device name (f.e. /dev/sdb1 instead of /dev/sda1), to me it looks like udev is not running.
What can be the problem, that the system boots normally when SSD is connected via USB and can not boot when connected directly to SATA port?
My mkinitcpio.conf:
# 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=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency 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 any way. This is useful for config files.
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
# '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 block filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev block filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev block mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev block lvm2 filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
Last edited by MaVac (2014-08-15 05:55:18)

MaVac wrote:Problem solved! :-) I made update with pacman -Su and then everything is working perfectly. :-)
Then please mark the thread as solved as well.

Cryptsetup luks boot mkinitcpio usb stick encrypted

Hi,
I am using cryptsetup and LUKS for encrypting my home partition.
Till now i've used ASK for PASSWORD in /etc/crypttab
But i wanted to use a usb stick for storing a key.
Reading https://wiki.archlinux.org/index.php/LUKS
I successfully have created i key, i added it with luksAddkey and everything seems to be ok.
I have a vfat usb stick that i have copied to the keyfile.
I did my tests, and its works fine.
So, i tweaked my /boot/grub/menu with this:
kernel /boot/vmlinuz26 root=/dev/sda3 ro cryptkey=/dev/disk/by-uuid/D74E-9973:vfat:keyfile cryptdevice=/dev/sda4:encrypted
I have edit /etc/mkinitcpio.conf to add some kernel modules and encrypt hook
and created a new kernel image for safety (i want to have a failsafe kernel image too);
base udev autodetect pata scsi sata encrypt filesystems
the problem is that: poll_device "${ckdev}" is failed (line 24 in encrypt hook) and i am reading
"Keyfile could not be opened. Reverting to passphrase"
I've hacked a little the encrypt hook to debug why poll_device is failing, but i cant figured it out.
The rootdelay is 10sec already.
It seems that my usb device cant be recognized from udev hook (Before encrypt) and my kernel image dont seem to find the external usb stick.
Any help would be appreciated it.
PS: Sorry for my bad english

Yes, mkinitcpio will be integrated in the next version of larch, which is gradually taking on form - at present I am reworking the hard disk installer.
As phrakture is working on a live CD based standard arch installer, I am hoping it will be possible to share much of the code.
It would of course be possible to integrate mkinitcpio into the current larch version, but it would require a bit of cleverness and probably some changes outside of the initramfs bit to cope with the limitations of the klibc environment (or else continued inclusion of busybox in the initramfs). Anyway, I think it would be better to wait for larch version 2, which has been designed with all this in mind. The approach used in version 1 works fine, it is just not quite the same as the new standard Arch boot sequence (and there need to be adaptations for live CD booting anyway).

[solved] kernel 2.6.27 - open LUKS encrypted root partition fails

Hi,
after updating to kernel 2.6.27 the passphrase for my LUKS encrypted root partition does not work anymore.
I get this error messages:
Enter LUKS passphrase:
device-mapper: table: 254:0 crypt: Error allocating crypto tfm
device-mapper: ioctl: error adding target to table
device-mapper: ioctl: device doesn't appear to be in the dev hash table.
Command failed: No key available with this passphrase.
Enter LUKS passphrase:
With a old (2.6.25) vanilla kernel it works.
any ideas?
EDIT
Solved.
The Problem was that I had this line in my mkinitcpio.conf to get rid of the padlock-error-message at boot.
#CRYPTO_MODULES="aes_i586 aes_generic sha256_generic"
With kernel 2.6.27 there are new / more modules needed to open the LUKS encryptet root partition.
So I removed the line from mkinitcpio.conf and deletet the padlock modules in /lib/modules/2.6.27-ARCH before regenarating the initrd image.
Thanks to GerBra for the tip.
Last edited by SiD (2008-10-22 11:41:56)

I'm not shure, but think ... yes.

Plymouth graphical boot, encrypted root, and systemd...

I'm having some difficulty getting Plymouth working with an encrypted root, and, systemd in the initramfs. I had identical issues getting Plymouth working without systemd in the initramfs, so that doesn't seem to be the issue.
I installed plymouth-git from the AUR. I similarly tried this with the non-git AUR package as well, with no different results. While trying to use the non-git package, I used the sd-plymouth mkinitcpio module from Celti's Github (He maintain's the -git AUR package), as posted in the comments. This enables support for systemd support inside the initramfs for plymouth, through using the sd-plymouth hook in place of the normal plymouth flag. When using the normal plymouth flag, and base + udev in place of systemd in my hooks, the same thing happens, so it seems unlikely to be the systemd implementation.
Anyhoo, when using plymouth and plymouth-encrypt in my hooks, I never get asked for a password to decrypt the root volume. It just presents the splash, and, that's all I ever see. After a couple of minutes, it dumps me to a black screen.
The contents of my /etc/mkinitcpio.conf file
MODULES=""
BINARIES=""
FILES=""
HOOKS="systemd sd-plymouth autodetect modconf block keyboard plymouth-encrypt filesystems fsck"
COMPRESSION="gzip"
COMPRESSION_OPTIONS=""
I use rEFInd, not grub or gummiboot, and my kernel options are as follows:
rd.luks.name=945737e7-94a0-49a0-b1ab-b51cb497ec4a=root root=/dev/mapper/root initrd=intel-ucode.img initrd=initramfs-linux.img rw nomodeset add_efi_memmap quiet splash
When booting, I'm greeted with my rEFInd GUI, it drops to a black screen for a fraction of a second, and loads Plymouth, and, sits there for about 90 seconds before dumping me to a black screen. When I type something on the keyboard, it shows up in the console, on top of the splash screen. It's almost as if plymouth isn't hooking the input. It fails to ask for a password or decrypt my root, too. I do notice when not using sd-plymouth, the splash logo appears to have an input box as if it at least knows it's attempting to decrypt it, but again, the input fails to go into the splash screen, but shows up (in cleartext) in the console at the top corner.
Suggestions would be appreciated.

Without hacking the encrypt hook, you'll only be able to unlock one volume at the same time. Afaik the device mapper asks for a password for each encrypted partition, and using one for all won't work, you have to repeat the process for each partition, whereas the encrypt hook only seems to be able to handle one partition. You can hack it, but I haven't done that (yet), it's already quite messy you have to hack the hook file to make it apply to non-root partitions.

My Macbook (2006) cannot boot from USB, is there any way to solve this?

I bought a retail copy of Snow Leopard 10.6.3 and upon trying to install it via optical drive, it fails every time. I'm certain that the drive itself has issues reading discs. So instead I opted to install my retail Snow Leopard onto a USB flash drive (a 32GB Kingston stick) but this macbook absolutely refuses to boot via USB. I've used Carbon Copy Cloner and Disk Utility but neither has yielded results. I've spent so many hours trying to install this OS, does anyone know what's going on??

Late reply, but if anyone is experiencing the same problem, I've found a solution. For whatever reason, some macbooks don't recognize usb flash drives during the boot-up phase, even though the usb ports themselves are powered (I tested this with a multimeter). The solution then, was to use an external USB hard drive that has its own power supply to install Snow Leopard. I don't know why, but it's the only way I got my macbook (Macbook 2,1/A1181) to recognize the install drive. Every was smooth sailing from there!

[SOLVED] Trouble installing with encrypted root system

I'm trying to install with an encrypted root filesystem following the wikiguide: http://wiki.archlinux.org/index.php/Enc … Filesystem
I've downloaded the latest 0.7.1 ISO with 2.6.15-12 kernel.
All I get when I try to intall a bootloader is
Missing/Invalid root partition
Errormsg taken from the top of my head
Any suggestions? Isn't the guide applicable on 0.7.1 / 2.6.15-2-kernel?

It was all my bad.. I somehow forgot to configure a mount for /boot.

[SOLVED] Unable to boot ISO on USB

Hello,
I'm unable to boot from USB. I have the following error : "Failed to install override security policy: (14) Not Found".
I tried the following solution : http://superuser.com/a/676059
But then my computer does not want to boot on the USB. I don't have any option for UEFI on my computer's BIOS (ASUS eeepc). Note that I don't want a dual boot with Windows and there is currently a broken archlinux installation on my hard drive.
Can anyone help me with this ?
Thanks. :-)
Last edited by filippo (2014-10-08 16:37:15)

Trilby wrote:How did you originally make the usb. Did you follow the wiki: https://wiki.archlinux.org/index.php/UE … B_from_ISO
Yes, I used :
dd bs=4M if=/path/to/archlinux.iso of=/dev/sdb && sync
And for creating the ISO (after copying the file for the workaround) :
genisoimage -iso-level 4 -o archlinux.iso archlinux
Mr.Elendig wrote:
This may be caused by buggy uefi firmware, check if there is a new one for your card.
Also in some cases it can be caused by fastboot/similar so check for that too in the bios.
I don't have an option for last boot. I'll check for a new uefi firmware !
EDIT: How do I check for that ?
I have an option on the BIOS "Launch EFIT Shell from filesystem" which search for Shellx64.efi on the available filesystem devices. However, it is calle shellx64_v1.efi and shellx64_v2.efi on the archlinux iso. May be this be a problem ?
Anyway, it's strange, the last time I installed Archlinux this eeepc (more than one year ago...) I didn't had any problem !
Last edited by filippo (2014-10-08 15:19:46)

[SOLVED] Unable to boot after downgrading from 2.6.38 to 2.6.37

After experiencing some issues with 2.6.38 and my Intel video card (external monitor support). I decided to go back to 2.6.37 for the time being.
I went into my /var/cache/pacman/pkg and typed in:
pacman -U kernel26-2.6.37-6-x86_64.pkg.tar.xz kernel26-headers-2.6.37-6-x86_64.pkg.tar.xz linux-api-headers-2.6.37-1-x86_64.pkg.tar.xz
warning: downgrading package kernel26 (2.6.38.2-1 => 2.6.37-6)
warning: downgrading package kernel26-headers (2.6.38.2-1 => 2.6.37-6)
warning: downgrading package linux-api-headers (2.6.38.1-1 => 2.6.37-1)
resolving dependencies...
looking for inter-conflicts...
Targets (3): kernel26-2.6.37-6 kernel26-headers-2.6.37-6 linux-api-headers-2.6.37-1
Total Download Size: 0.00 MB
Total Installed Size: 96.04 MB
Proceed with installation? [Y/n] y
(3/3) checking package integrity [#######################################################] 100%
(3/3) checking for file conflicts [#######################################################] 100%
(1/3) upgrading kernel26 [#######################################################] 100%
>>> Updating module dependencies. Please wait ...
>>> MKINITCPIO SETUP
>>> ----------------
>>> If you use LVM2, Encrypted root or software RAID,
>>> Ensure you enable support in /etc/mkinitcpio.conf .
>>> More information about mkinitcpio setup can be found here:
>>> http://wiki.archlinux.org/index.php/Mkinitcpio
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.37-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [uresume]
:: Parsing hook [filesystems]
:: Parsing hook [keymap]
:: Generating module dependencies
:: Generating image '/boot/kernel26.img'...SUCCESS
==> SUCCESS
==> Building image "fallback"
==> Running command: /sbin/mkinitcpio -k 2.6.37-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [uresume]
:: Parsing hook [filesystems]
:: Parsing hook [keymap]
:: Generating module dependencies
:: Generating image '/boot/kernel26-fallback.img'...SUCCESS
==> SUCCESS
(2/3) upgrading kernel26-headers [#######################################################] 100%
(3/3) upgrading linux-api-headers [#######################################################] 100%
Then I rebooted and to my surprise I got stuck very early during the boot process.
sda: sda1 sda2 sda3
sd 0:0:0:0 [sda] Attached SCSI disk
Waiting 10 seconds for device /dev/sda3
mount: mounting /dev/sda3 on /new_root failed: No such device
ERROR: Failed to mount the real root device
Hopefully I had a 2.6.39rc3-mainline entry in my grub so I selected it and was able to boot as before. I then upgraded from 2.6.37 back to 2.6.38 and guess what... still unable to boot (same message).
What could be the root cause?
Thanks
Alphazo
Last edited by alphazo (2011-04-13 14:09:20)

Finally I got both 2.6.37 and 2.6.38 to boot again but boy it wasn't pretty. Before I start here is what I did before the boot issue.
- Running 2.6.38.2-1 from [Core]
- I also have 2.6.39rc3 from [miffe] repo with a dedicated entry in Grub (testing & recovery)
- Downgraded to 2.6.37 using from /var/cache/pacman/pkg:
pacman -U kernel26-2.6.37-6-x86_64.pkg.tar.xz kernel26-headers-2.6.37-6-x86_64.pkg.tar.xz linux-api-headers-2.6.37-1-x86_64.pkg.tar.xz
- Rebooted
- Boot would stop early during the process
- Booted 2.6.39rc3
- Upgraded to 2.6.38.2-1 via
pacman -U kernel26-2.6.38.2-1-x86_64.pkg.tar.xz kernel26-headers-2.6.38.2-1-x86_64.pkg.tar.xz linux-api-headers-2.6.38.1-1-x86_64.pkg.tar.xz
- Rebooted
- Boot would stop early during the process
- Booted 2.6.39rc3
- Downgraded to 2.6.37 using from /var/cache/pacman/pkg:
pacman -U kernel26-2.6.37-6-x86_64.pkg.tar.xz kernel26-headers-2.6.37-6-x86_64.pkg.tar.xz linux-api-headers-2.6.37-1-x86_64.pkg.tar.xz
- Rebooted
- Boot would stop early during the process
- Booted 2.6.39rc3
- Copied via USB kernel26.img and vmlinuz26 from a friend's PC (running same Arch configuration with 2.6.38 kernel)
- Rebooted
- This time, my friend's 2.6.38 would start
- Upgraded to 2.6.38.2-1 via
pacman -U kernel26-2.6.38.2-1-x86_64.pkg.tar.xz kernel26-headers-2.6.38.2-1-x86_64.pkg.tar.xz linux-api-headers-2.6.38.1-1-x86_64.pkg.tar.xz
- Rebooted
- This time, my 2.6.38 would start
- Downgraded to 2.6.37 using from /var/cache/pacman/pkg:
pacman -U kernel26-2.6.37-6-x86_64.pkg.tar.xz kernel26-headers-2.6.37-6-x86_64.pkg.tar.xz linux-api-headers-2.6.37-1-x86_64.pkg.tar.xz
- Rebooted
- Again I can boot from 2.6.37
So overall there have been two issues. One when dowgrading from 2.6.38 to 2.6.37 while running 2.6.38 and then when downgrading to 2.6.37 or 2.6.38 while running 2.6.39.
A bit confusing I admit but I think there is a glitch here that does bad thing when generating kernel26.img
Alphazo

[SOLVED]Can't boot mac air mid-2012 (GPT,EFISTUB,rEFInd,LUKS,LVM2)

Partition scheme:
/dev/sda/
- /dev/sda1: /boot/efi, 512M
- /dev/sda2: /boot, 100M
- /dev/sda3: lvm partition (/, var, home)
+ lvm on luks.
install from usb: dd if=archlinux-2012-08-04.iso of=/dev/sdX
Installation steps:
- boot from usb with noapic parameter
- partition
- encrypt /dev/sda3
- partitioning on /dev/sda3 (/,var,home)
- mkfs.vfat -F32 /dev/sda1; mkfs.ext2 /dev/sda2; mkswap /dev/arch/swap; mkfs.ext4 /dev/arch/root; mkfs.ext4 /dev/arch/home; mkfs.reiserfs /dev/arch/var
- mount /dev/arch/root /mnt; mkdir /mnt/{boot,home,var,boot/efi}; mount /dev/sda2 /mnt/boot; mount /dev/sda1 /mnt/boot/efi; mount /dev/arch/home /mnt/home; mount /dev/arch/var /mnt/var
- pacstrap /mnt base base-devel
--- SETTING EFISTUB: https://wiki.archlinux.org/index.php/UE … up_EFISTUB
/boot/efi/EFI/arch/linux.conf
root=/dev/mapper/arch-root ro rootfstype=ext4 add_efi_memmap initrd=\EFI\arch\initramfs-linux.img
- pacman -Syy; pacman -Rdd sysvinit; pacman -S systemd-vcompat; pacman -S systemd-arch-units; pacman -Rns initscripts
--- Sync EFISTUB Kernel in UEFISYS partition using Systemd: https://wiki.archlinux.org/index.php/UE … ng_Systemd
--- Booting EFISTUB: pacman -S refind-efi-x86_64
/boot/efi/EFI/arch/refind_linux.conf
"Boot with defaults" "root=/dev/mapper/arch-root ro rootfstype=ext4 add_efi_memmap"
"Boot to Terminal" "root=/dev/mapper/arch-root ro rootfstype=ext4 add_efi_memmap 3"
---- Native systemd configuration files: https://wiki.archlinux.org/index.php/Sy … tion_files
- arch-root /mnt; ln -s /usr/share/zoneinfo/Europe/Athens /etc/localtime; locale-gen; mkinitcpio -p linux; passwd; reboot
+++ and result: white screen without output +++
my english is very bad, forgive me.
i'm wong or miss something?
EDIT 1: /etc/mkinitcpio.conf : HOOKS=....encrypt lvm2 filesystem.....
Last edited by angelfalls (2012-09-07 19:40:38)

sr am wrong. i must install grub2 follow wiki, i read wiki but don't understand much
solved.

[SOLVED] Encrypted root, /boot on USB, cryptkey issue

Similar Messages

Maybe you are looking for