On Tue, Jun 17, 2008 at 09:44:29AM +0300, Shachar Shemesh wrote: > Lior Kaplan wrote: > > > >$ file myfs.iso > >myfs.iso: , 44.1 kHz, Stereo > > > >any ideas ? > > > > > > Yesterday I got that very same reply for the first 10KB of an ext-2 > image that someone changed its magic number. Viewed from khexedit, the > first block and something were just nulls.
The first 1024 bytes of ext2/3 are not used by the filesystem. They are intended to be used by a boot loader, in case this partition will need to be bootable. If it's not bootable, you can basically put there anything you want. At least a few times it happened to me that I formatted a partition as ext2/3 and when trying to mount it was wrongly identified as fat (which it was before) because the magic that identifies FSs saw fat cookies there, not deleted by mke2fs (as it's not used by it). In all such cases, (carefully!) deleting the first 1024 bytes solved this. To the OP: It's not clear if you managed to solve, or at least learn more about your problem. Did you try reading the entire disk? Is it readable? If you did, you can try mounting (with -o loop) the image file with different fs types (-t type, e.g. '-t vfat', '-t iso9660', etc.). Does the disk have several tracks? Does it work in some other OS? How does this OS identify the content? -- Didi ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
