Here's my issue. I have 4 SATA drives in my system as follows.
SATA0 - Winxp
SATA1 - Storage
SATA2 - Storage
SATA3 -
I booted from the live CD and selected install. I set my target to an empty drive (SATA3). In the advanced tab, I selected to install GRUB onto HD3 (SATA3). The install completed without errors, GERUB installed without errors.
When finished it gave me options of 1- Continue using LiveCD 2-Reboot. I selected 2 and it started shuting down. It told me to remove the CD and press enter. I did that.
Nothing happend... I tried several times and still nothing, so I hit the reset button. When rebooting, I got Error 17: Cannot mount selected partition
Windows still boots fine, as I didn't mess with the MBR on that drive. I select my boot drive by using the F11 key and telling the BIOS which drive to boot.
This was working perfectly on a previous install but I upgraded that drive from and IDE to an SATA Raptor. Windows didn't know about ubuntu. knew about Windows but didn't jack up it's MBR. I have a good reason for doing it this way - I won't go into detail for brevity reasons, but I know it can work this way, I just can't duplicate making it work as my previous install did.
Now I get Error 17: Cannot mount selected partition. GRUB Loads but can't mount the ubuntu volume.
Tell me how to make this work please. I don't want the GRUB on the Windows drive.
Would disconnecting all other drives from the couputer during the install, then reconnecting them be my only option?
Please tell me how to make a clean ubuntu install on the desired drive, without mucking up the WinXP MBR.
Thanks...
Does this make any sense?
When I installed and hit advanced for where to load the grub, the default is HD0, on my firtst attempt the install completed but couldn't install a grub because I changed it to SDD which I thought would be correct.
On the second attempt, I changed it to HD3 since it's the 3rd device.
Could it be that the proper entry is SD3? Or is this even valid at all?
Please advise before my next attempt....
I'm getting ready to leave work and when I get home I plan to try again.
Any suggestions before I give it another go?
Well, it seems that SD3 isn't a valid option for the boot loader. It got all the way through the install and then when it tried to install the boot loader and/or Grub... It said fatal error.
Now I'm trying again with the HD3 option hoping that it would have worked before were it not for me hitting the hard reset.
I sure am glad to be getting so much help from myself. I don't know what I would do without me
Originally Posted by crjacksonHere's my issue. I have 4 SATA drives in my system as follows.
SATA0 - Winxp
SATA1 - Storage
SATA2 - Storage
SATA3 -
Windows still boots fine, as I didn't mess with the MBR on that drive. I select my boot drive by using the F11 key and telling the BIOS which drive to boot.
Thanks...
What i would try would be put sata0 to sata3 (just swap them around windows and ) and see if you can still boot windows (sata3) with the F11 key . Now if that boots into windows and it works i would then proceed to install on sata0 it should pick up that windows is on sata3 and put an option there on the mbr to either boot Winxp or and it will not touch the mbr from the windows disk.
cheers
Grub uses 'hd0, 'hd1'...etc to designate drives, regardless of whether they're sata, scsi, ide/pata, usb or whatnot. The OS uses the hda, sda terminology. So after hitting the 'Advanced' button for the grub install dialog box you should have entered either '(hdx)' or used the format '/dev/sdy' (where x=0-3 and y=a,b,c or d). But the ubuntu drive, 'sata3' as you call it (the sata channel it's on?) may or may not be last in the bios (hd3). (edit: that is, at the time of install)
You might want to post your menu.lst.
Boot from the live cd, go to the desktop, click on your ubuntu root partition (it should mount), open up /boot/grub/menu.lst and device.map.
Post it along with the output of:
sudo fdisk -l
Originally Posted by logos34Grub uses 'hd0, 'hd1'...etc to designate drives, regardless of whether they're sata, scsi, ide/pata, usb or whatnot. The OS uses the hda, sda terminology. So after hitting the 'Advanced' button for the grub install dialog box you should have entered either '(hdx)' or used the format '/dev/sdy' (where x=0-3 and y=a,b,c or d). But the ubuntu drive, 'sata3' as you call it (the sata channel it's on?) may or may not be last in the bios (hd3). (edit: that is, at the time of install)
You might want to post your menu.lst.
Boot from the live cd, go to the desktop, click on your ubuntu root partition (it should mount), open up /boot/grub/menu.lst and device.map.
Post it along with the output of:
sudo fdisk -l
Thank you for helping. I tried HD3 and that didn't work. I got the same error. The drive is the last one in the chain and is seen the same way in BIOS. Here is my output from the terminal.
charles@MSI-K8N-Neo4-SLI-Platinum:~$ sudo fdisk -l
Disk /dev/sda: 74.3 GB, 74355769344 bytes
255 heads, 63 sectors/track, 9039 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 9039 72605736 7 HPFS/NTFS
Disk /dev/sdb: 250.0 GB, 250059350016 bytes
16 heads, 63 sectors/track, 484521 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 484518 244197040+ 7 HPFS/NTFS
Disk /dev/sdc: 250.0 GB, 250059350016 bytes
16 heads, 63 sectors/track, 484521 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 484520 244198048+ 7 HPFS/NTFS
Disk /dev/sdd: 74.3 GB, 74355769344 bytes
255 heads, 63 sectors/track, 9039 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdd1 * 1 8666 69609613+ 83 Linux
/dev/sdd2 8667 9039 2996122+ 5 Extended
/dev/sdd5 8667 9039 2996091 82 Linux swap / Solaris
charles@MSI-K8N-Neo4-SLI-Platinum:~$
I got it installed but not the way I want. I was forced to let it re-write the MBR on the XP drive. I would like to get this installed so that it doesn't look to the XP drive for the boot record and/or grub.
I really need some help with this. I've been trying for hours and hours now.
# menu.lst - See: grub(, info grub, update-grub(
# grub-install(, grub-floppy(,
# 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.
default0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout10
## 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
#
# titleWindows 95/98/NT/2000
# root(hd0,0)
# makeactive
# chainloader+1
#
# titleLinux
# 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=5d2e3666-905e-4795-b1f2-701bfbf92ad1 ro
## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd3,0)
## 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 nosplash
## 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, kernel 2.6.20-16-generic
root(hd3,0)
kernel/boot/vmlinuz-2.6.20-16-generic root=UUID=5d2e3666-905e-4795-b1f2-701bfbf92ad1 ro quiet nosplash
initrd/boot/initrd.ing-2.6.20-16-generic
quiet
savedefault
title, kernel 2.6.20-16-generic (recovery mode)
root(hd3,0)
kernel/boot/vmlinuz-2.6.20-16-generic root=UUID=5d2e3666-905e-4795-b1f2-701bfbf92ad1 ro single
initrd/boot/initrd.ing-2.6.20-16-generic
title, kernel 2.6.20-15-generic
root(hd3,0)
kernel/boot/vmlinuz-2.6.20-15-generic root=UUID=5d2e3666-905e-4795-b1f2-701bfbf92ad1 ro quiet nosplash
initrd/boot/initrd.ing-2.6.20-15-generic
quiet
savedefault
title, kernel 2.6.20-15-generic (recovery mode)
root(hd3,0)
kernel/boot/vmlinuz-2.6.20-15-generic root=UUID=5d2e3666-905e-4795-b1f2-701bfbf92ad1 ro single
initrd/boot/initrd.ing-2.6.20-15-generic
title, memtest86+
root(hd3,0)
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.
titleOther operating systems:
root# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
titleMicrosoft Windows XP Professional
root(hd0,0)
savedefault
makeactive
chainloader+1(hd0)/dev/sda
(hd1)/dev/sdb
(hd2)/dev/sdc
(hd3)/dev/sdd
Nice to have all those drives except when it comes to dual booting! But there should be a way to fix this without reinstalling. Here's what I'd try:
Go into the bios and swap your raptors in the the hard disk boot priority:
1. sdd (ubuntu)
2. sdb
3. sdc
4. sda (windows)
Then boot the live cd, click on root partition to mount it, and edit menu.lst and device.map:
cd /media/disk/boot/grub
sudo cp menu.lst menu.lst_backup
gksudo gedit menu.lst
change all instances of (hd3,0) to (hd0,0)
Edit device.map by switching the first and last:
sudo cp device.map device.map_backup
(hd0) /dev/sdd
(hd1) /dev/sdb
(hd2) /dev/sdc
(hd3) /dev/sda
Now reinstall grub to the MBR of sdd:
sudo grub
find /boot/grub/stage1
(this should return '(hd0,0)'--enter in next command)
root (hd0,0)
setup (hd0)
quit
See if that works. If it does, then you can try changing the entry for windows to get it to boot from grub too (and then restore the windows bpotloader to sda so you can boot to it directly if need be)
A new windows entry might look like this:
# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title Microsoft Windows XP Professional
root (hd3,0)
map (hd3) (hd0)
map (hd0) (hd3)
savedefault
makeactive
chainloader +1
I don't mind reinstalling so do you think this MIGHT work...
What if I unplug my 3 NTFS drives, Leave the Ubunt drive plugged in to the same connector, then boot (I hope) to the liveCD and install to that drive.
If it all installs, will there be a problem when I plug in my other drives? Will I still be able to boot to ubuntu or will the grub be messed up and still not boot?
What do you think?
If you want, go ahead. Grub will instal to the MBR, and then reboot and test it. Then connect your other disks. The only thing is you will have to add fstab entries for the other drives manually if you want them to automount in linux. And you could still try adding a boot entry for windoes to grub even if you plan to boot straight to windows' own bootloader on that disk. Restore the windows bootloader using the windows install cd by going into recovery console and tying fixboot or fixmbr. |
Post at 2011-1-22 01:50
| This Author's Posts Only
