ext2-fs ram0 error ext2_get_inode unable to read inode block Elwin Illinois

Address 363 S Main St, Decatur, IL 62523
Phone (217) 422-1053
Website Link
Hours

ext2-fs ram0 error ext2_get_inode unable to read inode block Elwin, Illinois

Does anybody know y? What does ext3 give me other than journaling and what exactly does journaling give me? 0 LVL 34 Overall: Level 34 Linux 28 Message Active today Expert Comment by:Duncan Roe2012-09-02 Thots? 0 LVL 34 Overall: Level 34 Linux 28 Message Active today Accepted Solution by:Duncan Roe2012-09-04 Sounds like your old system only has USB-1. This is always distribution dependent and with newest distro, the number of modules increases, and the new way that mindi has to deal with udev and modules makes the ramdisk bigger.

Do you want me to test 32-bit ? The next reboot completed the upgrade process). If > not, I could remove the nfsmount info from the append line but if my server > changes its IP ? So I took the existing command line: Kernel command line: ramdisk_size=65536 root=/dev/ram rw mtdparts=fc000000.nor_flash:2M(linux),20M(ramdisk),4M(jffs2),38272k(user),256k(env),384k(uboot) ip=10.2.3.28:10.1.0.65:10.0.0.1::kilauea:eth0:off panic=1 console=ttyS0,115200 And modified it like below (4M -> 8M, 38272k->34176k).

However, I cannot write any actual data to these drives because I get lots of errors like: [16697.792671] EXT2-fs (sdb1): error: read_inode_bitmap: Cannot read inode bitmap - block group = 5331, One last question: your comment about uisng "tune2fs to upgrade 3 ext2 mounts to ext3 ... Reply Cancel Cancel Reply Suggest as Answer Use rich formatting Intellectual 1505 points Tom Rini Oct 27, 2011 3:47 PM In reply to Thanh Tran: Well, did you follow all of Now I want to use the latest stable version of Xilinx Linux for ZedBoard.

So I modified my PXE append line this way : append initrd=restore/master3dsy/RHEL/5/x86_64/20080528/initrd.img load_ramdisk=1 *ramdisk_size=131072 ramdisk_blocksize=1024* rw root=/dev/ram iso_mode devfs=nomount pxe prefix=mondorescue ipconf=eth0:128.3.11.151:255 .255.0.0:128.3.255.255:128.3.1.2 nfsmount=10.242.10.74:/home/backup I needed to change also the size I hinestly can't test everything. If so, how can I fix this? Does the new one?

Message 1 of 5 (6,452 Views) Reply 0 Kudos Accepted Solutions mobyx Visitor Posts: 5 Registered: ‎03-13-2013 Re: Need bigger ramdisk (32MB) on ZC702 Options Mark as New Bookmark Subscribe Subscribe Please refer to our Privacy Policy or Contact Us for more details You seem to have CSS turned off. attempt to access beyond end of device ram0: rw=0, want=98312, limit=70000 EXT2-fs error (device ram0): ext2_get_inode: unable to read inode block - inode=12289, block=49155 attempt to access beyond end of device Where can I find a per-built RAMDISK?

So I created a 32MB ramdisk, compressed it and used mkimage to generate uramdisk.image.gz. I got no errors. I can get the image into RAM just fine. Right now, one of these USB drives is ext2 and one is ext3.

Thanks for your tests and time, Bruno. -- Linux Profession Lead EMEA / Open Source Evangelist \ HP C&I EMEA IET http://www.mondorescue.org / HP/Intel Solution Center \ http://hpintelco.net Des infos sur Thanks. Please click the Verify Answer button on this post if it answers your question. Password Linux - General This Linux forum is for general Linux questions and discussion.

ugenn View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by ugenn 01-16-2006, 11:35 AM #3 shinobi59 Member Registered: Oct 2004 Posts: 53 Is the ram disk still too small?? attempt to access beyond end of device ram0: rw=0, want=46852, limit=40960 Buffer I/O error on device ram0, logical block 23425 attempt to access beyond end of device ram0: rw=0, want=46852, limit=40960 Is it possible that's all it was or am I just getting lucky today?

Tools Insider University Program Groups Corporate Citizenship TI University Program Russian E2E (сообщество E2E) Japanese E2E (日本語コミュニティ) Learn E2E Launch Your Design Motor Drive & Control Videos More Cancel Linux Linux Freeing unused kernel memory: 140k freed attempt to access beyond end of device ram0: rw=0, want=98312, limit=40960 EXT2-fs error (device ram0): ext2_get_inode: unable to read inode block - inode=12289, block=49155 Warning: Are you new to LinuxQuestions.org? This was the error prior to setting the parameter: RAMDISK: Compressed image found at block 0 RAMDISK: incomplete write (-28 != 32768) 16777216 VFS: Mounted root (ext2 filesystem) readonly.

I get a kernel panic at boot. After reinstalling a newer Slackware release is when I ran into this problem with not being able to write to the USB drive. If I could easily move the ext2 to ext3 w/o losing all the data, I'd give that a shot. Kernel boot logs below.

Sorry to hear ext3 held you up - did you actually do a re-format? I'd go for a USB2 plug-in card or replacement 2nd-hand system, whatever is cheaper. 0 LVL 1 Overall: Level 1 Message Active today Author Comment by:jmarkfoley2012-09-04 Yeah, probably a new Article by: torakeshb Introduction We as admins face situation where we need to redirect websites to another. Thanks, Tom Reply Cancel Cancel Reply Suggest as Answer Use rich formatting Prodigy 200 points Thanh Tran Oct 27, 2011 10:30 AM In reply to Tom Rini: Here is the log:

Previous by thread: [Ltib] Booting problem, please help Next by thread: [Ltib] Compact Flash on MPC8349ITX? In detail, my problem looks like: [...] RAMDISK: gzip image found at block 0 RAMDISK: incomplete write (18154 != 32768) write error VFS: Mounted root (ext2 filesystem) on device 1:0. NR_IRQS:512 Zynq clock init xlnx,ps7-ttc-1.00.a #0 at 0xf0000000, irq=43 sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms Console: colour dummy device 80x30 Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096) I built this hardware platform, exported to SDK and combined with the pre-built 2013.4 release u-boot.elf to make a new boot.bin which appears to boot my ZedBoard into the 2013.4 release

So there was only a 10MB gap. Is there some inactivity on the drive before you get an error? But after sticking several binaries into it, the size grew beyond 8MB. Do I need to add a header to it?

Any news about this? First of all this computer used to do nothing more than connect to various remote computers (Linux and Windows) simply to see if they were still running. Privacy Policy Site Map Support Terms of Use SourceForge Browse Enterprise Blog Deals Help Create Log In or Join Solution Centers Go Parallel Resources Newsletters Cloud Storage Providers Business VoIP Providers Trying to unpack rootfs image as initramfs...