This is probably trivial to check using cfdisk on a UDF-formatted CD/DVD/Blu-Ray, but I have neither of them at hand.

I have created an UDF formatted partition on a USB hard drive to share data between Linux and Windows computers (FAT doesn't handle 4GB files, NTFS access rights support is not stable under Linux). I have only one problem now - Windows refuses to mount the partition as the file system type id is set to '83' ('Linux'). I have looked quite extensively and can not find what number should I put there?

(follow-up: "With what tool should I format a hard drive as UDF?")

  • 2
    I don't think that you would get any meaningful results from executing cfdisk on a CD, DVD or Blu-Ray. Partitions are set by a few bytes of the MBR, which happens to exist in harddisks and pen-drives, not in floppies or optical media.
    – Juliano
    Jul 2, 2009 at 20:30

5 Answers 5


The answer is partition type 06 (FAT16). Don't ask me why, ask Microsoft.

  • 1
    5+ years later, this simple answer helped me immensely. Thank you “user48160” whoever and wherever you are now! Mar 12, 2015 at 6:26

It turns out there is no partition table for UDF and there is no partition ID assigned to it. This filesystem has to span the whole disk in oder to be recognized by Windows. Formatting a hard drive as UDF does not touch the existing partition table (be careful - it will contain stale information, and if you mount your drive using it, you will destroy the data!).

As a curiosity - UDF 2.5 and newer creates separate partitions (one or two per disk) for metadata. However, those partitions are also not visible in the standard DOS partition table.

  • 1
    Just formatted as UDF one of the (MBR) logical partitions on my hard drive and Windows 7 had no problem with it
    – MarcH
    Dec 29, 2011 at 23:49
  • @MarcH: so what partition ID does Windows or some tool report the partition as having? (had trouble to formulate the question, sorry if it's ill formed)
    – ata
    Mar 27, 2012 at 21:08
  • @Juaco scroll down for the answer. Or have a look at BOOTICE.
    – MarcH
    Mar 29, 2012 at 8:10
  • Some partitioning tools let you create partitions without file system. Exactly what you need to assign it a drive letter in Windows and then UDF format it.
    – DanMan
    Dec 16, 2013 at 11:09

Short answer: I would suggest to use MBR id 0x07 for UDF partitions.

Long answer:

Linux does not care about MBR partition ids and ignores it (*).

Windows 2000 and newer can assign a drive letter to the some partition with id PartitionType if and only if IsRecognizedPartition(PartitionType) is true. Moreover for non-FT partitions must hold that IsFTPartition(PartitionType) is false (otherwise that partition is detected as FT and not as ordinary FAT/NTFS/UDF/...).

Condition IsRecognizedPartition(PartitionType) && !IsFTPartition(PartitionType) apply for these MBR partition ids: 0x01, 0x04, 0x06, 0x07, 0x0B, 0x0C, 0x0E (**). Which means that Windows 2000 (and new) can recognize and use UDF partition if MBR partition id is one of those. There are probably no other restrictions and any supported file system accepts partition with any of those MBR id. Which means those MBR ids are not used for detection of file system.

But there are some recommendation by Microsoft when particular PartitionType should be used:

  • 0x01 - FAT12 primary partition or logical drive (fewer than 32,680 sectors in the volume)
  • 0x04 - FAT16 partition or logical drive (32,680–65,535 sectors or 16 MB–33 MB)
  • 0x06 - BIGDOS FAT16 partition or logical drive (33 MB–4 GB)
  • 0x07 - Installable File System (NTFS partition or logical drive)
  • 0x0B - FAT32 partition or logical drive
  • 0x0C - FAT32 partition or logical drive using BIOS INT 13h extensions (***)
  • 0x0E - BIGDOS FAT16 partition or logical drive using BIOS INT 13h extensions (***)

And also meaning by Microsoft:

  • 0x01 - Specifies a partition with 12-bit FAT entries.
  • 0x04 - Specifies a partition with 16-bit FAT entries.
  • 0x06 - Specifies an MS-DOS V4 huge partition.
  • 0x07 - Specifies an IFS partition.
  • 0x0B - Specifies a FAT32 partition.
  • 0x0C - Windows 95/98: Specifies a partition that uses extended INT 13 services.

On Wikipedia can be found also some recommendations:

  • 0x01 - CHS/LBA - DOS 2.0+ - FAT12 as primary partition in first physical 32 MB of disk ... (else use 0x06 instead)
  • 0x04 - CHS/LBA - DOS 3.0+ - FAT16 with less than 65536 sectors (32 MB) ... (else use 0x06 instead)
  • 0x06 - CHS/LBA - DOS 3.31+ - FAT16B with 65536 or more sectors. It must reside in first physical 8 GB of disk ... (else use 0x0E instead). Also used for FAT12 and FAT16 volumes in primary partitions if they are not residing in first physical 32 MB of disk.
  • 0x07 - CHS/LBA - OS/2 1.2+, Windows NT/CE - IFS/HPFS/NTFS/exFAT/QNX
  • 0x0B - CHS/LBA - DOS 7.1+ - FAT32 with CHS addressing
  • 0x0C - LBA - DOS 7.1+ - FAT32 with LBA
  • 0x0E - LBA - DOS 7.0+ - FAT16B with LBA

To complete list of ids, here is some information about older systems which do not support UDF formatted hard disk partition.

Windows NT 4.0 and older can assign a drive letter only to partitions with MBR id: 0x01, 0x04, 0x06, 0x07.

DOS-based Windows (95, 98 and ME) can assign a drive letter only to partitions with MBR ids: 0x01, 0x04, 0x06, 0x0B, 0x0C, 0x0E. MS-DOS itself can access only partitions with MBR ids: 0x01, 0x04, 0x06. Note that these systems uses MBR partition id for detection of file system. MBR partition id must match with file system on partition.


Look at partition size: 0x01 and 0x04 should be used only for partitions in first 32MB of disk. 0x06 only in first 8GB of disk. 0x0B is for CHS addressing which has limit for 8GB disks. So without such limits are only ids: 0x07, 0x0C and 0x0E. As 0x0C and 0x0E are used for FAT partitions I would suggest to choose 0x07. It is mean for IFS (Installable File System) partitions and according to Wikipedia, Microsoft added support for UDF into Windows 2000 IFS API. Usage of 0x0C or 0x0E would cause DOS-based systems to show that partition as FAT, even it would be formatted as UDF. Partitions with MBR id 0x07 are hidden on those systems. They do not support UDF, therefore it is better choice as 0x0C or 0x0E.


GPT partition layout is out of of this question, but it has similar problem as MBR. There is no partition GUID (GPT equivalent for MBR id) assigned for UDF. Because Windows XP x64 supports UDF and can recognize GPT data partition only with GUID EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft Basic Data Partition), it is the only possible choice for GPT.


(*) There is one exception: MBR Ids 0x05, 0x0F and 0x85 are used for detection of extended MBR partitions.
(**) Definitions of those two calls can be found in WinIoCtl.h file as they are declared as C macros.
(***) BIOS INT 13h extensions means usage of LBA instead CHS.

  • This page indicates that 0x0E partitions must be smaller than 2 GiB. Which means that for UDF, it's got to be either 0x07 or 0x0C. The latter sounds better to me, esp when you read the linked page. Impressive research, hats off!
    – Milind R
    Jul 1, 2017 at 6:10

On the CD's and DVD's I deal with, there is no partition table. On your USB hard drive, you've written a partition table to the media. I suspect if you format the entire drive as a UDF disk without the partition table, Windows will have no problem mounting it.

You don't say what size your USB drive is, and you might be reluctant to dedicate the whole drive as UDF, you could try setting the partition type with fdisk as NTFS or one of the other MS 'supported' types.

  • I am also booting Linux out of the same drive, so I need one partition to be of a format supported by grub. I just found out that grub2 (experimental) can boot Linux from UDF, so I will try this.
    – skolima
    Jul 3, 2009 at 8:54

I have got the same problem. My USB hard disk is 320GB. Partition table looks like this:

Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x44fdfe06

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1       27963   224612766    c  W95 FAT32 (LBA)
/dev/sda2           27964       38913    87955875    5  Extended
/dev/sda5           27964       33366    43399566    7  HPFS/NTFS
/dev/sda6           33367       38913    44556246   83  Linux

Partition sda5 is a UDF rev. 1.5 and shoulb be readable by Windows XP and above. Linux reads it properly of course. Windows however is confused. It recognise partition as NTFS and then it assumes it is raw partition.

My experiment with UDF on pendrive showed me that systems tend to mistake UDF with FAT. They interpret UDF as FAT. It must be quite large similarities because i can see directory stucture of random characters. Linux says that disk is corrupted but it don't refuse to use it.

I think UDF (at least rev 1.5) is not well supported on USB drives.

  • 1
    If the medium used to have FAT, there might be remains causing UDF to be confused with FAT. You should make sure the FAT is wiped/zeroed before formatting with UDF.
    – osvein
    Jun 11, 2016 at 11:37

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .