[Solved] Grub error when booting...

Today I decided to try out Archlinux everything worked fine until the reboot.. Grub doesn't seem to work as intended, grub just kept posting:
GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB
nothing but "GRUB" came up.
My menu.lst:
default 0
timeout 3
color light-blue/black light-cyan/blue
title Arch Linux
root (hd0,0)
kernel /vmlinuz26 root=/dev/sda3 ro vga=773
initrd /kernel26.img
Title Arch Linux Fallback
root (hd0,0)
kernel /vmlinuz root=/dev/sda3 ro vga=773
initrd /kernel26-fallback.img
version: 0.8beta2
I haven't found any threads about it, if there's any i'm sorry for bringing up a new one.
any suggests?
Last edited by Neko-san (2007-03-12 19:16:41)

SleepingGiant08 wrote:see this http://www.gentoo.org/doc/en/grub-error-guide.xml
scroll down to Error 7...
oohh.. there it is, I guess I didn't look enough thanks tho :)
vacant wrote:
GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB
Maybe you should start a poll "Vote for the most useless linux error message" ;)
True, not that good error message ^^
This is how I did it:
boot: arch root=/dev/sda3
grub
root (hd0,0)
setup (hd0)
quit
reboot
Last edited by Neko-san (2007-03-12 20:33:30)

Similar Messages

[Solved] "Version Magic" error when booting with m

Hi, I compiled kernel 2.6.16.18 and I receive the following error when booting:
ide_core: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
amd74xx: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
generic: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
ide_disk: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
cdrom: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
ide_cd: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
ide_floppy: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
sd_mod: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
libata: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
sata_nv: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
jbd: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
ext3: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
jfs: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
reiserfs: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
xfs: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
I compiled my kernel with this line:
# make -s clean bzImage modules modules_install
Any ideas?

Ok, I fixed it.
When doing mkinitrd auto it would make an initrd image from the modules at /lib/modules/2.6.16-ARCH when it had to do it from /lib/modules/2.6.16.18-ARCH
I fixed it with
mkinitrd kernel_version=2.6.16.18-ARCH
Also my menu.lst was wrong, a new image was created under the name of
initrd-2.6.16.18-ARCH.img.
My menu.lst pointed to initrd26.img. I didn't change it before because I didn't know, someone should update the wiki article about compiling the kernel from source.

Adobe error when booting

Hi
My MacBook Pro running Mountain Lion is logging the following Adobe error when booting. I don't know which program from Adobe it comes from. I have Flash and Photoshop installed.
It takes my Mac 11 seconds of boot time to generate this error every time I boot. I would like to get rid of the program causing it.
Frank
My log:
26/09/12 07.27.16,000 kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=264[ksadmin] clearing CS_VALID
26/09/12 07.27.27,665 osascript[276]: Error loading /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: dlopen(/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types, 262): no suitable image found. Did find:
          /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: no matching architecture in universal wrapper
26/09/12 07.27.44,484 osascript[280]: Error loading /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: dlopen(/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types, 262): no suitable image found. Did find:
          /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: no matching architecture in universal wrapper
26/09/12 07.27.46,308 osascript[281]: Error loading /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: dlopen(/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types, 262): no suitable image found. Did find:
          /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: no matching architecture in universal wrapper
26/09/12 07.27.46,401 osascript[282]: Error loading /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: dlopen(/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types, 262): no suitable image found. Did find:
          /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: no matching architecture in universal wrapper
26/09/12 07.27.46,753 osascript[283]: Error loading /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: dlopen(/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types, 262): no suitable image found. Did find:
          /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: no matching architecture in universal wrapper
26/09/12 07.27.46,890 genatsdb[251]: *GENATSDB* FontObjects generated = 737
26/09/12 07.27.46,927 osascript[284]: Error loading /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: dlopen(/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types, 262): no suitable image found. Did find:
          /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: no matching architecture in universal wrapper
26/09/12 07.27.46,983 osascript[285]: Error loading /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: dlopen(/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types, 262): no suitable image found. Did find:
          /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: no matching architecture in universal wrapper

First, in System Preferences -> Users & Groups -> Login items, look for anything Adobe in the list of items and remove it. Then your Mac will not attempt to load anything Adobe during boot-up or log-in anymore, but boot much faster again.
Then see if problems persist when starting your Adobe apps. If so, uninstall them completely (!!! - usually, there are files left over under Applications and in Application Support in the Libraries - remove those manually), then re-install these apps fresh.

I continue to have an Adobe error when booting up my computer. It reads: this specific module could not be found. \AppData\local\diagnostics\tlfpizv.dll

I continue to have an Adobe error when booting up my computer. It reads: this specific module could not be found. \AppData\local\diagnostics\tlfpizv.dll
Please tell me there is a fix that does not involve buying a computer clean sweep program.

Hi brigitta2,
You might be getting the error message because of any of the following reasons:
.dll files are corrupt or missing
Attack of malware or other spyware
Incorrect installation of applications
Damaged Windows registry
Old Windows device drivers that need to be updated
The problem can be sorted if you know the exact reason behind the same. Please let me know the exact error message that appears on your screen.
If the issue is with damaged files then you might need to replace them or if it is a system issue, then please take your laptop to an expert who can deal with system issues.
Regards,
Anubha

[SOLVED] Grub error 18 - cannot boot to Windows

Earlier today I tried to install Arch 64bit (I had 32bit earlier) with kdemod to test new KDE4.2. However, after installation I could not boot neither Arch nor Windows. Grub appeared, but every single option gave me an error. I can't remember anymore which error it was, but It doesn't matter anymore. I thought I had made a really stupid and basic mistake while installing, I just didn't know what.
I wanted to test KDE4.2 so much so I installed Kubuntu (yeah, this topic is not related to Arch Linux, I hope that somebody can help me though, move this topic to somewhere else if it doesn't belong here ). Installation was fine, booting to Kubuntu was fine (and upgrading to KDE4.2 was fine), but booting to Windows was not. It gave me a following error:
Error 18: Selected cylinder exceeds maximum supported by BIOS
I googled a bit and found this: http://wiki.linuxquestions.org/wiki/GRUB#Error_18 I reinstalled Kubuntu using /dev/sdb1 as /boot and /dev/sdb2 as / (/dev/sdb3 is windows and /dev/sdb4 is my game partition, ntfs). Before this I had /dev/sdb1 as / and /dev/sdb2 as swap (now I have no swap at all, my 4GB RAM should be enough). The only difference was that at first grub gave me error 15 (I fixed it with Kubuntu LiveCD). After that - no difference.
I need Windows for playing. That's why it's very important that I can use it. [SOLVED] In addition, I should say that /dev/sda is a separated hard drive which is encrypted with Truecrypt. (I said this because I think that Kubuntu tried to install grub on (hd0)...) When I tried to mount this hard drive with Kubuntu, it couldn't do it. I wanted to test mounting on Windows to check if it is just Kubuntu's problem. If not, I'm fucked because this hard drive contains VERY VERY VERY IMPORTANT files. [/SOLVED]
I really need help, please. If somebody can help me, (s)he is my hero.
Last edited by Exitium (2009-01-29 14:42:32)

Oops, I forgot:
menu.lst:
(Yup, a lot of comments, Ubuntu style)
# 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 10
## 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=e85e83e5-0f7c-419e-8cad-1fe5d9128e8f ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=504fab5b-7bb6-4b20-af58-83677386de37
## 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 8.10, kernel 2.6.27-11-generic
uuid 504fab5b-7bb6-4b20-af58-83677386de37
kernel /vmlinuz-2.6.27-11-generic root=UUID=e85e83e5-0f7c-419e-8cad-1fe5d9128e8f ro quiet splash
initrd /initrd.img-2.6.27-11-generic
quiet
title Ubuntu 8.10, kernel 2.6.27-11-generic (recovery mode)
uuid 504fab5b-7bb6-4b20-af58-83677386de37
kernel /vmlinuz-2.6.27-11-generic root=UUID=e85e83e5-0f7c-419e-8cad-1fe5d9128e8f ro single
initrd /initrd.img-2.6.27-11-generic
title Ubuntu 8.10, memtest86+
uuid 504fab5b-7bb6-4b20-af58-83677386de37
kernel /memtest86+.bin
quiet
title Wintoosa
root (hd1,2)
savedefault
makeactive
map (hd0) (hd1)
map (hd1) (hd0)
chainloader +1
fdisk -l
(Note: These results are mainly in Finnish. It could be hard to you to read it... But whatever... I'll translate these only if necessary)
Levy /dev/sda: 640.1 Gt, 640135028736 tavua
255 päätä, 63 sektoria/ura, 77825 sylinteriä
Yksiköt = 16065 * 512 = 8225280 -tavuiset sylinterit
Levyn tunniste: 0xcc5d88e2
Laite Käynn Alku Loppu Lohkot Id Järjestelmä
/dev/sda1 * 244091 485122 1936074870+ b8 BSDI sivutus
Osion 1 loppu ei ole sylinterin rajalla.
/dev/sda2 176430 394864 1754572509+ 43 Tuntematon
Osion 2 loppu ei ole sylinterin rajalla.
/dev/sda3 177329 413105 1893868925 29 Tuntematon
Osion 3 loppu ei ole sylinterin rajalla.
/dev/sda4 57435 309703 2026342066 5c Priam Edisk
Osion 4 loppu ei ole sylinterin rajalla.
Osiotaulumerkinnät eivät ole levyjärjestyksessä
Levy /dev/sdb: 500.1 Gt, 500107862016 tavua
255 päätä, 63 sektoria/ura, 60801 sylinteriä
Yksiköt = 16065 * 512 = 8225280 -tavuiset sylinterit
Levyn tunniste: 0x0007a52a
Laite Käynn Alku Loppu Lohkot Id Järjestelmä
/dev/sdb1 1 128 1028128+ 83 Linux
/dev/sdb2 129 13185 104880352+ 83 Linux
/dev/sdb3 13186 26239 104856255 7 HPFS/NTFS
/dev/sdb4 26240 60801 277619265 7 HPFS/NTFS
Last edited by Exitium (2009-01-28 21:05:33)

[Solved] Grub Error 15 at boot on new install.

So I was trying to avoid asking for help, but I honestly can't see what's wrong with my new install of arch. I followed the beginner's guide all the way up to the part where you reboot and remove the liveCD. It all went swimmingly until I rebooted and got:
GRUB Loading stage1.5.
GRUB Loading, please wait...
Error 15
I don't know what's going on. Error 15 is supposedly "file not found," but I don't know what file it's looking for since I have a grub.cfg that I created from the steps posted on the guide. Any help is greatly appreciated.
--Wes
EDIT:
Just to be clear I followed the BIOS motherboard steps for GRUB.
Last edited by Wesman26 (2012-11-09 01:25:38)

Xacky wrote:Which instructions did you follow? This would normaly do it when chrooted (during install).
Wat your disk en partition lay-out?
-One or more harddisks?
-Partitions? Everything on / or separate /home /boot (/var)?
I'm following the beginner's guide instructions for a BIOS install. After chroot I used the following:
# pacman -S grub-bios
# grub-install --target=i386-pc --recheck --force --debug /dev/sdb
# cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo
# grub-mkconfig -o /boot/grub/grub.cfg
Aside from the warnings (that I think most people ignored) of a few files not existing during the installation of grub-bios, it all went fine. The harddrive is definitely sdb (fdisk -l shows sda as my windows drive, not to mention I just formatted and partitioned sdb). My partitions are laid out exactly as the guide tells me to (/ on /dev/sdb1 and /home on /dev/sdb2). They are the only partitions on sdb.
DSpider wrote:Lol... a full reinstall wasn't needed. This mentality is typical to a Windows user.
I don't appreciate your condescension. These forums have (up to this point) always been really helpful and friendly to me; just because I'm posting in the newbie corner doesn't mean I'm not familiar with linux, and even if I were unfamiliar with linux I would hope that you could show more respect and compassion for someone who needs help than to ostracize them and laugh about their problem. I posted here because I figured I didn't need to waste the time of the mods and users who offer help in the installation subforum with something that I assumed would be a trivial fix. I expected courteous, thoughtful responses. I was apparently wrong to assume.
I reinstalled because I didn't know what else to do, and figured that there might have been a chance that I made a mistake. Since your previous advice was literally getting me nowhere I figured the 10 minutes of my time reinstalling took up would be worth the potential of fixing my problem.
To answer your questions that are actually helpful:
I don't have grub installed on another drive and my drive and partition layout is detailed above. As for boot priority, it hasn't changed since I first installed linux in 2006 and it's worked ever since; I'm performing this operation to clear what was once a drive cluttered with a few other distros that I've abandoned since 2007 when I found Arch (yes I am actually that lazy).
Is it possible that my old installation of grub might have stayed on the drive even after I rid it of the old partitions (since it's stored in MBR)? If so does the installation of grub2 I'm performing not get rid of it?
Hope this helps,
--Wes
Last edited by Wesman26 (2012-11-08 20:53:27)

[SOLVED] Grub Error "Read or write outside of disk hd0"

Trying to install Arch Linux (as per client request) on an old Seagate Mirra Personal Server. I reflashed the bios to get rid of the Seagate modified ROM and put the standard, stock, VIA bios image on there. Everything boots fine, it boots windows fine. But when I install Arch Linux on the drive and try to boot, it errors out with
Booting...
GRUB Loading.
Welcome to GRUB!
error: attempt to read or write outside of disk 'hd0'.
Entering rescue mode...
grub rescue>
When I ran grub-install and grub-mkconfig during installation neither reported errors or warnings. I'm open to ideas but I need to fix this sooner rather later as this is for a client. A forum thread I found in regards to Ubuntu and grub error 18 said to run:
apt-get remove linux-server
apt-get install linux-386
under Ubuntu and then it would boot. I know Arch removed i386 support a few months ago but im finding it hard to believe that the error above is because of an architecture mismatch. Also I didnt think the CPU in this thing was that old. Hardware Info from the arch live cd says
CPU Vendor: Centaur
CPU Model: VIA Nehemiah
1 core, 64k L2 Cache, 32bit
the Mirra is from 2007 or so, so I expected i686 Arch to be just fine for it.
Ideas???
EDIT:
Wikipedia's Article: https://en.wikipedia.org/wiki/VIA_C3
States: "Additionally, it implemented the cmov instruction, making it a 686-class processor"
So it shouldn't be an issue of i386 vs i686, right?
Last edited by FathisAeril (2013-04-26 21:46:11)

Good morning to all of You.
Sorry for posting in a [SOLVED] thread but I find the info that I am about to add relevant and I am betting my vital organs that someone else might find it interesting too.
I did an upgrade last night on my Thinkpad 600E. I was not upgrading it for several days (2 weeks tops) as I lost my USB wifi card and had no internet access on this particular machine. So...
As always before upgrade I checked my rss reader for news and sure enough there was a very informative post from Allan (thanks Dude btw.) in there:
https://www.archlinux.org/news/binaries … ervention/
I did as I was told and upgraded in the indicated way. All was peachy till I rebooted to get new kernel to load. I was met with the mentioned error:
error: attempt to read or write outside of disk 'hd0'.
but the second part was slightly different.
Error: You need to load kernel first
SO since the error was different why am I posting here? Because even after Googling the whole error message this post was the first to come up in my search results so I am betting others will get here as well.
Solution? After an hour or so of fighting (I tried booting up from the Arch CD and fscking partitions, reinstalling / reconfiguring grub, downgrading grub-bios and grub-common packages and many many other things) I finally rebooted to the Arch cd, chrooted (for all those that do not know what that means I would like to recommend this link as chrooting is explained in it https://wiki.archlinux.org/index.php/Be … %27_Guide) to the installation and I have reinstalled the linux (kernel) package and redid the image with the:
mkinitcpio -p linux
and rebooted. Turns out that did the trick. Apparently something went wrong during the kernel upgrade. Possibly due to the changes explained in Allan's article. Reinstalling kernel / recreating image did the trick for me.
So if You are still wondering what am I doing here and why am I replying in this thread - the answer is - 99% search results from Google suggests that this error means incompatibility between bios and the hard drive AND there is nothing really out there that I found helpful in this case. I mean it could not be a bios / hdd incompatibility. This drive has been used in this machine for few years and it was running Arch since November 2012... so this just could not be the case. I am just giving a shout to all those that will get this error that there is another option too.
Kind regards. Thanks for reading. My apologies again for sticking my nose in.
Andrzej
Edit: Few months later the same error - fix does not work... Trying to figure it out...
Last edited by AndrzejL (2013-10-19 02:43:15)

Grub error - but booting just fine

I recently got an SSD. I moved my Arch setup to it, turned on "discard" in fstab, wiped my grub config (I might've even wiped my entire /boot folder but I don't remember - I've been dealing with this problem for about a month), reinstalled grub from pacman, and used os-prober to assist in re-building grub.cfg.
For some strange reason though, just before grub loads I seem to get 3 errors all saying the same thing - "File not found". It doesn't tell me anything other than that. When Arch is then selected from the boot menu, it re-states those 3 errors and says "Press any key to continue". Pressing any key doesn't seem to do anything, it just sits there for about 5 seconds, and then proceeds to boot normally as though nothing happened.
I would love to give more in-depth details as to what's wrong, but this is all I can provide. Currently I am not using grub to boot anything else - just Arch.

I get these three alerts on another box which dont run arch, id hazard a guess its grub not erroring but merely alerting you, IDK what the 3 missing files are, but i do know its not errors. I think its grub looking for certain files (maybe hardware specific files) and if they arent found grub continues to boot. This wont cause you any ill effects.

Imaq.dll error when boot up Windows

Hello,
I have a little Problem with Labview 8.6. After i installed the driverpack for the dvd, my Windows give my the error
Der Prozedureinsprungpunkt "ProgramFPGAs" wurde in DLL "IMAQ.dll" nicht gefunden.
my tranzlation
the entry point "ProgramFPGAs" is not found in the Dll " Imaq.dll
Labview start an run without problems, only this message at windows boot up is annoying.
was anyone a idea to fix the problem or atleast stop that messagebox
Thank you
Solved!
Go to Solution.

Hi DRhatje.
Good Morning and I hope your well today. Thanks for your post.
I think thats a pretty good translation, the error message I was thinking of can be found in the knowledgebase article below.
The suggested cause of the error is that the IMAQ.exe is set (by default) to start on startup. But if you don't have a framer grabber installed on the machine then you could well see this error. The solution is to remove the exe from the startup list on your system. The steps to do this is listed in the link below but in summary,
From the section in the screenshot you sent me you should be able to
select the "Selective Startup", then navigate to the "Startup" tab and
uncheck the IMAQBoot.exe.
If this reverts back to the default
settings on restart, this is probably an indicator that your Admin
Rights on this PC are limited.
I think that a quick way to check
this is to go to Start>Run and type "regedit". This is essentially a
more advanced way to manipulate similar settings, but if you don't have
Admin Rights on the PC then you would most probably be denied access.
In any case though, please ask one of your IT colleagues to use their
passwords and change this setting. It will get rid of the warning you
are seeing until you start using our Vision Hardware and need to
reactivate it.
Make sure you click on "Apply" before you exit this utility.
Why do I get "IMAQBoot.exe - Entry Point Not Found" error when I restart computer?
http://digital.ni.com/public.nsf/allkb/AD70B1036D5B950B8625752400578CFE?OpenDocument
This should at least remove the error message upon start up.
Please let me know how you get on and I hope this helps!
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!

[SOLVED] grub error on installation

Hello
Ive just attempted to install arch for the first time, however grub fails when attempting to install
/boot is on sda5 and root on sda6. both are logical partitions, the rest are primary. root is ext4, boot is ext2.
tty7 gives:
grub> device (hd0) /dev/sda
grub> root (hd0,4)
Filesystem type unknown, partition type 0x1
i ran a find /boot/grub/stage1 with the grub utility under a separate tty, but grub doesnt find it
i did find it manually under /mnt however. i also ran "root (hd0," in grub and it gives the same error for every partition
the automatically generated menu.lst looked like this:
# (0) Arch Linux
title Arch Linux
root (hd0,4)
kernel /vmlinuz-linux root=/dev/sda6 ro
initrd /initramfs-linux.img
# (1) Windows
title Windows
rootnoverify (hd0,0)
#makeactive
chainloader +1
I only uncommented the lines for windows dual boot. The rest looked correct so I left it.
From what Ive read on these forums and from googling, it seems as though the grub utility cannot read the partitions correctly. i used windows 7 diskpart to partition. Is this the reason that the install fails and should I be using something else to partition?
Last edited by neilzium (2011-12-17 15:34:54)

Hmm... you may have some issues with installing GRUB to a logical partition but then again the last time I tried to do something like this was a few years ago and I don't remember so well. Do you want the GRUB installation that you're working on now to be the main bootloader for your computer? If so then you could try installing GRUB to the MBR. It's not a fix, I know, but it would be an adequate workaround. Do you have a second linux distribution installed on /dev/sda3 and /dev/sda4? Then you could try using the bootloader on /dev/sda3 to boot arch on /dev/sda6.
As far as actually thinking about the problem and the error that you have and not just stalling for an answer by giving you random workarounds partition type 0x1 is FAT12 and doesn't look too much like a linux boot partition, which should be more like 0x83.
This thread is kinda interesting, not sure if it's the exact same problem but anyways, here
This is where I found the info for whether logical boot partitions work or not

[SOLVED] Grub Error 17 and other not so fun stuff

Booted today and greeted by grub error 17.
I booted from Arch Live CD
fdisk -l
looks ok
fdisk /dev/sdb
x,f,w nothing done, proper order
ok, let's chroot my install and install grub
mount /dev/sdb1 /mnt
unknown filesystem type, doh
mount -t ext4 /dev/sdb1 /mnt
nope
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
(aren't you trying to mount an extended partition,
instead of some logical partition inside?)
In some cases useful info is found in syslog - try
dmesg | tail
dmesg | tail
attempt to access beyond end of device
sdb1: rw=0, want=4, limit=2
EXT4-fs: unable to read superblock
attempt to access beyond end of device
sdb1: rw=0, want=4, limit=2
EXT4-fs: unable to read superblock
time to fsck ?
Last edited by bloodniece (2009-10-04 15:11:12)

bloodniece wrote:
I fixed it thanks to testdisk.
When I initially set this install of Arch up I used a whole disk in 2 partitions: / and swap. A grub error 17 led me to believe the partition table was fuxored. Fdisk did not fix the partition table but it was reporting the root partition as extended, which would not boot and is NOT how I set the system up. If had been up for about 10 months and working fine. I was able to use testdisk in a livecd session to both backup my home and etc directories and fix the partition table.
I'm marking this issue fixed. But I'm still confused as to what the hell happened. Unclean shutdown?
I'm getting contantly ERROR 17...
I dunno how to fix, I simply reboot some times and it desapears..
If someone could give me a clue..
Thx guyz!

[SOLVED] GRUB: Error 15: File not found

I've used the beginners guide to install Arch on my laptop and everything went smooth untill I rebooted and ended up with GRUB error 15. I've seen some other people having trouble with this one but neither of the solutions that worked (or didn't work) for them have worked out for me. I will try to provide you with as much information as possible:
I get to the GRUB menu and get the error after choosing 'Arch Linux' from it.
menu.lst
title Arch Linux
root (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/0b899428... ro vga=773
initrd /kernel26.img
The only thing I've changed in menu.lst is that I've added vga=773. I left out the rest of the UUID because I'm writing it of my laptop beside me.
fdisk -l
Device Boot Start End Blocks ID System
/dev/sda1 * 1 13 104422 83 Linux
/dev/sda2 14 144 1052257+ 82 Linux swap / Solaris
/dev/sda3 145 1101 7687102+ 83 Linux
/dev/sda4 1102 9729 69304410 83 Linux
blkid
/dev/sda1: UUID="1afac34a-..." TYPE="ext2"
/dev/sda2: TYPE="swap" UUID="abd14101-..."
/dev/sda3: UUID="0b899428-..." TYPE="jfs"
/dev/sda4: UUID="3b33ca9f-..." TYPE="jfs"
I've also tried poking around in the GRUB console:
grub> root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... no
Checking if "/grub/stage1" exists... yes
Checking if "/grub/stage2" exists... yes
Checking if "/grub/e2fs_stage1_5" exists... yes
Running "embed /grub/e2fs_stage1_5 (hd0)"... failed (this is not fatal)
Running "embed /grub/e2fs_stage1_5 (hd0,0)"... failed (this is not fatal)
Running "install /grub/stage1 (hd0) grub/stage2 p /grub/menu.lst "... succeeded
Done.
Any help would be much appreciated and I'll gladly provide you guys with any other information if necessary.
EDIT: Solved through re-installing.
Last edited by zulustar (2009-09-13 20:20:57)

I moved the boot parition to hdd sda, but doing so I had to reinstall everything, and it seemed to fix it. I also found that one of the sata cables had been knocked out, but I don't think that was the orginal fault.
ibendiben wrote:
fumbles wrote:
timeout 5
default 1
color light-blue/black light-cyan/blue
#(0) Arch
title Arch Linux
root (hd2,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/blah(aka sda1) ro vga=795
initrd /kernel26.img
I wonder why you have "default 1". If you want to boot Archlinux (above) as default you should use "default 0", or has something changed lately?
Also:
root=/dev/disk/by-uuid/blah(aka sda1)
that doesn't seem to be very valid. You need to fill it in.
/edit
Ofcourse you used blah(aka sda1) just here, not in the real file... sorry for the unhelpfull post
The default was a typo, as I could not boot into anything except the Arch CD I had to type it in manually. Although thanks for the reply anyways.
kgas wrote:
Hello fumbles, As you have a separate /boot partition, the grub entry is not correct, I believe. if should be /boot/vmlinuz For more help this link may also help you.
http://www.experts-exchange.com/Operati … 72531.html
This is simply not true. The reverse however is. I did NOT have a seperate boot parition, ie boot was just in the root partition then yes I would have to add /boot to the kernel and initrd lines.
Last edited by fumbles (2009-01-08 04:32:07)

[SOLVED] [GRUB error] "no such device" "vmlinuz-linux not found"

SOLUTION AT POST #11
I just completed the install process onto a new machine. Grub starts but then returns these error messages.
Booting 'Arch GNU/Linux, with Linux core repo kernel'
error: no such device: ad4103fa-d940-47ca-8506-301d8071d467.
Loading Linux core repo kernel ...
error: file '/boot/vmlinuz-linux' not found.
Loading initial ramdisk ...
error: you need to load the kernel first.
Press any key to continue...
I installed Arch via a flashdrive (sdb), onto SATA port 1 (sda). SDA has a fresh MBR. Unfortunately, I have no way to post my grub config files. What files must I modify to get GRUB to work properly?
fstab: http://sprunge.us/SVMi
grub.cfg: http://sprunge.us/hQCB
Edit: Thread solved.
Last edited by qKUqm3wtY4 (2013-01-31 03:36:43)

SOLUTION
by: jynnantonix
Step 1: Start Arch via boot disc.
Step 2: Connect to internet.
Step 3: Mount partitions.
# swapon dev/sdX
# mount /dev/sdX /mnt
# mount /dev/sdX /mnt/home
# mount /dev/sdX /mnt/boot
Step 4: Chroot
# arch-chroot /mnt
Step 5: Remake grub.conf
# grub-mkconfig -o /boot/grub/grub.cfg
Another Notable Tip by: jynnantonix
If you need to post information from terminal to the internet, use the following:
[insert command here] | curl -F 'sprunge=<-' http://sprunge.us
example: ls -l /dev/disk/by-uuid/ | curl -F 'sprunge=<-' http://sprunge.us
example: cat /boot/grub/grub.cfg | curl -F 'sprunge=<-' http://sprunge.us
Last edited by qKUqm3wtY4 (2013-01-31 04:04:49)

[SOLVED] Grub Problems Can boot Arch w/ grub edits only

I had 3 Linux OS's installed on this computer, Arch and 2 versions of Ubuntu on one hard drive.
The MBR belonged to Ubuntu, using grub2. I decided to get rid of the older Ubuntu (sda8 and 9) and add it's HDD space to my Arch home (sda12). Used the current Gparted live to modify the partitions and all went well, but of course, the numbers changed getting rid of 2 partitions.
No boot upon restart so I decided to get Arch's grub back to the MBR with the new partition numbering scheme.
Using a live CD, I used the grub shell, find /boot/grub/stage1.....etc, etc. and after a bit of fumbling, grub indicated success in the shell. When I was through though, a reboot was not successful, although the current stable grub was now written to the MBR. I edited the lines using grub edit option, and got Arch to boot, and figured out the correct partition numbers. Next I edited the menu.lst to reflect the new sda numbers.
Now rebooting results in a long delay when grub should be on the screen, and the numbers on the Arch entries reflect the old numbers still!! I double checked thinking I forgot to save the edits to the menu.lst file, but they are correct. I can boot Arch, but have to edit the lines each time.
The current partitions are as follows. I edited the terminal output to show details.
[jeff@Arch2009p2 ~]$ sudo fdisk -l
Password:
Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000383e7
Device Boot Start End Blocks Id System
/dev/sda1 * 1 91201 732572001 5 Extended
/dev/sda5 1 255 2048224+ 82 Linux swap / Solaris
/dev/sda6 (ubuntu /) 256 1471 9767488+ 83 Linux
/dev/sda7 (ubuntu /home) 1472 22321 167477593+ 83 Linux
/dev/sda8 (arch boot) 22322 22325 32098+ 83 Linux
/dev/sda9 (arch /) 22326 23627 10458283+ 83 Linux
/dev/sda10 (arch /home) 23628 91201 542788123+ 83 Linux
I have a few questions regarding a separate boot partition for Arch.
Should the grub> root (hd0.0) command be directed to the root or boot partition.
My handy printed emergency guide says: Set grubs root device to the partition containing the boot directory.
OK.....Writing it out now, it seems clear, so I'll try reinstalling grub from a live CD.
Why does grub have incorrect partition numbers even though the menu.lst is correct?
There are only 2 OS's on this box now, and one contains grub2.
Is current grub able to interact with grub 2 if I screwed something up on the install?
Last edited by jeff story (2010-05-24 20:05:06)

OK
I managed to fix the problem of grub not reading/using the menu.lst file. Not sure WTF it was reading and where that file was located!
The problem seems to have been the most insignificant detail.
When using the grub terminal, I did not execute the quit command when I was through. I just closed the terminal and rebooted.
After repeating the following code via live CD a few times:
$ sudo grub
grub> find /grub/stage1
grub> root (hd0,7)
grub> setup (hd0)
Grub still didn't read the current menu.lst.
This morning I got things to work correctly and grub to read the current menu.lst by adding a quit command and returning to the linux shell prior to rebooting.
I used the following commands:
$ sudo grub
grub> find /grub/stage1
grub> root (hd0,7)
grub> setup (hd0)
grub> quit

Disk read error when booting Windows 7 / White screen / Screen frozen

Hello,
I installed Windows 7 and Mac OSx on Dual boot.
1) A problem arose when starting up. Sometimes the screen freezes after i have selected Windows 7 boot on BootCamp.
2) Second problem, when booting the screen is white and doesn't change.
3) Third problem, "Disk read error occured". This is the message that appears on the screen when booting Windows 7.
4) Fourth problem, a blinking folder with a Question Mark on it.
Please help with these problems.
Thank you for your help.
Stinou142

Windows insists that its Partition Map be set up the Windows way. No exceptions. If you use anything other than BOOT CAMP (or Open Source REFIt) to do the partition setup, it will not work.
WARNING: If you allow Windows to Modify the partition Map directly, Windows will clobber Mac OS X so completely that will require a complete Mac OS X Re-Install. Windows in not a pleasant guest.
Be certain you are using the correct version of BOOT CAMP to match Your Mac OS X, and check for which versions of Windows are supported under it.

[Solved] Grub error when booting...

Similar Messages

Maybe you are looking for