Hello, trying to make a usb install on a thin client it seems I notice an incorrect diskboot.img image in 5.7. Anyone already discovered/reported this?
As soon as I boot from usb pen drive, I get an error Could not find kernel image: linux
this depends on syslinux.cfg being empty
sha1sum of my dvd iso is correct # sha1sum CentOS-5.7-i386-bin-DVD-1of2.iso e0eab4dd77c3ecc73080428beaa4ffe28984dc4b CentOS-5.7-i386-bin-DVD-1of2.iso
# mount -o loop CentOS-5.7-i386-bin-DVD-1of2.iso /mnt/
# sha1sum /mnt/images/diskboot.img 0568258b34eda506e76801ea5bfd6b57cdd299bc /mnt/images/diskboot.img
# mount -o loop /mnt/images/diskboot.img /pp
on CentOS 5.7 under /pp I have: total 12244 -rwxr-xr-x. 1 root root 292 Sep 5 11:53 boot.msg -rwxr-xr-x. 1 root root 919 Sep 5 11:53 general.msg -rwxr-xr-x. 1 root root 10450542 Sep 5 11:53 initrd.img -rwxr-xr-x. 1 root root 10648 Sep 5 11:53 isolinux.bin -r-xr-xr-x. 1 root root 9660 Sep 5 11:53 LDLINUX.SYS -rwxr-xr-x. 1 root root 94600 Sep 5 11:53 memtest -rwxr-xr-x. 1 root root 817 Sep 5 11:53 options.msg -rwxr-xr-x. 1 root root 517 Sep 5 11:53 param.msg -rwxr-xr-x. 1 root root 490 Sep 5 11:53 rescue.msg -rwxr-xr-x. 1 root root 63803 Sep 5 11:53 splash.lss -rwxr-xr-x. 1 root root 0 Sep 5 11:53 syslinux.cfg -rwxr-xr-x. 1 root root 1892352 Sep 5 11:53 vmlinuz
while on CentOS 5.6 total 9562 -rwxr-xr-x. 1 root root 292 Mar 29 23:15 boot.msg -rwxr-xr-x. 1 root root 919 Mar 29 23:15 general.msg -rwxr-xr-x. 1 root root 7705221 Mar 29 23:15 initrd.img -rwxr-xr-x. 1 root root 10648 Mar 29 23:15 isolinux.bin -r-xr-xr-x. 1 root root 9660 Mar 29 23:15 LDLINUX.SYS -rwxr-xr-x. 1 root root 94600 Mar 29 23:15 memtest -rwxr-xr-x. 1 root root 817 Mar 29 23:15 options.msg -rwxr-xr-x. 1 root root 517 Mar 29 23:15 param.msg -rwxr-xr-x. 1 root root 490 Mar 29 23:15 rescue.msg -rwxr-xr-x. 1 root root 63803 Mar 29 23:15 splash.lss -rwxr-xr-x. 1 root root 340 Mar 29 23:15 syslinux.cfg -rwxr-xr-x. 1 root root 1888052 Mar 29 23:15 vmlinuz
Tried to simply copy the syslinux.cfg from 5.6 and recreating diskboot.img but as soon as there are some dots of the initrd phase, just before the moment when I should see the kernel messages the pc reboots itself. it is a Dell thin client Optiplex FX160 Donna if it could be a problem with my hw or other kind of problems in necessary files.....
Gianluca
Hi,
On 09/16/2011 04:09 PM, Gianluca Cecchi wrote:
Hello, trying to make a usb install on a thin client it seems I notice an incorrect diskboot.img image in 5.7. Anyone already discovered/reported this?
Investigating this issue. Could you open a bug report on bugs.centos.org please ? we can track progress there.
- KB
On Sat, Sep 17, 2011 at 9:45 AM, Karanbir Singh wrote:
Hi,
Investigating this issue. Could you open a bug report on bugs.centos.org please ? we can track progress there.
Ok, done: http://bugs.centos.org/view.php?id=5118
Gianluca
On 09/17/2011 11:07 AM, Gianluca Cecchi wrote:
Ok, done: http://bugs.centos.org/view.php?id=5118
we pushed a proposed replacement diskboot.img ( url'd from the bug report ) - would you be able to check that and make sure it ticks the box's.
- KB
On Sun, Sep 18, 2011 at 11:36 AM, Karanbir Singh wrote:
On 09/17/2011 11:07 AM, Gianluca Cecchi wrote:
Ok, done: http://bugs.centos.org/view.php?id=5118
we pushed a proposed replacement diskboot.img ( url'd from the bug report ) - would you be able to check that and make sure it ticks the box's.
I confirm that with this 18Mb diskboot I can successfully start installation an the same thin client reported. So it seems to solve the problem. Thanks!
Now install is running but I have a slow connection so it would take about 5hours to complete. I'm going to fill bug report when completed....
I noticed one possible "bug" in anaconda in 5.6 that fired me and seems to be still present in 5.7.
If you boot from usb key, it is seen as /dev/sdb while the internal disk is seen as /dev/sda correctly. But by default, even if you set to ignore /dev/sdb (asked two times during install), when it arrives at grub install it defaults to install on MBR of sdb, so the usb key.... and if you don't take care, at the end you get an unbootable system... The only way I found to force /dev/sda is to go for advanced grub option and select the tab where you say to swap drives names'.... (yet to see after my install if this works correctly).
I think the normal user could find difficult, at first to detect the wrong automatically set /dev/sdb option for grub, and then to put correct setup in..... Probably anaconda should guess that if you install on /dev/sda, probably you would like to set grub there too... What do you think? Or is this a bios related problem only for my particular client and not in general????
Gianluca
-
Gianluca Cecchi -
Karanbir Singh