Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info

READ-ONLY-MODE: PLEASE DO NOT POST NEW STUFF!
  New Forum: http://forum.puppylinux.com
 
 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 Thu 13 Aug 2020, 04:33
All times are UTC - 4
 Forum index » House Training » Users ( For the regulars )
initrd wrong path in xerrs.log when running filemnt [SOLVED]
Moderators: Flash, Ian, JohnMurga
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic
Page 1 of 2 [24 Posts]   Goto page: 1, 2 Next
Author Message
Argolance


Joined: 06 Jan 2008
Posts: 3822
Location: PORT-BRILLET (Mayenne - France)

PostPosted: Sat 30 May 2015, 08:50    Post subject:  initrd wrong path in xerrs.log when running filemnt [SOLVED]  

Bonjour,
Code:
stat: cannot stat `/initrd/initrd/mnt/dev_save/precisesave.4fs': No such file or directory

This is the line I (sometimes) get in my /tmp/xerrs.log file but I couldn't find the command or the script which is the cause of it (initrd directory is repeated twice making the path to be wrong)!
Has somebody any idea?

Thank you for your attention.

Cordialement.

_________________

Puppy Search

Last edited by Argolance on Wed 10 Jun 2015, 15:43; edited 2 times in total
Back to top
View user's profile Send private message Visit poster's website 
musher0

Joined: 04 Jan 2009
Posts: 15041
Location: Gatineau (Qc), Canada

PostPosted: Sat 30 May 2015, 11:35    Post subject: Re: initrd wrong path inside xerrs.log?  

Argolance wrote:
Bonjour,
Code:
stat: cannot stat `/initrd/initrd/mnt/dev_save/precisesave.4fs': No such file or directory

This is the line I (sometimes) get in my /tmp/xerrs.log file but I couldn't find the command or the script which is the cause of it (initrd directory is repeated twice making the path to be wrong)!
Has somebody any idea?

Thank you for your attention.

Cordialement.


Hello, Argolance.

I'm sure the community wants to help,
but please answer the usual questions! (You know the drill!)

You're not giving us much to go on in your post above.

What Puppy,
what machine,
how does this happen,
when,
how it impacts
...

Bye for now.

Christian

_________________
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Back to top
View user's profile Send private message 
Argolance


Joined: 06 Jan 2008
Posts: 3822
Location: PORT-BRILLET (Mayenne - France)

PostPosted: Sat 30 May 2015, 17:34    Post subject:  

Hello musher0,
Thanks for replying.
I really think I cannot do better Embarassed
    What Puppy: Puppy Precise 5.7.1
    what machine: Not sure it has something to do with?
    how does this happen: sometimes!
    when: I tried to reproduce but didn't succeed!
    how it impacts: Apparently none...

Cordialement.

_________________

Puppy Search
Back to top
View user's profile Send private message Visit poster's website 
musher0

Joined: 04 Jan 2009
Posts: 15041
Location: Gatineau (Qc), Canada

PostPosted: Tue 02 Jun 2015, 22:04    Post subject:  

Allô, Argolance,

I asked the questions because it's "initrd", the heart of the distro, the first
thing that loads in our Linux.

That's also why I asked about the type of machine: some computers have
"allergies" to some boot code.

But since it has no impact, I wouldn't worry too much about it. I'm no
great expert of initrd, but this "double initrd report" is probably a glitch in
how the xerrs.log perceives errors.

Unless of course you had an "accident" and really have created an
/initrd/initrd folder for some reason. Go check? Smile

(My cat does this to me all the time when I'm away too long! Laughing
Just joking!)

But again, seriously, if your Puppy works, I wouldn't worry too much
about it.

I hope this helps.

musher0

_________________
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Back to top
View user's profile Send private message 
mikeb


Joined: 23 Nov 2006
Posts: 11331

PostPosted: Wed 03 Jun 2015, 04:22    Post subject:  

initrd messages would not appear in xerrs.log

however its the message you get with the older initrd detection method which used ls and a pattern match...a not found file gives that message so its not an error as such since the file is probably not needed.

As to what script is doing this search who knows plus it probably uses distrospecs variables to choose the search parameter and unless you want to spend time doing a searchmonkey content search i would not worry about it.

Does seem curious though as to why its being done....its looking for a pupsave in the root of the save partition if that makes any sense to your setup...more likely its a woof leftover.

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


Joined: 06 Jan 2008
Posts: 3822
Location: PORT-BRILLET (Mayenne - France)

PostPosted: Wed 03 Jun 2015, 05:30    Post subject:  

Bonjour,
Quote:
But since it has no impact, I wouldn't worry too much about it.

Apparently...
Have my xerrs.log as clean as possible is deseased! Very Happy
Quote:
Does seem curious though as to why its being done....its looking for a pupsave in the root of the save partition if that makes any sense to your setup... more likely its a woof leftover.

I firstly just gave an example to simplify things (?), but it complains about all sfs files that are inside /initrd/mnt/dev_save.

Thank you a lot guys...

Cordialement.

_________________

Puppy Search
Back to top
View user's profile Send private message Visit poster's website 
mikeb


Joined: 23 Nov 2006
Posts: 11331

PostPosted: Wed 03 Jun 2015, 06:13    Post subject:  

I wonder...could it be something that sfs_load is doing? The usual system would not be looking there after initrd had finished.

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


Joined: 06 Jan 2008
Posts: 3822
Location: PORT-BRILLET (Mayenne - France)

PostPosted: Wed 03 Jun 2015, 07:05    Post subject:  

Bonjour,
Quote:
I wonder...could it be something that sfs_load is doing? The usual system would not be looking there after initrd had finished.

It is possible because I updated my sfs load to the latest release sfs_load 2.3.2. I suspected sfs_load indeed and had a look inside to see if any wrong initrd path in the code lines would be present. I found nothing but it doesn't mean that sfs_load is not the cause of this!

Cordialement.

_________________

Puppy Search
Back to top
View user's profile Send private message Visit poster's website 
mikeb


Joined: 23 Nov 2006
Posts: 11331

PostPosted: Thu 04 Jun 2015, 03:34    Post subject:  

well as mentioned its not an error as such just means a searched for file is missing.

could well be sfs_load...its long and complicated..the path is probably made from several variables so hard to find. Also you would not be able to change what it does anyway easily.

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


Joined: 06 Jan 2008
Posts: 3822
Location: PORT-BRILLET (Mayenne - France)

PostPosted: Thu 04 Jun 2015, 06:00    Post subject:  

Bonjour,
Quote:
could well be sfs_load
Yes it is: This error message occurs when installing a new sfs file...
Don't know if I should tell this on the sfs_load thread?
xerrs.log messages:
Code:
stat: cannot stat `/initrd/initrd/mnt/dev_save/tooppy_precisesave.4fs': No such file or directory
stat: cannot stat `/initrd/initrd/mnt/tmpfs/tooppy_precise_2.0.sfs': No such file or directory
stat: cannot stat `/initrd/initrd/mnt/dev_save/skype_apulse-4.3.0.37_all.sfs': No such file or directory
stat: cannot stat `/initrd/initrd/mnt/dev_save/chromium-28.0.1497_all.sfs': No such file or directory
stat: cannot stat `/initrd/initrd/mnt/dev_save/devx_precise_2.0.sfs': No such file or directory
stat: cannot stat `/initrd/initrd/mnt/dev_save/poeditor-1.5.4-1_all.sfs': No such file or directory
stat: cannot stat `/initrd/initrd/mnt/dev_save/libreoffice-4.4.1.2_en.sfs': No such file or directory
stat: cannot stat `/initrd/initrd/mnt/dev_save/libreoffice-language-pack-4.4.1.2_fr.sfs': No such file or directory
stat: cannot stat `/initrd/initrd/mnt/dev_save/gimp-2.8.2_all.sfs': No such file or directory
stat: cannot stat `/initrd/initrd/mnt/dev_save/jre-1.8.0-25_all.sfs': No such file or directory
stat: cannot stat `/initrd/initrd/mnt/dev_save/lazpaint-6.2_all.sfs': No such file or directory
stat: cannot stat `/initrd/initrd/mnt/dev_save/wine-1.7.34.sfs': No such file or directory
stat: cannot stat `/initrd/initrd/mnt/dev_save/vlc-2.0.5_all-dep_all.sfs': No such file or directory
stat: cannot stat `/initrd/initrd/mnt/dev_save/google-chrome-23.0.1271.97_all.sfs': No such file or directory

/tmp/sfs_load/loop_device_list contents:
Code:
/dev/loop4: 0 /initrd/mnt/dev_save/skype_apulse-4.3.0.37_all.sfs
/dev/loop5: 0 /initrd/mnt/dev_save/chromium-28.0.1497_all.sfs
/dev/loop6: 0 /initrd/mnt/dev_save/devx_precise_2.0.sfs
/dev/loop7: 0 /initrd/mnt/dev_save/poeditor-1.5.4-1_all.sfs
/dev/loop8: 0 /initrd/mnt/dev_save/libreoffice-4.4.1.2_en.sfs
/dev/loop9: 0 /initrd/mnt/dev_save/libreoffice-language-pack-4.4.1.2_fr.sfs
/dev/loop10: 0 /initrd/mnt/dev_save/gimp-2.8.2_all.sfs
/dev/loop11: 0 /initrd/mnt/dev_save/jre-1.8.0-25_all.sfs
/dev/loop12: 0 /initrd/mnt/dev_save/lazpaint-6.2_all.sfs
/dev/loop13: 0 /initrd/mnt/dev_save/wine-1.7.34.sfs
/dev/loop14: 0 /initrd/mnt/dev_save/vlc-2.0.5_all-dep_all.sfs
/dev/loop15: 0 /initrd/mnt/dev_save/google-chrome-23.0.1271.97_all.sfs
/dev/loop16: 0 /mnt/home/ytdlgui.sfs # < this is the latest installed sfs file


Cordialement.

_________________

Puppy Search
Back to top
View user's profile Send private message Visit poster's website 
musher0

Joined: 04 Jan 2009
Posts: 15041
Location: Gatineau (Qc), Canada

PostPosted: Thu 04 Jun 2015, 14:49    Post subject:  

Hi, Argolance.

Before blaming the sfs_load executable, I would use some "Cartesian
reasonable doubt" methodology: Smile

1) would you get such an xerrs.log report if you loaded the same
"squash-file-system" files (aka sfs files) in another Puppy?

2) can you check is those sfs files are properly formed, in and of
themselves? I mean: is their structure correct, as sfs files?

~~~~~~~~~

Another thought after reading your quote above: if one gets a stat
error, it means that the file is corrupted in some way. The usual
(non-)behavior is that one cannot access the file.

However, you mention that the error clearly has NO impact on your
Puppy. Very strange indeed.

Bye for now.

musher0

_________________
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 15041
Location: Gatineau (Qc), Canada

PostPosted: Thu 04 Jun 2015, 15:02    Post subject:  

Are you "root" or "spot"? According to this fellow, it does
make a difference, being "root" eliminates the "stat" error.

It's not exactly the same problem, but the question is still
worth asking, no?

_________________
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Back to top
View user's profile Send private message 
mikeb


Joined: 23 Nov 2006
Posts: 11331

PostPosted: Fri 05 Jun 2015, 04:51    Post subject:  

run sfs_load and it generates a path starting with '/initrd/initrd/'

seems pretty definite as to the source...yes I would let them know on the sfs_load thread...after all in some circumstances the results of search it is doing MAY be needed. (in lighthousepup it failed to load sfs to ram for example..might be related)

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


Joined: 06 Jan 2008
Posts: 3822
Location: PORT-BRILLET (Mayenne - France)

PostPosted: Fri 05 Jun 2015, 05:47    Post subject:  

Bonjour,
musher0 wrote:
Before blaming the sfs_load executable, I would use some "Cartesian
reasonable doubt" methodology: Smile
I do not "blame", just have some reasons for suspecting it (sfs_load 2.3.2). Wink
Quote:
1) would you get such an xerrs.log report if you loaded the same
"squash-file-system" files (aka sfs files) in another Puppy?

This occurs while running puppy mode 5 (usb hdd), not running puppy mode 12, both as root.
Quote:
2) can you check is those sfs files are properly formed, in and of
themselves? I mean: is their structure correct, as sfs files?

The sfs files are correctly loaded/mounted and programs work normally in both cases.
mikeb wrote:
run sfs_load and it generates a path starting with '/initrd/initrd/'
seems pretty definite as to the source...yes I would let them know on the sfs_load thread...after all in some circumstances the results of search it is doing MAY be needed. (in lighthousepup it failed to load sfs to ram for example..might be related)

So I will report this to the sfs_load thread.
_____________________________________________________________
EDIT:

Quote:
So I will report this to the sfs_load thread.

Done!

Cordialement.

_________________

Puppy Search
Back to top
View user's profile Send private message Visit poster's website 
mavrothal


Joined: 24 Aug 2009
Posts: 3108

PostPosted: Fri 05 Jun 2015, 06:33    Post subject:  

Argolance wrote:

This occurs while running puppy mode 5 (usb hdd), not running puppy mode 12, both as root.

Tried sfs_load-2.3.2 on Tahr 6.0.2 pupmode=5
No problem with sfs loading, SFS is loaded on /initrd/pup_ro4, no error message about /initrd/initrd in /tmp/xerrs.log Confused
AAMOF, sfs_load script does not have any "stat" call to generate the messages that you see in xerrs.log
Are there any other changes in the puppy that you are using?
Did you install sfs_load-2.3 and verified that these errors are not generated?
Since SFS loading works as expected why do you think that the errors are for sfs_load?

Please described your setup/puppy etc as detailed as possible. Is this on a remastered puppy? What other changes are there?

_________________
== Here is how to solve your Linux problems fast ==
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 2 [24 Posts]   Goto page: 1, 2 Next
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. 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.0897s ][ Queries: 12 (0.0331s) ][ GZIP on ]