Will BING/BIBM have problems with an AF aligned drive?

User discussion and information resource forum for BootIt Next Generation

Re: Will BING/BIBM have problems with an AF aligned drive?

Postby TeraByte Support » Tue Jan 29, 2013 12:55 am

You can also just enable the Limit Primaries options.

Also, you can use BIBM to align, just enable the 2048 alignment in settings, then ensure there is a gap after the last partition (typically will be as cylinder alignment has unused sectors at the end of the drive), if not, resize 1M smaller (you may have to tell it 2M smaller depending on where the alignment is at), then slide (leave existing values) and click okay , then do the same thing working backwards (towards top) if there any more partitions. If you care to align the end, resize after the slide to same size as well. The slide is the operation that will take the longest.

TeraByte Support(PP) wrote:
> It's best to convert to MBR before making those types of changes or align
> using BING/BIBM.
TeraByte Support
 
Posts: 2313
Joined: Thu May 05, 2011 3:37 pm

Re: Will BING/BIBM have problems with an AF aligned drive?

Postby ohaya » Tue Jan 29, 2013 5:47 am

Hi,

You all keep referring to using BING to align the partition. I may be missing something, but I don't see an option in BING to align a partition.

I'm running BING 1.87, which I think was the last one before BIBM.

I just did a couple of experiments.

Experiment 1:

That 1.5TB drive started with an ~1.5 TB partition that was aligned (via PAT).

I used BING to resize that partition down to ~1TB.

Then I used BING to create a new NTFS partition in the unallocated area, taking all of the free space.

I then booted into Windows 7 and ran PAT, just to check if the partitions were aligned. In WIndows 7 I formatted the new partition using defaults.

PAT showed the resized partition was aligned, but that the new partition was not aligned.

Experiment 2:

I booted into BING.

I used BING to delete the 2nd partition (so there was the 1st partition, ~1TB, aligned, and ~500GB free space).

I then booted into Windows 7. In WIndows 7 I used Disk Management to create a new Simple volume in the unallocated space, formatted the new partition using defaults.

Then, I ran PAT, and PAT showed both partitions as being aligned.


So, like I said, I don't see an option in BING to do the alignment of the new (or existing) partition?


Maybe you all are talking about only BIBM (but you did say "BING/BIBM")?

Jim
ohaya
 
Posts: 174
Joined: Fri Jan 06, 2012 4:40 pm

Re: Will BING/BIBM have problems with an AF aligned drive?

Postby TeraByte Support » Tue Jan 29, 2013 9:16 am

BIBM - you enable the global option for 2048 and then slide (don't need to
change any values).

"ohaya" wrote in message news:4529@public.bootitng...

Hi,

You all keep referring to using BING to align the partition. I may be
missing something, but I don't see an option in BING to align a partition.

I'm running BING 1.87, which I think was the last one before BIBM.

I just did a couple of experiments.

Experiment 1:

That 1.5TB drive started with an ~1.5 TB partition that was aligned (via
PAT).

I used BING to resize that partition down to ~1TB.

Then I used BING to create a new NTFS partition in the unallocated area,
taking all of the free space.

I then booted into Windows 7 and ran PAT, just to check if the partitions
were aligned. In WIndows 7 I formatted the new partition using defaults.

PAT showed the resized partition was aligned, but that the new partition was
not aligned.

Experiment 2:

I booted into BING.

I used BING to delete the 2nd partition (so there was the 1st partition,
~1TB, aligned, and ~500GB free space).

I then booted into Windows 7. In WIndows 7 I used Disk Management to create
a new Simple volume in the unallocated space, formatted the new partition
using defaults.

Then, I ran PAT, and PAT showed both partitions as being aligned.


So, like I said, I don't see an option in BING to do the alignment of the
new (or existing) partition?


Maybe you all are talking about only BIBM (but you did say "BING/BIBM")?

Jim

TeraByte Support
 
Posts: 2313
Joined: Thu May 05, 2011 3:37 pm

Re: Will BING/BIBM have problems with an AF aligned drive?

Postby TeraByte Support(PP) » Tue Jan 29, 2013 3:54 pm

When you ran your test was the "Align 2048" option enabled in BING's settings?
Paul Purviance
TeraByte Support
TeraByte Support(PP)
 
Posts: 1100
Joined: Thu Aug 11, 2011 5:51 pm

Re: Will BING/BIBM have problems with an AF aligned drive?

Postby ohaya » Tue Jan 29, 2013 5:13 pm

TeraByte Support(PP) wrote:
> When you ran your test was the "Align 2048" option enabled in
> BING's settings?

Paul,

No, it wasn't :(...

Question:

On my HD0 (the main drive inside the laptop), which is a 750GB, I have a bunch of partitions (BING is set for not limiting).

When I boot to Win7, I have a Boot item that has 4 of those partitions, including a SWAP partition where I put the Win7 pagefile.

I was able to get the SWAP partition aligned by using BING to delete the partition, and to create a partition in the same area. And then I booted into Win7 and used Windows Disk Management to format the drive NTFS. Then the SWAP partition now shows as aligned.

I can't do what I did with the SWAP partition, because I have Windows on the C: partition, and data on the other 2 partitions, but is there a way to use BING to get those other 3 partitions to be aligned? Maybe doing a resize and slide or something like that?

Here's the partinfo after booting to Win7:

PARTINFG, Version 1.01
Copyright (c) 2009,2013 TeraByte, Inc. All Rights Reseverd

Run Date: 1/29/2013 7:12 PM

===============================================================================
MBR Partition Information (HD0 - 0x800181CD)
(CHS: 1022/254/63) (WCHS: 91201/255/63)
+====+====+=============+====+=============+=============+=============+
| 0: | 80 | 1 0 1 | 7 | 1023 254 63 | 16065 | 102398310 |
| 1: | 0 | 1023 0 1 | 7 | 1023 254 63 | 102430440 | 30700215 |
| 2: | 0 | 1023 0 1 | 7 | 1023 237 3 | 133130655 | 204795489 |
| 3: | 0 | 1023 0 1 | 7 | 1023 224 2 | 337927275 | 806910869 |
+====+====+=============+====+=============+=============+=============+

===============================================================================
EMBR Found (HD0)
-------------------------------------------------------------------------------
Revision: 2 Min SPT: 9 Sectors: 1 SSize: 512
Last Cyl: 1022 Last Hd: 254 SPT: 63
-------------------------------------------------------------------------------
MPT Found Revision: 5 Number of Entries: 10 Flag: 0
-------------------------------------------------------------------------------
Num Name Flag Start End FS ID
----- ------------------ ------ ----------------- ----------------- ---- ----
0 BootIt EMBRM 4000 63 16064 DF CE
1 Win7 Ultimate 2000 16065 102414374 7 C1
2 SWAP4WIN 2000 102430440 133130654 7 79
3 DATA 2000 133130655 337926143 7 F8
4 DATA1 2000 337927275 1144838143 7 B9
5 Fedora 2000 1144840095 1166174414 83 44
6 Win8 2000 1166174415 1309522409 7 3A
7 SWAP4WIN8 2000 1309522410 1342278944 7 43
8 BINGIMAGES 2000 1342278945 1463087744 C 54
9 DATA4FEDORA 2000 1463087745 1465144064 C B7
-------------------------------------------------------------------------------
MBFT Found Revision: 2 Number of Entries: 0
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
MDT Found Revision: 2 Number of Entries: 1
-------------------------------------------------------------------------------
0: Bootit EMBRL Flag: 20 Start: 0 NumSecs: 7 Alloc: 50 ID: 0
===============================================================================
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 16065 Total Sectors: 102398310 ID: 0xC1
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 16065
NA 3: 0x800080
Total Sectors: 0x61A7965
MFT LCN: 0xC0000
MFT Mirr LCN: 0x2
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xD6F8B0A0F8B08073
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 102430440 Total Sectors: 30700215 ID: 0x79
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 102430440
NA 3: 0x800080
Total Sectors: 0x1D472B6
MFT LCN: 0xC0000
MFT Mirr LCN: 0x2
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x664CF48B4CF45771
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 133130655 Total Sectors: 204795489 ID: 0xF8
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 133130655
NA 3: 0x800080
Total Sectors: 0xC34EE60
MFT LCN: 0xC0000
MFT Mirr LCN: 0x2
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x3691BC3691B360
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 337927275 Total Sectors: 806910869 ID: 0xB9
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 337927275
NA 3: 0x800080
Total Sectors: 0x30187B94
MFT LCN: 0xC0000
MFT Mirr LCN: 0x2
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x58627C30627C154A
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0xDF LBA: 63 Total Sectors: 16002 ID: 0xCE
Jump: E9 82 0
OEM Name: BOOTITXX
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 1
Num FATs: 2
Root Dir Ents: 512
Sectors: 16002
Media: 0xF8
Secs Per FAT: 6
Sec Per Track: 63
Heads: 255
Hidden Secs: 63
Huge Sectors: 0
Drive Num: 0x80
Res: 0x0
Sig: 0x29
Vol ID: 0x723C0200
Volume Label: BOOTIT EMBR
FS Type: FAT12
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 1166174415 Total Sectors: 143347995 ID: 0x3A
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 1166174415
NA 3: 0x800080
Total Sectors: 0x88B511A
MFT LCN: 0xC0000
MFT Mirr LCN: 0x2
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xEC68734C6871ADB
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 1309522410 Total Sectors: 32756535 ID: 0x43
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 1309522410
NA 3: 0x800080
Total Sectors: 0x1F3D336
MFT LCN: 0xC0000
MFT Mirr LCN: 0x2
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x7024E2AB24E2740E
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0xC LBA: 1342278945 Total Sectors: 120808800 ID: 0x54
Jump: E9 57 0 (E9 57 0)
OEM Name: BOOTITXX (BOOTITXX)
Bytes Per Sec: 512 (512)
Sec Per Clust: 64 (64)
Res Sectors: 86 (86)
Num FATs: 2 (2)
Root Dir Ents: 0 (0)
Sectors: 0 (0)
Media: 0xF8 (0xF8)
Secs Per FAT: 0 (0)
Sec Per Track: 63 (63)
Heads: 255 (255)
Hidden Secs: 1342278945 (1342278945)
Huge Sectors: 120808800 (120808800)
Huge Secs Per FAT: 14744 (14744)
Flags: 0x0 (0x0)
Version: 0 (0)
Root Dir Clust: 9 (9)
FS Info Sec: 1 (1)
FS Bkup Sec: 6 (6)
Reserved: 0 0 0 0 0 0
Drive Num: 0x80 (0x80)
Res: 0x0 (0x0)
Boot Sig: 0x29 (0x29)
Vol ID: 0xCCB20200 (0xCCB20200)
Volume Label: BINGIMAGES (BINGIMAGES )
FS Type: FAT32 (FAT32 )
Boot Flag: 0xAA55 (0xAA55)
-------------------------------------------------------------------------------
File System ID: 0xC LBA: 1463087745 Total Sectors: 2056320 ID: 0xB7
Jump: E9 57 0 (E9 57 0)
OEM Name: BOOTITXX (BOOTITXX)
Bytes Per Sec: 512 (512)
Sec Per Clust: 8 (8)
Res Sectors: 32 (32)
Num FATs: 2 (2)
Root Dir Ents: 0 (0)
Sectors: 0 (0)
Media: 0xF8 (0xF8)
Secs Per FAT: 0 (0)
Sec Per Track: 63 (63)
Heads: 255 (255)
Hidden Secs: 1463087745 (1463087745)
Huge Sectors: 2056320 (2056320)
Huge Secs Per FAT: 2005 (2005)
Flags: 0x0 (0x0)
Version: 0 (0)
Root Dir Clust: 2 (2)
FS Info Sec: 1 (1)
FS Bkup Sec: 6 (6)
Reserved: 0 0 0 0 0 0
Drive Num: 0x80 (0x80)
Res: 0x0 (0x0)
Boot Sig: 0x29 (0x29)
Vol ID: 0xBAF40200 (0xBAF40200)
Volume Label: DATA4FEDORA (DATA4FEDORA)
FS Type: FAT32 (FAT32 )
Boot Flag: 0xAA55 (0xAA55)
-------------------------------------------------------------------------------
===============================================================================
MBR Partition Information (HD1 - 0xDBD921FD)
(CHS: 1022/254/63) (WCHS: 182401/255/63)
+====+====+=============+====+=============+=============+=============+
| 0: | 0 | 0 65 2 | 7 | 1023 254 63 | 4096 | 2930267969 |
| 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+=============+=============+
===============================================================================
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 4096 Total Sectors: 2930267969 ID: 0x1
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 4096
NA 3: 0x800080
Total Sectors: 0xAEA85740
MFT LCN: 0xC0000
MFT Mirr LCN: 0x2
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x7030FCD330FCA170
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
===============================================================================
MBR Partition Information (HD2 - 0x61E671D4)
(CHS: 1022/254/63) (WCHS: 91201/255/63)
+====+====+=============+====+=============+=============+=============+
| 0: | 0 | 0 32 33 | 7 | 1023 45 48 | 2048 | 1024000000 |
| 1: | 0 | 1023 45 49 | 7 | 1023 52 51 | 1024002048 | 441145344 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+=============+=============+
===============================================================================
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 2048 Total Sectors: 1024000000 ID: 0x1
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 2048
NA 3: 0x800080
Total Sectors: 0x3D08FFFF
MFT LCN: 0xC0000
MFT Mirr LCN: 0x2
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x94C0BB8FC0BB75D8
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 1024002048 Total Sectors: 441145344 ID: 0x2
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 1024002048
NA 3: 0x800080
Total Sectors: 0x1A4B57FF
MFT LCN: 0xC0000
MFT Mirr LCN: 0x2
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xA4D0C7D5D0C7AC3C
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
===============================================================================
MBR Partition Information (HD3 - 0x00000000)
(CHS: 480/254/63) (WCHS: 481/255/63)
+====+====+=============+====+=============+=============+=============+
| 0: | 80 | 1023 255 63 | b | 1023 255 63 | 2048 | 7731200 |
| 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+=============+=============+
===============================================================================
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0xB LBA: 2048 Total Sectors: 7731200 ID: 0x1
Jump: EB 58 90 (EB 58 90)
OEM Name: MSDOS5.0 (MSDOS5.0)
Bytes Per Sec: 512 (512)
Sec Per Clust: 64 (64)
Res Sectors: 6306 (6306)
Num FATs: 2 (2)
Root Dir Ents: 0 (0)
Sectors: 0 (0)
Media: 0xF8 (0xF8)
Secs Per FAT: 0 (0)
Sec Per Track: 63 (63)
Heads: 255 (255)
Hidden Secs: 2048 (2048)
Huge Sectors: 7731200 (7731200)
Huge Secs Per FAT: 943 (943)
Flags: 0x0 (0x0)
Version: 0 (0)
Root Dir Clust: 2 (2)
FS Info Sec: 1 (1)
FS Bkup Sec: 6 (6)
Reserved: 0 0 0 0 0 0
Drive Num: 0x80 (0x80)
Res: 0x0 (0x0)
Boot Sig: 0x29 (0x29)
Vol ID: 0xFEE52232 (0xFEE52232)
Volume Label: NO NAME (NO NAME )
FS Type: FAT32 (FAT32 )
Boot Flag: 0xAA55 (0xAA55)
-------------------------------------------------------------------------------


Jim
ohaya
 
Posts: 174
Joined: Fri Jan 06, 2012 4:40 pm

Re: Will BING/BIBM have problems with an AF aligned drive?

Postby ohaya » Tue Jan 29, 2013 5:17 pm

P.S. You mentioned the option for 2048, but with the AF drives, aren't the partitions suppose to start at 4096 multiples, rather than 2048?

Jim
ohaya
 
Posts: 174
Joined: Fri Jan 06, 2012 4:40 pm

Re: Will BING/BIBM have problems with an AF aligned drive?

Postby TeraByte Support » Tue Jan 29, 2013 5:42 pm

no. 4096 bytes you're talking certain device types, 2048 sectors is 1mib

"ohaya" wrote in message news:4538@public.bootitng...

P.S. You mentioned the option for 2048, but with the AF drives, aren't
the partitions suppose to start at 4096 multiples, rather than 2048?

Jim

TeraByte Support
 
Posts: 2313
Joined: Thu May 05, 2011 3:37 pm

Re: Will BING/BIBM have problems with an AF aligned drive?

Postby ohaya » Tue Jan 29, 2013 5:58 pm

Hi,

The HD0 is also an AF drive, so I'd like to get all the partitions aligned to 4096? Can I do that with BING?

I was able to get ONE partition on that drive, the SWAP/D: partition to show as aligned, but had to use the Windows 7 format to do that, which was ok, since it wasn't a problem blowing away the SWAP partition.

However, the other 3 partitions, including my C: partition have stuff on them, including Windows on the C; partition, so is there a way to use BING to non-destructively get those 3 partitions aligned?

Jim
ohaya
 
Posts: 174
Joined: Fri Jan 06, 2012 4:40 pm

Re: Will BING/BIBM have problems with an AF aligned drive?

Postby Brian K » Tue Jan 29, 2013 7:53 pm

Jim,

In Settings, do you have Align 2048 sectors or Align 2KiB?

Then do the first post on this page to align the start of each partition on a 2048 sector boundary. A partition is 2048 sector aligned if you get an integer when you divide the number of sectors preceding the partition by 2048.

A partition is cylinder aligned if you get an integer when you divide the number of sectors preceding the partition by 16065.
Brian K
 
Posts: 1175
Joined: Thu Aug 11, 2011 6:11 pm

Re: Will BING/BIBM have problems with an AF aligned drive?

Postby ohaya » Tue Jan 29, 2013 8:10 pm

Brian K wrote:
> Jim,
>
> In Settings, do you have Align 2048 sectors or Align 2KiB?
>
> Then do the first post on this page to align the start of each partition on
> a 2048 sector boundary. A partition is 2048 sector aligned if you get an
> integer when you divide the number of sectors preceding the partition by
> 2048.
>
> A partition is cylinder aligned if you get an integer when you divide the
> number of sectors preceding the partition by 16065.


Hi Brian K,

I've been following a procedure that I found on the radified forum:

http://radified.com/cgi-bin/yabb2/YaBB. ... 1277891819

I've been guessing that the "Brian" was you??

I've done two of the partitions thus far, following those steps, and it looks like it worked thus far. I'm currently doing the C:/Windows partition, but that's taking forever to do the slide, probably because I unchecked the "Data Only" checkbox.

BTW, a couple of things I'm curious about:

1) How did you come up with that (the resize to -5, etc.)? I think I kind of understand what's going on, i.e., the initial resize gives BING some room to adjust the end of the partition when it does the slide?

2) As mentioned, I've been running HDTach, just to get an idea of whether this whole thing is affecting anything. Thus far, after I've aligned each partition, I'm seeing increased average read speed, from about 92MB/s to 97MB/s after aligning the 2nd partition. I'll run HDTach again when the C; partition has been aligned.

Thanks for that other post!

Jim
ohaya
 
Posts: 174
Joined: Fri Jan 06, 2012 4:40 pm

PreviousNext

Return to BootIt Next Generation