On 12/26/05, Lan Barnes <[EMAIL PROTECTED]> wrote:
> FC4 with an Epmerex DVD RW using Sony DVD-Rs. I made an iso with mkisofs
> that I can mount and peruse on the loopback.
>
> The command I'm using to burn it is
>
> cdrecord -v -eject dev=/dev/hdc speed=32 -dao -driveropts=burnfree
> -data=/tv/pix.iso
>
> This burns happily and I can see the burned track on the DVD. But it
> won't mount:
>
> [EMAIL PROTECTED] tv]# mount -t iso9660 /dev/hdc /mnt
> mount: block device /dev/hdc is write-protected, mounting read-only
> mount: wrong fs type, bad option, bad superblock on /dev/hdc,
> missing codepage or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so
>
> So, doing what we are told
>
> [EMAIL PROTECTED] tv]# dmesg | tail
> ISO 9660 Extensions: Microsoft Joliet Level 1
> ISOFS: changing to secondary root
> cdrom: This disc doesn't have any tracks I recognize!
> attempt to access beyond end of device
> hdc: rw=0, want=68, limit=4
> isofs_fill_super: bread failed, dev=hdc, iso_blknum=16, block=16
> cdrom: This disc doesn't have any tracks I recognize!
> attempt to access beyond end of device
> hdc: rw=0, want=68, limit=4
> isofs_fill_super: bread failed, dev=hdc, iso_blknum=16, block=16
> [EMAIL PROTECTED] tv]#
>
> Does anyone have any insights/hints/recommendations? I can read, so a
> referral to a URL would be great.
Evidence points to the idea that pix.iso is not an ISO9660 file
system, despite its ".iso" name. What did you tell mkisofs when
creating that file? When you mount it as a loopback device, what file
system does the OS think it has?
carl
--
carl lowenstein marine physical lab u.c. san diego
[EMAIL PROTECTED]
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
