Well, it seems nothing wants to work the way it ought to...
Here is what I got :
jean-luc@E4300:~$ losetup -p /dev/loop0 recup.img
loop : impossible d'obtenir les renseignements sur le périphérique recup.img : Ioctl() inappropré pour un périphérique.
The img file is at the root of my home folder, and I used autocompletion to ensure that it would be correctly accessed.
If I try and mount the image using the GUI, it only mounts the MiNT partition. The one that got corrupted by several
aborts during Falcon boot.
That would be fine if I could for instance repair it, re-inject it into the image and then re-dd the image top the disk so
I finally can boot my Falcon again.
But, unfortunately, I don't think this can be done.
But now is time to bed.
> Message du 28/07/15 19:10
> De : "Markus Fröschle" <firstname.lastname@example.org>
> A : email@example.com
> Copie à :
> Objet : Re: [MiNT] Need help to resurrect a Falcon + CT60
> Am 27.07.2015 um 10:47 schrieb Miro Kropáček:
> > Maybe this also works but I doubt it: sudo mount
> > -o loop.
> Unfortunately, Linux loop devices do not support byte swapping.
> However, it should work here since he dd'ed the image with conv=swab.
> But it's not as simple as just mounting a loop device, because the image
> probably contains more than just a single partition. You first need to
> setup the image apropriately:
> losetup -P /dev/loop0 image_file
> -P forces the kernel to scan the new device for partition information so
> you can later on mount slices of it as separate file systems. This will
> only work if your kernel has Atari partition support (which Ubuntu
> kernels usually have).
> If not, you'll need to extract the partition information manually (with
> an Atari tool under Aranym, for example). Once you know the partition
> start sector(s), you can set up loop devices with offsets into the image
> (which will skip the root sector for the first partition, the first
> partition for the second, and so on).
> Partition type to mount should be either "fatfs" (for TOS partitions) or
> "ext2" (for MiNT ext2 filesystems).