[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Unable to mount UDF Volume




>________________________________
>From: Raf Czlonka <rjc@linuxstuff.pl>
>To: debian-user@lists.debian.org
>Sent: Friday, October 7, 2011 7:49 AM
>Subject: Re: Unable to mount UDF Volume
>
>On Thu, Oct 06, 2011 at 09:12:28PM BST, Steven Sciame wrote:
>> I tried to manually mount the volume and got the same error
>> 
>> debtop:/# mount -r /dev/sr0 /media/cdrom
>> mount: wrong fs type, bad option, bad superblock on /dev/sr0,
>>        missing codepage or helper program, or other error
>>        In some cases useful info is found in syslog - try
>>        dmesg | tail  or so
>
>Have you tried:
>
>% modprobe udf

>


Yes.  That had the same result.


>> It just works as expected on the Ubuntu laptop, but I don't have access to that one all of the time.  Mine is running Debian Squeeze. 
>
>Could you paste the corresponding lines from /etc/fstab from both
>systems, please?
>


Here is the fstab from Squeeze:

steven@debtop:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# /dev/hda1       /               ext3    errors=remount-ro 0       1
UUID=c12d7448-3eb9-4c84-b82b-442573f5ac9e       /               ext3    errors=remount-ro 0       1
# /dev/hda5       none            swap    sw              0       0
UUID=c50682ae-a43a-45b0-972d-895318f408ad       none            swap    sw              0       0
# /dev/hdc        /media/cdrom0   udf,iso9660 user,noauto     0       0
/dev/cdrom        /media/cdrom0   udf,iso9660 user,noauto     0       0
steven@debtop:~$ 


And here it is from Ubuntu

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sda1 during installation
UUID=50d4ee6b-e884-42bc-bc6d-eef3368d8297 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
#UUID=f16cde95-9c92-474c-9a55-4ece1616d3a7 none            swap    sw              0       0
/dev/mapper/cryptswap1 none swap sw 0 0


What do you think?


Reply to: