[Problem] MPF.Check: Pulling info from disc device path doesn't work in the Linux build #850

New Issue

Closed

opened 2026-01-29 16:23:20 +00:00 by claunia · 1 comment

claunia commented 2026-01-29 16:23:20 +00:00

Owner

Copy Link

Originally created by @gmipf on GitHub (Jul 3, 2025).

Originally assigned to: @mnadareski on GitHub.

Before You Submit

• Remember to try the latest WIP build to see if the issue has already been addressed.
• Is it copy protection related? If so, report the issue here instead.
• Check multiple discs to help narrow down the issue
• Check the Options to see if changing any of those affects your issue.

If all of those fail, then continue...

Version
What version are you using?

• [ x] Stable release (v3.3.2)
• [ x] WIP release (b806bc6cd1)

Build
What runtime version are you using?

• [ x] .NET 9.0 running on (Fedora 41)

As described in the wiki, I enter the drive path (/dev/sr0) after the -s -p parameters to scan for protections. It will clear at 0,00%. After mounting MPF still can't access files on the disc when specifying the drive path. Only after specifying the mount path of the disc the scan actually works.

Expected behaviour would be to gather info from the disc without mounting at all.

Another question is whether MPF.Check is able to do a sector level access for protection detection too or does it only do file access?

Credentials entered, will attempt Redump login...
Credentials accepted! Logged into Redump...
Redump username and password accepted!
Gathering submission information... please wait!
Extracting output information from output files...
Credentials entered, will attempt Redump login...
Credentials accepted! Logged into Redump...
Finding disc matches on Redump...
Single match found for f086c02149f35ade83c96f2e68b1a6d34657b5c7
Match finding complete! Fully Matched IDs: 49663
Processing ID: 049663
ID 049663 has been successfully downloaded
Filling fields from existing ID 49663...
Processing ID: 049663
ID 049663 has been successfully downloaded
Information filling complete!
Running copy protection scan... this might take a while!
0,00%:  - 
0,00%: /dev/sr0 - Checking file
Copy protection scan complete!
Extracting information complete!
Processing site codes...
100,00%: /dev/sr0 - 
Processing complete!
Formatting information...
Formatting complete!
Writing submission information file...
Writing complete!
Submission information process complete!

Originally created by @gmipf on GitHub (Jul 3, 2025). Originally assigned to: @mnadareski on GitHub. **Before You Submit** - Remember to try the [latest WIP build](https://github.com/SabreTools/MPF/releases/tag/rolling) to see if the issue has already been addressed. - Is it copy protection related? If so, report the issue [here](https://github.com/SabreTools/BinaryObjectScanner/issues) instead. - Check multiple discs to help narrow down the issue - Check the Options to see if changing any of those affects your issue. If all of those fail, then continue... **Version** What version are you using? - [ x] Stable release ([v3.3.2](https://github.com/SabreTools/MPF/releases/tag/3.3.2)) - [ x] WIP release (https://github.com/SabreTools/MPF/commit/b806bc6cd10d5527031a29765848fc2a77c73493) **Build** What runtime version are you using? - [ x] .NET 9.0 running on (Fedora 41) As described in the wiki, I enter the drive path (/dev/sr0) after the -s -p parameters to scan for protections. It will clear at 0,00%. After mounting MPF still can't access files on the disc when specifying the drive path. Only after specifying the mount path of the disc the scan actually works. Expected behaviour would be to gather info from the disc without mounting at all. Another question is whether MPF.Check is able to do a sector level access for protection detection too or does it only do file access? ``` Credentials entered, will attempt Redump login... Credentials accepted! Logged into Redump... Redump username and password accepted! Gathering submission information... please wait! Extracting output information from output files... Credentials entered, will attempt Redump login... Credentials accepted! Logged into Redump... Finding disc matches on Redump... Single match found for f086c02149f35ade83c96f2e68b1a6d34657b5c7 Match finding complete! Fully Matched IDs: 49663 Processing ID: 049663 ID 049663 has been successfully downloaded Filling fields from existing ID 49663... Processing ID: 049663 ID 049663 has been successfully downloaded Information filling complete! Running copy protection scan... this might take a while! 0,00%: - 0,00%: /dev/sr0 - Checking file Copy protection scan complete! Extracting information complete! Processing site codes... 100,00%: /dev/sr0 - Processing complete! Formatting information... Formatting complete! Writing submission information file... Writing complete! Submission information process complete! ```

claunia added the bug label 2026-01-29 16:23:20 +00:00

claunia closed this issue 2026-01-29 16:23:20 +00:00

claunia commented 2026-01-29 16:23:21 +00:00

Author

Owner

Copy Link

@mnadareski commented on GitHub (Jul 3, 2025):

To address in order:

• /dev/sr0 is a block device and not a mounted filesystem. The protection scanning in MPF has always been file-based, not scanning the device directly. The ability to add the mounted path to scan was added precisely for this reason, since Linux doesn't have an accessible filesystem at the same place that you'd be running the dump on, unlike Windows.
• Both MPF.CLI and MPF.Check use the same underlying libraries to do the work that they're doing. So the same applies that there is no sector-based access for protection scanning.

Neither of these things are likely to change due to how each OS that is supported by the dumping tools and by MPF work.

@mnadareski commented on GitHub (Jul 3, 2025): To address in order: - `/dev/sr0` is a block device and not a mounted filesystem. The protection scanning in MPF has always been file-based, not scanning the device directly. The ability to add the mounted path to scan was added precisely for this reason, since Linux doesn't have an accessible filesystem at the same place that you'd be running the dump on, unlike Windows. - Both MPF.CLI and MPF.Check use the same underlying libraries to do the work that they're doing. So the same applies that there is no sector-based access for protection scanning. Neither of these things are likely to change due to how each OS that is supported by the dumping tools and by MPF work.

claunia referenced this issue 2026-01-29 16:25:57 +00:00

[PR #850] [MERGED] Don't hash bad SS #1193

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

master

rolling

3.6.0

3.5.0

3.4.2

3.4.1

3.4.0

3.3.3

3.3.2

3.3.1

3.3.0

3.2.4

3.2.3

3.2.2

3.2.1

3.2.0

3.1.9

3.1.8

3.1.7

3.1.6

3.1.5

3.1.4

3.1.3

3.1.2

check-rolling

ui-rolling

3.1.1

3.1.0

3.0.3

3.0.2

3.0.1

3.0.0

2.7.5

2.7.4

2.7.3

2.7.2

2.7.1

2.7.0

2.6.6

2.6.5

2.6.4

2.6.3

2.6.2

2.6.1

2.6

2.5

2.4

2.3

2.2

2.1

2.0

1.18

1.17.1

1.17

1.16.1

1.16

1.15

1.14

1.13

1.12.2

1.12.1

1.12

1.11

1.10

1.07

1.06

1.05.1

1.05

1.04b

1.04a

1.04

1.03

1.02b

1.02

1.01d

1.01c

1.01b

Labels

Clear labels

bug

duplicate

enhancement

good first issue

help wanted

invalid

pull-request

Mirrored from GitHub Pull Request

question

regression

wontfix

No Label bug

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

claunia

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: SabreTools/MPF#850