[Solved] Problem booting root in LVM, which spans two LUKS partitions

Hello,
I recently switched to Arch from OpenSuse, and I'm having a bit of trouble getting my encrypted disks to boot properly. I have two disks, the first is a 4 TB drive set up like this:
MBR partition table
Partition 1 - Windows 7, 200GB
Partition 2 - Linux boot, 200MB
Partition 3 - Luks partition, 1.7TB
Partition 4 - Luks partition, 1.7TB
Within partition 3 and 4 is an LVM volume which spans the two partitions. The reason for that is just that I can't have a 3.4TB partition on an MBR formatted drive (as I understand it). I have the root volume and swap, etc within this LVM. The second hard drive is simply a data drive, also encrypted. My problem is that I don't know how to tell the system to open both of these encrypted partitions at boot, in order to boot the root volume. This worked fine under OpenSuse and I only needed to enter the Luks password once (it is the same for both partitions).
As it is right now, my boot parameters in /etc/default/grub look like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset cryptdevice=/dev/sda3:sda3_crypt root=/dev/mapper/vg_arch-root"
Currently the system boots, asks for the password to /dev/sda3, hangs for roughly 20 seconds and then kicks me into a root prompt. I can manually open /dev/sda4 at this point using cryptsetup and the system will continue booting normally... but I would like to have it set up properly, so I don't need to do that. Considering OpenSuse does this out of the box I figured it should be possible under Arch. Any help would be appreciated.
Thanks
Last edited by keitolainen (2015-06-09 21:56:08)

As a quick update in case anyone is reading this, I cleaned up the script a bit and hopefully made it something closer to a "proper" fix.
Rather than editing /usr/lib/initcpio/hooks/encrypt directly, I did the following:
cp /usr/lib/initcpio/hooks/encrypt /etc/initcpio/hooks/
then changed the following section of /etc/initcpio/hooks/encrypt from:
# Ask for a passphrase
if [ ${dopassphrase} -gt 0 ]; then
echo ""
echo "A password is required to access the ${cryptname} volume:"
#loop until we get a real password
while ! eval cryptsetup open --type luks ${resolved} ${cryptname} ${cryptargs} ${CSQUIET}; do
sleep 2;
done
fi
to:
# Ask for a passphrase
if [ ${dopassphrase} -gt 0 ]; then
echo ""
while true ; do
echo -n "A password is required to access the ${cryptname} volume: "
read -sr password
echo $password | cryptsetup open --type luks ${resolved} ${cryptname} ${cryptargs} ${CSQUIET}
if [ $? = 0 ] ; then
break
fi
done
echo $password | cryptsetup open --type luks /dev/sda4 sda4_crypt
echo ""
fi
then edited /etc/mkinitcpio.conf and changed:
FILES=""
to:
FILES="/etc/initcpio/hooks/encrypt"
and ran
mkinitcpio
This is working well for me and I think it's a little cleaner than the solution I posted earlier. Sorry for the awkward bash, if anyone has a more elegant solution please let me know.

Similar Messages

  • [Solved]Problem booting - nvidia is trying to boot, but not succeeding

    I did a recent pacman -Syu upgrade which failed due to files existing already - they were
    /usr/lib/libEGL.so.1
    /usr/lib/libEGL.so
    /usr/lib/libGLESv1_CM.so
    /usr/lib/libGLESv1_CM.so.1
    /usr/lib/libGLESv2.so
    /usr/lib/libGLESv2.so.2
    So I moved these files so they had an extension of -old after them - they are still there.
    The upgrade succeeded - but applications wouldn't run.
    I had a problem running some applications after this upgrade (e.g. firefox complained about some sort of XCOM - I wish I wrote this command down).
    Now, when I boot, X fails to start with nvidia splash screen cycling around and keyboard not loading (I can't interrupt this loop). When booting normally I get the last reports to screen -
    started account service Reached target graphical interface arch
    I've since managed to boot in at what is similar to the old run level 1 - with root.
    What are the best ways of recovering this system and allowing nvidia to boot syccessfully?
    Last edited by kabads (2014-03-08 18:20:19)

    Roll back the nvidia update, move back the files you moved, wait for the package conflict to be resolved (should be imminent -- packages are already in testing[1]), and next time please search before posting or trying to fix problems like this, chances are it's not just affecting you [2].
    [1] https://bugs.archlinux.org/task/39219?p … idia-libgl
    [2] https://bbs.archlinux.org/viewtopic.php?id=178189

  • [Solved] Problem with a SD card which I can't mount

    Hello everybody!
    So, when I'm plugging in my SD card ( from my camera ) then I use the dmesg command to know that it is known as /dev/mmcblk0
    Then I try to mount it by pmount /dev/mmcblk0 SD but it doesn't work :
    The error message is : bad block or bad fiel system type.
    I've tried the "-t" option to use a specific file system, but none work at all.
    My SD card is working properly on another computer so I know it is fine. But I don't know what file system a SD card uses.
    I really hope you'll help me!!!
    Last edited by jiehong (2009-03-19 20:28:31)

    Yes, I'ma member of the storage group of course.
    # fdisk -l /dev/mmcblk0
    Disc /dev/mmcblk0: 2057 Mo, 2057830400 octets
    53 heads, 52 secteurs/piste, 1458 cylinders
    Unities = cylinders of 2756 * 512 = 1411072 octets
    Disc identifier : 0x00000000
    Device Amorce Begin End Blocs Id System
    /dev/mmcblk0p1 1 1459 2009478+ 6 FAT16
    And blkid /dev/mmcblk0 don't give anything.

  • [solved] Update got me stuck on boot after activating lvm

    I did an update which contained a new kernel.  Now the system just hangs after this...
    Activating logical volumes
    4 logical volume(s) in volume group "VolGroup00" now active.
    Now I've booted in the live environment and use vgscan and vgchange -ay and I can see my partitions in /dev/mapper.  /boot is on it's own partition, not on lvm.
    I believe I need to rebuild the image, but I'm unsure as to how I should mount my partitions, and which partitions I should mount.  root, var, swap  and home are on lvm.  I tried figuring it out with the wiki, but my brain is burnt, and I'm really going nowhere fast.  Anybody could take pity on me and just give me the answer of what come next?
    Last edited by jpsimard (2012-04-28 01:11:11)

    boast wrote:Can you tell me everything you did? I need help
    I had the same problem. Here's a step by step solution:
    * Boot a live cd
    * # vgchange -ay
    * Mount your / partition to a folder
    * Bind proc, dev and sys like this:
    mount -t proc proc ${your-root}/proc
    mount -t sysfs sys ${your-root}/sys
    mount -o bind /dev ${your-root}/dev
    * # chroot ${your-root} /bin/bash
    Once you are in the chroot, mount your boot partition to /boot (do this *inside* the chroot!)
    * #mkinitcpio -p linux
    * reboot
    Hope it helps

  • [SOLVED] Weird Boot Problem

    I carried out an -Syu on my eeepc a couple of weeks ago. Unusually, this resulted in all kinds of error messages at boot time. most of which I've hunted down and squashed. The machine has functioned correctly throughout.
    However, there is one message which I cannot find. When the system boots, the on-screen command line output displayed before the desktop is loaded (lxde) shows a "Login:" prompt, which is followed immediately by the display of an error message
    FATAL: Module and not found
    I can't find this in any of the logs, so I don't know where to begin. Module "and"??!!
    Any advice would be very welcome.
    Thanks in advance
    Last edited by myrlin (2011-10-28 14:10:21)

    I have just discovered that this message is being generated by UFW.
    I have it in my Daemons array.
    A manual start (or restart) also fails with the same message.
    Strangely, when accessing UFW through GUFW, all seems to be normal.
    "ufw status" reports "active". Curious!
    **EDIT**
    I finally solved the problem by completely removing ufw and gufw (including ALL configuration files), then re-installing. I never did find out what had been corrupted, or how, but - hey - life's too short!!
    Many thanks to everyone for their help and support
    Last edited by myrlin (2011-10-28 14:13:36)

  • [SOLVED] USB installation, booting: root fs cannot be detected

    I followed this guide: http://wiki.archlinux.org/index.php/Ins … _a_USB_key
    SYMPTOMS
    I installed arch linux on a USB stick.
    I can see Grub, I can boot. After the HOOKS get loaded (udev is loaded as well: Loading udev...done.) I get errors as follows:
    Attempting to create root device '/dev/disk/by-uuid/myHdUUID'
    unknown
    ERROR: root fs cannot be detected. Try using rootfstype= kernel parameter.
    If the device '/dev/disk/by-uuid/myHdUUID' gets created while you are here, try adding 'rootdelay=8' or higher to the kernel command-line...
    Then I get a prompt that doesn't even let me issue the command "ls" (error: /bin/bash: ls: not found
    SOLUTION: use the fallback image, or better, rebuild your mkinitcpio kernel image, see: Configuring mkinitcpio
    My problem was that "usb" was not included in the HOOKS, it was present, yes but after the "autodetect".
    So, in the /etc/mkinitcpio.conf place "usb" before "autodetect", e.g. as follows:
    HOOKS="base udev autodetect sata filesystems"
    then regenerate the image (refer to the previous link to understand why the autodetect was creating the problems and to see exactly how to regenerate the image)
    Last edited by firepol (2008-10-09 19:18:34)

    Same problem, seems the new kernel broke UUID.
    @tim: as I stated above it seems that you fixed the problem with the kernel image file but did not adjust the grub menu to compensate for the fact that UUID is broken and thats why you got the same result even after fixing the image, lucky for me I had some broken hooks and only my fallback image generated properly so I figured it out, although it took me a little while.
    Anyhow this is basically what needs to be done to correct the problem.
    1. Boot ArchLive
    2. mkdir /media/disk
    3. mount /dev/sdxX /media/disk
    4. chroot /media/disk
    5. mkinitcpio -k 2.6.28-ARCH -g /boot/kernel26.img
    6. nano /boot/grub/menu.lst
    7. Replace any references to UUID with /dev/sdxX (where xX represents your drive and partition) instead, save and exit nano.
    8. reboot
    Make sure and pay attention to the output of the mkinitcpio command in my step 5. If there are any errors relating to one or more of the hooks you'll need to edit /etc/mkinitcpio.conf and remove the hook it complains about !!IF POSSIBLE!!.  I for example had some problem with the autodetect hook which caused my regular kernel to fail to create an image.
    If mkinicpio doesn't complain and tells you it SUCCEEDED generating the images then you should be good to go.
    Last edited by blazercist (2009-01-29 18:47:25)

  • [SOLVED]Dual boot problem with an Asus UX31A (EFI)

    I never did an EFI install before and I still don't understand how it works however following the Zenbook wiki, I have successfully installed Arch. Now I can't boot Windows 7 anymore. I am using grub2, have installed os-prober. Grub menu has windows 7 entry but when used prompts a wrong EFI file path error.
    My partition table is:
    [root@zenbook sonay]# lsblk
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    sda 8:0 0 238.5G 0 disk
    ├─sda1 8:1 0 200M 0 disk
    ├─sda2 8:2 0 128M 0 disk
    ├─sda3 8:3 0 98.6G 0 disk
    ├─sda4 8:4 0 4G 0 disk
    ├─sda5 8:5 0 90.7G 0 disk
    ├─sda6 8:6 0 512M 0 disk /boot/efi
    ├─sda7 8:7 0 3.9G 0 disk
    ├─sda8 8:8 0 10G 0 disk
    ├─sda9 8:9 0 200M 0 disk /boot
    └─sda10 8:10 0 30.3G 0 disk /
    sdc 8:32 0 931.5G 0 disk
    └─sdc1 8:33 0 931.5G 0 disk /run/media/sonay/My Passport
    /dev/sda1 used to be Windows 7 EFI partition. Gparted says it is flagged as boot.
    What I did to install arch:
    Partitioned /dev/sda5 with windows disk manager to create linux partitions and formatted the new partitions with gparted as the noob I am.
    created /dev/sda6 for EFI boot
    created /dev/sda9 for boot partition
    created /dev/sda10 as root.
    Did not touch
    /dev/sda1 which was the EFI partition named SYSTEM
    /dev/sda2 which was windows boot partition
    /dev/sda3 which was windows C:,
    /dev/sda4 and /dev/sda7 which I don't know what they used to be (possible for Asus fast wake up or swap whatever)
    /dev/sda8 which is recovery partition.
    I did not touch any grub files, except /etc/default/grub
    [sonay@zenbook ~]$ cat /etc/default/grub
    GRUB_DEFAULT=0
    GRUB_TIMEOUT=1
    GRUB_DISTRIBUTOR="Arch"
    GRUB_CMDLINE_LINUX_DEFAULT="quiet init=/bin/systemd add_efi_memmap elevator=noop i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0"
    GRUB_CMDLINE_LINUX=""
    # Preload both GPT and MBR modules so that they are not missed
    GRUB_PRELOAD_MODULES="part_gpt part_msdos"
    # Uncomment to enable Hidden Menu, and optionally hide the timeout count
    #GRUB_HIDDEN_TIMEOUT=5
    #GRUB_HIDDEN_TIMEOUT_QUIET=true
    # Uncomment to use basic console
    GRUB_TERMINAL_INPUT=console
    # Uncomment to disable graphical terminal
    #GRUB_TERMINAL_OUTPUT=console
    # The resolution used on graphical terminal
    # note that you can use only modes which your graphic card supports via VBE
    # you can see them in real GRUB with the command `vbeinfo'
    GRUB_GFXMODE=auto
    # Uncomment to allow the kernel use the same resolution used by grub
    GRUB_GFXPAYLOAD_LINUX=keep
    # Uncomment if you want GRUB to pass to the Linux kernel the old parameter
    # format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
    #GRUB_DISABLE_LINUX_UUID=true
    # Uncomment to disable generation of recovery mode menu entries
    GRUB_DISABLE_RECOVERY=true
    # Uncomment and set to the desired menu colors. Used by normal and wallpaper
    # modes only. Entries specified as foreground/background.
    #GRUB_COLOR_NORMAL="light-blue/black"
    #GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
    # Uncomment one of them for the gfx desired, a image background or a gfxtheme
    #GRUB_BACKGROUND="/path/to/wallpaper"
    #GRUB_THEME="/path/to/gfxtheme"
    # Uncomment to get a beep at GRUB start
    #GRUB_INIT_TUNE="480 440 1"
    #GRUB_SAVEDEFAULT="true"
    Finally my /boot/grub/grub.cfg is:
    [sonay@zenbook ~]$ cat /etc/default/grub
    GRUB_DEFAULT=0
    GRUB_TIMEOUT=1
    GRUB_DISTRIBUTOR="Arch"
    GRUB_CMDLINE_LINUX_DEFAULT="quiet init=/bin/systemd add_efi_memmap elevator=noop i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0"
    GRUB_CMDLINE_LINUX=""
    # Preload both GPT and MBR modules so that they are not missed
    GRUB_PRELOAD_MODULES="part_gpt part_msdos"
    # Uncomment to enable Hidden Menu, and optionally hide the timeout count
    #GRUB_HIDDEN_TIMEOUT=5
    #GRUB_HIDDEN_TIMEOUT_QUIET=true
    # Uncomment to use basic console
    GRUB_TERMINAL_INPUT=console
    # Uncomment to disable graphical terminal
    #GRUB_TERMINAL_OUTPUT=console
    # The resolution used on graphical terminal
    # note that you can use only modes which your graphic card supports via VBE
    # you can see them in real GRUB with the command `vbeinfo'
    GRUB_GFXMODE=auto
    # Uncomment to allow the kernel use the same resolution used by grub
    GRUB_GFXPAYLOAD_LINUX=keep
    # Uncomment if you want GRUB to pass to the Linux kernel the old parameter
    # format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
    #GRUB_DISABLE_LINUX_UUID=true
    # Uncomment to disable generation of recovery mode menu entries
    GRUB_DISABLE_RECOVERY=true
    # Uncomment and set to the desired menu colors. Used by normal and wallpaper
    # modes only. Entries specified as foreground/background.
    #GRUB_COLOR_NORMAL="light-blue/black"
    #GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
    # Uncomment one of them for the gfx desired, a image background or a gfxtheme
    #GRUB_BACKGROUND="/path/to/wallpaper"
    #GRUB_THEME="/path/to/gfxtheme"
    # Uncomment to get a beep at GRUB start
    #GRUB_INIT_TUNE="480 440 1"
    #GRUB_SAVEDEFAULT="true"
    [sonay@zenbook ~]$ cat /boot/grub/grub.cfg
    cat: /boot/grub/grub.cfg: Permission denied
    [sonay@zenbook ~]$ su
    Password:
    [root@zenbook sonay]# cat /boot/grub/grub.cfg
    # DO NOT EDIT THIS FILE
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    ### BEGIN /etc/grub.d/00_header ###
    insmod part_gpt
    insmod part_msdos
    if [ -s $prefix/grubenv ]; then
    load_env
    fi
    set default="0"
    if [ x"${feature_menuentry_id}" = xy ]; then
    menuentry_id_option="--id"
    else
    menuentry_id_option=""
    fi
    export menuentry_id_option
    if [ "${prev_saved_entry}" ]; then
    set saved_entry="${prev_saved_entry}"
    save_env saved_entry
    set prev_saved_entry=
    save_env prev_saved_entry
    set boot_once=true
    fi
    function savedefault {
    if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
    fi
    function load_video {
    if [ x$feature_all_video_module = xy ]; then
    insmod all_video
    else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
    fi
    if [ x$feature_default_font_path = xy ] ; then
    font=unicode
    else
    insmod part_gpt
    insmod ext2
    set root='hd0,gpt10'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt10 --hint-efi=hd0,gpt10 --hint-baremetal=ahci0,gpt10 cf66f05a-418c-4517-a0e0-af01b3be4a67
    else
    search --no-floppy --fs-uuid --set=root cf66f05a-418c-4517-a0e0-af01b3be4a67
    fi
    font="/usr/share/grub/unicode.pf2"
    fi
    if loadfont $font ; then
    set gfxmode=auto
    load_video
    insmod gfxterm
    set locale_dir=$prefix/locale
    set lang=en_US
    insmod gettext
    fi
    terminal_input console
    terminal_output gfxterm
    set timeout=1
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Arch GNU/Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-cf66f05a-418c-4517-a0e0-af01b3be4a67' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_gpt
    insmod ext2
    set root='hd0,gpt9'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt9 --hint-efi=hd0,gpt9 --hint-baremetal=ahci0,gpt9 42d2ba69-758d-4a54-9482-ae5d60866a52
    else
    search --no-floppy --fs-uuid --set=root 42d2ba69-758d-4a54-9482-ae5d60866a52
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /vmlinuz-linux root=UUID=cf66f05a-418c-4517-a0e0-af01b3be4a67 ro quiet init=/bin/systemd add_efi_memmap elevator=noop i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux.img
    menuentry 'Arch GNU/Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-cf66f05a-418c-4517-a0e0-af01b3be4a67' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_gpt
    insmod ext2
    set root='hd0,gpt9'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt9 --hint-efi=hd0,gpt9 --hint-baremetal=ahci0,gpt9 42d2ba69-758d-4a54-9482-ae5d60866a52
    else
    search --no-floppy --fs-uuid --set=root 42d2ba69-758d-4a54-9482-ae5d60866a52
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /vmlinuz-linux root=UUID=cf66f05a-418c-4517-a0e0-af01b3be4a67 ro quiet init=/bin/systemd add_efi_memmap elevator=noop i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux-fallback.img
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_linux_xen ###
    ### END /etc/grub.d/20_linux_xen ###
    ### BEGIN /etc/grub.d/20_memtest86+ ###
    ### END /etc/grub.d/20_memtest86+ ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry 'Windows 7 (loader) (on /dev/sda3)' --class windows --class os $menuentry_id_option 'osprober-chain-5246C0D846C0BE4B' {
    insmod part_gpt
    insmod ntfs
    set root='hd0,gpt3'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 5246C0D846C0BE4B
    else
    search --no-floppy --fs-uuid --set=root 5246C0D846C0BE4B
    fi
    chainloader +1
    menuentry 'Windows Recovery Environment (loader) (on /dev/sda8)' --class windows --class os $menuentry_id_option 'osprober-chain-3C98C9B298C96B4A' {
    insmod part_gpt
    insmod ntfs
    set root='hd0,gpt8'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt8 --hint-efi=hd0,gpt8 --hint-baremetal=ahci0,gpt8 3C98C9B298C96B4A
    else
    search --no-floppy --fs-uuid --set=root 3C98C9B298C96B4A
    fi
    drivemap -s (hd0) ${root}
    chainloader +1
    ### END /etc/grub.d/30_os-prober ###
    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###
    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f ${config_directory}/custom.cfg ]; then
    source ${config_directory}/custom.cfg
    elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
    source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###
    SOLUTION:
    first I needed to mount Windows EFI partition which was /dev/sda1, so :
    mount /dev/sda1 /mnt
    Then issue the following commands and take note of the outputs:
    grub-probe --target=fs_uuid /mnt/EFI/Microsoft/Boot/bootmgfw.efi
    which outputs: 18DF-E58E and
    grub-probe --target=hints_string /mnt/EFI/Microsoft/Boot/bootmgfw.efi
    which outputs: --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1
    Finally edit the os-prober entry to the following in /boot/grub/grub.cfg
    menuentry 'Windows 7 (loader) (on /dev/sda3)' --class windows --class os $menuentry_id_option 'osprober-chain-5246C0D846C0BE4B' {
    insmod part_gpt
    insmod fat
    insmod search_fs_uuid
    insmod chain
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 18DF-E58E
    chainloader /EFI/Microsoft/Boot/bootmgfw.efi
    Last edited by sonay (2012-10-07 18:20:20)

    grub-probe --target=hints_string /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi
    --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1
    Sorry, no need to anymore. Thanks anyways.
    Last edited by sonay (2012-10-07 18:08:39)

  • Does Adobe ever look at these forums to try to solve problems which have been reported???

    Does Adobe ever look at these forums to try to solve problems which have been reported?  Doesn't seem like we are getting any answers, does it??

    I think the best idea is to contact the book publishers, let them know that Adobe Digital Editions is not capable of delivering their book to you, and ask in what other, more reliable formats they can provide it. 

  • Root on LVM & shutting down

    I was originally going to post this problem b/c I believed it was causing corruption in my filesystem; I have since decided that it's in fact botched suspend2-attempts that are causing the corruptions (which ALSO isn't good, of course). Anyway, as the title indicates, I run root-on-lvm, and have the nagging problem that when rc.shutdown goes to deactivate the logical volumes, it fails since root is obviously still being used. It seems like sort of a chicken-and-egg problem, since you can't unmount root before deactivating the volume group since you need the lvm binary, but you can't deactivate the volume group b/c root is still mounted... I guess I'm just checking that this sort of behaviour is "normal", and that other users running root-on-lvm see it also. I'm trying to eliminate this as a cause for my filesystem corruptions.

    Hi I've managed to solve this problem. See my post https://bbs.archlinux.org/viewtopic.php … 95#p827495

  • [SOLVED] Cloning boot and var partitions to a new drive for booting

    Ok first of all here's my setup:
    fakeraid (dmraid) / and home on an OCZ Revodrive
    boot with GRUB on a flash drive (since fakeraid doesn't support grub)
    var and downloads/media folder on a 500GB WD Caviar drive
    When I originally installed Arch I had the Caviar drive in my home server in a RAID5 array, so that's why I opted to install boot and grub on a flash drive simply for booting.  Now that I have the drive in my desktop I've cloned the flash drive's partitions and MBR using dd:
    #dd if=/dev/sde of=~/MBR.img bs=512 count=1
    #dd if=/dev/sde1 of=~/boot.img
    #dd if=/dev/sdc1 of=~/var.img
    I then backed up my downloads/media partition, then removed the partition table, then used dd to put the img files on the Caviar drive.
    #dd if=~/MBR.img of=/dev/sdc bs=512 count=1
    #dd of=~/boot.img of=/dev/sdc1
    #dd of=~/var.img of=/dev/sdc2
    I also created labels for the filesystems and put those in fstab.
    I'm able to mount both partitions, however I can't boot from the drive.  I get a 'grub hard disk error' (no error number) when I put it as my first drive in the BIOS. 
    I can still use the flash drive as the first hard drive in the BIOS and boot from it, then it mounts the dmraid root partition and boots successfully.  It is also able to mount the var and boot partitions in fstab. 
    Basically the only problem is that the MBR is somehow wrong.  I then tried booting back into an Arch live USB and installing GRUB from the prompt:
    grub
    grub>setup (hd4,0) (in this case the Caviar drive's boot partition was /dev/sde1
    So essentially what I'm asking is how GRUB handles the MBR.  Is it specific to the partition table of the drive in which it resides when it's originally installed?  For instance, since I had an 8GB flash drive with 2 partitions when I installed GRUB, is the backed up MBR no good for a 500GB drive with 3 partitions?
    I have everything backed up so I can start with a fresh /boot and /var if need be....I'm just not sure where to start. 
    Thanks in advance.
    Last edited by DarksideEE7 (2011-02-13 23:25:31)

    Sorry, I forgot to mention that I tried to install GRUB from the GRUB shell in a live Arch USB.  It failed on a few non-critical parts, and succeeded on the last part. I'm going to try again shortly, possibly I did something wrong.  GRUB is able to find the stage files using:
    #grub
    grub>find /grub/stage1
    grub> find /grub/stage1
    (hd0,0)
    (hd5,0)
    grub>
    (hd0,0) is the desired boot drive, while (hd5,0) is the current bootable flash drive with /boot and GRUB installed.
    Here is the output of fdisk -l:
    WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn't support GPT. Use GNU Parted.
    Disk /dev/sde: 2000.4 GB, 2000398934016 bytes
    256 heads, 63 sectors/track, 242251 cylinders, total 3907029168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00000000
    Device Boot Start End Blocks Id System
    /dev/sde1 1 3907029167 1953514583+ ee GPT
    Disk /dev/sdb: 60.0 GB, 60022480896 bytes
    255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0xedb72db9
    Device Boot Start End Blocks Id System
    /dev/sdb1 * 2048 206847 102400 7 HPFS/NTFS
    /dev/sdb2 206848 117227519 58510336 7 HPFS/NTFS
    Disk /dev/sdd: 40.0 GB, 40018599936 bytes
    255 heads, 63 sectors/track, 4865 cylinders, total 78161328 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdd doesn't contain a valid partition table
    Disk /dev/sdc: 40.0 GB, 40018599936 bytes
    32 heads, 32 sectors/track, 76329 cylinders, total 78161328 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0xb8372fcd
    Device Boot Start End Blocks Id System
    /dev/sdc1 32 21484543 10742256 83 Linux
    /dev/sdc2 21484544 156317695 67416576 83 Linux
    Disk /dev/sda: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x8497e059
    Device Boot Start End Blocks Id System
    /dev/sda1 * 2048 206847 102400 83 Linux
    /dev/sda2 206848 42149887 20971520 83 Linux
    /dev/sda3 42149888 976773167 467311640 83 Linux
    Disk /dev/dm-0: 80.0 GB, 80035053568 bytes
    32 heads, 32 sectors/track, 152654 cylinders, total 156318464 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 65536 bytes / 131072 bytes
    Disk identifier: 0xb8372fcd
    Device Boot Start End Blocks Id System
    /dev/dm-0p1 32 21484543 10742256 83 Linux
    Partition 1 does not start on physical sector boundary.
    /dev/dm-0p2 21484544 156317695 67416576 83 Linux
    Disk /dev/dm-1: 11.0 GB, 11000070144 bytes
    255 heads, 63 sectors/track, 1337 cylinders, total 21484512 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 65536 bytes / 131072 bytes
    Alignment offset: 49152 bytes
    Disk identifier: 0x00000000
    Disk /dev/dm-1 doesn't contain a valid partition table
    Disk /dev/dm-2: 69.0 GB, 69034573824 bytes
    255 heads, 63 sectors/track, 8392 cylinders, total 134833152 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 65536 bytes / 131072 bytes
    Disk identifier: 0x00000000
    Disk /dev/dm-2 doesn't contain a valid partition table
    Disk /dev/sdf: 8086 MB, 8086618112 bytes
    249 heads, 62 sectors/track, 1023 cylinders, total 15794176 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x8497e059
    Device Boot Start End Blocks Id System
    /dev/sdf1 * 62 200693 100316 83 Linux
    /dev/sdf2 200694 15794175 7796741 83 Linux
    I'm using dmraid, so just to be clear I've configured the raid using:
    #modprobe dm_mod
    #dmraid -ay
    Then I saw the array stored in /dev/mapper/silXXXXX.  I then created partitions for /boot, /, and home.  At that time I was hoping to get GRUB working with the AUR package grub2-dmraid.  I wasn't able to get it working for some time, so I just went ahead and installed boot and GRUB to a separate USB flash drive.
    Here is the output of df -h:
    Filesystem Size Used Avail Use% Mounted on
    udev 10M 268K 9.8M 3% /dev
    /dev/mapper/sil_bgbgdjaddicbp1
    11G 5.3G 4.3G 56% /
    shm 6.0G 584K 6.0G 1% /dev/shm
    /dev/mapper/sil_bgbgdjaddicbp2
    64G 38G 23G 63% /home
    /dev/sda1 95M 16M 75M 18% /boot
    /dev/sda2 19G 142M 19G 1% /var
    /dev/sda3 439G 148G 269G 36% /home/l33/Torrents
    none 1000M 132K 1000M 1% /tmp
    shm 6.0G 584K 6.0G 1% /dev/shm
    /dev/sde1 1.8T 1.1T 665G 62% /mnt/Green
    and cat /etc/mtab
    proc /proc proc rw,nosuid,nodev,noexec,relatime
    sys /sys sysfs rw,nosuid,nodev,noexec,relatime
    udev /dev devtmpfs rw,nosuid,relatime,size=10240k,nr_inodes=1022975,mode=755
    /dev/mapper/sil_bgbgdjaddicbp1 / ext4 rw,noatime,barrier=1,stripe=32,data=ordered
    devpts /dev/pts devpts rw 0 0
    shm /dev/shm tmpfs rw,nosuid,nodev 0 0
    /dev/mapper/sil_bgbgdjaddicbp2 /home ext4 rw,noatime 0 0
    /dev/sda1 /boot ext2 rw 0 0
    /dev/sda2 /var reiserfs rw,noatime 0 0
    /dev/sda3 /home/l33/Torrents ext4 rw,noatime 0 0
    none /tmp tmpfs rw,nosuid,nodev,noatime,size=1000M,mode=1777 0 0
    shm /dev/shm tmpfs rw,nosuid,nodev,size=6G 0 0
    rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
    nfsd /proc/fs/nfsd nfsd rw,noexec,nosuid,nodev 0 0
    /dev/sde1 /mnt/Green ext4 rw 0 0
    Also I don't have a /proc/mdstat.  That's only for mdadm RAID setups, right?  It's been quite some time since I've used mdadm so I can't remember.
    EDIT:
    So I booted into a live Arch USB and entered the grub shell.  I ran:
    #grub
    grub> root (hd3,0)
    Filesystem type is ext2fs, partition type 0x83
    grub> setup (hd3)
    Checking if "/boot/grub/stage1" exists.....no
    Checking if "/grub/stage1 exists.......yes
    Checking if "/grub/stage2 exists.......yes
    Checking if "/grub/e2fs_stage1_5 exists....yes
    Running "embed /grub/e2fs_stage1_5 (hd3)".....25 sectors are embedded.
    succeeded
    Running "install /grub/stage1 (hd3) (hd3))1+25 p (hd3,0)/grub/stage2 /grub/menu.lst".......succeeded
    Done.
    Last time I recall more errors than this, then it reporting that one was a non-critical error, so I think the problem may be solved.  More to come.
    Last edited by DarksideEE7 (2011-02-13 23:18:44)

  • [solved] "No boot signature in partition"

    "No boot signature in partition" is the message i get when my computer boots.
    I always had an ata disk it booted from, sda. the OS was on sdb. I got rid of the ata disk and wanted my pc to boot from the disc which contains the OS. So hdb became sda. I installed lilo to the mbr and lilo reported it to be succesful. The partition on which the os resides is flagged bootable.
    This is in my lilo.conf:
    boot=/dev/sda
    default=arch
    timeout=50
    lba32
    prompt
    image=/boot/vmlinuz26
    label=arch
    root=/dev/sda1
    initrd=/boot/kernel26.img
    read-only
    image=/boot/vmlinuz26
    label=arch-fallback
    root=/dev/sda1
    initrd=/boot/kernel26-fallback.img
    read-only
    btw: I installed lilo with "lilo -M /dev/sdb" while the ata-disk was still plugged in. I then removed the disk.
    I dont know what to do. Anyone knows a solution?
    Last edited by build (2009-07-31 21:04:59)

    hello djszapi!
    At first I had problems with grub too. But I always had used lilo, so after the diskswitch I decided to go back to lilo bc grub wasnt doing what i wanted it to do.
    Eitherway, it is solved now. Grub did the trick and shone light on my darkest hour. Grub dissolved the dark enigma of boot signature problems and made them part of the past.
    Thanks
    Last edited by build (2009-07-31 21:03:24)

  • Very strange hard disk problem - Boot Camp/Windows related?

    On my first gen 1.83 GHz MacBook Pro (now at 10.5.2 with all System Updates applied), I've had Win XP Home installed under Boot Camp (from the very first beta, updated to the release Boot Camp assistant now) for well over a year. At one time about 14 months ago I tried using Parallels, but that used too much battery power, so I deleted Parallels. I don't know whether that left any traces of itself behind.
    More recently I've been amazed at how well VMWare Fusion works on my Mac Pro, so I decided to try it on my laptop. I installed the Fusion application and tried to "adopt" my Boot Camp partition installation of Win XP. I think I goofed and didn't install VMWare tools at the proper moment, because Windows went on a self-directed hunt for drivers after installation, and when I tried to start the virtual machine inside Fusion, Windows told me it needed to be activated by Microsoft and wouldn't even allow me to log in to do the activation.
    Wondering whether there might be some residual of the Parallels "hooks" to Windows contaminating things, I decided just to reinstall Windows.
    I used Boot Camp Assistant to remove the Windows partition. The first clue that something was now amiss was that I decided to reboot the laptop after reclaiming the Windows partition, and when I did so I encountered a black screen with a decidedly "microsoft pre-start up" text message on my screen, something like "press any key to start up from the removable media drive", then "press any key to start up", neither of which would work (even with a bootable disk in the optical drive).
    So, I rebooted holding down the option key and was able to start up Mac OS X 10.5.2. Only one volume was shown now in "About this Mac" and on my desktop, so I ran Boot Camp Assistant again to re-create a Boot Camp partition. UNFORTUNATELY, in the midst of this, I encountered my first ever kernal panic ("windowshade" effect descending down the screen and multiple-language dialog telling me I needed to reboot).
    I rebooted and ran Disk Utility, which told me my partition map was wrong and that I was missing about the amount of disk space I'd allocated to Windows in my previous Boot Camp partition. I thought at THAT point I'd solved my problem - I could just run disk utility from my Leopard startup disk. HOWEVER, the Leopard installation disk will no longer reboot the laptop!
    I confirmed that the problem is not the Leopard installation DVD, because it will boot my Mac Pro and it mounts on the desktop and Disk Utility says it's fine.
    So, I tried to repair my laptop's drive using DiskWarrior 4. That worked (at least it made a new directory, and after it did so, when I boot into the Mac OS, Disk Utility run from the hard drive also says the disk is fine). HOWEVER, the Leopard DVD still won't boot the MacBook Pro. I made one more attempt to create a Windows partition using Boot Camp assistant, and once again generated a kernal panic in the midst of partitioning.
    It seems that I've done something to the stuff on the hard drive that's needed at boot time or partitioning time. I can't erase and reformat the drive, because the Leopard install DVD won't start up the machine. Even though DiskWarrior creates a directory that Disk Utility says is fine, I cannot recreate a Windows partition.
    Any advice what I can or should do next? I can try using the System Install DVD that came with the laptop, or perhaps the system restore DVD, but my bet is they won't start the machine either.
    Please feel free to ask any questions, send me to any other resources, or contact me via email if you have ideas. I have a 10 day business trip beginning Sunday March 30, and I desperately need a working laptop by then.
    Thanks so much.

    "Responding" to my own post: the Install DVD that came with my MacBook Pro will boot it!
    So, I'll try running the earlier version of Disk Utility that came on IT (10.5.4, current Leopard version is 11.0) to repair the MacBook Pro's internal hard drive, THEN see if I can boot from the Leopard install disk (the notion being that I can (groan) recreate a virgin Leopard environment on the laptop with no traces of prior disk formatting nightmares.
    (a few minutes later): the Leopard Installer DVD will now boot the MacBook Pro. As one last attempt to avoid the whole reinstall nightmare, I'll try running Disk Utility from the Leopard Install DVD, and if it passes, make one more attempt to create a boot camp partition on my hard drive. If that doesn't work, next step is to wipe the internal drive and do a clean install of Leopard and all my other necessary stuff.
    Any other ideas?

  • Password problem booting from external hard drive

    I have an eMac and just installed Leopard. BUT now I can't use Photoshop and Quark from within Classic because it's not available with Leopard. I've installed my old 10.3 OS on my external hard drive, and when I boot up from that (using the Option key), after I choose the hard drive as the startup disc, I am asked for my admin password. When I type that in, the dialog box jiggles from side to side for a moment and blanks out the password, asking for it again.
    How can I boot up 10.3 from the external hard drive? Help -- I need to use the Classic environment for a job! Thanks for any help --

    Hi, Jeff --
    Well, I think my problem is finally solved, thanks (partly) to your help. Just to help other folks who have this problem, I'm going to state briefly how I fixed it:
    -- I did an Erase and Install on the Seagate AFTER spending all day burning 30 CDs with the archived files I'd taken off the Mac but didn't want to lose.
    -- After that, I could indeed boot up the Mac from the Seagate in 10.3 and all seemed fine.
    -- But I made the mistake of doing a full backup to the Seagate from the Mac (which took two hours).
    -- After that, I couldn't boot up the Seagate at all -- I spent two 20-minute periods waiting for it to get off the gray screen with the Apple log, to no avail. A friend of mine suggested that the backup program might be the problem.
    -- After some trepidation but knowing that I already had everything I needed on those 30 CDs, I decided to experiment and partition the Seagate (via Disc Utility) into one partition with only the 10.3 install on it and the other with whatever files I needed, including the applications I needed to open in 10.3.
    -- That worked!! I can now boot up the Seagate "10.3 drive" and access all the files and applications I need from the Seagate "Backup Drive."
    I hope this information helps someone else in the same predicament.
    Thanks for all your help and patience; your suggestion to do an Erase and Install was the right move to get me started.
    Eileen

  • [SOLVED] Problem with "su" and "login".

    Hi, I reinstalled Arch Linux today when I updated "filesystem" and reboot appeared an error with root device, but I solved with installation CD.
    I restarted laptop after solving error with root device when I went to XFCE4 and open a terminal I tried to login as root with "su" and "su -" but showed this error:
    bash: su: command not found
    So I rebooted to start in text mode.
    When loaded SLIM I press ctrl+alt+F1 to enter text mode.
    I type root to login but did'nt appear to enter the pass, appeared again to enter login. I tried type my user but did the same.
    Someone can help me?
    Thanks!
    Last edited by surrealistic (2012-10-12 08:54:58)

    Thank you falconindy. I upgrade with --force because I search in Google the problem show "filesystem" when I tried install and I read that solution is upgrade "filesystem" with --foce.
    I tried to reinstall util-linux and now works. Thank you!

  • Problem booting Lion after restoring disk from Time Machine

    I have a late 2009 iMac which I have upgraded to Lion, having created a bootcamp partition with Windows Server 2008 before upgrading.
    This has been working absolutely fine for a few months but then there appeared to be some kind of hard disk problem and booting would only go as far as a gray screen with apple logo and a progress bar, then shut itself down. I started into the recovery partition by holding down the Alt key and from there (after reading around the internet a bit) was able to reformat the OS X partition and restore it from my Time Machine backup (wireless to Time Capsule).
    However it now won't boot, initial grey screen with Apple logo and spinning progress meter then restarts into Recovery HD. In Recovery mode Disk Utility reports all appears to be OK with the disk - there were some errors before I restored from Time Machine, but Disk Utility was able to repair them.
    If I hold down Alt on booting I get the 'choice of boot disks' screen with EFi boot, Windows and Recovery HD. If I choose EFi boot I get the Apple symbol alternating with a circle with diagonal line (prohibitory?) a couple of times, then it boots into Recovery. If I boot the computer with the Shift key it successfully boots into Windows, but won't boot into Windows from the 'choice of boot disks' screen.
    Is my problem that I need to somehow 'make' the restored partition bootable and if so how, or is there a more fundamental problem here, either with my hard disk or (gulp) with my Time Machine backup?
    Any ideas much appreciated, thanks
    -Chris

    Can't see SMART status anywhere in Disk Utility, shouldn't it just be visible at the bottom of the window when I click on the disk? Verify disk returns OK. I do have the correct format option.
    I am now trying Tony T1's suggestion of trying again, but this time on Erase... I have chosen the Security Option that writes 0's over the whole partition to see if it throws up any signs of failure.
    Thanks for your suggestions.

Maybe you are looking for

  • HT5085 Can I remove applications from the Cloud that I now longer want to be associated with my Apple ID?

    I have applications that have been downloaded on my iPad and iPhone via my Apple ID, but I no longer want them associated with my account. Is there a way to permentanly delete them? If so, how? I have already deleted them from the devices. Most of th

  • New Display old comuter.

    I have a G3 B&W 400 and a Apple G4 ATI Rage6 32Mb VGA/ADC Video Card AGP 630-3600 I'm installing a Apple 15" Studio Display Flat Panel LCD Monitor M2454. I put the new card in the vid slot pluged in the new display and started up the computer. The di

  • Inline select statement and SQL optimizatino

    Hi everyone, I am trying to optimze a script but can't get the fulle explainplan in PL/SQL. The problem is that the select statements in de column defenition is not explained. below are the 2 scripts I want to compare: SQL1: Select z.title , (select

  • Scstat:  unexpected error , sc 3.2

    Hello, Looks like cluster nodes are completely messed up. I had configured mysql resource as failover group using smf.proxy.failover and it looked okay so I 'init 6' one node, other node somehow hung and when both were reset, both have problems . -ba

  • Passing values to Javascripts/ write to text file

    Hi, I m new to InDesign Programming. I m using InDesign CS3 on MAC OS... Is it possible to pass values to a javascript through plugin code? I have a dialog with textboxes in it, On clicking ok button a script is called which uses these text box value