[SOLVED]Booting into Arch after installation.

Good evening,
after getting a new harddrive (SSD) I've decidet to do a fresh install of Arch (it was already installed on the HDD I've used before).
The only difference made while installing is that I'm using a GPT-table and that I've configured grub for EFI.
After selecting Arch linux from the Grub menue I've get the message that there is a startup job running for sdb1, sdb2 and sdb3.
My Partition table:
gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.8
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 246162672 sectors, 117.4 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 6C1A58C8-7F1C-4E26-BD81-AB4BFB99F930
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 246162638
Partitions will be aligned on 2048-sector boundaries
Total free space is 2831 sectors (1.4 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 4196351 2.0 GiB EF00 Boot
2 4196352 239871182 112.4 GiB 8300 System
3 239872000 246162638 3.0 GiB 8200 Swap
and here my 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
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
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,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 13b889fb-a445-493a-afc7-2e342f381012
else
search --no-floppy --fs-uuid --set=root 13b889fb-a445-493a-afc7-2e342f381012
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=1366x768
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
insmod part_gpt
insmod fat
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 14A9-1329
else
search --no-floppy --fs-uuid --set=root 14A9-1329
fi
insmod gfxmenu
loadfont ($root)/grub/themes/Duet/SegoeWP-20.pf2
loadfont ($root)/grub/themes/Duet/SegoeWP-22.pf2
loadfont ($root)/grub/themes/Duet/SegoeWP-24.pf2
insmod jpeg
insmod png
set theme=($root)/grub/themes/Duet/theme.txt
export theme
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-13b889fb-a445-493a-afc7-2e342f381012' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 14A9-1329
else
search --no-floppy --fs-uuid --set=root 14A9-1329
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=13b889fb-a445-493a-afc7-2e342f381012 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-13b889fb-a445-493a-afc7-2e342f381012' {
menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-13b889fb-a445-493a-afc7-2e342f381012' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 14A9-1329
else
search --no-floppy --fs-uuid --set=root 14A9-1329
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=13b889fb-a445-493a-afc7-2e342f381012 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-13b889fb-a445-493a-afc7-2e342f381012' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 14A9-1329
else
search --no-floppy --fs-uuid --set=root 14A9-1329
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=13b889fb-a445-493a-afc7-2e342f381012 rw quiet
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/30_os-prober ###
### 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 ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
I'm a bit confused because in one point of the wiki it says that the efi partition is the /boot partition and on another it says that it only has to be about 1M big (but a kernel is a lot bigger (especially because I want to create some custom kernel's)).
I'm sorry if someone already asked something similar but I didnt find anything.
Thank's for the support in advance ^^.
Last edited by theblackdog (2014-10-25 22:28:49)

Output of lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 117.4G 0 disk
├─sda1 8:1 0 2G 0 part /mnt/boot
├─sda2 8:2 0 112.4G 0 part /mnt
└─sda3 8:3 0 3G 0 part
sdb 8:16 0 7.5G 0 disk
├─sdb1 8:17 0 559M 0 part /run/archiso/bootmnt
└─sdb2 8:18 0 31M 0 part
sr0 11:0 1 1024M 0 rom
loop0 7:0 0 241.3M 1 loop /run/archiso/sfs/airootfs
loop1 7:1 0 32G 1 loop
└─arch_airootfs 254:0 0 32G 0 dm /
loop2 7:2 0 32G 0 loop
└─arch_airootfs 254:0 0 32G 0 dm /
Contents of /etc/fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=13b889fb-a445-493a-afc7-2e342f381012
/dev/sdb2 / ext4 rw,relatime,data=ordered 0 1
# UUID=f094290d-4114-4ba1-9afc-c96858ab99a6
/dev/sdb1 /boot ext4 rw,relatime,data=ordered 0 2
# UUID=bd37b9d2-865a-4b19-aee9-7ff14cc7f959
/dev/sdb3 none swap defaults 0 0
Let me guess my UUID's don't match?

Similar Messages

  • [Solved] Can't boot into Arch after deleting some partitons

    About 6 months ago I installed Arch on a machine that used to run Ubuntu. Had some trouble at the time getting to boot into Arch but somehow managed. Now eventually decided to delete the old Ubuntu partitons to free up some space using gparted. Arch partition number changed from sda12 to sda6.
    On rebooting after deleting ubuntu partitions with gparted, I got an ubuntu splash screen and a whole lot of ubuntu boot options. Somehow these were all contained in my Arch's /boot/grub/menu.lst. Arch is all on one partition and no separate boot partition (which I had with Ubuntu - maybe I haven't deleted that and this is the problem?). Will need to check that out.
    I can chroot into Arch and did the following -
    grub> find /boot/grub/stage1
    (hd0,5)
    grub> root (hd0,5)
    Filesystem type is ext2fs, partition type 0x83
    grub> setup (hd0)
    Checking if "/boot/grub/stage1" exists... yes
    Checking if "/boot/grub/stage2" exists... yes
    Checking if "/boot/grub/e2fs_stage1_5" exists... yes
    Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded.
    succeeded
    Running "install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,5)/boot/grub/stage2 /boot/grub/menu.lst"... succeed
    ed
    Done.
    grub>
    The Arch /boot/grub/menu.lst had a whole lot of ubuntu stuff in it but I edited to the following -
    # menu.lst - See: grub(8), info grub, update-grub(8)
    # grub-install(8), grub-floppy(8),
    # grub-md5-crypt, /usr/share/doc/grub
    # and /usr/share/doc/grub-doc/.
    ## default num
    # Set the default entry to the entry number NUM. Numbering starts from 0, and
    # the entry number 0 is the default if the command is not used.
    # You can specify 'saved' instead of a number. In this case, the default entry
    # is the entry saved with the command 'savedefault'.
    # WARNING: If you are using dmraid do not use 'savedefault' or your
    # array will desync and will not let you boot your system.
    default 0
    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout 3
    ## hiddenmenu
    # Hides the menu by default (press ESC to see the menu)
    hiddenmenu
    # Pretty colours
    #color cyan/blue white/blue
    ## password ['--md5'] passwd
    # If used in the first section of a menu file, disable all interactive editing
    # control (menu entry editor and command-line) and entries protected by the
    # command 'lock'
    # e.g. password topsecret
    # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
    # password topsecret
    # examples
    # title Windows 95/98/NT/2000
    # root (hd0,0)
    # makeactive
    # chainloader +1
    # title Linux
    # root (hd0,1)
    # kernel /vmlinuz root=/dev/hda2 ro
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=(hd0,3)
    title Arch uuid
    #root (hd0,5)
    uuid d15cf4f9-18ca-4ec5-95bc-db0f6f264736
    kernel /boot/vmlinuz26 root=/dev/sda6 ro vga=775
    intrd /boot/kernel26.img
    title Arch hd
    root (hd0,5)
    kernel /boot/vmlinuz26 root=/dev/sda6
    intrd /boot/kernel26.img
    I have a bootinfo script which gives the following (from the chroot environment) -
    Boot Info Script 0.55 dated February 15th, 2010
    ============================= Boot Info Summary: ==============================
    => Grub 0.97 is installed in the MBR of /dev/sda and looks on the same drive
    in partition #6 for /boot/grub/stage2 and /boot/grub/menu.lst.
    => No boot loader is installed in the MBR of /dev/sdb
    sda1: _________________________________________________________________________
    File system: swap
    Boot sector type: -
    Boot sector info:
    sda2: _________________________________________________________________________
    File system: Extended Partition
    Boot sector type: -
    Boot sector info:
    sda5: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Mounting failed:
    mount: /dev/sda5 already mounted or sda5 busy
    sda6: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Mounting failed:
    mount: /dev/sda5 already mounted or sda5 busy
    mount: /dev/sda6 already mounted or sda6 busy
    sda7: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Operating System:
    Boot files/dirs:
    sda3: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Operating System: Ubuntu 10.04.1 LTS
    Boot files/dirs: /etc/fstab
    sda4: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Operating System:
    Boot files/dirs: /grub/menu.lst /grub/grub.cfg /grub/core.img
    sdb1: _________________________________________________________________________
    File system: xfs
    Boot sector type: -
    Boot sector info:
    Operating System:
    Boot files/dirs:
    =========================== Drive/Partition Info: =============================
    Drive: sda ___________________ _____________________________________________________
    Disk /dev/sda: 750.2 GB, 750155292160 bytes
    255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    Partition Boot Start End Size Id System
    /dev/sda1 417,690 6,554,519 6,136,830 82 Linux swap / Solaris
    /dev/sda2 25,414,954 1,465,144,064 1,439,729,111 5 Extended
    /dev/sda5 25,414,956 1,360,287,809 1,334,872,854 83 Linux
    /dev/sda6 1,360,287,873 1,423,198,349 62,910,477 83 Linux
    /dev/sda7 1,423,198,413 1,465,144,064 41,945,652 83 Linux
    /dev/sda3 6,554,520 25,414,829 18,860,310 83 Linux
    /dev/sda4 * 63 417,689 417,627 83 Linux
    Drive: sdb ___________________ _____________________________________________________
    Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    Partition Boot Start End Size Id System
    /dev/sdb1 2,048 1,953,523,711 1,953,521,664 83 Linux
    blkid -c /dev/null: ____________________________________________________________
    Device UUID TYPE LABEL
    /dev/loop0 squashfs
    /dev/sda1 2a95d85a-45fe-4584-88dd-0ee20e651ec5 swap
    /dev/sda2: PTTYPE="dos" PART_ENTRY_SCHEME="dos" PART_ENTRY_TYPE="0x5" PART_ENTRY_NUMBER="2"
    /dev/sda3 32495e1a-227c-4d23-9f63-b1319def0dd9 ext3
    /dev/sda4 d6dc69b0-967d-4886-b62d-8c0d6be06b41 ext3
    /dev/sda5 37971286-b8d3-4a1b-9f94-4008288fed6d ext3 data
    /dev/sda6 d15cf4f9-18ca-4ec5-95bc-db0f6f264736 ext3 30GB-02
    /dev/sda7 eb736131-b558-4404-9b83-7f1e6d9e76ae ext3 var
    /dev/sda: PTTYPE="dos"
    /dev/sdb1 0e83045d-a0bd-4d36-b61d-bdb905130dc2 xfs 1TB-04
    /dev/sdb: PTTYPE="dos"
    ============================ "mount | grep ^/dev output: ===========================
    Device Mount_Point Type Options
    /dev/sda12 / ext3 (rw,commit=0)
    =============================== sda3/etc/fstab: ===============================
    # /etc/fstab: static file system information.
    # <file system> <mount point> <type> <options> <dump> <pass>
    proc /proc proc defaults 0 0
    # /dev/sda1 = swap
    /dev/sda1 none swap sw 0 0
    # /dev/sda3 = root
    #UUID=32495e1a-227c-4d23-9f63-b1319def0dd9
    /dev/sda3 / ext3 relatime,errors=remount-ro 0 1
    # /dev/sda4 = boot
    # UUID=d6dc69b0-967d-4886-b62d-8c0d6be06b41
    /dev/sda4 /boot ext3 relatime 0 2
    # /dev/sda5 = home
    # UUID=670eee83-0a3e-429c-863f-b9ecced9f97e
    /dev/sda5 /home ext3 relatime 0 2
    #/dev/sda6
    #UUID=37971286-b8d3-4a1b-9f94-4008288fed6d
    /dev/sda6 /home/ben/Data ext3 defaults,relatime 0 0
    # /dev/sda7
    # UUID=fdb14ca4-d71d-489f-a00e-6e608770674c
    /dev/sda7 /var ext3 relatime 0 2
    # /dev/sda8
    /dev/sda8 /opt ext3 relatime 0 2
    # /dev/sda10 - Arch
    /dev/sda10 /mnt/arch ext3 relatime 0 2
    # Not sure what this is doing here
    # Have commented it out - May be the reason why xbmc and mythtv were crashing on dvd insert and play
    # /dev/hda /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
    # /dev/sde1
    # uuid appears to be 644406B3570C1846 -> ../../sde1
    #/dev/sde1 /home/ben/Data/TVRecordings-1TB01 xfs defaults,relatime 0 0
    #1TB-01
    UUID=76f3823a-81dc-45c9-a0b7-2bc6c3beb2f8 /media/1TB-01 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
    d defaults, relatime
    # 1TB-02
    UUID=59cbf7a1-7008-40d0-96ed-c6f231823d4f /media/1TB-02 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
    d defaults, relatime
    # 1TB-03
    UUID=0e936800-3c53-4b87-abc8-19be0ffca7f9 /media/1TB-03 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
    d defaults, relatime
    # 750GB-02 ext3 Partition
    # UUID giving problems, trying with dev
    # UUID=c23b9c9a-66fc-4256-9211-73156c1ac64a /media/750GB-02_ext3 ext3 defaults,relatime 0 0
    /dev/sde2 /media/750GB-02_ext3 ext3 defaults,relatime 0 0
    ============================= sda4/grub/menu.lst: =============================
    # menu.lst - See: grub(8), info grub, update-grub(8)
    # grub-install(8), grub-floppy(8),
    # grub-md5-crypt, /usr/share/doc/grub
    # and /usr/share/doc/grub-doc/.
    ## default num
    # Set the default entry to the entry number NUM. Numbering starts from 0, and
    # the entry number 0 is the default if the command is not used.
    # You can specify 'saved' instead of a number. In this case, the default entry
    # is the entry saved with the command 'savedefault'.
    # WARNING: If you are using dmraid do not use 'savedefault' or your
    # array will desync and will not let you boot your system.
    default 0
    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout 3
    ## hiddenmenu
    # Hides the menu by default (press ESC to see the menu)
    hiddenmenu
    # Pretty colours
    #color cyan/blue white/blue
    ## password ['--md5'] passwd
    # If used in the first section of a menu file, disable all interactive editing
    # control (menu entry editor and command-line) and entries protected by the
    # command 'lock'
    # e.g. password topsecret
    # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
    # password topsecret
    # examples
    # title Windows 95/98/NT/2000
    # root (hd0,0)
    # makeactive
    # chainloader +1
    # title Linux
    # root (hd0,1)
    # kernel /vmlinuz root=/dev/hda2 ro
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
    ### BEGIN AUTOMAGIC KERNELS LIST
    ## lines between the AUTOMAGIC KERNELS LIST markers will be modified
    ## by the debian update-grub script except for the default options below
    ## DO NOT UNCOMMENT THEM, Just edit them to your needs
    ## ## Start Default Options ##
    ## default kernel options
    ## default kernel options for automagic boot options
    ## If you want special options for specific kernels use kopt_x_y_z
    ## where x.y.z is kernel version. Minor versions can be omitted.
    ## e.g. kopt=root=/dev/hda1 ro
    ## kopt_2_6_8=root=/dev/hdc1 ro
    ## kopt_2_6_8_2_686=root=/dev/hdc2 ro
    # kopt=root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=(hd0,3)
    ## should update-grub create alternative automagic boot options
    ## e.g. alternative=true
    ## alternative=false
    # alternative=true
    ## should update-grub lock alternative automagic boot options
    ## e.g. lockalternative=true
    ## lockalternative=false
    # lockalternative=false
    ## additional options to use with the default boot option, but not with the
    ## alternatives
    ## e.g. defoptions=vga=791 resume=/dev/hda5
    # defoptions=quiet splash
    ## should update-grub lock old automagic boot options
    ## e.g. lockold=false
    ## lockold=true
    # lockold=false
    ## Xen hypervisor options to use with the default Xen boot option
    # xenhopt=
    ## Xen Linux kernel options to use with the default Xen boot option
    # xenkopt=console=tty0
    ## altoption boot targets option
    ## multiple altoptions lines are allowed
    ## e.g. altoptions=(extra menu suffix) extra boot options
    ## altoptions=(recovery) single
    # altoptions=(recovery mode) single
    ## controls how many kernels should be put into the menu.lst
    ## only counts the first occurence of a kernel, not the
    ## alternative kernel options
    ## e.g. howmany=all
    ## howmany=7
    # howmany=all
    ## should update-grub create memtest86 boot option
    ## e.g. memtest86=true
    ## memtest86=false
    # memtest86=true
    ## should update-grub adjust the value of the default booted system
    ## can be true or false
    # updatedefaultentry=false
    ## should update-grub add savedefault to the default options
    ## can be true or false
    # savedefault=false
    ## ## End Default Options ##
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-26-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-26-generic
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-24-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-24-generic
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-23-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-23-generic
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-22-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-22-generic
    title Ubuntu 10.04.1 LTS, memtest86+
    root (hd0,3)
    kernel /memtest86+.bin
    quiet
    ### END DEBIAN AUTOMAGIC KERNELS LIST
    ============================= sda4/grub/grub.cfg: =============================
    # DO NOT EDIT THIS FILE
    # It is automatically generated by /usr/sbin/grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    ### BEGIN /etc/grub.d/00_header ###
    if [ -s $prefix/grubenv ]; then
    load_env
    fi
    set default="0"
    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 recordfail {
    set recordfail=1
    if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
    insmod ext2
    set root='(hd0,3)'
    search --no-floppy --fs-uuid --set 32495e1a-227c-4d23-9f63-b1319def0dd9
    if loadfont /usr/share/grub/unicode.pf2 ; then
    set gfxmode=640x480
    insmod gfxterm
    insmod vbe
    if terminal_output gfxterm ; then true ; else
    # For backward compatibility with versions of terminal.mod that don't
    # understand terminal_output
    terminal gfxterm
    fi
    fi
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    set locale_dir=($root)/grub/locale
    set lang=en
    insmod gettext
    if [ ${recordfail} = 1 ]; then
    set timeout=-1
    else
    set timeout=10
    fi
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/05_debian_theme ###
    set menu_color_normal=white/black
    set menu_color_highlight=black/light-gray
    ### END /etc/grub.d/05_debian_theme ###
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Ubuntu, with Linux 2.6.32-26-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-26-generic
    menuentry 'Ubuntu, with Linux 2.6.32-26-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-26-generic ...'
    linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-26-generic
    menuentry 'Ubuntu, with Linux 2.6.32-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-24-generic
    menuentry 'Ubuntu, with Linux 2.6.32-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-24-generic ...'
    linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-24-generic
    menuentry 'Ubuntu, with Linux 2.6.32-23-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-23-generic
    menuentry 'Ubuntu, with Linux 2.6.32-23-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-23-generic ...'
    linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-23-generic
    menuentry 'Ubuntu, with Linux 2.6.32-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-22-generic
    menuentry 'Ubuntu, with Linux 2.6.32-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-22-generic ...'
    linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-22-generic
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_memtest86+ ###
    menuentry "Memory test (memtest86+)" {
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux16 /memtest86+.bin
    menuentry "Memory test (memtest86+, serial console 115200)" {
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux16 /memtest86+.bin console=ttyS0,115200n8
    ### END /etc/grub.d/20_memtest86+ ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry "Arch Linux (on /dev/sda10)" {
    insmod ext2
    set root='(hd0,10)'
    search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
    linux /boot/vmlinuz26 root=/dev/sda10 ro
    initrd /boot/kernel26.img
    menuentry "Arch Linux Fallback (on /dev/sda10)" {
    insmod ext2
    set root='(hd0,10)'
    search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
    linux /boot/vmlinuz26 root=/dev/sda10 ro
    initrd /boot/kernel26-fallback.img
    #### 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.
    # From Arch grub menu.lst
    # (0) Arch Linux
    #title Arch Linux [/boot/vmlinuz26]
    #root (hd0,0)
    #kernel /vmlinuz26 root=/dev/sda3 ro
    #initrd /kernel26.img
    #Note: With a separate boot partition, omit /boot from the path, (i.e. type set prefix=(hdX,Y)/grub and insmod
    (hdX,Y)/grub/linux.mod).
    #This introduces the "linux" and "initrd" commands, which should be familiar (see #Configuration).
    #An example, booting Arch Linux:
    #set root=(hd0,5)
    #linux /boot/vmlinuz26 root=/dev/sda5
    #initrd /boot/kernel26.img
    #boot
    ###menuentry "Arch1" {
    ###insmod ext2
    ###set root='(hd0,10)'
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
    PARTITION
    #linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
    UBUNTU THIS IS THE ROOT PARTITION
    #initrd /initrd.img-2.6.32-26-generic
    ###search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UU
    ID
    ###linux /boot/vmlinuz-26 root=635d7d02-3f5b-4af6-9c74-16b2af8cc7fd ro quiet splash # ARCH'S ROOT UUID
    ###initrd /boot/kernel26.img
    # /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
    ###menuentry "Arch2" {
    ###insmod ext2
    ###set root='(hd0,4)' #= TRYING UBUNTU'S BOOT
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
    PARTITION
    #linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
    UBUNTU THIS IS THE ROOT PARTITION
    #initrd /initrd.img-2.6.32-26-generic
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
    ###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
    ###initrd /boot/kernel26.img
    # /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
    ###menuentry "Arch3" {
    ###insmod ext2
    ###set root='(hd0,10)' #= TRYING UBUNTU'S BOOT IN HD FORMAT
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
    PARTITION
    #linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
    UBUNTU THIS IS THE ROOT PARTITION
    #initrd /initrd.img-2.6.32-26-generic
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
    ###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
    ###initrd /boot/kernel26.img
    # /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
    ### END /etc/grub.d/40_custom ###
    =================== sda4: Location of files loaded by Grub: ===================
    .0GB: grub/core.img
    .0GB: grub/grub.cfg
    .0GB: grub/menu.lst
    .0GB: grub/stage2
    .0GB: initrd.img-2.6.32-22-generic
    .0GB: initrd.img-2.6.32-23-generic
    .1GB: initrd.img-2.6.32-24-generic
    .1GB: initrd.img-2.6.32-26-generic
    .0GB: vmlinuz26
    .0GB: vmlinuz-2.6.32-22-generic
    .0GB: vmlinuz-2.6.32-23-generic
    .1GB: vmlinuz-2.6.32-24-generic
    .0GB: vmlinuz-2.6.32-26-generic
    =============================== StdErr Messages: ===============================
    No volume groups found
    mdadm: No arrays found in config file or automatically
    [/quote]
    Output of fdisk -l from chroot is -
    [quote]Disk /dev/sda: 750.2 GB, 750155292160 bytes
    255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 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: 0x0000b084
    Device Boot Start End Blocks Id System
    /dev/sda1 417690 6554519 3068415 82 Linux swap / Solaris
    /dev/sda2 25414954 1465144064 719864555+ 5 Extended
    /dev/sda3 6554520 25414829 9430155 83 Linux
    /dev/sda4 * 63 417689 208813+ 83 Linux
    /dev/sda5 25414956 1360287809 667436427 83 Linux
    /dev/sda6 1360287873 1423198349 31455238+ 83 Linux
    /dev/sda7 1423198413 1465144064 20972826 83 Linux
    Partition table entries are not in disk order
    Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk identifier: 0x00025bd3
    Device Boot Start End Blocks Id System
    /dev/sdb1 2048 1953523711 976760832 83 Linux
    I need to post this now and come back from a different machine to note the error messages I am now getting on boot. ...
    Note that when I boot and press esc to get the menu I get the menu.lst I created (in the second quote) above in /dev/sda6, ie the one with the Arch hd and uuid entries - so grub is looking there and finding that menu.lst, but something goes wrong after that.
    OK. Have now booted the machine and after pressing esc and selecting the uuid entry (the same thing happens with the hd entry) I get a whole lot of stuff, but what seems relevant is (typing it out) -
    List of all partitions:
    No filesystem could mount root, tried:
    Kernel panic - not syncing: VS: Unable to mount root fs on unknown-block(0,0)
    Pid: 1, comm: swapper Not tainted 2.6.39-Arch #1
    If anyone can help I'd really appreciate it. This is my MythTV machine so the WAF is about to take a big dive!
    If I could just install grub to the MBR as if this was a new installation of Arch that would be great.
    I am really lost as to what is going on, which I'm sure is evident.
    Thanks a lot
    belbo
    Last edited by belbo (2011-08-12 13:31:23)

    Hi. Unfortunately that didn't help.
    So next, based on this post https://wiki.archlinux.org/index.php/Ke … el_version I chrooted into Arch and (a) rolled back and (b) reinstalled my kernel but that didn't help either. I suspected it wouldn't because the kernel was working fine before I deleted the partitions in question.
    [2011-08-08 23:32] ==> Image generation successful
    [2011-08-08 23:32] upgraded kernel26 (2.6.39.3-1 -> 2.6.39.3-1)
    I then did a pacman -Suy and the linux package has now replaced kernel26. ( See this wiki entry http://www.archlinux.org/news/changes-t … filenames/). I didn't change anything in menu.lst owing to this and it seems there is no need to. Unfortunately this hasn't helped either - still getting the kernel panic. 
    Pacman.log relating to the new kernel package below -
    [2011-08-09 00:22] Running 'pacman -Suy'
    [2011-08-09 00:22] synchronizing package lists
    [2011-08-09 00:23] starting full system upgrade
    [2011-08-09 00:23] Running 'pacman -Suy'
    [2011-08-09 00:23] synchronizing package lists
    [2011-08-09 00:23] starting full system upgrade
    [2011-08-09 00:26] removed python-mygpoclient (1.5-1)
    [2011-08-09 00:26] removed kernel26 (2.6.39.3-1)
    [2011-08-09 00:26] warning: /boot/grub/menu.lst installed as /boot/grub/menu.lst.pacnew
    [2011-08-09 00:26] upgraded grub (0.97-17 -> 0.97-19)
    [2011-08-09 00:26] upgraded icu (4.8-1 -> 4.8.1-1)
    [2011-08-09 00:26] upgraded linux-firmware (20110512-2 -> 20110727-1)
    [2011-08-09 00:26] >>> Updating module dependencies. Please wait ...
    [2011-08-09 00:26] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
    [2011-08-09 00:26] ==> Building image from preset: 'default'
    [2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    [2011-08-09 00:26] ==> Starting build: 3.0-ARCH
    [2011-08-09 00:26] -> Parsing hook: [base]
    [2011-08-09 00:26] -> Parsing hook: [udev]
    [2011-08-09 00:26] -> Parsing hook: [autodetect]
    [2011-08-09 00:26] -> Parsing hook: [pata]
    [2011-08-09 00:26] -> Parsing hook: [scsi]
    [2011-08-09 00:26] -> Parsing hook: [sata]
    [2011-08-09 00:26] -> Parsing hook: [filesystems]
    [2011-08-09 00:26] -> Parsing hook: [usbinput]
    [2011-08-09 00:26] ==> Generating module dependencies
    [2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
    [2011-08-09 00:26] 7079 blocks
    [2011-08-09 00:26] ==> Image generation successful
    [2011-08-09 00:26] ==> Building image from preset: 'fallback'
    [2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    [2011-08-09 00:26] ==> Starting build: 3.0-ARCH
    [2011-08-09 00:26] -> Parsing hook: [base]
    [2011-08-09 00:26] -> Parsing hook: [udev]
    [2011-08-09 00:26] -> Parsing hook: [pata]
    [2011-08-09 00:26] -> Parsing hook: [scsi]
    [2011-08-09 00:26] -> Parsing hook: [sata]
    [2011-08-09 00:26] -> Parsing hook: [filesystems]
    [2011-08-09 00:26] -> Parsing hook: [usbinput]
    [2011-08-09 00:26] ==> Generating module dependencies
    [2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
    [2011-08-09 00:26] 23360 blocks
    [2011-08-09 00:26] ==> Image generation successful
    [2011-08-09 00:26] installed linux (3.0.1-1)
    I don't think I've mentioned that my old menu.lst seems to have disappeared and so must have been on one of the partitions that were deleted. I did have 2 Arch installations when I was setting things up months ago and that menu.lst may have been on the other partition but pointing to this partiton's kernel for booting. Presumably that's possible since this partiton is definitely the one I have been using for the last several months (confirmed by log and other files updated in the last few days etc). Even so, I suppose that probably wouldn't be relevant to this issue, since grub is finding the menu.lst on this partition when it boots so it is looking in the intended place now.
    It seems I'm at a bit of a dead end. It seems these kernel panics are usually because there is something wrong with the kernel - which there wasn't with mine (and presumably the kernel in the new linux package is fine) or there is a typo in menu.lst (I can't see one and nobody has pointed one out yet) or menu.lst is pointing to the wrong partition (mine is pointing to the same partition and /boot directory that is found by grub - which is where my boot image is located - so it seems to be correct). I have nevertheless tried editing the menu.lst entry when booting to boot from different partitions but so far that hasn't worked either.
    If anybody has other ideas I'd really appreciate it.
    If not, some suggestions on re-installing would also be appreciated. I have a recent tar archive of the partition, but presumably reinstalling that wouldn't be of much use since it would just put back what is currently there. I guess that I need to format the partition, create a separate boot partition, do a fresh install of Arch into the formatted partition (and with boot in the new boot partition). And then restore my tar backup (excluding the boot directory) into the formatted partition?
    Any assistance greatly appreciated.
    Thanks
    belbo
    Last edited by belbo (2011-08-08 23:17:49)

  • [SOLVED]Can't boot into OS after installation

    Hello all,
    I've ran into a few problems already all of which I could solve with somme googling etc.
    Until now the installation of arch Linux went pretty smoothly until I rebooted to get into the OS via grub (version 2), once I select Arch Linux in the menu the os starts booting but it stops at this: "a start job is running for dhcpcd on enp7s0 (x s/1m31s)" this always fails. After that 3 extra lines appear starting with a green OK all saying reached target ..........
    This is where no more progress is made, the only keys that generate a response are Ctrl+alt+Del then the system reboots.
    Here is a clear image of the status of the machine
    https://i.imgur.com/queQkEOh.jpg
    EDIT: If you guys need any extra information please ask, but I can't access the systems config files or anything due to this problem so suggestions on how to pull that data are welcome
    -- mod edit: converted img tags to url - Trilby --
    Last edited by Covati (2014-10-06 13:04:05)

    Trilby wrote:
    Welcome to the forums - please see the forum guidelines on how to post including image size restrictions.
    As for the issue - can you Alt-F2 or Alt-F3 to get to another tty?
    It worked, wow I feel dumb now.
    Anyways thank you for helping me out, I will look into the guidelines.
    Can mark this thread as solved!

  • Screen 'flicker'/artifacts after boot into arch

    i experience some sort of flickering/artifacts (dunno how to call it, it's like pixels flying across the screen) after i boot into arch. even when i'm (still) in a tty with no x session running. (before booting into arch, while in the grub menu, it's ok)
    it looks pretty much like this.
    my gpu is an ati radeon hd4570, i have the free radeon driver (xf86-video-ati) installed.
    not sure whether it can be a driver issue though, because it happens even when i'm not in a graphical session?
    unfortunately i don't know what to do or what to look at to fix this. investigating this issue i'm led to believe it could have something to do with grub or kernel settings or sth, but i have 0 experience with configuring either.
    i'm dualbooting with ubuntu 14.04 btw, which also runs the radeon driver, and i don't have the problem there.
    i'd appreciate any sort of help!
    (this is my first time posting here, i apologize if i ignored any forum etiquette)
    Last edited by weisbrot (2015-02-18 20:49:05)

    weisbrot wrote:my gpu is an ati radeon hd4570, i have the free radeon driver (xf86-video-intel) installed.
    For Radeon you should use xf86-video-ati, not xf86-video-intel.

  • [SOLVED]Ubuntu 11.10 broke grub2, can't boot into arch

    Hi, I'm having a little issue with grub2 at the moment, I have Arch installed on seperate /home / and /boot partitions, I installed Ubuntu using the "alongside" option in the installer which has added an option to boot into Arch on the grub bootup screen. However when I boot up into arch I get the follow message:
    Waiting 10 seconds for device /dev/hda3
    [ numbers] usb 1=-4.2: device descriptor read/all, error -3
    ERROR: Unable to find root device '/dev/hda3' .
    You are being dropped to a recovery shell
    Then I am promptly dropped into a recovery shell.
    My root device should be at /dev/sda5, not quite sure what's happened there.
    Any ideas on how to get this fixed? I think ubuntu has /boot on it's own parition, along with the rest of /.
    Last edited by will.price94 (2012-02-26 12:11:04)

    DSpider wrote:
    hda is an IDE drive.
    sda is a SCSI drive (SATA).
    Do you have both on your system? Or is Ubuntu getting it wrong?
    # sudo fdisk -l
    WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
    Disk /dev/sda: 750.2 GB, 750156374016 bytes
    255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 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: 0x568055d5
    Device Boot Start End Blocks Id System
    /dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
    /dev/sda2 206848 146802687 73297920 7 HPFS/NTFS/exFAT
    /dev/sda3 146802688 148828159 1012736 83 Linux
    /dev/sda4 148830206 1465147391 658158593 f W95 Ext'd (LBA)
    /dev/sda5 148830208 344139775 97654784 83 Linux
    /dev/sda6 344141824 781250559 218554368 83 Linux
    /dev/sda7 781252608 1257244671 237996032 83 Linux
    /dev/sda8 1257246720 1456762879 99758080 83 Linux
    /dev/sda9 1456764928 1465147391 4191232 82 Linux swap / Solaris
    Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes
    255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 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: 0x0004c41c
    Device Boot Start End Blocks Id System
    /dev/sdb1 2048 2930276351 1465137152 83 Linux
    Disk /dev/sdc: 1500.3 GB, 1500299395072 bytes
    255 heads, 63 sectors/track, 182401 cylinders, total 2930272256 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: 0x0005d269
    Device Boot Start End Blocks Id System
    /dev/sdc1 2048 2930272255 1465135104 83 Linux
    Ubuntu is getting it wrong, I have 2 SATA drives and an external USB drive.

  • [Solved] Booted into grub prompt

    Hello,
    I've followed the wiki to the last step but couldn't get booted into Arch:
    https://wiki.archlinux.org/index.php/Beginners%27_guide
    After I've generated the grub.cfg and rebooted.
    I got a grub prompt.
    I don't know what I am missing so please tell me what to do and I'll post the result.
    I'm installing it on qemu. The image is archlinux-2014.11.01-dual.iso
    fdisk result of the image:
    Disk /shosts/arch.img: 17 GB, 17179869184 bytes
    4 heads, 32 sectors/track, 262144 cylinders, total 33554432 sectors
    Units = sectors of 1 * 512 = 512 bytes
               Device Boot      Start         End      Blocks   Id  System
    /shosts/arch.img1              34        2047        1008   83  Linux
    /shosts/arch.img2            2048      411647      204736   83  Linux
    /shosts/arch.img3          411648    31868927    15728576   83  Linux
    /shosts/arch.img4        31868928    33554398      842688   82  Linux Swap / Solaris
    Warning: Partition 4 does not end on cylinder boundary.
    arch.imgX is actually /dev/vdaX
    Regards.
    Last edited by tgckpg (2014-11-24 07:10:31)

    After googling and such.
    I tried to use the grub command to boot it manually but couldn't get it work.
    I noticed some files are missing in /boot folder.
    ( Not sure, but from the look of it it seemed
    there is no such file initramfs-linux.img and vmlinuz-linux for me to run initrd or linux command in grub )
    So I boot back into the CD and ran "pacstrap -i base base_devel" & "grub-mkconfig -o /boot/grub/grub.cfg" again.
    And the file is there!
    And I booted into Arch!
    cheers:)

  • Hello! How can I change language of IndesignCC menus from russian into english after installation?

    Hello! How can I change language of IndesignCC menus from russian into english after installation?

    i don't think you can.
    uninstall id, open your cc desktop app>click settings (the gear icon)>preferences>apps>app language>english>reinstall id

  • I can boot into Arch, but not DM or DE [solved]

    I just recently installed Arch in VirtualBox. Arch is running on 1GB of RAM (changed from 512MB) and 8GB of storage with dynamic size enabled. I set the specs low as I want this to be portable and load on almost any machine. When it boots up I can access command line, but not DM or DE. If I set it to automatically boot into a DM or DE, it hangs (black screen). I have tried different DMs (GDM, KDM, SDDM) and DEs (Gnome, KDE, Plasma), but I get the same problem. During the boot process I get intel_rapl: no valid rapl domains in package 0 and SMBus base address uninitialized. While researching though, these problems don't appear to be linked to mine. Any advice would be helpful, thanks.
    Last edited by flavinator (2015-06-12 04:46:33)

    flavinator wrote:Update: So, I'm a little lost. I got all the packages installed. I edited the xinit file the way it says to. I chmod it.
    Why did you chmod it?  This is not in the instructions.
    flavinator wrote:When I startx though, X has no file or directory, and don't see where it says how to create one.
    What does this mean?  Is this some translation or interpretation of an error message?  Post the *actual* output.
    flavinator wrote:I thought it would do that when XDM installed.
    XDM is also not part of the instructions for testing TWM.  If you start doing random other steps, we will not be able to help you as we will not understand what state your machine is in.
    flavinator wrote:Update 2: I got startx to run, but then it fails with "Using system config directory "/usr/share/X11/xorg.conf.d" 0x00c00000, type = 1) Invalid argument (22) (II) Server terminated successfully"
    Please post the *full* output.  The server terminated successfully suggests a problem with your xinitrc, so as ewaller requested, we'll need to see that - after you provided the actual output and error messages you are getting.

  • [SOLVED] Grub won't boot into Arch...

    So, this all started when I got this wacky idea of trying Debian on a separate drive.
    Installs great, boots up and get a blank screen with blinky cursor..not in the mood to mess with it since I can't find
    a reasonable answer for what is wrong with it sooo I boot back into Arch but now I get Error device not found with a "Grub Rescue>" prompt.
    Not sure what to do now. I installed grub to the drive I was installing Debian on but it seemed to screw with my precious Arch too
    I looked around the forums for help but couldn't find anything.
    Also, it goes from post directly to the Grub Rescue prompt
    Last edited by PumpkinJack (2011-08-26 07:59:37)

    edit:
    ok here it is:
    # Config file for GRUB - The GNU GRand Unified Bootloader
    # /boot/grub/menu.lst
    # DEVICE NAME CONVERSIONS
    # Linux Grub
    # /dev/fd0 (fd0)
    # /dev/sda (hd0)
    # /dev/sdb2 (hd1,1)
    # /dev/sda3 (hd0,2)
    # FRAMEBUFFER RESOLUTION SETTINGS
    # +-------------------------------------------------+
    # | 640x480 800x600 1024x768 1280x1024
    # ----+--------------------------------------------
    # 256 | 0x301=769 0x303=771 0x305=773 0x307=775
    # 32K | 0x310=784 0x313=787 0x316=790 0x319=793
    # 64K | 0x311=785 0x314=788 0x317=791 0x31A=794
    # 16M | 0x312=786 0x315=789 0x318=792 0x31B=795
    # +-------------------------------------------------+
    # for more details and different resolutions see
    # https://wiki.archlinux.org/index.php/GRUB#Framebuffer_resolution
    # general configuration:
    timeout 5
    default 0
    color light-blue/black light-cyan/blue
    # boot sections follow
    # each is implicitly numbered from 0 in the order of appearance below
    # TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
    # (0) Arch Linux
    title Arch Linux
    root (hd0,0)
    kernel /vmlinuz-linux root=/dev/disk/by-uuid/6ab6f3ca-2c64-4264-97aa-10819e4561ed ro
    initrd /initramfs-linux.img
    # (1) Arch Linux
    title Arch Linux Fallback
    root (hd0,0)
    kernel /vmlinuz-linux root=/dev/disk/by-uuid/6ab6f3ca-2c64-4264-97aa-10819e4561ed ro
    initrd /initramfs-linux-fallback.img
    # (2) Windows
    #title Windows
    #rootnoverify (hd0,0)
    #makeactive
    #chainloader +1
    Last edited by PumpkinJack (2011-08-26 02:42:08)

  • Cannot boot into Arch using Gummiboot and Intel fake RAID

    This is my first time installing Arch Linux in a few years. The installation seemed to go fine, but I can't boot into it. At this point, when I try to boot into it this is my console output: http://pastie.org/9389435
    First of all, what confuses me about this output are the RAID lines. My system currently has two RAID arrays: My RAID0 array where Windows 7 is installed and my RAID1 array where I'm attempting to install Arch Linux. My fstab nor Gummiboot entry files refer to the RAID0 array at all. Why does it activate the partitions on the RAID0 array but not the RAID1 array?
    Second of all, lines 10, 11, 14, and 16 refer to /dev/sdd3. When I mount the partitions on my RAID array using the Arch live CD, I have to refer to them as either /dev/md/RAID1_0p1-4 or /dev/md124p1-4. The /dev/sda-sdd seem to refer to the individual drives. Why is it different when I try to boot into the system?
    Here is my current fstab: http://sprunge.us/bQCT
    The reason fstab is using labels is because the genfstab command generated an fstab that mounted the partitions on the RAID array with their /dev/md124p1-4 names. I noticed these names sometimes changed if I booted back into the live cd, so at one point I changed those names to the /dev/md/RAID1_0p1-4 names. Then in another attempt to fix the problem I'm currently having, I gave each of the partitions labels and I'm now referring to them by their labels in fstab. I also removed the commented UUID's since a few of them had changed since this fstab was generated. Everything to the right of the labels was kept from the original genfstab command.
    Here is my gummiboot arch.conf entry file: http://sprunge.us/HPVb
    I'm also referring to my root partition by label in this file, rather than the UUID which seems to be the norm. The reason for this is because I was previously getting an error saying that it couldn't even find the root partition based on that UUID. As you can see, I left the UUID line commented in case I have to use it again later.
    Here is my mkinitcpio.conf file, which I'm thinking the problem has something to do with this since it's the part I understand the least: http://sprunge.us/IFDL
    The modifications I made to this file were based on what I read in the fake raid article on the Arch wiki. All I did was make sure dm_mod and dm_mirror were added to the MODULES line and dmraid was added to the HOOKS line. At first I also had chipset_module_driver in MODULES, but it just generated warnings when I ran `mkinicpio -p linux` so I took it out. I don't know what that module would be for, since it only says "if necessary" on the wiki.
    As for the emergency shell it puts me in when it fails to boot, there's not really much I can do from there. The filesystem it puts me in looks entirely different from the root filesystem I can mount from the live cd.
    At this point, I'm stumped and I'm not sure where to go from here.

    x:5:respawn:/opt/kde/bin/kdm -nodaemon
    This is the line that's causing it.  It's probably not because of this line, but because kdm isn't starting properly (possibly erroring) and being re-run because of the respawn option.
    Try booting into single user mode, changing the default run level to 3, and debugging it from there (figure out why kdm doesn't want to start right).

  • Cannot Boot Into Archlinux After Install

    I'm trying to install Archlinux on my Lenovo Z570 laptop. I've already installed Windows on this computer, and I'm installing this in another partition I've created (created 3 partitions when I installed Windows with the default Windows tool).
    I'm using a bootable USB drive and have tried both downloading the complete .ISO file and downloading the .ISO for the netinstall and booting through that. Both times I follow the steps in the install guide (as detailed https://wiki.archlinux.org/index.php/In … ion_Guide) and after I reboot the system, my computer does not boot into anything. I'm trying to use syslinux as my bootloader, although I've tried the steps with Grub and they don't produce any better results. Additionally I installed it with my friend (he installed on his computer) and he used syslinux so I'd just like to keep our system with similar configurations (so I'd like to make the install work with syslinux).
    My partition table (extra partitions created with cfdisk) is laid out as:
    sda1 primary ntfs
    sda5 logical  ext4 bootable
    sda6 logical  ext4
    sda3 primary  FAT16 (empty formatted drive)
    sda4 primary (windows)
    I've set sda5 to be my root and sda6 to be my home. They are 15 and 85 gigabytes respectively.
    My syslinux.cfg file (/boot/syslinux/syslinux.cfg) is the standard generated file modified such that
    APPEND root=/dev/sda5 ro
    for both arch and archfallback.
    I've also tried the steps in (https://wiki.archlinux.org/index.php/Sy … al_Install), specifically using the altmbr, by entering:
    # printf '\x5' | cat /usr/lib/syslinux/altmbr.bin - | dd bs=440 count=1 iflag=fullblock conv=notrunc of=/dev/sda
    However the results are the same.
    I've tried the steps in the guide where it mentions setting acpi=off and booting - when looking at a terminal with a wall of text (that I can't move through). I can type but everything I've tried to type, but it always says "Cold not find kernel image: <text>", where <text> is whatever I entered. If I type "boot", it says "Invalid or corrupt kernel image."
    I would greatly appreciate any help as I've been trying this for a while.

    confusion-is-my-sedative wrote:Personally I don't use syslinux, but I know that with grub you have an option to go into command mode and manually give the parameters from which to boot. It could be that syslinux also has such options. You might want to check the config through a live cd if the bootloader menu isn't coming up. It could also be the windows. I'd say that a few diagnostic commands from a livecd would be your best bet. Then you could copy the output to a usb thumb drive, and we'd have better info to assess the situation. Good luck.
    Any advice on what diagnostics to run? All my config info I posted through viewing my system by inserting the USB drive and booting into a live Arch image - as it is there's nothing I can do by booting the computer without inserting this (or another live medium). Thanks.

  • IMac not connecting to network when booted into Mountain Lion Installation Partition

    My iMac for some reason won't connect to any networks in the list when I'm booted into the installer using a partition, I cick my network, but it does nothing! I even tried clicking a random network with a password it didn't even ask for the password after I clicked it, it wouldn't do anything! What do I do? How do I get this working in the installler partition?

    Reset the PRAM > About NVRAM and PRAM
    1. Shut down the computer.
    2. Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
    3. Turn on the computer.
    4. Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
    5. Hold the keys down until the computer restarts and you hear the startup sound for the second time.
    6. Release the keys.

  • Can't boot into Windows after splitting Mac partition with Disk Utility

    Hi everyone,
    I installed Windows 8 with BOOTCAMP, creating a large 871 GB partition with a smaller 127 GB partition for Windows. After installing Windows, I then went back to Disk Utility to shrink the Mac partition and add two new partitions, one for storage and another blank, hoping to use it to install Linux into one day.
    I did that, and now Windows doesn't boot. A Windows blue screen tells me I need to use the Windows DVD to repair it.
    I tried to use Disk Utility to delete the two new partitions I made and grow the Mac partition back to the max size of 871 GB. But it doesn't let me do this. The Disk Utility log doesn't report an error and thinks it worked but the partition stays the same size. However if I make the partition a little smaller, like 870 GB then it works. I'm wondering if the Recovery partition is hiding there and preventing me from fully expanding the Mac partition.
    What can I do?
    Here's what I get if I type in sudo gpt -r -vv show disk0:
    Code: 
    gpt show: disk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168 gpt show: disk0: Suspicious MBR at sector 0 gpt show: disk0: Pri GPT at sector 1 gpt show: disk0: Sec GPT at sector 1953525167 start        size  index  contents 0           1         MBR 1           1         Pri GPT header 2          32         Pri GPT table 34           6 40      409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B 409640  1701278816      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC 1701688456     1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC 1702957992     1846360 1704804352   248002560      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 1952806912      718223 1953525135          32         Sec GPT table 1953525167           1         Sec GPT header
    Here's what I get if I type sudo fdisk /dev/rdisk0:
    Code: 
    Disk: /dev/rdisk0     geometry: 121601/255/63 [1953525168 sectors] Signature: 0xAA55 Starting       Ending #: id  cyl  hd sec -  cyl  hd sec [     start -       size] ------------------------------------------------------------------------ 1: EE 1023 254  63 - 1023 254  63 [         1 -     409639] <Unknown ID> 2: AF 1023 254  63 - 1023 254  63 [    409640 - 1701278816] HFS+ 3: AB 1023 254  63 - 1023 254  63 [1701688456 -    1269536] Darwin Boot *4: 07 1023 254  63 - 1023 254  63 [1704804352 -  248002560] HPFS/QNX/AUX
    Here's what I get with gdisk:
    Code: 
    Disk /dev/rdisk0: 1953525168 sectors, 931.5 GiB Logical sector size: 512 bytes Disk identifier (GUID): 6075110F-7CEF-4604-85EE-6231B850E2AE Partition table holds up to 128 entries First usable sector is 34, last usable sector is 1953525134 Partitions will be aligned on 8-sector boundaries Total free space is 2564589 sectors (1.2 GiB)  Number  Start (sector)    End (sector)  Size       Code  Name 1              40          409639   200.0 MiB   EF00  EFI System Partition 2          409640      1701688455   811.2 GiB   AF00  1 TB APPLE HDD HTS54101 3      1701688456      1702957991   619.9 MiB   AB00  Recovery HD 4      1704804352      1952806911   118.3 GiB   0700  BOOTCAMP

    Okay, the code I typed didn't display properly in the forum. Let me try again.
    Here's what I get when I type
    sudo gpt -r -vv show disk0:
    gpt show: disk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168
    gpt show: disk0: Suspicious MBR at sector 0
    gpt show: disk0: Pri GPT at sector 1
    gpt show: disk0: Sec GPT at sector 1953525167
           start        size  index  contents
               0           1         MBR
               1           1         Pri GPT header
               2          32         Pri GPT table
              34           6        
              40      409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
          409640  1701278816      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
      1701688456     1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
      1702957992     1846360        
      1704804352   248002560      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
      1952806912      718223        
      1953525135          32         Sec GPT table
      1953525167           1         Sec GPT header
    And when I type fdisk /dev/rdisk0 I get:
    Disk: /dev/rdisk0          geometry: 121601/255/63 [1953525168 sectors]
    Signature: 0xAA55
             Starting       Ending
    #: id  cyl  hd sec -  cyl  hd sec [     start -       size]
    1: EE 1023 254  63 - 1023 254  63 [         1 -     409639] <Unknown ID>
    2: AF 1023 254  63 - 1023 254  63 [    409640 - 1701278816] HFS+       
    3: AB 1023 254  63 - 1023 254  63 [1701688456 -    1269536] Darwin Boot
    *4: 07 1023 254  63 - 1023 254  63 [1704804352 -  248002560] HPFS/QNX/AUX
    Kappy,
    I can boot into OS X just fine so if possible, I'd like to avoid reformatting everything. If you know of a way I can add more than 2 partitions with OS X and Boot Camp, please let me know. As far as I know, rEFInd can recognize more than two partitions, but I don't think it can edit partitions on a GPT / hybrid MBR system. Or am I wrong?

  • [SOLVED] Boot into different OS one time using grub

    I have a remote Arch Linux system, that I don't have physical access to too frequently. I wake this system up with WOL and then SSH in. By default, it boots into the first option on the grub menu, which is Arch. I don't want to change the default grub option, but I want to be able to change something while in Arch, reboot, have grub pick the second boot option, use the second OS (which could be any OS, not necessarily Arch), and then when I reboot again, grub would pick the default boot option.
    Is this possible?
    Last edited by gsingh93 (2013-12-12 21:08:45)

    https://wiki.debian.org/GrubReboot#Usage

  • Windows 7 won't boot, during or after installation, only through the Windows DVD

    Hi,
    I've been trying to install Windows 7 on a Macbook Pro 15'' (Mid 2010) through Boot Camp. The OS X version is Mountain Lion (the notebook was bought with Snow Leopard, and I got Lion and Mountain Lion through the Mac App Store). I don't have a physical Windows 7 DVD, but I have valid and genuine serials (seriously), so I downloaded a retail copy through this article (http://arstechnica.com/features/2012/06/blowing-away-bloatware-a-guide-to-reinst alling-windows-on-a-new-pc/), burned it with Disk Utility (in 2x - I've read reports of people complaining that maximum speex, 8x, could bring problems), and used Boot Camp Assistant to install. The Assistant downloaded the drivers and burned them to a DVD, and also began the Windows installing smoothly.
    Here's the problem, though: when Windows does its first reboot throught the installation process, the Mac stops at a grey screen with a flashing question mark (as if indicating that it doesn't know how to boot). To fix that, I restart and hold the option key, and then select to boot FROM THE WINDOWS DVD - then the installation continues from where it left off. It then reboots once more, where I get stuck at the same point - flashing question mark. If I repeat the process one more time, it finishes the installation just fine. If I try to restart the machine, however, it doesn't boot to Windows - I get stuck at the same flashing question mark. To boot into Windows sucessfully, I've got to hold the option key, and select for it to boot from the Windows DVD - if I try to boot from the windows partition, the problem repeats itself.
    Can anyone share some knowledge about this? I looked through the web like crazy, but amazingly, this does not seem to be a common problem people have when installing Windows on Macs.
    Just as a heads up, I installed Boot Camp on Windows (the DVD created through the Boot Camp Assistant with the most recent files downloaded straight from Apple) to see if it would fix the problem, but it didn't. I also downloaded 5 different iso's for Windows 7, making sure they were untouched/MSDN/full retail versions and burned them through Disk Utility at 2x, and trying to install them reproduces the very same error I just described.

    SP1 has been trouble for some Macs. Don't know so don't ask why. Pre-SP1 then worked fine.
    Try Windows 8 Preview.
    Some people use VirtualBox, install there, and use VB and windows native tools to burn the DVD.
    Once you’ve downloaded the ISO for your Windows edition and bit-ness, you can either burn it to a DVD using Windows 7's built-in DVD burning tool or copy it to a USB drive using Microsoft’s Windows 7 USB/DVD download tool—our guide will help you through it step-by-step.
    Because it sounds like even though you used 2x that it is not a good DVD. Or DVD media/brand. Or the Superdrive - which has to be internal on your model unless you're hacking the USB-DVD driver plist.
    Microsoft Windows 8 Preview
    http://msdn.microsoft.com/en-us/windows/apps/default
    Windows 8 Blog
    https://blogs.msdn.com/b/b8/
    Installing Windows 8 On a MacBook Air
    http://www.pcmag.com/article2/0,2817,2393005,00.asp
    http://huguesval.com/blog/2012/02/installing-windows-7-on-a-mac-without-superdri ve-with-virtualbox/

Maybe you are looking for