I cannot open Windows XP after dual boot

The previous question is here

https://answers.launchpad.net/ubuntu/+question/80374

and contains the output of "sudo fdisk -l".

Err what seems to be missing (bizarrely none of us asked for it) is your menu.lst. Please get to a command-line and type in (o copy&paste with the mouse)

cd /boot/grub
dir
sudo cp menu.lst menu.lst-100909
dir
gedit menu.lst

note that "menu.lst" is a lower-case "MENU.LST"
Good luck and regards from
Tom :)

Hi Tom. Thank you for the email.

However I did try the following:-

   " sudo mkdir /media/Windows "

   " sudo fdisk -l "

and got this response:-

  " Disk /dev/sda: 40.0 GB, 40060403712 bytes
255 heads, 63 sectors/track, 4870 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xef4fef4f

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 3240 26025268+ 7 HPFS/NTFS
/dev/sda2 4591 4870 2249100 82 Linux swap /
Solaris
/dev/sda3 3241 4577 10739452+ 83 Linux

Partition table entries are not in disk order "

when I tried to mount '/dev/sda1' I got the following response...

  "brian@brian-kratos:~$ sudo mount /dev/sda1 /media/Windows
$MFTMirr does not match $MFT (record 1).
Failed to mount '/dev/sda1': Input/output error
NTFS is either inconsistent, or you have hardware faults, or you have a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows TWICE. The usage of the /f parameter is very
important! If you have SoftRAID/FakeRAID then first you must activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for the details."

                This all leaves me none the wiser !

        I am using the DVD Version 8.04 LTS which accompanied the 'The
Official
ubuntu Book' and I am wondering whether to try and save my files that I
have got to work and then just try and load/install 'ubuntu 9.04' which
I have downloaded on to DVD which I have burnt.

Cheers Brian

On Thu, 2009-09-10 at 22:23 +0000, Tom wrote:
> Your question #82444 on grub in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/grub/+question/82444
>
> Status: Open => Answered
>
> Tom proposed the following answer:
> The previous question is here
>
> https://answers.launchpad.net/ubuntu/+question/80374
>
> and contains the output of "sudo fdisk -l".
>

Hi Tom. I copied and pasted what you gave me below and got the
following:-

brian@brian-kratos:~$ cd /boot/grub
brian@brian-kratos:/boot/grub$ dir
default installed-version minix_stage1_5 xfs_stage1_5
device.map jfs_stage1_5 reiserfs_stage1_5
e2fs_stage1_5 menu.lst stage1
fat_stage1_5 menu.lst~ stage2
brian@brian-kratos:/boot/grub$ sudo cp menu.lst menu.lst-100909
[sudo] password for brian:
brian@brian-kratos:/boot/grub$

cheers brian

On Thu, 2009-09-10 at 22:26 +0000, Tom wrote:
> Your question #82444 on grub in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/grub/+question/82444
>
> Tom proposed the following answer:
> Err what seems to be missing (bizarrely none of us asked for it) is your
> menu.lst. Please get to a command-line and type in (o copy&paste with
> the mouse)
>
> cd /boot/grub
> dir
> sudo cp menu.lst menu.lst-100909
> dir
> gedit menu.lst
>
> note that "menu.lst" is a lower-case "MENU.LST"
> Good luck and regards from
> Tom :)
>

Hi :)

I think you are ok booting into the Ubuntu that is on your hard-drive? There's no need to use a LiveCd session, note that we call it LiveCd even if it's done using a dvd, or often even if its done from a usb-stick!

Ok so the "cp" command created a copy of the "MENU.LST" file and typing in

cd /boot/grub
dir

now will show an additional file called "menu.lst-100909". Note the previous time it showed you these files "default installed-version minix_stage1_5 xfs_stage1_5 device.map jfs_stage1_5 reiserfs_stage1_5
e2fs_stage1_5 menu.lst stage1 fat_stage1_5 menu.lst~ stage2".

So, now we can safely edit your menu.lst and know that if it goes wrong we can get the old one back using a LiveCd session.

Note that making the ubuntu sio into a dvd is not always as easy as using a really cheap CD. I find the best plan is to get those really cheap "write once" or "record once" blank CDs that can normally only be bought in packs of 10 or more. For some reason these seem to work better than more expensive kinds. I think the more expensive ones might be optimised for storing data for the long-term rather than for creating boot disks.

Please can you do

gedit /boot/grub/menu.lst

and copy&paste the contents of that into here? Also on a command-line please type

fsck -h

to get a quick help cheat-sheet on how to use the "fsck" command. I think that we need to add full ntfs support to your ubuntu first tho so type in

sudo apt-get install ntfsprogs
sudo apt-get install ntfs-3g

as sometimes these aren't included in a basic install <sighs >
Ok, good luck with all that!
regards from
Tom :)

Hi Tom I type in the suggestions you gave me. Your suggestions
read from top to bottom but my responses go from bottom to top !!!

I just did them in the order you gave me and then pasted to the top of
this email. Hence order reversal....

Than you once again for your help

cheers brian

This is the result of

> sudo apt-get install ntfsprogs
> sudo apt-get install ntfs-3g
>
>
> brian@brian-kratos:~$
> brian@brian-kratos:~$ > sudo apt-get install ntfsprogs
> E: Could not open lock file /var/lib/dpkg/lock - open (13 Permission denied)
> E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
> brian@brian-kratos:~$ > sudo apt-get install ntfs-3g
>
>
>
........................................................

 This is the result of fsck -h

brian@brian-kratos:~$ gedit /boot/grub/menu.lst
brian@brian-kratos:~$ fsck -h
fsck 1.40.8 (13-Mar-2008)
fsck.ext3: invalid option -- h
Usage: fsck.ext3 [-panyrcdfvstDFSV] [-b superblock] [-B blocksize]
  [-I inode_buffer_blocks] [-P process_inode_size]
  [-l|-L bad_blocks_file] [-C fd] [-j external_journal]
  [-E extended-options] device

Emergency help:
 -p Automatic repair (no questions)
 -n Make no changes to the filesystem
 -y Assume "yes" to all questions
 -c Check for bad blocks and add them to the badblock
list
 -f Force checking even if filesystem is marked clean
 -v Be verbose
 -b superblock Use alternative superblock
 -B blocksize Force blocksize when looking for superblock
 -j external_journal Set location of the external journal
 -l bad_blocks_file Add to badblocks list
 -L bad_blocks_file Set badblocks list
brian@brian-kratos:~$

..................................................

This is the result of gedit /boot/grub/menu.lst

# 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 use 'savedefault' 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 3

## 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=322bb751-afe3-4b81-82c3-8258676cba08 ro

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

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

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

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title Ubuntu 8.04.2, kernel 2.6.24-24-generic
root (hd0,2)
kernel /boot/vmlinuz-2.6.24-24-generic
root=UUID=322bb751-afe3-4b81-82c3-8258676cba08 ro quiet splash
initrd /boot/initrd.img-2.6.24-24-generic
quiet

title Ubuntu 8.04.2, kernel 2.6.24-24-generic (recovery mode)
root (hd0,2)
kernel /boot/vmlinuz-2.6.24-24-generic
root=UUID=322bb751-afe3-4b81-82c3-8258676cba08 ro single
initrd /boot/initrd.img-2.6.24-24-generic

title Ubuntu 8.04.2, kernel 2.6.24-16-generic
root (hd0,2)
kernel /boot/vmlinuz-2.6.24-16-generic
root=UUID=322bb751-afe3-4b81-82c3-8258676cba08 ro quiet splash
initrd /boot/initrd.img-2.6.24-16-generic
quiet

title Ubuntu 8.04.2, kernel 2.6.24-16-generic (recovery mode)
root (hd0,2)
kernel /boot/vmlinuz-2.6.24-16-generic
root=UUID=322bb751-afe3-4b81-82c3-8258676cba08 ro single
initrd /boot/initrd.img-2.6.24-16-generic

title Ubuntu 8.04.2, memtest86+
root (hd0,2)
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

......................................................

This is the result of cd /boot/grub
dir :-

# 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 use 'savedefault' 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 3

## 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=322bb751-afe3-4b81-82c3-8258676cba08 ro

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

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

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

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title Ubuntu 8.04.2, kernel 2.6.24-24-generic
root (hd0,2)
kernel /boot/vmlinuz-2.6.24-24-generic
root=UUID=322bb751-afe3-4b81-82c3-8258676cba08 ro quiet splash
initrd /boot/initrd.img-2.6.24-24-generic
quiet

title Ubuntu 8.04.2, kernel 2.6.24-24-generic (recovery mode)
root (hd0,2)
kernel /boot/vmlinuz-2.6.24-24-generic
root=UUID=322bb751-afe3-4b81-82c3-8258676cba08 ro single
initrd /boot/initrd.img-2.6.24-24-generic

title Ubuntu 8.04.2, kernel 2.6.24-16-generic
root (hd0,2)
kernel /boot/vmlinuz-2.6.24-16-generic
root=UUID=322bb751-afe3-4b81-82c3-8258676cba08 ro quiet splash
initrd /boot/initrd.img-2.6.24-16-generic
quiet

title Ubuntu 8.04.2, kernel 2.6.24-16-generic (recovery mode)
root (hd0,2)
kernel /boot/vmlinuz-2.6.24-16-generic
root=UUID=322bb751-afe3-4b81-82c3-8258676cba08 ro single
initrd /boot/initrd.img-2.6.24-16-generic

title Ubuntu 8.04.2, memtest86+
root (hd0,2)
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

.............................................

On Fri, 2009-09-11 at 07:31 +0000, Tom wrote:
> Your question #82444 on grub in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/grub/+question/82444
>
> Status: Open => Answered
>
> Tom proposed the following answer:
> Hi :)
>
> I think you are ok booting into the Ubuntu that is on your hard-drive?
> There's no need to use a LiveCd session, note that we call it LiveCd
> even if it's done using a dvd, or often even if its done from a usb-
> stick!
>
> Ok so the "cp" command created a copy of the "MENU.LST" file and typing
> in
>
> cd /boot/grub
> dir
>
> now will show an additional file called "menu.lst-100909". Note the previous time it showed you these files "default installed-version minix_stage1_5 xfs_stage1_5 device.map jfs_stage1_5 reiserfs_stage1_5
> e2fs_stage1_5 menu.lst stage1 fat_stage1_5 menu.lst~ stage2".
>
> So, now we can safely edit your menu.lst and know that if it goes wrong
> we can get the old one back using a LiveCd session.
>
> Note that making the ubuntu sio into a dvd is not always as easy as
> using a really cheap CD. I find the best plan is to get those really
> cheap "write once" or "record once" blank CDs that can normally only be
> bought in packs of 10 or more. For some reason these seem to work
> better than more expensive kinds. I think the more expensive ones might
> be optimised for storing data for the long-term rather than for creating
> boot disks.
>
> Please can you do
>
> gedit /boot/grub/menu.lst
>
> and copy&paste the contents of that into here? Also on a command-line
> please type
>
> fsck -h
>
> to get a quick help cheat-sheet on how to use the "fsck" command. I
> think that we need to add full ntfs support to your ubuntu first tho so
> type in
>
> sudo apt-get install ntfsprogs
> sudo apt-get install ntfs-3g
>
> as sometimes these aren't included in a basic install <sighs >
> Ok, good luck with all that!
> regards from
> Tom :)
>

Hi :)

Please try to follow the links to this thread at the launchpad website rather than replying by email - although i think you did it right this time :)

The

sudo apt-get install ntfsprogs
sudo apt-get install ntfs-3g

commands didn't work. Do you have "Add/Remove Applications" or "Synaptic Package Manager" open? If Synaptic is already open then try searching for the 2 packages "ntfsprogs" and "ntfs-3g" in there and install them from there instead. All 3 methods of installing programs/packages use the same databases and repos so you can only use 1 of them at any particular time. I keep switching between Synaptic and using the command-line's "apt-get" because each has their advantages.

Ok, so please try installing "ntfsprogs" and "ntfs-3g" again.
Good luck and regards from
Tom :)

Hi again :)

I wanted to make sure you got the full menu.lst into here? Isn't there a stanza at the end that looks like this?

# This is a divider, added to separate the menu items below
title Windows XP
root (hd0,0)
savedefault
makeactive
chainloader +1

To edit menu.lst just type this into the command-line

sudo gedit /boot/grub/menu.lst

Now you should be able to add the Windows stanza and save the menu.lst file.

Good luck and regards from
Tom :)

Hi ...I have reinstalled the two NTFS programmes and then tried to open my 26 GB Media file. Thsi would not happen and instead got two messages as follows:-

You are not privileged to mount this volume.

DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

This is a puzzle!
Cheers Brian

Hi :)

So is Ubuntu booting normally now? Can you boot into Windows yet? Please use

sudo gedit /boot/grub/menu.lst

to add this stanza to the bottom of the menu.lst

# This is a divider, added to separate the menu items below
title Windows XP
root (hd0,0)
savedefault
makeactive
chainloader +1

Also please can you try these 2 commands to see if either gives any info about error checking ntfs partitions

fsck -h
fsck.ntfs -h

I have a feeling the 2nd one wont help at all. I still need to look up something that is bugging me about this. Please let us know how this goes, particularly if adding that stanza to the menu.lst does allow you to boot into Windows ;)
Thanks, good luck and regards from
Tom :)

Hi Tom. Ubuntu I can boot but Windows NO.

I have added the stanza to the end of the menu list.

I tried to open 26 GB Media file in all my Windows material is hiding
but no luck. I was told it cannot be mounted nd then it said it was
opening "26 GB Media" and THEN !!!! it tells me "Unable to mount
location" !!!

I have already sent you the results of checking these two commands
fsck -h
> fsck.ntfs -h
>
> That is the situation to date.
>
> I was rather expecting that when I turned on my pc I would be given the choice of either
> Ubuntu or Windows but I only get Ubuntu, no choice.
>
> Thanks for your help thus far.
>
> cheers Brian

On Sun, 2009-09-13 at 09:03 +0000, Tom wrote:
> Your question #82444 on grub in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/grub/+question/82444
>
> Status: Open => Answered
>
> Tom proposed the following answer:
> Hi :)
>
> So is Ubuntu booting normally now? Can you boot into Windows yet?
> Please use
>
> sudo gedit /boot/grub/menu.lst
>
> to add this stanza to the bottom of the menu.lst
>
> # This is a divider, added to separate the menu items below
> title Windows XP
> root (hd0,0)
> savedefault
> makeactive
> chainloader +1
>
> Also please can you try these 2 commands to see if either gives any info
> about error checking ntfs partitions
>
> fsck -h
> fsck.ntfs -h
>
> I have a feeling the 2nd one wont help at all. I still need to look up something that is bugging me about this. Please let us know how this goes, particularly if adding that stanza to the menu.lst does allow you to boot into Windows ;)
> Thanks, good luck and regards from
> Tom :)
>

Hi :)

Ok, now that you have ntfsprogs and ntfs-3g it should be possible to do this command

sudo fsck /dev/sda1

Hopefully that should fix the file-system on sda1. If it completes very very fast or otherwise gives some indication that it might not have done anything then try

sudo fsck /dev/sda1 -h

for some reason it's difficult to get the quick help cheat-sheet for this command for Windows partitions and the cheat sheet does seem to be a little different for Windows partitions. I found that 2nd command seemed to do the trick tho :)

Good luck and regards from
Tom :)

Hi Tom. thanks for the email. I put in the 2 commands and you
suggested and got a 'rude' message..

I re-installed both of the ntfs programs from Synaptic Package manager
and tried again and I got the same message as follows :-

brian@brian-kratos:~$ sudo fsck /dev/sda1
fsck 1.40.8 (13-Mar-2008)
fsck: fsck.ntfs-3g: not found
fsck: Error 2 while executing fsck.ntfs-3g for /dev/sda1
brian@brian-kratos:~$ sudo fsck /dev/sda1 -h
fsck 1.40.8 (13-Mar-2008)
fsck: fsck.ntfs-3g: not found
fsck: Error 2 while executing fsck.ntfs-3g for /dev/sda1
brian@brian-kratos:~$

I am puzzled.. cheers brian

On Mon, 2009-09-14 at 08:20 +0000, Tom wrote:
> Your question #82444 on grub in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/grub/+question/82444
>
> Status: Open => Answered
>
> Tom proposed the following answer:
> Hi :)
>
> Ok, now that you have ntfsprogs and ntfs-3g it should be possible to do
> this command
>
> sudo fsck /dev/sda1
>
> Hopefully that should fix the file-system on sda1. If it completes very
> very fast or otherwise gives some indication that it might not have done
> anything then try
>
> sudo fsck /dev/sda1 -h
>
> for some reason it's difficult to get the quick help cheat-sheet for
> this command for Windows partitions and the cheat sheet does seem to be
> a little different for Windows partitions. I found that 2nd command
> seemed to do the trick tho :)
>
> Good luck and regards from
> Tom :)
>

I will start again so I am marking this problem as solved.

Many thanks for all the suggestions that were offered.

cheers brian

Hi Tom well I wll be off the air for a while as I am going to start
again. !!

I have marked the problem as solved so this will now provide a 'natural
break' !!! Thank you for all of your help.

cheers brian .

On Mon, 2009-09-14 at 21:30 +0000, Tom wrote:
> Your question #82444 on grub in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/grub/+question/82444
>
> Status: Open => Answered
>
> Tom proposed the following answer:
> Hi :)
>
> Things are clearly not going according to plan and i would definitely
> recommend checking that you have backed up to external drive or dvds all
> your critical data, family photos and anything else like that as well.
>
> Do you have a Windows Cd, perhaps a Windows Recovery Cd for the machine
> or something like that? Usually they give an option to repair a WIndows
> install but this often runs the risk of wiping the data on the Windows
> side (and potentially on the linux partitions too). After using a
> Windows recovery cd we can fix the grub again fairly easily from the
> LiveCd.
>
> I take it then when you boot into the Ubuntu that is on your hard-drive
> Synaptic shows that you have installed ntfsprogs and ntfs-3g? and that
> it's the hard-drive install of ubuntu that is refusing to let you do an
> "fsck" scan of the ntfs partition?
>
> There are a few more tricks but these mainly involve using other specialist distros such as the new release of SystemRescueCd but i would consider GPartEd LiveCd or TrinityRescueKit too
> http://distrowatch.com/table.php?distribution=systemrescue
> http://distrowatch.com/table.php?distribution=gparted
> http://distrowatch.com/table.php?distribution=trinity
> My favourite would be Trinity because they are a friendly bunch and have a nice forum yet they are much less well-known. The main down-side is that they have so many tools packed onto their Cd that they didn't have room for a gui desktop and so their LiveCd only runs a command-line. However, their documentation and forums are good so i would be tempted to go with tem. Most people seem to use SystemRescue or GPartEdLive purely because they are the more famous distros. So i guess i would try one and if i didn't like using it then i would try another. Really all we need these for (hopefully) is to scan and fix errors on the ntfs partitions, any of the 3 should be able to do that quite easil, probably in many different ways :)
>
> Good luck and regards from
> Tom :)
>

Hi :)

Errr, have you been able to download and make a LiveCd of 1 of those 3 rescue distros? I would definitely do that first so that you do have access to them if/while everything else is in a temporary state of not-working.

Another good LiveCd to have is sliTaz because it is so tiny that when you run it's LiveCd you can take it's Cd out of the cd/dvd-drive! It does this by loading itself entirely into Ram which takes a little while at boot-up but does give quite a massive advantage
http://distrowatch.com/table.php?distribution=slitaz

Anyway remember to check the md5sum whenever you download an iso before making the iso into a Cd
https://help.ubuntu.com/community/HowToMD5SUM
Here's a guide that might help make a really decent LiveCd
https://help.ubuntu.com/community/BurningIsoHowto

And don't forget you can use the Ubuntu Cd as a LiveCd so you don't need to be completely without us for long
https://help.ubuntu.com/community/LiveCD

Also this video might help you with the partitioning section of the Ubuntu installer
http://static.screencasts.ubuntu.com/2009/09/03/Ubuntu_Partitioning.ogv

Good luck and regards from
Tom :)

Hmm, i tried to find out who made the video so that i could give them credit when i post the link but now i seem to be unable to play that excellent video even tho i can play another link i have which is made by the same chap. Please let me know if that last video link i gave doesn't work for you too.

Regards from
Tom )

Hi :)

Have you been able to test the new Ubuntu 10.04 before it gets officially released?
http://www.ubuntulinux.org/testing/lucid/beta1
Trying it as a LiveCd or as an extra dual/multi-boot would be ideal. Developers and everyone are keen to try to iron out any problems before 10.04 gets officially released so you might find faster & more effective answers to your bug reports which would make 10.04 work better on your system for you

Thanks and regards from
Tom :)