Author Topic: Filesystem Type Unknown, Partition Type 0x7 - Dual Boot Linux/Windows  (Read 8020 times)

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11561
  • ----IOFLU----
I am not certain that I understand all of what you just said. I feel certain that in my explanation I have used words sloppily such as to derail you. I will try again....

GRUB was used as the bootloader. On the subject PC and at the point where GRUB reads from menu.lst, I have the option of choosing to boot into PCLinuxOS (either with or without safemode) or into XP. When the XP option was chosen, the error message would appear. That has been the problem from the onset and it is real to me (and at least a few hundred others based upon my internet research). If the filesystem was not corrupt, then the error message is in error, itself. 

Do you really believe that the partition filesystem was not corrupt??

I have no way of knowing, at this point, one way or the other. You only reported what you did after the fact, so there's no way of verifying what you did, or what the actual state of the system was before. If we take your word for it, all we know for certain is there was the appearance of a problem, and it now appears to have been fixed. What the actual problem was is unknown, and that being the case, so is the actual solution. Whether the steps you took were in fact the cause of the fix, or were coincidental to the actual fix is also not a certainty.

Normally when a problem occurs, we have a number of tests we do, in an orderly fashion, to determine what the actual source, and extent of the problem is, and from that information derive a proper means of fixing it, using known and proven methods.  Without any verifiable test results, we can only speculate as to what the true condition of the system was, if your actions had any specific cause and effect relationship to the fix, or if it was just a happy accident that the system righted itself, before your actions damaged it further.

The best I can offer at this point is that I'm glad it seems to be working properly now, and I hope it stays that way for you.
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11561
  • ----IOFLU----
I'm not sure if this helps, but I think I have figured out what is going with my system and this error, although I haven't fixed it.

As a refresher, my system is set up like this:

SATA 80GB with Windows XP 64-bit installed

SATA 120GB with large NTFS partition and PCLOS 2010 Gnome installed (/,/home, and swap)

The 80GB is primary in the BIOS, the 120GB secondary.

The 120GB is set as the boot device.

In setting up GRUB using the Control Center I see the 80GB as Windows and as sda, while the 120GB is sdb.

When I try to boot Windows from Grub I get the error initially posted, and noticed it is showing (1,0) as the drive, which would seem to indicate it is looking at the second hard drive, not the first (it is looking at sdb1 rather than sda1).

For both BIOS and grub, the boot drive is always (hd0) so a second drive will by definition be (hd1) If you are booting from the Linux drive, with Windows on its own drive, that drive is for that moment (hd1). If windows is installed on the first partition, that partition is (hd1,0).  If you wish to boot Windows from grub, under those conditions, the proper Windows grub stanza would be;

title Windows
    rootnoverify (hd1,0)
    map (hd1) (hd0)
    map (hd0) (hd1)
    makeactive
    chainloader +1


Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline gungaden

  • Full Member
  • ***
  • Posts: 193
  • Bhisti, 2nd class

Normally when a problem occurs, we have a number of tests we do, in an orderly fashion, to determine what the actual source, and extent of the problem is, and from that information derive a proper means of fixing it, using known and proven methods.  Without any verifiable test results, we can only speculate as to what the true condition of the system was, if your actions had any specific cause and effect relationship to the fix, or if it was just a happy accident that the system righted itself, before your actions damaged it further.

The best I can offer at this point is that I'm glad it seems to be working properly now, and I hope it stays that way for you.

OP, I searched diligently in hope of finding such orderly steps to troubleshoot and fix this problem. I could find none. I promise that I have not exaggerated nor misstated any conditions of my system, nor actions I performed, nor results obtained. I recognize that the problem is perplexing to you and therefore you are skeptical that I properly researched, tested, or observed. Nevertheless, there are many people experiencing the same problem in attempting to get Linux to dual-boot with an existing Windows installation. If you research this specific error code, very few of those people are receiving tangible assistance in correcting the problem, other than a complete reinstallation of Windows, which is often undesirable. My only intent was to relate what worked for me and thus perhaps save someone else some time. One thing is for certain, orderly steps or not, sheer luck or not, I see no one getting any on-target advice on this particular error.

I thank you for taking the time to provide your views.

Offline Never_More

  • Full Member
  • ***
  • Posts: 138
I would suggest you repartition your hard drive and reinstall windows first then the other partition should be the linux part of it.

My computer geek score is greater than 100% of all people in the world! How do you compare? Click here to find out!



Greets
Never More

Offline pelone

  • Jr. Member
  • **
  • Posts: 14
I have had this problem too using Parted Magic a few months back. It seems Gparted was rounding blocks into the Windows partition. Windows of course was literal in what it thought it had. The best solution I came up with was using another distro to partition with which had a different release of Gparted. I think it was a copy error in the CD but that is only a guess.

pelone

Offline joec

  • Full Member
  • ***
  • Posts: 56
Re: Filesystem Type Unknown, Partition Type 0x7 - Dual Boot Linux/Windows
« Reply #20 on: June 02, 2010, 10:52:58 PM »
redombr  just worked for me on this type of problem. If you have a partition preceding the windows partition then grub may set itself up to point to hd0,0   when it should point to hd0,1

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11561
  • ----IOFLU----
Re: Filesystem Type Unknown, Partition Type 0x7 - Dual Boot Linux/Windows
« Reply #21 on: June 02, 2010, 11:39:45 PM »
redombr  just worked for me on this type of problem. If you have a partition preceding the windows partition then grub may set itself up to point to hd0,0   when it should point to hd0,1

Grub is not supposed to point to any specific partition; it points to where the grub files actually are, wherever that may be. If Windows is installed on (hd0,1) grub should certainly not be pointed there.

grub> find /boot/grub/stage2
 (hd0,0)
 (hd1,0)
 (hd1,6)
 (hd2,0)
 (hd2,6)
 (hd2,7)
 (hd2,8)
 (hd2,12)
 (hd2,13)
 (hd2,14)
 (hd3,0)
 (hd3,7)

Any one of the partitions listed could be chosen by me as my master grub partition. As I have 4 hard drives with a boot partition on each, each MBR has grub installed to it, from the boot partition on that drive, so each is bootable in its own right. If any one of the MBRs becomes corrupted, any other drives can be designated as the boot drive and all my installations would then be bootable from there.
« Last Edit: June 02, 2010, 11:56:31 PM by old-polack »
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline joec

  • Full Member
  • ***
  • Posts: 56
Re: Filesystem Type Unknown, Partition Type 0x7 - Dual Boot Linux/Windows
« Reply #22 on: June 03, 2010, 07:10:29 PM »
You are right old-polack and i should know better than to post using imprecise language late at night after a frustrating dual boot install. sorry.
this is what i changed using Restore MBR:

title windows
root (hd0,1)
makeactive
chainloader +1


(hd0,1) was originally (hd0,0)