Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

boot problems after clonning

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
dereko
Posts: 6
Joined: 2005-03-16 12:24

boot problems after clonning

#1 Post by dereko »

I have a debain machine which i cloned from another machine. The

cloning seemed to work perfectly but when i try boot the machine i get a



Grub error 17

Grub manual:

Error17:

" 17 : Cannot mount selected partition

This error is returned if the partition requested exists, but the

filesystem type cannot be recognized by GRUB.

"



So i booted the machine from a knoppix live cd and mounted the linux

files system ..



Menu.lst

-----------



default 0



## timeout sec

# Set a timeout, in SEC seconds, before automatically booting the

default entry # (normally the first entry defined).

timeout 5



# Pretty colours

color cyan/blue white/blue

## ## End Default Options ## title Debian GNU/Linux, kernel 2.6.8-2-386

root (hd0,0)

kernel /boot/vmlinuz-2.6.8-2-386 root=/dev/hda1 ro

initrd /boot/initrd.img-2.6.8-2-386

savedefault

boot



title Debian GNU/Linux, kernel 2.6.8-2-386 (recovery mode)

root (hd0,0)

kernel /boot/vmlinuz-2.6.8-2-386 root=/dev/hda1 ro single

initrd /boot/initrd.img-2.6.8-2-386

savedefault

boot



title Debian GNU/Linux, kernel 2.6.8

root (hd0,0)

kernel /boot/vmlinuz-2.6.8 root=/dev/hda1 ro

savedefault

boot



title Debian GNU/Linux, kernel 2.6.8 (recovery mode)

root (hd0,0)

kernel /boot/vmlinuz-2.6.8 root=/dev/hda1 ro single

savedefault

boot



title Debian GNU/Linux, kernel 2.4.27-1-386

root (hd0,0)

kernel /boot/vmlinuz-2.4.27-1-386 root=/dev/hda1 ro

initrd /boot/initrd.img-2.4.27-1-386

savedefault

boot



title Debian GNU/Linux, kernel 2.4.27-1-386 (recovery mode)

root (hd0,0)

kernel /boot/vmlinuz-2.4.27-1-386 root=/dev/hda1 ro single

initrd /boot/initrd.img-2.4.27-1-386

savedefault

boot



### END DEBIAN AUTOMAGIC KERNELS LIST





oddly the device.map file is different from the machine it was cloned

from



original machine

(hd0) /dev/hda



But in the cloned machine it is

(fd0) /dev/fd0





I tried adding hd0... to the cloned machine but it didn't make any

difference to the boot up



#fdisk -l



Disk /dev/hda: 80.0 GB, 80026361856 bytes

255 heads, 63 sectors/track, 9729 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes



Device Boot Start End Blocks Id System

/dev/hda1 * 1 9642 77449333+ 83 Linux

/dev/hda2 9643 9729 698827+ f W95 Ext'd (LBA)

/dev/hda5 9643 9729 698796 83 Linux



would someone be able to explain this to me..



I understand that linux usually has a linux partition (hda1)

and a swap partition (hda5)



but have no idea where that hda2 comes from .. don't even know what it

is, possible an empty windows partition or soemthing. I just grabed a

new machine and started then cloning process.



i think this is some kind of partition problem ..

under a bit of pressure to sort this out today so if someone can give me

a hand be much appreciated.



Oh and the filesystem type is reiserfs.



Thanks in advance,

derek

masonm
Posts: 5
Joined: 2005-04-09 21:18
Location: Plant City, FL
Contact:

#2 Post by masonm »

You could easily solve your problem my downloading the Sarge netinstaller and doing a fresh install on your machine. Then everything would be properly configured for you.
Mason M
Registered Linux User # 382617

Linux: because a PC is a terrible thing to waste.

sprucio
Posts: 143
Joined: 2005-03-29 03:30

#3 Post by sprucio »

Can you please edit that menu.lst file with the quote tag?

How did you clone this disc? Norton ghost?

Post Reply