✎ soc:2009:pravin:journal:fedora11bko

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Booting Fedora with BKO ======

===== Where I am getting stuck =====
Following are the messages which are showen before getting stuck
<code>
Mounting proc filesystem
Mounting sysfs filesystem
Creating initial /dev
Running plymouthd
udev: starting version 141
</code>
and It hangs after this point. I have bad feeling that it is not even reaching the step where it will execute /init script
<code>
squashfs: version 4.0 (2009/01/31) Phillip Lougher

</code>
Found the problem, ''plymouth'' is not working properly.  I don't know the reason right now, but for time being, I have commented out the line which starts plymouth and it is progressing after that point.

===== Mounting iso over httpfs =====
Quite a few things are missing from fedora initrd, so I am adding them as and when I am encountering the errors related to them.
  - Added ''ifconfig'' and ''route'' by using ''busybox'' soft link. (Note : I am using knoppix busybox here, Not using fedora busybox because it is not statically linked )
  - Adding fuse module, somehow it is missing, it should have been present by default in kernel. But may be my assumption is wrong about fuse that fuse will present in kernel by default.

Finally, iso is mounted over httpfs.

===== Next set of problems =====
<code>
/dev/root: error opening volume
/dev/root: error opening volume
JBD: barrier-based sync failed on dm-0:8 - disabling barriers
transfering control to /sbin/init
Bug in initramfs /init detected. Dropping to a shell. Good luck!
</code>

It seems, fedora wants something to be set for ''/dev/root'' and another thing that I need to find out is what is this ''JBD'' error about ''barrier-based sync failed''

==== /dev/root ====
''/dev/root: error opening volume''  is handled, I just looked for various places where ''/dev/root'' is used and wrapped it with ''if [-z ${HTTPFS}]'' \\
now I need to find out what is that JBD problem


==== JBD problem ====

I initially doubted function ''do_live_overlay'' but it is clean, 
now, concentrating parent function ''do_live_from_base_loop'' function.
<code>
mount -n -o ro,remount /dev/mapper/live-rw /sysroot
</code> 
is giving above JBD related errors. But this is not fatal, it is continuing even after this
But it seems there might be problems in run-init script


===== solution =====
Finally, problem is solved, there was one more reference to ''plymouth'' that I had to comment out
Most of the plymouth references where options.  Means even the command fails, the execution will not stop
<code>
plymouth --show-splash || :
</code>
but there was one perticular reference, which was not made optional.  I dont know if it is intentional or error.

may be, problem is in ''run-init'' script

===== Next problem =====
The graphical mode and run level 3 are not booting.  There is some problem in sendmail daemon, which is causing segementation fault which just freezes the execution and I get kernel panic.  I will try with disabling sendmail and see if it works.\\
Here is the error
<code>
Starting Bluetooth services:                                 [ OK ]
EXT-4-fs error (device dm-0): ext4_find_entry: reading #13191 offset 0
/etc/rc.d/rc : line 100 : /etc/rc3.d/S80sendmail: Input/output error
</code>
and so on....

=== solution ===
I disabled sendmail and tried.  It partially worked. There was some error which I could not see because of scrolling, but then it gave login prompt.
The problem is, when I press enter key, it takes it as ''^M'', so I am not able to login :-(

=== attempt 2 ===
Disabled selinux with ''selinux=0'' and tried again\\
I removed sendmail and other services which were related to S99 like firstboot, local.
but still I am getting error
<code>
EXT4-fs error (device dm-0): __ext4_get_inode_loc: unable to read inode block - inode=9642, block=827
</code>

and following are the logs from apache2 server which was serving this iso image.
<code>
$ cat /var/log/apache2/access.log | tail
192.168.0.1 - - [06/Jul/2009:23:56:27 +0200] "GET /Fedora-11-i686-Live.iso HTTP/1.1" 206 4096 "-" "-"
192.168.0.1 - - [06/Jul/2009:23:56:27 +0200] "GET /Fedora-11-i686-Live.iso HTTP/1.1" 206 16384 "-" "-"
192.168.0.1 - - [06/Jul/2009:23:56:27 +0200] "GET /Fedora-11-i686-Live.iso HTTP/1.1" 206 32768 "-" "-"
192.168.0.1 - - [06/Jul/2009:23:56:27 +0200] "GET /Fedora-11-i686-Live.iso HTTP/1.1" 206 65536 "-" "-"
192.168.0.1 - - [06/Jul/2009:23:56:27 +0200] "GET /Fedora-11-i686-Live.iso HTTP/1.1" 206 131072 "-" "-"
192.168.0.1 - - [06/Jul/2009:23:56:27 +0200] "GET /Fedora-11-i686-Live.iso HTTP/1.1" 206 131072 "-" "-"
192.168.0.1 - - [06/Jul/2009:23:56:27 +0200] "GET /Fedora-11-i686-Live.iso HTTP/1.1" 206 4096 "-" "-"
192.168.0.1 - - [06/Jul/2009:23:56:27 +0200] "GET /Fedora-11-i686-Live.iso HTTP/1.1" 206 16384 "-" "-"
192.168.0.1 - - [06/Jul/2009:23:56:27 +0200] "GET /Fedora-11-i686-Live.iso HTTP/1.1" 206 32768 "-" "-"
192.168.0.1 - - [06/Jul/2009:23:56:27 +0200] "GET /Fedora-11-i686-Live.iso HTTP/1.1" 206 65536 "-" "-"
</code>
I am not sure if they will make any sense, but I have put them for reference.

====== What is working?  ======
Single user mode is working fine.  so user gets shell where he can do all he wants
Trace: • initramfsbko • bkodebian • week10 • dverkamp • iscsi_install • bkodebianiscsi • ubuntubko • debian_and_ubuntu • project_plan • fedora11bko • week2