Fine ! I finally did it ! Just had to read the answears to my posts more than twice, with no hurry, all I needed was there.
sudo mount -t vfat /dev/loop0p14 /media/jean-luc/bigdos allowed me to access the files from within the bigdos folder
that I previously had created under /media/jean-luc !
So, I think now I can try and go further in my quest !
Thanks all for helping,
J.-Luc
> Message du 30/07/15 21:09
> De : "Jean-Luc CECCOLI" <jean-luc.ceccoli@wanadoo.fr>
> A : "Markus Fröschle" <mfro@mubf.de>, mint@lists.fishpool.fi
> Copie à :
> Objet : Re: [MiNT] Need help to resurrect a Falcon + CT60
>
>> Wow !
> Due to my very poor knowledge of Linux, I might have missed something very important if I hadn't paid further attention to
> some minor thing.
> The IDE image being on a usb stick, I already noticed that right-clicking on to it and selecting "Mount..." did indeed mount the
> MiNT partition, but none of the 14 others. Or so did I believe, until I lauched the disk partition tool and... could see the image
> mounted as 20 GB Loop Device, showing all 15 partitions with their sizes and all marked as unknown for content and type,
> except #15 marked as ext2 v1.0 type ! They all are listed as /dev/loop0p1 to /dev/loop0p15 (read only).
> Now, next step would be to find how to tell the system that #14 is TOS (or DOS ?) partition.
> Gparted can't see it, so I can't use it to modify its type.
> I'm going to google if I can find any useful information.
>
> Regards,
>
> J.-Luc
>
> Message du 30/07/15 00:45
> De : "Jean-Luc CECCOLI" <jean-luc.ceccoli@wanadoo.fr>
> A : "Markus Fröschle" <mfro@mubf.de>, mint@lists.fishpool.fi
> Copie à :
> Objet : Re: [MiNT] Need help to resurrect a Falcon + CT60
>
>> > 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.
> >
> > Regards,
> >
> > J.-Luc
> >
> >
> >
> Message du 28/07/15 19:10
> De : "Markus Fröschle" <mfro@mubf.de>
> A : mint@lists.fishpool.fi
> 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).
>
>
>