Author Topic: Bootloader Limitation Problem  (Read 2999 times)

Online TerryN

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 732
Re: Bootloader Limitation Problem
« Reply #15 on: January 16, 2013, 12:30:54 PM »
This file is in drakxtools-backend, so the way to change it in future ISOs would be to submit an updated version of that package. Would a package request for the change be legitimate?

I have noted the request  ;)
I have a couple of other things to fix in the draktools so I'll add it to the list.

Terry.
Dell E521 - AMD 64 X2 5000+, 4GB RAM, ATI X1300 graphics
PCLinuxOS 2013 (KDE)
|Twitter|

Online Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11597
  • ----IOFLU----
Re: Bootloader Limitation Problem
« Reply #16 on: January 16, 2013, 12:55:58 PM »
This file is in drakxtools-backend, so the way to change it in future ISOs would be to submit an updated version of that package. Would a package request for the change be legitimate?

I have noted the request  ;)
I have a couple of other things to fix in the draktools so I'll add it to the list.

Terry.

Terry, you are so good.  ;D
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline Just17

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 10694
  • MLUs Forever!
Re: Bootloader Limitation Problem
« Reply #17 on: January 16, 2013, 01:25:48 PM »
This file is in drakxtools-backend, so the way to change it in future ISOs would be to submit an updated version of that package. Would a package request for the change be legitimate?

I have noted the request  ;)
I have a couple of other things to fix in the draktools so I'll add it to the list.

Terry.

Thank you!

MLUs rule the roost!

Linux XPS 3.4.38-pclos1.bfs  64 bit
Intel Core2 Quad CPU Q9450 @ 2.66GHz
4 GB RAM
MCP51 High Def Audio
GeForce GTX 550 Ti
PHILIPS  ‎DVD+-RW DVD8701
‎Logitech ‎BT Mini-Receiver
Afatech DTT

Offline wedgetail

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2446
  • Any Bugs in site?
Re: Bootloader Limitation Problem
« Reply #18 on: January 16, 2013, 02:49:49 PM »

In my unsquashed system, the location where I made the change

/squashfs-root/usr/lib/libDrakX/bootloader.pm

....................
sub add_entry {
    my ($bootloader, $v) = @_;

    my $to_add = $v;
    my $label = $v->{label};
    for (my $i = 0; $i < 99;) {
   my $conflicting = get_label($label, $bootloader);
.........................

By the way I did not add the smiley here.

I assume this has nothing to do with why my mkiso turned the livecd.sqsfs into an executable file, well I think this is what the x in permissions means.      :D
32 bit: KDE (older) & various KDE-mini, ASUSTek P5P41D Rev X.0x, BIOS AMI0207 07/21/2009, "Pentium(R) Dual-Core CPU E5300 @ 2.60GHz", nVidia GeForce 9600 GT, 2x1GB Seagate Technology 1000528AS HDD
TV CompuPro VideoMate Vista E700 (not working in Linux), Acer X243HD LCD Screen

Offline Just17

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 10694
  • MLUs Forever!
Re: Bootloader Limitation Problem
« Reply #19 on: January 16, 2013, 03:17:43 PM »
Have you tried creating another ISO with the files?

If so was the squash file name altered again?



MLUs rule the roost!

Linux XPS 3.4.38-pclos1.bfs  64 bit
Intel Core2 Quad CPU Q9450 @ 2.66GHz
4 GB RAM
MCP51 High Def Audio
GeForce GTX 550 Ti
PHILIPS  ‎DVD+-RW DVD8701
‎Logitech ‎BT Mini-Receiver
Afatech DTT

Offline wedgetail

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2446
  • Any Bugs in site?
Re: Bootloader Limitation Problem
« Reply #20 on: January 16, 2013, 03:45:59 PM »
Yes I repeated last night with the same directory structure, ie source in one partition and destination in another both on my 2nd hard drive, partition numbers 18 and 20.

This morning I tried to make one with destination /tmp, crashed grand style, something about directory level exceeded a limit of 6.  Not a smart move as I did not know there was directory level limits here.

The last run I made to a new destination directory called /zmkiso this was successful but for filename change.
Here source was on second drive and active system is also located here.   

My problem now is I have so little base knowledge I am now running out of things to guess. 

I have this feeling that perhaps the filename change could be fixed by using a mkisofs option.

Also is there a problem with running through /media/ mounts

Timeout before next onslaught  ;D
32 bit: KDE (older) & various KDE-mini, ASUSTek P5P41D Rev X.0x, BIOS AMI0207 07/21/2009, "Pentium(R) Dual-Core CPU E5300 @ 2.60GHz", nVidia GeForce 9600 GT, 2x1GB Seagate Technology 1000528AS HDD
TV CompuPro VideoMate Vista E700 (not working in Linux), Acer X243HD LCD Screen

Offline Just17

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 10694
  • MLUs Forever!
Re: Bootloader Limitation Problem
« Reply #21 on: January 16, 2013, 04:35:41 PM »
I suggest you start again from scratch to see if the problem can be repeated, and post the three commands you use.

Also to eliminate any inconsistencies I suggest you keep all the files on the one partition.

The commands I used

Code: [Select]
unsquashfs -d /home/user/test-iso/unsquash livecd.sqfs

mksquashfs /home/user/test-iso/unsquash  livecd.sqfs

mkisofs -o /home/user/test.iso /home/user/test-iso/

which did not give any corruption of file names.

MLUs rule the roost!

Linux XPS 3.4.38-pclos1.bfs  64 bit
Intel Core2 Quad CPU Q9450 @ 2.66GHz
4 GB RAM
MCP51 High Def Audio
GeForce GTX 550 Ti
PHILIPS  ‎DVD+-RW DVD8701
‎Logitech ‎BT Mini-Receiver
Afatech DTT

Offline wedgetail

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2446
  • Any Bugs in site?
Re: Bootloader Limitation Problem
« Reply #22 on: January 16, 2013, 08:00:27 PM »
Just17
I will have to take it a bit easy, family activity is increasing and grandad does not have an escape any longer.  I will return to try and figure out what is going on.

A fix for the time being has now allowed me to write this post from Firefox on a running liveHDD where the bootloader.pm is fixed up but no time to test if it can install, this is the now the burning question.  I am scrambling through the manual for mkisofs, pheeew that is heavy going not understanding more than 5%.

From that I applied option -r and this seems to make the destination livecd.sqfs proper, ie now the .sqfs is back to 4 characters and it is totally read only.

I will use another new install of KDE32 and do it your way, as I did make a quick run keeping everything in the B-20 partition but that did not help.    :)

Added:
Running the liveHDD with edited bootloader.pm I installed the ISO to an empty partition-07 on my 3rd HDD, it worked bar minor fumblings like getting totally wrong password to what I normally use.  I will scrap the install later.

I used the installed KDE32-2012.12 after fully updating and adding a few smaller treats of my own, to experiment with your suggestion. I almost managed to do exactly but I had actually made the directory 

Code: [Select]
[root@localhost gert]# mkdir /home/user/test-iso/unsquash
not sure what happened here as when I came to do the unsquash, complaining that directory existed, quickly just added /expand and the process proceeded.

Quote
[root@localhost gert]# unsquashfs -d /home/gert/test-iso/unsquash/expand /za/livecd.sqfs

I have my original ISO loop mounted on /za so I could point to the livecd.sqfs file successfully.
Shortly afterwards this succeeded.

Code: [Select]
[root@localhost gert]# mksquashfs  /home/gert/test-iso/unsquash/expand livecd.sqfs
I followed up with a second run where the destination file was on /media/B-20, seems moving to another copy of the OS may have paid off.

Though I am niggled by why I had the trouble on the previous system, so I probably will go back and investigate a bit more.   :) ;D ;D
« Last Edit: January 17, 2013, 12:07:51 AM by wedgetail »
32 bit: KDE (older) & various KDE-mini, ASUSTek P5P41D Rev X.0x, BIOS AMI0207 07/21/2009, "Pentium(R) Dual-Core CPU E5300 @ 2.60GHz", nVidia GeForce 9600 GT, 2x1GB Seagate Technology 1000528AS HDD
TV CompuPro VideoMate Vista E700 (not working in Linux), Acer X243HD LCD Screen

Offline Just17

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 10694
  • MLUs Forever!
Re: Bootloader Limitation Problem
« Reply #23 on: January 17, 2013, 02:20:19 AM »
Quote
not sure what happened here as when I came to do the unsquash, complaining that directory existed, quickly just added /expand and the process proceeded.

Yes it expects to create the destination directory itself .....  which ensures it does not expand into an existing directory.
MLUs rule the roost!

Linux XPS 3.4.38-pclos1.bfs  64 bit
Intel Core2 Quad CPU Q9450 @ 2.66GHz
4 GB RAM
MCP51 High Def Audio
GeForce GTX 550 Ti
PHILIPS  ‎DVD+-RW DVD8701
‎Logitech ‎BT Mini-Receiver
Afatech DTT

Offline kjpetrie

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 4001
Re: Bootloader Limitation Problem
« Reply #24 on: January 17, 2013, 04:49:54 AM »
This file is in drakxtools-backend, so the way to change it in future ISOs would be to submit an updated version of that package. Would a package request for the change be legitimate?

I have noted the request  ;)
I have a couple of other things to fix in the draktools so I'll add it to the list.

Terry.

I'm already working on it. At the moment there are different packages for 32 and 64 bit and I just need to see whether they can be combined.

Edit: Found the "Requires: lib64xxf86misc1" - naughty Tex! (Presumably before he hit on changing the %{_lib} macro.)

Sent to Dropbox.

« Last Edit: January 17, 2013, 06:46:09 AM by kjpetrie »
-----------
KJP
-----------------------------------------------------------
PClos64 RC1 on Intel D945GCLF2 motherboard (Atom 330), 2GB DDR2 RAM, Maxtor STM325031, HL-DT-ST DVDRAM GSA-H42N, Amilo LSL 3220T monitor. Also Acer 5810TG (with custom kernel) and Asus eeePC 2G surf

Offline wedgetail

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2446
  • Any Bugs in site?
Re: Bootloader Limitation Problem
« Reply #25 on: January 17, 2013, 07:10:10 AM »
kjpetrie
Much appreciated, I will be most enthusiastic checking/testing this as I have suffered a lot just because I ran so many partitions.  So far I am happy with my testing. Only need to test some installs in high numbers, ie /dev/sdc17 and above.

Just17
I think I have returned to the original OS that started my search here, not quite sure as I lost my master menu.lst in a comical accident   ;D
In the following I am following relatively close to your proposed lines.  I am using the same source ISO, KDE32-2012.12 as in the previous tests.

1..  Loop mounting my source ISO (and just checking that I have a livecd.sqfs to work with, yeah I know but I am rather cautious). I have set up a couple of helper directories /za and /zz

Code: [Select]
[root@localhost gert]# mount -o loop  /media/B-18/130108-pclinuxos-kde-2012.12.iso /za
mount: warning: /za seems to be mounted read-only.
[root@localhost gert]# ls -l /za
total 1370030
drwxr-xr-x 3 root root       2048 Dec  7 04:38 boot/
drwxr-xr-x 2 root root       8192 Dec  7 05:08 isolinux/
-rw-r--r-- 1 root root 1402900480 Dec  7 05:08 livecd.sqfs
[root@localhost gert]#

2..  Unsquashing the /za/livecd.sqfs to /home/gert/test-iso/unsquash, this directory did give me the run around. Found that my system can not create a new directory two levels deep, ie I had to help along with first creating the /home/gert/test-iso before I had success with the process.

Code: [Select]
[root@localhost gert]# mkdir /home/gert/test-iso/  
                                  
[root@localhost gert]# unsquashfs -d /home/gert/test-iso/unsquash /za/livecd.sqfs      
Parallel unsquashfs: Using 2 processors                                        
128223 inodes (129153 blocks) to write      
.................
......
..
[root@localhost gert]#

3..  Then I find the /usr/lib/libDrakX/bootloader.pm and edit line 575 counter in question 10 goes to 99

4.. Now squashing the file system again, I direct the result to /zz

Code: [Select]
[root@localhost gert]# mksquashfs /home/gert/test-iso/unsquash  /zz/livecd.sqfs
Parallel mksquashfs: Using 2 processors
Creating 4.0 filesystem on /zz/livecd.sqfs, block size 131072.
[=================================================================/] 144487/144487 100%
Exportable Squashfs 4.0 filesystem, gzip compressed, data block size 131072                      
        compressed data, compressed metadata, compressed fragments, compressed xattrs                            
        duplicates are removed                                                                                      
..........................
..............

[root@localhost gert]#

[root@localhost gert]#  ls -l /zz
total 1773520
-rw-r--r-- 1 root root 1814306816 Jan 18 00:07 livecd.sqfs
[root@localhost gert]#

I see the edited livecd.sqfs has the expected permissions.  All that is needed is to copy the rest of /boot and /isolinux to the /zz and run mkisofs on this. Using root Dolphin and split panes it is easy to drag and drop from /za to /zz.  After ISO generation Then loop mount to check.

Code: [Select]
[root@localhost gert]# mkisofs -o /media/B-18/gert_livecd_image12.iso /zz
I: -input-charset not specified, using utf-8 (detected in locale settings)
  0.56% done, estimate finish Fri Jan 18 00:50:46 2013
..............
..........
 99.68% done, estimate finish Fri Jan 18 00:51:35 2013
Total translation table size: 0
Total rockridge attributes bytes: 0
Total directory bytes: 8192
Path table size(bytes): 50
Max brk space used 1e000
892867 extents written (1743 MB)
[root@localhost gert]#

Code: [Select]
[root@localhost gert]# mount -o loop  /media/B-18/gert_livecd_image12.iso /here
mount: warning: /here seems to be mounted read-only.
[root@localhost gert]# ls -l /here
total 1771790
dr-xr-xr-x 1 root root       2048 Dec  7 04:38 boot/
dr-xr-xr-x 1 root root       4096 Dec  7 05:08 isolinux/
-r-xr-xr-x 1 root root 1814306816 Jan 18 00:07 livecd.sqf*
[root@localhost gert]#

Must admit I did not expect this, the problem is back, this ISO will crash the liveHDD generator.

I will have to go back and see where I deviated from the test in the other OS and I will have to test mkisofs with -r option again to confirm this is a fix  >:(  , but ZZZzz...

Have not quite forgotten the ISO may not be bootable either, but later to see about that.   ;D
« Last Edit: January 17, 2013, 07:15:52 AM by wedgetail »
32 bit: KDE (older) & various KDE-mini, ASUSTek P5P41D Rev X.0x, BIOS AMI0207 07/21/2009, "Pentium(R) Dual-Core CPU E5300 @ 2.60GHz", nVidia GeForce 9600 GT, 2x1GB Seagate Technology 1000528AS HDD
TV CompuPro VideoMate Vista E700 (not working in Linux), Acer X243HD LCD Screen

Offline Just17

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 10694
  • MLUs Forever!
Re: Bootloader Limitation Problem
« Reply #26 on: January 17, 2013, 07:27:21 AM »
I wonder if there is some conflict due to having the original ISO mounted during the mkiso operation ....  seems far-fetched .....  but ....

The only differences I see presently in what you did and what I did are the paths used and also I copied all the contents of the orig ISO to a directory and then unmounted the ISO.

Oh yes ......  I used the Minime ISO to make things go a bit quicker  ;)

MLUs rule the roost!

Linux XPS 3.4.38-pclos1.bfs  64 bit
Intel Core2 Quad CPU Q9450 @ 2.66GHz
4 GB RAM
MCP51 High Def Audio
GeForce GTX 550 Ti
PHILIPS  ‎DVD+-RW DVD8701
‎Logitech ‎BT Mini-Receiver
Afatech DTT

Offline wedgetail

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2446
  • Any Bugs in site?
Re: Bootloader Limitation Problem
« Reply #27 on: January 17, 2013, 07:32:43 AM »
Just17
Good point about the mounted source ISO, easy to check just before I umount -l on the loop mount.
No that made no difference.

I ran another with option -r

Code: [Select]
[root@localhost gert]# mkisofs -o /media/B-18/gert_livecd_image16.iso -r   /zz


Code: [Select]
[root@localhost gert]# umount -l /here
[root@localhost gert]# mount -o loop  /media/B-18/gert_livecd_image16.iso /here
mount: warning: /here seems to be mounted read-only.

[root@localhost gert]# ls -l /here
total 1771794
dr-xr-xr-x 3 root root       2048 Dec  7 04:38 boot/
dr-xr-xr-x 2 root root       8192 Dec  7 05:08 isolinux/
-r--r--r-- 1 root root 1814306816 Jan 18 00:07 livecd.sqfs
[root@localhost gert]#

Now the livecd.sqfs file extension looks right, but I no nearer an explanation.   8)

« Last Edit: January 17, 2013, 07:46:24 AM by wedgetail »
32 bit: KDE (older) & various KDE-mini, ASUSTek P5P41D Rev X.0x, BIOS AMI0207 07/21/2009, "Pentium(R) Dual-Core CPU E5300 @ 2.60GHz", nVidia GeForce 9600 GT, 2x1GB Seagate Technology 1000528AS HDD
TV CompuPro VideoMate Vista E700 (not working in Linux), Acer X243HD LCD Screen

Offline wedgetail

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2446
  • Any Bugs in site?
Re: Bootloader Limitation Problem
« Reply #28 on: January 18, 2013, 02:40:13 AM »
Just17
Problematic OS?   Another defeat coming up in the following, where I try to get even closer to identical run to you.
first make the source ISO available for reading by loop mounting to /za

Code: [Select]
[root@localhost /]# mount -o loop  /media/B-18/130108-pclinuxos-kde-2012.12.iso /za
mount: warning: /za seems to be mounted read-only.
[root@localhost /]#

Root Dolphin used to do the ISO copy from /za/ to /home/gert/test-iso

Code: [Select]
[root@localhost /]# unsquashfs -d /home/gert/test-iso/unsquash livecd.sqfs
Could not open livecd.sqfs, because No such file or directory
[root@localhost /]#

aaaaaarrrrgggghh forgot to cd to /home/gert/test-iso, (look at using absolute paths every time to avoid this)

Code: [Select]
[root@localhost test-iso]# unsquashfs -d /home/gert/test-iso/unsquash livecd.sqfs
Parallel unsquashfs: Using 2 processors
128223 inodes (129153 blocks) to write
..................
.........
[root@localhost test-iso]#

Skipping a few code steps but checked the file system is in place for editing. Continued doing the edit, using Dolphin/KWrite and then re-squash.
Looking harder at the following statement I realised that I ought to have deleted the "old livecd.sqfs" but having read manual on mksquashfs I decided to do an overwrite, soon found out that this needs -noappend.
I have of course cut out a lot of data in most of these long runs.   :)

Code: [Select]
[root@localhost test-iso]# mksquashfs /home/gert/test-iso/unsquash  livecd.sqfs -noappend
Parallel mksquashfs: Using 2 processors
...................
.........
[root@localhost test-iso]#

At this point the new livecd.sqfs should be in place in /home/gert/test-iso/, I very nearly forgot to move the directory full of files /home/gert.test-iso/unsquash, but it is removed.

In the following I really made a bad choice of name for the ISO, it resembles far too close the directory it comes from, better choice next time.

Code: [Select]
[root@localhost test-iso]# mkisofs -o /home/gert/test.iso /home/gert/test-iso/
I: -input-charset not specified, using utf-8 (detected in locale settings)
  0.56% done, estimate finish Fri Jan 18 19:43:49 2013
...................
....
[root@localhost test-iso]#

Need to look inside the iso, so another loop mount

Code: [Select]
[root@localhost test-iso]# mount -o loop /home/gert/test.iso /here
mount: warning: /here seems to be mounted read-only.
[root@localhost test-iso]#

List the content of the ISO.

Code: [Select]
[root@localhost test-iso]# ls -l /here
total 1771790
dr-xr-xr-x 1 root root       2048 Dec  7 04:38 boot/
dr-xr-xr-x 1 root root       4096 Dec  7 05:08 isolinux/
-r-xr-xr-x 1 root root 1814306816 Jan 18 18:05 livecd.sqf*  <<< ------ problem
[root@localhost test-iso]#


I really did not expect this failure again, well so I test out the option -r again, sorry about the name choice again. Needs careful reading.
 
Code: [Select]
[root@localhost test-iso]#  mkisofs -o /home/gert/test-r_option.iso -r home/gert/test-iso

Code: [Select]
[root@localhost test-iso]# mount -o loop /home/gert/test-r_option.iso /here
mount: warning: /here seems to be mounted read-only.
[root@localhost test-iso]#

[root@localhost test-iso]# ls -l /here
total 1771794
dr-xr-xr-x 3 root root       2048 Dec  7 04:38 boot/
dr-xr-xr-x 2 root root       8192 Dec  7 05:08 isolinux/
-r--r--r-- 1 root root 1814306816 Jan 18 18:05 livecd.sqfs  <<< ------ option -r to the rescue
[root@localhost test-iso]#

I think I will look at sorting out the last bit of my mangled boot menu/process instead.  ;D
32 bit: KDE (older) & various KDE-mini, ASUSTek P5P41D Rev X.0x, BIOS AMI0207 07/21/2009, "Pentium(R) Dual-Core CPU E5300 @ 2.60GHz", nVidia GeForce 9600 GT, 2x1GB Seagate Technology 1000528AS HDD
TV CompuPro VideoMate Vista E700 (not working in Linux), Acer X243HD LCD Screen

Offline Just17

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 10694
  • MLUs Forever!
Re: Bootloader Limitation Problem
« Reply #29 on: January 18, 2013, 02:51:28 AM »
When you edited the bootloader.pm file, did it generate a backup of that file called bootloader.pm~ ?

If yes, did you delete it before squashing?

....  just wondering ...

Strange I did not need the -r or -R options.

MLUs rule the roost!

Linux XPS 3.4.38-pclos1.bfs  64 bit
Intel Core2 Quad CPU Q9450 @ 2.66GHz
4 GB RAM
MCP51 High Def Audio
GeForce GTX 550 Ti
PHILIPS  ‎DVD+-RW DVD8701
‎Logitech ‎BT Mini-Receiver
Afatech DTT