One copy of map broken ...

Hi,

Booting my raspberry pi today it failed with the error …

Error: Unable to create files in “SDFS::Riscpi.$.Scrap.ScrapDirs”, error returned is: “One copy of map is broken (use *CheckMap)” (Error number &6)

I tried CheckMap but it gave the error “Map inconsistent with the directory tree”.

Can it be fixed?

Rachel

“One copy of map is broken (use *CheckMap)”

Yes, it’s somewhat misleading as CheckMap is supposed to allow you to copy a good map over a bad one (the help says: CheckMap checks that the map of a new map disc has the correct checksums, and is consistent with the directory tree. If only one copy is good it allows you
to rewrite the other.), but to my knowledge that never worked. Or if it did, it was Arthur or RISC OS 2…

Did you suffer a powercut? Brownout? Unusual crash? What has happened is that the map – which tells RISC OS where to find stuff on the disc – has become messed up.

Can it be fixed?

https://armclub.org.uk/products/discknight/

Do you take images of your SD cards? If so, you could revert to a recent image? If only !Scrap is affected, you may be able to set up a new SD card, then insert the other in a reader and copy data across? However, if this error was caused by a long-standing problem that just got bad enough that things started going wrong, there may be corruption elsewhere in the filesystem. DiscKnight is your best bet for working out what’s actually gone wrong…

Thanks Rick,

I have placed my order and paid my £12 (inc. VAT). I have every hope that this will fix it when it arrives. After many “fresh starts” over the years I was finally rather happy with this image and was only thinking yesterday that I really should burn it down to an .img file so I can create fresh copies. Then… oh well.

Rachel

was only thinking yesterday that I really should burn it down to an .img file so I can create fresh copies. Then… oh well.

Okay… Hands up who’s been there, done that.

Hands up who’s been there, done that.

Too much counting. Can we go for the shorter list instead?

Do you take images of your SD cards?

I used to. but, time consuming.

One copy of map is broken

Not seen that since I moved to using filecore formatted mSATA SSD drives, life is so much easier and more reliable.

I only use simple FAT formatted SD cards for the initial pi boot. Just 6 files (7 if you count the Broadcom licence file). Easily copied on virtually any computer.

The FAT formatted mSATA drives are easily copied without using images and there is no “Loader” to worry about.

Simple filecore formatted memory sticks can also be used. (Easier to deal with physically than mSATA – just plug direct to a USB port. But without the inherent reliability of mSATA.

Of course, RISCOS on the Pi has got much more stable anyway after the introduction of the seperate ‘CMOS’ file.

You can boot off the msata drive on pi3/pi3+ No sdcard required

Thank you for that John. Sounds like a good idea. I’ll give it a go. I now have a use for at least one of the usb sticks that have been gathering dust since the global IT department blocked all the USB ports.

Hi,

Just having a play around to see how this works.

- I made a fresh image on a mini USB which boots the pi.
- I formatted a USB stick with !Hform and I it mounts OK.
- I copied the contents of the RISCOSpi drive to the USB stick.

What commands do I need to make this use the !Boot on here rather than in RISCOSpi?

I tried …

*configure SCSI
*configure boot

It mounts the hard disk and shows the command prompt in the little window but it does not start up the Wimp

configure SCSI

That should be :-

*Configure FileSystem SCSI

You might also need to *Configure SCSIFSDrive 0 (or 4).

You can boot off the mSATA drive on pi3/pi3+ No sdcard required

Yes. See my post here

https://www.riscosopen.org/forum/forums/5/topics/10690

If the Pi set to boot from mSATA finds an SD card, it will boot from that.

You might also need to *Configure SCSIFSDrive 0 (or 4).

Yes. drive 0 for a flash memory stick or drive 4 for SSD or mSATA

The first time you set this up, the SD card will still bave the, now unused, bootable system on it which you can go back to by typing
*configure filesystem SDFS

Keep that SD card for emergency use. But thereafter you can use a simple FAT formated SD card (straight from the shop) with just the 5 files from the original Loader partition. So much easier and safer to update (as is the mSATA, SSD or memory stick drive.

Building (and backing up) additional Pi systems is now also so much easier and safer. (no images to play with)

Thank you all or your help.

I think I did type “*Configure FileSystem SCSI” just not into the forum reply box :-)

I will try *Configure SCSIFSDrive 0 when I get home from the dentists tonight.

So Disk Knight worked a treat and I now have my favorite image back. So I have carefully taken an image of it and stored it away correctly in some obscure location which I will forget where it is and will never find again.

… and I have now copied the contents to a 32 GB USB stick and have managed to get that set up as the boot disk. Which is nice.