BING unable to mount the file system on NTFS partition it cr

User discussion and information resource forum for BootIt Next Generation

BING unable to mount the file system on NTFS partition it cr

Postby FValley » Wed Mar 30, 2016 6:59 am

After BING 1.85 creates a new NTFS partition out of part of a block of free space on HDD, it is "Unable to mount the file system" in the following two cases.

Case 1.

Create primary partition. The new primary partition's "Properties" dialog box shows "File System: 7/7h: HPFS/NTFS," but then clicking "Details" produces a "Notice" dialog box stating "Unable to mount the file system."

Windows 8 Disk Management sees the new primary partition, but without a file system, i.e., it reports RAW.


Case 2.

Create extended partition and then logical partition (volume) within it, using file systems "5/5h: Extended" and "7/7h: HPFS/NTFS," respectively. The new logical partition's "Properties" dialog box shows "File System: 7/7h: HPFS/NTFS," but then clicking "Details" produces a "Notice" dialog box stating "Unable to mount the file system."

Windows 8 Disk Management does not see either the extended or logical partition, just unallocated space.

Why can't the file system be mounted in both cases?

Thank you.
FValley
 
Posts: 4
Joined: Mon Nov 02, 2015 5:15 pm

Re: BING unable to mount the file system on NTFS partition it cr

Postby TeraByte Support » Wed Mar 30, 2016 9:05 am

BING doesn't format NTFS, you format it in the OS on first access.

Update to BIBM if you want it to format NTFS.

"FValley" wrote in message news:11350@public.bootitng...

After BING 1.85 creates a new NTFS partition out of part of a block of free
space on HDD, it is "Unable to mount the file system" in the following two
cases.

Case 1.

Create primary partition. The new primary partition's "Properties" dialog
box shows "File System: 7/7h: HPFS/NTFS," but then clicking "Details"
produces a "Notice" dialog box stating "Unable to mount the file system."

Windows 8 Disk Management sees the new primary partition, but without a file
system, i.e., it reports RAW.


Case 2.

Create extended partition and then logical partition (volume) within it,
using file systems "5/5h: Extended" and "7/7h: HPFS/NTFS," respectively. The
new logical partition's "Properties" dialog box shows "File System: 7/7h:
HPFS/NTFS," but then clicking "Details" produces a "Notice" dialog box
stating "Unable to mount the file system."

Windows 8 Disk Management does not see either the extended or logical
partition, just unallocated space.

Why can't the file system be mounted in both cases?

Thank you.

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

Re: BING unable to mount the file system on NTFS partition i

Postby FValley » Wed Mar 30, 2016 11:45 pm

Thank you for your reply.

I understand now how to fix Case 1, since Windows 8 Disk Management can see and format the primary partition BING created.

However, I still don't understand how to handle Case 2. Windows cannot see the extended partition or the logical volume in it that BING created. How can Windows format the logical volume? All Windows sees is unallocated space.

Thank you.
FValley
 
Posts: 4
Joined: Mon Nov 02, 2015 5:15 pm

Re: BING unable to mount the file system on NTFS partition i

Postby TeraByte Support » Thu Mar 31, 2016 6:20 am

See the first quick link at
http://www.terabyteunlimited.com/support-bootit-bare-metal.htm


"FValley" wrote in message news:11352@public.bootitng...

Thank you for your reply.

I understand now how to fix Case 1, since Windows 8 Disk Management can see
and format the primary partition BING created.

However, I still don't understand how to handle Case 2. Windows cannot see
the extended partition or the logical volume in it that BING created. How
can Windows format the logical volume? All Windows sees is unallocated
space.

Thank you.

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


Return to BootIt Next Generation