OESF Portables Forum

Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: gen2 on October 16, 2004, 01:19:43 pm

Title: dmesg questions (startup errors)
Post by: gen2 on October 16, 2004, 01:19:43 pm

Are these "problems"?

(dmesg)

cramfs: wrong magic
FAT: bogus logical sector size 381
Inode #3731 was a directory with children - removing those too...
Inode #4656 was a directory with children - removing those too...
jffs2: too few erase blocks (0)


running rc5 kathrin
with 121mb root

thanks!

Title: dmesg questions (startup errors)
Post by: xiaman on October 16, 2004, 06:26:36 pm

i see those same errors when i load.

Title: dmesg questions (startup errors)
Post by: rgrep on October 17, 2004, 04:07:38 am

I get these errors too, I think they are perfectly normal.

I love the new RC5 behaviour of showing the kernel messages on boot-up, but the first time I saw them it was pretty scary when "cramfs: wrong magic" appeared and the boot process paused for a few seconds.

Title: dmesg questions (startup errors)
Post by: ludovicus on October 31, 2004, 04:26:49 am

i got that message on my first boot with a sandisk card that was hosed.  but now that i have a panasonic sd card i have no indication of wrong magic.  We are talking about 1.1.0 right?  If this is old news please ignore
lu

Title: dmesg questions (startup errors)
Post by: Stubear on October 31, 2004, 08:22:59 am

Quote

Are these "problems"?

(dmesg)

cramfs: wrong magic
FAT: bogus logical sector size 381
Inode #3731 was a directory with children - removing those too...
Inode #4656 was a directory with children - removing those too...

Nope these are fine. The cramfs error is due to the automount deamon trying to guess what filesystem you have on your CF or SD card. They way it works is that it tries to mount the card with a cramfs, if that fails it tries another FS untill it gets one that mounts or gives up.

The FAT error message is one that you see alot with FAT12 and FAT16 filesystems under the linux vfat drivers - nothing to worry about.

The Inode children are Jffs2 error messages, this happens when you have deleted files from the main user area of the flash rom. Sometimes the full set of inodes don't get properly reset, but jffs2 is smart enough to work that out when the filesystem is mounted.

Quote

jffs2: too few erase blocks (0)

This is not one that I7ve seen before, and is probably a reminant of resizing your root. jffs2 filesystems are supposed to have an area set aside for erase blocks, seems that you don't have any - as I'm not really sure what an erase block is I can't say whether it is a problem or not

stu