[CentOS] 3.5 kernel panic on boot
Yes, I know 3.5 is old. However in this case it's required for a legacy app. a fresh install get's me: kmod: failed to exec /sbin/modprobe -s -k block-major-104, errno = 2 followed by: VFS: Cannot open root device cciss/c0d0p2 or 68:02 The system is an HP DL380 G4. any thought on what could cause this? the rescue system is able to mount the disk and grub-install works to re-install grub on the device. TIA Bruce Ferrell ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 3.5 kernel panic on boot
centos-boun...@centos.org wrote: Yes, I know 3.5 is old. However in this case it's required for a legacy app. a fresh install get's me: kmod: failed to exec /sbin/modprobe -s -k block-major-104, errno = 2 The system is an HP DL380 G4. any thought on what could cause this? errno =2 = No such file or directory I presume you have working copies of CentOS 3.5, so Compare /etc/modprobe.conf between working and new system Compare /lib/modules/ between working and new system Insert spiffy .sig here: Life is complex: it has both real and imaginary parts. //me *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated** ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 3.5 kernel panic on boot
Yes, I know 3.5 is old. However in this case it's required for a legacy app. a fresh install get's me: kmod: failed to exec /sbin/modprobe -s -k block-major-104, errno = 2 followed by: VFS: Cannot open root device cciss/c0d0p2 or 68:02 The system is an HP DL380 G4. any thought on what could cause this? Does your installed system have the cciss device entries that are needed? Is the cciss driver reflected in your /etc/modprobe.conf, and was it there when the initrd was built? If you're missing your /dev/cciss entries locating and running mkdev.cciss should create them. Barry ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 3.5 kernel panic on boot
2011/4/5 Bruce Ferrell bferr...@baywinds.org: Yes, I know 3.5 is old. However in this case it's required for a legacy app. What legacy app? You should install centos 5.5 and run legacy app under virtual machine running centos 3.5 .. -- Eero ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
