Re: how to rescue this backup data

Zhang Weiwu <[email protected]> wrote:

> But then why mount would not work?
>         
>         Jamaica:~ # mount /dev/sr1 /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 helper program, or other error
>                In some cases useful info is found in syslog - try
>                dmesg | tail  or so

If the medium was ever written correctly in multi-border mode, then
even a dumb kernel should be able to mont the first session.
         
>         Jamaica:~ # dmesg | tail
>         wlan0: authenticate with AP 00:25:86:01:8a:de
>         wlan0: authentication with AP 00:25:86:01:8a:de timed out
>         grow_buffers: requested out-of-range block 18446744073708710576
>         for device hdc
>         UDF-fs: No anchor found
>         UDF-fs: No partition found (1)
>         UDF-fs: No anchor found
>         UDF-fs: No partition found (1)

Did you run "isodebug -i input-file" for the medium?
If it does not print something like:

ISO-9660 image includes checksum signature for correct inode numbers.
ISO-9660 image created at Mon Jan  4 14:33:10 2010

Cmdline: '2.01.01a71 -o ooo OBJ'

the images have not been created with mkisofs and for this reason, there
may be an incorrect UDF hybrid filesystem on the medium.

Jörg

-- 
 EMail:[email protected] (home) Jörg Schilling D-13353 Berlin
       [email protected]                (uni)  
       [email protected] (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]