Fwd: Mounting issue

Fwd: Mounting issue

[tomy]

Hello,
            Currently I am working on an embedded system which is having 
512 MB NAND flash . The embedded system is having u-boot, kernel, root 
filesystem (JFFS2) and a backup file system all reside in NAND flash. I 
am now facing a booting issue randomly  (/*reboot */command from linux 
console ) and the snapshot of the error is given below
/
//udevd-work[1092]: '/etc/udev/scripts/network.sh' unexpected exit with 
status 0x000b//
//udevd-work[1089]: '/etc/udev/scripts/network.sh' unexpected exit with 
status 0x000b//
//udevd-work[1032]: '/etc/udev/scripts/mount.sh' unexpected exit with 
status 0x000b//
//
//
//udevd-work[1112]: '/etc/udev/scripts/network.sh' unexpected exit with 
status 0x000b//
//
//
///etc/init.d/rc: line 45:  1760 Segmentation fault      "$@"//
///etc/rcS.d/S37populate-volatile.sh: line 194:  1773 Segmentation 
fault      sh /etc/volatile.cache//
//ln: /var/run/ld.so.cache: No such file or directory//
///etc/init.d/rc: line 45:  1780 Segmentation fault      "$@"//
///etc/rcS.d/S55bootmisc.sh: line 68:  1784 Segmentation fault      
/etc/init.d/hwclock.sh start//
//
//INIT: Entering runlevel: 5/

After this, the board is not pinging  and not able to login through 
console and the only solution to recover from this is power reboot. But 
in the next reboot everything will be ok.

The problem is happening randomly may be in 30 or 40 software reboots. I 
am not sure whether the issue is happening because of mounting problem, 
but still why this is not happening in every reboots.

So can you people help me to find out the root cause of this problem.

Regards,
Tomy





"Disclaimer: This message is being sent from Kalki Communication Technologies
Pvt Ltd (KALKITECH). and may contain information which is confidential or 

privileged. If you are not the intended recipient, please advise the sender
immediately by reply e-mail and delete this message and any attachments 

without retaining a copy. Any unauthorized use of the content of this message
can expose the responsible party to civil and/or criminal penalties, 

and may constitute a more serious offense. Further the company does not accept
liability for any errors, omissions, viruses or computer problems 

experienced as a result of this transmission. If you have received this
message in error, notice is hereby given that no representation, contract or 

other binding obligation shall be created by this e-mail." 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130608/93cdcc9d/attachment.html 

Fwd: Mounting issue

[Mandeep Sandhu]

On Jun 8, 2013 12:56 PM, "tomy" <tomy@kalkitech.in> wrote:
>
>
> Hello,
>            Currently I am working on an embedded system which is having
512 MB NAND flash . The embedded system is having u-boot, kernel, root
filesystem (JFFS2) and a backup file system all reside in NAND flash. I am
now facing a booting issue randomly  (reboot command from linux console )
and the snapshot of the error is given below
>

Does this happen only when u give the reboot command? Could it be possible
that some files on your flash partition have been corrupted?

What kernel and busybox version are you running?

What does this 0x000b exit status mean? Looks like your scripts may have
been killed by the reboot cmd I've given.

HTH,
-mandeep

> udevd-work[1092]: '/etc/udev/scripts/network.sh' unexpected exit with
status 0x000b
> udevd-work[1089]: '/etc/udev/scripts/network.sh' unexpected exit with
status 0x000b
> udevd-work[1032]: '/etc/udev/scripts/mount.sh' unexpected exit with
status 0x000b
>
>
> udevd-work[1112]: '/etc/udev/scripts/network.sh' unexpected exit with
status 0x000b
>
>
> /etc/init.d/rc: line 45:  1760 Segmentation fault      "$@"
> /etc/rcS.d/S37populate-volatile.sh: line 194:  1773 Segmentation
fault      sh /etc/volatile.cache
> ln: /var/run/ld.so.cache: No such file or directory
> /etc/init.d/rc: line 45:  1780 Segmentation fault      "$@"
> /etc/rcS.d/S55bootmisc.sh: line 68:  1784 Segmentation fault
/etc/init.d/hwclock.sh start
>
> INIT: Entering runlevel: 5
>
> After this, the board is not pinging  and not able to login through
console and the only solution to recover from this is power reboot. But in
the next reboot everything will be ok.
>
> The problem is happening randomly may be in 30 or 40 software reboots. I
am not sure whether the issue is happening because of mounting problem, but
still why this is not happening in every reboots.
>
> So can you people help me to find out the root cause of this problem.
>
> Regards,
> Tomy
>
>
>
>
>
>
>
> "Disclaimer: This message is being sent from Kalki Communication
Technologies
>
> Pvt Ltd (KALKITECH). and may contain information which is confidential or
>
>
>
> privileged. If you are not the intended recipient, please advise the
sender
>
> immediately by reply e-mail and delete this message and any attachments
>
>
>
> without retaining a copy. Any unauthorized use of the content of this
message
>
> can expose the responsible party to civil and/or criminal penalties,
>
>
>
> and may constitute a more serious offense. Further the company does not
accept
>
> liability for any errors, omissions, viruses or computer problems
>
>
>
> experienced as a result of this transmission. If you have received this
>
> message in error, notice is hereby given that no representation, contract
or
>
>
>
> other binding obligation shall be created by this e-mail."
>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130609/c36b103e/attachment-0001.html 

Fwd: Mounting issue

[tomy]

Hello,
           This is happening when we give reboot command from Linux 
console. But if the files got corrupted then every time this issue 
should occur  rt?. This is happening very randomly.
Every running scripts will be closed  as part of reboot

Regards,
Tomy
On 09-Jun-2013 12:16 PM, Mandeep Sandhu wrote:
>
>
> On Jun 8, 2013 12:56 PM, "tomy" <tomy@kalkitech.in 
> <mailto:tomy@kalkitech.in>> wrote:
> >
> >
> > Hello,
> >            Currently I am working on an embedded system which is 
> having 512 MB NAND flash . The embedded system is having u-boot, 
> kernel, root filesystem (JFFS2) and a backup file system all reside in 
> NAND flash. I am now facing a booting issue randomly  (reboot command 
> from linux console ) and the snapshot of the error is given below
> >
>
> Does this happen only when u give the reboot command? Could it be 
> possible that some files on your flash partition have been corrupted?
>
> What kernel and busybox version are you running?
>
> What does this 0x000b exit status mean? Looks like your scripts may 
> have been killed by the reboot cmd I've given.
>
> HTH,
> -mandeep
>
> > udevd-work[1092]: '/etc/udev/scripts/network.sh' unexpected exit 
> with status 0x000b
> > udevd-work[1089]: '/etc/udev/scripts/network.sh' unexpected exit 
> with status 0x000b
> > udevd-work[1032]: '/etc/udev/scripts/mount.sh' unexpected exit with 
> status 0x000b
> >
> >
> > udevd-work[1112]: '/etc/udev/scripts/network.sh' unexpected exit 
> with status 0x000b
> >
> >
> > /etc/init.d/rc: line 45:  1760 Segmentation fault      "$@"
> > /etc/rcS.d/S37populate-volatile.sh: line 194:  1773 Segmentation 
> fault      sh /etc/volatile.cache
> > ln: /var/run/ld.so.cache: No such file or directory
> > /etc/init.d/rc: line 45:  1780 Segmentation fault      "$@"
> > /etc/rcS.d/S55bootmisc.sh: line 68:  1784 Segmentation fault      
> /etc/init.d/hwclock.sh start
> >
> > INIT: Entering runlevel: 5
> >
> > After this, the board is not pinging  and not able to login through 
> console and the only solution to recover from this is power reboot. 
> But in the next reboot everything will be ok.
> >
> > The problem is happening randomly may be in 30 or 40 software 
> reboots. I am not sure whether the issue is happening because of 
> mounting problem, but still why this is not happening in every reboots.
> >
> > So can you people help me to find out the root cause of this problem.
> >
> > Regards,
> > Tomy
> >
> >
> >
> >
> >
> >
> >
> > "Disclaimer: This message is being sent from Kalki Communication 
> Technologies
> >
> > Pvt Ltd (KALKITECH). and may contain information which is 
> confidential or
> >
> >
> >
> > privileged. If you are not the intended recipient, please advise the 
> sender
> >
> > immediately by reply e-mail and delete this message and any attachments
> >
> >
> >
> > without retaining a copy. Any unauthorized use of the content of 
> this message
> >
> > can expose the responsible party to civil and/or criminal penalties,
> >
> >
> >
> > and may constitute a more serious offense. Further the company does 
> not accept
> >
> > liability for any errors, omissions, viruses or computer problems
> >
> >
> >
> > experienced as a result of this transmission. If you have received this
> >
> > message in error, notice is hereby given that no representation, 
> contract or
> >
> >
> >
> > other binding obligation shall be created by this e-mail."
> >
> >
> >
> > _______________________________________________
> > Kernelnewbies mailing list
> > Kernelnewbies at kernelnewbies.org <mailto:Kernelnewbies@kernelnewbies.org>
> > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> >
>


"Disclaimer: This message is being sent from Kalki Communication Technologies
Pvt Ltd (KALKITECH). and may contain information which is confidential or 

privileged. If you are not the intended recipient, please advise the sender
immediately by reply e-mail and delete this message and any attachments 

without retaining a copy. Any unauthorized use of the content of this message
can expose the responsible party to civil and/or criminal penalties, 

and may constitute a more serious offense. Further the company does not accept
liability for any errors, omissions, viruses or computer problems 

experienced as a result of this transmission. If you have received this
message in error, notice is hereby given that no representation, contract or 

other binding obligation shall be created by this e-mail." 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130609/6e69c120/attachment.html 

Fwd: Mounting issue

[Mandeep Sandhu]

On Sun, Jun 9, 2013 at 1:05 PM, tomy <tomy@kalkitech.in> wrote:

>  Hello,
>           This is happening when we give reboot command from Linux
> console. But if the files got corrupted then every time this issue should
> occur  rt?. This is happening very randomly.
>

Is your root FS mounted read-only? I'm not sure if this can happen, but it
could be that the cached version of these files (which reside in RAM) could
have got corrupted? I haven't played around with JFFS2 much (mostly used
YAFFS2) so maybe somebody experienced with JFFS2 can throw some light on
this.

Can you reformat your flash and put the root FS again on it? While
formatting see if bad blocks are reported.

-mandeep




> Every running scripts will be closed  as part of reboot
>
> Regards,
> Tomy
>
> On 09-Jun-2013 12:16 PM, Mandeep Sandhu wrote:
>
>
> On Jun 8, 2013 12:56 PM, "tomy" <tomy@kalkitech.in> wrote:
> >
> >
> > Hello,
> >            Currently I am working on an embedded system which is having
> 512 MB NAND flash . The embedded system is having u-boot, kernel, root
> filesystem (JFFS2) and a backup file system all reside in NAND flash. I am
> now facing a booting issue randomly  (reboot command from linux console )
> and the snapshot of the error is given below
> >
>
> Does this happen only when u give the reboot command? Could it be possible
> that some files on your flash partition have been corrupted?
>
> What kernel and busybox version are you running?
>
> What does this 0x000b exit status mean? Looks like your scripts may have
> been killed by the reboot cmd I've given.
>
> HTH,
> -mandeep
>
> > udevd-work[1092]: '/etc/udev/scripts/network.sh' unexpected exit with
> status 0x000b
> > udevd-work[1089]: '/etc/udev/scripts/network.sh' unexpected exit with
> status 0x000b
> > udevd-work[1032]: '/etc/udev/scripts/mount.sh' unexpected exit with
> status 0x000b
> >
> >
> > udevd-work[1112]: '/etc/udev/scripts/network.sh' unexpected exit with
> status 0x000b
> >
> >
> > /etc/init.d/rc: line 45:  1760 Segmentation fault      "$@"
> > /etc/rcS.d/S37populate-volatile.sh: line 194:  1773 Segmentation
> fault      sh /etc/volatile.cache
> > ln: /var/run/ld.so.cache: No such file or directory
> > /etc/init.d/rc: line 45:  1780 Segmentation fault      "$@"
> > /etc/rcS.d/S55bootmisc.sh: line 68:  1784 Segmentation fault
> /etc/init.d/hwclock.sh start
> >
> > INIT: Entering runlevel: 5
> >
> > After this, the board is not pinging  and not able to login through
> console and the only solution to recover from this is power reboot. But in
> the next reboot everything will be ok.
> >
> > The problem is happening randomly may be in 30 or 40 software reboots. I
> am not sure whether the issue is happening because of mounting problem, but
> still why this is not happening in every reboots.
> >
> > So can you people help me to find out the root cause of this problem.
> >
> > Regards,
> > Tomy
> >
> >
> >
> >
> >
> >
> >
> > "Disclaimer: This message is being sent from Kalki Communication
> Technologies
> >
> > Pvt Ltd (KALKITECH). and may contain information which is confidential
> or
> >
> >
> >
> > privileged. If you are not the intended recipient, please advise the
> sender
> >
> > immediately by reply e-mail and delete this message and any attachments
> >
> >
> >
> > without retaining a copy. Any unauthorized use of the content of this
> message
> >
> > can expose the responsible party to civil and/or criminal penalties,
> >
> >
> >
> > and may constitute a more serious offense. Further the company does not
> accept
> >
> > liability for any errors, omissions, viruses or computer problems
> >
> >
> >
> > experienced as a result of this transmission. If you have received this
> >
> > message in error, notice is hereby given that no representation,
> contract or
> >
> >
> >
> > other binding obligation shall be created by this e-mail."
> >
> >
> >
> > _______________________________________________
> > Kernelnewbies mailing list
> > Kernelnewbies at kernelnewbies.org
> > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> >
>
>
>
> "Disclaimer: This message is being sent from Kalki Communication Technologies
> Pvt Ltd (KALKITECH). and may contain information which is confidential or
>
> privileged. If you are not the intended recipient, please advise the sender
> immediately by reply e-mail and delete this message and any attachments
>
> without retaining a copy. Any unauthorized use of the content of this message
> can expose the responsible party to civil and/or criminal penalties,
>
> and may constitute a more serious offense. Further the company does not accept
> liability for any errors, omissions, viruses or computer problems
>
> experienced as a result of this transmission. If you have received this
> message in error, notice is hereby given that no representation, contract or
>
> other binding obligation shall be created by this e-mail."
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130610/0c2e90e1/attachment-0001.html