On Tue, Aug 17, 2010 at 7:08 AM, Ondrej Zary <linux@xxxxxxxxxxxxxxxxxxxx> wrote: > On Tuesday 17 August 2010, Tao Ma wrote: >> Hi Ondrej >> >> On 08/17/2010 12:50 AM, Ondrej Zary wrote: >> > On Monday 16 August 2010 16:18:57 Ondrej Zary wrote: >> >> On Monday 16 August 2010, Johannes Stezenbach wrote: >> >>> On Mon, Aug 16, 2010 at 02:38:54PM +0200, Ondrej Zary wrote: >> >>>> I have a CD that came with Samsung printer that Linux cannot mount but >> >>>> works fine in Windows. The CD is physically OK - "dd" made ISO image >> >>>> without any problems. This ISO image is unmountable too. When I force >> >>>> the filesystem to iso9660, it mounts but no files are visible: >> >>> >> >>> Maybe it's a multi-session disk where the first session is >> >>> HFS with Apple software. Try mounting with -t iso9660 -o session=1. >> >> >> >> Still the same - no files. dmesg contains: >> >> >> >> ISOFS: Invalid session number or type of track >> >> ISOFS: Invalid session number >> >> ISO 9660 Extensions: Microsoft Joliet Level 3 >> >> ISO 9660 Extensions: RRIP_1991A >> > >> > Here's the compressed ISO file if anyone wants to examine it: >> > http://www.rainbow-software.org/linux_files/samsung-bad.rar >> >> what is your kernel version? I can mount it successfully in my el5 box >> with kernel 2.6.35+. > > I have 2.6.35. Also tried it on another two machines with Debian Squeeze > 2.6.32 and Lenny 2.6.26 with the same result (no files visible when mounted). > > > -- > Ondrej Zary > -- > To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > Try -unide mount option. If it does not work, try what is described in the last posts of this thread: http://www.pubbs.net/200910/kernel/12764-iso9660-mount-problem.html Regards -- A. C. Censi accensi [em] gmail [ponto] com accensi [em] montreal [ponto] com [ponto] br -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
