I'm having problem with a USB external drive, which seem to be formatted with UDF and was being used for MAC and Windows (or at least that is what told). When I attached the HDD to my Linux system the next are the dmesg entries: [21784.312960] usb 2-1.2: new high-speed USB device number 5 using ehci-pci **[21784.406283] usb 2-1.2: New USB device found, idVendor=1058, idProduct=1023** [21784.406291] usb 2-1.2: New USB device strings: Mfr=1,Product=2,SerialNumber=3 [21784.406296] usb 2-1.2: Product: Elements 1023 **[21784.406299] usb 2-1.2: Manufacturer: Western Digital** [21784.406303] usb 2-1.2: SerialNumber: [21784.406815] scsi8 : usb-storage 2-1.2:1.0 [21785.403470] scsi 8:0:0:0: Direct-Access WD Elements 1023 2005 PQ: 0 ANSI: 4 [21785.404686] sd 8:0:0:0: Attached scsi generic sg2 type 0 [21785.409491] sd 8:0:0:0: [sdb] 1953519616 512-byte logical blocks: (1.00 TB/931 GiB) [21785.410605] sd 8:0:0:0: [sdb] Test WP failed, assume Write Enabled [21785.411723] sd 8:0:0:0: [sdb] Asking for cache data failed [21785.411729] sd 8:0:0:0: [sdb] Assuming drive cache: write through [21785.413600] sd 8:0:0:0: [sdb] Test WP failed, assume Write Enabled [21785.414603] sd 8:0:0:0: [sdb] Asking for cache data failed [21785.414609] sd 8:0:0:0: [sdb] Assuming drive cache: write through **[21785.449997] sdb: sdb1 ** [21785.452466] sd 8:0:0:0: [sdb] Test WP failed, assume Write Enabled [21785.453503] sd 8:0:0:0: [sdb] Asking for cache data failed [21785.453515] sd 8:0:0:0: [sdb] Assuming drive cache: write through [21785.453524] sd 8:0:0:0: [sdb] Attached SCSI disk With that information the HDD seem to be OK. However I'm unable to identify the type of partition (some commands from Windows console show is UDF but I can't confirm with Linux counterparts) Trying to get more information, the fdisk -l outputs: Disk /dev/sdb: 1000.2 GB, 1000202043392 bytes 255 heads, 63 sectors/track, 121600 cylinders, total 1953519616 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 Disk identifier: 0x0bba88f0 Device Boot Start End Blocks Id System /dev/sdb1 0 1953519615 976759808 5 Extended fdisk: unable to read /dev/sdb1: Inappropriate ioctl for device As the partition doesn't mount, tools like testdisk and fsck can't work here (well testdisk and photorec just freeze trying to read the HDD). And due the size of the disk the badblocks command takes a lot of time (and is still running). I can't find many material about the UDF format (and I don't understand why a HDD use it when is ) and neither what to do when is unable to read any partition at all. Any suggestion?

I'm renting a node on a linux server.

uname -a
Linux 5.15.112-gentoo #2 SMP x86_64 AMD 64-Core Processor Authentic AMD GNU/Linux

By nature as a renter I can't become superuser or even use sudo. I need to read/mount a UDF filesystem stored in a .ISO format. I looked into fuseISO as an option with the command

fuseiso ~/files/iso.iso ~/mountpoint

but it appears this only handles ISO9660 format and not UDF. So I just get a bunch of error messages when attempting to use fuseiso. I thought also maybe a tool exists that can read a UDF .iso and export the contents without mounting it at all. My research is stuck does anyone have any suggestions if one even exists.

I recently discovered some old double-sided mini dvd-rw disks (2.8GB) which were used for recording video with a Sony DCR-DVD201E handycam. Both sides already had content but they were unfinalized so I could not mount them on my Ubuntu 22.04 box. I proceeded with finalizing them through the camera. One side worked fine. But the other one didn't: The disk now appears as almost full of data (~1.3GB out of 1.4GB) but something seems to be wrong with the filesystem, which appears completely empty of files or folders both on my computer AND the camera. Note that the disk does *not* contain any bad blocks and it does not cause any read errors. So we're not talking about medium failures or hardware-related issue. Judging from other disks created and finalized by the same camera (including the other side of this disk), the filesystem should contain something like this:

VIDEO_TS/
VIDEO_TS/
VIDEO_TS/VIDEO_TS.BUP
VIDEO_TS/VIDEO_TS.IFO
VIDEO_TS/VIDEO_TS.VOB
VIDEO_TS/VTS_01_0.BUP
VIDEO_TS/VTS_01_0.IFO
VIDEO_TS/VTS_01_1.VOB
:
:

The output of dvd+rw-mediainfo is the following:

$ dvd+rw-mediainfo /dev/sr0
INQUIRY:                [HL-DT-ST][DVDRAM GP57EB40 ][RF01]
GET [CURRENT] CONFIGURATION:
 Mounted Media:         13h, DVD-RW Restricted Overwrite
 Media ID:              TDK502sakuM3
 Current Write Speed:   2.0x1385=2770KB/s
 Write Speed #0:        2.0x1385=2770KB/s
 Speed Descriptor#0:    00/716191 R@6.0x1385=8310KB/s W@2.0x1385=2770KB/s
READ DVD STRUCTURE[#10h]:
 Media Book Type:       00h, DVD-ROM book [revision 0]
 Legacy lead-out at:    716800*2KB=1468006400
READ DVD STRUCTURE[#0h]:
 Media Book Type:       32h, DVD-RW book [revision 2]
 Last border-out at:    2045*2KB=4188160
READ DISC INFORMATION:
 Disc status:           complete
 Number of Sessions:    1
 State of Last Session: complete
 Number of Tracks:      1
READ FORMAT CAPACITIES:
 formatted:		690544*2048=1414234112
 00h(800):		716192*2048=1466761216
 10h(10):		716192*2048=1466761216
 13h(10):		25648*2048=52527104
 15h(10):		716192*2048=1466761216
READ TRACK INFORMATION[#1]:
 Track State:           complete incremental
 Track Start Address:   0*2KB
 Free Blocks:           0*2KB
 Fixed Packet Size:     16*2KB
 Track Size:            690544*2KB
FABRICATED TOC:
 Track#1  :             14@0
 Track#AA :             14@690544
 Multi-session Info:    #1@0
READ CAPACITY:          690544*2048=1414234112

K3b reports the following: However if you mount the disk, ls, du, etc. show 0 data/files/folders. I ripped the contents using dd:

dd bs=2048 skip=0 count=690544 if=/dev/sr0 of=./out.iso

The output file is recognized via file command as:

out.iso: UDF filesystem data (version 1.5) '2009_06_27_05H54M_PM'

Then I tried udfinfo:

filename=out.iso
label=2009_06_27_05H54M_PM
uuid=00a8784b20202020
lvid=2009_06_27_05H54M_PM
vid=SONY_MOBILE
vsid=        SONY_MOBILE_VOLUME_SET
fsid=SONY_MOBILE_FILE_SET
fullvsid=00A8784B        SONY_MOBILE_VOLUME_SET
owner=
organization=
contact=
appid=
impid=*SONY_MOBILE
winserialnum=0x709b0f01
blocksize=2048
blocks=690544
usedblocks=690268
freeblocks=0
behindblocks=0
numfiles=0
numdirs=1
udfrev=1.02
udfwriterev=1.02
integrity=closed
accesstype=readonly
softwriteprotect=yes
hardwriteprotect=yes
start=16, blocks=5, type=VRS
start=32, blocks=16, type=MVDS
start=48, blocks=16, type=RVDS
start=64, blocks=1, type=LVID
start=256, blocks=1, type=ANCHOR
start=260, blocks=690268, type=PSPACE
start=690543, blocks=1, type=ANCHOR

I mounted it and tried photorec but it produces multiple small mpeg files, many of which are unplayable and which are probably part of a bigger VOB file that doesn't show up. Since I know that the disc contains VOB files, I tried ffmpeg just in case it could somehow skip the "garbage" and transcode it into something useful, however if failed:

out.iso: Invalid data found when processing input

Handbrake also failed to recognize any data when I tried to use the file as a source, although it does work properly with the directory structure of other disks possessing the VIDEO_TS folder I showed earlier. Then I tried opening the out.iso file with VLC. That one actually DID work, i.e. it started streaming video content, however with some issues: - You cannot navigate in the video as timestamps/index is broken - Converting it to mp4 creates a video with stuttering, broken timestamps, etc.. - It is obvious that it doesn't contain the whole video. Most probably the camera broke the content into multiple VOB files, so at some point it stops reading I tried to recode one of the mp4 files that I produced using VLC, even with shorter length than expected, in order to be able to see proper length (in seconds) and navigate using a player, but ffmpeg produced the following errors in the output without fixing them in the final output file:

ffmpeg -fflags +igndts -i vlc-converted.mp4 -vcodec libx264 -acodec aac fixed.mp4
:
[aac @ 0x555e72b0a6c0] Queue input is backward in time
[mp4 @ 0x555e72afe980] Non-monotonous DTS in output stream 0:1; previous: 143927607, current: 143927095; changing to 143927608. This may result in incorrect timestamps in the output file.
[aac @ 0x555e72b0a6c0] Queue input is backward in time
[mp4 @ 0x555e72afe980] Non-monotonous DTS in output stream 0:1; previous: 143933751, current: 143933239; changing to 143933752. This may result in incorrect timestamps in the output file.
:

So the questions are these: - Are you aware of any (linux) tool that can discover files in a UDF filesystem which contains the data but obviously doesn't have proper filesystem entries for them? - If no UDF tool exists, are you aware of any tool that can specifically recognize VOB files from a raw filesystem and "restore" them as ddrescue would do? - If none of the above is possible, do you know any ffmpeg trick or alternative tool that could at least fix the timestamp indexes of the portion of the video stream that VLC managed to convert?

I'm trying to use a CD on CentOS 6.4, but I keep getting this error:

Unable to mount Disc Error mounting: mount: unknown filesystem type 'udf'

I've installed udftools I've tried changing the permissions around on /dev/sr0 to no avail. I've tried various ways of mounting the disc such as: - mount /dev/sr0 /mnt (unknown filesystem type 'udf') - mount -t auto /dev/sr0 /mnt (unknown filesystem type 'udf') - mount -r -t iso9660 /dev/sr0 /mnt (wrong fs type...) - mount -t udf /dev/sr0 /mnt (unknown filesystem type 'udf', despite being in the man page for mount) - dd if=/dev/sr0 of=disc.iso -> mount -o loop disc.iso /mnt -t iso9660 I can see and read from the disc just fine in a VM on that host and on other physical machines. It also seems to happen with just about every disc that I've tried. Any thoughts?

So, it's that time of year when I need to make a backup disk of some files on a Windows machine, and I want to use UDF so that I can add to it later. It's refusing to let me create *any* CDs or DVDs since it says the disk is empty and needs formatting, and then *won't let me format them*... And yes, the disks have never been used (yet) and are un-scratched and so on. It also won't let me edit some disks that I **know** were made with Windows' own utility for this (Live Filesystem, which is basically UDF as well), so I'm just going to squint at that and move on. (Interestingly, I **can** open & modify those in Linux...) So, I went over to my Linux (Ubuntu 18.04) machine and tried to make a UDF-formatted disk with mkudffs (since multisession disks work correctly with absolutely NOTHING, apparently, at least not anymore [I made one once around the Ubuntu 14.04 days, but they haven't actually been editable since, and it's expensive to test]) and it's superior anyway. I ran the command mkudffs --media-type=dvd /dev/sr0 and it dumps an error message "Device is read-only" (I don't have the exact wording, but that was all it said). Running the command as root didn't help, and I know for a *fact* that this has worked before. Interestingly, the "copy files to disk and burn" thing built into Nautilus worked just fine. Of course, checking the "Leave disk open for future additions" option didn't actually do anything (no surprise there), but it DID burn the files I had on hand. Now, for next time, what exactly is wrong that it won't let me UDF-format my darn CDs or DVDs?! [I have not tested with one of my DVD-RWs, but I have tried both CD and DVD just now (with the appropriate media-type flags) and got the same error. They are a bit old, but they are apparently still writable, it's just that for some reason mkudffs in particular is having issues with them.]

I have a couple of large files I want to burn to an M-Disc 50G BD-R DL. Files are larger than 4G so I have to use UDFv3, if I am not mistaken. (Or split, which I am not especially keen on doing.) A graphical tool is not an option (no X on the server and those do a remarkably bad job on that anyway in my experience) so what I plan on doing is the following: 1. find the capacity of my medium with dvd+rw-mediainfo. 2. create a temporary file with dd if=/dev/zero of=/tmp/bd.udf bs=2048 count=n with n being an integer extracted from mediainfo's output. 3. create a UDF filesystem on that temp with mkudffs -b 2048 -l somelabel /tmp/bd.udf 4. mount it with mount -o loop -t udf /tmp/bd.udf ./mntpt 5. populate it with my files cp xyz* mntpt/ 6. unmount it umount ./mntpt 7. burn it with growisofs -Z /dev/dvd=/tmp/bd.udf -speed=5 Please correct me if this is not a good procedure. I'd be grateful for improvements. What really confuses me is the output of dvd+rw-mediainfo: INQUIRY: [PIONEER ][BD-RW BDR-UD03][1.11] GET [CURRENT] CONFIGURATION: Mounted Media: 41h, BD-R SRM Media ID: VERBAT/IMf Current Write Speed: 6.0x4495=26970KB/s Write Speed #0: 6.0x4495=26970KB/s Write Speed #1: 4.0x4495=17980KB/s Write Speed #2: 2.0x4495=8990KB/s Speed Descriptor#0: 00/24438783 R@6.0x4495=26970KB/s W@6.0x4495=26970KB/s Speed Descriptor#1: 00/24438783 R@4.0x4495=17980KB/s W@4.0x4495=17980KB/s Speed Descriptor#2: 00/24438783 R@2.0x4495=8990KB/s W@2.0x4495=8990KB/s :-[ READ BD SPARE INFORMATION failed with SK=5h/MEDIUM NOT FORMATTED]: Wrong medium type READ DISC INFORMATION: Disc status: blank Number of Sessions: 1 State of Last Session: empty "Next" Track: 1 Number of Tracks: 1 READ FORMAT CAPACITIES: unformatted: 24438784*2048=50050629632 00h(6000): 23652352*2048=48440016896 32h(0): 23652352*2048=48440016896 32h(0): 11200512*2048=22938648576 32h(0): 24307712*2048=49782194176 READ TRACK INFORMATION[#1]: Track State: invisible incremental Track Start Address: 0*2KB Next Writable Address: 0*2KB Free Blocks: 24438784*2KB Track Size: 24438784*2KB READ CAPACITY: 0*2048=0 Should I use the "unformatted" block count for the temp file? What does "32h(0)" etc. mean? Is it necessary to somehow account for error correction spare blocks or something...? In a first test I used unformatted block count - 1 (don't ask me why;) ) and writing ends with an error message (that I unfortunately didn't record). The disc was readable though and md5 sums were fine. Can someone point me to a definitve guide for writing BDs on the command line?

My HDD Disk /dev/sdb: 927.5 GiB, 995875618816 bytes, 1945069568 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: 0xc4094bc2 Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 718847 716800 350M c W95 FAT32 (LBA) /dev/sdb2 718848 269154303 268435456 128G 7 HPFS/NTFS/exFAT /dev/sdb4 269156350 1945067519 1675911170 799.1G f W95 Ext'd (LBA) /dev/sdb5 403374080 1945067519 1541693440 735.1G 6 FAT16 /dev/sdb6 269156352 403374079 134217728 64G 83 Linux I have formatted /dev/sdb5 as udf with mkfs.udf --utf8 -l UDFStore /dev/sdb5 on Gentoo. But blkid doesn't list /dev/sdb5. How can I reliably mount my UDF partition at startup in /etc/fstab when device enumeration changes due to additional connected USB devices at startup.

sudo cdrwtool -i -d /dev/sr4 and dvd+rw-mediainfo /dev/sr4 do not indicate the UDF version.
(1.02, 1.50, 2.00, 2.01, 2.50, 2.60) ### How can I find out the UDF version of a DVD?

A few months ago I formatted half an ssd (for use by all of my operating systems as file storage, I use os x, Debian, and Microsoft's windows) It was recommended that I use udf, because it is, in most cases, compatible with the operating systems in question. However, I later began getting input output error messages, even when using a file manager to open the drive. rizk@rizk-bl-h:/media/rizk/LinuxUDF/torrents$ ls ls: cannot access 'legal_software.dmg': Input/output error The command then proceeds to list the rest of the files and directories in the folder. I figure, at least I have my files, but when trying to open them it always reads Failed to open directory "LinuxUDF". when getting information for file "/media/rizk/LinuxUDF/kj1WRC3.jpg": Input/output error. Leaving my files un-browsed. However I can open things such as torrent files through my torrent client, I cannot access anything outside of it, and the files in question seem corrupt and broken (for example videos play half through then stop playing entirely). Any ideas? edit: per request, here is the results of smartctl --all https://pastebin.com/GP2a9Gng

I couldn't assume that a file system can be converted to another in-place until I bumped into btrfs-convert. I want to convert my 700GB/1TB ExFAT partition to UDF. Google has no answer for that. Is there a way to convert ExFAT to UDF?

It's embarrassing to imagine that there are no intelligent tools on Linux to create UDF images, similar to makeisofs, but I have yet to find any. The tool genisoimage does work for creating video disk images, but there is no equivalent for general data. Is the Linux toolset really so deficient when it comes to optical disc tools? I've already seen this and the accepted answer simply isn't sufficient.

In my search for the ideal filesystem to share files between a lot of computer with a lot of different OS'es I accepted this answer and installed a UDF filesystem on my USB stick. First I blanked the disk, to make sure there are no leftovers to confuse a system that's reading the drive: dd if=/dev/zero of=/dev/sdb bs=1M Then I formatted the drive, using udftools from arch linux's AUR: sudo mkudffs --media-type=hd --blocksize=512 /dev/sdb Obviously, the drive was in /dev/sdb. Now my question is, since the drive doesn't have any traditional partitions or even a partition table as far as I know, it does not have a UUID. Therefore, I can not add it to the fstab, which I find rather annoying. What can I do to fix this (e.g. is there an alternative way to set default mount point and options, or an alternate partitioning option)?

I've formatted a removable USB drive using UDF and would like to rename the partition. Currently the name of the drive is LinuxUDF on each machine I access it on. How can I rename the partition, preferably using command line tools?

I'm trying to create a UDF partition on a flash drive to install grub2 (to boot ISOs from) ~$ export DSK=/dev/sdd # wipe the disk ~$ sudo dd if=/dev/zero of=${DSK} bs=512 count=2048 ~$ sudo sgdisk --zap-all ${DSK} # create partition for udf ~$ #sudo parted -s ${DSK} mklable msdos ~$ #sudo parted -s ${DSK} -a optimal unit MB -- mkpart primary 1 -1 ~$ (echo o; echo n; echo p; echo 1; echo ; echo ; echo t ; echo 6 ; echo w) | sudo fdisk -b 512 ${DSK} ~$ sudo mkudffs --media-type=hd --blocksize=512 ${DSK}1 trying to change type of multiple extents

How to convert .bin/.cue files into DVD-ROM UDF-ISO file in linux ? I found that genisoimage can make CD-ROM UDF with that command: genisoimage -udf -o MY_FILE.iso ~/MY_DIR/ but I didn't find for DVD-ROM. Is there a program to do it on linux ? Thank you.

I would like install a proprietary operating system onto my CentOS box using VirtualBox. There is a problem though, when I mount the install ISO image as a DVD, soon the installer complains of missing DVD drivers. I tried to download some but they did not work. Now I want to circumvent the DVD issue and I would like to create a virtual disk image of the install ISO. The forum discussion [ISO To VDI VBoxManage convertfromraw Not Bootable](https://forums.virtualbox.org/viewtopic.php?f=1&t=37765) says that >I am trying to make a bootable vdi from a bootable ISO >for linux guest. I am running >VBoxManage convertfromraw source.iso output.vdi >I get a valid vdi that I can attach and read but I cannot boot from it. Any idea how to solve this. for an experienced forum user says >To use "convertfromraw" your starting point (as the name implies) has to be a raw image of a hard disk - which an ISO image most certainly is not. In spite of this, is there a Unix way of creating a bootable hard disk image of a Windows 7 install disk? And, to create a .vdi file of that?

Somebody knows what the maximum size of file could be processed by create_compressed_fs tool or used by /dev/cloop device? I suspect that it could be the root of the issue. I created "ISO" (UDF) image with: genisoimage --allow-limited-size command and then passed it through the create_compressed_fs. But mounting on /dev/cloop is failed with reason: cloop: final offset wrong (73........ not 61........)

I know for a fact, that Live CD versions of distros like Arch Linux, Debian, Fedora, Gentoo Linux, Salix, Ubuntu and on embedded distributions such as the OpenWrt and DD-WRT router firmware use [SquashFS]. But I was convinced, that optical media is practically bound to ISO9660 or UDF. I was thinking, that it might be a good idea to use SquashFS for recovery partitions, as it works well on hard drives as well. Another idea I had was: how about using it on other optical media? Most CD/DVD/BD-R is WORM anyway, so using SquashFS should be a step forward, given the transparent compression and all. I don't know if that would actually work though. How do those non-UDF/ISO9660 filesystems on optical media work? Does it work anywhere else as well?