PDA

View Full Version : [SOLVED] Operating System not found- - dual boot ubuntu 10.10 & windows 7



CottonCandy
December 7th, 2010, 11:48 AM
I have a Dell laptop that came with windows7. I installed Ubuntu 10.10 & everything was going ok. I restarted the laptop & booted into windows, then restarted the laptop again intending to boot back into Ubuntu. Instead of the screen with boot options I got a message saying:


no module name found
Aborted. Press any key to exit.After I press a key it says


Intel UNDI, PXE-2.0 (build 083)
Copyright (C) 1997-2000 Intel Corporation
CLIENT MAC ADDR: xxxinfohereavailableifnecessaryxxx
PXE-E53: No boot filename received

PXE-M0F: Exiting Intel PXE ROM
Operating System not foundI searched the forum & saw a lot of posts with variations of this problem, but haven't figured out what I need to do to solve it.

In the posts I saw, posters were being asked to run the boot info script & post the results, so I followed the instructions, ran the script & here are my results:


Boot Info Script 0.55 dated February 15th, 2010 ============================= Boot Info Summary: ============================== => Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in partition #4 for (,msdos4)/boot/grub. sda1: __________________________________________________ _______________________ File system: vfat Boot sector type: Dell Utility: Fat16 Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files/dirs: /COMMAND.COM sda2: __________________________________________________ _______________________ 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 sda3: __________________________________________________ _______________________ 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 sda4: __________________________________________________ _______________________ File system: ext4 Boot sector type: - Boot sector info: Operating System: Ubuntu 10.10 Boot files/dirs: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img =========================== Drive/Partition Info: ============================= Drive: sda ___________________ __________________________________________________ ___ Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes Partition Boot Start End Size Id System /dev/sda1 2,048 206,847 204,800 de Dell Utility /dev/sda2 * 206,848 30,926,847 30,720,000 7 HPFS/NTFS /dev/sda3 30,926,848 509,827,119 478,900,272 7 HPFS/NTFS /dev/sda4 509,829,120 959,045,631 449,216,512 83 Linux blkid -c /dev/null: __________________________________________________ __________ Device UUID TYPE LABEL /dev/loop0 squashfs /dev/sda1 3030-3030 vfat DellUtility /dev/sda2 C032AFEA32AFE41E ntfs RECOVERY /dev/sda3 18B4B7BBB4B799A8 ntfs OS /dev/sda4 d6d72bdf-09c8-4ee1-aece-d1880ea38c55 ext4 /dev/sda: PTTYPE="dos" error: /dev/sdb: No medium found ============================ "mount | grep ^/dev output: =========================== Device Mount_Point Type Options aufs / aufs (rw) /dev/sr0 /cdrom iso9660 (ro,noatime) /dev/loop0 /rofs squashfs (ro,noatime) =========================== sda4/boot/grub/grub.cfg: =========================== # # DO NOT EDIT THIS FILE # # It is automatically generated by 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 set have_grubenv=true 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 } function load_video { insmod vbe insmod vga } insmod part_msdos insmod ext2 set root='(hd0,msdos4)' search --no-floppy --fs-uuid --set d6d72bdf-09c8-4ee1-aece-d1880ea38c55 if loadfont /usr/share/grub/unicode.pf2 ; then set gfxmode=640x480 load_video insmod gfxterm fi terminal_output gfxterm insmod part_msdos insmod ext2 set root='(hd0,msdos4)' search --no-floppy --fs-uuid --set d6d72bdf-09c8-4ee1-aece-d1880ea38c55 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.35-23-generic-pae' --class ubuntu --class gnu-linux --class gnu --class os { recordfail insmod part_msdos insmod ext2 set root='(hd0,msdos4)' search --no-floppy --fs-uuid --set d6d72bdf-09c8-4ee1-aece-d1880ea38c55 linux /boot/vmlinuz-2.6.35-23-generic-pae root=UUID=d6d72bdf-09c8-4ee1-aece-d1880ea38c55 ro quiet splash initrd /boot/initrd.img-2.6.35-23-generic-pae } menuentry 'Ubuntu, with Linux 2.6.35-23-generic-pae (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os { recordfail insmod part_msdos insmod ext2 set root='(hd0,msdos4)' search --no-floppy --fs-uuid --set d6d72bdf-09c8-4ee1-aece-d1880ea38c55 echo 'Loading Linux 2.6.35-23-generic-pae ...' linux /boot/vmlinuz-2.6.35-23-generic-pae root=UUID=d6d72bdf-09c8-4ee1-aece-d1880ea38c55 ro single echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-2.6.35-23-generic-pae } ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ### ### BEGIN /etc/grub.d/20_memtest86+ ### menuentry "Memory test (memtest86+)" { insmod part_msdos insmod ext2 set root='(hd0,msdos4)' search --no-floppy --fs-uuid --set d6d72bdf-09c8-4ee1-aece-d1880ea38c55 linux16 /boot/memtest86+.bin } menuentry "Memory test (memtest86+, serial console 115200)" { insmod part_msdos insmod ext2 set root='(hd0,msdos4)' search --no-floppy --fs-uuid --set d6d72bdf-09c8-4ee1-aece-d1880ea38c55 linux16 /boot/memtest86+.bin console=ttyS0,115200n8 } ### END /etc/grub.d/20_memtest86+ ### ### BEGIN /etc/grub.d/30_os-prober ### menuentry "Windows 7 (loader) (on /dev/sda2)" { insmod part_msdos insmod ntfs set root='(hd0,msdos2)' search --no-floppy --fs-uuid --set c032afea32afe41e 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 ### ### BEGIN /etc/grub.d/41_custom ### if [ -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ### =============================== sda4/etc/fstab: =============================== # /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). # # proc /proc proc nodev,noexec,nosuid 0 0 # / was on /dev/sda4 during installation UUID=d6d72bdf-09c8-4ee1-aece-d1880ea38c55 / ext4 errors=remount-ro 0 1 =================== sda4: Location of files loaded by Grub: =================== 441.5GB: boot/grub/core.img 450.2GB: boot/grub/grub.cfg 261.7GB: boot/initrd.img-2.6.35-23-generic-pae 441.5GB: boot/vmlinuz-2.6.35-23-generic-pae 261.7GB: initrd.img 441.5GB: vmlinuz =======Devices which don't seem to have a corresponding hard drive============== sdb What I've found so far seems to point to the problem being some issue with Grub (or Grub 2?) & windows. Is that the problem I'm having here? Can you tell that from the boot info script or would I have to provide some other information?

Or maybe the problem is something to do with the partitions? The windows install took 3 partitions - Utility, RECOVERY, & OS. The RECOVERY partition is flagged with boot. Is that how it's supposed to be or should the OS partition be flagged with boot? If I change the flags in GParted using the Live-CD environment, will that work & if it will work, will it fix this problem or mess things up worse?

Does this issue affect previous releases? I don't mind not having the latest thing if a previous release wouldn't have this problem.

Any help fixing this will be very appreciated!

Quackers
December 7th, 2010, 01:41 PM
I don't know what you've done with the boot script output to get it to show like that but it's too hard for me to read it properly. Can you redo it please? Thanks.

Is your bios set to boot from a network first?

CottonCandy
December 7th, 2010, 11:05 PM
Hi =) Thanks for replying!

I don't know what is making it stretch like that & I don't know how to fix it, so I'm attaching a .txt file. Hopefully that will be ok.

As for the bios settings, I don't know.

When I don't have my internet modem cable plugged in & try to boot I get a slightly different output after "no module name found Aborted. Press any key to exit."
It gives me:

Intel UNDI, PXE-2.0
Copyright (C) 1997-2000 Intel Corporation


For Atheros PCIE Ethernet Controller


Check cable connection!
PXE-M0F: Exiting Intel PXE ROM
Operating System not found
That's not what you mean, is it? I mean, either way it's not finding either OS & it's not showing the OS options screen (that's part of the bios right?) any more.

After I installed ubuntu it began showing an options screen for a few seconds (with win7 as the last option) before booting directly into ubuntu. I'm guessing when I installed Ubuntu it wrote-over or changed the settings that the windows installer set up (no options, boot directly into windows).
And apparently booting back into windows changed the settings again & now it won't boot at all.

I can press Fn12 & get a screen with options: Hard Drive, CD/DVD, Removable Media, & Network Diagnostics. Is that what you mean?

Quackers
December 7th, 2010, 11:17 PM
Yes, choose hard drive. What happens when you boot then?

CottonCandy
December 8th, 2010, 01:07 AM
When I choose hard drive I get the black screen with white text that says no module name found...etc..Operating System not found.

efflandt
December 8th, 2010, 04:56 AM
I have a Dell desktop and that happened to me too. I believe the problem is Dell DataSafe which stores something in what it "thinks" is an unused part of the mbr, but grub2 is larger than DOS/Win mbr, so that trashes grub.

Boot a 10.10 install CD or iso on USB to a live system. Open a terminal and do:


sudo mount /dev/sda4 /mnt
sudo grub-install --boot-directory=/mnt/ --force /dev/sda4That will put grub2 on sda4 instead of in the mbr. The --force is necessary because grub does not like to not be in total control of your hard drive, but works fine for me.

This is similar to reinstalling grub2 per https://help.ubuntu.com/community/Grub2 except in this case we are installing grub2 to a partition instead of the mbr.

Then you need to figure out how to restore the mbr to a standard DOS/Win mbr. One way if you forgot to create your recovery discs is right from the live Ubuntu CD:


sudo apt-get install ms-sys
sudo ms-sys -m /dev/sdaThen use gparted to mark /dev/sda4 as the boot partition.

That is how I have this system set up with grub2 on sda4 so Dell DataSafe does not step on it. Although I recently put natty on SSD and am currently booting grub2 from sdb mbr:


Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x2fb1db22

Device Boot Start End Blocks Id System
/dev/sda1 1 5 40131 de Dell Utility
/dev/sda2 6 1541 12331008 7 HPFS/NTFS
/dev/sda3 1541 108853 861986816 7 HPFS/NTFS
/dev/sda4 * 108853 121602 102403072 83 Linux

Disk /dev/sdb: 80.0 GB, 80026361856 bytes
32 heads, 32 sectors/track, 152638 cylinders
Units = cylinders of 1024 * 512 = 524288 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0006a571

Device Boot Start End Blocks Id System
/dev/sdb1 * 2 152638 78150144 83 LinuxMake a note that if you ever remove Ubuntu or move it to a different drive, if you want Win7 to boot on its own, simply mark /dev/sda2 as the boot partition (not sda3, even though sda3 is C: ). If you try to boot sda3 directly you would get some sort of an error about missing bootmgr, which takes several reboots from Win7 system disc to fix if you do not realize that you simply picked the wrong boot partition. I know this because I played around with Ubuntu on a new Dell laptop before giving it to someone, and had not noted which partition was originally the boot partition.

CottonCandy
December 8th, 2010, 06:14 AM
What awesome timing! I was just typing up another reply about how I was wondering if it could be the Dell/HP/Win7 software corrupting Grub2 thing & questions about getting back into windows without a recovery disk. Thank you for all the info!

I'm still a little unsure though...
If I mark /dev/sda4 as the boot partition, does that mean I'll be able to successfully dual boot ubuntu & windows without removing any of the grub-breaking software from windows? or do I still have to remove the software?

wilee-nilee
December 8th, 2010, 08:43 AM
First here is the script second dell data safe can be removed from windows and should be here is the link.
http://ubuntuforums.org/showpost.php?p=9330849&postcount=9

Okay so lets get the recovery disc so you can boot into windows by running a command to reload its bootloader.http://neosmart.net/blog/2009/windows-7-system-repair-discs/

1) Boot with your Vista/Windows 7 installation disk. Hit <Enter> at the language selection prompt then hit <R> for Repair to get to the Repair section.
2) Select the command prompt (console) and type in the following commands:
BootRec.exe /fixmbr
http://www.sevenforums.com/tutorials/20864-mbr-restore-windows-7-master-boot-record.html

Now all you have to do after getting into windows is go to the control panel and the remove programs and remove the dell data safe. You then just need to reload grub2.
https://help.ubuntu.com/community/Grub2#Reinstalling%20GRUB%202


Boot Info Script 0.55 dated February 15th, 2010

============================= Boot Info Summary: ==============================

=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in
partition #4 for (,msdos4)/boot/grub.

sda1: __________________________________________________ _______________________

File system: vfat
Boot sector type: Dell Utility: Fat16
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files/dirs: /COMMAND.COM

sda2: __________________________________________________ _______________________

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

sda3: __________________________________________________ _______________________

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

sda4: __________________________________________________ _______________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 10.10
Boot files/dirs: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

=========================== Drive/Partition Info: =============================

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sda1 2,048 206,847 204,800 de Dell Utility
/dev/sda2 * 206,848 30,926,847 30,720,000 7 HPFS/NTFS
/dev/sda3 30,926,848 509,827,119 478,900,272 7 HPFS/NTFS
/dev/sda4 509,829,120 959,045,631 449,216,512 83 Linux


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/loop0 squashfs
/dev/sda1 3030-3030 vfat DellUtility
/dev/sda2 C032AFEA32AFE41E ntfs RECOVERY
/dev/sda3 18B4B7BBB4B799A8 ntfs OS
/dev/sda4 d6d72bdf-09c8-4ee1-aece-d1880ea38c55 ext4
/dev/sda: PTTYPE="dos"
error: /dev/sdb: No medium found

============================ "mount | grep ^/dev output: ===========================

Device Mount_Point Type Options

aufs / aufs (rw)
/dev/sr0 /cdrom iso9660 (ro,noatime)
/dev/loop0 /rofs squashfs (ro,noatime)


=========================== sda4/boot/grub/grub.cfg: ===========================

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by 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
set have_grubenv=true
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
}

function load_video {
insmod vbe
insmod vga
}

insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set d6d72bdf-09c8-4ee1-aece-d1880ea38c55
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set d6d72bdf-09c8-4ee1-aece-d1880ea38c55
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.35-23-generic-pae' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set d6d72bdf-09c8-4ee1-aece-d1880ea38c55
linux /boot/vmlinuz-2.6.35-23-generic-pae root=UUID=d6d72bdf-09c8-4ee1-aece-d1880ea38c55 ro quiet splash
initrd /boot/initrd.img-2.6.35-23-generic-pae
}
menuentry 'Ubuntu, with Linux 2.6.35-23-generic-pae (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set d6d72bdf-09c8-4ee1-aece-d1880ea38c55
echo 'Loading Linux 2.6.35-23-generic-pae ...'
linux /boot/vmlinuz-2.6.35-23-generic-pae root=UUID=d6d72bdf-09c8-4ee1-aece-d1880ea38c55 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.35-23-generic-pae
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set d6d72bdf-09c8-4ee1-aece-d1880ea38c55
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos4)'
search --no-floppy --fs-uuid --set d6d72bdf-09c8-4ee1-aece-d1880ea38c55
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows 7 (loader) (on /dev/sda2)" {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set c032afea32afe41e
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 ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

=============================== sda4/etc/fstab: ===============================

# /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/sda4 during installation
UUID=d6d72bdf-09c8-4ee1-aece-d1880ea38c55 / ext4 errors=remount-ro 0 1

=================== sda4: Location of files loaded by Grub: ===================


441.5GB: boot/grub/core.img
450.2GB: boot/grub/grub.cfg
261.7GB: boot/initrd.img-2.6.35-23-generic-pae
441.5GB: boot/vmlinuz-2.6.35-23-generic-pae
261.7GB: initrd.img
441.5GB: vmlinuz
=======Devices which don't seem to have a corresponding hard drive==============

sdb

CottonCandy
December 9th, 2010, 10:48 AM
Thank you! I got windows 7 running from the repair disk & command prompt instructions. :D


I figured that before anything else I should create a CD that I can use to reinstall win7 in case I ever need to...


](*,)



Apparently it takes several DVDs to create a &quot;system image&quot; of win7. I canceled after 2 since I'm not really sure if that's actually the right way to create a disk that I can use to reinstall win7. Is using the &quot;create a system image&quot; thing the right way to create a win7 reinstall disk? & does anyone know what size it will end up being? (it says it may be up to 40GB!)
Is there some program I could be using to make an .iso that I could burn to a CD instead?
What about creating a system restore point? If win7 were to crash or if the partitions got accidentally damaged or erased, would I be able to use the repair disk I made to boot windows & access the restore files & restore/fix/reinstall windows from that? Only if the area where that data was stored hadn't been corrupted/erased right? So I do need a way to reinstall win7. Which brings me back to: will I be able to reinstall win7 using the DVDs from the &quot;create a system image&quot; option that burns multiple DVDs?
If so, is there a way to check if the system image DVDs will work? Would I put in the 1st DVD & then boot from the CD/DVD drive to see if a windows installer comes up? Will it damage my laptop trying to boot from a DVD if it's not boot-able?

I'm sorry for asking so many questions about windows but I'm hoping maybe one of the nice, intelligent people around here can help me. The info I've found so far has been great step-by-step stuff but hasn't answered any of my questions.




- - - - -If you're feeling extra nice... - - - - -

I have some questions about BIOS back ups & upgrades. I'm going to search on these things more later, but for now it's 3:30 am & I am very tired so I am asking here in hopes that people will feel helpful while I am asleep. Thank you again for all the help given already!



In my searching for this boot problem I read that updating to BIOS A08 fixes the dell programs writing to the mbr. (one thread example: http://ubuntuforums.org/showpost.php?p=9767341&postcount=14)

And along with the setup guide & other paperwork dell did include a sheet of paper recommending you update to the latest BIOS & drivers by going to their support website before using your computer.

But I also read in my searching that updating the BIOS can cause things to stop working or even brick your system.

A BIOS upgrade is the most risky thing you can do to a PC!!

IF anything goes wrong, you will end up with an &quot;electric brick&quot; -- as, after that, NOTHING will work.


The very first thing you should do, after you have all the items needed, is back up your existing BIOS. The BIOS update programs generally provide an option to do that. At least that way, if the upgrade goes wrong, you will have a way to restore the current BIOS.

Does anyone know if the dell BIOS updater provides that option?


And how would I go back to the previous BIOS if I had to? Would it be added to the boot menu? Or would I have to reinstall windows in order to reinstall the previous BIOS? Will the system image thing of win7 that takes multiple DVDs include a back up of the BIOS?

wilee-nilee
December 9th, 2010, 11:06 AM
I'm going to answer just a couple of questions. W7 has a great back up set up.You can back up the image of the whole OS install on a external HD, you just use the recovery disc you used to reinstall the bootloader to load it back in. Really you should have anything extra beyond the OS image backed up as well.

If it says more then 40 gigs it sounds like your trying to back up the OS and the extras.

Quackers
December 9th, 2010, 12:27 PM
All my machines came with a means to create a set of recovery dvd's. In fact most of them keep flashing a pop-up insisting you make them. Unless you make those recovery dvd's you could, at some time in the future, need to buy a set of oem recovery discs from the manufacturer. They are definitely worth making.
You can also make a repair disc (which is not the same thing as a set of recovery dvd's even though Windows calls it a recovery cd) in the Control Panel by choosing "make recovery cd" on the left side of the window.

If a bios update can stop Dell's program writing to the mbr it would be good to run it. However, please note that if something goes wrong your machine could become a paper-weight! No going back! Finito! It must be done correctly and no power loss during running! Check up on how to do it first. Some manufacturers include a little program to do it now.

CottonCandy
December 9th, 2010, 10:07 PM
Thank you both for helping me. :) Sounds like I was doing the right thing then.
I've never had to make a boot-able back up of an OS before (unless you count burning the ubuntu .iso to CD) but I was really surprised that the windows back-up is gonna be so big.

I haven't transfered a single one of my files to the new laptop yet, so I was expecting the OS back-up to be up to 15 maybe even 20 GB, but not 40! Maybe it's the software that comes with the OS that's made it larger... guess I need to get more DVDs.



If a bios update can stop Dell's program writing to the mbr it would be good to run it. However, please note that if something goes wrong your machine could become a paper-weight! No going back! Finito! It must be done correctly and no power loss during running! Check up on how to do it first. Some manufacturers include a little program to do it now.
Oh boy, I love how Dell "recommends you update to the latest computer BIOS & drivers" on a sheet titled "Important Information: Before Using Your Computer". Anyone who follows instructions could render their brand new computer useless!

CottonCandy
December 10th, 2010, 05:54 AM
Ok, got my repair & recovery disks made & uninstalled dell datasafe. I don't think I want to take a chance on updating the BIOS, so I'm all done except for reinstalling Grub2.

Do I install it to /dev/sda4 & then flag that partition as the boot partition in gparted like I was instructed earlier?
Or do I just install it to /dev/sda as instructed in https://help.ubuntu.com/community/Grub2#Reinstalling%20GRUB%202 since I uninstalled datasafe?

wilee-nilee
December 10th, 2010, 06:09 AM
Ok, got my repair & recovery disks made & uninstalled dell datasafe. I don't think I want to take a chance on updating the BIOS, so I'm all done except for reinstalling Grub2.

Do I install it to /dev/sda4 & then flag that partition as the boot partition in gparted like I was instructed earlier?
Or do I just install it to /dev/sda as instructed in https://help.ubuntu.com/community/Grub2#Reinstalling%20GRUB%202 since I uninstalled datasafe?

Post the output of this command in the Ubuntu live cd booted terminal and I will give you the commands, merry Christmas.;) copy and paste the command it is just to confirm the partitions one last time.


sudo fdisk -l

CottonCandy
December 10th, 2010, 06:40 AM
Why thank you. :) Here's the output:

ubuntu@ubuntu:~$ sudo fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xf6996217

Device Boot Start End Blocks Id System
/dev/sda1 60674 60802 1022976 c W95 FAT32 (LBA)
/dev/sda2 * 13 1926 15360000 7 HPFS/NTFS
/dev/sda3 1926 31736 239450136 7 HPFS/NTFS
/dev/sda4 31736 59698 224608256 83 Linux

Partition table entries are not in disk order



Just trying to figure out if I should use

sudo grub-install --root-directory=/mnt/ /dev/sda
or

sudo grub-install --boot-directory=/mnt/ --force /dev/sda4

wilee-nilee
December 10th, 2010, 06:45 AM
Everything is in the same place, so from the live cd run these two commands then reboot to the Ubuntu install and run the 3rd command.


sudo mount /dev/sda4 /mnt
then

sudo grub-install --root-directory=/mnt/ /dev/sda
reboot to install and then run.

sudo update-grub

And watch out for that eggnog it will catch up with you.;)

Here the grub2 link I used.
https://help.ubuntu.com/community/Grub2#Reinstalling%20GRUB%202

The second command is correct we want grub in the HD mbr=sda

wilee-nilee
December 10th, 2010, 06:54 AM
My commands are correct just copy and paste them if you type them wrong you will just have to do it again.

CottonCandy
December 10th, 2010, 07:04 AM
As long as

Generating grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.35-23-generic-pae
Found initrd image: /boot/initrd.img-2.6.35-23-generic-pae
Found memtest86+ image: /boot/memtest86+.bin
Found Windows 7 (loader) on /dev/sda2
doneis the right output for sudo update-grub, I should be ok now. :D

Going to try booting into win7 again then back into ubuntu to see if removing datasafe worked for me. I hope so!

Thank you again for your help!

CottonCandy
December 10th, 2010, 07:14 AM
Hooray! Into windows then back into ubuntu, no problems! :D Thank you so much for your help!

wilee-nilee
December 10th, 2010, 07:18 AM
Hooray! Into windows then back into ubuntu, no problems! :D Thank you so much for your help!

No problem I was a bit worried you might follow the other advice on not removing the, beast, dell data safe, now where's that holy water and the silver bullet for the next dell setup.;)