Check all your ext* and vfat partitions automatically

[musher0]

Hi, L18L.

Thanks for your interest. But... are you serious? Your script is not a joke?
You really use it:?:

Your script is tiny all right, but it generates lots of impossibilities (not to say errors),
and it produces very crude results. See attached capture pics in fs-check-L18L.tar.xz
downloadable from http://www63.zippyshare.com/v/91633346/file.html.
By golly, your script even wants to check swaps and mounted partitions!

Under the circumstances, I'll keep my script! It's way more precise and more polite
to the disk!

But of course you did not explain anything... You just threw your script there.
Please explain more and maybe I'll change my judgment. Thanks in advance.

BFN.

musher0

[musher0]

@L18L

I looked at your code again. Your "echo $par-blahblah" had thrown me off.

So... for the sake of argument, the following should limit the damage, by
* beginning with a "umount" command
-- running fsck on a mounted partition is dangerous, remember?
and then
* excluding the swap(s)s and the secondary partition "holders",
-- these being usually partitions 3 and 4 on any large drive
-- or swap can on partition 2, on simpler drive constitutions
-- or 4 if you're not using the secondary holder
-- (so we'd have to do detective work for this anyway)
and of course
* remounting the partitions afterwards. Of what use is a clean , but unmounted
partition, eh?

Code: Select all

umount -a -t vfat,ext2,ext3,ext4;for dev in /sys/block/sd*;do cd $dev;for f in `ls -1d sd* | awk -F"/" '$1 !~ /3|4/ { print $1 }'`;do fsck /dev/$f;done;done;mount -a -t vfat,ext2,ext3,ext4

Also, neither your script nor mine take into account the fact that fsck requires different
settings for vfat and ext? partitions to do any correction of value. Again, detective work
will be necessary here to give fsck the proper settings for the partition.

As I said, this is "for the sake or argument"... In real life, this probably means bye-bye one-liner!

My 2¢. BFN.

musher0

[musher0]

Many thanks to Detective Awk! (edited)

Code: Select all

typ="t vfat,ext2,ext3,ext4";df -T | awk '$2 ~ /vfat|ext/ && $1 !~ /loop/ && $7 !~ /save/ { print "fsck."$2" -p -v "$1 }' > cmnds;chmod 770 cmnds;umount -a -$typ;./cmnds;mount -a -$typ;rm -f cmnds

BFN.

musher0

[L18L]

..it generates lots of impossibilities (not to say errors),
and it produces very crude results. See attached capture pics in fs-check-L18L.tar.xz
downloadable from http://www63.zippyshare.com/v/91633346/file.html.
By golly, your script even wants to check swaps and mounted partitions!

From that url one can download flash...... (not for me)

I have posted my results:
dosfsck for my /dev/sda1
and
e2fsck for the other partitions
and
Cannot continue, aborting. for a mounted partition
and I cannot see anything crude with these.

Now repeating it in slacko57
Larger output

Code: Select all

# time for dev in /sys/block/sd*; do echo ; cd $dev; for f in `echo $par*`; do cmd="fsck /dev/$f" ;  echo $cmd; $cmd ;echo ;done;echo =================; done 

fsck /dev/alignment_offset
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/alignment_offset
Possibly non-existent device?

fsck /dev/bdi
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/bdi
Possibly non-existent device?

fsck /dev/capability
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/capability
Possibly non-existent device?

fsck /dev/dev
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/dev
Possibly non-existent device?

fsck /dev/device
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/device
Possibly non-existent device?

fsck /dev/discard_alignment
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/discard_alignment
Possibly non-existent device?

fsck /dev/events
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/events
Possibly non-existent device?

fsck /dev/events_async
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/events_async
Possibly non-existent device?

fsck /dev/events_poll_msecs
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/events_poll_msecs
Possibly non-existent device?

fsck /dev/ext_range
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/ext_range
Possibly non-existent device?

fsck /dev/holders
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/holders
Possibly non-existent device?

fsck /dev/inflight
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/inflight
Possibly non-existent device?

fsck /dev/power
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/power
Possibly non-existent device?

fsck /dev/queue
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/queue
Possibly non-existent device?

fsck /dev/range
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/range
Possibly non-existent device?

fsck /dev/removable
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/removable
Possibly non-existent device?

fsck /dev/ro
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/ro
Possibly non-existent device?

fsck /dev/sda1
fsck from util-linux 2.21.2
dosfsck 3.0.11, 24 Dec 2010, FAT32, LFN
/dev/sda1: 5164 files, 47477/51693 clusters

fsck /dev/sda2
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
boot: clean, 30/4016 files, 11430/16064 blocks

fsck /dev/sda3
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
/dev/sda3: clean, 81562/1872304 files, 6898018/7476249 blocks

fsck /dev/size
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/size
Possibly non-existent device?

fsck /dev/slaves
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/slaves
Possibly non-existent device?

fsck /dev/stat
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/stat
Possibly non-existent device?

fsck /dev/subsystem
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/subsystem
Possibly non-existent device?

fsck /dev/uevent
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/uevent
Possibly non-existent device?

=================

fsck /dev/alignment_offset
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/alignment_offset
Possibly non-existent device?

fsck /dev/bdi
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/bdi
Possibly non-existent device?

fsck /dev/capability
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/capability
Possibly non-existent device?

fsck /dev/dev
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/dev
Possibly non-existent device?

fsck /dev/device
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/device
Possibly non-existent device?

fsck /dev/discard_alignment
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/discard_alignment
Possibly non-existent device?

fsck /dev/events
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/events
Possibly non-existent device?

fsck /dev/events_async
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/events_async
Possibly non-existent device?

fsck /dev/events_poll_msecs
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/events_poll_msecs
Possibly non-existent device?

fsck /dev/ext_range
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/ext_range
Possibly non-existent device?

fsck /dev/holders
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/holders
Possibly non-existent device?

fsck /dev/inflight
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/inflight
Possibly non-existent device?

fsck /dev/power
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/power
Possibly non-existent device?

fsck /dev/queue
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/queue
Possibly non-existent device?

fsck /dev/range
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/range
Possibly non-existent device?

fsck /dev/removable
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/removable
Possibly non-existent device?

fsck /dev/ro
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/ro
Possibly non-existent device?

fsck /dev/sdb1
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
/dev/sdb1: clean, 15/1616 files, 467/6456 blocks

fsck /dev/sdb2
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
/dev/sdb2 is mounted.
e2fsck: Cannot continue, aborting.



fsck /dev/size
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/size
Possibly non-existent device?

fsck /dev/slaves
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/slaves
Possibly non-existent device?

fsck /dev/stat
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/stat
Possibly non-existent device?

fsck /dev/subsystem
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/subsystem
Possibly non-existent device?

fsck /dev/uevent
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
fsck.ext2: Datei oder Verzeichnis nicht gefunden while trying to open /dev/uevent
Possibly non-existent device?

=================

real	0m1.321s
user	0m0.323s
sys	0m0.560s
#

Nothing crude or harmful, just larger

Mystery of electronics

You want code explained:
compose a command cmd
display command
execute command
in 2 for loops

[musher0]

Hello, L18L.

I rest my case. Those results are basically what the uploaded capture pictures contain.
~~~~~~~~~~~~
Of course, you have a partition named /dev/slaves!!!
Of course, you have a partition named /dev/capability!!!
Of course, you have a partition named /dev/inflight!!!
Of course, you have a partition named /dev/discarded alignment!!!

Everybody does! People save stuff on those partitions all the time!
~~~~~~~~~~~~~

That's what I call crude. You do what you want, no offense intended,
but that's not my style.

I like precise. Something like

Code: Select all

fsck /dev/sdb1

Now there's a real fsck command -- almost. The other ones, not so much.

musher0

~~~~~~~~~~~~~~~~~~
PS. Since you like jokes, I fsck my /dev/beard every morning in my /dev/mirror!
(hehe)

[some1]

Hi
FWIW,I liked L18L's approach - fast indeed..but
a pet probably needs more than a one-liner.

L18Lcode:
"Special" case:Old e2fsck-version -throws a "WARNING" - when the
pupsave-partition is encountered-without any gracefull resolution.
In my case the pupsave-partition was the last one,so the job was finished -
but what if the pupsave was on sda1 ?

But as said - an older e2fsck.
---
@L18L,Musher0:
My own take on this is a much clumsier walk of the devs - so thanks for
the efforts/ideas/insights.

Cheers

[musher0]

Hello all.

Sticking to my guns until I get a logical explanation -- and actual proof
that L18L's solution actually checks anything. When L18L states that
"this is the mystery of electronics", it is an insult to my mind.

I've stood up against this kind of racket in teaching all my adult life, and
I will not stop now. Either the experienced one or the teacher has a logical
explanation or he/she does not. You don't send your apprentice to pasture
for three weeks, laughing at them, when they sincerely wish to learn. If
Mr. L18L has so much experience and is such a great programmer, will
he please explain with valid references that his solution is not simply a
put-down -- for reasons he only understands -- of what I've done so far
on this subject? Because that's what it looks like at present from a
human relations stand-point. If you don't come up with a rational
explanation, rest assured that I'll make sure that your reputation stays
where it is now, in my mind, at least: I mean, down there. Thank you in
advance for obliging me.

Taken together,

/dev/slaves
and
/dev/handlers

look like they should be reported to the Immigration Police!

Since they are not proper partitions, they have no place in a fsck script, IMO.

Besides, does L18L's one-liner correct anything? As far as I can tell;
it just blazes over the partitions field, listing what is already known,
with a lot of useless info in between.

In any case, choose what you will. The important thing here is that the
partitions get properly checked. Clean partitions are faster, that's a fact.

BFN.

musher0

[L18L]

My "one-liner" was really NOT a solution.

I am in Quirky Tahr now, there things are different again.

Step by step:
There was 1 mistake that made all the nonsense appear.

Step 1
Change the one-line to (and do not execute that is : without $cmd;)

Code: Select all

 for dev in /sys/block/sd*; do echo ; cd $dev; for f in `echo ${dev##*/}*`; do cmd="fsck /dev/$f" ;  echo $cmd; echo ;done;echo =================; done

and I am getting that what you can see in attached image. That is the core of my idea.

Step 2
If I am changing it to execute the fsck commands:

Code: Select all

 for dev in /sys/block/sd*; do echo ; cd $dev; for f in `echo ${dev##*/}*`; do cmd="fsck /dev/$f" ;  echo $cmd; $cmd; echo ;done;echo =================; done

Code: Select all

# 
# for dev in /sys/block/sd*; do echo ; cd $dev; for f in `echo ${dev##*/}*`; do cmd="fsck /dev/$f" ;  echo $cmd; $cmd; echo ;done;echo =================; done

fsck /dev/sda1
fsck from util-linux 2.21.2
CP437: Das Argument ist ungültig
fsck.fat 3.0.25 (2014-01-17)
/dev/sda1: 5164 files, 47477/51693 clusters

fsck /dev/sda2
fsck from util-linux 2.21.2
e2fsck 1.42.9 (28-Dec-2013)
boot: clean, 30/4016 files, 11430/16064 blocks

fsck /dev/sda3
fsck from util-linux 2.21.2
e2fsck 1.42.9 (28-Dec-2013)
/dev/sda3: clean, 81563/1872304 files, 6899710/7476249 blocks

=================

fsck /dev/sdb1
fsck from util-linux 2.21.2
CP437: Das Argument ist ungültig
fsck.fat 3.0.25 (2014-01-17)
/dev/sdb1: 7 files, 1517/8167 clusters

fsck /dev/sdb2
fsck from util-linux 2.21.2
e2fsck 1.42.9 (28-Dec-2013)
/dev/sdb2 is mounted.
e2fsck: Cannot continue, aborting.



=================

fsck /dev/sdc1
fsck from util-linux 2.21.2
e2fsck 1.42.9 (28-Dec-2013)
/dev/sdc1: clean, 15/1616 files, 467/6456 blocks

fsck /dev/sdc2
fsck from util-linux 2.21.2
e2fsck 1.42.9 (28-Dec-2013)
/dev/sdc2: clean, 3546/244800 files, 601549/977327 blocks

=================
# 

Hope that helps

for dev in /sys/block/sd*; do
echo # a blanc line
cd $dev
for f in `echo ${dev##*/}*`; do
cmd="fsck /dev/$f" # compose a command
echo $cmd # show the command
$cmd # execute the command
echo # a blanc line
done
echo =================
done

[musher0]

Thanks.

[musher0]

Hello, all.

some1's picture (see his attachment above) prompted me to do another upgrade.

This one excludes more CD/DVD formats, so /dev/sr0, etc. shouldn't appear in the
list, and no attempt to check them be made.

While I was at it, I specifically excluded other most common filesystems that may be
used by other Linuxes.

The first post of this thread has been updated.

BFN.

musher0

[musher0]

Hello, all.

I just added a how-to and some add'l info to my 1st post.

Enjoy! BFN.

musher0

[Sylvander]

1. Installed automverif-11a.pet within Slacko-5.5.91.
a. Tried to run it using the entry that had been placed in the "Menu" [under "Filesystem" methinks: now no entry to be seen, even after running fixmenus in terminal], but nothing happened.
b. Tried typing the beginning of automverif in a terminal and hitting <tab>, but nothing showed.
c. So I decided to "not save" the session and rebooted.
However...
d. Once back into the desktop, automverif auto-ran and scanned just fine.
Except...
e. It reported that my sda5 partition, auto-mounted because it holds the slackosave.4fs file...
Had NOT been scanned, due to being unable to be dismounted, and aught to be scanned using a "live" Puppy optical disk, for example.
SO....

2. I booted my multi-session DVD-RW holding Precise-5.6.1, and once at the desktop, installed automverif-11a.pet, rebooted and saved [to a folder] at shutdown/reboot.
BUT....
a. When it was attempting to boot, it FAILED to do so [it normally succeeds].
So now I have a multi-session DVD-RW that no longer boots.
b. Tried booting into Slacko to take a look at the contents of the Precise multi-session DVD-RW, but sr0 doesn't appear on the desktop.
c. Does that mean the filesystem on the DVD-RW is no longer readable?
d. Is it possible to recover the DVD-RW to a working state?

[musher0]

Hello, Sylvander.

Thankis for the confirmation of try-out in your # 1.
As to # 1 b), you have to open a terminal in folder
/root/my-applications/Systeme/automverif/11

Code: Select all

cd /root/my-applications/Systeme/automverif/11

and type

Code: Select all

./automverif11-direct.sh 

(note the ./ in front) -- if that's how you want to run it.

As to your # 2, various thoughts, in no particular order:
* is it the same Puppy in # 1 and # 2? If the same Puppy[number].sfs is on the disc and
on the hard drive, you may get a kernel panic message. Try to reboot from your DVD
with the "pfix=ram" parameter.

* why save to folder if the purpose of this session is to check a partition? Try erasing
this recent pupsave in particular -- and only that one! -- from your hard drive. Me, I'd
save the CD/DVD session to the CD/DVD -- if I was to use this DVD only for checking
the partitions.

* did you reboot your DVD with the parameter " pfix=ram "?

* maybe a hair, some dust or a tea stain has recently found its way to the surface of
your DVD?

* the new version of automverif specifically excludes checking any CD or DVD format,
so the automverif script will not have even tried to look at /dev/sr0. I did test the script
with music and data CD's in the sr0, and they weren't checked. Besides, there is no
fsck.iso9660 utility to check a data CD/DVD, it doesn't exist. So it has to be another
factor.

Finally -- it has nothing to do with your DVD problem and it's none of my business, of
course -- : I find it strange that you saved to a folder from your DVD boot and you did
not save to your regular pupsave from your HD boot.

I hope the above will help. BFN.

musher0

[Sylvander]

1. "As to # 1 b), you have to open a terminal in folder
/root/my-applications/Systeme/automverif/11"
Did as you instructed here, and it worked just fine.

2. "As to your # 2, various thoughts, in no particular order:
* is it the same Puppy in # 1 and # 2? If the same Puppy[number].sfs is on the disc and
on the hard drive, you may get a kernel panic message."
Hmm, there is indeed a puppy_precise_5.6.1.sfs in a folder on a partition on the internal HDD.
This has never produced any problem prior to now.
Regardless; I've deleted the SFS file on the HDD.
Perhaps the multi-session DVD_RW will now boot successfully.
No, it doesn't boot; the UEFI bios halts like it doesn't know what to do, so I hit F11 to get a boot menu and tell it to boot the optical drive, which it does, but all it then does is display a flashing underscore on a black screen

3. "Try to reboot from your DVD
with the "pfix=ram" parameter."
Will try that, but I don't think the multi-session Puppy on the DVD-RW boots to that point, so I expect that attempt to be unsuccessful.
As expected the boot doesn't get this far, so I'm unable to do this

4. "why save to folder if the purpose of this session is to check a partition?"
I thought it would be handy to have that capability built into the multi-session DVD-RW.
Then I'd be able to use it to scan&fix ALL the PFS's on the internal HDD.

5. "Try erasing this recent pupsave in particular -- and only that one! -- from your hard drive."
I fail to understand your thinking here.
The Slacko that is using the slackosave on the internal HDD is working just fine; so why would I erase the slackosave?

6. "Me, I'd
save the CD/DVD session to the CD/DVD -- if I was to use this DVD only for checking
the partitions."
That's exactly what I did.

7. "did you reboot your DVD with the parameter " pfix=ram "?"
Not yet, but I'll try that [if the disk boots to that point, which I don't think it does->It doesn't].

8. "maybe a hair, some dust or a tea stain has recently found its way to the surface of
your DVD?"
Nah...no way, it's pretty clean, but I polished it anyway.

9. "the new version of automverif specifically excludes checking any CD or DVD format,
so the automverif script will not have even tried to look at /dev/sr0."
I was aware of that, and I like that, which is why I decided to include/install it in the multi-session Puppy on the DVD-RW.

10. "I find it strange that you saved to a folder from your DVD boot and you did
not save to your regular pupsave from your HD boot."
The reason I decided to NOT save the session changes to the Slacko-5.5.91 with the slackosave on the internal HDD:
It seemed as though the automverif install had failed.
It wouldn't run either of the 2 ways I tried.
And yet it HAD installed OK and is working fine after that subsequent reboot, and...
Strange to say...
Not saving the session failed to prevent the session changes persisting.
I wondered it you'd built that feature->[immediate autosave] into your program/script.

11. "I hope the above will help."
Thank you for your assistance; much appreciated.

[musher0]

Hi, Sylvander.

Your # 2 caught my attention. So you have:
* a computer with the new UEFI bios;
* the same puppy on CD and on hard drive.

I believe your UEFI bios is behaving properly, however annoying the UEFI idea in itself
can be for us Linuxians. (But all my computers are oldish, so I have no real experience
of UEFI.)

I think it's the same Puppy that's the problem. Here's a tentative explanation:

If we boot from the Puppy Precise 5.7.1 DVD with the pfix=ram setting, we don't have
access to any DVD session, let alone the one where you stored the automverif script.

If we boot from the Puppy Precise 5.7.1 DVD without the prix=ram setting, the Puppy
boot process is confused, it doesn't know if it should load the Puppy Precise sfs from
HD or the one on CD/DVD, so it stops in the black terminal with the flashing underscore.
(If it doesn't send you a "kernel panic" message, too!)

I'd suggest trying a CD/DVD with any other version of Puppy (one version of Puppy
that you do NOT have on your hard drive). It could actually be a minimal or bare-
bones Puppy, it doesn't matter if we're going to use it only for disk or partition checking.
I'd suggest that you download and install the script on that CD/DVD Puppy, save the
session to CD/DVD and re-boot from this CD/DVD Puppy.

What happens then? Hopefully, success? Keep me posted? Thanks.

(I have dpup-4.86 on one partition and UpupRaring-3.992 on another, and both have
the automverif script installed. So I don't have the problem. I mostly use UpupRaring;
I use dpup on the other partition to check the partition UpupRaring is on [plus for the
nice mrxvt and a couple of other things, but that's not the subject!)

Best.

musher0

[Sylvander]

1. "I believe your UEFI bios is behaving properly"
So do I.
I think the DVD-RW has been messed up so it no longer has a readable filesystem on it.
Puppies can no longer see the filesystem; so sr0 no longer shows on a Puppy desktop when I put the DVD in the drawer and close the drawer.

2. "I have no real experience
of UEFI"
My experiences of it have been good; it seems to be smart, it responds to what it sees and automatically does the smart thing, so as to automatically boot the correct device.
e.g. It aught to be booting the optical disk in the drive, but it isn't seeing a filesystem on the disk, so it does nothing.
Then when I force it to attempt to boot the DVD-RW, the attempt fails [as the BIOS "knew" it would?]

3. "it doesn't know if it should load the Puppy Precise sfs from
HD or the one on CD/DVD, so it stops in the black terminal with the flashing underscore."
a. I have now deleted both the Precise SFS file and the precisesave file from the internal HDD, so the Precise-5.6.1 Puppy on the multi-session DVD-RW cannot see anything but its own files on the DVD, and yet it still goes to a black screen with flashing underscore.
b. Surely if it hasn't booted so far as offering the command prompt, then it cannot have yet searched for Puppy files on other drives.
I'm inclined to think it is halting at a VERY early stage; if it's booting the Puppy at all.
I suspect the UEFI BIOS is attempting to find a bootable OS on the DVD and finding nothing; not even a readable file system.

4. "I'd suggest trying a CD/DVD with any other version of Puppy (one version of Puppy
that you do NOT have on your hard drive). It could actually be a minimal or bare-
bones Puppy, it doesn't matter if we're going to use it only for disk or partition checking.
I'd suggest that you download and install the script on that CD/DVD Puppy, save the
session to CD/DVD and re-boot from this CD/DVD Puppy."
I'm hoping to save/recover this existing multi-session DVD-RW. [Anyone know how?]
If forced, I'll make a new DVD-RW of a Puppy version I don't have on the internal HDD, but that must wait until I have both the inclination and the opportunity.

[Jasper]

Hi Sylvander,

Logic dictates, in your case, the chance that there is anything wrong with your DVD that cannot be fixed using F2 and “puppy pfix=1“ is almost zero.

Since you cannot reach F2 - first test your DVD drive - ideally using a different Multi--session-DVD-RW. If you don’t have one, perhaps make one. If that doesn’t work then investigate your BIOS settings.

If you boot using any Puppy - can you insert and mount the DVD and see inside your dated save folders? If so, in the most unlikely event it becomes necessary, you should be able to make a working replica of that DVD.

With a Multi-session-CD/DVD the main sfs will always load into RAM from an internal Hard Drive if it is found there. That may take only a couple of seconds. However, if, when it’s working again, it takes say. ten or twenty + seconds to load your 150-200MB sfs into RAM it will be from your DVD.

If all else fails - put your engineering hat back on and think and test.

[Ted Dog]

On a rare situation a earilier DVD filesystem image can affect current filesystem. if an area is readible and not writable the past can haunt your DVD-RW. I had a DVD-RW that I used for years that has a stuck bit at the 700M mark. Still use it for testing ( a known bad disc is useful for testing )
I have been using a md5sum checkfiles on my own multisession upgrades to check disks after burn. DVD-RW seem to have a 2 to 3 year lifespan under use. Where DVD-R are readible missus scratches for 7 plus years.

[Sylvander]

@Jasper

1. "Since you cannot reach F2 - first test your DVD drive - ideally using a different Multi--session-DVD-RW."
Done:
I looked out yet another multi-session DVD-RW that holds Lighthouse64-6.02-B2-Mariner->[previously used and known to be functional].
It works just fine; I'm typing this from it right now.
Prior to trying it, I noticed that when I put it into my DVD-RW drive and closed the drawer, whilst running in Slacko-5.5.91, sr0 showed on the desktop, unlike the Precise-5.6.1 multi-session DVD-RW, which doesn't show [as sr0 or anything] on the desktop.

2. "If you boot using any Puppy - can you insert and mount the DVD and see inside your dated save folders?"
Here in Lighthouse64 I believe I've managed [not simple] to [dismount Lighthouse64 and eject its DVD, then insert the Precise-5.6.1 DVD-RW, close drawer and] view the contents on the multi-session DVD-RW which aught to hold Precise-5.6.1.
BUT:
It's showng ONLY:
AppRun size=11 K [kilobytes]
AppInfo.xml size=758 B [bytes]
This seems to me to suggest that the original contents of the disk have been overwritten rather than having a save folder added.
Yet I believe I did the correct thing when I shutdown the multi-session, and chose to "Save" the session changes back to the DVD-RW.
Something must have gone wrong.

[musher0]

Hi, Sylvander.

Your # 2 above: Sounds like you just left-clicked on the icon. If you right-click on it, there
are other choices, among which there's a "mount". Did you try that?

BFN.

musher0