Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Well after having worked so hard, I would rather try to have it with grub :/. I would feel like a small victory rather than a retreat.
Plus it seems there's a small improvement, I now know how to boot from a particular device.
So there I am at the grub command prompt.
What should I do ?
hmmm...
so I tried root (hd0,6), it gave no output.
Then setup (hd0) gave:
checking if "/boot/grub/stage1" ecists... no
checking if "/grub/stage1" exists... no
hmmm...
so I tried root (hd0,6), it gave no output.
Then setup (hd0) gave:
checking if "/boot/grub/stage1" ecists... no
checking if "/grub/stage1" exists... no
Error 15: file not found.
Hmm, try the same exact steps but precede them with:
the first one, which is root (hd0,6) /dev/sda, still produced nothing, and the second, which is setup (hd0) /dev/sda, now says:
error 11: unrecognized device string
the first one, which is root (hd0,6) /dev/sda, still produced nothing, and the second, which is setup (hd0) /dev/sda, now says:
error 11: unrecognized device string
Ok weird, and I did notice something here. The partitions are not correct. I noticed when you posted your original config that sdb (the 250G) has partitions 1-7 on it but 4 was missing. Please post the output of bootinfo again so we can verify our device IDs and partition #'s, something is off.
Isn't this due to the fact that the 4th is hidden, it's just an extended partition that contains the subsequent ones, which are logical partitions ?
Basically, I wanted a partition for seven, one for xp, one for the linux swap, one for the /, and one for /home, and that is greater than 4 so I had to make 3 principal partitions, one for each OS, and the 3rd contains several logical partitions for linux
Isn't this due to the fact that the 4th is hidden, it's just an extended partition that contains the subsequent ones, which are logical partitions ?
Basically, I wanted a partition for seven, one for xp, one for the linux swap, one for the /, and one for /home, and that is greater than 4 so I had to make 3 principal partitions, one for each OS, and the 3rd contains several logical partitions for linux
Code:
set root=(hd0,7)
Code:
set prefix=(hd0,6)/boot/grub
Code:
setup (hd0)
Code:
quit
At this point I am guessing, since we do not have current bootinfo. And yes to that 4th partition thing, that explains that. Regardless, all partition numbers should have remained the same, only the drive letter has changed.
Honestly dude, at this point I would just boot it to that liveCD again and re-run the grub reinstall as explained here.
Just remember when you reinstall it to use sda6. It might not have worked properly the first time because you were still booting to that other drive.
okay, so here I am back again with the live CD.
Here is the output of the script:
Boot Info Script 0.55 dated February 15th, 2010
============================= Boot Info Summary: ==============================
=> Grub 0.97 is installed in the MBR of /dev/sda and looks on the same drive
in partition #6 for /boot/grub/stage2 and /boot/grub/menu.lst.
=> Windows is installed in the MBR of /dev/sdb
=> Windows is installed in the MBR of /dev/sdc
=> Windows is installed in the MBR of /dev/sdd
File system: ntfs
Boot sector type: Windows Vista/7
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows 7
Boot files/dirs: /Windows/System32/winload.exe
File system: ntfs
Boot sector type: Windows XP
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows XP
Boot files/dirs: /ntldr /NTDETECT.COM
File system: ntfs
Boot sector type: Windows Vista/7
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files/dirs: /bootmgr /Boot/BCD
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
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 recordfail {
set recordfail=1
if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
}
insmod ext2
set root='(hd1,6)'
search --no-floppy --fs-uuid --set e339f209-bb4b-4e57-876a-b2b0d17e2e0b
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
insmod ext2
set root='(hd1,6)'
search --no-floppy --fs-uuid --set e339f209-bb4b-4e57-876a-b2b0d17e2e0b
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.32-28-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd1,6)'
search --no-floppy --fs-uuid --set e339f209-bb4b-4e57-876a-b2b0d17e2e0b
linux /boot/vmlinuz-2.6.32-28-generic root=UUID=e339f209-bb4b-4e57-876a-b2b0d17e2e0b ro quiet splash
initrd /boot/initrd.img-2.6.32-28-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-28-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd1,6)'
search --no-floppy --fs-uuid --set e339f209-bb4b-4e57-876a-b2b0d17e2e0b
echo 'Loading Linux 2.6.32-28-generic ...'
linux /boot/vmlinuz-2.6.32-28-generic root=UUID=e339f209-bb4b-4e57-876a-b2b0d17e2e0b ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-28-generic
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod ext2
set root='(hd1,6)'
search --no-floppy --fs-uuid --set e339f209-bb4b-4e57-876a-b2b0d17e2e0b
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod ext2
set root='(hd1,6)'
search --no-floppy --fs-uuid --set e339f209-bb4b-4e57-876a-b2b0d17e2e0b
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows NT/2000/XP (on /dev/sdb2)" {
insmod ntfs
set root='(hd1,2)'
search --no-floppy --fs-uuid --set 384cd74b4cd70314
drivemap -s (hd0) ${root}
chainloader +1
}
menuentry "Windows 7 (loader) (on /dev/sdc1)" {
insmod ntfs
set root='(hd2,1)'
search --no-floppy --fs-uuid --set 9e34497534495207
chainloader +1
}
### 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 ###
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sdb6 during installation
UUID=e339f209-bb4b-4e57-876a-b2b0d17e2e0b / ext4 errors=remount-ro 0 1
# /home was on /dev/sdb7 during installation
UUID=069330ae-88c3-41d3-a102-8293f131928f /home ext4 defaults 0 2
# swap was on /dev/sdb5 during installation
UUID=7685b1a8-59ea-4c0a-99b2-d75d54fe99ff none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
=================== sda6: Location of files loaded by Grub: ===================
Well fair enough, I did it yet one more time (the 3rd?) and this time it worked.
So there I am at the grub menu (not prompt).
It seems there's a piece of something everywhere:
ubuntu, with linux 2.6...
ubuntu, with linux 2.6... (recovery mode)
memory test
windows xp (on /dev/sdb2) <-- this is weird, why is it not sdA2 ?
windows 7 (on /dev/sdc1) <-- this problem was already known, and has to be fixed.
Should I follow the rest of the tutorial or jump straight to that seven problem ?
Well fair enough, I did it yet one more time (the 3rd?) and this time it worked.
So there I am at the grub menu (not prompt).
It seems there's a piece of something everywhere:
ubuntu, with linux 2.6...
ubuntu, with linux 2.6... (recovery mode)
memory test
windows xp (on /dev/sdb2) <-- this is weird, why is it not sdA2 ?
windows 7 (on /dev/sdc1) <-- this problem was already known, and has to be fixed.
Should I follow the rest of the tutorial or jump straight to that seven problem ?
Sweet! Yeah that must have been it then man, seems like the reinstalls got boned up because we weren't yet booting to that drive. Gimme a couple mins, looking over the output from bootinfo again.
Ok done, I suspect the reason the Windows entries are stale is because they're cached from before. Boot to your HD install (1st option) of Ubuntu, and open your bash terminal and run:
okay, so I did that command and restarted.
edit: ok it's fine.
So now we're left with that 7 situation, where the loader is located in sdc1.
Windows 7 (loader) (on /dev/sdc1)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.