[ ] I was converting the image to another format...
[ ] I was retrieving image information...
[ ] I was retrieving filesystem information...
[X] I was listing the filesystem contents...
[X] I was extracting the filesystem contents...
[ ] I was creating a metadata sidecar...
[ ] I was checksumming the image...
[ ] I was verifying the image...
[ ] I was calculating the image entropy...
Destination image format
No response
Filesystem
FAT
Description
Two .ST images from the same Atari ST game have been downloaded from the Internet. I do not have any information on how the image was created.
One of the image (floppy A) is correctly handled by Aaru. Aaru detects the FAT filesystem and is able to perform file extract.
Aaru does not detect any filesystem from the second image (floppy B). The same image however can be mounted on Linux (losetup and then standard mount). Files can be accessed and copies from the mounted partition.
.ST images have been shared privately with @claunia
I cannot exclude that the "faulty" image can be ill-structured.
Exact command line used
aaru fs info
Expected behavior
Aaru identifies the filesystem and can extract the files.
Actual behavior
Aaru does not detect any filesystem
Output of command execution with debug output enabled
<Will be inserted later>
Affected image
.ST images have been shared privately with @claunia
Version
5.3.0
Commit hash
No response
Tested debug version?
Which operating systems have you used?
What is the architectural bit size you're using?
What processor are you using?
Image format
Raw .ST file format
Application that created the image
Unknown
What were you doing when it failed?
Destination image format
No response
Filesystem
FAT
Description
Two .ST images from the same Atari ST game have been downloaded from the Internet. I do not have any information on how the image was created.
One of the image (floppy A) is correctly handled by Aaru. Aaru detects the FAT filesystem and is able to perform file extract.
Aaru does not detect any filesystem from the second image (floppy B). The same image however can be mounted on Linux (losetup and then standard mount). Files can be accessed and copies from the mounted partition.
.ST images have been shared privately with @claunia
I cannot exclude that the "faulty" image can be ill-structured.
Exact command line used
aaru fs info
Expected behavior
Aaru identifies the filesystem and can extract the files.
Actual behavior
Aaru does not detect any filesystem
Output of command execution with debug output enabled
Affected image
.ST images have been shared privately with @claunia