Digging an original Raspberry PI out of the loft, I decided Risc OS
probably could do with and upgrade and cleanup as I wish to lend it to
someone else.. I decided the simplest way would be to download the RISC OS Direct distribution, which I have done.

This appears to be a 16G disc image and it was recommended to use 16G
upwards SD card. I decided to use a 32G card as it would leave me with
plenty of free space.

Having gone through the process and installed it in my Pi, "Free" tells me
it is 7G in total and there is 2G free for my stuff.

What happened to the other 9G of the image and, more importantly how can I
get access to the other 25G to store my files?

--
Stuart Winsor

Tools With A Mission
sending tools across the world
http://www.twam.co.uk/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <59ed2b73b3Spambin@argonet.co.uk>, Stuart
<Spambin@argonet.co.uk> wrote:

Digging an original Raspberry PI out of the loft, I decided Risc OS
probably could do with and upgrade and cleanup as I wish to lend it
to someone else.. I decided the simplest way would be to download
the RISC OS Direct distribution, which I have done.

This appears to be a 16G disc image and it was recommended to use
16G upwards SD card. I decided to use a 32G card as it would leave
me with plenty of free space.

Having gone through the process and installed it in my Pi, "Free"
tells me it is 7G in total and there is 2G free for my stuff.

What happened to the other 9G of the image and, more importantly
how can I get access to the other 25G to store my files?

I've just had a look at my old RISC OS Direct SD card version 5.27
(06-Feb-20) and it reports something very similar. Using the
recommended BalenaEtcher app on the PC, I generated (in 2021) RISC OS
Direct on a 16GB SD card and when plugging into my Raspberry Pi seem to
get the same result as you.

Free reports Free 5GBytes, Used 1979MBytes and Size 7GBytes. A
software bug perhaps?

Richard

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <59ed2b73b3Spambin@argonet.co.uk>,
Stuart <Spambin@argonet.co.uk> wrote:

Digging an original Raspberry PI out of the loft, I decided Risc OS
probably could do with and upgrade and cleanup as I wish to lend it to someone else.. I decided the simplest way would be to download the RISC OS Direct distribution, which I have done.

This appears to be a 16G disc image and it was recommended to use
16G upwards SD card. I decided to use a 32G card as it would leave
me with plenty of free space.

Having gone through the process and installed it in my Pi, "Free"
tells me it is 7G in total and there is 2G free for my stuff.

What happened to the other 9G of the image and, more importantly
how can I get access to the other 25G to store my files?

Certainly when you burn Raspian - buster or bullseye to an sd card,
the card seems to become the size of the burnt on data with most of
the disc not allocated. I think this is because the download is a
complete disc partition.

In raspian you get this back using sudo raspi-config and option 6A1
which says - Expand partiiton to whole disc.

If it the same situation in RISCOS I've no idea how you expand the RO partition. Perhaps you could put the card back in the PC and allocate
the spare area to fat32 or some such.

Bob,

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Stuart, on 23 May, wrote:

Digging an original Raspberry PI out of the loft, I decided Risc OS
probably could do with and upgrade and cleanup as I wish to lend it to someone else.. I decided the simplest way would be to download the RISC OS Direct distribution, which I have done.

This appears to be a 16G disc image and it was recommended to use 16G
upwards SD card. I decided to use a 32G card as it would leave me with
plenty of free space.

It is a 16GB image, that is the size of the extracted img file. Oddly that
16GB image only contains a 7GB RISC OS disc image.

Having gone through the process and installed it in my Pi, "Free" tells me
it is 7G in total and there is 2G free for my stuff.

What happened to the other 9G of the image and, more importantly how can I get access to the other 25G to store my files?

SystemDisc from Elesar.

http://shop.elesar.co.uk/index.php?route=product/product&path=25&product_id=73


(MPro might have destroyed that URL.)

--
David Pitt

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 23/05/2022 21:48, Bob Latham wrote:

In article <59ed2b73b3Spambin@argonet.co.uk>,
Stuart <Spambin@argonet.co.uk> wrote:

This appears to be a 16G disc image and it was recommended to use
16G upwards SD card. I decided to use a 32G card as it would leave
me with plenty of free space.

Having gone through the process and installed it in my Pi, "Free"
tells me it is 7G in total and there is 2G free for my stuff.

Certainly when you burn Raspian - buster or bullseye to an sd card,
the card seems to become the size of the burnt on data with most of
the disc not allocated. I think this is because the download is a
complete disc partition.

In raspian you get this back using sudo raspi-config and option 6A1
which says - Expand partiiton to whole disc.

When you burn a Linux image, it only takes up part of the SD card, but
either automatically when it is first run, or manually using
raspi-config, a resize2fs command is run to expand the partition to the
full size of the card.

If it the same situation in RISCOS I've no idea how you expand the RO partition. Perhaps you could put the card back in the PC and allocate
the spare area to fat32 or some such.

I did look at doing this for RISC OS, but due to the vulgarities of the FileCore format expanding the filing system may require moving every
single file so they align to new boundaries, which would take longer
then copying to a new card, and would be fatal if interrupted.

I did think of various hideous bodges to initial format to make the
expansion easier and quicker, but the bigger the card you allow the
filing system expand to, the more compromised it becomes at smaller
sizes. The standard 8GB isn't yet full, and when it is they should just
move to 16GB as the documentation claims.

In the end I said no to doing it. It's a lot quicker and safer to just
copy all the RISC OS files to a new card, and if you want to use
substantially more storage, don't use a big SD card, get a proper SSD
which is faster and far more reliable.

---druck

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)