Syslinux - Jan 2014 - USB boot problems on Gigabyte GA-M55Plus-S3G

In message <52D90648.4010900 at mattiasschlenker.de>, 
Mattias Schlenker <ms at mattiasschlenker.de> wrote:
>I would be personally interested in the following experiment:
>
> 1. Download this LessLinux test build:
>   
http://download.lesslinux.org/testing/lesslinux-search-and-rescue/lesslinux
>-search-and-rescue-uluru-20140107-193740.iso
> 2. dd it to the 8GB thumb that formerly failed
> 3. Boot it
> 4. Shut down
> 5. Boot again
I am downloading this file now, but it is rather large, and will take
awhile.  As soon as I have it I will perform the above procedure and
then report results.


Regards,
rfg

In message <49973.1389992217 at server1.tristatelogic.com>, I wrote:
>
>In message <52D90648.4010900 at mattiasschlenker.de>, 
>Mattias Schlenker <ms at mattiasschlenker.de> wrote:
>
>>I would be personally interested in the following experiment:
>>
>> 1. Download this LessLinux test build:
>>   
http://download.lesslinux.org/testing/lesslinux-search-and-rescue/lesslinu
>x
>>-search-and-rescue-uluru-20140107-193740.iso
>> 2. dd it to the 8GB thumb that formerly failed
>> 3. Boot it
>> 4. Shut down
>> 5. Boot again
>
>I am downloading this file now, but it is rather large, and will take
>awhile.  As soon as I have it I will perform the above procedure and
>then report results.

I have performed the above test, both with my 8GB Patroit XT and also with
one of my 2GB Sandisk Cruzer Blades.  (I can't remember having reporting
any booting problems with the 8GB Patroit XT so far, which is why I decided
to do the test also with one of the 2GB Sandisk Cruzer Blades, because I
*have* reported problems with those.)

 The results were the same in both cases.

In both cases, LessLinux Search & Rescue booted up and began a timed
10 second countdown, which I allowed it to finish in each case.  After
that, it started to do something... I'm not even sure what, exactly...
and eventually froze up while displaying a progress bar, showing about 50%
completion (of something) and the phrase "Starting dhcpcd".

For each of the two USB sticks I then powered the system off and rebooted
again.

Results were then identical to the first boot from each of the two sticks.


Regards,
rfg

Am 18.01.2014 04:30, schrieb Ronald F. Guilmette:
> The results were the same in both cases. In both cases, LessLinux 
> Search & Rescue booted up and began a timed 10 second countdown, which 
> I allowed it to finish in each case. After that, it started to do 
> something... I'm not even sure what, exactly... and eventually froze 
> up while displaying a progress bar, showing about 50% completion (of 
> something) and the phrase "Starting dhcpcd".
It is an unstable build. DHCPCD got updated and might behave 
differently. Its should continue after a very long time (five minutes or 
so). If you are interested in booting LessLinux, press Tab when the menu 
appears and add "dhcpcd" to the skipservices variable. But that's 
off-topic here.
> For each of the two USB sticks I then powered the system off and 
> rebooted again. Results were then identical to the first boot from 
> each of the two sticks.
My intention was to find out, if this very special partitioning boots 
correctly. Upon first boot you started an isohybrid thumbdrive with the 
isohdpfx.bin boot record, the ISO was prepared with Thomas' xorriso. 
After the first boot the drive gets partitioned to seven or eight 
partitions with a GPT partition table with a legacy boot partition, an 
UEFI boot partition and compat MBR. The boot sector in this case is 
gptmbr.bin.

So far this setup really works best with legacy BIOS and modern UEFI. It 
sometimes fails miserably with old broken EFI implementations.

To cut a log story short, we probably should write some advices for best 
practices of creating bootable media. I got five:

 1. Never ever rely on partitioning or filesystems that a already on the
    user's thumb drives. These might use odd CHS geometries or drives
    may be flashed with a broken FS - partition and format using well
    proven tools
 2. If your system has to be bootable from USB and optical media try to
    deliver isohybrid images. Thomas and Mattias might help you with
    working around typical bugs in BIOS and UEFI implementations
 3. When converting a thumb drive to read only ISO9660 does not seem
    suitable, you might go with LessLinux' solution of converting the
    isohybrid drive to a partitioned layout with a large FAT32 partition
    at the start - this way even Windows can write to the drive. If
    windows doesn't matter just add one partition in the free space
    after the dd'ed ISO
 4. Check the media upon first boot. Too many too cheap thumb drives
    flip too many bits after a few dozen full writes.
 5. Move away from MBR/DOS, goto GPT, you'll be rewarded with reliable
    boot both on UEFI and on BIOS. You'll just break compatibility with
    Windows XP, but this is dead after April 8th anyway.

Regards,
Mattias

-- -
Mattias Schlenker - Redaktion + EDV-Beratung + Linux-CD/DVD-Konzepte
August-Bebel-Str. 74 - 04275 LEIPZIG - GERMANY

Telefon (VoIP "ueberall"), geschaeftlich: +49 341 39290767
Telefon (Festnetz), privat und Fax:       +49 341 30393578
Mobil:                                    +49 163  6953657
Mobil (SIM in Testgeraeten):              +49 1578 3499550

Bitte fuer geschaeftliche Telefonate vorzugsweise die VoIP-Telefonnummer
+49 341 39290767 verwenden, da ich diese aufs Mobiltelefon routen kann!