[SOLVED] Root partition wrongly assumed to be encrypted.

Hi,
I'm trying to install arch using newest iso image (2012.10.06) in a following manner:
gpt partition on /dev/sda1
root on btrfs on /dev/sda2
var on btrfs on /dev/sda3
home on btrfs on /dev/mapper/crypt (LUKS) on /dev/sda4,
but I have a problem after booting into freshly installed system. There's a message stating that:
ERROR: Failed to open encryption mapping: The device /dev/sda2 is not a LUKS volume and the crypto= parameter was not specified.
(actually there's uuid instead of /dev/sda2 but I've changed it for brevity)
Then after some time I get an error:
[ TIME ] Timed out waiting for device dev-mapper-crypt.device
then some "dependency failed" messages and I get welcomed to the emergency mode prompt.
I've added encrypt before filesystems to mkinitcpio hooks, and rebuild the image.
My /etc/fstab is generated by genfstab at installation and looks like this (comments ommited):
/dev/sda2 / btrfs rw,noatime,compress=lzo,space_cache,subvol=/__active 0 0
/dev/mapper/crypt /home btrfs rw,noatime,compress=lzo,space_cache,subvol=/__active 0 0
/dev/sda3 /var btrfs rw,noatime,compress=lzo,space_cache,subvol=/__active 0 0
Problem is that my / is NOT encrypted, only my home partition. But when I remove my home partition entry from fstab system boots to normal login prompt (but the error saying / is not a LUKS partition still shows up).
What am I doing wrong? I didn't alter my grub.cfg after running grub-mkconfig, and there are no entries in it stating that root is encrypted (only flags are: subvol=__active). How can I prompt the user (me) for passphrase on boot? As far as I read it should be done automatically by "encrypt" hook.
Any suggestions?
cheers,
kajman
Last edited by kajman (2012-10-18 08:45:05)

What are the boot parameters in grub?
You need a cryptdevice= entry if you want to unlock it from the initramfs.
For the syntax read the help of the encrypt hook:
mkinitcpio -H encrypt
If it's only for the home partition, I would unlock it from /etc/crypttab instead of the initramfs.

Similar Messages

[SOLVED]root partition read only after update systemd

After update systemd today, the systemd-remount-fs.service fail to start. Root filesystem is read only I tried add rw to fstab mount option, but the root parition is still read only. I noticed that util-linux package are installed and udev package is dropped , Does it related to my problem?
Please advice me.
Sorry for my bad English.
Update
After downgard util-linux package, the system work again
Update 2
UUID in grub.conf and fstab are inconsistent, Thanks to tomegun for point out this problem.
Last edited by aduser (2012-06-08 04:05:59)

output of systemctl status systemd-remount-fs.service
systemd-remount-fs.service - Remount Root and Kernel File Systems
Loaded: loaded (/usr/lib/systemd/system/systemd-remount-fs.service; static)
Active: failed (Result: exit-code) since Sun, 03 Jun 2012 01:17:42 +0800; 5min ago
Process: 132 ExecStart=/usr/lib/systemd/systemd-remount-fs (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/systemd-remount-fs.service
fstab
UUID=55326b3a-eec9-498e-8e20-0a7ddd8daf9a / btrfs rw,compress=lzo,space_cache,autodefrag 0 1
UUID=54c17991-716b-496e-a89b-4e978f2d92a4 /boot ext2 defaults 0 1
systemctl
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
proc-sys...misc.automount loaded active waiting Arbitrary Executable File Formats File System Automount Point
sys-devi...d-card1.device loaded active plugged RV630 audio device [Radeon HD 2600 Series]
sys-devi...d-card0.device loaded active plugged 82801I (ICH9 Family) HD Audio Controller
sys-devi...et-eth0.device loaded active plugged RTL8111/8168B PCI Express Gigabit Ethernet controller
sys-devi...dd-sdd1.device loaded active plugged ST3120213A
sys-devi...dd-sdd2.device loaded active plugged ST3120213A
sys-devi...ock-sdd.device loaded active plugged ST3120213A
sys-devi...da-sda1.device loaded active plugged WDC_WD6400AAKS-22A7B0
sys-devi...da-sda2.device loaded active plugged WDC_WD6400AAKS-22A7B0
sys-devi...da-sda3.device loaded active plugged WDC_WD6400AAKS-22A7B0
sys-devi...da-sda5.device loaded active plugged WDC_WD6400AAKS-22A7B0
sys-devi...ock-sda.device loaded active plugged WDC_WD6400AAKS-22A7B0
sys-devi...db-sdb1.device loaded active plugged WDC_WD1002FAEX-00Z3A0
sys-devi...db-sdb2.device loaded active plugged WDC_WD1002FAEX-00Z3A0
sys-devi...db-sdb3.device loaded active plugged WDC_WD1002FAEX-00Z3A0
sys-devi...db-sdb4.device loaded active plugged WDC_WD1002FAEX-00Z3A0
sys-devi...db-sdb5.device loaded active plugged WDC_WD1002FAEX-00Z3A0
sys-devi...ock-sdb.device loaded active plugged WDC_WD1002FAEX-00Z3A0
sys-devi...dc-sdc1.device loaded active plugged ST980811AS
sys-devi...dc-sdc2.device loaded active plugged ST980811AS
sys-devi...ock-sdc.device loaded active plugged ST980811AS
sys-devi...y-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS1
sys-devi...y-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS2
sys-devi...y-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS3
sys-devi...y-ttyS0.device loaded active plugged /sys/devices/pnp0/00:07/tty/ttyS0
-.mount loaded active mounted /
boot.mount loaded active mounted /boot
dev-hugepages.mount loaded active mounted Huge Pages File System
dev-mqueue.mount loaded active mounted POSIX Message Queue File System
sys-kernel-debug.mount loaded active mounted Debug File System
tmp.mount loaded active mounted /tmp
xs-big.mount loaded active mounted /xs/big
xs-dev-\...pace\x5d.mount loaded active mounted /xs/dev/[workspace]
xs-dev.mount loaded active mounted /xs/dev
xs-dl.mount loaded active mounted /xs/dl
xs-file.mount loaded active mounted /xs/file
systemd-...d-console.path loaded active waiting Dispatch Password Requests to Console Directory Watch
systemd-...word-wall.path loaded active waiting Forward Password Requests to Wall Directory Watch
console-...daemon.service loaded active running Console Manager
console-...-start.service loaded failed failed Console System Startup Logging
dbus.service loaded active running D-Bus System Message Bus
[email protected] loaded active running dhcpcd on eth0
gdm.service loaded active running Gnome Display Manager
[email protected] loaded active running Getty on tty1
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-...unt-fs.service loaded failed failed Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-...-setup.service loaded active exited Recreate Volatile Files and Directories
systemd-...rigger.service loaded active exited udev Coldplug all Devices
systemd-udev.service loaded active running udev Kernel Device Manager
systemd-...nlevel.service loaded failed failed Update UTMP about System Runlevel Changes
systemd-...ssions.service loaded active exited Permit User Sessions
systemd-...-setup.service loaded active exited Setup Virtual Console
dbus.socket loaded active running D-Bus System Message Bus Socket
systemd-initctl.socket loaded active listening /dev/initctl Compatibility Named Pipe
systemd-journald.socket loaded active running Journal Socket
systemd-shutdownd.socket loaded active listening Delayed Shutdown Socket
systemd-...control.socket loaded active listening udev Control Socket
systemd-...-kernel.socket loaded active running udev Kernel Socket
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
network.target loaded active active Network
remote-fs.target loaded active active Remote File Systems
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
systemd-...es-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
74 units listed. Pass --all to see inactive units, too.
grub2 conf
menuentry 'Broken' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-ck kernel-true-852c733e-be0d-4375-8668-d7ae049295a9' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 54c17991-716b-496e-a89b-4e978f2d92a4
else
search --no-floppy --fs-uuid --set=root 54c17991-716b-496e-a89b-4e978f2d92a4
fi
echo 'Loading Linux ck kernel ...'
linux /vmlinuz-linux-ck root=UUID=852c733e-be0d-4375-8668-d7ae049295a9 ro rootflags=subvol=broken quiet add_efi_memmap elevator=bfq
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-ck.img
The update packages
core/btrfs-progs 0.19.20120328-2 2 -> 3
core/device-mapper 2.02.95-4 4 -> 6
core/cryptsetup 1.4.2-1 1 -> 2
core/gpm 1.20.6-7 7 -> 8
core/lvm2 2.02.95-4 4 -> 6
extra/libglapi 8.0.3-1 1 -> 2
extra/libgl 8.0.3-1 1 -> 2
extra/ati-dri 8.0.3-1 1 -> 2
extra/bluez 4.99-2 2 -> 6
extra/consolekit 0.4.6-3 3 -> 4
extra/gvfs 1.12.3-1 1 -> 2
extra/gvfs-obexftp 1.12.3-1 1 -> 2
extra/libatasmart 0.18-1 1 -> 2
extra/libcanberra 0.28-4 4 -> 5
extra/libpulse 2.0-1 1 -> 2
extra/libcanberra-pulse 0.28-4 4 -> 5
extra/mesa 8.0.3-1 1 -> 2
extra/pulseaudio 2.0-1 1 -> 2
extra/xf86-video-ati 6.14.99-0.20120517 0.20120517 -> 1.20120517
community/libvirt 0.9.12-7 7 -> 8
community/ttf-ubuntu-font-family 0.80-2 2 -> 3
multilib/lib32-libglapi 8.0.3-3 3 -> 3.1
multilib/lib32-libgl 8.0.3-3 3 -> 3.1
==> Software upgrade (new version) :
core/util-linux 2.21.1-2 -> 2.21.2-1
core/e2fsprogs 1.42.2-2 -> 1.42.3-1
core/libpipeline 1.2.0-2 -> 1.2.1-1
core/libsystemd 44-7 -> 184-2
core/procps-ng 3.3.2-2 -> 3.3.3-1
core/systemd 44-7 -> 184-2
core/systemd-sysvcompat 3-1 -> 184-2
extra/pixman 0.24.4-1 -> 0.26.0-1
extra/xorg-server-common 1.12.1.902-1 -> 1.12.2-1
extra/xorg-server 1.12.1.902-1 -> 1.12.2-1
community/libuser 0.57.1-2 -> 0.57.6-1
community/os-prober 1.49-3 -> 1.53-1
community/systemd-arch-units 20120412-6 -> 20120528-3
repo-ck/linux-ck-corex 3.3.7-1 -> 3.4-1
repo-ck/linux-ck-corex-headers 3.3.7-1 -> 3.4-1
==> New package :
core/systemd-tools 184-2 (required by systemd)
Does the systemd not support btrfs subvolume as root partition??
Last edited by aduser (2012-06-02 17:45:39)

[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.

[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.

Copied my Arch root partition to a new one but I can't boot [SOLVED]

I booted to my arch live cd and copied my Arch / partition (/dev/sda1) to an empty partition (/dev/sda9) via a cp -a command. The new partition should now contains an exact copy of my old root partition. I also modified the /etc/fstab in the new partition to reflect the new block device for the root filesystem. I also added a line to my menu.lst to boot it. I didn't do something right because I get a kernel panic when grub boots into the new partition.
menu.lst entry:
title Arch Testing
root (hd0,8)
kernel /boot/vmlinuz26 root=/dev/sda9 ro quiet vga=773 acpi_enforce_resources=lax vga=773
initrd /boot/kernel26.img
Ideas?
EDIT: Just read this wiki page
The fix as root:
mount /dev/sda9 /mnt
cd /mnt/dev
rm console ; mknod -m 600 console c 5 1
rm null ; mknod -m 666 null c 1 3
rm zero ; mknod -m 666 zero c 1 5
mount -o bind /dev /mnt/dev
mount -t proc none /mnt/proc
mount -o bind /sys /mnt/sys
cd /
chroot /mnt /bin/bash
mkinitcpio -p kernel26
Last edited by graysky (2009-12-05 15:14:01)

Since you can't delete Apple IDs and having multiple Apple IDs can cause confusion, what you may want to do is rename your existing Apple ID to the new email (desired Apple ID). That would in effect do what you want, get rid of the old and give you the new.
See "Apple ID: Changing your Apple ID"
ivan

[solved] unable to boot to the root partition on my new (usb) HDD

hello,
i got a "unable to determine major/minor number of root device" error message when the system try to find the root partition (after it succefully boot on the boot partition).
Shuttle XPC SB65G2 (Mainboard FB65), usb HDD: Intenso INIC-1608L, Linux ctkarch 2.6.37-ARCH #1 SMP PREEMPT, grub legacy.
sdb1: /boot (ext2), sdb2: swap, sdb3: / (ext4), sdb4: /home (ext4)
of course i have a kernel compiled with usb in HOOKS in mkinitcpio.conf.
i tried to install with sdb1: / (ext4), sdb2: swap, sdb3: /home (ext4)
but i got another error: it can't find the file /dev/blabla (root partition) (after it succefully boot on the partition!).
at last i found the solution: i have to comment "root (hdx,x)" in menu.lst for grub legacy!:
# (0) Arch Linux
title Arch Linux
# root (hd1,0)
kernel ... by-uuid...
you don't need this line when you define by uuid, by label, or so...
it seems this line perturbs the behavior of the system.
if this can help...

You do not need the "raw". If you do:
ok devalias
it will show you how other aliases are formed
do ls -l /dev/dsk/c0t2d0s0 and you'll see the "non-raw" device path
ok reset
will "lock" your alias in NVRAM but it will attempt to boot from boot-device (normally disk) the next time unless auto-boot? is set to false
ok setenv auto-boot? false
My guess is that it could not understand "raw", reset, and booted from boot-device.
You can:
ok setenv auto-boot? false
ok nvunalias altboot
ok nvalias altboot /pci@1f,0/ide@d/dad@2,0
ok reset
ok boot altboot

[solved] How to convert fs from ext2 to ext3 on root partition?

Hello there!
Edit: It seems that the plan works! apparently it worked for alleyoopster also on a mounted fs.
As the title says, I want to convert my fs on / from ext2 to ext3. After some research I think I know what
to do, but want to make sure that I don't mess anything up....
So here is the plan:
boot with an install disc and leave the root partition unmounted (I know that in theory the conversion should
work on a mounted fs, but it feels awkward to me and I want to avoid it....).
Then use the
tune2fs -j /dev/xxx
command (the defaults for the forced checks are ok with me). Then reboot with the CD still in place, but use
this time root=/dev/xxx. Then I can change my /etc/fstab (ext3 should have been able to be mounted as ext2 at
the moment). Finally I have to rebuild my initrd image with
mkinitcpio -p kernel26
Then I should be able to boot into my system. And now the question: Can anyone verify that this is a valid approach
and will work? Or knows a better way to do it?
I'm grateful for any input
Last edited by alafanky (2007-11-26 15:41:35)

Have a look at the man for tune2fs and mkinitcpio
man tune2fs
man mkinitcpio
I am looking at doing the same and as far as I can figure out it goes like this, BUT this is not a proven method just what I am thinking of doing, Maybe someone else can correct or add to this or confirm that it will work.
1. Add journal parameter like this:
tune2fs -j /dev/sda1
2. Change the partition type from ext2 to ext3 in /etc/fstab
3. For a standard kernel re-create ramdisk with preset parameters (no good for custom kernel)
mkinitcpio -p kernel26
As the system is mounted it will create the journal inode in the top level, don't delete this, it will get hidden into the filesystem on reboot.
Let me know if you make some progress. I may get brave and try it later.
So in answer, yes pretty much the same but I think you can do it with the fs mounted.
Last edited by alleyoopster (2007-11-26 12:44:29)

[SOLVED]root file system partition too small

O.K. so I have this stupid problem:
[rsw@myhost ~]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda3 2542076 2320972 92988 97% /
none 94784 0 94784 0% /dev/shm
/dev/sda4 12041420 2406244 9028324 22% /home
/dev/sda1 38888 8336 28544 23% /boot
When I set up my partitions I expected 2.5 gigs to stretch a little farther than this. is there any way to resize it without formating the drive and starting over?
Last edited by rsw (2008-10-16 00:52:02)

rsw wrote:
O.K. so I have this stupid problem:
[rsw@myhost ~]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda3 2542076 2320972 92988 97% /
none 94784 0 94784 0% /dev/shm
/dev/sda4 12041420 2406244 9028324 22% /home
/dev/sda1 38888 8336 28544 23% /boot
When I set up my partitions I expected 2.5 gigs to stretch a little farther than this. is there any way to resize it without formating the drive and starting over?
Yep, your home partition is directly after the root partition, so what I suggested should work, however, give good consideration to the size of each, considering you don't have another drive (according to df) to use for storage. Personally, I only have 12GB on my home partition (after resizing) and now have 23GB on root.
Here's mine.
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdb3 22864180 7438764 14503608 34% /
none 517648 548 517100 1% /dev/shm
/dev/sdb4 11897496 5947088 5470708 53% /home
/dev/sdb1 38888 22534 14346 62% /boot
/dev/sda1 155059036 37878624 109365872 26% /media/thevault
/dev/sdc1 116294120 84739460 25693748 77% /media/music
Last edited by Execute_Method (2008-10-14 12:53:41)

Will upgrades fill up root partition? [Solved]

I've noticed over the last month since installing Arch, that when I do upgrades it filling up my root partition.
[davek@arch64 ~]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda2 19228308 5983660 12267896 33% /
none 962680 144 962536 1% /dev
none 962680 0 962680 0% /dev/shm
/dev/sda3 134405528 6996148 120581956 6% /home
/dev/sda1 198337 15489 172608 9% /boot
does this mean if I do a -Syu every week the root partition will be filled up in a few months? How do I limit this problem? What can I do to keep it down?
Last edited by vinoman2 (2009-09-04 13:34:17)

Packages downloaded during upgrades are stored in /var/cache/pacman/pkg. You can use the -c option of pacman in a sync operation (i.e..: pacman -Sc) to get rid of older packages that are no longer installed. Specify the -c option twice (pacman -Scc) to delete all cached packages.
pacman(8) wrote:
-c, --clean
Remove packages that are no longer installed from the cache as well
as currently unused sync databases to free up disk space. When
pacman downloads packages, it saves them in a cache directory. In
addition, databases are saved for every sync DB you download from,
and are not deleted even if they are removed from the configuration
file pacman.conf(5). Use one --clean switch to only remove packages
that are no longer installed; use two to remove all packages from
the cache. In both cases, you will have a yes or no option to
remove packages and/or unused downloaded databases.
If you use a network shared cache, see the CleanMethod option in
pacman.conf(5).

[SOLVED] Root fs cannot be found on boot (initramfs works)

Hi all! Long time lurker, first time poster.
I'd been using catalyst drivers since I started out on Arch. I knew there were conflicts during updates involving catalyst, so I've never updated my kernel or Xorg during "pacman -Syu" updates. I'd specifically blocked them in pacman.conf. However, I recently decided to switch to open source ati drivers and in doing so, decided to update my entire system including the kernel. Everything went smoothly, but upon reboot I'm getting the dreaded "root filesystem cannot be found" error.
Root device '/dev/sdb6' doesn't exist, attempting to create it
ERROR: Failed to parse block device name for '/dev/sdb6' unknown
ERROR: Unable to create/detect root device, '/dev/sdb6'
Dropping to recovery shell.. type 'exit' to reboot
Note that the initramfs worked, it's just it couldn't get into my root partition even though I can mount it without any problems from the live CD.
I set about trying to fix my problem. Here is a list of things I've tried.
1) Using the liveCD, I chrooted into my install (mounting proc, dev, etc. in the process) and did
depmod -a
followed by
pacman -Sf kernel26
which completed with no errors problems. This didn't solve my issue.
2) Using the liveCD, performing
mkinitcpio -M
and ensuring my mkinitcpio.conf file contained all the listed modules. I then rebuilt the initramfs with another
pacman -Sf kernel26
This didn't solve my issue.
3) Playing with grub, replacing my UUID lookups with /dev/sdb6. I also tried different combinations (see this thread) to check the bios and grub were matching up. I did the suggested rootdelay=8 and rootfstype=ext3 stuff, too. This didn't solve my issue.
4) Using the liveCD, I did another depmod -a then downgraded my kernel to the older package found on the 2008.6 CD. Mkinitcpio completed successfully, everything seemed fine, but... This didn't solve my issue.
I've done these steps over and over again in various orders, trying different combinations, but I've not had any luck.
Here is my current mkinitcpio.conf file:
MODULES="pata_acpi pata_jmicron ata_generic scsi_mod ahci ata_piix ext3 ahci libata cdrom ide-core ide-pci-generic jmicron ieee1394 ohci1394 atl1 mii sr_mod usbcore ehci-hcd uhci-hcd jbd"
BINARIES=""
FILES=""
HOOKS="base udev autodetect pata scsi sata usb net usbinput keymap encrypt filesystems"
Here is the important bit of my grub file:
Without UUIDs:
title Arch Linux
root (hd1,5)
kernel /vmlinuz26 root=/dev/sdb6 quiet vga=869 rootdelay=8 rootfstype=ext3
initrd /boot/kernel26.img
title Arch Linux (fallback)
root (hd1,5)
kernel /vmlinuz26 root=/dev/sdb6 ro quiet vga=869 rootdelay=8
initrd /boot/kernel26-fallback.img
With UUIDs:
title Arch Linux
uuid ec450c30-5197-4330-9831-914eafad66ce
kernel /vmlinuz26 root=/dev/disk/by-uuid/ec450c30-5197-4330-9831-914eafad66ce ro quiet vga=869
initrd /boot/kernel26.img
title Arch Linux (fallback)
uuid ec450c30-5197-4330-9831-914eafad66ce
kernel /vmlinuz26 root=/dev/disk/by-uuid/ec450c30-5197-4330-9831-914eafad66ce ro quiet vga=869
initrd /boot/kernel26-fallback.img
Any ideas, help, suggestions, fixes, etc would be greatly appreciated. I just felt like my arch install was damn near perfect - I'd hate to have to install everything again!
(Edit: Just fixing something I'd messed up in my attempts to fix it, as kindly pointed out by Karol. It didn't fix the problem, though.)
Last edited by binarymonster (2009-06-04 10:03:19)

karol wrote:
If you've read http://bbs.archlinux.org/viewtopic.php?id=63033 I assume you've tried to use 'root=/dev/sdb6' w/
root (hd0,5)
instead of
root (hd1,5)
but didn't work, right?
This one's old (and odd) but you may want to have a look at it anyway http://bbs.archlinux.org/viewtopic.php?pid=376939
And the very bottom of http://bbs.archlinux.org/viewtopic.php?id=44921
I read that first link - though I might have misinterpreted it. I tried keeping (hd1,5) the same and changing /dev/sdb6 to /dev/sda6, etc. I always through that the grub root (hd0,5) wasn't correct, the initramfs would not be able to show up and I'd just get a grub error. What I have tried so far hasn't worked, but I might try changing to (hd0,5) instead of (hd1,5) in a little while.
With regards to the other links, they seem to suggested lots of things I've already tried. The list is getting quite long now!
I have tried reinstalling kernel26, downgrading kernel26, using the fallback image, made sure mkinitcpio.conf contains my filesystem type, made sure mkinitcpio.conf contains my hdd controller module, tried rootdelay=8 a few times... and my mkinitcpio seems to work, so I don't think the problem is with my mkinitcpio.conf file.
Phew! Thanks for your continued help... I'm sure this problem will get solved eventually (and I bet it'll be something simple!). At least I'm learning about chrooting, initramfs, etc.
Do you think it's worth trying to change root (hd1,5) to (hd0,5)? I imagine that would only cause grub to give me and error and not even be able to find the initramfs!

[Solved] Mounting Partitions from Beginners Guide

Hi everyone. I've setup Arch before, but I see that the installer has been removed. I had a question on some of the documentation from the Beginners Guide...
From the section "Prepare the storage drive" it states to setup the partitions like so:
Name Flags Part Type FS Type [Label] Size (MB)
sda1 Boot Primary Linux 15440
sda2 Primary Linux swap / Solaris 1024
sda3 Primary Linux 133000*
In the section below it ("Mount the partitions ") it explains to "mount any other separate partition" like so:
# mkdir /mnt/home
# mount /dev/sda4 /mnt/home
# mkdir /mnt/boot
# mount /dev/sda1 /mnt/boot
However, I set my partitions up just how it was above, when I put in the syntax "mount /dev/sda4 /mnt/home" I receive an error that sda4 doesn't exist. Using my best judgement I put in "mount /dev/sda3 /mnt/home" as I set my partitions exactly the way from the storage drive section (minus some storage space for sda3). I'd just like to be sure that I set this up right and not doing anything extremely wrong. For some reason, Arch won't boot after I have the system setup in virtualbox, and I'm trying to narrow down the issue.
Thanks.
Last edited by Quill (2012-09-01 04:16:22)

Trilby wrote:
It says to do that if you have any additional partitions. You do not.
Sda3 should not be mounted as home, it should be your root partition right? You should have already done
mount /dev/sda3 /mnt
You should not remount sda3 as something else (in fact I suspect it should give an error).
That partition scheme does not have a separate home parition.
Cool, thanks for the info. Yeah, sda3 is set as my root partition. It's solved.

Trouble with luks non root partition

hello,
today i struggled with creating an encryptet archlinux installation.
what i want is to encrypt my root and all other partitions with luks.
basically i used the guide on the archwiki ( https://wiki.archlinux.org/index.php/Dm-crypt_with_LUKS ),
but iam always failing at the same point.
my setup is a bit more complex, but to describe my problem i want to use a simple testcase
/dev/sda with 2 partitions
/dev/sda1 as /boot
/dev/sda2 as crypto_LUKS
/dev/sdb with 1 partition
/dev/sdb1 as crypto_LUKS
/dev/sda2 should be / and /dev/sdb1 f.eks. /home
iam using passphrases for both partitions.
i edited the HOOKS line in mkinitcpio.conf and added "encrypt" before "filesystems",
and i also edited the crypttab to somethink like this:
sdb1_crypt /dev/sdb1 none luks
my fstab entry for /home looks like
/dev/mapper/sdb1_crypt /home ext4 rw,relatime,data=ordered 0 1
so far so good, when iam booting iam prompted for passphrases 2 times. first time to encrypt and mount the root-partition, which works fine.
second time for the /home partition, but then the boot process stucks and systemd times out
[ OK ] Found device /dev/mapper/sdb1_crypt
[ OK ] Started Cryptography Setup for sdb1_crypt
[ OK ] Reached target Encryptet Volumes
[ TIME ] Timed out waiting for device dev-mapper/sdb1_crypt
[ DEPEND ] Dependency failed for /home
[ DEPEND ] Dependency failed for Local File Systems
iam thrown to emergency shell then.
/dev/mapper/sdb1_crypt exists, but when iam trying to mount it with
mount /dev/mapper/sdb1_crypt /mnt
it says
mount: special device /dev/mapper/sdb1_crypt does not exist
cryptsetyp says , that /dev/mapper/sdb1_crypt is inactive.
anyway i can luksOpen it manually with
cryptsetup luksOpen /dev/sdb1 foo
enter passphrase again and now iam able to mount /dev/mapper/foo
what am i missing in my here?
thanks for helping !
ineb

I just worte this. It dose not cover the LVM part. However, you do not need to do anything for that.
Just add this between "keymap encrypt" and "filesystems" in the HOOKS= array
lvm2
Also, becuase you have more then mone parition that is encrypted and needs to be decrypted at boot, you may need to have this the the /etc/default/grub instead of what what I put in the post I linked to.
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda2:root cryptdevice=/dev/sdb1:home"
The `grub-mkconfig -o /boot/grub/grub.cfg` command WILL find all your LVM2 lv's with no problem and configure grub.cfg correctly. You just need to edit /etc/default/grub and use that command to rebuild the grub.cfg
Other then that this post should solve your problems.
https://bbs.archlinux.org/viewtopic.php … 2#p1209702
Last edited by hunterthomson (2012-12-25 02:40:23)

[CLOSED + MOVED]Activate lvm2 on ext3 root partition

Hello guys,
I want to move to lvm2 on my arch installation, I haven't used any lvm before. So here's what I did so far:
1. shrink root partition using gparted to 7 gigabytes
2. created an lvm partition with size 8 gigabytes
3. migrated all files from the root partition to the lvm partition (in single user mode: # rsync -axSX / /newpartition)
4. added lvm2 hook before the filesystems hook in /etc/mkinitcpio.conf according to http://wiki.archlinux.org/index.php/Con … #Using_lvm
5. regenerated the initramfs image using # sudo mkinitcpio -g /boot/kernel26.img
5a. added a grub entry with root=/dev/vg/root (I have no idea what the difference is between that and /dev/mapper/vg-root)
5b. edited /etc/fstab to use /dev/vg/root (again, no idea if /dev/mapper/vg-root would have been more appropriate) as root mountpoint "/"
6. Rebooted
7. Unfortunately, I cannot copy-paste the output, but upon reboot, the initramfs loads fine, it seems to recognize to lvm2 volume, but then says "trying to open console - not found" or something like that and then kernel panics on me.
Any ideas?
thanks!
CLOSED+MOVED:Moving this question elsewhere, as this topic seems too advanced for this subgroup.
Last edited by awayand (2010-01-13 12:44:11)

I used reiserfs for many years, many partitions, many distros and had no problems. Every now and then I'd use ext3 but there were a few issues. I got a new laptop in January and decided to take the plunge: shrunk vista, small ext2 /boot and the rest set up as an encrypted partition with LVM2, all logical volumes set up as ext4 (except swap!). I've been very impressed with ext4 stability.
Oh, and step (5) edit fstab to reflect the new file systems, make sure /etc/mtab doesn't exist.

Can't get lvm/luks to boot - cannot find root partition

Hi,
I'm trying to get a dm-crypt on top of lvm to boot but without success so far. I followed http://wiki.archlinux.org/index.php/Sys … r_dm-crypt and http://wiki.archlinux.org/index.php/Ins … AID_or_LVM, everything works fine (I can mount the partition) but when I try to boot from it, it cannot find the crypted partition and fails.
USELVM="yes"
HOOKS="base udev usb usbinput lvm2 encrypt filesystems"
root=/dev/mapper/sda2 cryptdevice=/dev/sda2:root2-lvol0 ro
jan@jan ~/src/xf86-video-ati $ ll /dev/mapper/
insgesamt 0
crw-rw---- 1 root root 10, 62 21. Feb 2008 control
brw------- 1 root disk 254, 0 21. Feb 2008 root
brw------- 1 root disk 254, 1 21. Feb 2008 root2-lvol0
brw------- 1 root disk 254, 2 21. Feb 2008 sda2
/dev/mapper/root is my current encrypted / without lvm
The boot process successfully identifies the lvm /dev/mapper/root2-lvol0 and continues with hook 'encrypt' but doesn't ask me for a passphrase but goes on to hook 'filesystems' and fails then because it can't mount the correct root-partition obviously.
There's only /dev/mapper/root2-lvol0 and /dev/mapper/control when I'm in the rescue sh from initrd.
Anyone got that combination to work?
- Jan

Reboot, at the sound of the chime (not before) depress the option key, when the startup manager appears choose OSX.

[SOLVED]Root file system changed

I'm currently using ArchLinux
I'm not sure what went wrong, but now when I login as root and "cd" I don't see the root file system. Instead i see
[root@aspect ~]# ls -al
total 36
drwxr-x--- 7 root root 4096 Apr 13 16:29 .
drwxr-xr-x 17 root root 4096 Apr 13 08:18 ..
-rw------- 1 root root 2849 Apr 13 16:27 .bash_history
drwxr-xr-x 2 root root 4096 Apr 13 10:35 .config
drwx------ 3 root root 4096 Apr 13 10:34 .dbus
-rw------- 1 root root 49 Apr 13 10:35 .directory
drwxr-xr-x 3 root root 4096 Apr 13 10:34 .kde4
drwxr-xr-x 3 root root 4096 Apr 13 10:35 .local
drwx------ 3 root root 4096 Apr 13 16:29 .nv
If I cd to ".." I can see the root file system from there.
Also When I drag files into terminal, it can't locate them. I Used a java folder I had in downlaods as an example. But it's like this everywhere.
[aspect@aspect ~]$ file:///home/aspect/Downloads/jre bash: file:///home/aspect/Downloads/jre: No such file or directory
Last edited by aspectratio (2015-04-13 22:05:33)

ewaller wrote:
aspectratio wrote:I've already done all of this. What makes you think I was running KDE as root?
drwxr-xr-x 3 root root 4096 Apr 13 10:34 .kde4
Sometime today a hidden directory containing kde files was created in the /root being owned by root. That's how
So the problem here is I came from debian. And aparently there when you cd as root, it will bring you to the atual file system.
Fair enough.
I was told to edit /etc/passwd and change the root dir to just / from /bin/bash
Now I can no longer login as root. I will try to boot recue mode and chroot into the system to fix the file.
That would be the way to fix it. You may not need to actually chroot, just mount the root partition at /mnt and edit /mnt/etc/passwd.
As to not running desktop environments as root -- it is a pet peeve of mine. I am not saying this about you, you understand the issue; but I have had arguments with people in the past about not running GUI DEs as root, and them insisting on it being their machines and they can do what they want. They are absolutely correct. But they can also fend for themselves.
Edit: If you do have another user in wheel, and if wheel can gain root privileges, just log in as that user and use sudo to fix it.
Yeah it's a security risk.
I've fixed the file. But I'm just not sure why I can't drag and drop paths anymore. It apears as though it's not a common thing anyways.

[SOLVED] Root partition wrongly assumed to be encrypted.

Similar Messages

Maybe you are looking for