[SOLVED]Gummiboot cannot boot arch

Hello. I've been reading the wiki guide until the end when i got stuck. I have windows 8 installed with a UEFI mobo so i just used the same ESP for arch. Now i try to boot arch but get a "vmlinuz not found" message. What did i do wrong?
while still on live cd i mounted the EFI partition (/dev/sda2) to /boot (same root and home partition) and then installed and configured gummiboot as described.
Do i have to add that ESP to the fstab file? Or how to fix it?
Last edited by Juszr (2015-03-31 17:10:49)

Load up the Arch live ISO, mount your partitions and use `arch-chroot` then post the output of:
ls /boot
# efibootmgr -v
lsblk -f
# parted -l
You can use `sprunge` to post the output of the commands.
<command> | curl -F 'sprunge=<-' http://sprunge.us
https://wiki.archlinux.org/index.php/Li … in_clients

Similar Messages

[SOLVED] Fail to boot Arch x86_64 live CD on a HP laptop

Hey, guys, what's up?
Well, here's the thing: I bought a new laptop a couple days ago and I'm kind of having some trouble. Its a HP Pavilion dm4-1063cl (this model: http://www.notebookcheck.info/HP-Pavili … 579.0.html, just in case).
I ran some tests in Windows 7 about the architecture of the processor and it clearly seems that it can support arch x86_64 bits. However, I tried to boot Arch x86_64 by a Net Installation CD and it doesn't work. The process fail in the "Loadin UDEV events" phase, something like that. PS: the i686 image boots perfectly.
Then, I thought that was the CD I burned the reason for trouble - I did not check md5sum and stuff like that. So, I burned another dual image (with boths i686 and x86_64) and tried to run again the 64bits kernel. It did not work in the same phase.
The only response I get is a dark screen that never seems to go away. It was a panic I've never seen before with Arch Linux.
The only alternative I can think right now is trying an older version of the live image CD and see what happens, but it doesn't seem like a very good option. Any ideas?
Hope someone of you can help me. Here in Brazil, most of computers we buy come with Windows installed and we don't have quite a chance of not getting - or paying for - it. I'm sure I'll have such a trouble installing dual boot with Arch Linux, but I really miss my Arch Linux...
And, damn, I worked too hard to get a new processor. I really dont wanna use Arch i686 on a pc with x86_64 architecture, it seems like an option, but a dumb one. =p
Cheers,
Wilson.
EDIT: It turns out that tt was not a kernel panic as I thought. The kernel changed the resolution of the display during this fase, and somehow it doesent work.
The trick I used to solve this was adding "nomodeset" to the kernel line in the Live CD booting. Btw, you can do it by selecting the booting option you want in the live CD and pressing TAB. Then, you can edit the kernel line. (:
Last edited by wilsaooo (2010-12-28 06:17:41)

lamegaptop wrote:
Resurrecting this post because I may help you or someone else.
HP DM4-1265, Intel Corei5, Intel Graphics. (Two days old, windoze wiped, Arch installed)
At boot the brightness is, for some unexplained reason, set all the way down to 0 on these intel based DM4 laptops. A few simple <Fn>+<F3> turns the brightness back up.
To solve this I had to put this in rc.local -
echo 6 > /sys/class/backlight/acpi_video0/brightness
you can enter it manually to test first (as root). Try to turn your brightness up and down with it to make sure it works.
My fan ran like crazy too. HP chose to default a BIOS setting that keeps the fan running constantly. I disabled that and all is well. Fan only comes on when needed and lm_sensors shows my temps, right now, at 43C. Ambient is at 77F right now (I'm in Florida) and this kick butt Arch laptop is, in fact, on my lap.....
Don't give up man.
First of all: thanks for replying.
I installed manually the "coretemp" kernel modules and lm-sensors now give some different response. The script "sensors-detect" does not find any answer.
Looks like the temperature run in a regular level (50º-60º), which I consider a good sign. However, sometimes when I use arch for 24h+, it shuts down suddenly and does not let me boot my computer again - I believe it is a overheating problem. Happened a couple times, big no big deal.
On the other hand, in Windows 7 I have no trouble at all. The temperature goes around 40º with some daily activities. It worries me out because I used - and I do use - largely and successfully Arch i686 version in crappy notebooks with no heating at all.
I tried some tweaks in the rc.local, but none of them seemed to really work. With cpufreq, I could slow down the processors and maintain a regular temperature. Looks like I can list some of the fans speed in the /sys/ files, but much of them do not seem to have any change at all. Some of them looks like to have some "max_state" set to low values like 1, but most do have a limit like 10.
I will keep trying. If there's anything new, I'll post here
Cheers,
Wilson

[Solved] Dual UEFI Booting Arch against pre-existing Ubuntu install

Hi All,
I'm new to Arch Linux and have just managed to install it on my T530 Lenovo laptop along side a pre-existing Ubuntu installation.
However, although I did consult the dual boot posting and article here on the site beforehand, those articles seemed to be about installing Grub. Since I already have it up and working, I was nervous about deleting it and so potentially loosing my working Ubuntu installation.
I tried installing mounting my pre existing /boot/efi partition but the pre-existing vmlinuz-linux file (no doubt from my Ubuntu installation) prevented it from working. My solution was to create the boot folder on the same partition as my Arch installation.
I now have an installation that works (kind of) however, it appears each time I boot up, I have to edit the Grub entry for my Arch installation to update the UUID Grub points to to get it to load up Arch. I can't find where the actual file being loaded in Grub resides (the file that it appears generates this script, is itself built from a series of predefined variables).
I admit I am playing at the moment - I'm keen to get to grips with this distro and am up for considering all options including deleting and starting again to learn to get it set up correctly. My questions are:
How should I have done this so that my Arch linux distro was loaded via Grub called by the UEFI and had the same booting file structure as the already existing Ubuntu installation (using the BOOTLOADER partition and the /boot/efi folders on it)
How do I edit the Grub file for my Arch distro so it stays edited (no more retyping all the UUIDs each time I load it up
Is there a way to get to the installation I currently have to an the more ideal state
Details taken thanks to the bootrepair application are here:
http://paste.ubuntu.com/10682898/
Thanks and regards,
Simon
Last edited by simon_sjw (2015-04-22 11:50:52)

I don't think there are any Ubuntu kernel images on your EFI system partition (they are in /boot, not /boot/efi).
If you want Arch to boot in an EFI system you should mount /boot (rather than /boot/efi) to the EFI system partition.
To do this, copy the /boot folder over to /dev/sda1 and add it to your /etc/fstab (in Arch):
/dev/sda1 /boot vfat rw,relatime,discard,nodev,nosuid,noexec,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
It's probably best to install & configure GRUB from Arch rather than Ubuntu because Arch mounts /boot to the ESP while all other distributions mount /boot/efi so the results may get confusing (ie, GRUB may create menu entries to boot Ubuntu with your Arch kernel and vice versa); also the Arch kernel image is booted read-write whereas most other kernel images are booted read-only.
https://wiki.archlinux.org/index.php/GRUB#UEFI_systems
I find the os-prober script can fail sometimes so this is probably your problem here.
Personally, I use gummiboot to boot my Debian system by copying the kernel image & initial ramdisk to the EFI system partition using these commands in Debian (this would also work in Ubuntu):
# mount /dev/sda1 /mnt
# cp /vmlinuz /initrd.img /mnt
Then I make a gummiboot menu entry; your Ubuntu entry would look like this:
title Ubuntu
linux /vmlinuz
initrd /initrd.img
options root=/dev/sda2 ro
Add any kernel parameters after "ro" and make an entry for Arch as well (you may also need to configure /boot/loader/loader.conf as per the ArchWiki page) & install gummiboot from Arch using:
# gummiboot install
You can then create a post-install script at /etc/kernel/postinst.d/zz-update-gummiboot in your Ubuntu system to copy over the kernel image & initrd to the ESP whenever the kernel is updated:
#!/bin/sh
mount /dev/sda1 /mnt
cp /vmlinuz /initrd.img /mnt/
umount -R /mnt
Make this executable:
# chmod +x /etc/kernel/postinst.d/zz-update-gummiboot
This method will only work if you have /boot mounted to the EFI system partition (as outlined in the Beginner's Guide).

[Solved] Unable to boot Arch off SUSE GrUB

Hi,
I have several OS installed on my machine. I used to boot everything including Arch but BSD, Solaris & PCBSD with GrUB2 off UbuntuStudio. Earlier today I installed SUSE GrUB on sda and now I am unable to boot Arch. I've used SUSE GrUB earlier and was able to boot Arch off it.
Here is my menu.lst
# Modified by YaST2. Last modification on Sun Oct 17 18:52:19 SGT 2010
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader
default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,30)/boot/message
##YaST - activate
###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 11.2 - 2.6.31.14-0.1
root (hd0,30)
kernel /boot/vmlinuz-2.6.31.14-0.1-desktop root=/dev/disk/by-id/ata-ST3320418AS_9VMD0YPT-part31 resume=/dev/disk/by-id/ata-ST3320418AS_9VMD0YPT-part5 splash=silent quiet showopts vga=0x315
initrd /boot/initrd-2.6.31.14-0.1-desktop
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.2 - 2.6.31.14-0.1
root (hd0,30)
kernel /boot/vmlinuz-2.6.31.14-0.1-desktop root=/dev/disk/by-id/ata-ST3320418AS_9VMD0YPT-part31 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x317
initrd /boot/initrd-2.6.31.14-0.1-desktop
###Don't change this comment - YaST2 identifier: Original name: windows 1###
title Windows 7 Ultimate Edition x64
rootnoverify (hd0,0)
chainloader +1
###Don't change this comment - YaST2 identifier: Original name: other###
title FreeBSD 8.1 i386
rootnoverify (hd0,2)
chainloader +1
###Don't change this comment - YaST2 identifier: Original name: other###
title OpenSolaris 2009.06 b134 x86
rootnoverify (hd0,3)
chainloader +1
###Don't change this comment - YaST2 identifier: Original name: other###
title PC-BSD 8.1 amd64
rootnoverify (hd2,0)
chainloader +1
###Don't change this comment - YaST2 identifier: Original name: CentOS (2.6.18-194.11.4.el5xen) (/dev/sda6)###
title CentOS (2.6.18-194.11.4.el5xen) (/dev/sda6)
root (hd0,5)
kernel /boot/vmlinuz-2.6.18-194.11.3.el5 ro root=/dev/sda6 rhgb quiet
initrd /boot/initrd-2.6.18-194.11.3.el5.img
###Don't change this comment - YaST2 identifier: Original name: Centos-base###
title CentOS-base (2.6.18-194.el5) (on /dev/sda6)
root (hd0,5)
kernel /boot/vmlinuz-2.6.18-194.el5 ro root=/dev/sda6 rhgb quiet
initrd /boot/initrd-2.6.18-194.el5.img
###Don't change this comment - YaST2 identifier: Original name: linux (/dev/sda8)###
title PCLinuxOS
root (hd0,7)
configfile /boot/grub/menu.lst
###Don't change this comment - YaST2 identifier: Original name: linux (/dev/sda10)###
title Simply Mepis
root (hd0,9)
configfile /boot/grub/menu.lst
###Don't change this comment - YaST2 identifier: Original name: Chakra GNU/Linux (/dev/sda12)###
title Chakra GNU/Linux (/dev/sda12)
root (hd0,11)
configfile /boot/grub/menu.lst
###Don't change this comment - YaST2 identifier: Original name: Fedora (2.6.34.7-56.fc13.x86_64) (/dev/sda14)###
title Fedora (2.6.34.7-56.fc13.x86_64) (/dev/sda14)
root (hd0,13)
configfile /boot/grub/menu.lst
###Don't change this comment - YaST2 identifier: Original name: linux (/dev/sda16)###
title Mandriva Spring 2010.1
root (hd0,15)
configfile /boot/grub/menu.lst
###Don't change this comment - YaST2 identifier: Original name: Calculate Linux Desktop x86_64 10.9 KDE (/dev/sda18)###
title Calculate Linux Desktop x86_64 10.9 KDE (/dev/sda18)
root (hd0,17)
configfile /boot/grub/menu.lst
###Don't change this comment - YaST2 identifier: Original name: linux###
title Arch linux 2010.05 x86_64
rootnoverify (hd0,18)
chainloader +1
###Don't change this comment - YaST2 identifier: Original name: Desktop -- openSUSE 11.3 - 2.6.34.7-0.3 (/dev/sda23)###
title openSUSE 11.3 - 2.6.34.7-0.3
root (hd0,22)
configfile /boot/grub/menu.lst
###Don't change this comment - YaST2 identifier: Original name: other###
title caeLinux
root (hd0,24)
kernel /vmlinuz root=/dev/sda25 ro quiet splash
initrd /initrd.img
###Don't change this comment - YaST2 identifier: Original name: other###
title UbuntuStudio 10.04 amd64
root (hd0,26)
kernel /vmlinuz root=/dev/sda27 ro quiet splash
initrd /initrd.img
###Don't change this comment - YaST2 identifier: Original name: other###
title Linux Mint 9 amd64
root (hd0,28)
kernel /vmlinuz root=/dev/sda29 ro quiet splash
initrd /initrd.img
Here is etc/fstab from Arch -
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 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/sda19 /boot ext2 defaults 0 1
/dev/sda20 / ext4 defaults 0 1
/dev/sda21 /var ext4 defaults 0 1
/dev/sda22 /home ext4 defaults 0 1
/dev/sda5 swap swap defaults 0 0
I've results from bootinfo script as well but the file is big and I am unable to post all those details in here.
Best,
David
Last edited by avenuemax (2010-10-18 05:30:48)

Here is the menu list off PCLinuxOS
timeout 15
color black/cyan yellow/cyan
gfxmenu (hd0,7)/boot/gfxmenu
default 0
title linux
kernel (hd0,7)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=77fb6caf-c436-4855-b25a-436f4f6c40f0 vmalloc=256M resume=UUID=92ecb3e1-84a1-4855-8a49-3c9616638795 splash=silent vga=788
initrd (hd0,7)/boot/initrd.img
title linux-nonfb
kernel (hd0,7)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=77fb6caf-c436-4855-b25a-436f4f6c40f0 vmalloc=256M resume=UUID=92ecb3e1-84a1-4855-8a49-3c9616638795
initrd (hd0,7)/boot/initrd.img
title failsafe
kernel (hd0,7)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=77fb6caf-c436-4855-b25a-436f4f6c40f0 failsafe vmalloc=256M
initrd (hd0,7)/boot/initrd.img
title Windows 7 Ultimate Edition x64
root (hd0,0)
map (0x81) (0x80)
map (0x80) (0x81)
makeactive
chainloader +1
title CentOS (Final)
root (hd0,5)
configfile /boot/grub/menu.lst
title MEPIS Linux 8.5
root (hd0,9)
configfile /boot/grub/menu.lst
title Arch
root (hd0,18)
configfile /grub/menu.lst
title Fedora (Goddard)
root (hd0,13)
configfile /boot/grub/menu.lst
title Mandriva Linux (Official)
root (hd0,15)
configfile /boot/grub/menu.lst
title Calculate Linux sda18
root (hd0,17)
configfile /boot/grub/menu.lst
title Chakra
root (hd0,11)
configfile /boot/grub/menu.lst
title openSUSE 11.3 (x86_64)
VERSION = 11.3
root (hd0,22)
configfile /boot/grub/menu.lst
title PC-BSD 8.1 amd64
root (hd2,0)
chainloader +1
title FreeBSD 8.1 i386
root (hd0,2)
chainloader +1
title OpenSolaris 2009.06 b134 x86
root (hd0,3)
chainloader +1
I can boot Arch from here, wish I get to do that from SUSE GrUB.

Cannot boot arch

Hey folks.
Got a brand new HP dv6 laptop with an AMD Phenom quad core processor that's refusing to boot. I got through the install ok, and the reboot after the install. I was installing the gnome desktop environment and took the dog out while waiting on the huge download/install. When I came back, my laptop screen was blacked out, and didn't respond to any keyboard/mouse stimuli.
I did a hard power off, and started it back up, and tried to boot arch. Among the startup fly-by info, I saw:
CPU 1: Not responding
CPU 2: Not responding
CPU 3: OK
After this, a few more lines go by, and then the system locks up with a blacked out screen and a flashing caps lock light. Same happens when I try and boot into Arch recovery. Windows still boots just fine.
It's a 64 bit install.

To respond to ewaller's suggestions:
Neither Ctrl + Alt + F12 elicits a response, nor Ctrl + Alt + F1-F6.
In my best attempt at trying to provide more information, I've used my android to take a video of the laptop starting up, up to the blank black screen, hopefully it can be of use. On a mildly related note, I think it's weird that I can see myself in the reflection of the screen once it goes black, but I'm trying to fix my laptop here, so bear with me
Video is .3gp format, usual mobile video format, VLC can play it.
http://goose.honk-honk.org/files/2011-0 … 15_708.3gp
If I can get away without having to do a reinstall, then I'd prefer not to, as the installation seemed to go off without a hitch. But if it appears that's what the actual issue is, I can certainly reinstall.
Thanks.

Cannot boot Arch (USB or HDD) in UEFI Mode

I have a new MSi GT70-0ND, 1x 128GB SSD (no RAID) and 1x 750GB HDD. The SSD was preloaded with an MSi OEM copy of Windows 8. I did not receive an OEM disc, so I've tried to avoid touching the SSD and the hidden recovery partition on the HDD.
Using Universal USB Installer, installed archiso onto USB flashdrive.
Windows boot device selection menu did not detect the flashdrive.
Checked UEFI BIOS settings - USB set to "Full Initial".
Moved flashdrive from port to port, eventually was detected.
Reboot, received an error relating to bootloader signing.
Rebooted again into UEFI BIOS settings, disabled secure boot.
Rebooted, received infamous "No loader found. Configuration files in \loader\entries\*.conf are needed."
Googled, checked forums, saw gummiboot issues, recommendations to use rEFInd, and dd/UEFI issue.
Transferred archiso to working Arch machine, followed instructions here https://wiki.archlinux.org/index.php/UE … B_from_ISO.
Installed rEFInd using instructions here https://bugs.archlinux.org/task/31894#comment102233. I have since tried various changes to refind.conf and can not discern any difference.
Attempted to boot laptop from flashdrive in UEFI mode after Windows' boot device menu again failed to detect flashdrive multiple times.
Got rEFInd menu, found nothing functional (except Windows bootloader, of course): Arch entry froze the system requiring hard reboot, UEFI Shell v2 gave an assertion error (from memory, it was "String.c(166) String != ((void *)0)"); Googled, seeing some related but no identical errors, UEFI Shell v1 failed to start reporting something like "using load options '<null string>'".
Rebooted in BIOS/Legacy mode, but flashdrive was unbootable (duh)
Again using Universal USB Installer, installed archiso onto flashdrive.
Rebooted in BIOS/Legacy mode, archiso menu appeared, but during udev events, received a drm/nouveau init table error; Hard reboot. Appended
nouveau.modeset=0
to kernel line, everything worked
Installed vanilla Arch system to the HDD including UEFISYS partition.
When it came time to set up and install rEFInd/efibootmgr, of course
modprobe efivars
failed.
Redid flashdrive the UEFI-safe way on Arch machine, attempted to boot in UEFI mode, it appears that menu entries from my /boot/efi (UEFISYS) partition are present, but this is irrelevant as only the Windows bootloader and \refindx64.efi work (loads rEFInd graphical mode, in which nothing works except BOOTX64.efi which quickly flashes a message with a file path (too quickly to read) then loads Windows. UEFI Shell v2 now has same error as v1:
Using load options '<null string'> Error: Not Found while loading shellx64_v2.efi
rEFInd (version 0.5.0) "About" dialog reports EFI Revision 2.31, Firmware: American Megatrends 4.653, Screen Output: Graphics Output (UEFI)
I have tried adding various things to the refind.conf "options" directive, e.g. gpt, loglevel=7, pci=nocrs, add_efi_memmap, archisobasedir=arch, archisolabel=ARCH_201212, acpi=off, etc. in different combinations.
I am at wits' end. Bottom line: nothing but rEFInd (via flashdrive) and Windows works in UEFI boot mode - nothing. Any help will be greatly appreciated. Thank you.

I doubt if this will help you with your main goal, but I've fixed a few memory bugs in rEFInd recently, so the "String.c(166) String != ((void *)0)" error you mentioned might go away if you upgraded to the latest version of rEFInd (0.6.0).
Beyond that, here's a suggestion:
Prepare a USB flash drive or CD-R with rEFInd 0.6.0. Be sure to include an EFI driver for whatever filesystem you used in Arch's /boot (or root, if there's no separate /boot partition) in the flash drive's or CD's EFI/BOOT/drivers_x64 directory. (Note that rEFInd 0.6.0 includes an ext4fs driver.)
Using an emergency disc, create a refind_linux.conf file in Arch's /boot directory. Include, at a minimum, two lines, each of which should include the options "ro root=/dev/{whatever} initrd={\path\to\initrd}", changing the device filename to point to your root and the initrd= specification to point to your two Arch initrd files (one for each line). The path should be relative to the root of whatever filesystem holds those files, so if you've got a separate /boot partition, there would be no directories, just the filename preceded by a backslash; and if you have no separate /boot partition, you'd lead with "\boot\". Note the need for BACKslashes, not forward slashes, in the initrd= specification (but forward slashes in the root= specification).
Reboot using the rEFInd flash drive or CD-R you've prepared. With any luck, rEFInd should come up and show you an Arch option. Try using it. If it fails, try again, but hit Insert and select the second option from the list.
With any luck this will get your system booted in EFI mode, but I can't make any promises about that.

[SOLVED] Can only boot Arch via CD

Hi all,
I've installed 64 bit Arch on the 2nd hard drive of a Dell Optiplex 980.
It works very nicely, but I have a strange boot issue:
If I boot from the Arch CD, and select "Boot other OS", hit Tab, and manually edit the grub line to "chain.c32 hd 1 0", I am taken to the grub menu on the hard drive and can select my install which boots and runs fine.
If I select the 2nd HD in the BIOS boot menu (instead of the CD), I get to the same grub menu, but upon selecting my install, I get an Error 17.
Has anyone run into this before?
Thanks in advance!
Last edited by basementhead (2010-09-24 17:52:11)

Turns out I misunderstood how grub works.
When I changed my menu.lst to (hd 0,0) it works.
I thought that the 2nd drive was (hd 1,0), which was reinforced by the boot CD working with (1,0), but I guess the drives are renumbered when you boot from CD?
The big clues were that the partition that grub said couldn't boot was 0xde (a Dell partition), and I was sure I'd wiped the entire drive, but I knew that the 1st drive was a default Dell/Windows7 install.
Then using grub command line menu, I typed "find /sbin/init" and it found it on (hd0,2), and the mystery was solved....
Anyway - fixed by treating the drive as if it was /dev/sda (hd 0,0) instead of /dev/sdb (hd 1,0)
Thanks!

[Solved] Can't boot arch after merge linux partition

Before this i have issue with my partition table, but i can fix it with testdisk.
After that, i merge all my linux partition into one. I mean like this
Before i merge my linux partition:
/ >> /dev/sda3
/var >> /dev/sda4
swapfile >> /dev/sda6
/home >> /dev/sda7
My new partition
/ >> /dev/sda3
swapfile >> /dev/sda6
i can't boot my arch after i backup and moved my home and var directory to /dev/sda3 with livecd.
How to fix this issue?
Last edited by nizar (2009-03-28 04:18:29)

Solved by myself! LOL
I edit and remove /dev/sda4 and /dev/sda7 in my /etc/fstab file with livecd.
Now, arch boot without /dev/sda4 and /dev/sda7

[SOLVED] Unable to boot Arch installer

Hello everyone.
I am no experienced Linux user (I'm just about one year and a half), but I think that dealing with things is the way to learn about them. I'm using Debian and want to switch to Arch.
I have an USB drive, and would like to put the installer (sorry? I'm not sure if that's the correct name. Please excuse me if I am not too concise) on it, without using a CD. I also have an Internet connection through ethernet, and I guess the "installer" will be able to use it to download any needed files.
So, as explained in the wiki and some external guides, I have copied the ISO I downloaded to the USB drive (with dd), just after formatting it as FAT32 with MBR.
I rebooted, with the USB plugged in, entered the BIOS menu and set the USB floppy as the first boot device. Then I exited from BIOS. I saw the LED of my pendrive flicking but no more, the BIOS stayed there (Press ESC to enter BIOS setup menu) and the light always flicking. (I waited about half an hour and nothing happened.)
I have tried it many times, and nothing has changed. I'm now a bit scared: is there anything wrong with my motherboard? Maybe with the filesystem on the external drive? I was wondering if there were any other choices to install Arch from within another Linux distro (Debian "Squeeze" in this case). I know nothing about chroot and other advanced techniques, but (if this helps) I don't want to save anything from my hard drive, i.e., I want a clean install.
Thank you, and, as I said, sorry if this question is very weird, or if I'm missing something important. I'm sure I've looked through many places in the web -too many, I guess; my eyes now hurt me. I'm also not very good at English so, sorry again.
P.S.: I have just tried with a CD-R burning the ISO with Brasero, and it didn't work. The same: freezing. I have UEFI disabled in my BIOS. I'm now wondering what's happening with my computer. It has about five years, and it looks like packed rubbish, but ...
Last edited by Kalrish (2013-03-02 18:46:23)

It sounds like you're mixing up the methods for creating the USB install media. You mention formatting with FAT32, that's from the Without overwriting the USB drive method. But you also mention copying the iso with dd, which is from the Overwrite the USB drive method.
You should follow one method or the other from the wiki only, and pay attention to the output for any errors. Then, if things go wrong again, you will be able to provide better detail.

[SOLVED]Can't boot Arch after installation-grub use wrong uuid in bios

Hello I would like to ask for Your help and say hello. I'm new here.
I have one big problem with Arch. Can't boot it after base installation. The same problem with Arch, that was mentioned in this topic:
https://bbs.archlinux.org/viewtopic.php … 7#p1294597
I have the same problem and the same error:
No such Device: ad4103fa-d940-47ca-8506-301d8071d467.
Loading Linux core repo kernel ...
error: no such partition.
Loading initial ramdisk ...
error: you need to load the kernel first.
Press any key to continue..._
I'm new here, and with Arch, could you explain me how to fix it? I tried the solution given in the link above, several times but with each time i have errors and warnings from the post 1 in mentioned topic. I installed my Arch from usb thumb drive. Maybe this is something to do with it? Also, my hard drive that Arch is installed on is being connected to a "raid card" named Adaptec, but during installation my disk is being found so i think that drivers is present and works ok, so it is not related to this, also there is no raid present, i use it only as a mean to connect to motherboard because there is not enough sata port, and because:
https://bugs.archlinux.org/task/35626
he wrote that this error is also on virtualbox, so it is not my fault and Adaptec related issue.
I haven't tried this yet:
Sotanaht,
I had the exact same problem as you, but I was able to fix it by replacing the bad grub.cfg file with the grub.conf file found in the same directory. If you try this do not forget to back up your original file (just in-case smile)
because i don't know much about it, don't want to destroy data on my hard disks or to destroy my other distros (i use Ubuntu with derrativates such as Mint, Kubntu, Lubuntu, Xubuntu, and Slackware 13.37 and 14.00).
If you could explain it in details i would be really happy.
I could post something about my setup, please write what. My computer is:
-AMD X4 PII 955 runinng at 3.2GHz
-4GB DDR2 runinng at base clock (800 if i remember correctly)
-about 7 hard drive disk connected to a sata ports, one adaptec drive that i mentioned above and one dvd-rom
-nvidia GTX260
-850W PSU Chieftec
Last edited by firekage (2013-07-02 08:11:29)

Yes, of course. I did it several times with
grub-mkconfig -o /boot/grub/grub.cfg
and the result is always the same - Error posted above.
Here is my grub.cfg file:
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 ad4103fa-d940-47ca-8506-301d8071d467
else
search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-ad4103fa-d940-47ca-8506-301d8071d467' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 ad4103fa-d940-47ca-8506-301d8071d467
else
search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=ad4103fa-d940-47ca-8506-301d8071d467 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img
menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-ad4103fa-d940-47ca-8506-301d8071d467' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 ad4103fa-d940-47ca-8506-301d8071d467
else
search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=ad4103fa-d940-47ca-8506-301d8071d467 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
### 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 ###
It is wrong, the root partition is different than in this, we can see that this grub leads to wrong root partition, i posted my root partition at the bottom from /etc/fstab. I don't know how to fix it - i'm not familiar with the dos names (hd 0,5 and so on).
Here is my /etc/fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sdb2
UUID=59603166-5d8a-4aaf-81f7-5a822fd630e5 / ext4 rw,relatime,data=ordered 0 1
# /dev/sdb1
UUID=20028674-d7e8-4bf4-8551-64f133641962 none swap defaults 0 0
(END)
Last edited by firekage (2013-07-01 06:26:59)

[SOLVED] nouveau error while booting arch

Hi!!! I'm newbie to arch, here is an error I can't solve myself. I search in google for solutions but they didn't solved. Please help me to solve this. I dual booted arch linux with window 8.1. After installation, while booting for the first time, this error occurred.
Here is the error I found.
[0.063411] Ignoring BGRT: Invalid status 0 (expected 1)
starting version 218
Arch_Linux: clean, 70622/18677760 files, 1643393/74703025 blocks
[ 15.759913] nouveau E[ PIBUST][0000:01:00.0] HUBO: 0xffffffff (0x1a
[ 15.759952] nouveau E[ PIBUST][0000:01:00.0] GPCO: 0x00000001 (0x1a
[ 15.823494] nouveau E[ PBUS][0000:01:00.0] MMIO: 0x00000000 FAULT a
[ 15.824050] nouveau E[ DRM]Pointer to TMDS table invalid
[ 15.824072] nouveau E[ DRM]Pointer to flat panel table invalid}
Last edited by aaa234 (2015-02-04 04:18:42)

aaa234 wrote:
runical wrote:
That is a different problem to be honest. I assume that you can login using your normal user? If you set up sudo you might be able to get into root by using
sudo su
and change the password like that.
I'm sorry if this is a noob question. Where do I type sudo su because as soon as the OS is booted, the system asks localhost login and password. I haven't installed any desktop environment yet. I only set up a password under arch-chroot but I can't login with and without that password.
I was assuming a normal installed environment with a normal user. Using "sudo su", you can abuse privileges granted by sudo to circumvent the password required by su. A well configured sudo should not allow this, but in this case it seemed likely that the system was not completely set up yet.
problem has been solved with this https://bbs.archlinux.org/viewtopic.php?id=168879
Then, if there are no more problems, please mark the thread as solved.

[SOLVED] Is Refit required for single-boot Arch on Macbook Pro?

I have a Macbook Pro 7.1, and now that the issue with a non-supported chipset has a workaround I am planning to create a single boot Arch system using the latest Archboot that comes with the 2.6.35 kernel.
If I understand well I need the non-efi grub combined with the firmware's bios compatibility mode if I want 2d/3d accelerated gfx, since that does not work currently with grub2-efi. One question I cannot find an answer to though is whether or not I need Refit and an EFI partition for this. The Arch wiki (nor the Debian/Gentoo/Refit docs) is not very clear about this. Is it only needed for multi-boot setups or for all setups that use bios compatibility?
Last edited by rwd (2010-09-06 15:44:00)

Veovis Muad'dib wrote:You need to bless the Arch partition from OS X, probably running from USB or something like that
Do you mean that I need to install Arch besides the existing OSX and 'bless' that arch partition from OSX in order to be able to remove all non-Arch partitions?
Veovis Muad'dib wrote:, and then make sure to never zap the PRAM..
Not that I was planning to do this, but does this remove the possibility to boot Arch?
Veovis Muad'dib wrote:As for if you can change BIOS settings, no. You can change boot disk, but that's it. What would you need to do in the BIOS anyway?.
I just thought it might come in handy for tweaking powermanagement, wake-on-lan, bluetooth and stuff like that.
litemotiv wrote:Also be sure to set your boot partition active if you plan to fdisk, EFI won't be able to see it otherwise.
Thanks all for the info!
Last edited by rwd (2010-08-24 16:13:27)

[SOLVED]How to install Arch Linux UEFI to dual-boot?

Hey,
so I have a Lenovo G50-70 on which I want to have a Windows-Arch dualboot. I followed the Beginner's Guide, installed Arch but ended up with an inaccessible Windows. I could boot into Windows from the BIOS utility, but not from the gummiboot bootloader.
The guide said if I wanted to dual-boot, I must leave windows EFI partition alone, which I did. I have my Windows partitions set up the Windows way, with the system reserved and EFI and recovery partitions, and I have my Windows partition of course and a data partition. After that I have some unallocated space, on which I made the Arch partitions, /dev/sda6 as an ESP partition for the EFI files, /dev/sda7 as root, /dev/sda8 as swap and /dev/sda9 as /home. The install process went without any error, then I made some configurations and installed dosfstools & efibootmgr. After that, I installed gummiboot and ran "gummiboot --path=/boot install". After that I created the configuration files exactly like in the guide, unmounted the partitions, rebooted and saw that there's no (easy) way getting into Windows. So my question is: how can I install Arch to have a working dual-boot system?
Thanks for any help in advance!
Regards, Matteussz
Last edited by Matteussz (2015-02-11 20:41:37)

Hey,
Writing to you on my working dual-boot with ArchLinux (Windows 8.1 64-Bit, UEFI)
So first step I've done is creating free space of an existing partition in the windows disk management (windows button and r and then type diskmgmt.msc). At this step, you have to record which partition your efi partition is (just take a look at your efi partition and remember the mb of this partition for later)
Then go into the uefi settings (bios) and disable secure boot as well as fast boot, otherwise it could cause data crash.
Boot your Arch Live CD and follow the beginners guide all the way along till you reach the disk management.
If you want to have swap, you can create yours right now, should be a primary partition of about 4gigs.
Next partition is gonna be your home, system partition (I've didn't created two partitions for home and for the system but you could do this as well as just go with one partition) this partition gonna be formatted in ext4
Next step, you have to mount your windows-efi partition in /boot/efi but don't format it dont remeber if it asks you how to use the partition but if so, just use as fat32.
After the disk management go ahead with your arch installation and follow the beginners guide. (Make sure you're using the grub bootloader)
After finishing the installation, restart your system, hopefully you will recognize the opening grub menu. (but dont scare, windows wont show in the grub menu at this time so you have to boot your arch)
Arrived in arch linux type the command
grub-mkconfig -o /boot/grub/grub.cfg
Reboot and your done with your Arch Linux, Windows 8 dual boot, hopefully

[solved] cannot boot from dd usb and cannot install 64 with unetbootin

hi,
been trying to install arch for almost 24 hours now. i just cannot manage to setup USBs to boot from.
first i was using unetbootin, but when the device not found error came up i tried using the methods recommended in the wiki. however, my hp elitebook 2540p cannot boot from the usb created using dd or imagewriter. so i went back to unetbootin and figured out the error was that the syslinux.cfg file needed to have ../../ replaced by archisobasedir=arch archisolabel=KINGSTON. now however, i cannot seem to figure out how to install a 64 bit system. when i run pacstrap all packages have i686 at the end, which i assume means its the 32 bit one.
help
EDIT: ok i have now used 3 different USB sticks and run
sudo dd if=~/Downloads/archlinux-2012.07.15-netinstall-dual.iso of=/dev/sdd
on them. plugging them into the 2540p the laptop just wont boot. it wont get past the first hp screen, where i normally press esc to enter the menu so i can choose boot options. the usb just blinks and nothing happens. this same problem happens with imagewriter in windows.
Last edited by iOfWhy (2012-07-29 13:01:10)

McDoenerKing wrote:Was the usb stick mounted, when issueing the dd command?
Did you use "of=/dev/sdx1" instead of "of=/dev/sdx" for the dd command?
Which image did you use?
i wrote exactly
sudo dd if=~/Downloads/archlinux-2012.07.15-netinstall-dual.iso of=/dev/sdd
as mentioned in the edit above, the computer wont get past the hp screen where one gets the option to press the esc key... the usb just blinks and nothing happens...
EDIT:
no the usb was not mounted...
the image was checked with both sha1sum and md5sum...
EDIT2:
ok so i think i am in... i reformatted the usb with fat filesystem, and then went through the second instructions from the wiki, ie installing "Without overwriting the USB stick"... But i am still wondering why i couldnt just do the normal dd method. Is it that the hp bios cannot read certain filesystems?
Last edited by iOfWhy (2012-07-28 13:39:40)

[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]Gummiboot cannot boot arch

Similar Messages

Maybe you are looking for