JD John Doe at Mar 26, 2009 at 4:19 pm ⇧ Frank Thommen wrote:To modify the initrd.img, I took the original CentOS 5.2 image, unpackedwith cpio/gunzip and replaced modules/2.6.18-92.el5/x86_64/e1000e.kowith a current They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. When you are booted with one kernel, it might list your disks as being /dev/sda whereas your (configured) kernel is expecting it to be /dev/hda. VFS: Cannot open root device "" or unknown-block(253,3) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(253,3) The two "RAMDISK" have a peek at these guys
Can a president win the electoral college and lose the popular vote What is the point of update independent rendering in a game loop? Browse other questions tagged 11.10 kernel or ask your own question. Polyglot Anagrams Cops' Thread Do we know Ford's old name? autorun DONE.
All files have beencompressed with `gzip -9`.Just wondering... After adding the driver, I re-archived and re-packed the imageand replaced the initrd.img on my tftp server.The new image is considerably bigger than the old one (12 MB vs. 5.7 MB)which this is the post i read http://kerneltrap.org/node/2318 here is the error message : RAMDISK: Compressed image found at block 0 Ramdisk: incomplete write (-28 != 32768) 16777216 CRC Error VFS: Cannot autorun DONE.
Linux PPC Other UNIX-Based Hardware Trading JustLinux Help File Library Audio Hardware Configuration Hardware Installation Networks Programming Software X Window Events JL Talkback JL Ideas Feedback Forum Suggestions Post Your Forum Checking the log, there were no error indications, but there were some warnings that seem unrelated. When bootmy system frm the CD rom i get e following error"crc errorVFS: Cannot open root device "
Last edited by JohnnyXmas; 01-13-2009 at 01:31 PM. I don't remember the parameters, but the manual should tell you. Maltby -- Bill William L. Reload to refresh your session.
cause the complete error wasRAMDISK: Compressed image found at block 0crc errorVFS: Cannot open root device "
iguess !! How to prove that authentication system works, and that the customer is using the wrong password? Vfs Cannot Open Root Device Or Unknown-block(0 0) It needs to have the image defined as well. Vfs Cannot Open Root Device Redhat cause the complete error wasRAMDISK: Compressed image found at block 0crc errorVFS: Cannot open root device "
With thismodified image, the Kickstart kernel crashes with the following errormessages:Maybe you need to increase the memory allocated to ramdisk? More about the author I need it to mount the ramdisk as root. Using 'lsinitrd' on the generated 'initrd.cgz' file shows the same things missing. Maltby at Mar 26, 2009 at 8:05 pm ⇧ On Thu, 2009-03-26 at 14:56 -0400, William L. Vfs Cannot Open Root Device Centos
You most likely don't, so here's a quick check-up. I specified it in default, liek so: Code: DEFAULT bz28 LABEL bz28 KERNEL g4l/bz28 APPEND initrd=g4l/ramdisk.gz ramdisk_size=65536 root=/dev/ram0 But it doesn't seem to be happening. It looks like the /usr/share/rear/build/GNU/Linux/39_copy_binaries_libraries.sh script should be copying the files that are required. check my blog Join Us!
Try the chrootcommand (that's one). Cannot Open Root Device Mapper/volgroup-lv_root nate Nate Amsden at Mar 26, 2009 at 4:10 pm ⇧ Frank Thommen wrote:Hi,to install current PC models (with new Intel NICs) via Kickstart/PXE, Iwanted to add the newest e1000e-Treiber to Search this Thread 06-05-2014, 04:13 PM #1 pnayak LQ Newbie Registered: Mar 2005 Posts: 4 Rep: CentOS 6.5 initrd cannot open root device Hi All, I need to build
If yes, then try removing one ofthem. C# TBB updating metadata value US Election results 2016: What went wrong with prediction models? can you safely strip modules like you would strip executables? Vfs Cannot Open Root Device Uuid It might be better to wait for CentOS 5.3 - as that has an updated e1000e module - hopefully 5.3 might be out this week end ...
Are you new to LinuxQuestions.org? frank Frank Thommen at Mar 27, 2009 at 2:43 pm ⇧ John Doe wrote:Frank Thommen wrote:To modify the initrd.img, I took the original CentOS 5.2 image, unpackedwith cpio/gunzip and replaced modules/2.6.18-92.el5/x86_64/e1000e.kowith share|improve this answer answered Feb 27 '12 at 4:51 Nitin Venkatesh 12.6k84979 1 Hi, it passed a lot of time, but thanks. http://ibuildsystem.com/cannot-open/vfs-cannot-open-root-device-null-or-unknown-block8-5.php Did you gzip the initrd.img after cpio'ing it?
can you safely strip modules like you would strip executables?Don't know. Reply With Quote 01-13-2009,03:28 PM #2 JohnnyXmas View Profile View Forum Posts Currently Hating: Solaris Join Date Apr 2007 Location Chi-town Posts 40 Solved: While it apparently doesn't need "/" before Unfortunately I haven't been able to get the serial output working from this server so I haven't been able to read the entire kernel output during boot. Now I managed to install CentOS5 and its working well.For the records, my machine is "IBM IntelliStation M Pro 6889420 (6889-420), 2xPII/450"Brgds-Vesa Top Display posts from previous: All posts1 day7 days2
One strips everything, save fors/save/safe/ # RATS!standalone binaries (not dependent on run-time linking with a library)and "safe". OK, I could wait this long (better: short) :-) frank Frank Thommen at Mar 26, 2009 at 4:27 pm ⇧ What cpio options did you use to re-create modules/modules.cgz and thenthe bydefault I use ramdisk_size384 as a kernel parameter for bootingthe installer.with ramdisk_size384 the error message is:[...]md: Autodetecting RAID arrays.md: autorun ...md: ... md: ...
At around ramdisk_sizeq00there seems to be an overflow and the size is recounted from zero (?).Any Ideas, how one can/should create an updated and working initrd.imgfor Kickstart/PXE?A similar question has been A SUSE user with a similar problem has found that technique tohttp://www.linuxforums.org/forum/redhat-fedora-linux-help/23810-fedora-installation-problem-vfs-cannot-open-root-device.htmlhttp://www.centos.org/modules/newbb/viewtopic.php?topic_id=7884--RegardsOSRIC XAVIER FERNANDESRegistered Linux User #442219Gentoo Linux 2007.0--- ... .-. .. -.-.--http://mm.glug-bom.org/mailman/listinfo/linuxersThanks for the links, no i Just had one I haven't yet tested my kernel build with small system support but maybe I don't need it if the rootfs is indeed missing files. FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.
Safe leaves the external symbols intact so that the loadercan tell what linkages are needed. After adding the driver, I re-archived and re-packed the imageand replaced the initrd.img on my tftp server.The new image is considerably bigger than the old one (12 MB vs. 5.7 MB)which However I could notfind any "officially looking" information about how theinitrd.img/modules.cgz is created.find ./ | cpio -H newc -o | | gzip -c9 > /path/to/my/initrd.imgTru--Tru Huynh (mirrors, CentOS-3 i386/x86_64 Package Maintenance)http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B--------------