Community
cancel
Showing results for 
Search instead for 
Did you mean: 
idata
Community Manager
1,275 Views

Intel 520 SSD unreadable for Linux after using Acronis align tool

Hi,

I just switched my system to a Intel 520 SSD. I'm using Win Xp Pro as main system, and occasionally a Linux.

I moved the old content to the new SSD with the use of gparted (linux part editor).

The new system worked fine (and fast), right from the beginning.

Then I installed the two tools, that are mentioned on the Intel page (the Intel SSD Toolkit and the Acronis align tool).

Then I did the aligning with the acronis tool.

The system still works without any prob under Windows, but Linux is not capable of recognizing the disk anymore. gparted just reports overlapping partitions...

BTW, there are 3 partitions on the disk:

* 1GB FAT32 (basic boot partition, for easier interchange between various OS)

* 80GB NTFS (Windows)

* 20GB NTFS (Temp)

(rest unused for better handling of the SSD)

What's the problem here? And how can I go back again (if this is anyhow possible), for I personally didn't recognize much difference in speed between unaligned and aligned, but would surely wanna have the disk accessible under Linux.

0 Kudos
1 Reply
idata
Community Manager
140 Views

Now, I had a look at the partition table with fdisk:

Disk /dev/sda: 120.0 GB, 120034123776 bytes

255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors

Units = sectors of 1 * 512 = 512 bytes

Disk identifier: 0xf3a9f3a9

Device Boot Start End Blocks Id System

/dev/sda1 * 2048 2039807 1018880 b W95 FAT32

/dev/sda2 2039808 207832904 102896548+ 5 Extended

/dev/sda5 2041856 165885951 81922048 7 HPFS/NTFS

/dev/sda6 165888000 207833087 20972544 7 HPFS/NTFS

Now it's obvious. The Acronis Align Tool from the Intel Site created a faulty partition table!

Why are you propagation such faulty tools on your website???

I actually bought an Intel product, for you're famous to only propagate tested and working things.

Obviously the tools aligned all 3 partitions. But it didn't correct the extended partition, wherein the 2 logical partitions lie. Now the end of the 3rd partition doesn't lie anymore within the extended partition!

What way is there to correct this faulty partition table?

Reply