No option to make an NTFS partition

Hello
I try to install Windows XP 32bits SP3 with Bootcamp, but when i get to select partition and i select BOOTCAMP FAT32 partition on 32GB my windows just starts to install. i do not get the option to do an format of disc to NTFS. Windows just starts to install and when my mac reboots all i get is Disc Error and i have to boot back to MAC OS.
Did anyone else have this problem before or?
Tnx to all that replays

It is a bad version of XP if it doesn't stop and ask, that does happen. Heck, some are so bad they wipe out the whole hard drive and use the entire Mac HD partition.
PS: don't ever use Disk Utility to create a partition for Windows XP, it doesn't work and not sure where you came up with that idea. Only Boot Camp Assistant works with XP and where installing Windows on same drive as Mac OS.
The BOOTCAMP partition is MSDOS/FAT32 and a 'proper' Windows installer will give you option to choose where target volume, click on ADVANCED OPTIONS to format or delete and create NTFS partition.

Similar Messages

Arch and Win7 cannot open an NTFS partition created by the other

This is almost certainly related to another post where I was struggling to create logical partitions from Windows. Basically, Linux and Minitool Partition Wizard agreed that there were no logical partitions, but the built-in Windows disk utility said there was. I ended up using fdisk from Arch install media, and Minitool and Arch now both saw the logical partitions (Windows shows a big extended partition of free space). I installed Arch just fine, can boot to it and win7... life is good.
Not so much. A key to my setup is having an encrypted partition to share data between OS's. I used TrueCrypt with great success on my former laptop and am now having great difficulty!
Some preliminary information:
# fdisk -l /dev/sda
Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 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
Disklabel type: dos
Disk identifier: 0x1e6513b3
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 2101247 2099200 1G 7 HPFS/NTFS/exFAT
/dev/sda2 2101248 172433407 170332160 81.2G 7 HPFS/NTFS/exFAT
/dev/sda3 172433408 390537215 218103808 104G 7 HPFS/NTFS/exFAT
/dev/sda4 390537216 500118191 109580976 52.3G 5 Extended
/dev/sda5 390539264 391587839 1048576 512M 83 Linux
/dev/sda6 391589888 500118191 108528304 51.8G 83 Linux
I also went partition by partition to check Minitool's agreement on sectors (they match perfectly with the exception that it doesn't show the extended /dev/sda4 container). I triple checked the Minitool partition info properties as you can't copy and paste from it's window, and pasted the fdisk output to minimize errors. I'm showing a column for mini/Arch for both start/stop sectors, and just subtracted them to make sure I got 0. Appears to be perfect alignment:
| part | start (mini) | start (arch) | diff | | end (mini) | end (arch) | diff |
|------+--------------+--------------+------+---+------------+------------+------|
| sda1 | 2048 | 2048 | 0 | | 2101247 | 2101247 | 0 |
| sda2 | 2101248 | 2101248 | 0 | | 172433407 | 172433407 | 0 |
| sda3 | 172433408 | 172433408 | 0 | | 390537215 | 390537215 | 0 |
| sda4 | 390539264 | 390539264 | 0 | | 391587839 | 391587839 | 0 |
| sda5 | 391589888 | 391589888 | 0 | | 500118191 | 500118191 | 0 |
- Screenshot of how Minitool sees my disk
- Screenshot of how Windows disk utility sees my disk
I used TrueCrypt 7.1a on both OS's. I created a non-system encrypted partition using the GUI on Arch with the AES cipher/sha-512 hash, with filesystem as "none." Once created I did:
$ sudo cryptesetup --type tcrypt open /dev/sda3 vault
That worked fine, which I followed with:
$ sudo mkfs.ntfs /dev/mapper/vault
It initialized the device with zero's and then gave me the success/have a nice day message. Closed the volume and rebooted. When I tried to open the device from win7, I got "Incorrect password or not a TrueCrypt volume." Hmmm. I guess I'll try in reverse. I duplicated the procedure exactly as above from win7, this time having TrueCrypt automatically format with NTFS. All succeeds and I can open the device. Reboot into Arch and I get the same message from TrueCrypt! If I try with cryptsetup, it's "No device header detected with this passphrase."
Next, I tried just doing NTFS with no encryption. From Arch:
$ sudo mkfs.ntfs /dev/sda3
All goes well and I can mount it. I boot into Windows and it's not even listed! I used Minitool to issue it a drive letter, at which point clicking that pops up a windows dialog box asking me if I want to format the disk. Format the partition with NTFS in Windows, reboot into Arch and I get:
[jwhendy@arch_zbook ~]$ sudo mount /dev/sda3 /mnt/scratch/
NTFS signature is missing.
Failed to mount '/dev/sda3': Invalid argument
The device '/dev/sda3' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Doesn't matter if I add "-t ntfs" or "-t ntfs-3g." I get the same result.
Just to add a couple more oddities... when I created the NTFS partition in Arch, I also created a file called vault.tc as a TrueCrypt file-based encrypted container. My thinking was that the issue was with TrueCrypt full-partitions and that I could get around it with a plain partition containing an encrypted file. Reboot into windows and the partition isn't shown (as stated above). From Minitool, if I right click the partition and choose "Explore," it lists the partition contents and there is my vault.tc file. Windows thinks it's unformatted!
I noticed the option to backup/restore a TrueCrypt header, and gave a shot at backing up the working TrueCrypt setup on windows to a flash drive, booting to Arch, and then restoring the /dev/sda3 header from the flash drive file. Arch still couldn't open it.
Lastly, I noticed when I go to select a device to encrypt in TrueCrypt, my logical partitions aren't showing up (just like Windows only sees the end of the disk as free space). I just can't help but think something is tweaked in the partition table... basically:
- TrueCrypt sees what Windows sees
- Arch sees what Minitool sees
How could I go about diagnosing further or fixing the issue. This is driving me crazy!
I'd hate to do this given that I already setup my wm, configs, packages, etc... but my last resort attempt would be to wipe my logical partitions and see if I can at least get the win7 disk utility, minitool, arch, and truecrypt to like each other with respect to /dev/sda1-3... and then try to re-add the logicals afterward and re-install arch? I honestly don't know why this would be any different, but was just a thought. The issues from the other post seem to arise with logical partitions not being recognized the same between win/linux.
Or figure out how to just use primaries (like dedicated boot on a USB drive or something). Or fiddle with growing/shrinking windows to see if I can undo whatever is telling windows where/what things are? Really grasping at straws here.
Last edited by jwhendy (2015-06-10 23:32:22)

Hi Ramesh,
Please install the hotfix package and test the issue again:
http://support.microsoft.com/kb/2817576/en-us
In addition, try uncheck the option “confirm open after download” per:
http://jritmeijer.wordpress.com/2006/08/20/some-files-can-harm-your-computer-if-the-file-information-looks-suspicious-or-you-do-not-fully-trust-the-source-do-not-open-the-file/
Regards,
Rebecca Tu
TechNet Community Support

Easy to install Lion with BootCamp + Win 8 + NTFS partition for data?

Hey, I have a MacBook Pro (2011) currently on OS X 10.6.8, but I bought Lion 10.7 and want to use that.
Here's what I want to do:
* install Lion (fresh, not upgrade)
* install BootCamp
* install Win 8 (DevEd) (for games and some other apps)
And here are my questions:
1) What's the best (free) way to save/"ghost" the current OS so I can quickly get back to that in case something happens when I install Lion?
2) What order do I install BootCamp and Win 8 in? Any fool-proof tutorial for how to do this?
3) If I do a backup with Time Machine as the last thing I do before installing Lion, I just copy the data back from the TM drive after install, right?
4) I would like to use Win 8 and some programs there to read and write to the HFS+ OS X partition - is there a free and/or good way to do that?
5) On PC I can use WinAmp, the great plugin "DeleteCurrentSong" and a shortcut key to delete the currently playing track. Is there a way to do something similar in any program in OS X?
6) If not, would it be possible to - early in the install process - make a big NTFS partition and put most of my data there so it can be accessed from both OS X (with Paragon) and Windows? And Time Machine wouldn't back it up as long as it's NTFS, right?
Thanks a lot for any answers!

Answer to question 1:
a. Get a USB disc the same size or better larger than your internal HD
b. Download Carbon Copy Cloner (free)
c. Clone the internal HD to the external disc
d. Reboot with the 'option' key held down. Choose the external disc to check that the clone was successful and is bootable.
e. If yes, reboot again, hodling down the 'option' key. Choose the internal HDD.
f. Dismount/eject the external HD and disconnect it from your computer.
g. Go to app store and download Lion.
h. When the download is complete, DO NOT run it. First, copy the file (Applications > Lion Install.app) to another location on your disc (the downloads folder will do). This is because after you run the installer it will delete itself from the Applications folder, and you may very well either want/need to do a re-install later without wanting to wait for hours for the download.
i. Run Applications > Lion Install.app

Renaming files with invalid characters in their names on NTFS partitions, introduced by operating systems other than Windows

Essentially, Linux created some files with colons (:) in the name on a NTFS partition where I have Windows installed. I have since uninstalled Linux, but now I can only view these files in Windows Explorer. I can't open them, I can't even rename them to
correct the problem. It's as if they don't exist, because of the invalid search paths.
If I try to rename them in Windows Explorer I get following message.
The file name you specified is no valid or too long.
Specify a different file name.
Well isnt' that something?... isn't that nice? Windows is able to display these files, but it doesn't allow me to open them and it certainly doesn't like me to rename them. So why is it whining about it then, when I'm trying to help? It says "try a different
file name". Yeah, right! Like I haven't tried that one already! It doesn't matter what file name I input it will never accept it.
So what am I supposed to do now? Ditch Windows and go back to Linux? Surely, Microsoft doesn't like the sound of that. Sure, I could reinstall Linux or run a Linux live system to correct the problem. But what good is Windows then? I might as well switch to
Linux altogether.
After doing some research I now know by fact that it's (kind of) possible to rename files from UNIX and UNIX-like operating systems to those compliant with Windows by using something called file name character translation. To some level this is essential and
necessary for Windows interoperability with other operating systems (Windows is not the only operating system in the world). But this seems to be very complicated and I can't get my head around it. My brain is in overload. I don't know where to start.
Once there was a...
There's the Windows Services for UNIX (SFU) 1.0, 2.0, 3.0, 3.5. The first two versions were based on MKS Toolkit, a package licensed by Microsoft from MKS Inc. The later versions were based on the similar Interix product, after Microsoft purchased the company
that made it.
Then there's the new Subsystem for UNIX-based Applications (SUA). These are services for UNIX components. They are supposed to have Client for NFS v3 included as well. But the server components from the SFU line is missing (e.g. Server for NFS). These are included
in Server editions of Windows.
Then there's the Microsoft Knowledge Base article
289627: "How to Enable File Name Character Translation". This article seems to describe exactly my situation.
Windows and UNIX operating systems have restrictions on valid characters that can be used in a file name. The list of illegal characters for each operating system, however, is different. For example, a UNIX file name can use a colon (:), but a Windows
file name cannot use a colon (:). If a UNIX user attempts to create a file with a Windows illegal character on a Windows Services for UNIX network file system (NFS) share, the attempt is unsuccessful and the UNIX client computer receives an input or output
error.
It goes further than that. At first glance, this KB article also seems to offer a solution to this exact problem, with examples as shown below.
For example, the following maps the UNIX colon (:) to a Windows dash (-):
0x3a : 0x2d ; replace client : with - on server
I checked these values in charmap.exe and they are correct. Except for 2D not being a "dash", it's rather a hyphen ("hyphen minus" to be exact), but these two have pretty much the same appearance and they get interchanged a lot, I'm sure
they are used to it by now. (Yes, the characters! They don't mind.)
Then there's this registry key.
HKEY_LOCAL_MACHINE\Software\Microsoft\Server For NFS\CurrentVersion\Mapping
Well, of course, I don't have Server for NFS. So this is a dead end. Well, actually, it was a dead end from the beginning...
1. First of all, I'm not working with a network share on a NAS or SAN storage. The files are on the local disk drive where Windows is installed, so that's a DAS for you.
2. I don't have SFU! Well obviously, I'm on Windows Vista! So that means SUA!
3. SUA are service components only. No server components. Can you guess what that means? Yeah... no "Server for NFS" since it's a server component.
4. Windows Vista is a client side operating system! Server for NFS is only offered for use with Windows Server systems.
5. Back to square one!
So there you have it. They all lived happy for the rest of their lives...
I'm stuck here. Can someone tell me what to do? I mean beyond the obvious option to use Linux to fixa a Windows problem? The NTFS file system itself supports colons in file names. It's Windows that doesn't, and so by default it proclaims it invalid character.
Surely, even a Windows client operating system like Windows Vista should be able to allow the user to at least rename files with invalid characters to something more sensible (from the system point of view) and valid, if not being able to open them as they
are. Just add some crazy voodoo code to it and it will work. If you can make it possible on Windows Server with UNIX user-mode subsystem on NT kernel, then what's stopping you from giving the Windows client system the same benefit?
So what now? Purchase a Windows Server 2012 R2 license, copy my invalid files to a NAS share with NFS on a UNIX or Linux system, and have a go at the Windows registry and Server for NFS? Yeah... you're right, it's probably a bit over the top...
On a second thought... I might as well install Linux again. There are countless situations where Linux has helped me solve problems related to, and more often than not caused by Windows.

Essentially, Linux created some files with colons (:) in the name on a NTFS partition where I have Windows installed. I have since uninstalled Linux, but now I can only view these files in Windows Explorer. I can't open them, I can't even rename them to
correct the problem. It's as if they don't exist, because of the invalid search paths.
If I try to rename them in Windows Explorer I get following message.
The file name you specified is no valid or too long.
Specify a different file name.
Well isnt' that something?... isn't that nice? Windows is able to display these files, but it doesn't allow me to open them and it certainly doesn't like me to rename them. So why is it whining about it then, when I'm trying to help? It says "try a different
file name". Yeah, right! Like I haven't tried that one already! It doesn't matter what file name I input it will never accept it.
So what am I supposed to do now? Ditch Windows and go back to Linux? Surely, Microsoft doesn't like the sound of that. Sure, I could reinstall Linux or run a Linux live system to correct the problem. But what good is Windows then? I might as well switch to
Linux altogether.
After doing some research I now know by fact that it's (kind of) possible to rename files from UNIX and UNIX-like operating systems to those compliant with Windows by using something called file name character translation. To some level this is essential and
necessary for Windows interoperability with other operating systems (Windows is not the only operating system in the world). But this seems to be very complicated and I can't get my head around it. My brain is in overload. I don't know where to start.
Once there was a...
There's the Windows Services for UNIX (SFU) 1.0, 2.0, 3.0, 3.5. The first two versions were based on MKS Toolkit, a package licensed by Microsoft from MKS Inc. The later versions were based on the similar Interix product, after Microsoft purchased the company
that made it.
Then there's the new Subsystem for UNIX-based Applications (SUA). These are services for UNIX components. They are supposed to have Client for NFS v3 included as well. But the server components from the SFU line is missing (e.g. Server for NFS). These are included
in Server editions of Windows.
Then there's the Microsoft Knowledge Base article
289627: "How to Enable File Name Character Translation". This article seems to describe exactly my situation.
Windows and UNIX operating systems have restrictions on valid characters that can be used in a file name. The list of illegal characters for each operating system, however, is different. For example, a UNIX file name can use a colon (:), but a Windows
file name cannot use a colon (:). If a UNIX user attempts to create a file with a Windows illegal character on a Windows Services for UNIX network file system (NFS) share, the attempt is unsuccessful and the UNIX client computer receives an input or output
error.
It goes further than that. At first glance, this KB article also seems to offer a solution to this exact problem, with examples as shown below.
For example, the following maps the UNIX colon (:) to a Windows dash (-):
0x3a : 0x2d ; replace client : with - on server
I checked these values in charmap.exe and they are correct. Except for 2D not being a "dash", it's rather a hyphen ("hyphen minus" to be exact), but these two have pretty much the same appearance and they get interchanged a lot, I'm sure
they are used to it by now. (Yes, the characters! They don't mind.)
Then there's this registry key.
HKEY_LOCAL_MACHINE\Software\Microsoft\Server For NFS\CurrentVersion\Mapping
Well, of course, I don't have Server for NFS. So this is a dead end. Well, actually, it was a dead end from the beginning...
1. First of all, I'm not working with a network share on a NAS or SAN storage. The files are on the local disk drive where Windows is installed, so that's a DAS for you.
2. I don't have SFU! Well obviously, I'm on Windows Vista! So that means SUA!
3. SUA are service components only. No server components. Can you guess what that means? Yeah... no "Server for NFS" since it's a server component.
4. Windows Vista is a client side operating system! Server for NFS is only offered for use with Windows Server systems.
5. Back to square one!
So there you have it. They all lived happy for the rest of their lives...
I'm stuck here. Can someone tell me what to do? I mean beyond the obvious option to use Linux to fixa a Windows problem? The NTFS file system itself supports colons in file names. It's Windows that doesn't, and so by default it proclaims it invalid character.
Surely, even a Windows client operating system like Windows Vista should be able to allow the user to at least rename files with invalid characters to something more sensible (from the system point of view) and valid, if not being able to open them as they
are. Just add some crazy voodoo code to it and it will work. If you can make it possible on Windows Server with UNIX user-mode subsystem on NT kernel, then what's stopping you from giving the Windows client system the same benefit?
So what now? Purchase a Windows Server 2012 R2 license, copy my invalid files to a NAS share with NFS on a UNIX or Linux system, and have a go at the Windows registry and Server for NFS? Yeah... you're right, it's probably a bit over the top...
On a second thought... I might as well install Linux again. There are countless situations where Linux has helped me solve problems related to, and more often than not caused by Windows.

HOWTO: Resize Bootcamp (NTFS) partition for free using gparted

Hi,
Well, if you find your Bootcamp/NTFS/Windows partition running out of space, you may want to increase it or decrease it. The OSX Bootcamp utility doesn't allow resizing the NTFS partitio nor does Disk Utility. Here is a free solution ...
NOTE: I've tried this on Windows 7 64bit, but it should work with other windows setups in a similar manner.
Requirements:
1. SysRescueCD (for an NTFS capable 'gparted')
- http://www.sysresccd.org/Download
2. rEFIt bootable CD (or install to hard disk, doesn't matter)
- http://refit.sourceforge.net/doc/c1s5_burning.html
3. Windows XP/Vista/7 CD (depends what you've installed)
- just for a quick 'repair' at the end, no reinstall here!
In short:
1 Shrink Mac partition in OSX's Disk Utility
2 Grow the NTFS partition in gparted booting off sysrescue CD (reboot->option key). This may take 30mins to a few hours to complete!
3 Boot the rEFIt CD -> choose "start partitioning tool" -> hit yes when it says it needs to sync the MBR with the GPT.
4 Boot your Windows CD.
Vista/Windows7 CD -> hit the repair option to fix the boot record.
XP CD -> you may need to go to the administrative shell and type fixboot and then fixmbr.
5. Reboot and you should be able to boot into Windows via the option key as before. I liked rEFIt a lot so I installed it to my disk itself. (FYI, I did notice I needed to install rEFIt a few times to get it to show up during boot time)
Message was edited by: SidOnline

One bug I learnt:
if
1. you set the 'boot' flag on the Windows partition in gparted AND
2. you use gptsync to sync the GPT with the MBR (i.e. MBR->GPT translation)
then
you will find that your Windows partition becomes inaccessible in OS X. Your partition is OK - you can boot in windows etc - OS X just doesn't see it as a NTFS partition.
Solution:
1. Don't enable the boot flag in gparted. Simple, no need to read further.
If you're done it and have been hit by the bug and would like to see Windows/Bootcamp again in Finder, read on...
1. Goto http://www.insanelymac.com/forum/index.php?showtopic=31562, post #9 has a tool to fix it. Download the diskpart.zip file (it's got diskpart.efi)
2. Extract the diskpart.zip file, copy the diskpart.efi to /efi/tools on your OSX volume (default location for hard disk install of rEFIt).
3. Reboot, in the rEFIt menu, select the EFI terminal
4. type fs1: and hit enter. This should take you to your Leopard volume (for me fs0: was the 1st partition (EFI boot partition), fs1: was the 2nd partition (Leopard)
5. type _cd /efi/tools_ and hit enter
6. type diskpart and hit enter
7. As the post linked above says, type
+select <zero-based disk number>+
inspect
+chtype <zero-based partition number> MSDATA+
For me this was
+select 0+
inspect
+chtype 2 MSDATA+
Look at the output of select to make sure you're using the right number - if you have your eyes open it's hard to make a mistake!
Behind the scene details:
Your partition type is set to NTFS in the MBR table (which is why windows can load it up etc) but if you do the above then the partition type in the GPT is written as EFI instead of NTFS (or more accurately 'MSDATA'). This is a bug in gptsync and I believe Chris (writer of rEFIt) is aware of this - at least another post elsewhere made it look like that. I guess you can't blame it since EFI, GPT tools are still in their infancy.
BTW, to sync the GPT with the MBR, there is a tool gptsync. I believe it's a tool from Intel's EFI toobox. It exists as either an efi program (i.e. gptsync.efi, runs when you select it from rEFIt's menu) or as a OSX program (just gptsync, runs when you download it and type 'sudo gptsync').

"Lag" when Nautilus is opened with NTFS partition mounted

Hi, I have a problem with Nautilus 3.14. I have a mounted shared Windows partition with the options below in fstab:
defaults,nls=utf8,umask=000,uid=1000,gid=1000,windows_names,hide_dot_files,hide_hid_files
Everytime I open Nautilus, it "lags" (I don't know what to call it. It freezes and then be usable again for an uncertain amount of time). Tried to unmount the ntfs partition and it worked flawlessly. Nautilus' shell output doesn't show anything strange (just some random GTK warning).
This "lag" doesn't happen when I use Nemo. It runs well with the NTFS partition mounted.
Is anyone knows the solution or has the same problem?

solstice wrote:
it began to make a few click noise when I was copying data to/from it.
I can't believe it. It's a 2 week old harddrive. a western digital suposed to be good quality.
Have I broken it or what ?
I have made a badblocks scan before trying to use it and found no problem. I'll try again but I fear loosing data any moment now :-(((
Western Digital is great but every manufacturer ships out defective drives now and again. Run a hard test with Sea Tools or the WD equivalent and if anything comes up, call them immediately. Your drive is still under warranty if it's brand new so they should replace it for free.

Cannot mount NTFS partition!!!!!!!!

People I'm new to this ARCH world. I want to mount my XP partition(NTFS). I tried
#ntfsmount /dev/sda1 /mnt
But some errors are thrown on de console
fuse: unknown option "USER = root"
fuse_new failed
umounting /dev/sda1 ()
Now how can i resolve this problem to mount my ntfs partition in rw mode.

What is not working? Is it not r/w?
EDIT: Look into the possible use of ........mount -o remount,rw /dev/sdxx..... in /etc/rc.local.......
Not sure of the exact command but the idea is to make it r/w on every boot-up via rc.local.
Hopefully, other users can correct any discrepancy I have introduced.
Last edited by lilsirecho (2008-01-09 17:21:00)

[SOLVED] NTFS partition unmounted after suspend to ram

I recently did a from-scratch installation after I bought an SSD to replace of my old harddrive. Since this fresh install I have been having a problem with an NTFS partition that is mounted by way of fstab (it's not _the_ windows partition just a bit of shared space on a dual-boot setup): Whenever I suspend the computer and bring it back up, the NTFS partition is invariably unmounted.
The mount point is empty and the mount command makes no mention of the mount. A simple "sudo mount /mnt/SAND" will bring the partition back up again although sometimes it needs to be umounted first (the mount point is still empty despite the 'mount'). Here is the fstab line:
/dev/sda3 /mnt/SAND ntfs-3g defaults,noatime,uid=1000,gid=100 0 0
Testing and screwing around I've noticed that if the WINDOWS partition is mounted using nautilus (as it is not mentioned in fstab) that too will be unmounted while a non-root ext4 partition (UBUNTU) is not.
So my hypothesis is that these NTFS partitions are singled out for unmounting when suspending (but apparently not mounting when reawakening?) -- maybe because they are assumed to be external drives? Given that it happens across mounting solutions (fstab/nautilus) I'm inclined to think it's not a bug?
At any rate I'm looking for a solution that will allow me to stop the unmounting when suspending -- ideally for all internal drives, secondarily for these specific partitions. I have checked the suspend to ram article on the wiki but it doesn't seem to mention anything about unmounting...
EDIT: After the Great Big Arch Switch To Systemd this problem no longers occurs on so I'm closing it. Not necessarily much of a solution to anyone who happens on this from google, sorry.
Last edited by madchine (2012-10-13 12:58:54)

Hi all,
It seems that most freezes are gone with:
- 270.29 beta driver
- MTRR enabled by appending enable_mtrr_cleanup mtrr_spare_reg_nr=1 to the list of kernel options (see http://www.nvnews.net/vbulletin/showpos … tcount=39)
I didn't investigate further to know if both the driver and the MTRR trick are required.
Thanks a lot,
Aurel.

How do I create a Boot Camp partition with Windows & blank NTFS partitions?

I'm trying to create this kind of setup:
OS X partition
Windows 7 partition
blank NTFS partition (no OS)
blank NTFS partition (no OS)
This would be much easier if I created just the OS X partition and the Windows 7 partition with the Boot Camp Assistant tool (done this many times before successfully on other computers). The problem begins when I try to split the Boot Camp partition through the Windows 7 DVD partition manager during setup by deleting the Boot Camp partition, and recreating three partitions from the unallocated space. After installing Windows 7 on one of those new three partitions, I'm getting all kinds of startup errors when I try to install the Boot Camp drivers.
What would the best way to achieve this setup?

Yes, I researched many options for three partition dual boot set ups. After many trials and tribulations, there is a simple method that I have used on multiple MBPs.
1. Run Boot Camp Assistant, as per the Boot Camp Installation and Setup Guide. Once you have Mac OS X and Windows 7 set up, check the partitions and back them up (with Time Machine, and Winclone).
2. Get iPartition, and resize the Mac and Windows partitions to what you want, say 100GB each, and set up your other partitions to the size you want. I put mine "after" the Windows partition, at the end of the disk, and have had no problems. It takes a few minutes to create the bootable CD for iPartition, but you get everything you need to do so from Coriolis Systems. You will need your Mac OS X installl disc.
3. Install Paragon's HFS+ for Windows and NTFS for Mac, and everybody can read and write everything.
4. I have both Time Machine and Norton 360 back up the Data partitions, just in case -- to an external drive, of course.
You can boot to either OS and access any partition.

I am unable to mount my NTFS partition after the last update

I usually mounted my NTFS partition with the "gnome-disk" utility. It works no longer, only if I start it with "sudo". But in this case the mount point will be in a directory called "root" and this cause several problems, eg.: old hardcoded paths stop working in scripts. What can I do to make the gnome-disk utility work as an ordinary user.

Thx, maybe I could use the fstab to mount the partition, am I right? But I don't know how to do it properly, because when I tried it in the past native hungarian characters iny the file and directory names always caused problems. If I somehow could capture the command sequence which the gnome-disk utility passes to the kernel / bash, would be helpful.

Problem accessing mounted ntfs partitions

Hi,
I have problems accessing ntfs partitions as a non root user. The user trying to acces the partition is in usergroup wheel and has sudo acces.
/etc/fstab looks like this:
/dev/sda5 /media/winC ntfs defaults 0 2
/dev/sdb1 /media/winD ntfs defaults 0 2
It does not matter where I mount them (e.g. /home/user/media/winC), if i try cd-ing into the directory, it tells me:
cd /medi/winC
-bash: cd: /media/winC: Permission denied
When i try the following, it tells me:
sudo cd /medi/winC
sudo: cd: command not found
which I find a bit strange, but ok.
Any pointers what I am doing wrong? cd-ing as root works, but i would like to acces it as a normal user too. Using the following options did not work for me:
rw,suid,dev,exec,auto,users,async
mount -l tells me the following when using the options stated above:
/dev/sda5 on /media/winC type ntfs (ro,nosuid,nodev,noexec,relatime,uid=0,gid=0,fmask=0177,dmask=077,nls=utf8,errors=continue,mtf_zone_multiplier=1)
Thanks for any pointers!

Trilby wrote:
You should use ntfs-3g instead of ntfs. I'm not sure if that will solve this problem, though it might, but it will prevent others.
As for "sudo cp" failing, that is not odd at all: `cd` is not a program, it is a shell builtin - there is no `cd` binary for sudo to execute.
Thanks for the explanation. I will try ntfs-3g as soon as I manage to connect to the internet again.

Unable to erase windows ntfs partition thru mac using disk utility

i connected my desktop hard disk to my mac. i am not able to delete any files from the Windows NTFS partition. in disk utility the erase option is greyed out.
please help.
thanks.

NTFS is a read-only filesystem to OS X. You can read and copy files from an NTFS formatted drive but you cannot write to one.

How to mount SATA Ntfs Partitions on Arch Linux

Please help me mounting sata ntfs partitions.
Here is my fdisk -l :
[kaola@ArchHost ~]$ sudo fdisk -l
Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x020e020e
Device Boot Start End Blocks Id System
/dev/sda1 1 371 2980026 82 Linux swap / Solaris
/dev/sda2 * 372 2803 19535040 83 Linux
/dev/sda3 2804 6450 29294527+ 83 Linux
/dev/sda4 6451 6463 104422+ 83 Linux
Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xd7a23d33
Device Boot Start End Blocks Id System
/dev/sdb1 2 5875 47182905 5 Extended
/dev/sdb2 * 5876 9139 26218080 7 HPFS/NTFS
/dev/sdb5 2 3918 31463271 7 HPFS/NTFS
/dev/sdb6 3919 5875 15719571 7 HPFS/NTFS
Disk /dev/sdc: 4043 MB, 4043308544 bytes
255 heads, 63 sectors/track, 491 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00050ebd
Device Boot Start End Blocks Id System
/dev/sdc1 1 491 3943926 b W95 FAT32
As far as I know, the sata ntfs partitions are those with (sdb#).
I tried mounting one of them but this is what it shows:
[kaola@ArchHost ~]$ sudo mount /dev/sdb6
mount: can't find /dev/sdb6 in /etc/fstab or /etc/mtab
Please help me, this is very annoying compared to ubuntu which does do the job pretty well. By the way, I'm using kde as my DE. Dolphin sees the partitions but cant access.
It says:
An error occured while accessing 'Backup2 HD2', the system responded:
org.freedesktop.Hal.Device.Volume.UnknownFailure: TODO:
have to rethink extra options
Reading some tutorials on ntfs-3g wiki, I've modified my fstab. Still, I can't read the partitions...Please help me, this is my fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
UUID=2167baaa-d1e0-4719-920c-0bc09fa56caa / reiserfs defaults 0 1
UUID=3e2250a0-ac45-458c-ba40-44ddbe8af54d /boot ext2 defaults 0 1
UUID=cbf76343-12cf-4975-9284-3360735be927 /home reiserfs defaults 0 1
UUID=f39da452-efe4-49d0-abd4-bb5246b83b33 swap swap defaults 0 0
/dev/cdrom /media/cdrom auto ro,user,noauto,unhide 0 0
/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
UUID=2167baaa-d1e0-4719-920c-0bc09fa56caa / reiserfs defaults 0 1
UUID=3e2250a0-ac45-458c-ba40-44ddbe8af54d /boot ext2 defaults 0 1
UUID=cbf76343-12cf-4975-9284-3360735be927 /home reiserfs defaults 0 1
UUID=f39da452-efe4-49d0-abd4-bb5246b83b33 swap swap defaults 0 0
/dev/sdb1 /mnt/ntfs1 ntfs-3g users,noauto,uid=1000,gid=100,fmask=0113,dmask=0002,locale=en_US.utf8 0 0
/dev/sdb2 /mnt/ntfs2 ntfs-3g users,noauto,uid=1000,gid=100,fmask=0113,dmask=0002,locale=en_US.utf8 0 0
/dev/sdb5 /mnt/ntfs3 ntfs-3g users,noauto,uid=1000,gid=100,fmask=0113,dmask=0002,locale=en_US.utf8 0 0
/dev/sda6 /mnt/ntfs4 ntfs-3g users,noauto,uid=1000,gid=100,fmask=0113,dmask=0002,locale=en_US.utf8 0 0
Last edited by kaola_linux (2008-10-04 14:51:24)

AD28 wrote:
For seamless integration similar to Ubuntu:
Follow this wiki for ntfs-3g installation and fstab configuration.
For basic on-demand support:
# pacman -Sy ntfs-3g
and mount with:
# mount -t ntfs-3g /dev/sdbX /mnt
Now that did the trick!!!!!
A happy Arch Linux user here!!!!hehee
Any idea how to automate this? I want it to be automatically mounted so that it would be easy to transfer files...Pleasssseeeeee.....Thanks

Arch64: wine won't launch exe on NTFS partitions but will do on reiser

Hi everyone!
OK, this is an other issue with wine and x64 (2.6.30). I say another because I saw that a lot of us have issues with wine and x64 that end up being answered "wine and 32 bit applications under x64 architecture won't do fine" but this one is driving me nuts: it looks like i'm not far away from making it.
My problem is: wine can't launch applications if the exe is on my NTFS partition but will do if the same exe is on one of my reiserfs partition.
ie:
[miguel@WKM_MSI ~]$ wine /mnt/win_NTFS/WINDOWS/NOTEPAD.EXE
wine: Unhandled page fault on read access to 0x0044b6ab at address 0x44b6ab (thread 0009), starting debugger...
wine: Unhandled page fault on read access to 0x00000028 at address 0x7eb73c83 (thread 0018), starting debugger...
wine: Unhandled page fault on read access to 0x00000028 at address 0x7eb67c83 (thread 001c), starting debugger...
wine: Unhandled page fault on read access to 0x00000028 at address 0x7eb67c83 (thread 001e), starting debugger...
^C
I get the usual wine popup saying that "NOTEPAD.exe has encountered a serious problem and needs to close" (http://img410.imageshack.us/i/ekrangrnts1.png/)
But:
[miguel@WKM_MSI ~]$ cp /mnt/win_NTFS/WINDOWS/NOTEPAD.EXE /mnt/my_reiserfs_partition/
[miguel@WKM_MSI ~]$ wine /mnt/my_reiserfs_partition/NOTEPAD.EXE
And NOTEPAD works like a charm!
To answer usual questions:
- I gave each bin32-wine* package a try, even some old versions but none make any difference
- all lib32-* packages are installed (except for community/lib32-libgl and community/lib32-nvidia-utils which would conflict with my aur/lib32-nvidia-utils-beta)
- I tried several nvidia configuration but it really doesn't look like a video driver issue... rather a 64 problem
- I installed many things throught winetricks such as DirectX etc...
- I didn't find any similar issue on google
Here is how I mount my partitions if you think that could come from some right issues:
[miguel@WKM_MSI ~]$ cat /etc/fstab
/dev/sda1 /mnt/win_NTFS ntfs-3g users,locale=en_US.utf8 0 0
/dev/sda8 /mnt/my_reiserfs_partition reiserfs defaults 0 0
Some threads with similar problems but no mention of the "partition behavior"
http://bbs.archlinux.org/viewtopic.php?id=60639
http://bbs.archlinux.org/viewtopic.php?id=80394
http://bbs.archlinux.org/viewtopic.php?id=80703
Any clue would be apreciated!
Cheers!
(and keep on the good job )

Hi Slightlystoopid!
Thanks for the idea but that doesn't look like it. I tried the "umask" but no luck!
Actually the line I quoted in the original post was already "experimental". My usual fstab before I tried this one was:
/dev/sda1 /mnt/win_NTFS ntfs-3g users,uid=1000,gid=100,fmask=0113,dmask=0002,locale=fr_FR.utf8 0 0
/dev/sda8 /mnt/my_reiserfs_partition reiserfs defaults 0 0
That gives me:
[root@WKM_MSI miguel]# ll /mnt/
total 8.0K
drwxrwxr-x 1 miguel users 8.0K 2009-09-23 10:42 win_NTFS
drwxrwxrwx 12 root root 384 2009-09-23 10:33 my_reiserfs_partition
Which doesn't work neither!
BTW as we talk about it: "my_reiserfs_partition" is owned by root! Isn't it a security issue? I mean: I can read/write/execute on it as regular user but shouldn't it be mounted with the same rights as /mnt/win_NTFS?
Still interested in any piece of advice on the original issue !

Time Machine hoses external NTFS partition?

A friend of mine, a fresh convert from WIndows, attached her external 1TB NTFS-formatted (Windows Vista) disc, wanting to transfer files from it to the internal HD.
For some reason Time Machine appropriated the drive and placed a Time Machine partition on it, taking up close to the whole space (1TB). I assume Time Machine in a friendly manner asked if she wanted to make backups to this external drive without having some kind of protocol on informing the user that this will overwrite existing information.
It was only when Time Machine was about to make a backup writing to this partition she mentioned it for me via chat and I immediately told her to stop Time Machine from doing that. She then shared her screen with me so I could investigate, which I did with Disk Utility after turning Time Machine off completely. It shows the Time Machine partition on the disk, but no NTFS partition is acknowledged.
What I assume have happened is that for whatever reason OS X wasn't able to see the NTFS partition and instead treated the disk as an unformatted device. Then Time Machine put a partition on it.
When doing so, I hope Time Machine didn't write zeros all over the disc and it's a good chance the files in the NTFS-partition is still there. And if it didn't write over the NTFS-partition part, that may also be there.
However, as far I know the NTFS-partition should be visible in Disk Utility. Which is isn't. That's a bit scary.
My next course of action is to use a file recovery application from a Windows machine on this drive in hope that files can be rescued. As we don't have access to an empty 1TB drive it would be even better, if the Time Machine partition could be just removed and the NTFS-partition repaired or reinstated.
Any ideas on how to proceed?

Mikael Bystrom wrote:
I assume Time Machine in a friendly manner asked if she wanted to make backups to this external drive without having some kind of protocol on informing the user that this will overwrite existing information.
Yes, similar to this one:
|
|
What I assume have happened is that for whatever reason OS X wasn't able to see the NTFS partition and instead treated the disk as an unformatted device. Then Time Machine put a partition on it.
It reformatted it. The NTFS partition is gone. Time Machine can only back up to an HFS+ journalled volume.
When doing so, I hope Time Machine didn't write zeros all over the disc and it's a good chance the files in the NTFS-partition is still there. And if it didn't write over the NTFS-partition part, that may also be there.
Correct. A +data recovery+ app should be able to recover most of it.

No option to make an NTFS partition

Similar Messages

Maybe you are looking for