[SOLVED] Chromebook: help partitioning /dev/sda7 to install GRUB

My goal is to dual boot Arch and Chrome OS on an Acer C720. I repartitioned the drive using the Chrubuntu script. Following the Wiki, I created the file system for Arch on /dev/sda7.
The next step in the Wiki reads
Following the instructions for installing GRUB on GPT, use gdisk to create a 1007kb partition and set the type to EF02.
I don't understand what to do. Do I really make another partition on sda? I've read that if you change the partitioning, it will not boot into Chrome OS.
Can someone please help me understand how to create the 1007kb partition for GRUB? Thanks!!
Last edited by Watney (2015-05-10 00:32:05)

There aren't details of what you've done, think of what we can comment here.
What says
# parted -l /dev/sdX ### could be /dev/sda
Or even better what's your actual partitioning  scheme and how the partitions are laid out.
The note is clear (for me) and the link in it will show more details. The real point is to have the Post-MBR gap where GRUB will use to write its files.
If you don't have that  Post-MBR gap then you need to shrink the first partition from the beginning to leave that Mb gap.

Similar Messages

  • [SOLVED] Dual boot with ubuntu w/o installing GRUB? (YES)

    Hi all -
    This is my first shot at arch, tho I've installed a few other linux distros.
    So far I really appreciate the excellent documentation, especially compared to other linuxes!
    But I can't find a good answer to this question:
    I already have ubuntu installed and would like to dual-boot with arch.  (I also have Win7 but boot it from a separate disk selected via BIOS, and usually leave this disk disconnected anyway, so it's not an issue; grub doesn't know it exists).
    Q:  Before installing, can I make a new LOGICAL ext4 partition (say /dev/sda7),
    - then install arch on that **w/o installing grub** and **without messing with the MBR**,
    - then edit ubuntu's existing menu.lst to add arch to the boot options?
    Current $ fdisk -l
    /dev/sda1    ext4 primary/boot (/ for ubuntu)
    /dev/sda2    extended
    --/dev/sda6  linux-swap
    --/dev/sda5  NTFS (data - mp3s, etc)
    unallocated  480GB  --> Create new ext4 partition /dev/sda7,  (logical or primary? Prefer logical)
    Current menu.lst entry that I normally boot:
    title       Ubuntu 12.04 LTS, kernel 3.2.0-24-generic REGULAR
    uuid        UUIDforSDA1 (file has actual UUID number...)
    kernel      /boot/vmlinuz-3.2.0-24-generic root=UUID=UUIDforSDA1 ro
    initrd      /boot/initrd.img-3.2.0-24-generic
    and add something like this to menu.lst:
    title  Arch Linux
    uuid  UUIDforSDA7
    kernel /boot/vmlinuz-linux root=/dev/sda7/ARCH ro  (??? - from example in arch docs)
    initrd /boot/initramfs-linux.img
    or
    kernel /boot/vmlinuz-linux root=UUID=UUIDforSDA7 ro  (??? - like the ubuntu entry)
    I'd really like to NOT mess up booting ubuntu!  (Another option might be install arch to a separate disk with the ubuntu disk disconnected, then copy the whole install over via a USB adapter...I've done worse!)
    TIA for any help!
    Edit: so I guess there's three questions:
    1 - Can I install arch w/o installing grub & MBR messing-wth?
    2 - What's the correct syntax for menu.lst to access and boot arch?
    3 - Will this work?
    Last edited by Flemur (2012-05-25 15:24:18)

    Well, it worked and booted up first time - no grub install.
    The main hassle was merely creating a new ext4 partitions because "Partition Wizard" boot CD screwed up and I kept getting "Unable to update kernel until reboot" messages until I deleted and rebuilt all the partitions in the extended partition with puppy linux & gparted instead of Partition Wizard.
    In case others stumble upon this trhread, here's some info:
    The entry in the ubuntu (original) menu.lst was this:
       title           Arch Linux
       uuid          af7...etc...9f3c
       kernel        /boot/vmlinuz-linux root=UUID=af7...etc.f3c ro
       initrd          /boot/initramfs-linux.img
    I'm even posting this from arch/fluxbox/Firefox, although getting X set up with nvidia (PITA!) apparently required using a different pacman source:
    File "mirrorlist" now points to
        Server = http://mirror.us.leaseweb.net/archlinux/$repo/os/$arch
    which wasn't in the original file.
    Then
    $ pacman -Su --> "/etc/mtab exists" --> delete it and something else broke,
    so
    $ pacman -Su --force --> worked fine (against official advice)
    Also: needed to install nvidia-utils and xorg-xinit
    Thanks again!

  • Solved Acer v3 571G laptop dual boot windows 8.1 help partitioning

    I have made a usb installation drive and have got as far as the root prompt on installation after having the uefi issue with loader and using the hashtool successfully on the wiki page.  However I did not go any further because I had not the partitioning done.  And I am stuck.  My system has a 500gb disk running windows 8.1.  The partition is like the following
    /dev/sda1     ntfs     Recovery    400mb
    /dev/sda2     fat32     ESP         300mb
    /dev/sda3   unknown    microsoft reserved partition   128mb
    /dev/sda4    ntfs    Acer    222.82    47 used
    /dev/sda5    ntfs    --------    450mb     hidden diag
    /dev/sda6    ntfs    Data    222.16mb    mfsdata
    unallocated              1.00mb
    /dev/sda7    ntfs     Push Button Reset     19.53gb     hidden diag
    I can boot gparted from a cdrom.  Where would I install archlinux and how do I format the partition.  I suppose I will be using uefi and formatting a partition accordinlgy.
    Last edited by leonax (2014-11-15 17:10:58)

    I resubmitted this question in the Installation thread and got an answer there.

  • Help urgently needed, I have installed Logic Pro 9, since then my Final Cut Pro X keep freezing. Anyone what is wrong and how to solve it? I desperately need help on this. Thanks

    Help urgently needed, I have installed Logic Pro 9, since then my Final Cut Pro X keep freezing. Anyone what is wrong and how to solve it? I desperately need help on this. Apple support says I have to pay £85 for to help me. Thanks

    Just a word of advice. Never ever use the word "urgent" on this forum

  • Error "Building boot caches on boot helper partition failed" when installing Yosemite

    I Have a MacBook Pro 8,3 17" and have been running OSX Maverick 10.9.5 quite happily.  I finally decided to bite the bullet and update to OSX 10.10.1.  I went through the App Store and clicked install on the Yosemite offered there.
    THe install took about 55 mins and then right at the end it reported: Building boot caches on boot helper partition failed, install failed.
    now i can't boot normally or restore from my time machine backup.
    can anybody suggest a fix?

    Install OS X Using Internet Recovery
    Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
    Boot to the Internet Recovery HD:
    Restart the computer and after the chime press and hold down the COMMAND-OPTION- R keys until a globe appears on the screen. Wait patiently - 15-20 minutes - until the Recovery main menu appears.
    Partition and Format the hard drive:
    Select Disk Utility from the main menu and click on the Continue button.
    After DU loads select your newly installed hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
    Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed. Quit DU and return to the main menu.
    Reinstall OS X: Select Reinstall OS X and click on the Install button. Be sure to select the correct drive to use if you have more than one.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
    This should restore the version of OS X originally pre-installed on the computer.

  • [SOLVED] Need help with rEFInd boot entry for rsync backup

    I made a successful backup my arch install to an other internal SSD disk (from my HDD).
    But now I can't figure out how to make a boot entry for this drive. The wiki only mentions GRUB, which I do not use.
    This is the fstab for my HDD:
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sda5
    UUID=c1822e3c-e037-4445-bdd8-b71778237dee / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda2 LABEL=SYSTEM_DRV
    UUID=D2DF-9F74 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    And this is the fstab on my SSD which I edited:
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sdb1
    UUID=c61a1301-4728-465d-b40b-bde5e084eb50 / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda2 LABEL=SYSTEM_DRV
    UUID=D2DF-9F74 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    But I'm not sure about the /boot entry, do I need something else here?
    Afterward I tried updating rEFInd by reinstalling using refind-install, but that did not work.
    ps. I dual boot with Windows.
    Last edited by Devenda (2014-08-18 07:58:07)

    I also tried adding the menu entry manually by editing refind.conf but that didn't work. I got:
    Invalid loader file!
    Error: Not Found while loading vmlinuz-linux
    Here is some additional info:
    refind.conf:
    menuentry "SSD Arch Linux" {
    icon /EFI/refind/icons/os_arch.png
    volume "ArchSSD"
    loader /boot/vmlinuz-linux
    initrd /boot/initramfs-linux.img
    options "root=/dev/sdb1 ro"
    I hope this helps.
    blkid
    /dev/sda1: LABEL="WINRE_DRV" UUID="7C2ADD1D2ADCD4EC" TYPE="ntfs" PARTUUID="b7137819-2ca6-40fb-9167-b73ac37d8d96"
    /dev/sda2: LABEL="SYSTEM_DRV" UUID="D2DF-9F74" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="9c77b526-730f-42f9-9904-f9a31b205687"
    /dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="f4d5275b-24c1-4847-b937-345bc23bec89"
    /dev/sda4: LABEL="Windows 8" UUID="38D6E449D6E408C8" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="d777a359-f42c-4629-a07c-cc55316352fe"
    /dev/sda5: UUID="c1822e3c-e037-4445-bdd8-b71778237dee" TYPE="ext4" PARTUUID="3d282004-2515-4630-b82e-35ed7f707b89"
    /dev/sda6: UUID="F80680CC06808D76" TYPE="ntfs" PARTUUID="575bc623-c7f1-44da-a79e-220ce3c98d9b"
    /dev/sda7: LABEL="Lenovo_Recovery" UUID="0898D76B98D75632" TYPE="ntfs" PARTUUID="99bfc6d6-1b71-46d1-887e-2f7e65e3eab1"
    /dev/sdb1: LABEL="ArchSSD" UUID="c61a1301-4728-465d-b40b-bde5e084eb50" TYPE="ext4" PARTUUID="e87704a5-01"
    lsblk -f
    NAME FSTYPE LABEL UUID MOUNTPOINT
    sda
    ├─sda1 ntfs WINRE_DRV 7C2ADD1D2ADCD4EC
    ├─sda2 vfat SYSTEM_DRV D2DF-9F74 /boot
    ├─sda3
    ├─sda4 ntfs Windows 8 38D6E449D6E408C8
    ├─sda5 ext4 c1822e3c-e037-4445-bdd8-b71778237dee /
    ├─sda6 ntfs F80680CC06808D76
    └─sda7 ntfs Lenovo_Recovery 0898D76B98D75632
    sdb
    └─sdb1 ext4 ArchSSD c61a1301-4728-465d-b40b-bde5e084eb50
    sr0
    boot tree
    /boot
    ├── BOOT
    │   └── boot.sdi
    ├── BOOTSECT.BAK
    ├── EFI
    │   ├── Boot
    │   │   ├── bootx64.efi
    │   │   ├── LenovoBT.EFI
    │   │   ├── License.txt
    │   │   └── ReadMe.txt
    │   ├── gummiboot
    │   │   └── gummibootx64.efi
    │   ├── Lenovo
    │   │   └── Boot
    │   │   ├── BCD
    │   │   ├── BCD.LOG
    │   │   ├── BCD.LOG1
    │   │   ├── BCD.LOG2
    │   │   ├── bg-BG
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── bootmgfw.efi
    │   │   ├── bootmgr.efi
    │   │   ├── BOOTSTAT.DAT
    │   │   ├── boot.stl
    │   │   ├── cs-CZ
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── da-DK
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── de-DE
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── el-GR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── en-GB
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── en-US
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── es-ES
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── et-EE
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── fi-FI
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── Fonts
    │   │   │   ├── chs_boot.ttf
    │   │   │   ├── cht_boot.ttf
    │   │   │   ├── jpn_boot.ttf
    │   │   │   ├── kor_boot.ttf
    │   │   │   ├── malgun_boot.ttf
    │   │   │   ├── malgunn_boot.ttf
    │   │   │   ├── meiryo_boot.ttf
    │   │   │   ├── meiryon_boot.ttf
    │   │   │   ├── msjh_boot.ttf
    │   │   │   ├── msjhn_boot.ttf
    │   │   │   ├── msyh_boot.ttf
    │   │   │   ├── msyhn_boot.ttf
    │   │   │   ├── segmono_boot.ttf
    │   │   │   ├── segoen_slboot.ttf
    │   │   │   ├── segoe_slboot.ttf
    │   │   │   └── wgl4_boot.ttf
    │   │   ├── fr-FR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── hr-HR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── hu-HU
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── it-IT
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── ja-JP
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── ko-KR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── lt-LT
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── lv-LV
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── memtest.efi
    │   │   ├── nb-NO
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── nl-NL
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── pl-PL
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── pt-BR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── pt-PT
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── qps-ploc
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── Resources
    │   │   │   ├── bootres.dll
    │   │   │   └── en-US
    │   │   │   └── bootres.dll.mui
    │   │   ├── ro-RO
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── ru-RU
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── sk-SK
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sl-SI
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sr-Latn-CS
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sv-SE
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── tr-TR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── uk-UA
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── zh-CN
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── zh-HK
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   └── zh-TW
    │   │   ├── bootmgfw.efi.mui
    │   │   ├── bootmgr.efi.mui
    │   │   └── memtest.efi.mui
    │   ├── Microsoft
    │   │   └── Boot
    │   │   ├── BCD
    │   │   ├── BCD.LOG
    │   │   ├── BCD.LOG1
    │   │   ├── BCD.LOG2
    │   │   ├── bg-BG
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── bootmgfw.efi
    │   │   ├── bootmgr.efi
    │   │   ├── BOOTSTAT.DAT
    │   │   ├── boot.stl
    │   │   ├── cs-CZ
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── da-DK
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── de-DE
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── el-GR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── en-GB
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── en-US
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── es-ES
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── et-EE
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── fi-FI
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── Fonts
    │   │   │   ├── chs_boot.ttf
    │   │   │   ├── cht_boot.ttf
    │   │   │   ├── jpn_boot.ttf
    │   │   │   ├── kor_boot.ttf
    │   │   │   ├── malgun_boot.ttf
    │   │   │   ├── malgunn_boot.ttf
    │   │   │   ├── meiryo_boot.ttf
    │   │   │   ├── meiryon_boot.ttf
    │   │   │   ├── msjh_boot.ttf
    │   │   │   ├── msjhn_boot.ttf
    │   │   │   ├── msyh_boot.ttf
    │   │   │   ├── msyhn_boot.ttf
    │   │   │   ├── segmono_boot.ttf
    │   │   │   ├── segoen_slboot.ttf
    │   │   │   ├── segoe_slboot.ttf
    │   │   │   └── wgl4_boot.ttf
    │   │   ├── fr-FR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── hr-HR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── hu-HU
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── it-IT
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── ja-JP
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── ko-KR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── lt-LT
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── lv-LV
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── memtest.efi
    │   │   ├── nb-NO
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── nl-NL
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── pl-PL
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── pt-BR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── pt-PT
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── qps-ploc
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── Resources
    │   │   │   ├── bootres.dll
    │   │   │   ├── en-US
    │   │   │   │   └── bootres.dll.mui
    │   │   │   └── nl-NL
    │   │   │   └── bootres.dll.mui
    │   │   ├── ro-RO
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── ru-RU
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── sk-SK
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sl-SI
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sr-Latn-CS
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sr-Latn-RS
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sv-SE
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── tr-TR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── uk-UA
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── zh-CN
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── zh-HK
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   └── zh-TW
    │   │   ├── bootmgfw.efi.mui
    │   │   ├── bootmgr.efi.mui
    │   │   └── memtest.efi.mui
    │   ├── refind
    │   │   ├── icons
    │   │   │   ├── arrow_left.png
    │   │   │   ├── arrow_right.png
    │   │   │   ├── boot_linux.png
    │   │   │   ├── boot_win.png
    │   │   │   ├── func_about.png
    │   │   │   ├── func_exit.png
    │   │   │   ├── func_firmware.png
    │   │   │   ├── func_reset.png
    │   │   │   ├── func_shutdown.png
    │   │   │   ├── os_altlinux.png
    │   │   │   ├── os_arch.png
    │   │   │   ├── os_centos.png
    │   │   │   ├── os_chrome.png
    │   │   │   ├── os_clover.png
    │   │   │   ├── os_debian.png
    │   │   │   ├── os_ecomstation.png
    │   │   │   ├── os_fatdog.png
    │   │   │   ├── os_fedora.png
    │   │   │   ├── os_freebsd.png
    │   │   │   ├── os_freedos.png
    │   │   │   ├── os_funtoo.png
    │   │   │   ├── os_gentoo.png
    │   │   │   ├── os_gummiboot.png
    │   │   │   ├── os_haiku.png
    │   │   │   ├── os_hwtest.png
    │   │   │   ├── os_kubuntu.png
    │   │   │   ├── os_legacy.png
    │   │   │   ├── os_linuxmint.png
    │   │   │   ├── os_linux.png
    │   │   │   ├── os_lubuntu.png
    │   │   │   ├── os_mac.png
    │   │   │   ├── os_mageia.png
    │   │   │   ├── os_mandriva.png
    │   │   │   ├── os_manjaro.png
    │   │   │   ├── os_mythbuntu.png
    │   │   │   ├── os_netbsd.png
    │   │   │   ├── os_openbsd.png
    │   │   │   ├── os_opensuse.png
    │   │   │   ├── os_redhat.png
    │   │   │   ├── os_refind.png
    │   │   │   ├── os_refit.png
    │   │   │   ├── os_slackware.png
    │   │   │   ├── os_suse.png
    │   │   │   ├── os_ubuntu.png
    │   │   │   ├── os_unknown.png
    │   │   │   ├── os_win.png
    │   │   │   ├── tool_apple_rescue.png
    │   │   │   ├── tool_memtest.png
    │   │   │   ├── tool_mok_tool.png
    │   │   │   ├── tool_part.png
    │   │   │   ├── tool_shell.png
    │   │   │   ├── tool_windows_rescue.png
    │   │   │   ├── transparent.png
    │   │   │   ├── vol_external.png
    │   │   │   ├── vol_internal.png
    │   │   │   └── vol_optical.png
    │   │   ├── icons-backup
    │   │   │   ├── arrow_left.png
    │   │   │   ├── arrow_right.png
    │   │   │   ├── boot_linux.png
    │   │   │   ├── boot_win.png
    │   │   │   ├── func_about.png
    │   │   │   ├── func_exit.png
    │   │   │   ├── func_firmware.png
    │   │   │   ├── func_reset.png
    │   │   │   ├── func_shutdown.png
    │   │   │   ├── os_altlinux.png
    │   │   │   ├── os_arch.png
    │   │   │   ├── os_centos.png
    │   │   │   ├── os_chrome.png
    │   │   │   ├── os_clover.png
    │   │   │   ├── os_debian.png
    │   │   │   ├── os_ecomstation.png
    │   │   │   ├── os_fatdog.png
    │   │   │   ├── os_fedora.png
    │   │   │   ├── os_freebsd.png
    │   │   │   ├── os_freedos.png
    │   │   │   ├── os_funtoo.png
    │   │   │   ├── os_gentoo.png
    │   │   │   ├── os_gummiboot.png
    │   │   │   ├── os_haiku.png
    │   │   │   ├── os_hwtest.png
    │   │   │   ├── os_kubuntu.png
    │   │   │   ├── os_legacy.png
    │   │   │   ├── os_linuxmint.png
    │   │   │   ├── os_linux.png
    │   │   │   ├── os_lubuntu.png
    │   │   │   ├── os_mac.png
    │   │   │   ├── os_mageia.png
    │   │   │   ├── os_mandriva.png
    │   │   │   ├── os_manjaro.png
    │   │   │   ├── os_mythbuntu.png
    │   │   │   ├── os_netbsd.png
    │   │   │   ├── os_openbsd.png
    │   │   │   ├── os_opensuse.png
    │   │   │   ├── os_redhat.png
    │   │   │   ├── os_refind.png
    │   │   │   ├── os_refit.png
    │   │   │   ├── os_slackware.png
    │   │   │   ├── os_suse.png
    │   │   │   ├── os_ubuntu.png
    │   │   │   ├── os_unknown.png
    │   │   │   ├── os_win.png
    │   │   │   ├── tool_apple_rescue.png
    │   │   │   ├── tool_memtest.png
    │   │   │   ├── tool_mok_tool.png
    │   │   │   ├── tool_part.png
    │   │   │   ├── tool_shell.png
    │   │   │   ├── tool_windows_rescue.png
    │   │   │   ├── transparent.png
    │   │   │   ├── vol_external.png
    │   │   │   ├── vol_internal.png
    │   │   │   └── vol_optical.png
    │   │   ├── keys
    │   │   │   ├── altlinux.cer
    │   │   │   ├── canonical-uefi-ca.der
    │   │   │   ├── fedora-ca.cer
    │   │   │   ├── openSUSE-UEFI-CA-Certificate.cer
    │   │   │   ├── refind.cer
    │   │   │   └── SLES-UEFI-CA-Certificate.cer
    │   │   ├── refind.conf
    │   │   ├── refind.conf.old
    │   │   ├── refind.conf-sample
    │   │   └── refind_x64.efi
    │   └── tools
    ├── grub
    │   ├── grub.cfg
    │   └── grub.cfg.example
    ├── initramfs-linux-fallback.img
    ├── initramfs-linux.img
    ├── loader
    │   ├── entries
    │   │   └── arch.conf
    │   └── loader.conf
    ├── refind_linux.conf
    └── vmlinuz-linux
    refind_linux.conf
    "Boot with standard options" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee quiet "
    "Boot to single-user mode" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee quiet single"
    "Boot with minimal options" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee"

  • [solved] Unlocking luks partitions fails at boot, no prompt.

    Hello,
    I have just installed Arch and I really like it so far - I'm a convert from Ubuntu. I did face a couple of problems that I have not been able to solve and have not been able to find any solutions for anywhere. The most important one at the moment is that with my two encrypted partitions.
    Here's my fstab:
    # /etc/fstab: static file system information
    # <file system>        <dir>         <type>    <options>          <dump> <pass>
    none                   /dev/pts      devpts    defaults            0      0
    none                   /dev/shm      tmpfs     defaults            0      0
    #/dev/cdrom             /media/cd   auto    ro,user,noauto,unhide   0      0
    #/dev/dvd               /media/dvd  auto    ro,user,noauto,unhide   0      0
    #/dev/fd0               /media/fl   auto    user,noauto             0      0
    /dev/scd0 /media/dvd   udf,iso9660 user,noauto,exec,utf8 0 0
    /dev/sda3 / ext3 defaults 0 1
    /dev/sdb1 swap swap defaults 0 0
    /dev/sdb2 /home reiserfs user,owner,auto 0 0
    /dev/sda6 /home/nerd/E   reiserfs defaults 0 0
    /dev/mapper/croot /home/nerd/F ext3 defaults 0 0
    /dev/mapper/crypt /home/nerd/D ext3 defaults 0 0
    and here's my crypttab:
    crypt /dev/sda5 none
    croot /dev/sda7 none
    I have cryptsetup installed, enabled the dm-crypt and aes-i586 kernel modules, and even edited mkinitcpio and added the encrypt hook. At boot, my computer does see both of the drives, but it just doesn't prompt for passwords, what it prints out is:
    Password:!unlocking encrypted volume crypt
    command failed: No key available with this passphrase.
    I am able to mount the drives manually using cryptsetup, and the data is there. Is there any way for me to fix that? Thanks!
    Last edited by DavidR (2009-09-19 10:32:57)

    afaik, you should have 'ASK' instead of 'none' in crypttab
    edit: argh. too late again
    Last edited by bender02 (2009-09-18 19:35:37)

  • [SOLVED] Dualboot w7 + Arch ( where to install grub )

    Hello,
    I have win 7 already installed,
    now i want to install Archlinux on same disk, but on other partitions.
    My currently partiotion schema ( MBR ) looks like:
    /dev/sda1 win7
    /dev/sda2 reserverd for linux boot part
    /dev/sda3 reserverd for linux root
    I readed beginners guide, and the only one thing is not clear for me,
    beginners guide advises not to install grub on any partiorion only on disk's mbr /dev/sda
    I can not do that, because it will destroy my win7's mbr( partion table and so on )
    Earlier with this configuration i had sabayon linux installed,
    with grub on /dev/sda2, both systems booted with bcdedit and all worked fine.
    How can I solve this ( grub2 can not be installed in /dev/sdaX )
    Thanks for any help.
    Last edited by tangram (2013-11-18 09:55:29)

    tangram wrote:
    henk wrote:... Why do you personally think grub will update to /dev/sda? Do you know how grub works that well? ...
    I do not know, I felt it so, earlier linux experiences, maybe better I should write "I suppose".
    It is not a question of knowing grub. It is a question of knowing Arch. When pacman updates grub, it does not reinstall to disk, it does not generate a new configuration file and it does not, therefore, touch either the MBR or the BIOS boot partition or any installation to a partition or anything else. The most pacman will do is remind you to do these things, as necessary. And sometimes it does not even do that.
    This is why, for example, it is possible to maintain grub.cfg manually in Arch but not in most other distros. Because the system will never, ever run grub-mkconfig unless you tell it to. So a manually maintained configuration file will never be overwritten unless you overwrite it.
    The only boot manager/loader I know of where this is not the case is gummiboot and IMNSHO, that makes the gummiboot package a badly behaved one which fails to properly respect the local customs. (And I won't install gummiboot for essentially this reason.)
    That said, installing grub to a partition is not recommended because it is very easily broken. So I don't think you should do that. I'm just saying that if you did do it, no pacman upgrade would ever write to the MBR. Nor, for that matter, would it update the installation on the partition. It would do zilch to upgrade the actual installation of the boot loader - it would just update the package files in your system.
    Last edited by cfr (2013-11-03 03:15:34)

  • Recovery HD partition disappears when I install Mavericks. File Vault 2 can't be turned on.

    Hi folks,
    I've run into this issue and repeated internet searches don't turn up anyone else having the same problem.
    Until a couple of days ago, I've had the most recent version of Mountain Lion installed with File Vault 2 turned on. Everything has been fine.
    I did a clean install of Mavericks, and everything went fine with the install. During the post-install set up, I get a window saying that I used to have FV2 turned on, and that to do so again requires me turning it on in System Preferences. So I try to do that, but then I get a message saying that "some disk formats do not support the recovery partion that needs to be created...".
    So I look (using both diskutil list and enabling the debug menu in Disk Utility) and see that the Recovery HD is gone. I don't know how to recreate it and don't understand the command line partitioning well enough to try it, so I try again with Mavericks, doing it the long way:
    I do a clean install of Lion.
    Boot up into Lion, and verify that the Recovery HD partition was created. It was.
    Boot up from the Mavericks bootable USB I made, erase just the main partition I intend to install Mavericks on (again, I see Recovery HD exists).
    Install Mavericks.
    Boot up from the internal HD Mavericks, get the same note about turning on FV2 manually, and try to do so.
    It fails again. I use diskutil and Disk Utility with the debug menu, and sure enough Recovery HD is gone and I cannot turn on FV2.
    Does anyone know what I'm doing wrong? I feel like this would be a more widely discussed issue if this were a pure Mavericks issue. But Apple is not giving us a lot of support for doing clean installs (all instructions I find are on tech nerd blogs), so I'm lost about where to begin.
    Thanks for your help.
    It is Thu Oct 24 08:32:28 MDT 2013.
    < Thu 8:32am ~ > diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *500.1 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:                  Apple_HFS Tesla                   499.2 GB   disk0s2

    FWIW, I did a clean install of Mavericks with a bootable USB drive, which I created following the instructions in this link:
    http://www.gottabemobile.com/2013/10/22/perform-clean-install-os-x-mavericks/
    The short method did not work. I succeeded with the longer method.
    Mavericks installed without a hitch, after which I spent hours customizing settings, clean installing applications and restoring data from my prior Mountain Lion backup. No problems at all, just very time consuming.
    However, I could not activate "Find my Mac" because the installer had not created a a Recovery HD. I trawled the forums and was discouraged by the apparent complexity of creating one.
    This is what I did, which worked perfectly and required very little attention. It is almost automatic, fail proof and done in under an hour (with a fast internet connection to download Mavericks at just over 5GB).
    1.- Back up the system. Better still, clone your system to an external HD using Carbon Copy Cloner.
    2.- Download Mavericks from the App Store.
    3.- It will warn you that you already have 10.9 installed. Download anyway.
    4.- When it finishes downloading you'll get a window prompting you to install. Confirm.
    5.- Enter your user password when prompted.
    6.- Go for a walk. In about 45 min your system will have restarted Mavericks and all your settings, applications and data will be there.
    7.- Check that you now have a Recovery HD by restarting the system, holding the Option key down when you hear the startup gong. You'll (hopefully) see the system HD and the Recovery HD (10.9).
    Hope this will help someone.

  • Problems with partitioning and install Grub. Fresh install

    All,
    First post here. I appreciate any help you can offer.
    I am having some problems when installing Arch Linux.
    I am installing Arch on a brand new (3 days old) Toshiba SatelliteC655D-S5300 Laptop.
    Hot sheet can be found at http://cdgenp01.csd.toshiba.com/content … -S5300.pdf.
    I was initially installing from 2011.08.19 x86_64 Core CD but someone suggested using the latest version.
    Now I am installing from 2011.11.13 x86_64 CD burned at 4x (the slowest my burner can go).
    I am able to complete all steps up to installing GRUB, but it fails to install.
    During partitioning I receive a few errors and I believe this is contributing to the issue.
    At first I tried automatic partitioning with 100mb boot, 1024mb swap, 10,000mb / and the rest of 320g for /home. Each partition is ext3 except /boot which is ext2.
    During the automatic partitioning an error briefly occured: /usr/lib/aif/core/libs/lib-blockdevices-filesystems.sh: line 355: !((partition_flag)): command not found.
    After speaking with a friend they suggested manually partitioning and using UUIDs instead.
    1) So far I have removed all partitions, rebooted.
    2) Partitioned using cFdisk. Bootable 100mb parition, 1024mb swap, 15,000mb primary (/), 3000mb logical (/var), and the rest 300949mb logical (/home).
    3) Once I write the changes and quit I reboot.
    4)I go back into the installer and complete steps 1-3.
    5) Go to step 4 and and then manually configure block devices, file systems, or mount points.
    6) I choose the option for uuid and hit ok.
    At this point 3 error messages appear at the bottom:
    /usr/lib/aif/core/libs/lib-ui-interactive.sh: line 602: local: 'part,' : not a valid identifier
    /usr/lib/aif/core/libs/lib-ui-interactive.sh: line 602: local: 'type,' : not a valid identifier
    /usr/lib/aif/core/libs/lib-ui-interactive.sh: line 602: local: 'label,' : not a valid identifier
    (Screenshot: http://i.imgur.com/OHRKo.jpg)
    7) Next it prompts me to add the mount points for each partition set.
    8) Select the partition, the mount point, it asks me for label and any additional opts for mkfs.ext3.
    9) I leave the label and opts field blank. After selecting ok to the opts field I get the same 3 errors as above:
    /usr/lib/aif/core/libs/lib-ui-interactive.sh: line 602: local: 'part,' : not a valid identifier
    /usr/lib/aif/core/libs/lib-ui-interactive.sh: line 602: local: 'type,' : not a valid identifier
    /usr/lib/aif/core/libs/lib-ui-interactive.sh: line 602: local: 'label,' : not a valid identifier
    (Screenshot: http://i.imgur.com/QqkSP.jpg)
    I am able to successfully set a mount point and format each partition. But I receive the same set of 3 errors occur for each partition.
    10) Once I complete the formatting I proceed to step 8, install bootloader.
    It says Generating Grub device map.. This could take a while. Please be patient.
    I receivieve the following error on this screen: /usr/lib/aif/core/libs/lib-blockdevices-filesystems.sh: line 355: !((partition_flag)): command not found.
    (Screenshot: http://i.imgur.com/B5j4K.jpg)
    11) After the error displays it goes to the next screen, before installing grub you must review config file. etc.
    12) I hit ok and then :q the config file. Is there a critical change in the config file that I'm missing?
    13) After closing the file I select which the boot device where the GRUB bootloader will be installed. My only option is /dev/sda. I hit ok
    Then I get the following 2 errors:
    /usr/lib/aif/core/libs/lib-blockdevices-filesystems.sh: line 355: !((partition_flag)): command not found
    /usr/lib/aif/core/libs/lib-blockdevices-filesystems.sh: line 355: !((partition_flag)): command not found
    (Screenshot: http://i.imgur.com/ol840.jpg)
    13) Error installing GRUB. See /dev/tty7 for output. Ok
    14) GRUB was NOT successfully installed. Ok
    I checked out TTY7.
    It shows the installer issuing the following commands in GRUB.
    1) device (hd0,) /dev/sda
         Error 12: Invalid device requested
    2) root (hd0,0)
         Filesystem type is extf2, partition type 0x83
    3) setup (hd0,)
    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 (hd0,0)"... failed (this is not fatal)
    Running "embed /grub/e2fs_stage1_5 (hd0,0)"... failed (this is not fatal)
    Running "install /grub/stage1 (hd0,0) /grub/stage2 p /grub/menu.lst "... succeeded
    Done.
    4) quit
    I have tried rebooting from here and using the Arch CD to boot into the existing OS but it does not work.
    I tried grub-install /dev/sda
    I get Probing devices to check BIOS drives. This may take a long time.
    /dev/mapper../dm-0 does not have any corresponding BIOS drive.
    I have tried going into grub and issuing the same commands the install script did.
    Same errors.
    I'm afraid I don't have network access at the moment so I can't get a successful /arc/report-issues to run.
    I hope I've included enough information to start the troubleshooting.
    Let me know if I've missed anything!
    Thanks in advance,
    -Jason
    Last edited by username17 (2011-11-17 22:37:56)

    username17 wrote:I get Probing devices to check BIOS drives. This may take a long time.
    /dev/mapper../dm-0 does not have any corresponding BIOS drive.
    Your drive does not have an MBR to install grub to as it is a GPT disk - which is also not supported under the old GRUB.
    You need to create a small partition at the very beginning of the drive (8MB is plenty) and set the "bios_grub" flag. ie the "BIOS drive" your error refers to.
    You will then need to install the grub2-bios package following the chroot instructions on the grub2 wiki page here: https://wiki.archlinux.org/index.php/GRUB2#Installation
    ** Please note that I found the chroot mounts to be outdated - replace "/tmp/install" with "/mnt" **
    Your alternative solution is to boot a gparted liveCD and prepare your disk as MBR - this will (most likely) destroy all existing data on the disk.

  • [SOLVED]Unable to install grub "couldn't find /mnt/boot/grub/menu.lst"

    Ok so I was trying to install windows after I had arch installed, used an ubuntu cd to use gparted to create a partition, tried to go to the windows installation but it would endlessly send me back to restart the installation even after succesfully writting all files...
    So now I decided to not install it, went back into ubuntu/gparted, deleted the partition and rejoined the space with my main arch partition and then selected the "boot" flag to boot...
    Cannot boot, grub its still on /boot/ but the MBR its obviously tempered with by windows ( which coincidentally couldn't even find itself after writing mbr to its liking....*sigh* ).
    So I try to use my arch install cd to reinstall grub but i get this:
    "couldn't find /mnt/boot/grub/menu.lst is grub installed?"
    I tried to use the select packages thing to make sure the cd is mounted and mounts fine but it keeps getting me that error message. I managed to boot to my system just fine with arch root=/dev/sda1 but obviosly the kernell does not has my nvidia module which means I can't get into x which means i am using links and since my grub is not loaded i can't even get framebuffer so this is rather inconvenient.
    Im sure im missing a very simple and stupid thing but im so annoyed my brain must be saying "ok im done somebody else figure it out". I still have a backup copy of my grub menu.lst I made before. Do I just delete /bood/grub/ and try again? Am I missing something on the install procedure to be able to rewrite grub? Can I just do it from the command line or with pacman? Any help appreciate it thanks.
    Last edited by Misanthrope (2008-06-01 17:22:32)

    If you can get into your arch and cli then you should just be able to reinstall grub with
    install-grub /dev/sda
    or reinstall grub with
    pacman -S grub
    if the package is messed up or missing.

  • [PARTIALLY SOLVED] Arch on MacBook4: can't install GRUB

    I've been running Arch on my MacBook4 (4 years old now) for quite some time in dualboot mode and have already set up GRUB sucessfully several times. I therefore feel kinda bad that I have to open a new thread this time, but after wasting the whole morning on Google, I don't see another solution.
    What has happened is that I had to resize my Linux partitions because there was no space left on my system partition. I have the following partitions:
    sda1 - fat32 EFI partition
    sda2 - hfs+ Mac partition
    sda3 - ext4 Arch system partition
    sda4 - ext4 Arch home partition
    As mentioned, when I first organized my Arch partitions this way, I could successfully set up GRUB, but it was GRUB1 which I had to set up via grub shell. Now, as it looks to me, GRUB1 is not available anymore but only GRUB2 which doesn't use the grub shell anymore. I've not been able to install GRUB2 the last time (that's why I ended up using GRUB1) and I'm still not able to install it this time!
    When I start the MacBook and choose the Linux partition in rEFIt, I get to a black screen displaying GRUB_ and doing nothing more (because I don't have GRUB set up). That's how far I am right now.
    Now can anyone help me with setting up GRUB(2)? Thanks in advance for any help!
    Last edited by cryptkeeper (2012-09-05 06:13:14)

    I've succeeded in working around the problem of installing GRUB2 after I found out that grub-legary is nothing else but GRUB1. So all I had to do to get back a running system was:
    - removing the GRUB2 installation
    - installing grub-legacy
    - copying my old menu.lst to /boot/grub/
    - grub shell: root (hd0,2); setup (hd0); quit
    Now it works like a charm again.
    Still I only consider this thread half solved because I still don't know how to install GRUB2 on my system. It's not of vital interest to me anymore (I don't care too much why, that is, due to which boot loader, my system boots, as long as it boots), but a solution would nonetheless be nice since this thread is opened anyway.
    So: How can GRUB2 be installed on a MacBook dualboot system with rEFIt such as mine?

  • Cannot mount certain partitions: /dev/ entries do not exist

    Hello all. Strange problem here. First I will describe my disk layout. I triple boot Gentoo, Arch, and FreeBSD. My partitions look like this:
    /dev/hda = MAXTOR 6L040J2, ATA DISK drive 40GB
    hda1 = shared '/boot' partition
    hda2 = gentoo '/' partition
    hda3 = gentoo '/usr/' partition
    hda4 = gentoo '/home' partition
    /dev/hdb = SAMSUNG SP0802N, ATA DISK drive 80GB
    hdb1 = shared music partition mounted as /home/music on both Gentoo and Arch
    hdb2 = shared swap partition
    hdb3 = FreeBSD partition
    hdb4 = logical Partition
    hdb5 = archlinux '/' partition
    hdb6 = shared video partition mounted as /home/music/video on both Gentoo and Arch
    Now both gentoo and arch use devfs. From gentoo I can see all partitions in the /dev directory and mount accordingly, however, from Arch I cannot mount my gentoo partitions on /dev/hda, and in fact they do not even exist in the /dev directory. Only /dev/hda1 is visible (the shared boot partition which holds all my kernels regardless of distro).
    Running fdisk -l /dev/hda from arch gives me this puzzling output:
    Disk /dev/hda: 40.0 GB, 40027029504 bytes
    255 heads, 63 sectors/track, 4866 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/hda1 * 1 4111 33021576 55 EZ-Drive
    So it would seem that fdisk thinks that /dev/hda1 takes up the entire drive, and is labeled as 'EZ-Drive'?!?!?!?!?!? I can assure you that running the same command from gentoo gives me the correct partitions and disklabels ie: id 83  Linux
    Does anyone have a clue as to what is going on here? This isn't really a big deal at this point, just an interesting annoyance that I would like to discover the cause of.
    TIA

    I don't know how it could be that the kernels interpret the partition table differently, and I'm certainly not sure that this is what's going on. That's why I suggested loading Arch with the Gentoo kernel. I wouldn't expect the system to be its true self, but merely satesfy the curiosity by checking whether it would see the right partitions (a.k.a. trouble-shooting).
    It shouldn't be a problem to test this, unless your Arch root uses a file system that is not built into your Gentoo kernel. If for instance hdb5 is reiserfs and your 2.4 kernel has that as a module, you're probably out of luck regarding my suggestion. If this is the case, you could also try the Arch 2.4 kernel. It can coexist with your current kernel because the kernel packages for the two trees have different names.
    pacman -S kernel
    Hope this helps,
    -bogo

  • [solved] Cannot complete install, grub fails to boot the new install

    I'm using the 2009.08 USB image.
    I've tried this 2 weeks ago, tried it again today, same result. (I'm on Win7 meanwhile).
    I'm installing arch, everything goes fine.
    I've tried 2 setups:
    a)
    100GB ext4 /
    12GB swap
    (no separate /boot, should work)
    b)
    100MB ext3 /boot
    100GB ext4 /
    12GB swap
    Neither a) or b) will boot.
    When the newly installed grub boots, I get a error saying:
    filesystem type unknown, partition type 0x7
    I get this for the ext3, ext4, and windows partitions.
    I get it for both a) and b) setups.
    I have doublechecked the menu.lst file. I've even created another entry setting root=/dev/sdb1 (as opposed to the default /dev/disks/by-uuid/..).
    I should mention, I have two disks, the first (sda) is currently with a Win7 installation, the 2nd (sdb) is the one I'm trying to install Arch again (and failing).
    After the reboot, I've tried booting into the livecd again and manually trying to mount /dev/sdb1 /mnt, it works.
    Why isn't my grub boothing from ext{3,4}?
    Last edited by Frantic (2009-11-05 18:35:15)

    Rede wrote:
    I was getting that error but after re-installing grub and making some changes to the menu.lst file it was fixed.
    I was able to at one stage boot into arch but it gave problems with the root. Now it just seems to freeze while trying to load grub.
    I am currently trying yet another install of grub. I have been noticing though that my menu.lst file has been rolling back or not updating when I chroot back into my install after changing it earlier.
    Try mounting your /boot partition under /mnt/boot.

  • Dual booting win 7 and arch: cannot install grub to partition

    I have read the arch wiki page on dual booting and several other sources on line, but I am still struggling to get this to work.
    I am trying to dual boot arch and windows 7 on my lenovo ideapad s205. the machine comes with windows 7 pre-installed.
    I shrank the win 7 partition and added an extended partition with 3 logical partions for /boot, swap, and /.
    I am able to install and run arch by installing grub to the mbr. when I do this, though, I cannot boot windows. (the windows section of grub menu.lst is uncommented and points toward hda0,0. I have tried hda 0,1 as well).
    I have also tried to use the windows boot loader to load arch, as described in the arch wiki page on dual booting. The problem here is that, taking this approach, I should install grub to my /boot partition, but when I try to do this, the installer only allows me to install grub to sda or sdb (the usb stick).
    I have read that grub should be able to boot linux from a logical partition. Is this so?
    Is there something wrong with the arch installer that it is not giving me the option of installing to a partition rather than the mbr, or is this  a problem with my partition scheme, or something else?
    I am tempted to remove lenovo's recovery system, but on the other hand, I have already needed to use it several times while monkeying around with installing arch.
    Thanks for any help.
    UPDATE:
    I now have the laptop dual-booting win 7 and arch. My solution ( adapted from here: http://helms-deep.cable.nu/~rwh/blog/?p=177) was to:
    1. installed arch on the partitions I had created for it, but skipped the "install bootloader" stage.
    2. in win 7, I downloaded and installed EasyBCD and made an entry for arch in it. I checked the option to "Use EasyBCD's copy of GRUB"
    3. When I restarted, I got a grub error because the entry in grub's menu.lst was pointing at the wrong partitions for the kernel and root.
    4. So I went back into the arch live disk, mounted the boot partition and edited menu.lst.
    Now when I start the laptop, the windows boot loader starts and I can choose between win  7 and arch. when I select arch, grub4dos starts and gives me the option to start arch. this is not particularly elegant (nor is it fast), so I think this solution is less than ideal, but it does work.
    I'd be interestd in any thoughts about what went wrong and what a better solution would be.
    thanks.
    Last edited by ratchet (2011-10-10 19:09:16)

    ratchet wrote:II am able to install and run arch by installing grub to the mbr. when I do this, though, I cannot boot windows. (the windows section of grub menu.lst is uncommented and points toward hda0,0. I have tried hda 0,1 as well).
    Is this a typo in your post or how it was in menu.lst? Surely it should be hd0,0 and not hda0,0? The entry I have in my menu.lst is as follows:
    # (2) Windows
    title Windows
    rootnoverify (hd0,0)
    makeactive
    chainloader +1
    What was yours?
    Last edited by JHeaton (2011-10-10 20:18:22)

Maybe you are looking for

  • WEBUTIL FILE_SAVE_DIALOG BUG

    This is more untested code than a bug. I am using WEBUTIL_FILE.FILE_SAVE_DIALOG in my form to download a file from the database onto client machine. When the file dialog comes up and the user clicks on a directory to save to, the File Name field gets

  • Mapping drum kit to Yamaha DTxplorer

    Hi all I have recently bought a Mac Mini and Logic Pro X. My band have previously been recording the drums on my ancient eMac and GB '06 using the inbuilt sounds in the brain of the DTxplorer but would now like to make use of the drum kits in Logic.

  • Removing Drill Down is not summing up the values for key figure

    Hi , While analysing the data in BW report , I have encounter the problem in getting the correct data. BW report is showing two records for material , having different customer ie. customer1 & customer 2 . If i remove the customer from the Drill down

  • Problem for XSL copying  XML file with Error in expression '*|/'.

    Hi, I am trying to convert xml file to another xml through command-line interface but failed. java oracle.xml.parser.v2.oraxsl data.xml data.xsl data_new.xml My sample xml and xsl files are: 1. XML file <employee_data> <employee_row> <employee_number

  • Logical Diagram Notation - Information Engineering Notation

    I'm a little confused about the Logical Diagram Relational Properties diagram. In a parent/child relationship where parent is required and children are optional, the Source to Target Cardinality must be set to * and Target to Source Cardinality to 1.