checkmap on Pi SD image

Would somebody please run checkmap on the default SD image?

I get:

Map inconsistent with directory tree.

Run DiscKnight on it.

Would somebody please run checkmap on the default SD image?

*checkmap
Map inconsistent with directory tree
*`

Run DiscKnight on it.

...
---------------------------------------------
    Disc is bad, 5 faults found
    Run a repair (-f and -u flags) to fix
---------------------------------------------

DiscKnight fixes the issue and the maps are reported good, after a reboot.

Might I suggest that might be better done just once, at source? (Also, my copy of DiscKnight is on my RPc, so old.)

Why not just get the free update to DiscKnight as it is a valuable tool anyway since you have a copy already!

How do you know it’s the source SD Card as the issue.

How do you know it’s the source SD Card as the issue.

The problem affects both the 2024-04-28 release and the 2024-05-16 release of RISC OS Pi 5.30. This does rather point to a problem at the source.

A corrected test RISC OS Pi pCloud download is here. It is a DiscKnight’d version of the current ROOL download and as far as I can see there has been no data loss.

I further noticed that “Switch to DST automatically” is not configured.

@Chris, that’s why I asked for someone else to try it.

@David, thanks very much!

It might be an idea to let me have the verbose output from DiscKnight so I can tell if they are genuine faults, and not some new 5.30 format change.

It might be an idea to let me have the verbose output from DiscKnight so I can tell if they are genuine faults, and not some new 5.30 format change.

The verbose report is here.

not some new 5.30 format change

I’d hope that CheckMap could handle such a change!

At a quick look, seems like the source media is damaged…

I agree. Is there anything recognisable in the files in $.Lost+Found ?

Is there anything recognisable in the files in $.Lost+Found ?

No.

I would be suspicious of SE4.70a15 which is reported to have a rare but very well hidden bug. A while ago the Titanium had a happening that might have been the alpha StrongED or just as likely perhaps, something completely different. The seeds of doubt are sown though.

It would be prudent, now, to use the stable version of StrongED given that that can now handle more than 2GB of RAM.

Something unfortunate may have happened during the creation or updating of ROOL’s master source.