[Buildroot] Filesystem being corrupted

[Buildroot] Filesystem being corrupted

[Robert Larsen]

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>

[Buildroot] Filesystem being corrupted

[Gustavo Zacarias]

On 07/03/2014 07:40 AM, Robert Larsen wrote:

> 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

Hi.
The corruption happens with the vexpress target, but for instance it
doesn't happen with versatile (it was easily reproduced with vexpress,
not a single failure with multiple boots on versatile).
I suspect it's related to some bug or missing feature in Qemu's mmc
hardware emulation for the vexpress or some kernel bug.
Any reason in particular to stick with vexpress? versatile can be made
to use a better processor than arm926 if that's it.
Regards.

[Buildroot] Filesystem being corrupted

[Robert Larsen]

On 07/03/2014 02:30 PM, Gustavo Zacarias wrote:
> Any reason in particular to stick with vexpress?
Not really, that was what I was used to. I'll try versatile.

Thanks for the quick answer.

-------------- 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/023c3f52/attachment.asc>

[Buildroot] Filesystem being corrupted

[Robert Larsen]

On 07/03/2014 03:05 PM, Robert Larsen wrote:
> On 07/03/2014 02:30 PM, Gustavo Zacarias wrote:
>> Any reason in particular to stick with vexpress?
> Not really, that was what I was used to. I'll try versatile.
>
Hmm, building with versatile defconfig hangs qemu. I tried both '-M
versatilepb' and '-M versatileab'
Both hang after this message:

Uncompressing Linux... done, booting the kernel.

-------------- 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/7cb760fc/attachment.asc>

[Buildroot] Filesystem being corrupted

[Thomas Petazzoni]

Dear Robert Larsen,

On Thu, 03 Jul 2014 16:25:06 +0200, Robert Larsen wrote:
> On 07/03/2014 03:05 PM, Robert Larsen wrote:
> > On 07/03/2014 02:30 PM, Gustavo Zacarias wrote:
> >> Any reason in particular to stick with vexpress?
> > Not really, that was what I was used to. I'll try versatile.
> >
> Hmm, building with versatile defconfig hangs qemu. I tried both '-M
> versatilepb' and '-M versatileab'
> Both hang after this message:
> 
> Uncompressing Linux... done, booting the kernel.
> 

Most likely incorrect kernel configuration.

You should start with the qemu_arm_versatile_defconfig available in
Buildroot, which uses a correct kernel configuration.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Filesystem being corrupted

[Robert Larsen]

On 07/03/2014 08:22 PM, Thomas Petazzoni wrote:
> You should start with the qemu_arm_versatile_defconfig available in
> Buildroot, which uses a correct kernel configuration.
That was the one I used, and I didn't change a thing in the kernel
config :-(

The only thing changed between my vexpress and new build is this:

322c322
< BR2_LINUX_KERNEL_DEFCONFIG="vexpress"
---
> BR2_LINUX_KERNEL_DEFCONFIG="versatile"

-------------- 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/20140704/e2146e55/attachment.asc>

[Buildroot] Filesystem being corrupted

[Peter Korsgaard]

>>>>> "Robert" == Robert Larsen <robert@the-playground.dk> writes:

 > On 07/03/2014 08:22 PM, Thomas Petazzoni wrote:
 >> You should start with the qemu_arm_versatile_defconfig available in
 >> Buildroot, which uses a correct kernel configuration.
 > That was the one I used, and I didn't change a thing in the kernel
 > config :-(

 > The only thing changed between my vexpress and new build is this:

 > 322c322
 > < BR2_LINUX_KERNEL_DEFCONFIG="vexpress"
 > ---
 >> BR2_LINUX_KERNEL_DEFCONFIG="versatile"

But are you using the qemu_arm_versatile *BUILDROOT* defconfig? That one
E.G. uses a custom Linux defconfig
(board/qemu/arm-versatile/linux-3.13.config)

-- 
Bye, Peter Korsgaard