Re: Can't mount WinXP partition or boot to it. Will "fixboot" work?
- From: ANC <anc@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 10 Jul 2006 14:27:59 GMT
iforone wrote:
ANC wrote:
Have dual-boot XP with Kanotix. Used Qtparted to shrink XP to install
Linux. Linux boots fine. XP won't boot at all with grub... no error at
all, just pops up another grub menu.
What is more important is that I also can't mount the Win partition sda1.
Dmesg says:
NTFS-fs error (device sda1): ntfs_fill_super(): Not an NTFS volume.
NTFS-fs warning (device sda1): is_boot_sector_ntfs(): Invalid boot sector
checksum.
NTFS-fs error (device sda1): read_ntfs_boot_sector(): Primary boot sector
is invalid.
NTFS-fs error (device sda1): read_ntfs_boot_sector(): Mount option
errors=recover not used. Aborting without trying to recover.
The cfdisk program sees the partition ok.
Someone told me to boot with XP disc and run the "fixboot" program. Why
will that fix the mount problem. Seems to me that even if I can't boot, I
should be able to mount. So what does the "fixboot" thing do to the WinXP
boot sector (not mbr) and why will it work to let me mount (and boot?)
Is it possible "fixboot" will screw up something else? (I never trust
Windows utilities.)
Otherwise: While booted to linux, Please post the output of;
~$ cat /etc/fstab
al@kanotix1:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
usbfs /proc/bus/usb usbfs devmode=0666 0 0
/dev/sda2 / reiserfs defaults 0 1
#/dev/sda1 /media/sda1 ntfs ro,umask=000 0 0
/dev/sda1 /media/sda1 ntfs noauto,users,exec,ro,umask=000 0 0
/dev/sdb3 /media/sdb3 reiserfs noauto,users,exec 0 0
/dev/sdb4 /media/sdb4 reiserfs noauto,users,exec 0 0
/dev/sdb1 /media/sdb1 reiserfs noauto,users,exec 0 0
/dev/sdb2 none swap defaults 0 0
#/dev/cdrom /media/cdrom0 udf,iso9660 users,noauto 0 0
/dev/hdc /media/cdrom0 udf,iso9660 users,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
#none /sys sysfs defaults 0 0
sysfs /sys sysfs defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
~$ cat /etc/mtabal@kanotix1:~$ cat /etc/mtab
/dev/sda2 / reiserfs rw 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
usbfs /proc/bus/usb usbfs rw,devmode=0666 0 0
tmpfs /dev/shm tmpfs rw 0 0
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
tmpfs /dev tmpfs rw,size=10M,mode=0755 0 0
~$ mount
root@kanotix1:/home/al# mount
/dev/sda2 on / type reiserfs (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
usbfs on /proc/bus/usb type usbfs (rw,devmode=0666)
tmpfs on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev type tmpfs (rw,size=10M,mode=0755)
~$ sudo fdisk -l /dev/sda
(might as well post the info from fdisk for each/all your HDDs )
root@kanotix1:/home/al# fdisk -l /dev/sda
Disk /dev/sda: 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/sda1 * 1 5264 42282268 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 5265 6830 12578895 83 Linux
NOTICE ABOVE 'WARNING' ABOUT NOT ENDING ON A CYL BOUNDRY.
I'm getting all sorts of conflicting advice from various sources. Some
people say to run 'fixboot' from WinXP install disk. So how does fixing the
boot sector of sda1 (not mbr) have anything to do with mounting?
Another says to run XP 'chkdsk'. But that could make changes to sda2 (my
kanotix partition) right? Can't do that right now.
Another says to try ntfsfix but I'm not sure WHAT that will do, if anything.
Another says that the hard disk is borked and that sooner or later my sda2
partition will crap out because of the boundary thing... especially if I
reboot often. But I've been running it for 8 months now! And how would
rebooting change anything or cause sda1 to overlap into sda2?
Another said to try the gparted livecd and resize the sda1 partition again.
But what damage might that do to sda2, if any?
What version of Kanotix?
2005-04 the last stable release.
What was your setup like before you installed Kanotix?
I have 2 80 GB drives, sda and sdab. I always ran Linux on sda2. But the
last release of Kanotix had a problem with my controller chipset and would
not install to sdB, only to sdB. I had hosed my sdb by trying to install
PC-BSD... and had to delete some partitions, etc.... a mess... which I did
and installed Etch into sdB3. However, I didn't like Etch so I decided to
use sdA. All it had was WindowsXP and had never been used. I kept it just
in case I might need it (and now I do!).
OK, so I trotted out QTparted and resized sda1 from 80GB down to about 65
leaving 15 GB and created sda2. I then installed Kanotix. I changed the
Etch (sdb3) grub menu.lst to give me a boot choice for kanotix (I'm not a
newbie... am comfortable doing this stuff.) All worked great. I never
bothered to test sda1 (Windows) because I didn't need it and assume it
would be fine. Well now that I do need it (for one single program (it is
not fine.)
How many Hard disks, and are they SCSI, IDE, SATA ?
2 drives, both SATA
What OS(es) are installed where on these HDDs.?
sda1=WinXP
sda2=Kanotix
sdb1=empty
sdb2=swap
sdb3=Debian Etch
sdb4=Kubuntu
I use sdb1 and sdb4 to experiment with other distros. Etch is my 'backup
distro and where I boot to. But Kanotix on sda2 is my work-horse everyday
distro (and it's been stable like you would not believe... I'm a long-time
user of Kanotix and can't say enough good things about it.)
Did you install GRUB to the XPoop Boot sector as a file?
I hope not. No way to see as I can't mount it. However it might be, because
when I choose "Windows" in grub's menu.lst at boot time, it changes from a
blue/white grub menu to a black-with menu.... with no choice for Windows.
Looks like I'm starting up a new grub... and where did it come from? sda1?
Could be. BUT I STILL SHOULD BE ABLE TO MOUNT THE DAMN PARTITION.
Or did you install it to the MBR
I'm real careful with that. Only Etch installed it to the mbr... but maybe
I've fixed it a few times with (in grub):
root (hd1,2)
setup (hd0)
If the prior (the XP partition Boot sector area only), then you *may*
need to also modify Boot.ini as well as the GRUB file
I don't understand the question.
I'm not new to Linux, but I'm lost here. Obviously one answer is for me to
wait until the new release of Kanotix comes out (very soon now) and install
it to my empty partition on sdB1 and then hose sda and repartition it for
50 GB for Windows and then install Windows and then go back and fix the mbr
(which XP will clobber.) However, if there is an easy way to fix this one
damn Windows partition so I can boot the damn thing just to run this one
frickin' program, that's where I want to go today if I can.
Thanks,
Al
.
- Follow-Ups:
- Re: Can't mount WinXP partition or boot to it. Will "fixboot" work?
- From: Douglas Mayne
- Re: Can't mount WinXP partition or boot to it. Will "fixboot" work?
- References:
- Prev by Date: Re: having trouble mounting disk image on loopback device
- Next by Date: Re: ICQ + randomly changing keyboard layouts
- Previous by thread: Re: Can't mount WinXP partition or boot to it. Will "fixboot" work?
- Next by thread: Re: Can't mount WinXP partition or boot to it. Will "fixboot" work?
- Index(es):
Relevant Pages
|
