Read-only disk Puppy Linux problem (solved)

[oldaolgeezer]

When this problem first began occuring, I found that I was initially
debugging by "barking up the wrong tree".

In the last few weeks I had been suddenly getting "read only" error messages
whenever I try to copy a file or create a Folder onto my disks or SSD's.
I try to have similar data and Puppy software on many of my PC's and, as the
weeks went by, I noticed this problem was seeming to spread onto some of my other PC's !
(For example, when I now booted Bookworm, my Firefox would restore the browser tabs that were days or weeks old.
My /tmp or root folders and my flash drives would still read and write normally,
but when I tried to update my personal folders, a "read only" error message occured.)

I did a lot of Google searching about how to restore read/write
capability but a lot of the suggestions on the WEB said to recreate the entire disk !
https://askubuntu.com/questions/197459/ ... ile-system
Other disturbing suggestions mentioned: ... It looks like some mounted files have
got corrupted, and as a result, the kernel has set the file system
to RO to prevent further damage ...

But finally in the WEB comments I found this: ... to find which file system is
corrupted, run:

Code: Select all

cat /proc/mounts | grep -i ro
... and if you want to force your root filesystem to remount as rw, 
you can do the following:   mount -o remount,rw /

That last command or rebuilding, sounded too overpowering when all my files and folders looked intact.

On a PC that had the "read only" problem, I decided to at least display
my issue with their suggested cat command (I'll show only the first output line):

Code: Select all

cat /proc/mounts|grep -i ro

  /dev/sda3 /initrd/mnt/dev_save fuseblk ro,noatime,user_id=0,group_id=0,default_permissions,blksize=4096 0 0

I thought, what is this mystery "fuseblk" parameter, so I searched for it:
https://superuser.com/questions/563345/ ... ile-system
but down in the comments, I found:

Code: Select all

"Just a pointer to future readers 
that if mount displays "fuseblk", it usually means that the underlying 
filesystem is actually NTFS or exFat."

Thus, I thought, because my disks were formatted NTFS, "fuseblk" did
not imply disk data format corruption.

I finally fixed my problem by merely re-disabling hibernation with my Windows10,
shutting down Windows10 and merely rebooted my Puppy Linux Bookworm's ISO.
(I had disabled hibernation on my PC's which have had Puppy Linux
and Windows10 cohabitating for months and years. I guess recent updates
by Microsoft had recently re-installed hibernation.)

On my same PC after disabling hibernation in Windows10:

Code: Select all

cat /proc/mounts|grep -i ro

/dev/sda3 /initrd/mnt/dev_save fuseblk rw,noatime,user_id=0,group_id=0,default_permissions,blksize=4096 0 0

notice that the "fuseblk" parameter now has "rw"

I hope this long posting might help someone else.
Note: Years ago, with my older Puppy ISO versions, re-installed hibernation by Windows
manifested itself differently: It always showed me the Puppy's "first run" time zone screen
when booted:
https://oldforum.puppylinux.com/viewtop ... 1#p1038141