Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sun 17 Dec 2017, 21:43
All times are UTC - 4
 Forum index » House Training » Users ( For the regulars )
2.14x filesystem-check problems (SOLVED)
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 3 [31 Posts]   Goto page: 1, 2, 3 Next
Author Message
Dewbie

Joined: 15 Apr 2010
Posts: 1779

PostPosted: Fri 01 Nov 2013, 03:28    Post subject:  2.14x filesystem-check problems (SOLVED)  

It's apparently there:
(line 141 of init)
Code:
# a function to run e2fsck on the save partition (passed as a param)
run_fsck(){
 if [ "$FSCK" = "yes" ] ; then
  echo -n "Perfoming periodic filesystem check on /dev/$1..." >/dev/console
  e2fsck -yv /dev/$1
  check_status 0
 fi
}

However, when fsck boot option is chosen, it never displays on the monitor during boot.
(I'm assuming save partition above refers to a save file.)

It only filesystem checks partitions during shutdown.
There's another fsck script for this in rc.shutdown, activated by the fsck boot option:
(line 935 of rc.shutdown)
Code:
# run periodic fsck on partitions
if grep -F -q 'fsck' /proc/cmdline ; then
 echo -e "\n\\033[1;35mRunning filesystem check on available partitions:\\033[0;39m\n"
 for APART in `probepart | grep -E 'ext2|ext3|minix|reiserfs' | cut -d'|' -f1`
 do
   # make sure it's not still mounted
   busybox mount | grep -F -q "$APART" && continue
   fsck -y $APART
   echo
 done

So I requested some input...
npierce wrote:
Quote:
I tested the function itself in an ash script and it worked OK for me. But I'm using Racy 5.2.2, which uses e2fsck 1.41.14 and the ash applet in BusyBox v1.19.3, so something could be different with Puppy 2.14x.

If the echoed message never appears on the console at all, then it is likely that the function never gets called at all, or $FSCK isn't being set.

I didn't see anything wrong with the code that looks for the boot option "pfix=fsck" and then sets FSCK="yes" (line 77).

So if the run_fsck() function is not being called, you will probably need to look closely at the code that is supposed to call it, which depends on the PUPMODE you are running (beginning at line 1439).

If run_fsck() is being called, you will need to look back in the code to see if the parameter being passed to run_fsck() ($PDEV1 or $SAVEPART, depending upon your PUPMODE) is being set correctly before the call.

Sorry that I couldn't be more helpful. I'm not the best person to ask about this, since I've never run a Puppy older than 4.3.1, and don't use save files.

I'm totally lost. Any suggestions?
214x-init.tar.gz
Description  init script from 2.14x
gz

 Download 
Filename  214x-init.tar.gz 
Filesize  20.52 KB 
Downloaded  180 Time(s) 
214x-rc_shutdown.tar.gz
Description  rc.shutdown script from 2.14x
gz

 Download 
Filename  214x-rc_shutdown.tar.gz 
Filesize  13.46 KB 
Downloaded  172 Time(s) 

Last edited by Dewbie on Thu 21 Nov 2013, 03:59; edited 2 times in total
Back to top
View user's profile Send private message 
mikeb


Joined: 23 Nov 2006
Posts: 11083

PostPosted: Fri 01 Nov 2013, 08:55    Post subject:  

no can't see it either.... looks like it will fsck ext2 or ext3 saves if pfix=fsck is set.
Are other pfix options working such as pfix=rdsh?

Only other suggestion is to debug each step with strategic echos to see what variables are set to and if functions actually get called.

I use a steamlined version of that init in all me pups so am a bit familiar.

It might be one of those right under your nose obvious things that get missed time...I love those Very Happy

Mike
Back to top
View user's profile Send private message 
Dewbie

Joined: 15 Apr 2010
Posts: 1779

PostPosted: Fri 01 Nov 2013, 23:11    Post subject:  

mikeb wrote:
Quote:
Are other pfix options working such as pfix=rdsh?

Didn't try that one, but pfix=ram works.

Quote:
Only other suggestion is to debug each step with strategic echos to see what variables are set to and if functions actually get called.

How is this done?
Back to top
View user's profile Send private message 
mikeb


Joined: 23 Nov 2006
Posts: 11083

PostPosted: Sat 02 Nov 2013, 07:22    Post subject:  

My usual strategy is to add things like
echo "you got here"
to see if a function is called and such as
echo $PDEV1
to check if a variable is being set correctly.

..so for example add echos to see if the fsck function is actually being called and what partition it is trying to check....
On that last subject its doing it on the partition NOT the save file itself.... just realised/remembered.... not sure if the later pups fsck the save file either....

As a side step ext3 is a better bet.

mike
Back to top
View user's profile Send private message 
Dewbie

Joined: 15 Apr 2010
Posts: 1779

PostPosted: Wed 06 Nov 2013, 03:29    Post subject:  

mikeb wrote:
Quote:
..so for example add echos to see if the fsck function is actually being called and what partition it is trying to check..

Tried this, but no luck.
(I might have done something wrong...)

Quote:
On that last subject its doing it on the partition NOT the save file itself.... just realised/remembered

I just heavily edited the first post to clarify this.
(attached rc.shutdown file, too...)

Quote:
not sure if the later pups fsck the save file either

Indeed, they do...starting somewhere in the 4-series.

When I did this, it was an easy copy-and-paste, because the 3.01 and 4.12 init scripts were so similar. Everything worked right out of the box.

On the other hand, 2-series is radically different.
Thanks, Mike. Smile
Back to top
View user's profile Send private message 
mikeb


Joined: 23 Nov 2006
Posts: 11083

PostPosted: Wed 06 Nov 2013, 08:08    Post subject:  

so you dropped in the initrd from 3 into 2.14x? or was it 4 to get an actual save file check? did I get that right.

Yes my init script is 22k and runs in 1.5 seconds on a pentium 3 including loading sfs to ram... thats the sort of radical I like Very Happy.
The main change was the sub folder searches and options... for me it made adding or changing any features a nightmare and intorduced quirks like trashing full installs but thats another story .

Well at least you got sorted...... I question a system that needs a fsck every boot though...you might have an ext3 save option now. I added reiserfs to mine...was nice and solid though ext3 behaved well when I used to use save files.

mike
Back to top
View user's profile Send private message 
Dewbie

Joined: 15 Apr 2010
Posts: 1779

PostPosted: Thu 07 Nov 2013, 01:27    Post subject:  

mikeb wrote:
Quote:
Well at least you got sorted.

With 2.14x, no. Confused
With 3.01, yes.
I copied the filesystem check script from the 4.12 init to the 3.01 init.
And that one worked right out of the box.

Quote:
so you dropped in the initrd from 3 into 2.14x?

Well, I tried, but it doesn't work.
It stalls after this part:
Code:
Loading kernel drivers to access disk drives.


Quote:
I question a system that needs a fsck every boot though

It doesn't need it.
I just choose this option to recover some of the lost save-file space.
Back to top
View user's profile Send private message 
mikeb


Joined: 23 Nov 2006
Posts: 11083

PostPosted: Thu 07 Nov 2013, 07:25    Post subject:  

Ah ok

well it would stall then as it would have the wrong kernel drivers versions at a quick guess. (you used retro 4?)

So not really solved for 2.14x.

You can't quite drop in the init script as there would be some other changes needed too. (only minor ones though but that would be going from 3 -> 2.... 3 is not a cpio initrd, 4 is iirc.)
I did the opposite...the init I developed in puppy 2 is used in 4 and lucid Smile ....

I just happened to be updating busybox and adding a couple of things to my initrds this week so its a bit of a topical subject for me.

Your original script hack looked like it would work actually...at least for the partition..the save would have only needed a bit extra.

So it recovers space.... forgot about that one.

you cannot escape from this thread....muh haw haw

mike
Back to top
View user's profile Send private message 
Dewbie

Joined: 15 Apr 2010
Posts: 1779

PostPosted: Thu 07 Nov 2013, 22:53    Post subject:  

mikeb wrote:
Quote:
(you used retro 4?)

I tried the 3.01 hack that I linked to above.

Quote:
So not really solved for 2.14x.

Nope.
Back to top
View user's profile Send private message 
mikeb


Joined: 23 Nov 2006
Posts: 11083

PostPosted: Fri 08 Nov 2013, 09:08    Post subject:  

Ok perhaps my question would be ... do you want to persue 2.14x.

I happen to be updating my initrds at the moment so a good time to test

mike
Back to top
View user's profile Send private message 
Dewbie

Joined: 15 Apr 2010
Posts: 1779

PostPosted: Fri 08 Nov 2013, 21:53    Post subject:  

If your init files need testing with 2.14x, I'd be glad to help. Smile
But I'm set up to run only frugal with WakePup2 (no GRUB).

(If anyone else is interested, ttuuxxx's instructions here explain how to open initrd.gz in 2-series.)
Back to top
View user's profile Send private message 
mikeb


Joined: 23 Nov 2006
Posts: 11083

PostPosted: Sat 09 Nov 2013, 07:33    Post subject:  

has ttuuxxx gone quiet? not seen anything from him for a while.

my init with 2.14x...well thats role reversal for you....also has companion rc.shutdown, and perhaps some changes in one or 2 other files eg rc.sysinit but they are more to do with the main system boot. What does 2.14x use for drive mounting...I made some icons like the 4+ series but not using the puppy frontend d and rox? He still uses the 2.6.18 kernel? I don't follow those long threads so have to pick your brains instead.

for the initrds I use a fiddled with xfilemount which gives a one click open and repack ability... nice and quick.

Well finished my updates... built a custom busybox to do as much as it can , made a custom mut for drive detection (and pci) and threw in fred ... a windows dos edit clone. So apart from some hid module handling needed in lucid 2.02, 2.12, 4.12 and lucid all run pretty much the same initrds....cheeky eh Very Happy well they sort of did anyway....just found a lot of redundant functions in lucids.

Wakepup just does the grub boogie without grub for flash stick If i remember...so you on a flash stick...you probably mentioned this before but there are so many users on here all with unique setups Smile

mike
Back to top
View user's profile Send private message 
Dewbie

Joined: 15 Apr 2010
Posts: 1779

PostPosted: Sun 10 Nov 2013, 02:27    Post subject:  

mikeb wrote:
Quote:
has ttuuxxx gone quiet? not seen anything from him for a while.

He was working on the next 2.14x release here, but that was almost a year ago.

Quote:
What does 2.14x use for drive mounting

HotPup and mut2.
(HotPup won't allow writing to NTFS partitions.)

Quote:
He still uses the 2.6.18 kernel?

2.6.18.1.

Quote:
Wakepup just does the grub boogie without grub for flash stick If i remember...so you on a flash stick.

I boot to IDE HD.
See the attached shell scripts?
You copy those from floppy to wherever you want to boot.
That's all.
(Frugal and FAT are required.)
WakePup2-floppy.png
 Description   WakePup2 files
 Filesize   21.63 KB
 Viewed   148 Time(s)

WakePup2-floppy.png

Back to top
View user's profile Send private message 
amigo

Joined: 02 Apr 2007
Posts: 2637

PostPosted: Sun 10 Nov 2013, 03:02    Post subject:  

Quote:
has ttuuxxx gone quiet?
His stated goal seemed to be achieving the longest thread here. Once he reached that goal he slipped away.
Back to top
View user's profile Send private message 
mikeb


Joined: 23 Nov 2006
Posts: 11083

PostPosted: Sun 10 Nov 2013, 09:53    Post subject:  

Actually the only change in my rc.shutdown that would need adjusting would be related to multiuser support. This affects the startup and shutdown sequence but you get nice a nice login screen and a true /home working profile for a full su life Very Happy ...optional of course.

Don't need testing as such as me wrappers have been used for 2-3 years ... just fancied playing with busybox and stuff out of general interest.. As to how 2.14x would benefit from them is another matter. The nearest I have is 2.12 though it uses aufs, has newer gtk2 and glibc and various fiddles like multiuser, NFS networking, ROX/xfce4 desktop and of course the alternative save options which were originally developed on there. But I did not go as far as ttuuxxx when it came to updates as. if you update to a newer version effectively why not use the newer version. I mentioned to him how fast 2.02 was but he went for 2.14 as a base as it was a better starting point for what he intended.

But enough history lesson Very Happy

mike
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 3 [31 Posts]   Goto page: 1, 2, 3 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Users ( For the regulars )
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0796s ][ Queries: 13 (0.0071s) ][ GZIP on ]