From: Robert Larsen <robert@the-playground.dk>
To: buildroot@busybox.net
Subject: [Buildroot] Filesystem being corrupted
Date: Thu, 03 Jul 2014 12:40:27 +0200 [thread overview]
Message-ID: <53B5331B.9030703@the-playground.dk> (raw)
Hi list
I am having a problem with my root filesystem being corrupted.
When I halt a newly built system (simply log in and execute 'halt') get
this message:
---------------------------------------------------------------
# halt
The system is going down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to all processes
Requesting system halt
Flash device refused suspend due to active operation (state 20)
Flash device refused suspend due to active operation (state 20)
reboot: System halted
---------------------------------------------------------------
Then when I restart it I get:
---------------------------------------------------------------
....
Starting network...
EXT2-fs (mmcblk0): error: ext2_lookup: deleted inode referenced: 625
EXT2-fs (mmcblk0): error: remounting filesystem read-only
Generating RSA Key...
No user exists for uid 0
EXT2-fs (mmcblk0): error: ext2_lookup: deleted inode referenced: 627
EXT2-fs (mmcblk0): error: remounting filesystem read-only
Generating DSA Key...
No user exists for uid 0
EXT2-fs (mmcblk0): error: ext2_lookup: deleted inode referenced: 629
EXT2-fs (mmcblk0): error: remounting filesystem read-only
Generating ECDSA Key...
No user exists for uid 0
EXT2-fs (mmcblk0): error: ext2_lookup: deleted inode referenced: 631
EXT2-fs (mmcblk0): error: remounting filesystem read-only
Generating ed25519 Key...
No user exists for uid 0
Starting sshd: Privilege separation user sshd does not exist
OK
ARM Testing System
arm-testing login:
---------------------------------------------------------------
I start it with this command:
sudo qemu-system-arm -M vexpress-a9 -m 512 -kernel zImage -sd
rootfs.ext2 -append "root=/dev/mmcblk0 rw physmap.enabled=0
console=ttyAMA0" -net tap -net nic -net
user,hostfwd=tcp:0.0.0.0:2222-:22 -nographic
Any ideas as to what has happened and how to fix it?
You can view my buildroot config file here:
http://www.the-playground.dk/buildroot_config.txt
Robert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 246 bytes
Desc: OpenPGP digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140703/d561c064/attachment.asc>
next reply other threads:[~2014-07-03 10:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 10:40 Robert Larsen [this message]
2014-07-03 12:30 ` [Buildroot] Filesystem being corrupted Gustavo Zacarias
2014-07-03 13:05 ` Robert Larsen
2014-07-03 14:25 ` Robert Larsen
2014-07-03 18:22 ` Thomas Petazzoni
2014-07-04 9:05 ` Robert Larsen
2014-07-04 21:24 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53B5331B.9030703@the-playground.dk \
--to=robert@the-playground.dk \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox