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 Fri 25 Jul 2014, 14:26
All times are UTC - 4
 Forum index » House Training » HOWTO ( Solutions )
Make Puppy recover automatically from improper shutdowns
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 3 of 6 [80 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6 Next
Author Message
SilverPuppy


Joined: 28 May 2009
Posts: 143

PostPosted: Mon 07 Dec 2009, 10:40    Post subject: You pm-ed me.....  

rameshiyer wrote:
I am using 4.3.1 full installation with Ext4 ( dual boot). I am not able to boot after power loss or improper shutdown. Kindly provide solution or pet package to install so that I can reboot my puppy with reinstall the same. I have read your postings int his regard, however, I am not able to follow the postings. Kindly help me in this regard.


Well, if you can't boot, then your first course of action is to boot from a LiveCD and run fsck on the partition that Puppy lives on (probably sda2 in your case, but do verify this)

Once you get things running again, check out my original post for new files I just made yesterday for 4.3.1----they work the same as the ones for 4.1.2, (drop-in to /etc/rc.d, then change the line in rc.sysinit that says "fsck /dev/sda1" to reflect whatever the partition Puppy lives on is called, then reboot) with one additional caveat: the TIME ZONE MUST BE SET TO GREENWICH, or fsck reports that the superblock last write time is in the future, and won't run automatically (might only apply for the first few hours after installation, come to think of it.)

Anybody want to comment on the superblock/Greenwich issue? Thinking about it now, I guess it shouldn't matter in general, only for the first few hours after installation, as IIRC the superblock is not written to otherwise.....or am I mistaken?
Back to top
View user's profile Send private message 
mikeb


Joined: 23 Nov 2006
Posts: 8028

PostPosted: Mon 07 Dec 2009, 11:41    Post subject:  

I have yet to achieve a clean shutdown with frugal and the clean up script is in initrd.gz anyway. Inability to unmount from the union is the cause although slax manages this Very Happy .

As I mentioned before puppy 4 unreliability is mainly due to useng ext2 for the pup_save...I don't get problems like this with puppy 2 which uses ext3... a tweak of the init script needed for that change . Alternatively add pfix=fsck to the kernel boot line.
If unionfs is used whiteout files do accumulate and eventually cause problems...aufs does not seem to suffer this.

Full installs are not supported as its not considered the approved way of using puppy so its up to us to provide the fixes.

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


Joined: 28 May 2009
Posts: 143

PostPosted: Mon 07 Dec 2009, 12:24    Post subject: Unapproved and improving it  

Well, I aim to make that "unapproved" use much more usable! Very Happy

As for unmounting from the union......the Southern States managed to SECEDE from the Union.....so how hard can a simple unmount be? Laughing

Why on earth does the Universal Installer make it so easy then, if it's not the "approved" way? Perhaps because Puppy is OSS, and doesn't need anybody's approval? Razz
Back to top
View user's profile Send private message 
enhu


Joined: 26 May 2009
Posts: 301

PostPosted: Wed 06 Jan 2010, 14:55    Post subject:  

what shall i do with this rc.sysinit&shutdown-4.1.2-4.3.1.zip?
i download it, unzip it and saw some files.

havent understand puppy yet until now.

should i put it inside rc.d?
Back to top
View user's profile Send private message Visit poster's website 
G0XAN

Joined: 08 May 2009
Posts: 31
Location: Brighton, UK

PostPosted: Wed 06 Jan 2010, 17:22    Post subject:  

enhu

First, go to /etc/rc.d and rename the existing rc.sysinit and rc.shutdown or move them into another directory so they are kept safe.

Next you have to choose which version of the files you need - 4.1.2 or 4.3.1
Extract the files you need and rename them to rc.sysinit and rc.shutdown (remove the version numbers)
Now copy (or move) the new rc.sysinit and rc.shutdown into /etc/rc.d
Finally, change the permissions on the files so they can execute
Code:

chmod 755 rc.sysinit
chmod 755 rc.shutdown

And that's it, you should be good to go.

Silverpuppy, can I suggest you add the instruction on where to put the files into the first post with the files, or maybe a brief readme in the zip file.
Excellent work BTW, just what I was looking for. Smile Thanks!

(Edit: Added in the chmod instruction, as I fell foul of it myself!)

_________________
Gary
Back to top
View user's profile Send private message 
enhu


Joined: 26 May 2009
Posts: 301

PostPosted: Thu 07 Jan 2010, 06:19    Post subject: Re: You pm-ed me.....  

SilverPuppy wrote:
rameshiyer wrote:
I am using 4.3.1 full installation with Ext4 ( dual boot). I am not able to boot after power loss or improper shutdown. Kindly provide solution or pet package to install so that I can reboot my puppy with reinstall the same. I have read your postings int his regard, however, I am not able to follow the postings. Kindly help me in this regard.


Well, if you can't boot, then your first course of action is to boot from a LiveCD and run fsck on the partition that Puppy lives on (probably sda2 in your case, but do verify this)

Once you get things running again, check out my original post for new files I just made yesterday for 4.3.1----they work the same as the ones for 4.1.2, (drop-in to /etc/rc.d, then change the line in rc.sysinit that says "fsck /dev/sda1" to reflect whatever the partition Puppy lives on is called, then reboot) with one additional caveat: the TIME ZONE MUST BE SET TO GREENWICH, or fsck reports that the superblock last write time is in the future, and won't run automatically (might only apply for the first few hours after installation, come to think of it.)

Anybody want to comment on the superblock/Greenwich issue? Thinking about it now, I guess it shouldn't matter in general, only for the first few hours after installation, as IIRC the superblock is not written to otherwise.....or am I mistaken?


it didn't work. even after installing it back and setting it to greenwich.
Back to top
View user's profile Send private message Visit poster's website 
sarum

Joined: 07 Jul 2007
Posts: 59
Location: The Thames, New Zealand

PostPosted: Sat 16 Jan 2010, 17:21    Post subject:  

Goxan wrote: chmod 755 re.sysinit
chmod 755 rc.shutdown
I get the answer 'no such file or directory' in rxvt.

I've done all the other stuff. Renaming -sysinit & -shutdown. Extracted both new downloads; in my case 4.3.1 and renamed them(ie. without the 4.3.1 number). Can anyone see where I've gone wrong - please.
The new files are in /etc/rc.d.
Thanks for any help...........sarum
Back to top
View user's profile Send private message 
sarum

Joined: 07 Jul 2007
Posts: 59
Location: The Thames, New Zealand

PostPosted: Sat 16 Jan 2010, 17:33    Post subject:  

I forgot to:- cd /etc/rc.d. then I did a 'chmod 755' and it worked, or at least it seems to have done. I'd like to try it out now but I'm worried about the GMT thing. I see that SilverPuppy says it'll be OK after a few hours. So I'll give it a go this evening.
Thanks to all who do these very useful things........sarum.
Back to top
View user's profile Send private message 
sarum

Joined: 07 Jul 2007
Posts: 59
Location: The Thames, New Zealand

PostPosted: Sun 17 Jan 2010, 02:16    Post subject:  

.......................and it worked. Thanks again.
A big part of a good distro: is it's forum.
Back to top
View user's profile Send private message 
SilverPuppy


Joined: 28 May 2009
Posts: 143

PostPosted: Thu 28 Jan 2010, 04:53    Post subject: And then again....  

A few thoughts....have been busy.....

1. As far as I know, the only way I know of FOR SURE to make the fsck work properly is to set the timezone to GMT. I theorized that it might work hours later in GMT-x timezones, but that was only a theory, and upon further digging into superblock theory, I am in greater doubt than before as to whether there is any other way to do it other than to set the clock to GMT. Running in GMT causes no problems that I can see, and in fact, causes no changes that I can perceive. The clock is still accurate in the tray.

2. All functionality except fsck will work fine no matter when it is used or what timezone is set. You won't mess up your system by not setting to GMT or forgetting to wait or whatever. The worst thing you can get is a fsck "I can't run automatically" message and no fsck on reboot. You won't get a non-booting system or anything like that.
Back to top
View user's profile Send private message 
gcmartin

Joined: 14 Oct 2005
Posts: 4088
Location: Earth

PostPosted: Sun 31 Jan 2010, 18:48    Post subject: Make Puppy recover automatically from improper shutdowns  

@SilverPuppy

This Looks a very useful and thought thru effort.

My question is what are the implication of my using Puppy on a system that has multiple partitions on it....particularly since much of the data that use is on Linux and Microsoft partitions?

Is your process ONLY applicable to the "Puppy" partition or is it applicable to all mounted partitions that were in the running when power was lost?

Thanks in advance

_________________
Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Engine or use DogPile
Back to top
View user's profile Send private message 
SilverPuppy


Joined: 28 May 2009
Posts: 143

PostPosted: Sun 31 Jan 2010, 23:55    Post subject: Re: You pm-ed me.....  

enhu wrote:
SilverPuppy wrote:
rameshiyer wrote:
I am using 4.3.1 full installation with Ext4 ( dual boot). I am not able to boot after power loss or improper shutdown. Kindly provide solution or pet package to install so that I can reboot my puppy with reinstall the same. I have read your postings int his regard, however, I am not able to follow the postings. Kindly help me in this regard.


Well, if you can't boot, then your first course of action is to boot from a LiveCD and run fsck on the partition that Puppy lives on (probably sda2 in your case, but do verify this)

Once you get things running again, check out my original post for new files I just made yesterday for 4.3.1----they work the same as the ones for 4.1.2, (drop-in to /etc/rc.d, then change the line in rc.sysinit that says "fsck /dev/sda1" to reflect whatever the partition Puppy lives on is called, then reboot) with one additional caveat: the TIME ZONE MUST BE SET TO GREENWICH, or fsck reports that the superblock last write time is in the future, and won't run automatically (might only apply for the first few hours after installation, come to think of it.)

Anybody want to comment on the superblock/Greenwich issue? Thinking about it now, I guess it shouldn't matter in general, only for the first few hours after installation, as IIRC the superblock is not written to otherwise.....or am I mistaken?


it didn't work. even after installing it back and setting it to greenwich.


2 things.

1. I was mistaken on the way the superblock works, and the time will have to be set to GMT until one of us figures out a workaround.

2. You have to change the e2fsck line in the rc.sysinit file to have the correct name of the Puppy partition. Otherwise it won't work. Also, if you are not using EXT2 or EXT3, substitute the appropriate command for e2fsck. A lot of people have forgotten this, it seems.
Back to top
View user's profile Send private message 
SilverPuppy


Joined: 28 May 2009
Posts: 143

PostPosted: Mon 01 Feb 2010, 00:06    Post subject: Re: Make Puppy recover automatically from improper shutdowns  

gcmartin wrote:
@SilverPuppy

This Looks a very useful and thought thru effort.

My question is what are the implication of my using Puppy on a system that has multiple partitions on it....particularly since much of the data that use is on Linux and Microsoft partitions?

Is your process ONLY applicable to the "Puppy" partition or is it applicable to all mounted partitions that were in the running when power was lost?

Thanks in advance


By default, the only partition that would be checked is the Puppy partition, but the answer to that question depends a bit on what software is included on your system.

I am pretty certain that by default, Puppy does not have a utility installed capable of checking/repairing NTFS filesystems, and I'm not totally sure that such a utility exists, as NTFS is proprietary.

That said, it is possible to add lines to the rc.sysinit file to check other partitions at the same point in the process. Just add them immediately under the e2fsck line that checks the Puppy partition.

I am pretty sure that you can check FAT32 partitions from within Puppy, and it would just be a matter of inserting the correct command line after the e2fsck line. I don't recall offhand what that is.

If you can find a command-line Linux utility to check NTFS partitions, it should be possible to achieve the functionality you seek.

Hope that helps you.
Back to top
View user's profile Send private message 
sindi

Joined: 16 Aug 2009
Posts: 389

PostPosted: Tue 02 Feb 2010, 16:01    Post subject: Puppy 4.3.1 frugal ext2 ROX-filer error on improper shutdown
Subject description: Most icons lost, Error messages
 

HP Pavilion 84802, circa 1999, 450MHz, 256MB RAM. HSF1 modem
(combo with riptide sound). Onboard video okay with Xorg
(and I think Xvesa - unload ctmouse first).

puppy 4.3.1 oldest retro kernel, files in /dev/hda2
ext2. Puppy is loaded using loadlin from /dev/hda1 (FAT32,
used for 100 old DOS games, boot to DOS then choose games
or Puppy Linux).

loadlin vmlinuz initrd=initrd.gz ro nosmp

On first use, the 11-year-old user turned it off without
shutting down.
They returned it (via bus - huge computer).
During boot, pages of udevd-event error messages.
After booting, dialog box with error (may not be exact).

Error :
root/Choices/ROX-filer?
Pinboard PuppyPin:
Input/Output error

None of this showed up in a forum search.
Home icon. No trash or lock or other icons. Menu is
there. The owner wants the icons back.

fd0 hda1 hda2 piled on top of each other in lower left,
refuse to be separated.

e2fsck did not help (from Basiclinux 3.5 floppy disk).

Works if booted pfix=ram (ignore save file).
Since this computer is only for internet access and school
work, one possible fix is a small DOS batch file called
'fixit' which would recopy both the .sfs and the save
file from a backup location, on top of originals in FAT2
partition. Since e2fsck did not fix the
problem, would ext3 help anyinstead of the above fix?

Is there some way to fix the ROXfiler problem rather than
delete the save file? They can wait a few days for a
better solution.
Back to top
View user's profile Send private message 
sindi

Joined: 16 Aug 2009
Posts: 389

PostPosted: Tue 02 Feb 2010, 17:26    Post subject: Puppy 4.3.1 frugal lost icons on improper shutdown
Subject description: e2fsck pupsave.2fs fixes it - where to run it during startup
 

I was able to mount -o loop pupsave.2fs. It is ext2.
e2fsck -y /initrd/mnt/dev_save/puppy431/pupsave.2fs fixed the problem.

Should I also e2fsck /dev/hda2 at startup? That was apparently required for the full install. In my case Puppy boots to X (Xvesa) but most of the icons are missing (see previous message).

How do I run it at startup? I put it in rc.sysinit before the first occurrence of pinboard (since I got a pinboard error otherwise). How do I know
if it is actually running? It was not in dmesg, and there is still the complaint about needing to run e2fsck.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 3 of 6 [80 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » HOWTO ( Solutions )
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.1047s ][ Queries: 12 (0.0048s) ][ GZIP on ]