Jump to content

Corrupted partition but still alive


^GoJo^
 Share

12 posts in this topic

Recommended Posts

Hello,

 

I have a trouble with my Snow Leopard netbook partition, i'm not sure like that now anyway, here's the story :

 

I took off that hard drive and i did plug it in my desktop computer to restore the Windows partition with Acronis True Image.

 

I didn't touch the OSX partition at all. After restore was done i maybe set wrong partition as active (one that contains no system).

 

So of course it didn't boot, i found that mistake and set the OSX partition as active, then restarted and got "Boot0 done but memory allocation error".

 

Since i didn't have the solution, i took the hard drive and plug it back in my desktop to save files from my OSX partition, just in case something worse happen.

 

So as you can guess, i use MacDrive on my desktop Windows to browse HFS partitions. Since i also have OSX on my desktop, i started it, to see if i can fix the {censored}.

 

The thing is... The partition is now seen as a NTFS partition but cannot be mounted, fixed... Nothing! While MacDrive on Windows can see and let me browse it perfectly.

 

I bet that once again i'm having a quite weird/unknown problem but i hope someone will have some idea to let me fix it or at least know why this happened... Waiting for you ;)

 

Thanks.

Link to comment
Share on other sites

Not sure how MacDrive on windows checks file system type vs how OS X checks file system type, but you could boot into a linux live cd and see what it sees the drive as. While your in there, fire up fdisk and you can use it to manually set the partition type, ie.. whether its a fat, hfs, ntfs, whatever. You might be able to do that under OS X, but the Mac version of fdisk is kinda wonky and I don't usually use it.

 

Overall, I'd say your imaging mucked something up. I've never had much luck with Acronis. Try Winclone under OS X if you are trying to save/restore windows partitions. As for me, I would just get my data off and reinstall both Windows and OS X (in that order). That way you are sure your disk is setup correctly and it will be much easier to get things working. Always always always install Windows second.

Link to comment
Share on other sites

Yes finally that's what i did, i just deleted that fuc**** partition and made clean install of all, with different method so i'm not running 10.6.4 and everything works, even more than before! Only thing changed is sleep function (check my other post in this section)...

Link to comment
Share on other sites

  • 2 weeks later...

Ok now i'm really pissed off, the same thing happened with another disk and it {censored}ed ALL MY OSX PARTITIONS!!!! Just using MacDrive {censored} them even though i disconnect the disk properly. I want to fix them now. How do i do? Same as before, MAC see them as NTFS but other as HFS... {censored} MacDrive!!!! :)

Link to comment
Share on other sites

Hello,

 

I have a trouble with my Snow Leopard netbook partition, i'm not sure like that now anyway, here's the story :

 

I took off that hard drive and i did plug it in my desktop computer to restore the Windows partition with Acronis True Image.

 

I didn't touch the OSX partition at all. After restore was done i maybe set wrong partition as active (one that contains no system).

 

So of course it didn't boot, i found that mistake and set the OSX partition as active, then restarted and got "Boot0 done but memory allocation error".

 

Since i didn't have the solution, i took the hard drive and plug it back in my desktop to save files from my OSX partition, just in case something worse happen.

 

So as you can guess, i use MacDrive on my desktop Windows to browse HFS partitions. Since i also have OSX on my desktop, i started it, to see if i can fix the {censored}.

 

The thing is... The partition is now seen as a NTFS partition but cannot be mounted, fixed... Nothing! While MacDrive on Windows can see and let me browse it perfectly.

 

I bet that once again i'm having a quite weird/unknown problem but i hope someone will have some idea to let me fix it or at least know why this happened... Waiting for you ;)

 

Thanks.

 

 

Thanks you for the post.

 

;):):P:P:P

 

__________________

Watch Resident Evil: Afterlife Online Free

Link to comment
Share on other sites

I seem to recall hearing that MacDrive incorrectly sets the partition type code of HFS+ partitions to 0x07 (they should be 0xAF). I believe this can be fixed with the OS X fdisk program, but I'm not very familiar with it. Check its man page if you want to figure it out. I'm more familiar with Linux's fdisk. If you've got a Linux installation, or a Linux emergency disk, you can launch fdisk on the disk, type "p" to view the partitions, and then type "t" to change the type of the OS X partition. (You'll need to know the partition number, hence using "p" to try to identify it from its size.) When you're done, type "w" to save the changes.

Link to comment
Share on other sites

I have an Ubuntu live, i went on terminal, but if i type fdisk -t or fdisk -n it says that it's not an avalaible option...

 

So how do i do? By the way, Gparted show those partitions as HFS+...

 

Thanks you for the post.

Uh??? Why? I guess you were not talking to me...

Link to comment
Share on other sites

I have an Ubuntu live, i went on terminal, but if i type fdisk -t or fdisk -n it says that it's not an avalaible option...

 

I'm not sure why you were trying to use -t or -n with Linux's fdisk. Despite having the same name, Linux's fdisk and OS X's fdisk are two entirely different programs. To use Linux's fdisk, you'd do something like this:

 

# fdisk /dev/sdc

Command (m for help): p

Disk /dev/sdc: 16.2 GB, 16166944768 bytes
255 heads, 63 sectors/track, 1965 cylinders, total 31576064 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

  Device Boot	  Start		 End	  Blocks   Id  System
/dev/sdc1			2048	16779263	 8388608	7  HPFS/NTFS
/dev/sdc2		16779264	31576030	 7398383+  af  HFS / HFS+

Command (m for help): t
Partition number (1-4): 1
Hex code (type L to list codes): af
Changed system type of partition 1 to af (HFS / HFS+)

Command (m for help): p

Disk /dev/sdc: 16.2 GB, 16166944768 bytes
255 heads, 63 sectors/track, 1965 cylinders, total 31576064 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

  Device Boot	  Start		 End	  Blocks   Id  System
/dev/sdc1			2048	16779263	 8388608   af  HFS / HFS+
/dev/sdc2		16779264	31576030	 7398383+  af  HFS / HFS+

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.

 

Once in fdisk, "p" displays the partition table. In this example, it showed one NTFS and one HFS/HFS+ partition. For the sake of this demonstration, I assumed both should be HFS/HFS+, so I typed "t" to change the partition type code, entered "1" for the partition number, and entered "af" as the type code. I then verified that I'd done the right thing (using "p" again) and exited while saving changes by typing "w".

 

By the way, Gparted show those partitions as HFS+...

 

That's because GParted doesn't tell you anything about partition type codes; it looks inside the partitions to identify the filesystems they actually contain. The type codes, OTOH, aren't part of the data inside the partitions; rather, they're part of the data that defines the partitions (like their locations on the disk, their sizes, etc.). Many OSes use type codes to determine how to treat partitions, so if the type code doesn't match the type of filesystem actually on the partition, wackiness can happen. I suspect this is what's happened to you, but I'm not positive of that.

Link to comment
Share on other sites

 Share

×
×
  • Create New...