[Solved] /boot/lin_start_here.sh shows md5sum failure

[kaz]

While trying to install Porteus-v1.2-i486 to an ext2 partition on a USB drive, /boot/lin_start_here.sh says:

_.====.._
,:._ ~-_
'\ ~-_
\ \.
,/ ~-_
-..__..-'' PORTEUS ~~--..__
--==--==--==--==--==--==--==--==--==--==--==--==--==--==
Welcome to Porteus-v1.2
--==--==--==--==--==--==--==--==--==--==--==--==--==--==

[1] Read Porteus requirements
[2] Read Porteus installation instructions
[3] Read Porteus cheatcodes
[4] Read about bootloaders
[5] Install Porteus to FATx or EXTx partition (extlinux)
[6] Install Porteus to any partition (LILO)
no graphical - only text menu available
[7] Quit this application

Please choose a menu item ...
5



Checking md5sums - wait a while...

checking md5sum for boot/vmlinuz ok
checking md5sum for boot/initrd.xz ok
checking md5sum for porteus/base/000-kernel.xzm fail!
checking md5sum for porteus/base/001-core.xzm fail!
checking md5sum for porteus/base/002-xorg.xzm fail!
checking md5sum for porteus/base/003-lxde.xzm fail!
checking md5sum for porteus/base/004-tde.xzm fail!
checking md5sum for porteus/base/005-tdeapps.xzm fail!
checking md5sum for porteus/base/006-abiword.xzm fail!
checking md5sum for porteus/base/007-devel.xzm fail!
checking md5sum for porteus/base/008-firefox.xzm fail!

Some md5sums doesn't match or some files from default ISO are missing,
please check above...
Be aware that vmlinuz, initrd.xz, 000-kernel.xzm and 001-core.xzm are
most important and booting wont be possible when they are missing.
Press enter to continue or ctrl+c to exit

Ignoring the failure and just continuing makes a good bootable USB drive.

Official Porteus Installation Guide says, "As of Porteus Version 1.1, the officially supported method for installing Porteus to a flash drive or hard drive is ... run the program 'Porteus Installer'", so is using /boot/lin_start_here.sh not officially supported?

[Ahau]

Hi kaz,

lin_start_here.sh is still maintained and supported (I still install Porteus this way). Our goal with that line of text in the install guide is to point new users to burning Porteus to a CD and running 'porteus installer' because lin_start_here.sh can fail when run from some other distributions (most are OK, but debian and ubuntu are problematic). Plus, we like brokenman's gtkdialog work

Regarding the checksum failures -- do you perhaps have some sort of non-standard directory layout (/boot and /porteus/base not in the same parent directory), or did you only copy some of the files from the ISO into an existing installation on the flash drive? Since the kernel and initrd check out OK but all others fail and your system still boots OK, it leads me to believe the checksums script (/porteus/chkbase.sh) is not finding your modules in order to check them, or perhaps your md5sums.txt, kernel and initrd are from an older install.

To test, please mount the Porteus 1.2 ISO and manually check the md5sums:

Code: Select all

mloop /path/to/Porteus-1.2-i486.iso
cd /mnt/loop/porteus
./chkbakse.sh

and if everything checks out OK there, then see how the md5sums compare with your flash drive install:

Code: Select all

#still in /mnt/loop/porteus
cat md5sum.txt
cd /mnt/sdXY/porteus/base
md5sum *

And see if they all match up with /mnt/sdXY/porteus/md5sum.txt -- find the odd man out

[kaz]

Thank you, Ahau.

OK, I will follow your testing method.

Code: Select all

root@porteus:~# mloop /mnt/ph/archives/misc-linux/Porteus-v1.2-i486.iso
#################################
Your image has been mounted at:
/mnt/loop

You can unmount it by typing uloop

Here is a list of the files:
USB INSTALLATION.txt  boot  porteus

root@porteus:~# cd /mnt/loop/porteus
root@porteus:/mnt/loop/porteus# ./chkbakse.sh
-su: ./chkbakse.sh: No such file or directory

Instead of ./chkbase, I tried sh chkbase, and went on. The output was:

Code: Select all

root@porteus:/mnt/loop/porteus# sh chkbase.sh 

Checking md5sums - wait a while...

checking md5sum for  boot/vmlinuz    ok
checking md5sum for  boot/initrd.xz    ok
checking md5sum for  porteus/base/000-kernel.xzm   fail!
checking md5sum for  porteus/base/001-core.xzm   fail!
checking md5sum for  porteus/base/002-xorg.xzm   fail!
checking md5sum for  porteus/base/003-lxde.xzm   fail!
checking md5sum for  porteus/base/004-tde.xzm   fail!
checking md5sum for  porteus/base/005-tdeapps.xzm   fail!
checking md5sum for  porteus/base/006-abiword.xzm   fail!
checking md5sum for  porteus/base/007-devel.xzm   fail!
checking md5sum for  porteus/base/008-firefox.xzm   fail!

Some md5sums doesn't match or some files from default ISO are missing,
please check above...
Be aware that vmlinuz, initrd.xz, 000-kernel.xzm and 001-core.xzm are
most important and booting wont be possible when they are missing.
Press enter to continue or ctrl+c to exit

root@porteus:/mnt/loop/porteus# cat md5sum.txt
cat: md5sum.txt: No such file or directory

Here the file to be displayed is not md5sum.txt but md5sums.txt.

Code: Select all

root@porteus:/mnt/loop/porteus# cat md5sums.txt
a28bcc069c17e09dbee068c1209929c5  boot/vmlinuz
6a2a4330de7ab462f9103496b6204692  boot/initrd.xz
cf1dd85903bfab3a1a90884561bae048  porteus/base/000-kernel.xzm
2074dff08df544bf872f8324e7f8d296  porteus/base/001-core.xzm
2910a5618a606ff158270144720ba254  porteus/base/002-xorg.xzm
f09f06d6df404117661478d8b31bb501  porteus/base/003-lxde.xzm
7c6fe7450ab5105b81ecea2ef2f926d9  porteus/base/004-tde.xzm
eb54962a61b2f2521fccc8cecbaf3f32  porteus/base/005-tdeapps.xzm
5b2772b6ba3eeb69316a636f85c5379d  porteus/base/006-abiword.xzm
5449410859adbccfb3853bde275cccbc  porteus/base/007-devel.xzm
260a47e2b854292600d3ef5b1b15d3ee  porteus/base/008-firefox.xzm
root@porteus:/mnt/loop/porteus# cd /mnt/sdd1/porteus/base
root@porteus:/mnt/sdd1/porteus/base# md5sum *
cf1dd85903bfab3a1a90884561bae048  000-kernel.xzm
2074dff08df544bf872f8324e7f8d296  001-core.xzm
2910a5618a606ff158270144720ba254  002-xorg.xzm
f09f06d6df404117661478d8b31bb501  003-lxde.xzm
7c6fe7450ab5105b81ecea2ef2f926d9  004-tde.xzm
eb54962a61b2f2521fccc8cecbaf3f32  005-tdeapps.xzm
5b2772b6ba3eeb69316a636f85c5379d  006-abiword.xzm
5449410859adbccfb3853bde275cccbc  007-devel.xzm
260a47e2b854292600d3ef5b1b15d3ee  008-firefox.xzm

All look good.

Posted after 17 minutes 15 seconds:
chkbase.sh reads:

Code: Select all

    file=`awk NR==$x md5sums.txt |  cut -d " " -f2-`
    first=`awk NR==$x md5sums.txt |  cut -d " " -f1`
    second=`grep $file $out |  cut -d " " -f1`
    if [ "$first" = "$second" ];then
        echo "checking md5sum for $file    ESC[36mok""ESC[0m"
    else
        echo "checking md5sum for $file   ESC[31mfail!""ESC[0m"
        fail="yes"
    fi

According to my test results, $file looks like "porteus/base/000-kernel.xzm", but in the file $out, the file name looks like "000-kernel.xzm".
So, grep $file $out shows nothing.

[Ahau]

Hi kaz,

Looks like this was an issue in the creation of md5sums.txt when the iso was created, and it's being fixed -- sorry for the bum info on my part (I assumed it was correct without testing to be sure). Proceeding with installing despite the error should work fine for now, as you found out.

Thanks!

[brokenman]

My bad.

Paths in md5sums.txt are not relative to porteus folder. Should be:

../boot/vmlinuz
../boot/initrd.xz
./base/000-kernel.xzm
./base/001-core.xzm
./base/002-xorg.xzm