Double Kubuntu install

[Quaxo76]

Hello all,
After having messed around a bit too much with my Kubuntu install, I decided to install another Kubuntu in another partition. I prepared the partition, ran the livedvd, installed on the new partition, everything went fine; but at reboot I can't find the new Kubuntu. I can use the old one as usual, but there's nothing new. I tried grub-update, and tried to manually edit menu.lst (by just adding a copy of the original Kubuntu entry, and modifying the partition from (0,2) to (0,11)). But when I choose this new entry at boot time, I get a "File not found" error from Grub.
What can I do to enable boot at the new system?

Thanks
Cristian

[jankushka]

Re: Double Kubuntu install

funny...i'd have expected the new one would be visible and old one would be missing...

well, whatever...hopefully we can put this right.

we need to know a few things first, though...
like what is installed where...

can you boot up the old install at all?

if yes, could you pls open up a konsole and post the result of

fdisk -l <list of device name goes here>

example:

fdisk -l /dev/sda /dev/sdb

cheers

[Quaxo76]

Re: Double Kubuntu install

I can boot perfectly into the old system, even though it's a little "crippled" due to my mistakes.
Here's the output:

Disk /dev/sdb: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot   Start     End   Blocks  Id System
/dev/sdb1  *      1    1912  15358108+  7 HPFS/NTFS
/dev/sdb2      1913    33333  252389182+  f W95 Ext'd (LBA)
/dev/sdb5      1913    2167   2048256  7 HPFS/NTFS
/dev/sdb6      2168    19122  136191006  7 HPFS/NTFS
/dev/sdb7      19123    29958  87040138+  7 HPFS/NTFS
/dev/sdb8      29959    30111   1228941  7 HPFS/NTFS
/dev/sdb9      30112    31084   7815591  83 Linux
/dev/sdb10     31085    32057   7815591  83 Linux
/dev/sdb11     32058    32300   1951866  82 Linux swap / Solaris
/dev/sdb12     32301    33333   8297541  83 Linux

The old system is in sdb9, home is sdb10, the new system is in sdb12.

Thanks
Cristian

[jankushka]

Re: Double Kubuntu install

thanks.
some more info, always working from the konsole...

pls, post (or attach, if they're too long) the content of

the old installation's menu.lst:

cat /boot/grub/menu.lst

and (hopefully) the new installation's menu.lst:

sudo mount /dev/sdb12 /mnt
cat /mnt/boot/grub/menu.lst

you must have grub installed in the mbr, yeah?

cheers

[Quaxo76]

Re: Double Kubuntu install

Here's the old one:

# 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 change this entry to 'saved' 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=64f8c4de-b1db-425b-8a44-84529148f99b ro

## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,8)

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

## ## End Default Options ##

title      Ubuntu, kernel 2.6.20-16-generic
root      (hd0,8)
kernel     /boot/vmlinuz-2.6.20-16-generic root=UUID=64f8c4de-b1db-425b-8a44-84529148f99b ro quiet splash
initrd     /boot/initrd.img-2.6.20-16-generic
quiet
savedefault

title      Ubuntu, kernel 2.6.20-16-generic (recovery mode)
root      (hd0,8)
kernel     /boot/vmlinuz-2.6.20-16-generic root=UUID=64f8c4de-b1db-425b-8a44-84529148f99b ro single
initrd     /boot/initrd.img-2.6.20-16-generic

title      Ubuntu, kernel 2.6.20-15-generic
root      (hd0,8)
kernel     /boot/vmlinuz-2.6.20-15-generic root=UUID=64f8c4de-b1db-425b-8a44-84529148f99b ro quiet splash
initrd     /boot/initrd.img-2.6.20-15-generic
quiet
savedefault

title      Ubuntu, kernel 2.6.20-15-generic (recovery mode)
root      (hd0,8)
kernel     /boot/vmlinuz-2.6.20-15-generic root=UUID=64f8c4de-b1db-425b-8a44-84529148f99b ro single
initrd     /boot/initrd.img-2.6.20-15-generic

title      Ubuntu, memtest86+
root      (hd0,8)
kernel     /boot/memtest86+.bin
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/sda1
title      Microsoft Windows XP Professional
root      (hd0,0)
savedefault
makeactive
chainloader   +1

title      Ubuntu, kernel 2.6.20-16-generic
root      (hd0,11)
kernel     /boot/vmlinuz-2.6.20-16-generic root=UUID=64f8c4de-b1db-425b-8a44-84529148f99b ro quiet splash
initrd     /boot/initrd.img-2.6.20-16-generic
quiet
savedefault

And the new one:

# 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 change this entry to 'saved' 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=a7cd8dde-70b1-40c3-8671-3b9a6249b525 ro

## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd1,11)

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

## ## End Default Options ##

title      Ubuntu, kernel 2.6.20-15-generic
root      (hd1,11)
kernel     /boot/vmlinuz-2.6.20-15-generic root=UUID=a7cd8dde-70b1-40c3-8671-3b9a6249b525 ro quiet splash
initrd     /boot/initrd.img-2.6.20-15-generic
quiet
savedefault

title      Ubuntu, kernel 2.6.20-15-generic (recovery mode)
root      (hd1,11)
kernel     /boot/vmlinuz-2.6.20-15-generic root=UUID=a7cd8dde-70b1-40c3-8671-3b9a6249b525 ro single
initrd     /boot/initrd.img-2.6.20-15-generic

title      Ubuntu, memtest86+
root      (hd1,11)
kernel     /boot/memtest86+.bin
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/sdb1
title      Microsoft Windows XP Professional
root      (hd1,0)
savedefault
makeactive
map       (hd0) (hd1)
map       (hd1) (hd0)
chainloader   +1


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb9.
title      Ubuntu, kernel 2.6.20-16-generic (on /dev/sdb9)
root      (hd1,8)
kernel     /boot/vmlinuz-2.6.20-16-generic root=UUID=64f8c4de-b1db-425b-8a44-84529148f99b ro quiet splash
initrd     /boot/initrd.img-2.6.20-16-generic
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb9.
title      Ubuntu, kernel 2.6.20-16-generic (recovery mode) (on /dev/sdb9)
root      (hd1,8)
kernel     /boot/vmlinuz-2.6.20-16-generic root=UUID=64f8c4de-b1db-425b-8a44-84529148f99b ro single
initrd     /boot/initrd.img-2.6.20-16-generic
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb9.
title      Ubuntu, kernel 2.6.20-15-generic (on /dev/sdb9)
root      (hd1,8)
kernel     /boot/vmlinuz-2.6.20-15-generic root=UUID=64f8c4de-b1db-425b-8a44-84529148f99b ro quiet splash
initrd     /boot/initrd.img-2.6.20-15-generic
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb9.
title      Ubuntu, kernel 2.6.20-15-generic (recovery mode) (on /dev/sdb9)
root      (hd1,8)
kernel     /boot/vmlinuz-2.6.20-15-generic root=UUID=64f8c4de-b1db-425b-8a44-84529148f99b ro single
initrd     /boot/initrd.img-2.6.20-15-generic
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb9.
title      Ubuntu, memtest86+ (on /dev/sdb9)
root      (hd1,8)
kernel     /boot/memtest86+.bin
savedefault
boot

And yes, grub is in the mbr.
Looks like the new grub "sees" the old installation. The old grub added the last entry when I run grub-update, but if I select that last line the system won't boot...

Thanks
Cristian

[penguin.ch]

Re: Double Kubuntu install

The old grub added the last entry when I run grub-update, but if I select that last line the system won't boot...

Which, if I were right, would not be too much of surprise - since all (!) three entries seem to refer to the same "root" partition (at least the so-called UUIDs are looking absolutely identical to me ...).

Therefore, I'd recommend to first backup the old menu.lst, then replace all four (!) occurences of "UUIDs" by regular device nodes (not least to get an idea of what they are really pointing at ...).

[jankushka]

Re: Double Kubuntu install

EDIT (just saw unicornrider's post):
you might just as well replace the uuid values with the traditional dev file names
as per unicornrider's suggestion

---

alright.
yes, i don't know how it happened, but, yeah, there's quite a bit of a mess in there...
i'll go through it.

meanwhile, one thing sticks out pretty clearly.

you see...
the old menu.lst addresses your disc as (hd0).
the new menu.lst says (hd1).

did you add/remove disc drives lately?
or do you have a /dev/sda, with other stuff on it, too?

also, in this old menu.lst file, try replacing the last entry:

title Ubuntu, kernel 2.6.20-16-generic
root (hd0,11)
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=64f8c4de-b1db-425b-8a44-84529148f99b ro quiet splash
initrd /boot/initrd.img-2.6.20-16-generic
quiet
savedefault

with the following (i'm not sure what kernel is installed where at this point, so i put one entry each):

title New Ubuntu, kernel 2.6.20-15-generic
root (hd0,11)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=a7cd8dde-70b1-40c3-8671-3b9a6249b525 ro splash
initrd /boot/initrd.img-2.6.20-15-generic
savedefault

title New Ubuntu, kernel 2.6.20-16-generic
root (hd0,11)
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=a7cd8dde-70b1-40c3-8671-3b9a6249b525 ro splash
initrd /boot/initrd.img-2.6.20-16-generic
savedefault

then save the file and reboot.
see if one of these two boots the new system alright.

if it does, we need to do quite a bit of cleaning and explaining...

let me know.

cheers

ps:
we could also re-install grub from this old install.
but that would be too easy.
we'll keep it as a last resort.

[Quaxo76]

Re: Double Kubuntu install

I haven't added or removed any drives lately. i just created a new partition for the new system.

I tried replacing the last entry as said in the last post... Now if I choose the last entries, the new system boots. But there's something weird: under the "media" folder, what was sda1-8 in the old system, is sdb1-8 in the new. And what was /media/Mp3 is now /media/sdc, and /media/Volume is now /media/sda1. So, most of my programs point to the wrong places now. How do I fix this? Actually, I opened a partition manager and saw that even in the old system, what is called /media/sda1 is actually /dev/sdb1 and so on, so it looks just like a naming thing... How do I change it?

As for UUIDs: I don't know much about them. I thought they were the hard drive's serial? But if they are, why are they different? The new system is in the same hard disk, it's just a different partition...

Thanks
Cristian

[penguin.ch]

Re: Double Kubuntu install

As for UUIDs: I don't know much about them. I thought they were the hard drive's serial?

Rather they're supposed to be some sort of "unique identifiers" for partitions
(in which at least the "unique" part is only wishful thinking; further reading).

[jankushka]

Re: Double Kubuntu install

well...at least we've managed to get your new installation up and running.
or...i think we have, 'cause, at this point, i'm sure what is what anymore...

don't touch grub or any menu.lst files for now.

I haven't added or removed any drives lately. i just created a new partition for the new system.

alright...but...

But there's something weird: under the "media" folder, what was sda1-8 in the old system, is sdb1-8 in the new. And what was /media/Mp3 is now /media/sdc, and /media/Volume is now /media/sda1.

see?
that's the one issue we need to sort out.
as i said earlier, even grub got messed up (remember? old menu.lst=hd0, new menu.lst=hd1).
hd0 usually = sda, hd1 usually = sdb, ...
but, how come in your second post, fdisk showed everything as sdb?

see? it's a mess...
and i'm a bit lost, i must admit...
you, penguin?

So, most of my programs point to the wrong places now. How do I fix this? Actually, I opened a partition manager and saw that even in the old system, what is called /media/sda1 is actually /dev/sdb1 and so on, so it looks just like a naming thing... How do I change it?

wait, wait...
don't change anything just yet...if my assumptions above are correct, we only risk causing more mess...

As for UUIDs: I don't know much about them. I thought they were the hard drive's serial? But if they are, why are they different? The new system is in the same hard disk, it's just a different partition...

see unicornrider's pointers on this.
in theory, but only very much so, for now, it's something that should help abstracting hw from sw better (i'm putting it very simply).
in practice, for now, it's caused a good deal of confusion and not helped all that much.

i reckon we need understand what causes this sda/sdb thing.
and while we try to do that, could you pls do the following:

a) boot your old installation and post the result of the following commands:

ls -l /dev/disk/by-uuid/*

mount

b) boot your new installation and post the result of the following commands:

ls -l /dev/disk/by-uuid/*

mount

cheers

[Quaxo76]

Re: Double Kubuntu install

Old installation...

cristian@A26:~$ ls -l /dev/disk/by-uuid/*
lrwxrwxrwx 1 root root 10 2007-08-08 04:21 /dev/disk/by-uuid/0414503114502846 -> ../../sda1
lrwxrwxrwx 1 root root 10 2007-08-08 04:21 /dev/disk/by-uuid/109E71F87C323999 -> ../../sdc1
lrwxrwxrwx 1 root root 10 2007-08-08 04:21 /dev/disk/by-uuid/121C97911C976E8B -> ../../sdb6
lrwxrwxrwx 1 root root 10 2007-08-08 04:21 /dev/disk/by-uuid/162001B520019D3D -> ../../sdb1
lrwxrwxrwx 1 root root 10 2007-08-08 04:21 /dev/disk/by-uuid/64f8c4de-b1db-425b-8a44-84529148f99b -> ../../sdb9
lrwxrwxrwx 1 root root 10 2007-08-08 04:21 /dev/disk/by-uuid/90F871C3F871A85C -> ../../sdb5
lrwxrwxrwx 1 root root 11 2007-08-08 04:21 /dev/disk/by-uuid/a7cd8dde-70b1-40c3-8671-3b9a6249b525 -> ../../sdb12
lrwxrwxrwx 1 root root 11 2007-08-08 04:21 /dev/disk/by-uuid/b3e2dd06-94fa-4e56-b57f-696efceb8920 -> ../../sdb11
lrwxrwxrwx 1 root root 10 2007-08-08 04:21 /dev/disk/by-uuid/D208A51E08A50299 -> ../../sdb7
lrwxrwxrwx 1 root root 11 2007-08-08 04:21 /dev/disk/by-uuid/ef04e859-8bd5-4e26-8af8-2a9434d7eefe -> ../../sdb10
lrwxrwxrwx 1 root root 10 2007-08-08 04:21 /dev/disk/by-uuid/F644C08544C049D7 -> ../../sdb8

cristian@A26:~$ mount
/dev/sdb9 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
lrm on /lib/modules/2.6.20-16-generic/volatile type tmpfs (rw)
/dev/sdb10 on /home type ext3 (rw)
/dev/disk/by-uuid/162001B520019D3D on /media/sda1 type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096)
/dev/disk/by-uuid/90F871C3F871A85C on /media/sda5 type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=2048)
/dev/disk/by-uuid/121C97911C976E8B on /media/sda6 type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096)
/dev/disk/by-uuid/D208A51E08A50299 on /media/sda7 type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096)
/dev/disk/by-uuid/F644C08544C049D7 on /media/sda8 type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=2048)
/dev/sdc1 on /media/Mp3 type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096)
/dev/sda1 on /media/Volume type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096)

I'll reboot into the new installation and post the results in a moment...

[Quaxo76]

Re: Double Kubuntu install

New installation:

cristian@A26:~$ ls -l /dev/disk/by-uuid/*
lrwxrwxrwx 1 root root 10 2007-08-08 04:35 /dev/disk/by-uuid/0414503114502846 -> ../../sda1
lrwxrwxrwx 1 root root 10 2007-08-08 04:35 /dev/disk/by-uuid/109E71F87C323999 -> ../../sdc1
lrwxrwxrwx 1 root root 10 2007-08-08 04:35 /dev/disk/by-uuid/121C97911C976E8B -> ../../sdb6
lrwxrwxrwx 1 root root 10 2007-08-08 04:35 /dev/disk/by-uuid/162001B520019D3D -> ../../sdb1
lrwxrwxrwx 1 root root 10 2007-08-08 04:35 /dev/disk/by-uuid/64f8c4de-b1db-425b-8a44-84529148f99b -> ../../sdb9
lrwxrwxrwx 1 root root 10 2007-08-08 04:35 /dev/disk/by-uuid/90F871C3F871A85C -> ../../sdb5
lrwxrwxrwx 1 root root 11 2007-08-08 04:35 /dev/disk/by-uuid/a7cd8dde-70b1-40c3-8671-3b9a6249b525 -> ../../sdb12
lrwxrwxrwx 1 root root 11 2007-08-08 04:35 /dev/disk/by-uuid/b3e2dd06-94fa-4e56-b57f-696efceb8920 -> ../../sdb11
lrwxrwxrwx 1 root root 10 2007-08-08 04:35 /dev/disk/by-uuid/D208A51E08A50299 -> ../../sdb7
lrwxrwxrwx 1 root root 11 2007-08-08 04:35 /dev/disk/by-uuid/ef04e859-8bd5-4e26-8af8-2a9434d7eefe -> ../../sdb10
lrwxrwxrwx 1 root root 10 2007-08-08 04:35 /dev/disk/by-uuid/F644C08544C049D7 -> ../../sdb8

cristian@A26:~$ mount
/dev/sdb12 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
lrm on /lib/modules/2.6.20-16-generic/volatile type tmpfs (rw)
/dev/sdb10 on /home type ext3 (rw)
/dev/sda1 on /media/sda1 type ntfs (rw,nls=utf8,umask=007,uid=0,gid=46)
/dev/sdb1 on /media/sdb1 type ntfs (rw,nls=utf8,umask=007,uid=0,gid=46)
/dev/sdb5 on /media/sdb5 type ntfs (rw,nls=utf8,umask=007,uid=0,gid=46)
/dev/sdb6 on /media/sdb6 type ntfs (rw,nls=utf8,umask=007,uid=0,gid=46)
/dev/sdb7 on /media/sdb7 type ntfs (rw,nls=utf8,umask=007,uid=0,gid=46)
/dev/sdb8 on /media/sdb8 type ntfs (rw,nls=utf8,umask=007,uid=0,gid=46)
/dev/sdb9 on /media/sdb9 type ext3 (rw)
/dev/sdc1 on /media/sdc1 type ntfs (rw,nls=utf8,umask=007,uid=0,gid=46)

Thanks,
Cristian

[jankushka]

Re: Double Kubuntu install

alright.

here's what i think we should do, in general terms:
a) boot into your new install
b) re-install grub from the new install
c) make sure the new menu.lst file is alright
d) clean what needs to be cleaned
e) forget about the old installation's grub
f) i then need to explain you a few things about grub (for the future)

unfortunately i'll have to leave here shortly, so i can't get into any details now.
but i'll do it later on today, as soon as i can.

in the meanwhile (courtesy of unicornrider), here's a resource you should find helpful.

cheers.

[jankushka]

Re: Double Kubuntu install

can you pls tell me what this sda1 (/media/Volume) is?
it wasn't in the fdisk output in your second post...

Old installation...

lrwxrwxrwx 1 root root 10 2007-08-08 04:21 /dev/disk/by-uuid/0414503114502846 -> ../../sda1

/dev/sda1 on /media/Volume type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096)

New installation:

lrwxrwxrwx 1 root root 10 2007-08-08 04:35 /dev/disk/by-uuid/0414503114502846 -> ../../sda1

/dev/sda1 on /media/sda1 type ntfs (rw,nls=utf8,umask=007,uid=0,gid=46)

i think here's where the hd0/hd1 confusion might originate from...


could you also please boot into your new installation,
open up a konsole and enter the grub cli, like so:

sudo grub

once in grub (don't attempt anything else, if you don't know),
pls, issue:

find /boot/grub/stage1

then

quit

and post the result back here...


cheers

[Quaxo76]

Re: Double Kubuntu install

hi jankushka,
The sda1 (/media/Volume) is a hd mounted in a removable tray that I use to move data between home and work. It is usually plugged in, it looks like I had forgotten plugging it at the time of my second post. It is a P-ATA drive, containing nothing but data (no OSs). It has never created problem in either Windows or my old Kubuntu installation...

Now, you say I should boot into the new install and "re-install grub from the new install"... How do I do that? Sorry but I'm really new to GRUB, and I don't want to start messing around until I know exactly what to do...

I'm in my old installation right now - I'll reboot asap and post the results of the command you posted...

Cristian