Il giorno dom, 28/01/2007 alle 21.45 +0100, Sander Hoentjen ha scritto: > > > Well that doesn't give me the Starting service [ OK ] stuff, what I was > looking for. It does give me some kernel error: Yes, I don't know (and I think there isn't a way to) to obtain the same output of the boot process. But the messages is enough if all log by using the kernel > Jan 28 21:19:10 storagevrt kernel: scsi4 : iSCSI Initiator over TCP/IP > Is this something I should report, and where? To the fedora kernel or upstream kernel? I can't understand well. Better is to have the entire log from the boot until the logging prompt You can cat from the messages and attach as file (or send to me directly). Post also the fstab. > then after the service netfs start: > Jan 28 21:39:03 storagevrt kernel: kjournald starting. Commit interval 5 seconds > Jan 28 21:39:03 storagevrt kernel: EXT3 FS on dm-70, internal journal > Jan 28 21:39:03 storagevrt kernel: EXT3-fs: mounted filesystem with ordered data mode. > Jan 28 21:39:03 storagevrt kernel: kjournald starting. Commit interval 5 seconds > Jan 28 21:39:03 storagevrt kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended This is a normal messages. If all goes well at boot time, the fsck is automatic. It's better to umount it and check by hand now, and after change the parameter by tune2fs > How can I check if this is needed? By examining the log > /boot is primary ext3 partition (/dev/sda1) > / is logical ext3 partition (/dev/sda5) So it's possible that the / is not mounted at boot time and you need the initrd to contain all modules needed for boot. Post also the /etc/modprobe.conf Bye Ambrogio
