Missing Operating System?!?

hack-wizard · **Joined:** Thu Jul 14, 2011 7:36 pm **Posts:** 8

I decided that I was going to update the AV files for UBCV V5.03, then install it to my flash drive (via opensuse linux): so I followed the instructions online and in the readme to the letter, with seemingly no issues at all ... and what do I get when I try to boot it on my Dell Vostro 1520, after explicitly instructing it to do so from the BIOS boot menu? A stupid little "Missing Operating System" message, and then it tries to boot from the network!

Once again, I followed *all* the steps *to the letter* and checked what I was doing was right thrice! I even made sure to use FAT32, as the drive in question is 4 GB in size.

Any ideas as to why I can't boot from it, and how this might be fixed?

ady · **Joined:** Sat May 08, 2010 5:26 am **Posts:** 654

Could you try the latest development release of UBCD at http://www.ultimatebootcd.com/forums/viewforum.php?f=7?

There might be more than one "readme" at
ubcd51b1 -> ubcd -> tools -> linux -> ubcd2usb ,
or at
ubcd51b1 -> ubcd -> tools -> linux

so you may find instructions that may not be fully up-to-date.

Please first try it with no customizations (no AV updates for example) so to be sure it works "as-is". If it works, then you can perform additional modifications and test them.

Please report back.

hack-wizard · **Joined:** Thu Jul 14, 2011 7:36 pm **Posts:** 8

ady wrote:

Could you try the latest development release of UBCD at http://www.ultimatebootcd.com/forums/viewforum.php?f=7?

There might be more than one "readme" at
ubcd51b1 -> ubcd -> tools -> linux -> ubcd2usb ,
or at
ubcd51b1 -> ubcd -> tools -> linux

so you may find instructions that may not be fully up-to-date.

Please first try it with no customizations (no AV updates for example) so to be sure it works "as-is". If it works, then you can perform additional modifications and test them.

Please report back.

Thanks for the advice, I'll try that after I get home. Also, I've been thinking … should the syslinux installation executable possibly be ran *before* I move the rest of the files onto the drive, just after I dd the mbr to it? If so, then I think that may be the issue, as the instructions indicated that it should be ran after moving all the files over.

I've had to reinstall stage one of grub after repartitioning my laptop's hard drive, due to it basically using a hard-coded pointer for the address of stage 2 which was no longer valid… so I thought perhaps syslinux might be similar.

ady · **Joined:** Sat May 08, 2010 5:26 am **Posts:** 654

hack-wizard wrote:

… so I thought perhaps syslinux might be similar.

I don't think that's the problem, no. Please carefully read the updated instructions in the "ubcd2usb -> readme.txt" file (it has been updated since ubcd503, together with the included version of syslinux).

Please report back, whichever the (positive/negative) result.

hack-wizard · **Joined:** Thu Jul 14, 2011 7:36 pm **Posts:** 8

Um ... the beta doesn't seem to contain Avira Antivir SystemRescue ... which was one of the things I really wanted to use. May I ask why this is?

Unless there is a version of the beta with this in it, I'm going to have to use the stable version ... so please let me know, though I will try it with the instructions from the beta now ...

EDIT: Also, I checked, and the instructions included have *not* changed one bit, plus the stable version still won't boot even without customization. Seriously, how can you call something stable if it won't even boot up.

ady · **Joined:** Sat May 08, 2010 5:26 am **Posts:** 654

Let's separate the issues.

hack-wizard wrote:

Also, I checked, and the instructions included have *not* changed one bit.

ubcd51b1 -> ubcd -> tools -> linux -> ubcd2usb -> readme.txt

contains the following line:

Code:

4. Type a, then 1, to make the first primary partition active or bootable.

which wasn't there in ubcd503.

The included version of syslinux (among other updates) might be key to make it work from UFD. So you certainly should test the latest beta as suggested.

Quote:

Um ... the beta doesn't seem to contain Avira Antivir SystemRescue ... which was one of the things I really wanted to use. May I ask why this is?

The size of the latest Avira is too big to add it in the original download. You still can add it by customization (search the forum, there are several topics about it). In addition, Avira Rescue includes some utilities, which are not needed when Avira is included in UBCD.

There are simple solutions to merge UBCD with several different tools, including Avira Rescue (web search for SARDU latest beta version, just to give one example).

Quote:

Unless there is a version of the beta with this in it, I'm going to have to use the stable version ... so please let me know, though I will try it with the instructions from the beta now ...

This is the main issue of this topic: to make UBCD work from your UFD.

So, as suggested, try the latest UBCD beta "as-is" first. If it doesn't work "as-is", then we need to solve that issue first. Only then we can talk about customizations or merging it with additional tools.

Whichever the results, please report feedback.

hack-wizard · **Joined:** Thu Jul 14, 2011 7:36 pm **Posts:** 8

ady wrote:

Let's separate the issues.

hack-wizard wrote:

Also, I checked, and the instructions included have *not* changed one bit.

ubcd51b1 -> ubcd -> tools -> linux -> ubcd2usb -> readme.txt

contains the following line:

Code:

4. Type a, then 1, to make the first primary partition active or bootable.

which wasn't there in ubcd503.

The included version of syslinux (among other updates) might be key to make it work from UFD. So you certainly should test the latest beta as suggested.

Quote:

Um ... the beta doesn't seem to contain Avira Antivir SystemRescue ... which was one of the things I really wanted to use. May I ask why this is?

The size of the latest Avira is too big to add it in the original download. You still can add it by customization (search the forum, there are several topics about it). In addition, Avira Rescue includes some utilities, which are not needed when Avira is included in UBCD.

There are simple solutions to merge UBCD with several different tools, including Avira Rescue (web search for SARDU latest beta version, just to give one example).

Quote:

Unless there is a version of the beta with this in it, I'm going to have to use the stable version ... so please let me know, though I will try it with the instructions from the beta now ...

This is the main issue of this topic: to make UBCD work from your UFD.

So, as suggested, try the latest UBCD beta "as-is" first. If it doesn't work "as-is", then we need to solve that issue first. Only then we can talk about customizations or merging it with additional tools.

Whichever the results, please report feedback.

Ok ... more strangeness when I try exactly what you suggested, along with adding the boot flag using fdisk.

For instance, I get the following message when I attempt to install syslinux:

Code:

jwesleycooper@linux-twom:~> sudo ./ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux -s -d /boot/syslinux /dev/sdb1
root's password:
./ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux: no previous syslinux boot sector found

And a lovely little bios message when instructing it to boot saying "This is not a bootable floppy" ...

Now, I've made bootable flash drives before using unetbootin and ran them on this computer, so I know it does work with them ... any idea why this one isn't?

Icecube · **Joined:** Fri Jan 11, 2008 2:52 pm **Posts:** 1277

Can you run Boot Info Script and post the output?
http://bootinfoscript.sourceforge.net/

ady · **Joined:** Sat May 08, 2010 5:26 am **Posts:** 654

Icecube wrote:

Can you run Boot Info Script and post the output?
http://bootinfoscript.sourceforge.net/

I'm guessing that the OP should run it under his/her Linux, with the UFD connected and mounted?

Could the problem be related to how the UFD is identified by the BIOS (USB-FDD / USB-ZIP / USB-HDD...)?

hack-wizard · **Joined:** Thu Jul 14, 2011 7:36 pm **Posts:** 8

Code:

jwesleycooper@linux-twom:~/boot_info_script060> cat RESULTS.txt 
                  Boot Info Script 0.60    from 17 May 2011


============================= Boot Info Summary: ===============================

 => No known boot loader is installed in the MBR of /dev/sda.
 => Syslinux MBR (4.04 and higher) is installed in the MBR of /dev/sdb.

sda1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  Dell Utility: FAT16
    Boot sector info:   No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        /DELLBIO.BIN /DELLRMK.BIN /COMMAND.COM

sda2: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info:  
    Operating System:  
    Boot files:        

sda3: __________________________________________________________________________

    File system:       Extended Partition
    Boot sector type:  Grub Legacy
    Boot sector info:   Grub Legacy (v0.97) is installed in the boot sector 
                       of sda3 and looks at sector 164094215 of the same hard 
                       drive for the stage2 file.  A stage2 file is at this 
                       location on /dev/sda.  Stage2 looks on partition #6 
                       for /boot/grub/menu.lst.

sda5: __________________________________________________________________________

    File system:       swap
    Boot sector type:  -
    Boot sector info:  

sda6: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info:  
    Operating System:  Welcome to openSUSE 11.4 
                       "Celadon" - Kernel ().
    Boot files:        /boot/grub/menu.lst /etc/fstab

sda7: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info:  
    Operating System:  
    Boot files:        

sdb1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  FAT32
    Boot sector info:   According to the info in the boot sector, sdb1 starts 
                       at sector 0. But according to the info from fdisk, 
                       sdb1 starts at sector 2048.
    Operating System:  
    Boot files:        /boot/grub/menu.lst /boot/syslinux/syslinux.cfg 
                       /boot/syslinux/ldlinux.sys

============================ Drive/Partition Info: =============================

Drive: sda _____________________________________________________________________

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sda1                  63        80,324        80,262  de Dell Utility
/dev/sda2              81,920   154,898,431   154,816,512  83 Linux
/dev/sda3    *    154,900,324   312,576,704   157,676,381   f W95 Extended (LBA)
/dev/sda5         154,900,325   159,107,760     4,207,436  82 Linux swap / Solaris
/dev/sda6         159,107,823   201,053,474    41,945,652  83 Linux
/dev/sda7         201,053,538   312,576,704   111,523,167  83 Linux


Drive: sdb _____________________________________________________________________

Disk /dev/sdb: 4007 MB, 4007624704 bytes
4 heads, 8 sectors/track, 244606 cylinders, total 7827392 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sdb1    *          2,048     7,827,391     7,825,344   c W95 FAT32 (LBA)


"blkid" output: ________________________________________________________________

Device           UUID                                   TYPE       LABEL

/dev/sda1        3030-3030                              vfat       DellUtility
/dev/sda2        5f87ad87-3a67-4979-a28d-9398ec4dd7ad   ext4       
/dev/sda5        863094eb-8354-4616-b512-244796f3c3e0   swap       
/dev/sda6        15b5b4e5-e9fe-46d6-9424-2b2e8eaf3faf   ext4       
/dev/sda7        5af4d571-50f7-4121-a129-589f9e0a7e87   ext4       
/dev/sdb1        FC0F-1206                              vfat       

================================ Mount points: =================================

Device           Mount_Point              Type       Options

/dev/sda2        /home/jwesleycooper/xtendedfs ext4       (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/sda6        /                        ext4       (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/sda7        /home                    ext4       (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/sdb1        /media/FC0F-1206         vfat       (rw,nosuid,nodev,relatime,uid=1000,gid=100,fmask=0022,dmask=0077,codepage=cp437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,errors=remount-ro,uhelper=udisks)


=========================== sda6/boot/grub/menu.lst: ===========================

--------------------------------------------------------------------------------
# Modified by YaST2. Last modification on Sun May  1 10:16:58 MST 2011
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader

default 0
timeout 8
gfxmenu (hd0,5)/boot/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 11.4 - 2.6.37.6-0.5
    root (hd0,5)
    kernel /boot/vmlinuz-2.6.37.6-0.5-desktop root=/dev/disk/by-id/ata-WDC_WD1600BEVT-75ZCT2_WD-WXC409A36789-part6 resume=/dev/disk/by-id/ata-WDC_WD1600BEVT-75ZCT2_WD-WXC409A36789-part5 splash=silent quiet i915.powersave=0 showopts vga=0x317
    initrd /boot/initrd-2.6.37.6-0.5-desktop

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.4 - 2.6.37.6-0.5
    root (hd0,5)
    kernel /boot/vmlinuz-2.6.37.6-0.5-desktop root=/dev/disk/by-id/ata-WDC_WD1600BEVT-75ZCT2_WD-WXC409A36789-part6 showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x317
    initrd /boot/initrd-2.6.37.6-0.5-desktop
--------------------------------------------------------------------------------

=============================== sda6/etc/fstab: ================================

--------------------------------------------------------------------------------
/dev/disk/by-id/ata-WDC_WD1600BEVT-75ZCT2_WD-WXC409A36789-part5 swap                 swap       defaults              0 0
/dev/disk/by-id/ata-WDC_WD1600BEVT-75ZCT2_WD-WXC409A36789-part6 /                    ext4       acl,user_xattr        1 1
/dev/disk/by-id/ata-WDC_WD1600BEVT-75ZCT2_WD-WXC409A36789-part7 /home                ext4       acl,user_xattr        1 2
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
/dev/sda2            /home/jwesleycooper/xtendedfs/ ext4       acl,user_xattr        1 2
--------------------------------------------------------------------------------

=================== sda6: Location of files loaded by Grub: ====================

           GiB - GB             File                                 Fragment(s)

  76.985129833 = 82.662153728   boot/grub/menu.lst                             1
  78.246314526 = 84.016340480   boot/grub/stage2                               1
  78.856029034 = 84.671016448   boot/initrd                                    2
  78.856029034 = 84.671016448   boot/initrd-2.6.37.6-0.5-desktop               2
  79.688453197 = 85.564825088   boot/vmlinuz                                   1
  79.688453197 = 85.564825088   boot/vmlinuz-2.6.37.6-0.5-desktop              1

=========================== sdb1/boot/grub/menu.lst: ===========================

--------------------------------------------------------------------------------
configfile /ubcd/menus/grub4dos/main.lst
--------------------------------------------------------------------------------

======================= sdb1/boot/syslinux/syslinux.cfg: =======================

--------------------------------------------------------------------------------
DEFAULT main

LABEL main
COM32 /boot/syslinux/menu.c32
APPEND /ubcd/menus/syslinux/main.cfg
--------------------------------------------------------------------------------

=================== sdb1: Location of files loaded by Grub: ====================

           GiB - GB             File                                 Fragment(s)

            ?? = ??             boot/grub/menu.lst                             1

================= sdb1: Location of files loaded by Syslinux: ==================

           GiB - GB             File                                 Fragment(s)

            ?? = ??             boot/syslinux/chain.c32                        1
            ?? = ??             boot/syslinux/config.c32                       1
            ?? = ??             boot/syslinux/hdt.c32                          1
            ?? = ??             boot/syslinux/ldlinux.sys                      1
            ?? = ??             boot/syslinux/localboot.c32                    1
            ?? = ??             boot/syslinux/menu.c32                         1
            ?? = ??             boot/syslinux/reboot.c32                       1
            ?? = ??             boot/syslinux/syslinux.cfg                     1
            ?? = ??             boot/syslinux/vesamenu.c32                     1
            ?? = ??             boot/syslinux/whichsys.c32                     1

============== sdb1: Version of COM32(R) files used by Syslinux: ===============

 boot/syslinux/chain.c32            :  COM32R module (v4.xx)
 boot/syslinux/config.c32           :  COM32R module (v4.xx)
 boot/syslinux/hdt.c32              :  COM32R module (v4.xx)
 boot/syslinux/localboot.c32        :  COM32R module (v4.xx)
 boot/syslinux/menu.c32             :  COM32R module (v4.xx)
 boot/syslinux/reboot.c32           :  COM32R module (v4.xx)
 boot/syslinux/vesamenu.c32         :  COM32R module (v4.xx)
 boot/syslinux/whichsys.c32         :  COM32R module (v4.xx)

======================== Unknown MBRs/Boot Sectors/etc: ========================

Unknown MBR on /dev/sda

00000000  90 eb 07 c0 01 0a 0a 00  80 00 fa 33 c0 8e d0 bc  |...........3....|
00000010  00 7c fb 50 53 51 52 1e  06 cd 12 eb 07 07 b1 04  |.|.PSQR.........|
00000020  38 6e 00 62 c1 e0 06 8b  d0 2e c5 1e bc 00 81 7f  |8n.b............|
00000030  03 52 50 75 0b 80 7f 05  4c 75 05 b8 06 4a cd 2f  |.RPu....Lu...J./|
00000040  8b ca 0e 1f 55 56 57 8b  f1 4e 2b 36 03 7c 83 e6  |....UVW..N+6.|..|
00000050  c0 89 36 4b 7d 2b ce c1  e1 03 8e c6 33 ff 33 c0  |..6K}+......3.3.|
00000060  fc f3 ab 06 8e c0 b4 08  8b 16 08 7c 52 cd 13 83  |...........|R...|
00000070  e1 3f 8a c1 f6 e6 03 c1  8b f8 bb 00 7e 88 0e 4d  |.?..........~..M|
00000080  7d 8b 0e 06 7c 5a e8 4b  00 33 c0 07 8a 07 68 00  |}...|Z.K.3....h.|
00000090  08 07 8d 77 08 50 5b 4b  53 52 c1 e3 02 8b 00 8b  |...w.P[KSR......|
000000a0  50 02 3b d7 73 3e f7 f7  92 8b ca f6 36 4d 7d c0  |P.;.s>......6M}.|
000000b0  e5 06 fe c4 0a ec 86 cd  5a 8a f0 c1 e3 07 74 64  |........Z.....td|
000000c0  8a 26 05 7c fe cc d0 e4  38 e7 75 05 ff 36 4b 7d  |.&.|....8.u..6K}|
000000d0  07 68 96 7c b0 05 50 b8  01 02 cd 13 58 72 01 c3  |.h.|..P.....Xr..|
000000e0  fe c8 75 f2 0e 07 0e 1f  fc be 00 7c 0e 58 c1 e0  |..u........|.X..|
000000f0  04 2b f0 56 8b de 8b fe  81 c7 00 02 b9 ae 01 f3  |.+.V............|
00000100  a4 e9 00 02 83 c6 10 8b  14 0a d2 74 f7 79 05 8b  |...........t.y..|
00000110  4c 02 eb c0 be 63 7f ac  0a c0 74 fe 32 ff b4 0e  |L....c....t.2...|
00000120  cd 10 eb f3 58 a1 03 7c  8b 36 06 7c 8b 3e 08 7c  |....X..|.6.|.>.||
00000130  8c c5 83 c5 20 8e dd 66  81 3f fe fd ce ef 75 a4  |.... ..f.?....u.|
00000140  89 6f 08 ff 5f 06 72 9c  ea 04 02 49 6e 76 61 6c  |.o.._.r....Inval|
00000150  69 64 20 70 61 72 74 69  74 69 6f 6e 20 74 61 62  |id partition tab|
00000160  6c 65 00 45 72 72 6f 72  20 6c 6f 61 64 69 6e 67  |le.Error loading|
00000170  20 6f 70 65 72 61 74 69  6e 67 20 73 79 73 74 65  | operating syste|
00000180  6d 00 4d 69 73 73 69 6e  67 20 6f 70 65 72 61 74  |m.Missing operat|
00000190  69 6e 67 20 73 79 73 74  65 6d 00 00 00 00 00 00  |ing system......|
000001a0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000001b0  00 00 00 00 00 2c 44 63  a3 04 2d a4 00 00 00 01  |.....,Dc..-.....|
000001c0  01 00 de fe 3f 04 3f 00  00 00 86 39 01 00 00 19  |....?.?....9....|
000001d0  15 05 83 fe ff ff 00 40  01 00 00 50 3a 09 80 fe  |.......@...P:...|
000001e0  ff ff 0f fe ff ff 64 97  3b 09 5d f3 65 09 00 00  |......d.;.].e...|
000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
00000200


=============================== StdErr Messages: ===============================

  No volume groups found
mdadm: No arrays found in config file or automatically

Icecube · **Joined:** Fri Jan 11, 2008 2:52 pm **Posts:** 1277

The Syslinux MBR is correctly installed and the first partition of your USB drive is marked active.
Syslinux is not installed in the PBR of sdb1. Try to remove the /boot/syslinux/ldlinux.sys file onf sdb1 and run the Syslinux installer again.

Then run Boot Info Script again. It should display something like this, when Syslinux is correctly installed:

Code:

sdb1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  SYSLINUX 4.04 2010-04-18
    Boot sector info:  SYSLINUX is installed in the /boot/syslinux directory. 
                       According to the info in the boot sector, sdb1 starts
                       at sector 0. But according to the info from fdisk,
                       sdb1 starts at sector 2048.
    Operating System: 
    Boot files:        /boot/grub/menu.lst /boot/syslinux/syslinux.cfg
                       /boot/syslinux/ldlinux.sys

hack-wizard · **Joined:** Thu Jul 14, 2011 7:36 pm **Posts:** 8

Icecube wrote:

The Syslinux MBR is correctly installed and the first partition of your USB drive is marked active.
Syslinux is not installed in the PBR of sdb1. Try to remove the /boot/syslinux/ldlinux.sys file onf sdb1 and run the Syslinux installer again.

Then run Boot Info Script again. It should display something like this, when Syslinux is correctly installed:

Code:

sdb1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  SYSLINUX 4.04 2010-04-18
    Boot sector info:  SYSLINUX is installed in the /boot/syslinux directory. 
                       According to the info in the boot sector, sdb1 starts
                       at sector 0. But according to the info from fdisk,
                       sdb1 starts at sector 2048.
    Operating System: 
    Boot files:        /boot/grub/menu.lst /boot/syslinux/syslinux.cfg
                       /boot/syslinux/ldlinux.sys

I'm still not getting the boot sector info and boot files you indicated ... also, once again, the following occurred upon executing the syslinux install command:

Code:

jwesleycooper@linux-twom:~/ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb> sudo ./syslinux -s -d /boot/syslinux /dev/sdb1
./syslinux: no previous syslinux boot sector found

But the more I think about it, the more this would appear to me to be the cause of this:

Code:

According to the info in the boot sector, sdb1 starts at sector 0. But according to the info from fdisk, sdb1 starts at sector 2048

Which leads me to believe that perhaps the MBR is pointing to the wrong starting location for SDB, thus they are not connecting, thus preventing syslinux from installing ... perhaps I should try altering this pointer value contained in the mbr.bin file using a hex editor, dd it to the drive again, and see if this fixes it?

ady · **Joined:** Sat May 08, 2010 5:26 am **Posts:** 654

Could you please double check that

Code:

/ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux

is indeed executable, and that the path is exactly that, as the instructions requests? It is simpler for all of us to use the correct path while giving / receiving instructions.

Could you try connecting your UFD to a different USB port?

Could you run the command with the complete path:

_ if your UFD is still sdb (sdb1); and,
_ the complete path is exactly (and really, in your actual system) :
/ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux

then run (it's all one and the same line of code):

Code:

sudo /ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux
 -s -d /ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux /dev/sdb1

Code:

sudo /ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux
 -s -d /boot/syslinux /dev/sdb1

Please verify and correct the path, including the origin.

After that, with your sdb mounted, run BootInfoScript (BIS) (and select the new results.txt, or results1.txt or results2.txt..., according to the number of times you already ran the script).

Run BIS even if the new syslinux command states "no previous syslinux boot sector found".

Please post the results.

The fdisk discrepancy shouldn't be the problem here, but I do recognize that for a "normal" FAT UFD, the difference I would expect would be "zero" and "63", not "2048". It is still possible though.

( So it might be recommended that the UFD should be completely "cleaned", disconnected, and reformatted to FAT32, with the "traditional" 63 sectors offset. If you do, then the "cleaning" of the MBR and FATs, and disconnection steps are important, not just the reformat. BUT, probably Icecube should comment on this too, before you perform these cleaning and formatting steps. )

This could be related to the specific "CHS" shown in your BIS result (4 heads, 8 sectors/track, 244606 cylinders, total 7827392 sectors), which "may" have problems with the "floppy" format expected.

In any case, as your report *should* show, the "boot sector type" should be "syslinux 4.04" for sdb1, not "FAT32" as it is now. So please try again the syslinux instructions with the complete path as described some paragraphs above and report back.

ady · **Joined:** Sat May 08, 2010 5:26 am **Posts:** 654

Sorry, my apologies.

I corrected the code in my previous post:

Code:

sudo /ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux
 -s -d /ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux /dev/sdb1

Code:

sudo /ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux
 -s -d /boot/syslinux /dev/sdb1

hack-wizard · **Joined:** Thu Jul 14, 2011 7:36 pm **Posts:** 8

ady wrote:

Could you please double check that

Code:

/ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux

is indeed executable, and that the path is exactly that, as the instructions requests? It is simpler for all of us to use the correct path while giving / receiving instructions.

Could you try connecting your UFD to a different USB port?

Could you run the command with the complete path:

_ if your UFD is still sdb (sdb1); and,
_ the complete path is exactly (and really, in your actual system) :
/ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux

then run (it's all one and the same line of code):

Code:

sudo /ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux
 -s -d /ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux /dev/sdb1

Please verify and correct the path, including the origin.

After that, with your sdb mounted, run BootInfoScript (BIS) (and select the new results.txt, or results1.txt or results2.txt..., according to the number of times you already ran the script).

Run BIS even if the new syslinux command states "no previous syslinux boot sector found".

Please post the results.

The fdisk discrepancy shouldn't be the problem here, but I do recognize that for a "normal" FAT UFD, the difference I would expect would be "zero" and "63", not "2048". It is still possible though.

( So it might be recommended that the UFD should be completely "cleaned", disconnected, and reformatted to FAT32, with the "traditional" 63 sectors offset. If you do, then the "cleaning" of the MBR and FATs, and disconnection steps are important, not just the reformat. BUT, probably Icecube should comment on this too, before you perform these cleaning and formatting steps. )

This could be related to the specific "CHS" shown in your BIS result (4 heads, 8 sectors/track, 244606 cylinders, total 7827392 sectors), which "may" have problems with the "floppy" format expected.

In any case, as your report *should* show, the "boot sector type" should be "syslinux 4.04" for sdb1, not "FAT32" as it is now. So please try again the syslinux instructions with the complete path as described some paragraphs above and report back.

Here it is, explicitly coded, though I had to run the installer from my computer's built in hard drive, as I can't seem to get the permissions to change on the flash drive. (With the dev as sdd1, which it now is)

Code:

jwesleycooper@linux-twom:~> chmod a+x /home/jwesleycooper/ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux
jwesleycooper@linux-twom:~> sudo /home/jwesleycooper/ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux -s -d /media/FC0F-1206_/boot/syslinux /dev/sdd1
/home/jwesleycooper/ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux: no previous syslinux boot sector found

And now the pertinent results from the latest run of the BIS scripts:

Code:

sdd1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  FAT32
    Boot sector info:   According to the info in the boot sector, sdd1 starts 
                       at sector 0. But according to the info from fdisk, 
                       sdd1 starts at sector 2048.
    Operating System:  
    Boot files:

So it would appear that the issue is the the unusual offset ... but herein lies another issue: fdisk says that a value of 63 for the offset is "out of range" and than the lowest I can use is 2048!

So is this basically an issue with how the hardware is made, or is there some way to override fdisk on this?

Or is this perhaps because it's a 4GB flash drive?

ady · **Joined:** Sat May 08, 2010 5:26 am **Posts:** 654

Several comments.

First, I hope you noticed the correction to the code in my post. I mention this because, for some reason, the edition I made was not quoted in your post. Instead, the original (wrong) code is quoted. It would be better if you could please edit the quote in your post too, so to avoid confusion to any future reader.

Now, in your latest results.txt, there are no "Boot files" information; or you simply didn't paste it here?

About the 4GB UFD, for FAT32 it shouldn't be a problem. The limit around 4GB related to FAT32 is for "files", not for "partitions".

[OFF-TOPIC]
(Little OT : About the offset, 2048 is not "unusual". For any new HDD partitioned and formatted with Windows Vista and up, 2048 is the new "normal" offset, specially (but not only) for new "Advance Format" drives. Linux has supported this for a long time.)
[/OFF-TOPIC]

For fdisk to be able to partition from offset 63, you would need to "clean" the current MBR and FAT tables of the current UFD (please, backup anything important, and PLEASE do NOT confuse the drives you want to "clean". YOU are the only responsible).

***

I WOULD SUGGEST WAITING FOR ICECUBE'S INPUTS BEFORE ACTUALLY FOLLOWING THE NEXT STEPS.

I know about MBR, partitions and formatting, but Icecube REALLY knows Syslinux.

The 2048 offset might not be a factor here (in regards to syslinux), so maybe the fdisk-related steps are unnecessary.

Still, the "CHS" ( 4 heads, 8 sectors/track, 244606 cylinders, total 7827392 sectors ) indeed might have relation to the other problem "This is not a bootable floppy".

***

You can't simply and directly "repartition". You need to

1_ "Delete" the current MBR information of your UFD. Save that "status" (no partitions at all). EXIT fdisk.
2_ (Unmount if necessary and) Disconnect your UFD.
3_ Do NOT reconnect it immediately. Wait, so any residual info (cache, swap, whatever) about your UFD won't interfere when you reconnect it.
4_ Reconnect your UFD. Wait until it is completely recognized by your system.
5_ Start anew Fdisk, which should recognized a "clean/empty" MBR of you UFD. Partition from offset 63 ("old traditional") and up to a logical cylinder limit, if the 63 initial offset is what you want and need.
6_ Format as FAT32, and mark the partition as active/bootable. For now, do NOT add any boot code nor system files.

Exit fdisk, and disconnect the UFD. Now that you have a new FAT32 formatted partition, follow the "readme.txt" instructions, including the syslinux mbr.bin and syslinux loader installations.

Then run BIS and report back.

I want to strongly advice (again) about being specially careful with fdisk (or alternatives). If you wipe your main HDD instead of the UFD, don't blame anyone but yourself!

I'll wait for your report from BIS.

ady · **Joined:** Sat May 08, 2010 5:26 am **Posts:** 654

One additional comment about the CHS and the offset.

If your BIOS detects your UFD with the current CHS values
( 4H x 8S )

and changing the BIOS settings to
USB-FDD / USB-ZIP / USB-HDD / OTHER

together with changing

AHCI / IDE COMPATIBLE modes

won't change the CHS values of your UFD recognized by the BIOS, the 2048 is the "best" offset.

Explanation:

The "63" is originated from "the first track" ( 63 sectors per track is the "traditional" value).

If your UFD will be recognized as 8 sectors per track (in any setting in your BIOS), then "63" is not such a good value. The next "best" value would be 2048, which is the current new "standard" (but "64" could be used in some cases).

The problem with installing syslinux shouldn't be the "63" or the "2048". Let's hear from Icecube.

Icecube · **Joined:** Fri Jan 11, 2008 2:52 pm **Posts:** 1277

I think I found your problem, try this:

Code:

sudo /home/jwesleycooper/ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux --install --directory /boot/syslinux /dev/sdd1

The offset of the partition doesn't matter. I never had any problems installing Syslinux to partitions that start at sector 2048.

Also try the last test version of Syslinux:
http://www.kernel.org/pub/linux/utils/b ... x/Testing/

ady · **Joined:** Sat May 08, 2010 5:26 am **Posts:** 654

Icecube wrote:

I think I found your problem, try this:

Code:

sudo /home/jwesleycooper/ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux --install --directory /boot/syslinux /dev/sdd1

The offset of the partition doesn't matter. I never had any problems installing Syslinux to partitions that start at sector 2048.

Also try the last test version of Syslinux:
http://www.kernel.org/pub/linux/utils/b ... x/Testing/

@hack-wizard,

be aware of the "--directory /boot/syslinux" part of the code. That part is "exactly as-is" ( for UBCD ), and obviously the rest depends on the exact path to syslinux and the exact device (sdd1 or the correct one for you).

About trying the latest test version of Syslinux, I would leave that only after trying the current version already included in UBCD ( syslinux 4.04 ). Changing syslinux version implies several group of files, not just the executable command.

Please run BIS after the command suggested by Icecube and report back.

hack-wizard · **Joined:** Thu Jul 14, 2011 7:36 pm **Posts:** 8

ady wrote:

Icecube wrote:

I think I found your problem, try this:

Code:

sudo /home/jwesleycooper/ubcd51b1-extracted/ubcd/tools/linux/ubcd2usb/syslinux --install --directory /boot/syslinux /dev/sdd1

The offset of the partition doesn't matter. I never had any problems installing Syslinux to partitions that start at sector 2048.

Also try the last test version of Syslinux:
http://www.kernel.org/pub/linux/utils/b ... x/Testing/

@hack-wizard,

be aware of the "--directory /boot/syslinux" part of the code. That part is "exactly as-is" ( for UBCD ), and obviously the rest depends on the exact path to syslinux and the exact device (sdd1 or the correct one for you).

About trying the latest test version of Syslinux, I would leave that only after trying the current version already included in UBCD ( syslinux 4.04 ). Changing syslinux version implies several group of files, not just the executable command.

Please run BIS after the command suggested by Icecube and report back.

Thanks Icecube and ady, it seems to be working correctly now, and I'm getting the following output from BIS:

Code:

sdb1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  SYSLINUX 4.04 2011-04-18
    Boot sector info:   Syslinux looks at sector 731560 of /dev/sdb1 for its 
                       second stage. SYSLINUX is installed in the 
                       /boot/syslinux/ directory. According to the info in 
                       the boot sector, sdb1 starts at sector 0. But 
                       according to the info from fdisk, sdb1 starts at 
                       sector 2048.
    Operating System:  
    Boot files:        /boot/grub/menu.lst /boot/syslinux/syslinux.cfg 
                       /boot/syslinux/ldlinux.sys

So should I be able to simply add/replace files on the usb for the purpose of customizing it (for instance, antivirus definitions)?

Missing Operating System?!?

Who is online