cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Contributor
Contributor
3,515 Views
Registered: ‎02-19-2009

ramdisk size issue

Hello, I'm using an old ramdisk image that was created sometime ago. When the linux boots I'm getting the following message. It looks like the ramdisk image is either small or big. I set the kernel parameter Default Ram Disk size = 65536 (whick is abt 64Mb). Can someone explain what does this error message in the bold mean. Should increase the Default Ram Disk size larger than 64Mb. Please help

 

 

 

RAMDISK: gzip image found at block 0
RAMDISK: incomplete write (21872 != 32768)
write error
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem) on device 1:0.
Freeing unused kernel memory: 164k init
attempt to access beyond end of device
ram0: rw=0, want=32776, limit=16384
EXT2-fs error (device ram0): ext2_get_inode: unable to read inode block - inode=
3265, block=16387
Warning: unable to open an initial console.
attempt to access beyond end of device
ram0: rw=0, want=16548, limit=16384
EXT2-fs error (device ram0): ext2_get_inode: unable to read inode block - inode=
1633, block=8273
Failed to execute /bin/bash.  Attempting defaults...
attempt to access beyond end of device
ram0: rw=0, want=32776, limit=16384
EXT2-fs error (device ram0): ext2_get_inode: unable to read inode block - inode=
3268, block=16387
attempt to access beyond end of device
ram0: rw=0, want=16548, limit=16384
EXT2-fs error (device ram0): ext2_get_inode: unable to read inode block - inode=
1633, block=8273
attempt to access beyond end of device
ram0: rw=0, want=16548, limit=16384
EXT2-fs error (device ram0): ext2_get_inode: unable to read inode block - inode=
1633, block=8273
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.
Call Trace:
[cf831f30] [c0005de8] show_stack+0x44/0x16c (unreliable)
[cf831f70] [c00345bc] panic+0x94/0x168
[cf831fc0] [c0001420] init_post+0xe8/0xf8
[cf831fd0] [c0318224] kernel_init+0x108/0x130
[cf831ff0] [c000e140] kernel_thread+0x4c/0x68

0 Kudos
1 Reply
Highlighted
Xilinx Employee
Xilinx Employee
3,513 Views
Registered: ‎09-10-2008

I've seen that before, but can't think what it is if not a size issue.

 

You can always go look in the source code as it may help. 

 

Sorry.

0 Kudos