Kernel26 2.6.26.3-1: Probing EDD [SOLVED, like]

Hi,
After the upgrade to kernel26 2.6.26.3-1 the boot process stops at the kernel message "Probing EDD...". The situation gets scary as I discover that livecds like MiniMe and Knoppix refuse to boot too. Thanks to another box (not yet upgraded) found about kernel option edd=off. I edited edd=off first into GRUB command line; now the system is back to normal, though during the boot process kernel complains a lot about this or that (sata3) undetected, relinked, etc. Is my situation safe or there are proper measured to be taken?
My /boot/grub/menu.lst:
# 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,1)
kernel /boot/vmlinuz26 edd=off root=/dev/disk/by-label/Root ro
initrd /boot/kernel26.img
# (0) Arch Linux
title Arch Linux BootChart
root (hd0,1)
kernel /boot/vmlinuz26 root=/dev/disk/by-label/Root init=/sbin/bootchartd ro
initrd /boot/kernel26.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,1)
kernel /boot/vmlinuz26 root=/dev/disk/by-label/Root ro
initrd /boot/kernel26-fallback.img
title Memtest86+ [/boot/memtest86+/memtest.bin]
kernel (hd0,1)/boot/memtest86+/memtest.bin
# (1) Windows
#title Windows
#rootnoverify (hd0,0)
#makeactive
#chainloader +1
Last edited by Llama (2008-09-05 11:43:19)

A bit of additional information: after the upgrade EDD failure shows on the fallback kernel as well as on the current (2.6.26.3-1) kernel. Which means that some other piece of software/configuration is to blame.
A post here suggested a syslinux trouble; I've tried pacman and discovered that syslinux has never been installed on my system. So my Arch is supposed to run without it. I don't want to experiment in the dark - any suggestions?

Similar Messages

Kernel reboots right after "Probing EDD"

When booting, the kernel starts to initialize but right after "Probing EDD" it fails, rebooting instead. If i use the kernel option "edd=off" the "Probing EDD" line doesn't show, but still the kernel reboots at that point. I'm convinced this is not an EDD-related problem, but trouble with whatever comes next. FWIW, some googling turned up the idea of trying "hpet=disable" but that made no difference. Tried loading the alternate kernel, got same thing.
What should the kernel be printing after "Probing EDD"?
Potential suspects for the original cause of this problem: i updated with pacman -Syu two days ago which provided a new kernel (2.6.29?), and i've been fiddling with trying to get sound to work again. Maybe i screwed up the kernel modules or some file in /etc/modules.d/. Though this is a laptop, i turn it off only rarely. It's a Gateway 6860FX.

Hi i have the same trouble of EDD and reboot, only way for fix (this happen when the last kernel upgrades) is go to arch, and make again the pacman -S kernel26. My fstab is
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/dvd2 /media/dvd1 auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
#hds
UUID=5a4ea1d2-287a-48b8-b50c-65a59b1d7ed8 / jfs noatime,defaults 0 1
UUID=87b857ca-275f-4bc4-b48a-72eee660e7f0 swap swap defaults 0 0
UUID=9c1d25b0-6f2a-47c3-aaea-42f12e81a4a2 /home ext4 noatime,barrier=0,defaults 0 1
UUID=41eccea1-fb78-4727-b788-5878698cfcba /mnt/disk ext3 defaults 0 1
UUID=e0b55c91-8614-4dd6-862b-c1635c2158b3 /mnt/disk2 reiserfs defaults 0 1
UUID=decca5e5-88b1-43ea-a9dc-63c384c86cc5 /mnt/disk3 ext3 defaults 0 1
UUID=49f202c3-7b86-4a10-8535-85783a30b9f1 /Movies reiserfs defaults 0 1
and, menu.lst:
and # (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/sda1 elevator=deadline
initrd /boot/kernel26.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,0)
kernel /boot/vmlinuz26 edd=off root=/dev/disk/by-uuid/5a4ea1d2-287a-48b8-b50c-65a59b1d7ed8 ro
initrd /boot/kernel26-fallback.img
# (2) Windows
#title Windows
#rootnoverify (hd0,0)
#makeactive
#chainloader +1
any tip, is really welcomed..thx!!
Last edited by enito (2009-06-23 05:15:53)

[SOLVED] Probing EDD then system reboots ???

I read the user who recently asked about this same problem, but i could not solve it.
What happens is, I try to boot and it, stops on Probing EDD and then reboots on me.
I put in the bootloader and did:
arch root=/dev/sda4 (my root partition) and it loaded up.
I tried a /sbin/lilo -v and it give me this error: Fatal: raid_setup: stat("/dev/hda")
I don't have a raid setup though... not sure what this means.
I also tried to this:
arch
mount /dev/sda4 /mnt
mount /dev/sda1 /mnt/boot
mount --bind /dev /mnt/dev
mount-t proc none /mnt/proc
mount -t sysfs none /mnt/sys
chroot /mnt
then tried to run lilo and the same thing happens.
I also tried the Arch fallback and that fails, saying Kernel panic - not syncing. Attempted to kill init!
I found one more thing to try right now...
anyone know what this could be?
Last edited by efourseven (2009-06-19 02:00:40)

Thanks you for the reply. Sorry for the confusion, I fixed my typo's in my previous post's. I use lilo. I am not sure how to copy my config files, I dual boot this computer and right now I can only use windows.
My lilo config says:
boot=/dev/hda (which is maybe why I am getting this Fatal: raid_setup: stat: ("/dev/hda") error? It tries to boot up /dev/hda4 as root from the lilo.conf. Should I try switching them to /dev/sda4?
I have been running Arch for quite awhile now, and nothing like this has ever happened. I installed it years ago.
I tried the wiki articals on Boot Recovery, almost all of them. Everytime I try to run lilo it gives me that same error.
Ok.. I got somewhere!!
I just went into my /etc/fstab and /etc/lilo.conf and switched all the /dev/hda to /dev/sda and I am now in the system without the FILESYSTEM CHECK FAIL error. I still cannot boot though. But... I can now copy my config files here...
Here is my lilo.conf
# /etc/lilo.conf
boot=/dev/sda
append="devfs=nomount"
# This line often fixes L40 errors on bootup
# disk=/dev/discs/disc0/disc bios=0x80
default=ArchLinux
timeout=50
lba32
prompt
image=/boot/vmlinuz26
label=ArchLinux
root=/dev/sda4
initrd=/boot/kernel26.img
read-only
image=/boot/vmlinuz26archck
label=ArchFallback
root=/dev/sda4
initrd=/boot/kernel26-fallback.img
read-only
other=/dev/sda2
label=dos
# End of file
and here is my /etc/fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
tmpfs /tmp tmpfs defaults 0 0
usbfs /proc/bus/usb usbfs defaults 0 0
/dev/cdrom0 /mnt/cdrom iso9660 ro,user,noauto,unhide 0 0
/dev/cdrom1 /mnt/cdburn iso9660 rw,user,noauto,unhide 0 0
/dev/sda1 /mnt/usbdrive vfat defaults,user,noauto 0 0
/dev/sdb2 /mnt/ipod vfat noatime,noauto,user,umask=000,quiet,exec 0 0
/dev/sdc1 /mnt/camera vfat defaults,noauto,user 0 0
/dev/sda3 swap swap defaults 0 0
/dev/sda4 / ext3 defaults 0 1
any help would be very much appreciated.
Last edited by efourseven (2009-06-18 02:39:08)

[Project] Kernel26-ideapad

Hey everyone,
Just announcing the release of the first package in the -ideapad series on the AUR. This kernel is optimized for the Lenovo Ideapad Y-series laptops (specifically Y560 at the moment, but works with all Y), which had no special builds before now. This package is currently based almost entirely off of graysky's kernel26-ck package, using his PKGBUILD with custom entries and a custom x86_64 .config file. It uses the full ck* patchset along with optionally using BFQ as well. I will be working on tweaking it down in the following weeks so that it only includes the needed drivers (mainly pulling out intel/nvidia/apple-specific drivers at the moment). If you have an Ideapad Y series, or like model, that you would like support for, please let me know here or in the comments on the package's AUR page.
AUR page is located here
Wiki entry to consult is the kernel26-ck wiki article, since this package is based off of that one (though I do not maintain a repository of precompiled kernels like graysky)
Okay, three more things:
1) This package will only provide an improved experience for x86_64 users--I do not optimize for i686 since the Y5xx laptops have no reason to be operating in that environment. Please use graysky's kernel26-ck* packages for your architecture if you'd like i686.
2) The package is designed to be built on a system using the AMD Catalyst drivers, and so I kept the initcpio for this. If you use the open-source radeon driver, I'd be more than happy to make a separate package with all the drivers built into the kernel itself, which will speed up the boot process even more. Please PM, email, or notify me on the package page in the AUR.
3) Do NOT enable the localmodconfig option in the packagebuild! The drivers you need are already included, and localmodconfig will omit a few drivers that aren't loaded at boot time. I use modprobe_db scripts (also by graysky) to build for this laptop, and it includes only drivers that are used on these systems (with a few extras in case the functionality is needed, like peripherals).
If you'd like another driver compiled in, let me know, I only include the needed drivers (for example, if you want full disk encryption I will need to enable it).
This package includes the latest BFS and ck patches as the kernel26-ck package, and uses a few other options: core2 instead of generic cpu, 1000mhz timer, zero-latency desktop, and several peripheral drivers.
-Admiralspark
Last edited by admiralspark (2011-06-23 02:34:24)

admiralspark wrote:tribhuvanesh:
First, I'll need the information in the above post: 32 or 64 bit, what version of catalyst and xorg (pacman -Qi xorg-server etc.). Note that fglrx and Gnome3 are still not working if that's what you're using.
I'm using a 64-bit install.
catalyst-generator - 11.6-1 (I tried the alternatives, but ended up with the same problem)
xorg-server - 1.10.3-1
I haven't yet bothered trying to install gnome or any other desktop environment for that matter.
First, you must boot with the 'nomodeset' option. The drivers will not work without that.
Yes, I did specify that in the kernel line of my /boot/grub/menu.lst
Second, are you sure catalyst compiled correctly? Do you have the autofglrx daemon first in your daemons array in rc.conf? (This is provided by the catalyst-daemon package, which you will find useful to have). It will compile the fgrlx module every time you reboot into a new kernel, which is nice to have and may help as well.
I've already tried compiling the catalyst twice. Eventually, I resorted to adding the main catalyst repositories in /etc/pacman.conf. Just tried the catalyst-daemon right now, but, over and over again, I've faced the same problem.
Third, are you running aticonfig --initial as the root user, not with sudo? And try running startx as root user as well, you should get twm or something to show up (a few terminals).
Fourth, here is my /etc/X11/xorg.conf which should technically work for you. No need to use aticonfig --initial with this.
My /etc/X11/xorg.conf was exactly the same, except for the - Option "UseInternalAGPGart" "no", which was missing. I replaced your file with mine, and again, the same error.
This is a start. I don't want to get into the harder stuff without more input on what you have first, otherwise I may get sidetracked.
EDIT: if you need clearer, cleaner instructions I can rewrite, but it's 1:30AM here so I'm off to bed for now.
Here's my /var/log/Xorg.0.log which for some reason seems to throw the same error each and every time.
For some reason, its always the Failed to load module "intel" (module does not exist, 0). But then, the intel module cant work as stand-alone. To add to the hysteria, it conflicts with catalyst and throws an error when it doesn't exist.
Oh no, I must say, I've been able to clearly follow your instructions.

Installation of Archboot: cannot resolve "kernel26-lts"

Hi,
I'm trying to install the latest Archboot. My existing host is using kernel 3.1.9-2 but Archboot seems to need kernel26. When I try to install it with pacman, it says:
warning: cannot resolve "kernel26-lts>=2.6.32.46-1", a dependency of "archboot"
warning: cannot resolve "kerenl26-lts>=2.6.32", a dependency of "noveau-drm-lts"
warning: cannot resolve "kernel26-lts<2.6.33", a dependency of "nouveau-drm-lts"
Do I really need to install kernel26 items? I'm hesitant because I really like the nice minimal system I have at the moment.
tia!

kernel26-lts has been renamed to linux-lts when Linux 3.0 became LTS, so your ArchBoot must be out of date...
In fact "pacman -Si archboot | grep kernel" returns nothing.
However:
$ pacman -Si nouveau-drm-lts | grep kernel
Depends On : kernel26-lts>=2.6.32 kernel26-lts<2.6.33
This package is orphan, which must be the reason why it's not up to date.
I suppose you could use abs to rebuild nouveau-drm-lts against kernel 3.0... Maybe .

Kernel26 upradging problem

Hi, I have a small problem with upradging kernel26 to newest version.
I typed pacman -S kernel26
But after downloading file there is an error like this:
checking package integrity... done.
loading package data... done.
checking for file conflicts...
error: the following file conflicts were found:
kernel26: /lib/modules/2.6.16-ARCH/modules.alias: exists in filesystem
kernel26: /lib/modules/2.6.16-ARCH/modules.ccwmap: exists in filesystem
kernel26: /lib/modules/2.6.16-ARCH/modules.dep: exists in filesystem
kernel26: /lib/modules/2.6.16-ARCH/modules.ieee1394map: exists in filesystem
kernel26: /lib/modules/2.6.16-ARCH/modules.inputmap: exists in filesystem
kernel26: /lib/modules/2.6.16-ARCH/modules.isapnpmap: exists in filesystem
kernel26: /lib/modules/2.6.16-ARCH/modules.ofmap: exists in filesystem
kernel26: /lib/modules/2.6.16-ARCH/modules.pcimap: exists in filesystem
kernel26: /lib/modules/2.6.16-ARCH/modules.seriomap: exists in filesystem
kernel26: /lib/modules/2.6.16-ARCH/modules.symbols: exists in filesystem
kernel26: /lib/modules/2.6.16-ARCH/modules.usbmap: exists in filesystem
errors occurred, no packages were upgraded.
What should I do with it??
Regards

Oi. Umm, milosh - it seems you installed a kernel without the aid of pacman. Because of that, pacman does not control those files and cannot overwrite them. If you wish to overwrite them (make sure this is what you want), you need to use "pacman -Sf kernel26" to force pacman to install over those files.
Again, be careful, and be sure this is what you want.

IBM x3950 Fails to boot the instalation disc

So I got hold of this IBM x3950 server with quad Xeon 7150N 's, 2 SAS drives in RAID, it currently runs Debian Wheezy, as a temporarily place holder, and I can't boot the arch installation medium, I ckecked the CD it runs fine on 2 other computers.
While it boots Debian I still get the
MP-BIOS bug: 8254 timer not connected to IO-APIC
error like below.
So this is the messages during the boot process on arch:
Loading boot/x86_64/vmlinuz......
Loading boot/x86_64/archiso.img...........................ready.
Probing EDD (edd=off to disabl)... ok
early console in decompress_kernel
Decompressing Linux... Parsing ELF... done.
Booting the kernel
[ 0.04999] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
Then the console is cleared and this pops up:
[ 4.972054] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, reminder is 130
[ 4.972233] Raw EDID:
[ 4.972342] o00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
[ 4.972469] off ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 4.972596] off ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 4.972723] off ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 4.972850] off ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 4.972976] off ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 4.973116] off ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 4.973245] off ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 5.004910] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, reminder is 130
[ 5.005089] Raw EDID:
[ 5.005198] o00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
[ 5.005325] off ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 5.005452] off ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 5.005579] off ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 5.005705] off ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 5.005832] off ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 5.005959] off ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 5.006086] off ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 5.006218] [drm:radeon_vga_detect] *ERROR* VGA-1: probed a monitor but no|invalid EDID
:: running hook [memdisk]
:: running hook [archiso]
:: running hook [archiso_loop_mnt]
:: running hook [archiso_pxe_common]
:: running hook [archiso_pxe_nbd]
:: running hook [archiso_pxe_http]
:: running hook [archiso_pxe_nfs]
:: Mounting '/dev/disk/by-label/ARCH_201305' to '/run/archiso/bootmnt'
[ 6.000013] Calgary: DMA error on Calgary PHB 0x0, 0x02020000@CSR 0x00018000@PLSSR
At this point the system hangs and spouts gibberish to the console and then the system shuts down and I get a red LED on the server, indicating there's critical logs available in the system log. Unfortunately I can't find anything of relevance in there.
For odd reasons when I first boot the Arch CD and after it crashes ( the system does not physically shut down, the fans and everything still spin, apparently it always does that when it's plugged in to the power socket ) and then proceed to boot my Debian installation I get identical errors and it crashes. I have to unplug it for a minute or two and then it will boot just fine.
It's the first time I had an encounter like this so help would be much appreciated. Posting this late in the night so I'll have a look at it later tomorrow.

Hi Paolo,
Thks for the reply. I have made some success since I posted. I actually downloaded Ubuntu & created a boot up disk. I have managed to successfully load this alongside the Vista (which doesn't work) & everything seems OK - so all I can say is that it must be somekind of s/w issue or perhaps damaged sectors or something on the Vista install.
I am happy to use Ubuntu - it will be interesting to see if I have to do anymore reformats in future...
Thks, John

Can't boot installation cd on my Macbook pro 8.1

Hi everybody,
I am trying to install archlinux for dualboot with os x. The problem is that no matter what I do I just can't boot the installation CD. First I come to the normal screen where I can choose to boot archlinux, boot existing os, do memtest etc. If I choose boot archlinux I get an output similar to this: (I am trying to copy the text by hand from my macbook to another computer)
Loading /arch/boot/x86_64/vmlinux.....
Loading /arch/boot/x86_64/archiso.img.....................ready.
Probing EDD (edd=off to disable).... ok
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
[ 4.261364] i8042: No controller found
:: Starting udevd...
done.
:: Running hook [udev]
:: Triggering uevents...[ 5.859626] ata2.01: failed to resume link (SControl0)
[ 5.859749] ata1.01: failed to resume link (SControl0)
[ 12.352939] ata2.01: failed to resume link (SControl0)
[ 18.866288] ata2.01: failed to resume link (SControl0)
[ 25.379640] ata2.01: failed to resume link (SControl0)
done.
:: Running Hook [memdisk]
:: Running Hook [archiso]
:: Running Hook [archiso_pxe_nbd]
:: Running Hook [archiso_loop_mnt]
:: Waiting for boot device...
Waiting 30 seconds for device /dev/disk/by-label/ARCH_201108 ...
ERROR: boot device didn't show up after 30 seconds..
And I get the same result no matter what i do. I have tried it on two different harddrives (both newly formatted and with a fresh install of OS X 10.6.6 fully updated), with or without premade partitions of many different kinds. I have made like 5 different cd:s and dvd:s and I now that at least one of them have worked on another macbook of the same model.
Please could someone help me because I have no idea what I possibly can be doing wrong.
Last edited by gkarreskog (2011-08-29 14:35:44)

groundnuty wrote:
had the same problem today.
My observations are:
1) I tried that with brand new mac pro 8.1 - OSX just as I got it from apple. All worked, arch boot up and I was able to begin installation. eth0 worked as well.
2) I tried it again few days later and got the same problem as you described/pasted. meanwhile I downloaded upgrade from apple - I guess that is what causes the problem. Basicly cd is not detected at all, so /dev/disk/by-label/ARCH_201108 obviously is not there.
Anyway the solution to this was quite easy - sice in initramfs you can detect usb keys:
1) Copy all the files from your arch-install cd to some usb key (just cp. no need to format/dd etc)
2) try to boot from the cd like before untill you arrive at ramfs
3) plug your usb key and hope it will get detected
4) then do
ln -s /dev/<usb key> /dev/disk/by-label/ARCH_201108
5) logout (exit)
and you have your arch booting
Ho
I'm ok with that procedure.
But now i'm on archlinux installer, how to make an proper installation of grub, that work?
Because all of the things I tried didn't worked.
Thanks !

[Unsolved] Kernel linux 3.8.4-1 fails with fsck boot error on raid 0

The stock linux-3.8.4-1 (x86_64) fails to boot with the following unrecoverable error:
Loading ../initramfs-linix.img......ready.
Probing EDD (edd=off to disable)... ok
early console in decompress_kernel
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents...
Waiting 10 seconds for device /dev/md127 ...
:: performing fsck on '/dev/md127' ...
fsck.ext2: Invalid argument while trying to open /dev/md127
/dev/md127:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
ERROR: fsck failed on '/dev/md127'
:: mounting '/dev/md127' on real root
mount: you must specify the filesystem type
You are now being dropped into an emergancy shell.
sh. can't access tty; job control turned off
[rootfs /]#
My hooks are:
HOOKS="base udev autodetect modconf block mdadm_udev filesystems keyboard fsck"
I am however able to boot the linux-lts & my own custom kernels. Custom kernel is built from the abs linux package.
The / partition is on a raid 0 with an ext4 filesystem. fsck -f /dev/md127 comes back clean & the raid & two hard drives are healthy.
Last edited by straykat (2013-07-11 09:27:45)

straykat wrote:
xanb,
For sanity to prevail, I am going to suggest the following:
Back up your data
Remove the RAIDs from your 2 linux hard drives. The Arch RAID wiki has instructions on this or (my prefered method) wipe your two linux drives with dd. If you are not sure on dd "Parted Magic" has a GUI for it.
Create a new partition table on both of your linux hard drives.
Partition your 2 linux hard drives as follows;
/dev/sdb1 as / (root) with ext4 fs
/dev/sdb2 as swap
/dev/sdc1 as /home with ext4 fs.
Reinstall Arch Linux on / (/dev/sdb1)
I would also recommend reading up in the Arch wiki, Kernel wiki etc on RAID & decide why you would use it on your system & which one would give you any benefit with your current hardware set up. Also learn more on how to create & maintain a RAID on an Arch system.
Keep in mind that KISS is always the way to go with any computer system as complexity will always increase the amount of mistakes & gotchas.
No. I don't want to behave as ostrich, hide the head ;-) This is my configuration, this is want I want. If archlinux fails, we have a bug. Another question is if the triage of the bug is difficult. No all bugs are good for triagging, but it's real life. If always we change the configuration, we will never detect new bugs.
Keep in mind that I don't want to blame, it's always "good force" comments.
Regards,
Xan.

Problem to locate boot device

I've just recieved and assemblied it. After downloading the favorite distro we all know and love I was presenterd with an error in finding the boot device. I've searched around for a solution but every one I find seem to not work as expected.
I've taken the time to write down the boot output in hope that anyone can identify a working solution. I'm using a CD as my boot device.
Loading /arch/boot/x86_64/vmlinuz.....
Loading /arch/boot/x86_64/archiso.img............. ready.
Probing EDD (edd=off to disable)... ok
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
:: Starting udevd...
done.
:: Running Hook [udev]
:: Triggering uevents...[ 2.029469] xhci_hcd 000:00:14.0: Failed to enable MSI-X
[ 3.524615] ata1.01: failed to resume link (SControl 0)
[ 3.534605] ata2.01: failed to resume link (SControl 0)
[ 10.029839] ata2.01: failed to resume link (SControl 0)
[ 16.545099] ata2.01: failed to resume link (SControl 0)
[ 23.060307] ata2.01: failed to resume link (SControl 0)
done.
:: Running Hook [memdisk]
:: Running Hook [archiso]
:: Running Hook [archiso_pxe_nbd]
:: Running Hook [arch_loop_mnt]
:: Waiting for boot device...
Waiting 30 seconds for device /dev/disk/by-label/ARCH_201108 ...
ERROR: boot device didn't show up after 30 seconds...
Falling back to interactive prompt
You can try to fix the problem manually, log out when you are finished
sh: can't access tty; job control turned off
[ramfs /]#
I've tried to locate the archiso by creating a symlink to /dev/sd* but no effect. If someone can assist me finding a solution, I would be very appreciative.

Thank you for your input. I tried with an USB install, and renamed the USB drive to ARCH_201108 and it booted successfully. But I think this was kind of odd, since I can't remember stumbling upon errors like these when I've tried to install Arch before. Is this something recent?

[SOLVED] ERROR: Unable to find root device '/dev/sda3'

Earlier I updated the kernel to my arch system and found this error while trying to boot. I hate to post this because there are so many topics like it, but I've been looking for hours for a solution to this problem and can't find one.
Here is the output:
Booting 'Arch Linux'
root (hd0,1)
Filesystem type is ext2fs, partition type 0x83
kernet /vmlinuz-linux root=/dev/sda3 ro
[Linux-bzImage, setup=0x4200, size=0x2ff2d0]
initrd /initrd @ 0xfd17000, 0x2c878c bytes]
Probing EDD (edd=off to disable)... ok
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
:: Starting udevd...
done.
Waiting 10 seconds for device /dev/sda3 ...
ERROR: device '/dev/sda3' not found. skipping fsck.
ERROR: Unable to find root device '/dev/sda3'.
You are being dropped to a recovery shell
type 'exit' to try and continue booting
sh: can't access tty; job control turned off
My partition layout is like this:
swap: /dev/sda1
boot: /dev/sda2
root: /dev/sda3
extended: /dev/sda4
home: /dev/sda5
I have two hard drives, but i'm sure /dev/sda is the one with my OS.
Here are some things I've tried:
This was at the very bottom of the pacman wiki
# mkdir /mnt/arch
# mount /dev/sdaX /mnt/arch (your root partition)
# cd /mnt/arch
# mount -t proc proc proc/
# mount -t sysfs sys sys/
# mount -o bind /dev dev/
# mount /dev/sdaX boot/ (your /boot partition) #This step is not needed if you do not have a separate boot partition
# chroot .
# pacman -Syu udev mkinitcpio
# mkinitcpio -p linux
I've also tried performing the above, downgrading the kernel, updating my mirrorlist, reinstalling the kernel, and rebooting as mentioned here.
I've alsa tried a few other things that I've read, but can no longer remember.
Any help would be greatly appreciated! Thanks.
Last edited by colton7909 (2012-05-25 02:09:36)

Thank colton
Same problem here, but on a mac book (not mine eyh )
So, for those how have the problem (or need a live usb for mac or uefi systems),
1) with a 32bits system
- download gparted live cd
- use it for the step 3
2) with a 64bits system:
- you need the gparted live cd too: mount it and copy the EFI directory somewhere; then umount it;
- download a 64bits system (system rescue cd, as colton said is enough, follow the instructions for installation on their website first);
- mount you live usb, install the 64bits system;
- copy EFI system on the key
- edit the grub.cfg in EFI/boot/ , add the following before the other entries:
menuentry "System Rescue" {
set gfxpayload=keep
linux /syslinux/altker64 nomodeset efi
initrd /syslinux/initram.igz
3) repairing...
- boot the broken computer with the live usb
- mount the partition on which your system is (e.g. /dev/sda1 on /mnt)
- chroot it, init the system as needed (mount /dev, /proc, etc. the easier way is using init scripts)
% chroot /mnt /bin/bash
% /etc/rc.sysinit
% mkinitcpio -p linux

[Solved]Wont boot after installing syslinux; unknown filesystem 'swap'

After installing syslinux to be my boot manager I can no longer boot into Arch, I can however boot into Windows 7. When I try to boot into Arch I get the following error.
Loading ../vmlinuz-linux......
Loading ../initramfs-linux.img......ready.
Probing EDD (edd=off to disable)... ok
Decompressing Linux... Parsing ELF... done
Booting the kernel.
:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents...
:: performing fsck on '/dev/sda3'
fsck: fsck.swap: not found
fsck: error 2 while executing fsck.swap for /dev/sda3
ERROR: fsck failed on 'dev/sda3'
:: mounting '/dev/sda3' on real root
mount: unknown filesystem type 'swap'
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs /]#
What's going on?
Last edited by slughappy1 (2012-07-05 22:50:35)

loafer wrote:Can you post your syslinux.cfg please.
Surely
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
# * poweroff.com - shutdown the system
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples
DEFAULT arch
PROMPT 1 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 ro
INITRD ../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 ro
INITRD ../initramfs-linux-fallback.img
LABEL windows
MENU LABEL Windows7
COM32 chain.c32
APPEND hd0 1
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL off
MENU LABEL Power Off
COMBOOT poweroff.com

Arch x86_64 won't boot, but i686 will. Live USB and HDD.

To be more succinct, what could cause 64 bit arch not to boot when 32 bit arch boots fine on a non-UEFI system that supports 64 bit, when all other variables are constant?
My first response seeing this post would be to immediately assume the noob (me) posting this doesn't know the difference between a 32 and 64 bit system. However, "ubuntu-14.04.1-desktop-amd64.iso" (latest 64 bit ubuntu iso) boots from live USB and installs without error. It also came preinstalled with Windows 7 (64 bit), so I'm relatively sure it supports x86_64.
I wrote "archlinux-2014.08.01-dual.iso" (MD5 verified) to my USB. Selecting i686 boots fine. Selecting x86_64 restarts my system, eventually sending me back to the arch live menu after it posts.
Upon recommendation by a WonderWoofy on reddit, I tried to install arch x86_64 by bootstrapping and chrooting from the 64 bit ubuntu live usb. I ended up with same problem, where attempting to load arch reboots my system immediately.
Right now, I'm assuming it's the same issue booting from the live usb (arch iso) and from the arch installation on my hard drive, since they seem identical to me. I haven't tried recreating the install for i686 to see if it works (mainly because it's late -- if it'll help I'll do it upon suggestion).
Here's the only text that shows once I attempt to boot into arch. This is from the hard drive and using syslinux (which is pointed at my root partition on sda -- I don't have a boot partition).
Loading ../vmlinuz-linux... ok
Loading ../initramfs-linux.img...ok
Probing EDD (edd=off to disable)... ok
Which doesn't look like it's messing up anywhere...
And of course I'm a noob so go easy on me x)
UPDATE: I found this thread but I'm not seeing his error message, so I'm not sure what to do.
Last edited by SirProudNoob (2014-08-13 02:54:24)

It's an Intel Core 2 Quad processor. Are there any more diagnostic commands that would be helpful? I didn't see anything else in util-linux that might help...
Here's the output for "lscpu":
ubuntu@ubuntu:~$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 23
Stepping: 10
CPU MHz: 2327.537
BogoMIPS: 4655.07
L1d cache: 32K
L1i cache: 32K
L2 cache: 2048K
NUMA node0 CPU(s): 0-3

Booting the kernel freezes

Hello,
I'm trying to install Arch Linux on an old computer (AMD Athlon 900MHz) but the system freezes at boot. All I can see on screen is:
Loading boot/i686/vmlinuz.......
Loading boot/i686/archiso.img.....................................ready
Probing EDD (edd=off to disable)... ok
Decompressing Linux... Parsing ELF... done.
Booting the kernel
and then freezes. I've tried adding "nomodeset noacpi noapic nolapic acpi=off loglevel=7 debug" with no success and no debug information.
This computer is running a Linux 2.6.32 kernel right now and I wanted to update it.
Any ideas?
Thanks in advance

Should I try net install or anything like that?
Are you using latest install iso?
If so, it is already net install, it only allows you to install if you have an internet connection and will install all packages from arch servers.
The specs are more than the minimum requirements, at lest for what i've been reading arrond. The only problem i see is the PATA hdd, because latest arch kernel's don't support it anymore, there is a workarround for it at least
pcie_aspm=force
The other thing i don't know is if your VIA chipset is still supported in new kernels!
Last edited by s1ln7m4s7r (2013-03-29 16:58:10)

Net_nfs4 has no build function

Hello, I don't understood how can I build net_nfs4 hook for Diskless_System NFSv4
# sed s/nfsmount/mount.nfs4/ "$root/usr/lib/initcpio/hooks/net" | tee "$root/usr/lib/initcpio/hooks/net_nfs4"
after I copied from "$root/usr/lib/initcpio/hooks/{net,net_nfs4} to $root/usr/lib/initcpio/install/
after build from new mkinitcpio.conf kernel, and get this error.
==> ERROR: Hook /usr/lib/initcpio/install/net_nfs4 has no build function
And this on remote machine. What I did wrongly?
UNDI data segment at 9C59 leu 1830
Getting cached packet 01 02 03
My IP address seems to be 0AO0007E 10.0.0.126
ip=10.0.0.126:10.0.0.1:10.0.0.1:255.255.255.0
BOOTIF=01-08-00-27-eO-a0-22
SYSUUID=4c53f3dd-0b02-4047-abd2-b8639cc5a48e TFTP prefix: /
Trying to load: pxe1inux.cfg/defauIt
Loading vmlinuz-1inux......
Load ing initramfs-linux.img.....ready.
Probing EDD (edd=off to disable)... ok ear iy console in decompress_kerne1
Decompressing Linux... Parsing ELF... done. Booting the kernel.
[ 0.0000001 tsc: Fast TSC calibration faile
:: running early hook [udevl :: running hook [udevl : : Triggering ueuents. . .
ERROR: device '' not found. Skipping fsck. ERROR: Unable to find root device '' .
You are being dropped to a recovery shell
Type ' exit' to try and continue booting sh: can't access tty; job control turned off [rootfs /I#
Thanks, Geo...

Did you look at the file you created? I'm no expert wrt initcpio, but from what I've seen only the files in initcpio/install have a build function.

Kernel26 2.6.26.3-1: Probing EDD [SOLVED, like]

Similar Messages

Maybe you are looking for