Announcement

**sithlord48** · Jan 02, 2010, 12:30 PM

Re: Gettin error grub code 17: Cannot unmount partition....

can you boot to kubuntu recovery mode and attempt to restore grub from there ?
also mac os prolly just stole your boot part.

if all else fails try to fix grub w/ a super grub disk if you have grub2 or not you might want instead the sg2d. you should have no problems using win 7 to dl and burn the iso. (imgburn is recommended for all iso burning in windows)

**kiraitachi** · Jan 02, 2010, 12:50 PM

Re: Gettin error grub code 17: Cannot unmount partition....

No i cant boot to any recovery mode...neither the memtest86 or the recovery mode.
But i dont think its a prob with the OS its the grub or some flag...idk...

I have Alcohol 120% for burning ISO so dont worry dont got a prob with that...either way, I have in Sda a flag of boot in the partition of fat32 that i use for multiboot (there is where i got installed the grub), and thats the only boot flag that i got in that drive; in the other dive i got Sdb i got no boot flags. Do i have to put a boot flag in my Kubuntu os partition

(no right cause its the grub partition the only one who is booting the rest of the OS right

)

Thanks

**Qqmike** · Jan 02, 2010, 07:48 PM

Re: Gettin error grub code 17: Cannot unmount partition....

Don't know a thing about Mac.
In this situation, I would ignore Mac and simply re-install GRUB properly.

From a Live Kubuntu CD, in Konsole.
sudo grub
to get the GRUB prompt.
Then figure out your drives from the point of view of the Live CD:
grub>geometry (hd<Press TAB key now>
(or grub>geometry (hd0), then grub>geometry (hd1), etc.)
and use that info about (hdx,y)'s next:
In GRUB Legacy, it is
grub>root (hdx,y)
grub>setup (hdz)
grub>quit

WHERE:
(hdx,y) is the partition containing the GRUB files you wish to use (either a Kubuntu partition or a dedicated GRUB partition);
(hdz) is the MBR of the hard drive z you wish to install GRUB to (usually hdz is the drive set in BIOS to boot first, the hard from which the PC boots; seen from the live CD, it can be anything: hd0, hd1, hd2, etc.).

GRUB Legacy (see the section "re-install GRUB" from live CD:
-- How To GRUB Methods - Toolkit
http://kubuntuforums.net/forums/inde...opic=3081671.0
Or if it GRUB 2 (I hope not!

):
GRUB 2 A Guide for Users
http://kubuntuforums.net/forums/inde...opic=3106368.0
(SECTION 3: Fixing things)

**kiraitachi** · Jan 03, 2010, 04:21 AM

Re: Gettin error grub code 17: Cannot unmount partition....

Yeah thats the first thing i did cause i though i may have toched something during the Mac installation, so i reinstalled the grub like 4 times and wont work.....the grub works perfectly cause Windows 7 boots from the grub...but its just that the kubuntu partition will say cannot unmount partition drive when i try to boot it from grub.

U know if might be the flags

? maybe i have to put a boot flag from the partition editor?? or something like it? thanks

**Qqmike** · Jan 03, 2010, 07:15 AM

Re: Gettin error grub code 17: Cannot unmount partition....

"but its just that the kubuntu partition will say cannot unmount partition drive when i try to boot it from grub."

That's Error 17, as you said, and it should be: cannot mount the partition.
That usually occurs when you are pointing GRUB at a partition it cannot mount

Like Windows or Mac, and trying to boot it directly (instead of indirectly using chainloader). Are you pointing GRUB at Mac instead of at Kubuntu? It sounds like you might be. Double-check your deice names (hdx,y)'s. In fact, if you mess them up, then even re-installing GRUB won't help.

As for boot flags, BIOS should be set to boot from one of your HDs and a boot flag should be set somewhere on that hard drive. It doesn't hurt to set another boot flag on another HD, but set only one boot flag per HD. But your error 17 thing is the more serious problem.

**kiraitachi** · Jan 03, 2010, 07:34 AM

Re: Gettin error grub code 17: Cannot mount partition....

Lol your right Qqmike its mount partition, just changed the title and everything i had mistake lol never mind, either way so what ur saying is taht i should check out if i got the devices name wrong? ill check out that , but i think i didnt did any mistake in that, ill post later my menu.lst over here, thanks.

**Qqmike** · Jan 03, 2010, 03:19 PM

Re: Gettin error grub code 17: Cannot mount partition....

If in your "controlling" GRUB menu.lst, the (hdx,y) that points to your Kubuntu is absolutely correct, then one thing it could be is your Kubuntu filesystem needs checking (to make sure it is not damaged).
Run GParted Live CD to do that.
Highlight the Kubuntu partition (in GParted), make sure it is unmounted (right-click > unmount), then check it (right click > check). Click "applies" as needed to make it go, watch for any details you can see. GParted should also fix things as it goes, too.

**kiraitachi** · Jan 03, 2010, 06:43 PM

Re: Gettin error grub code 17: Cannot mount partition....

Thanks for the tip Qqmike cause now that i remember the last time that i booted into kubuntu, strangely it did a checksystem....maybe is that, hope it works....i think it cause i removed a kernel or something...dammit.

**kiraitachi** · Jan 04, 2010, 06:04 AM

Re: Gettin error grub code 17: Cannot mount partition....

Dude i tried checking the partition with gparted after unmounting it and gives me and error so i cant do it...but i doesnt specifys the error so i cant do nothing...still in the same...i brought some pics to show u how everything is set up. Maybe with that we get a clear idea of whats going on..

This is are my partitions of sda and how they are set up....the one that is fat and has the lowest space (39 megas) is the one where i got my grub installed (its done to only have the grub in it).

[img width=400 height=270]http://img510.imageshack.us/img510/96/gpartedsdad.png[/img]

This one are the partitions that i got on my sdb.

[img width=400 height=270]http://img199.imageshack.us/img199/833/screenshotdevsdbgparted.png[/img]

And i brought also a pic of the terminal when i do sudo grub geometry, cause i think that the fat partition and where i got to install the grub is in hd0,0 right

U can know just looking up at the pic. I dont know...maybe im wrong...

[img width=400 height=280]http://img690.imageshack.us/img690/725/screenshotterminalu.png[/img]

And this is my Menu.lst and how i have it set.

# 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=2f186bf6-3416-47c2-b0b0-d4cdb5c7506b ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=2f186bf6-3416-47c2-b0b0-d4cdb5c7506b

## 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

## specify if running in Xen domU or have grub detect automatically
## update-grub will ignore non-xen kernels when running in domU and vice versa
## e.g. indomU=detect
## indomU=true
## indomU=false
# indomU=detect

## 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 ##

splashimage=(hd0,0)/boot/grub/splashimages/bt4.xpm.gz

title Kubuntu 9.10, kernel 2.6.31-16-generic (on /dev/sdb2)
root (hd1,1)
kernel /boot/vmlinuz-2.6.31-16-generic root=UUID=2f186bf6-3416-47c2-b0b0-d4cdb5c7506b ro quiet splash
initrd /boot/initrd.img-2.6.31-16-generic
savedefault
boot
quiet

title Kubuntu 9.10, kernel 2.6.31-16-generic (recovery mode) (on /dev/sdb2)
root (hd1,1)
kernel /boot/vmlinuz-2.6.31-16-generic root=UUID=2f186bf6-3416-47c2-b0b0-d4cdb5c7506b ro single
initrd /boot/initrd.img-2.6.31-16-generic
savedefault
boot

title Kubuntu 9.10, memtest86+ (on /dev/sdb2)
root (hd1,1)
kernel /boot/memtest86+.bin
savedefault
boot
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root

# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda2
title Windows 7
rootnoverify (hd0,1)
savedefault
makeactive
chainloader +1

**Qqmike** · Jan 04, 2010, 06:14 AM

Re: Gettin error grub code 17: Cannot mount partition....

I'll try to take a look at this sometimes today.
Two thoughts, though:
> I remember when we set up your separate GRUB partition. Now, what changed? This is still the same setup, right? I don't see how Mac could have messed with it. Since you DO get a GRUB boot menu and CAN boot Windows, it seems the Master Boot Record is still the same (and therefore the GRUB setup is still "in place" as you made it awhile ago). However, it seems you are saying that the Mac-thing damaged your Kubuntu? I don't see how that could happen since Mac was installed to some other separate partition?
> You can do a separate filesystem check/repair, say from a Live CD:
http://members.iinet.net.au/%7Eherma...xt3_filesystem
It doesn't hurt to do that, might help.

**Qqmike** · Jan 04, 2010, 06:17 AM

Re: Gettin error grub code 17: Cannot mount partition....

sda:
Shouldn't the boot flag be on the GRUB partition sda1 and NOT on the Windows partition?

**Qqmike** · Jan 04, 2010, 06:20 AM

Re: Gettin error grub code 17: Cannot mount partition....

Where is Kubuntu? It looks like it is on sdb4.
But sdb4 should be (hd1,3), not (hd1,1).
Am I seeing this right?
In fact, (hd1,1) looks like the Mac-thing ((hd1,1) = sdb2).

**Qqmike** · Jan 04, 2010, 07:20 AM

Re: Gettin error grub code 17: Cannot mount partition....

So, Kubuntu is on (hd1,3) = sdb4

It should read:
title Kubuntu 9.10, kernel 2.6.31-16-generic (on /dev/sdb2)
root (hd1,3)
kernel /boot/vmlinuz-2.6.31-16-generic root=UUID=2f186bf6-3416-47c2-b0b0-d4cdb5c7506b ro quiet splash
initrd /boot/initrd.img-2.6.31-16-generic
savedefault
boot
quiet

And you have to make sure that is the correct UUID corresponding to sdb4 (Kubuntu):
Konsole
sudo blkid

That's why you are getting Error 17:
(hd1,1) = hfs and GRUB doesn't like it or doesn't know it.

Probably no need to repair your Kubuntu filesystem; it's probably OK.

And try changing the boot flag on sda (try it on sda1 = your dedicated GRUB partition; and take it off the other one).

**kiraitachi** · Jan 04, 2010, 08:32 AM

Re: Gettin error grub code 17: Cannot mount partition....

hahahaha im getting nuts hahah XD ur right Qqmike how come i didnt see that one!!!! haha of course is hd1,3 and not hd1,1 ****!!! so many codes and numbers i got lost haaha it was so easy but i didnt saw it lol thanks a lot dude honestly thanks. will do right now and tell u whats going on

Announcement

(solved)Gettin error grub code 17: Cannot mount partition....

(solved)Gettin error grub code 17: Cannot mount partition....

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment