[beagleboard] Beagle giving error in rootfs

GoogleGroups
1

Hello

I am getting the following error when i boot up my beagle. It was running fine but all of a sudden it has started giving this error in its rootfs.
http://pastebin.com/ZtNG1VUD
Two of my beagles have come down with this error.
I am using the latest Ubuntu Karmic version given at
http://elinux.org/BeagleBoardUbuntu#Karmic_9.10

These boards were working fine till now. The problem is that i dont even know the ‘root password for maintenance’ is. I have tried temppwd and root but to no avail.
A speedy response would be very much helpful

Thanks

2

Hello

I am getting the following error when i boot up my beagle. It was running
fine but all of a sudden it has started giving this error in its rootfs.
http://pastebin.com/ZtNG1VUD
Two of my beagles have come down with this error.
I am using the latest Ubuntu Karmic version given at
BeagleBoardUbuntu - eLinux.org

Check that you enabed this workaround "/etc/e2fsck.conf"

http://elinux.org/BeagleBoardUbuntu#Karmic

These boards were working fine till now. The problem is that i dont even
know the 'root password for maintenance' is. I have tried temppwd and root
but to no avail.
A speedy response would be very much helpful

Umm, that's kinda rude... Remember we are all doing this on our "FREE" time...

Regards,

3

This usually happens on normal Linux systems when we make a cold shutdown, if you are running your system from a pen or a card this can be your problem since the file system doesn’t unmount and may create problems.

Best Regards

2010/5/6 Robert Nelson <robertcnelson@gmail.com>

4

The root password should be the default ubuntu karmic password or some other you defined in your system setup.

Umm, that’s kinda rude… Remember we are all doing this on our “FREE” time… …:::.> Agree, if everyone is polite it’s easier to get help.

Best Regards

2010/5/6 Joao Lopes <joaonl@gmail.com>

5

Except in ubuntu, there is no root user... So when this error occurs
you are kinda stuck..

For Karmic we have a workaround in "/etc/e2fsck.conf"

Lucid can use the same workaround, but when using an uInitrd we can
also pass "fixrtc" thru the bootargs and it'll adjust the time clock
based on the last file access..

For Maverick, the ubuntu dev's i've been working with are helping to
push the fix to upstream util-linux-ng or help get something different
for the fix..

Regards,

6

On regular ubuntu the root password is the same as the one you defined for your user at least my Ubuntu works like that

Maybe karmic is diferent…

Regards

2010/5/6 Robert Nelson <robertcnelson@gmail.com>

7

Umm, that’s kinda rude… Remember we are all doing this on our “FREE” time…

I sincerely apologize if i seemed rude there. It was totaly unintended. Thanks for the speedy reply though.
So the conclusion from what you guys have said is that when this particular error occurs in rootfs, there isnt much you can do about it?

8

Umm, that’s kinda rude… Remember we are all doing this on our “FREE” time…

I sincerely apologize if i seemed rude there. It was totaly unintended. Thanks for the speedy reply though.
So the conclusion from what you guys have said is that when this particular error occurs in rootfs, there isnt much you can do about it?

  • Show quoted text -
9

I can’t help you much more, i think the problem you are having is because we are dealing with an embedded system, mounting the filesystem as readonly should handle your problem, since the OS is running directly from the memory (similar to a live cd). The other way to solve your problem is to shutdown your system using “shutdown -h now”, the next time you boot you shouldn’t get that error because the filesystem is unmount as it should be. I found that something similar happens to memory cards in desktop ubuntu, if u remove the pen without unmounting it, the files usually get corrupted.

Please tell me one of that 2 solutions work or fit you

Best Regards

2010/5/6 cmpe reg <cmpereg2@gmail.com>