- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: LINUX initrd
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2003 06:53 AM
тАО09-02-2003 06:53 AM
Re: LINUX initrd
When I try the --with=efs switch to mkinitrd I get the following:
mkinitrd --with=efs3 /boot/initrd-2.4.22 2.4.22
No module efs3 found for kernel 2.4.22
--dan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2003 07:33 AM
тАО09-02-2003 07:33 AM
Re: LINUX initrd
* The module is called "ext3", not "efs";
* Please include the output of "lsmod" in the 2.4.7 kernel;
* Try also include the option "--with=cciss" BEFORE "--with=ext3". It's possible that the cciss is not being included into the initrd as it's not a SCSI device (from the kernel point of view) but a BLOCK device;
* Don't forget to assign the points!
HTH
Paulo Fessel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2003 11:02 AM
тАО09-02-2003 11:02 AM
Re: LINUX initrd
Thanks for you help. I promise I will give points as soon as I get this resolved.
--dan
[root@datprod1 root]#mkinitrd --with=cciss --with=ext3 /boot/initrd-2.4.22 2.4.22
No module jbd found for kernel 2.4.22
[root@datprod1 root]#lsmod
Module Size Used by
ide-cd 27136 0 (autoclean)
cdrom 28736 0 (autoclean) [ide-cd]
loop 9648 0 (autoclean)
pcmcia_core 42688 0
autofs 12096 0 (autoclean) (unused)
nfs 83680 1 (autoclean)
lockd 53744 1 (autoclean) [nfs]
sunrpc 70000 1 (autoclean) [nfs lockd]
bcm5700 104416 1
e1000 67440 1
ipchains 41600 0
ext3 67728 3
jbd 44480 3 [ext3]
cciss 17712 4
sd_mod 11584 0 (unused)
scsi_mod 98512 1 [sd_mod]
[root@datprod1 root]#
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2003 11:34 AM
тАО09-02-2003 11:34 AM
Re: LINUX initrd
"--with=cciss --with=jbd --with=ext3"
jbd is a module that is neccessary in order to ext3 works correctly. Make sure that it gets compiled when you make your kernel.
HTH
Paulo Fessel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2003 11:40 AM
тАО09-02-2003 11:40 AM
Re: LINUX initrd
#mkinitrd --with=cciss --with=jbd --with ext3 /boot/initrd-2.4.22 2.4.22
No module jbd found for kernel 2.4.22
[root@datprod1 root]#
My situation is that I need to build support for the bonding drivers, but they don't appear to be supported on my kernel. I have to run 7.2 because it is the latest OS supported by BEA Weblogic.
Thanks again for you help!
--dan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2003 12:17 PM
тАО09-02-2003 12:17 PM
SolutionUnless you're not using ext3 yes, jbd is neccessary. If it's not available on your system, then something hasn't been compiled correctly.
Here's part of lsmod for my firewall system, running Mandrake for PPC:
ext3 76272 3 (autoclean)
jbd 53808 3 (autoclean) [ext3]
Here you can see ext3 is loaded "on top" of jbd. As you can't copy jbd to your initrd as it doesn't exist, the ext3 can't be loaded as well and your file system will not mount.
Before rebooting, edit your fstab and change all your file system types which are "ext3" to "ext2". Then, use your original initrd and try to boot. I'm almost certain that your system will come online. If it's the case, then double-check your kernel parameters and ensure that both jbd and ext3 modules compile successfully.
To change your newly ext2 file systems converted back to ext3, make sure that jbd and ext3 are loaded and issue this command:
# tune2fs -j /dev/cciss/c0d0p2
HTH
Paulo Fessel
- « Previous
-
- 1
- 2
- Next »