Non Booting PCLinuxOS liveCD

[wedgetail]

Old-Polack
Yes, the bootloader.pm is not the real problem, this is just something that will happen when you have high partition count > 10.  Just proved it to myself, and when I followed the konsole record I reconised this is not what I was after.

For my clarification:
1..  Do I understand that the USB stick works fine when the partition count is 10 or under ( 1TB drive turned off bringing the count within range?)
2.. The big drive is USB

I am off to my notes again 

[Just17]

O-P

do you recall a few reports from users of failing to get a proper Grub prompt .......  occurring infrequently over a long time period?

As I recall, the answer (provided by Tex IIRC) was to enter

LiveCD      (case sensitive)

at the prompt. {I also seem to recall a tip to use  livecd=livecd but that is probably memory playing tricks with me}

Found the following

http://www.pclinuxos.com/forum/index.php/topic,71515.msg587445.html#msg587445
http://www.pclinuxos.com/forum/index.php/topic,86801.msg722035.html#msg722035


Only reason I raise this is that if your problem was similar/same then it is not something new ......  just something very few have met.

I found no explanation why the "LiveCD" worked  ....  the fact that it is case sensitive might make it easier to locate?

[Old-Polack]

Old-Polack
Yes, the bootloader.pm is not the real problem, this is just something that will happen when you have high partition count > 10.  Just proved it to myself, and when I followed the konsole record I reconised this is not what I was after.

For my clarification:
1..  Do I understand that the USB stick works fine when the partition count is 10 or under ( 1TB drive turned off bringing the count within range?)
2.. The big drive is USB

I am off to my notes again 

When the seeking is done from a liveHDD on /dev/sdb13 (the 1 TB drive) the <whatever>.sqfs file is found and boots properly, so the partition limit of 10 does not apply.

I think the problem with that drive specifically is that it ws partitioned with two different versions of fdisk, and there is some conflict in how the partitions are seen at a low level. I'm planning to wipe the drive and repartition it with the newest version of fdisk only, to see if that fixes things.

For the sake of argument, I added another 2 TB drive, so now the 1 TB has become /dev/sda, and all of the drives, other than the newest 2 TB drive, have more than 10 partitions.

[root@fatman ~]# fdisk -l

Disk /dev/sdb: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x2db1883a

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              63      208844      104391   83  Linux
/dev/sdb2          208845    12225464     6008310   82  Linux swap / Solaris
/dev/sdb3        12225465    72244304    30009420   83  Linux
/dev/sdb4        72244305  1465144064   696449880    5  Extended
/dev/sdb5        72244368   272253554   100004593+  83  Linux
/dev/sdb6       272253618   670713749   199230066   83  Linux
/dev/sdb7       670713813   731278799    30282493+  83  Linux
/dev/sdb8       731278863   811378889    40050013+  83  Linux
/dev/sdb9       811378953  1045767239   117194143+  83  Linux
/dev/sdb10     1045767303  1280155589   117194143+  83  Linux
/dev/sdb11     1280155653  1465144064    92494206   83  Linux

Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x18eee7ae

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1            2048     2099199     1048576   83  Linux
/dev/sdc2         2099200    18876415     8388608   82  Linux swap / Solaris
/dev/sdc3        18876416    81790975    31457280   83  Linux
/dev/sdc4        81790976  3907029167  1912619096    5  Extended
/dev/sdc5        81793024   176164863    47185920   83  Linux
/dev/sdc6       176166912   281024511    52428800   83  Linux
/dev/sdc7       281026560   385884159    52428800   83  Linux
/dev/sdc8       385886208   805316607   209715200   83  Linux
/dev/sdc9       805318656   857747455    26214400   83  Linux
/dev/sdc10      857749504   910178303    26214400   83  Linux
/dev/sdc11      910180352   962609151    26214400   83  Linux
/dev/sdc12      962611200  1172326399   104857600   83  Linux
/dev/sdc13     1172328448  1382043647   104857600   83  Linux
/dev/sdc14     1382045696  1803573247   210763776   83  Linux

Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xbbcb054b

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1            2048     4196351     2097152   83  Linux
/dev/sdd2         4196352  2101348351  1048576000   83  Linux

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0000d21c

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              63      626534      313236   83  Linux
/dev/sda2          626535    16820054     8096760   82  Linux swap / Solaris
/dev/sda3        16820055   114495254    48837600   83  Linux
/dev/sda4       114495255  1953520064   919512405    5  Extended
/dev/sda5       114495318   329332499   107418591   83  Linux
/dev/sda6       329332563   534434354   102550896   83  Linux
/dev/sda7       534434418   596943269    31254426   83  Linux
/dev/sda8       596943333   659452184    31254426   83  Linux
/dev/sda9       659452248   721961099    31254426   83  Linux
/dev/sda10      721961163   784470014    31254426   83  Linux
/dev/sda11      784470078   994198589   104864256   83  Linux
/dev/sda12      994198653  1623368249   314584798+  83  Linux
/dev/sda13     1623368313  1685893229    31262458+  83  Linux
/dev/sda14     1685893293  1749366044    31736376   83  Linux
/dev/sda15     1749366108  1816485614    33559753+  83  Linux
/dev/sda16     1816487663  1889887982    36700160   83  Linux
/dev/sda17     1889892080  1953520064    31813992+  83  Linux

Don't ask me why the drives read out of order, with /dev/sda listed last, as I haven't a clue. 

[Old-Polack]

O-P

do you recall a few reports from users of failing to get a proper Grub prompt .......  occurring infrequently over a long time period?

As I recall, the answer (provided by Tex IIRC) was to enter

LiveCD      (case sensitive)

at the prompt. {I also seem to recall a tip to use  livecd=livecd but that is probably memory playing tricks with me}

Found the following

http://www.pclinuxos.com/forum/index.php/topic,71515.msg587445.html#msg587445
http://www.pclinuxos.com/forum/index.php/topic,86801.msg722035.html#msg722035


Only reason I raise this is that if your problem was similar/same then it is not something new ......  just something very few have met.

I found no explanation why the "LiveCD" worked  ....  the fact that it is case sensitive might make it easier to locate?

I remember the post from Tex. I also noted that the error message has DEFAULT and UI in upper case letters, and the isolinux.cfg has those items in lower case letters, so I'm also wondering if that hasn't something to do with it.

Error message:

ISOLINUX 3.85 2010-02-20 ETCD Copyright (C) 1994-2010 H. Peter Anvin et al
No DEFAULT or UI configuration directive found.
Boot:

Top headers from isolinux.cfg:

default LiveCD
prompt  1
timeout 90
ui gfxboot.com bootlogo

Now I have to find that burned disk, and see if Boot: will accept either LiveCD or gfxboot.com as a usable argument.

[wedgetail]

Old-Polack


Your lead i much more promising than what I have found but in case it fails I have another shot.  

I happened to be looking in isolinux.bin relevant section, this is just to confirm where the message comes from (this is not my shot )

Code: [Select]

00003120   6F 74 69 6E  67 2C 20 61  6E 64 20 49  20 77 69 6C  6C 20 74 61  6B 65 20 79  oting, and I will take y
00003138   6F 75 72 20  77 6F 72 64  20 66 6F 72  20 69 74 2E  0D 0A 00 4E  6F 20 44 45  our word for it....No DE
00003150   46 41 55 4C  54 20 6F 72  20 55 49 20  63 6F 6E 66  69 67 75 72  61 74 69 6F  FAULT or UI configuratio
00003168   6E 20 64 69  72 65 63 74  69 76 65 20  66 6F 75 6E  64 21 0D 0A  00 62 6F 6F  n directive found!...boo
00003180   74 3A 20 00  08 20 08 00  49 6E 76 61  6C 69 64 20  69 6D 61 67  65 20 74 79  t: .. ..Invalid image ty
00003198   70 65 20 66  6F 72 20 74  68 69 73 20  6D 65 64 69  61 20 74 79  70 65 21 0D  pe for this media type!.
And now I have to find out why the limit apply to my system, I thought it was over and sorted 

[Old-Polack]

Old-Polack


Your lead i much more promising than what I have found but in case it fails I have another shot.  

I happened to be looking in isolinux.bin relevant section, this is just to confirm where the message comes from (this is not my shot )

Code: [Select]

00003120   6F 74 69 6E  67 2C 20 61  6E 64 20 49  20 77 69 6C  6C 20 74 61  6B 65 20 79  oting, and I will take y
00003138   6F 75 72 20  77 6F 72 64  20 66 6F 72  20 69 74 2E  0D 0A 00 4E  6F 20 44 45  our word for it....No DE
00003150   46 41 55 4C  54 20 6F 72  20 55 49 20  63 6F 6E 66  69 67 75 72  61 74 69 6F  FAULT or UI configuratio
00003168   6E 20 64 69  72 65 63 74  69 76 65 20  66 6F 75 6E  64 21 0D 0A  00 62 6F 6F  n directive found!...boo
00003180   74 3A 20 00  08 20 08 00  49 6E 76 61  6C 69 64 20  69 6D 61 67  65 20 74 79  t: .. ..Invalid image ty
00003198   70 65 20 66  6F 72 20 74  68 69 73 20  6D 65 64 69  61 20 74 79  70 65 21 0D  pe for this media type!.
And now I have to find out why the limit apply to my system, I thought it was over and sorted 

I just tried a reboot with the burned CD, tried LiveCD at the Boot: prompt and got an error couldn't find the kernel. Tried gfxboot.com as the command and got a gfxboot: prompt, then the same error. Typed the boot stanza starting with vmlinuz ... and it booted like before.

Did a reboot with the USB stick, and it got as far as gfxboot: went back to Boot: went to gfxboot: again and continued to loop between those two. Typed the stanza again, and it too booted. Turned off the power to the 1 TB external drive, rebooted and got the normal boot screen. Hit enter, and got the normal boot process.

So, we know there's definitely something funny with the 1 TB drive, as it is now. We also know the USB stick works without that drive present, and it makes no difference to the burned disk whether the 1 TB drive is there or not. I need to type the stanza manually either way, to have the burned disk boot.

That was fun, but didn't get a cigar.

[wedgetail]

Old-Polack
Ohhh, I was sure you were onto something.  
I read on the net that somebody suggested editing out ui did you see that?  A desperate suggestion.  
Errh, I did see you probably have done exactly that by supplying gfxboot.com, my understanding was this was edited out of the disk.  Will see if I kept a note of the site.

[Just17]

I came across this interesting tidbit

Error:

SYSLINUX 4.04 CHS 2011-04-18 Copyright (C) 1994-2011 H. Peter Anvin et al
ERROR: No configuration file found
No DEFAULT or UI configuration directive found!
boot:

Suggestion:

NOTE: Syslinux also has a -stupid mode.
-s, --stupid
Install a "safe, slow and stupid" version of SYSLINUX . This version may work on some very buggy BIOSes on which SYSLINUX would otherwise fail.

Yes I know this reports Syslinux and not Isolinux in the error .....


Some have reported the same error when using LiveUSB .......  and this suggestion seemed to work for some .....

On the USB key, rename the isolinux folder to syslinux.

In the same folder, rename the isolinux.bin and isolinux.cfg files to syslinux.bin and syslinux.cfg, respectively.

Now, try booting with the USB drive again.

As a generality, it appears to be a syslinux/isolinux problem with some hardware.
There does not appear to be anything I can find that gives a solution for all cases.

One might come to the conclusion that the problem lies with syslinux/isolinux and not with any particular implementation of either by distro releases.

[Old-Polack]

I came across this interesting tidbit

Error:

SYSLINUX 4.04 CHS 2011-04-18 Copyright (C) 1994-2011 H. Peter Anvin et al
ERROR: No configuration file found
No DEFAULT or UI configuration directive found!
boot:

Suggestion:

NOTE: Syslinux also has a -stupid mode.
-s, --stupid
Install a "safe, slow and stupid" version of SYSLINUX . This version may work on some very buggy BIOSes on which SYSLINUX would otherwise fail.

Yes I know this reports Syslinux and not Isolinux in the error .....


Some have reported the same error when using LiveUSB .......  and this suggestion seemed to work for some .....

On the USB key, rename the isolinux folder to syslinux.

In the same folder, rename the isolinux.bin and isolinux.cfg files to syslinux.bin and syslinux.cfg, respectively.

Now, try booting with the USB drive again.

As a generality, it appears to be a syslinux/isolinux problem with some hardware.
There does not appear to be anything I can find that gives a solution for all cases.

One might come to the conclusion that the problem lies with syslinux/isolinux and not with any particular implementation of either by distro releases.

I read something similar, that said the solution would come with syslinux 4.02, which I assume was the addition of the -s --stupid mode. However there are also file name changes involved in the upgrades, and some functional changes within some files, so the end result of an upgrade would be a forced editing of mylivecd as well. A bit of a sticky wicket, eh wot?

[Just17]

aye ......  nothing simple