<br><font size=2 face="sans-serif">Dear Wang</font>
<br>
<br>
<br><font size=2 face="sans-serif"><br>
> hi,<br>
> <br>
> The boot flag is only set on /dev/sda1, but it's for the /boot partition<br>
> (100M), and df can not found the the root partition with the latest <br>
> kboot<br>
> (20070817), but with the old one (comes from yellowdog), it's OK.<br>
> <br>
> here is the `fdisk -l' output:<br>
> <br>
> Device Boot Start End Blocks Id System<br>
> /dev/ps3da1 * 1 96 98288 83 Linux<br>
> /dev/ps3da4 97 44943 45923328 5 Extended<br>
> /dev/ps3da5 97 22032 22462448 83 Linux<br>
> /dev/ps3da6 22033 43968 22462448 82 Linux<br>
> /dev/ps3da7 43969 44943 998384 82 Linux swap<br>
> <br>
> ps3da1 /boot<br>
> ps3da4 Extended<br>
> ps3da5 /<br>
> ps3da6 /backup<br>
> ps3da7 swap<br>
> <br>
> I'm not sure why the new kboot don't try to mount the / partition. I've <br>
> used<br>
> <br>
> e2label /dev/ps3da5 /</font>
<br>
<br><font size=2 face="sans-serif">Old kboot use the file system label to search a root partiton.</font>
<br><font size=2 face="sans-serif">YellowDog kboot is old kboot based. So you can boot your Linux.</font>
<br>
<br><font size=2 face="sans-serif">But current kboot does not use the file system label.</font>
<br><font size=2 face="sans-serif">Current kboot configuration file search algorithm is as follows.</font>
<br>
<br><font size=2 face="sans-serif"> - device search priority</font>
<br><font size=2 face="sans-serif"> built-in BD drive, USB mass storage, built-in HDD</font>
<br>
<br><font size=2 face="sans-serif"> - check if the media has more than one partitions, if no, try to</font>
<br><font size=2 face="sans-serif"> examine boot configuration file on the media.</font>
<br>
<br><font size=2 face="sans-serif"> - Otherwise, it checks if the partition is marked as "active" or not in </font>
<br><font size=2 face="sans-serif"> ascending order. In the case of "active', try to examine boot configuration</font>
<br><font size=2 face="sans-serif"> file on the partition.</font>
<br>
<br><font size=2 face="sans-serif"> - check if format of the media(or partition) meet one of following;</font>
<br><font size=2 face="sans-serif"> ext2, ext3 (on USB mass), FAT16/32 (on USB mass) or ISO9660 (on optical)</font>
<br><font size=2 face="sans-serif"> (Caution) kboot mount ext3 file system by using "-t ext2" option</font>
<br>
<br><font size=2 face="sans-serif"> - try to mount the selected media(or partition) and check a boot</font>
<br><font size=2 face="sans-serif"> configuration file named either /etc/kboot.conf or /ETC/KBOOT.CNF. </font>
<br><font size=2 face="sans-serif"> If the boot configuration file exists, kboot read it. If the boot </font>
<br><font size=2 face="sans-serif"> configuration file does not exist, kboot umount the selected media</font>
<br><font size=2 face="sans-serif"> (or patition) and check the next media(or patition).</font>
<br>
<br><font size=2 face="sans-serif">New kboot try to mount /dev/ps3da1 to '/' and seach '/etc/kboot.conf' file.</font>
<br><font size=2 face="sans-serif">But '/boot/etc/kboot.conf' does not exist, so you can not boot your Linux.</font>
<br><font size=2 face="sans-serif"><br>
> <br>
> I've also cat /etc/kboot.conf while I got the kboot prompt<br>
> <br>
> 1) If there is no network:<br>
> <br>
> root=LABEL=/<br>
> <br>
> 2) If network is avialiable (we have a dhcp server and also provide <br>
> diskless<br>
> linux)<br>
> <br>
> default=nfsboot<br>
> timeout=10<br>
> <br>
> nfsboot='tftp://192.168.1.1pxelinux.0 root=/dev/nfs ip=on nfsroot=192.168.1.1: '</font>
<br>
<br><font size=2 face="sans-serif">This setting is wrong.</font>
<br><font size=2 face="sans-serif">Correct setting is as follows.</font>
<br>
<br><font size=2 face="sans-serif">nfsboot='tftp://192.168.1.1/pxelinux.0 root=/dev/nfs ip=on nfsroot=192.168.1.1:/ '</font>
<br><font size=2 face="sans-serif"> - -</font>
<br><font size=2 face="sans-serif">Regards,</font>
<br><font size=2 face="sans-serif">Hiroaki Fuse<br>
</font>