[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)
Similar Messages
-
[SOLVED]error: attempt to read or write outside of partition
Hello, I update my system at least once a week, sometimes I run pacman -Syu more than that. So this system is no more than about 7 days behind what is available today. Last time I did this the kernel got updated and it updated itself again or at least it just ran mkinitcpio, also my passwd and group changed, anything that was not represented in the pacnew version got a representation, this last one mainly featured a lot of changes to "/usr/bin/nologin" from the login false version, whatever it was, nothing that looks too fussy.
Reboot just to see what will happen and I am greeted with this:
Booting `Arch Linux, with Linux core repo kernel'
Loading Linux core repo kernel ...
error: attempt to read or write outside of partition
Loading initial ramdisk ...
unaligned pointer 0x1d
Aborted. Press any key to exit.
I happen to have a usb drive that has Arch Linux 3.11.6.-1-ARCH, so I put that in and get an environment I can work with. Chroot in and so I can run mkinitcpio -p linux, thinking that that is the problem, some error in the kernel, I actually end up using the command
# /usr/lib/modules
, since
# mkinicpio -p linux
won't run, it gives:
==> Building image from preset: /etc/mkinitcpio.d/linux.present: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.config -g /boot/initramfs-linux.img
hexdump: /boot/vmlinuz-linux: Input/output error
==> ERROR: invalid kernel specified: '/boot/vmlinuz-linux'
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.config -g /boot/initramfs-linux-fallback.img -S autodetect
hexdump: /boot/vmlinuz-linux: Input/output error
==> ERROR: invalid kernel specified: '/boot/vmlinuz-linux'
However,
# mkinitcpio -g /boot/linux.img -k 3.14.6-1-ARCH
will. Everything finishes with a success, exit out, reboot and bam, same message, so it is not the kernel at least not on its own. Here is what my fstab looks like:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda3
UUID=4dbfa319-4f88-49c1-a595-27faabfe4f57 / ext3 rw,relatime,data=ordered 0 1
# /dev/sda1
UUID=4C05-1A6B /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
# /dev/sda4 LABEL=home
UUID=bff35508-596c-4d7c-a983-b6b0ddc4f6e2 /home ext3 rw,relatime,data=ordered 0 2
# /dev/sda2
UUID=e87030ad-3226-41e3-938a-5be3351e34ed none swap defaults 0 0
#efivars
efivarfs /sys/firmware/efi/efivars efivarfs defaults 0 0
#MySQL, linux version
tmpfs /var/lib/mysqltmp tmpfs rw,gid=89,uid=89,size=100m,mode=0750,noatime 0 0
and my mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect block filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev block filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev block mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev block lvm2 filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
While I am here I might as well ask this is this an appropriate boot structure?
/boot/
>>>>/EFI/
>>>>/>>>/grub/
>>>>/>>>/>>>>grubx64.efi
>>>>/grub
>>>>/>>>>/fonts
>>>>/>>>>/grub.cfg
>>>>/>>>>/grub.cfg.example
>>>>/>>>>/grubenv
>>>>/>>>>/local
>>>>/>>>>/>>>>/*.mo files
>>>>/>>>>/themes/
>>>>/>>>>/>>>>>>/starfield/*.png *.pf2 files
>>>>/>>>>/x86_64-efi
>>>>/>>>>/>>>>>>>/ *.mod files
>>>>/initramfs-linux-fallback.img
>>>>/initramfs-linux.img
>>>>/linux.img
>>>>/vmlinuz-linux
Anyone have any ideas on what I can do to get my system back?
Last edited by Never (2014-06-11 03:17:24)Inside of my rescue disk I get:
# efibootmgr
BootCurrent: 000A
Timeout: 0 seconds
BootOrder: 0005,0003,0001,0002,000A,0004,0000,0007,0008,0009
Boot0000 Windows Boot Manager
Boot0001* USB Flopp/CD
Boot0002* USB Hard Drive
Boot0003* arch_grub
Boot0004* ATAPI CD-ROM Drive
Boot0005* grub
Boot0007* CD/DVD Drive
Boot0008* USB Floppy/CD
Boot0009* Hard Drive
Boot000A* UEFI: SanDisk Cruzer Glide 1.26
my /dev/sda1 was /boot/ not /boot/efi, so I made that change, allowing /boot on / [/dev/sda3] to now be populated with part of the stuff on /dev/sda1 and /dev/sda1 would just have /boot/efi/, instead of all of boot, then ran:
# modprobe -r efivars
# umount /sys/firmware/efi/efivars
# modprobe -r efivarfs
# modprobe efivarfs
# mount -t efivarfs efivarfs /sys/firmware/efi/efivars
# efivar -l
returned a bunch of variables
# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub --recheck --debug
# grub-mkconfig -o /boot/grub/grub.cfg
# efibootmgr
BootCurrent: 000A
Timeout: 0 seconds
BootOrder: 0003,0001,0002,000A,0004,0000,0007,0008,0009
Boot0000 Windows Boot Manager
Boot0001* USB Flopp/CD
Boot0002* USB Hard Drive
Boot0003* grub
Boot0004* ATAPI CD-ROM Drive
Boot0007* CD/DVD Drive
Boot0008* USB Floppy/CD
Boot0009* Hard Drive
Boot000A* UEFI: SanDisk Cruzer Glide 1.26
arch_grub, whatever that was, went away. Pull out of arch-chroot, unmount sdaXs, reboot and:
ERROR: No boot disk has been detected or the disk has failed.
An extensive hp diagnostic check reveals... Nothing wrong.
A reboot and removal of all data written in /dev/sda1 and /dev/sda3/boot sectors reveals:
# mkdir /boot/efi/123
mkdir: cannot create directory /boot/efi/123: Cannot allocate memory
Which persist even on a restart and trying to mkdir into /mnt/arch/boot/efi/EFI while outside of arch-chroot. No idea why that is happening, oh well. -
[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 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) -
[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! -
my problem here
https://bbs.archlinux.org/viewtopic.php … 6#p1001936
ps:sry mods
well my problem solved when i done a install from cd and not from net.
info for developers:when i did a install from net my system doesn't has a initrmfs file
Last edited by vegihat (2011-10-11 06:05:40)Yes: that is the bug report that ataraxia linked to in response to your post: if you had read it you would have found the workaround and wouldn't have needed to open this thread.
I'm glad you have it sorted. Please mark your thread as [Solved]... -
[SOLVED] - Grub Error 15 on Fresh Install
I've created a Boot CD from the archlinux-2011.08.19-core-i686.iso and booted from the CD.
I've used both Autoconfig and Manual to set up my 4 Gig USB Flash Drive - /dev/sdb
BOOT - /dev/sdb1: UUID="467fc66a-6c36-48ab-a7f3-69f449407927" TYPE="ext2" Size=1003.53 Meg
SWAP - /dev/sdb2: UUID="f83191f6-cdf3-4647-80e2-86ac73063725" TYPE="swap" Size=259.75 Meg
/dev/sdb3: UUID="fc7e8565-6668-4370-bb32-33d2d89ee28e" TYPE="ext2" Size=2.02 Gig
/dev/sdb4: UUID="00055f18-3e0a-48b8-a9c5-5593aacc2bee" TYPE="ext2" Size=676.91 Meg
unallocated 1.68 Meg
Disk /dev/sdb: 4206 MB, 4206886912 bytes
130 heads, 62 sectors/track, 1019 cylinders
Units = cylinders of 8060 * 512 = 4126720 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00002773
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 255 1027619 83 Linux
/dev/sdb2 256 321 265980 82 Linux swap / Solaris
/dev/sdb3 322 847 2119780 83 Linux
/dev/sdb4 848 1019 693160 83 Linux
No matter how I prepare the USB Flash Drive I get the Grub Error message as follows:
Booting Arch Linux
Root (HD1,0)
Filesystem type is ext2fs, Partition Type 0x83
Kernel /vmlinux-linux root-/dev/disk/by-uuid/xxx-xxxx-xxx-xxx ro
ERROR 15: File not Found
In Grub I've tried:
root (HD
and HD0, HD1 are the Options. HD1 is my USB Flash Drive (sdb)
find /boot/grub/stage1 finds nothing.............
I'd think that stage1 would be found if Grub was installed properly.
I've tried EXT2, EXT3, and the following sizes....Boot as 100 Meg, Root as 1800 Meg, Swap as 256 Meg, and Home = Remainder (~1800).
I've searched this Forum and haven't found any answer that makes my USB Flash Drive Boot. At this point I'm stuck.
Is there something I'm overlooking?
Thanks.
Larry
Last edited by lkraemer (2012-02-21 15:17:21)Thanks, DSpyder I already had it as hd0,0. I found the clue here to get my USB Booting.
https://wiki.archlinux.org/index.php/In … _a_USB_key
I used /dev/sdbx versus the UUID, and edited the /etc/mkinitcpio.conf, add the usb hook to the hooks array right after udev.
Larry -
[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] "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 Error 13, ext4 and 2.6.28.1
Hi guys!!!
I have formatted my laptop disk in new ext4 format, following wiki instructions:
http://wiki.archlinux.org/index.php/Cre … _Partition
and all wok fine.
But after today update (pacman -Syu), my arch don't boot.
Grub messages (lastest grub version, normal grub no grub2):
Filesystem type is ext2fs, partition type 0x83
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/.............
Error 13: invalid or unsupported executable format
No Normal image nor Fallback image boot.
Any suggestion?
P.D. Sorry for my englis xD
Check wiki solution:
http://wiki.archlinux.org/index.php/Cre … B_Error_13
Last edited by superchango (2009-01-23 02:19:19)from grub's web site:
13 : Invalid or unsupported executable format
This error is returned if the kernel image being loaded is not recognized as Multiboot or one of the supported native formats (Linux zImage or bzImage, FreeBSD, or NetBSD).
I think your vmlinuz26 file is wrong in some ways, or grub can't read ext4 correctly (I have done a fresh install with ext4, but I have made a separate partition for /boot in ext2)
superchango wrote:following wiki instructions:
http://wiki.archlinux.org/index.php/Cre … _Partition
did you create from scratch or did you convert from ext3 ? -
[Solved] Grub errors 18 and 22 when booting from SSD
Hello community,
recently I purchased an SSD drive and am now having trouble doing an Arch install on it. Before that a 2TB HDD was in use. After building in the SSD I partitioned it (msdos partition table) creating partitions for swap, / and /home. Then I copied the files from the old /home partition on the freshly created one and installed Arch on the new / partition. Here's the partition setup:
$ LANG=C sudo fdisk -l
Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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: 0x0003a234
Device Boot Start End Blocks Id System
/dev/sda1 2048 3907028991 1953513472 5 Extended
/dev/sda5 16065 4192964 2088450 82 Linux swap / Solaris
/dev/sda6 4196352 65720319 30761984 83 Linux # old /
/dev/sda7 65722368 577720319 255998976 83 Linux # old /home
/dev/sda8 577722368 3907028991 1664653312 83 Linux
Disk /dev/sdb: 128.0 GB, 128035676160 bytes
255 heads, 63 sectors/track, 15566 cylinders, total 250069680 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: 0x000a9841
Device Boot Start End Blocks Id System
/dev/sdb1 51863552 241582079 94859264 83 Linux # new /home
/dev/sdb2 241582080 250068991 4243456 82 Linux swap / Solaris
/dev/sdb3 2048 51863551 25930752 83 Linux # new /
Partition table entries are not in disk order
The problem is: booting from the SSD fails as follows: On the first try to select some Grub entry I get an error 22 "No such partition.". On any further try I get error 18 "Selected cylinder exceeds maximum supported by bios".
What works is to boot up the new system from the Grub residing on the HDD. So the problem is just the new Grub install in the SSD's MBR. Also it's not a thing of Grub's configuration, since copying the working menu.lst from the HDD install and reinstalling grub via grub-install /dev/sdb gives the correct Grub entries but selecting them results in the same errors.
So currently I'm booting from the HDD and selecting the boot entry for the freshly installed SSD system there, which works fine. But of course I'd like the SSD to be able to boot without "help" on the part of the HDD.
I tried to activate AHCI in the Bios but it didn't make any difference. The SSD is a Crucial M4 128GB.
Thanks for any hints,
PhotonX
Last edited by PhotonX (2012-07-26 06:04:53)I created a /boot partition now:
$ LANG=C sudo fdisk -l
Disk /dev/sdb: 128.0 GB, 128035676160 bytes
255 heads, 63 sectors/track, 15566 cylinders, total 250069680 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: 0x000a9841
Device Boot Start End Blocks Id System
/dev/sdb1 51863552 241582079 94859264 83 Linux # /home
/dev/sdb2 241582080 249831423 4124672 82 Linux swap / Solaris
/dev/sdb3 2048 51863551 25930752 83 Linux # /
/dev/sdb4 * 249831424 250068991 118784 83 Linux # /boot
Partition table entries are not in disk order
Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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: 0x0003a234
Device Boot Start End Blocks Id System
/dev/sda1 2048 3907028991 1953513472 5 Extended
/dev/sda5 16065 4192964 2088450 82 Linux swap / Solaris
/dev/sda6 4196352 65720319 30761984 83 Linux
/dev/sda7 65722368 577720319 255998976 83 Linux
/dev/sda8 577722368 3907028991 1664653312 83 Linux
Then installed Grub on this partition: "grub-install /dev/sdb4". Then placed the SSD on the first position in the Bios, booted but got the same errors in Grub. So it doesn't matter where exactly Grub is installed, if it's somewhere on the SSD, it fails...
edit: Concerning using UUIDs: I couldn't find any howto regarding Grub (legacy) configuration with UUID's. Could you point me to some example config?
edit2: I now put the SSD on the first place in the boot list and started PartedMagic. But fdisk still recognizes the SSD as sdb and the HDD as sda. I think, the sdX identifier can be changed only by plugging the SSD in the first SATA port and the HDD in the second (while now it is the other way around).
edit3: I tried to install Grub from the HDD installation on the SSD (executed "grub-install /dev/sdb4" from the HDD system) and found out that, though I created a /boot partition on the SSD, the Grub files installed directly on /dev/sdb are used. So I tried to install Grub from the HDD system onto /dev/sdb (executed "grub-install /dev/sdb" from the HDD system) and got error 22 even before Grub's boot list was shown. But maybe it's really a bad idea to install Grub on another drive than the system it belongs to is located.
Last edited by PhotonX (2012-05-18 21:54:56) -
[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 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: no such device....
Here is the error after grub tab:
Thumbnails only -- Follow image posting rules --- Inxsible
This are my partitions and uuid:
lrwxrwxrwx 1 root root 10 Sep 11 12:39 124dca57-5a6e-483b-8563-0d1f7b03b12c -> ../../sda3
lrwxrwxrwx 1 root root 10 Sep 11 12:40 606fbea0-2aaa-44d0-8677-e93f49004ffc -> ../../dm-2
lrwxrwxrwx 1 root root 10 Sep 11 12:39 87f92183-9031-44cd-bf6c-1046a636b127 -> ../../sda2
lrwxrwxrwx 1 root root 11 Sep 11 12:39 99fcc4b6-ea63-46ed-b740-472d28e50d35 -> ../../loop1
lrwxrwxrwx 1 root root 10 Sep 11 12:39 b5024c82-b015-4e4e-a1c2-0777f31d9ff1 -> ../../sda4
lrwxrwxrwx 1 root root 10 Sep 11 12:40 be601ccb-531f-4947-9988-67d855f83bfb -> ../../dm-1
lrwxrwxrwx 1 root root 10 Sep 11 12:39 ef0cbf1f-d46d-40ca-973f-bda3f1b4fa95 -> ../../sda1
sda1 - boot(100MB), sda2 - swap, sda3 (/, ext4), sda4(ext4 - data storage...)
I installed archlinux for second time - first time I just partitioned it using cfdisk(so propably mbr and grub doesnt delete properly.
System couldnt start and showed that partition with uuid xxx is not there.
I connected that disk to usb of another computes and here is uuid of boot partition, with everything what is on it:
Thumbnails only -- Follow image posting rules --- Inxsible
Here is my grub.cfg:
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
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 GNU/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 GNU/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 ###
How to solve it? What is wrong?
Last edited by rado3105 (2012-09-11 16:32:25)Ok sorry.
The problem was that I didnt know that syslinux is alternative to grub. So I installed syslinux and also grub. Thanks -
Error after sync, cannot read or write to ipod disk
when my computer has sync'd with i tunes i get the error " Attempting to copy i ipod"my ipod" failed. the disk could not be read or written to"
PLEASE HELPIt can be several different reasons caused the problem e.g. hub, USB port, cable etc.
See if you doing a restore with another computer helps.
Maybe you are looking for
-
HHow can I get the 15 minute time limit back instead of putting in iTunes password on every purchase?
-
Simple update on mouse click.... im lost!
hi all im new to forms... now what i have is a table with pk... and several feilds... i have managed to create a datablock easily enough... now what i need to do is allow the user to enter the id of a record and have the rest of its feilds show up in
-
IS IT POSSIBLE TO EXECUTE A QUERY BASED ON USER
Hi, I need to restrict a set of queries to a user. Is it possible. Thanks Mini
-
On my new iMac running OSX 10.8.2 and Aperture 3.4.3 ... if "Use Centered Loupe" is selected, the Loupe appears, but if I try to move it, the Loupe zips to the upper left corner of the Aperture window and the entire Aperture window slides to the righ
-
Playing video files on a iMac G3...
I am planning on using my old iMac which is running Jaguar and OS9 to play an animation and a short film at an exhibition I have coming up next week. It doesn't have a DVD drive - just CD-ROM only. I was going to install the videos straight to the ha