Page 1 of 1

GRUB2 menu entries clarification....

Posted: 04 Aug 2013, 13:57
by surio
Hi again.

I downloaded the new RC2 ISOs and decided to install them on HDD rather than carry USBs that get bashed everywhere. So, now I have a weird issue.

First, here's a scrot of my partitions.

Image

sda16 => port32
sda11 => port64

I had a minor hiccup installing it to the partitions [ext4] but they're nicely installed.

I use GRUB2 as my bootloader (VSIDO => sda9) and my menu entry had:

Porteus 64bit:

Code: Select all

set root='hd0,msdos11' ### (hd1,11)
linux /boot/syslinux/vmlinuz rw from=LABEL:port64 changes=/porteus/
Porteus 32bit:

Code: Select all

set root='hd0,msdos16' ### (hd1,16)
linux /boot/syslinux/vmlinuz rw from=LABEL:port32 changes=/porteus/
The 32 bit kept teling me
from= cheatcode is incorrect. Press ENTER to scan through all possible devices
After I changed the above line to

Code: Select all

set root='hd0,msdos16' ### (hd1,16)
linux /boot/syslinux/vmlinuz rw  from=/dev/sda16   changes=/porteus/ 
it boots straight away.

Anyone knows why? 32 bit recognised the LABEL:port32 command previously... In fact, I got that from an earlier question I clarified from our forums. See here: http://forum.porteus.org/viewtopic.php?f=48&t=2195

So, I can't understand why it won't take it now. In fact, I'm on ext4, so there is no need for the container.dat anymore.

Thanks in advance people.

Surio o/

Re: GRUB2 menu entries clarification....

Posted: 05 Aug 2013, 08:51
by fanthom
1) if you are using 3rd party bootloader (GRUB2 in this case) then there is no need to perform an installation. unpack the ISO where you want and point bootloader config to vmlinuz and initrd.xz.
2) you should not use the same 'changes=/porteus' cheatcode for both 32/64 bit archs as files will be mixed (first /porteus folder found is used). in your case you must tell exac location of /porteus folder so use 'changes=LABEL:port32/porteus' and 'changes=LABEL:port64/porteus' to keep them separate.
3) 'from=LABEL:port32' should work unless you changed label name or moved /porteus folder somewhere else. please boot 64bit porteus and show me output of 'blkid' command and 'ls -1 /mnt/sda16/porteus'

Re: GRUB2 menu entries clarification....

Posted: 06 Aug 2013, 03:27
by surio
@fanthom,
Thank you for the reply.
fanthom wrote:1) if you are using 3rd party bootloader (GRUB2 in this case) then there is no need to perform an installation. unpack the ISO where you want and point bootloader config to vmlinuz and initrd.xz.
Having already installed it, I hope there is no harm done, right? I wanted it to be persistent with updates, language packs etc to be added, so I "installed".
fanthom wrote: 2) you should not use the same 'changes=/porteus' cheatcode for both 32/64 bit archs as files will be mixed (first /porteus folder found is used). in your case you must tell exac location of /porteus folder so use 'changes=LABEL:port32/porteus' and 'changes=LABEL:port64/porteus' to keep them separate.
I will make these changes and provide you with feedback later on. Regarding,
>> " 'from=LABEL:port32' should work unless you changed label name or moved /porteus folder somewhere else"
I have provided you with a scrot of my Partition table... you saw port32 there, didn't you? ;)

Here's scrot of my port32 partition:
Image
fanthom wrote: 3) 'from=LABEL:port32' should work unless you changed label name or moved /porteus folder somewhere else. please boot 64bit porteus and show me output of 'blkid' command and 'ls -1 /mnt/sda16/porteus'
Ran both these as root!

Output for command blkid:

Code: Select all

/dev/sda1: LABEL="System" UUID="BC98F14798F10126" TYPE="ntfs" 
/dev/sda2: LABEL="S3A8723D005" UUID="F6A016EAA016B0DB" TYPE="ntfs" 
/dev/sda4: LABEL="HDDRECOVERY" UUID="A8363C7C363C4D96" TYPE="ntfs" 
/dev/sda5: UUID="13511b68-409a-48dd-84df-696020f8de22" TYPE="swap" 
/dev/sda6: LABEL="mydata" UUID="199e0bd6-413d-44b2-b158-6642486b1869" TYPE="ext4" 
/dev/sda7: UUID="80a8a034-e631-4775-9d31-a0db3d9ba704" TYPE="ext4" 
/dev/sda8: LABEL="korora" UUID="12a43497-a703-459f-a253-e5aa8b8c5382" TYPE="ext4" 
/dev/sda9: LABEL="vsido" UUID="fba15e84-edbe-4955-ab25-5fda0193818d" TYPE="ext4" 
/dev/sda10: LABEL="pinguy" UUID="736e0c78-0c8d-4285-b92f-f97423f33f73" TYPE="ext4" 
/dev/sda11: LABEL="port64" UUID="54aaa2c3-2c23-4b68-b917-79f109cc80cb" TYPE="ext4" 
/dev/sda12: LABEL="mint" UUID="334866da-db75-4350-b270-e36ca5f79f4e" TYPE="ext4" 
/dev/sda13: LABEL="cbang11" UUID="62dd40f3-1dd9-48e2-8126-616b4e4912c0" TYPE="ext4" 
/dev/sda14: LABEL="suse123" UUID="a4da5efa-510c-4296-927f-7bc0436f6d8b" TYPE="ext4" 
/dev/sda15: LABEL="slax64" UUID="73e8aca9-6017-41a1-96a0-bf42a5dfe9d1" TYPE="ext4" 
/dev/loop0: TYPE="squashfs" 
/dev/loop1: TYPE="squashfs" 
/dev/loop2: TYPE="squashfs" 
/dev/loop3: TYPE="squashfs" 
/dev/loop4: TYPE="squashfs" 
/dev/loop5: TYPE="squashfs" 
/dev/loop6: TYPE="squashfs" 
/dev/loop7: TYPE="squashfs" 
/dev/loop8: TYPE="squashfs" 
/dev/loop9: TYPE="squashfs" 
/dev/loop10: TYPE="squashfs" 
/dev/loop11: TYPE="squashfs" 
/dev/loop12: TYPE="squashfs" 
/dev/loop13: TYPE="squashfs" 
/dev/sda16: LABEL="port32" UUID="4b459983-9cf2-4268-aded-6a5585051d97" TYPE="ext4" 
/dev/sda17: LABEL="kp-dev" UUID="28e1e418-2e45-4d34-83cb-d42381110e6e" TYPE="ext4" 
/dev/sda18: LABEL="antix" UUID="46809567-8bb5-40d4-86ee-f188b99ba7d5" TYPE="ext4" 
/dev/sda19: LABEL="grml-home" UUID="683a74c6-abee-4c33-9675-1ca60b73a301" TYPE="ext4" 
/dev/sda20: LABEL="slack" UUID="11c6f4d1-d053-40c0-a7d3-dde5b072180e" TYPE="ext4" 
/dev/sda21: LABEL="ratsalix" UUID="450cd499-9b44-4dfb-9e45-117a5af5209e" TYPE="ext4" 
/dev/sda22: LABEL="xfcsalix" UUID="e6a547d3-2ec5-40af-9600-3577354eb402" TYPE="ext4" 
/dev/sda23: LABEL="matsalix" UUID="cad19e36-7afc-43ac-89d6-4f56e76398e5" TYPE="ext4" 
/dev/sda24: LABEL="lxdsalix" UUID="39b7a310-dd1f-4a65-89e5-f9da1bea4b93" TYPE="ext4" 
/dev/sda25: LABEL="flxsalix" UUID="a3a6aa95-18d2-45b4-aa96-e65ef2a5545f" TYPE="ext4" 
/dev/sda26: LABEL="kdesalix" UUID="7dd00e6a-04d9-467d-bc96-e6bc1364243f" TYPE="ext4" 
/dev/sda27: LABEL="funtoo" UUID="7c3e3230-40fb-4d0f-9b0a-85499093e9dd" TYPE="ext4" 
/dev/sda28: LABEL="llite106" UUID="45a371e5-cbe3-43cf-a921-560053401a10" TYPE="ext4" 
/dev/sda29: LABEL="gentoo" UUID="2c98d4f3-6abb-49ac-a793-753352e5aa55" TYPE="ext4" 
/dev/sda30: LABEL="qt-salen" UUID="283d5387-13e9-4db1-90ef-8ddb0fe68fe2" TYPE="ext4" 
/dev/sda31: LABEL="wattos" UUID="4bf0bcdc-1667-49e8-a90f-8cf736aaaf24" TYPE="ext4" 
/dev/sda32: LABEL="manjaro" UUID="2bf11db9-5d1e-4cfa-b9ef-ae6217acca07" TYPE="ext4" 
/dev/sda33: LABEL="chakra" UUID="0ba3f3f0-9fda-4696-a2c1-9a55a3cf02c6" TYPE="ext4" 
/dev/sda34: LABEL="slackel" UUID="8022b8eb-708a-44c0-96ff-1da25b19a538" TYPE="ext4" 
/dev/sda35: LABEL="SHARED" UUID="2995B8E862C2F35D" TYPE="ntfs" 
Output of "ls -l /mnt/sda16/porteus"

Code: Select all

root@porteus:/home/guest# ls -l /mnt/sda16/porteus
/bin/ls: cannot access /mnt/sda16/porteus: No such file or directory
root@porteus:/home/guest# ls -l /dev/sda16/porteus
/bin/ls: cannot access /dev/sda16/porteus: Not a directory
root@porteus:/home/guest# mount /dev/sda16
mount: can't find /dev/sda16 in /etc/fstab or /etc/mtab
root@porteus:/home/guest# ls -1 /mnt/sda16/porteus
/bin/ls: cannot access /mnt/sda16/porteus: No such file or directory
root@porteus:/home/guest# ls -l /media/port32
total 96
-rwxr-xr-x 1 root root  1152 Aug  3 13:16 USB_INSTALLATION.txt*
-rwxr-xr-x 1 root root 17542 Aug  3 13:16 autorun.ico*
-rwxr-xr-x 1 root root   210 Aug  3 13:16 autorun.inf*
drwxr-xr-x 4 root root  4096 Aug  3 00:54 boot/
-r-xr-xr-x 1 root root 37204 Aug  3 13:16 ldlinux.sys*
drwx------ 2 root root 16384 Jun  4 19:04 lost+found/
drwxr-xr-x 6 root root  4096 Aug  3 00:54 porteus/
-rwxr-xr-x 1 root root   104 Aug  3 13:16 syslinux.cfg*
root@porteus:/home/guest# 


Re: GRUB2 menu entries clarification....

Posted: 06 Aug 2013, 21:44
by fanthom
i trust cli tools more and looks like your label is set correctly. any idea why /dev/sda16 was not automounted during boot? did you use 'noauto/nohd' cheatcodes by any chance?
please check if you have valid .sgn in /mnt/sda16/porteus as incorrect version or missing .sgn may be also a reason of your trouble.

i would reformat this partition and unpack the ISO once again to be 100% sure that everything is ok (especially that you wrote that it was working ok previously).