-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option to format partition only (not whole disk) #24
Comments
Hi @lucky62, thanks for your message! If I'm understanding you correctly, then format-udf can currently do what you're asking: Just invoke with You may be able to use a pre-existing non-entire-disk partition by invoking Does this help? Please report back on your results if you end up using |
When partition is formatted under linux by mkudffs it is not recognized by Windows 7 and probably also other Windows versions. Also when partition is formatted under Windows it is not recognized by Linux. So working script will be very useful. |
Hello again, Sorry, I must not be understanding you. If you use the script as directed (i.e. entire disk), it will work on both Linux and Windows. The only way to get Windows to recognize UDF drives is to use the entire disk and write a fake MBR. Please see the README. If I'm missing the point altogether, please forgive me, and explain exactly what you're looking for. Thanks! |
Hi, sorry for unclear comment. But my internal disk is partitioned to 3 partitions. One is Windows 7 system partition, second is Linux system partition (multi-boot) and third is data partition shared by both systems. Currently I am using NTFS file system on shared partition. My intention is to format this shared partition as UDF. The problem is that when partition is formatted by mkudffs in Linux then it is not recognized by Windows and vice versa - when partition is formatted in Windows (by format utility in command line), then it is not recognized by Linux. I tried many variations of formatting parameters (blocksize, etc.) - no success. Your script I cannot use, because it is not designed to format single partition. It would be good to add this option to your script. Most probably you already have the required knowledge for this. |
Hi @lucky62, thanks for taking the time to explain. I think I understand now. This is an interesting edge case. I'm not fully confident that the resultant drive will auto-mount on Windows (or perhaps mount at all). But, I'm willing to code it up if you're willing to be my tester. Deal? I may be able to get to this as soon as Friday, but no guarantees. In order for me to ensure that I'm hitting the right target, it's important for me to understand your setup. Is your current partition table MBR or GPT? |
Hi JElchison, |
Hi @lucky62, the ball is in your court! Please clone/test from https://github.com/JElchison/format-udf/tree/dev-single-existing-partition Please report back with your results. If this meets your liking, I will merge this branch into master and release it. |
Hi, Few comments:
I see that "/dev/$DEVICE" pattern is used many times in your script so I think better is to check at the beginning if has the "/dev/" prefix and add it if not. Then you can use simple "$DEVICE" intead of "/dev/$DEVICE". |
Hi again, |
Hi @lucky62, thanks for the quick turnaround! I will merge/release later today. I will try to address your comments in order.
The disk geometry is tied to your physical device, and will not differ between operating systems. You're likely running into item 2 above. It's probably behaving differently because of the partition table mismatch. I recommend attempting to change the partition type to FAT32 ( Another possibility is that your HDD doesn't have the standard block size of 512. Windows has been known to choke on certain devices. See the issue history for more info. Thanks again for your help! |
It would be good to have the option to format single partition on partitioned disk.
I know that this will not work with OS X. But it will be useful for peoples using only Linux and Windows.
The text was updated successfully, but these errors were encountered: