Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14

Thread: unetbootin, failure to boot after creation

  1. #11
    Join Date
    Nov 2011
    Location
    /dev/root
    Beans
    Hidden!

    Re: unetbootin, failure to boot after creation

    Quote Originally Posted by F W Adams View Post
    I went and bought another flash USB today and set it up, it was fine.

    I did as you suggested but rather as expected it didn't work. The transfer was of about 1GB from partition 1 of the ok system ( sdd1 ) to the bad one ( sdc1 ). SYNC took about 15 seconds so definately necessary. As expected it turned it into a 1GB device. I haven't looked in detail but the files seem fine, the disk label was transferred as well, it doesn't show as I changed the label of the ok one afterwards. Bad one: according to fdisk the format is FAT16, as it was before the transfer, but gparted has it as FAT16 before the transfer and F32 afterwrds. When booting there was just a blank screen.


    fdisk, mount & two ls -l -R

    Code:
    felix@emma:~$ 
    felix@emma:~$ sudo fdisk -l
    ...
    Disk /dev/sdc: 3869 MB, 3869544448 bytes
    105 heads, 18 sectors/track, 3998 cylinders, total 7557704 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: 0x0009020b
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdc1            2048     7557119     3777536    6  FAT16
    
    Disk /dev/sdd: 3999 MB, 3999268864 bytes
    255 heads, 63 sectors/track, 486 cylinders, total 7811072 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: 0xc3072e18
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdd1   *          63     2152709     1076323+   b  W95 FAT32
    /dev/sdd2         2152710     7807589     2827440    b  W95 FAT32
    ...
    I emailed the supplier today about whether it was a solvable problem, though there's not a lot of consolation in being well paid doing up a parcel and then posting it.

    -------------------

    I was just about to send this when I decided to check something else. The flags ( BOOT in this case ) hadn't been transferred by dd, is this what you would expect? I was expecting the flag to be transferred. The working version had BOOT set on partition 1, but not the copy. When I manually set the boot flag it fixed the problem. Booted ok and files seem ok.

    I'll mark as solved when I'm more sure it works.

    I'm still surprised that your method worked, well, with a tiny bit of help, and yet the dd'ing the zeros didn't.
    The target pen-drive is smaller than the source one

    Disk /dev/sdc: 3869 MB
    Disk /dev/sdd: 3999 MB

    also heads, sectors/track and cylinders differ.

    When the target is smaller the dd cloning is truncated. This might cause problems. Also it is strange that the heads, sectors/track and cylinders differ. 255 heads, 63 sectors/track are standard values for modern drives. Maybe it would help if you change those values. See
    Code:
    man fdisk
    A successful cloning would certainly copy also the boot flag. I'm glad you observed that difference and could fix it

    Anyway, those four pendrives really behave in a strange way.
    Last edited by sudodus; July 16th, 2012 at 10:19 PM. Reason: also heads, sectors/track and cylinders differ

  2. #12
    Join Date
    Oct 2007
    Beans
    87
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: unetbootin, failure to boot after creation

    The target pen-drive is smaller than the source one

    Disk /dev/sdc: 3869 MB
    Disk /dev/sdd: 3999 MB
    No arguing with 3999 > 3869 but the dd was only asked to copy the first partition, and about 1000 < 3869. When source is really bigger than destination it gives an error message.

    -------

    Is it possible the KINGSTON drive is storing the partition flags in the area before the partitions start and consequently not looking at them on copy paritions?

    Anyway glad to have it fixed. Thanks.
    regards,
    ubuntu 12.04 with full encryption, an SSD and dual monitors

  3. #13
    Join Date
    Nov 2011
    Location
    /dev/root
    Beans
    Hidden!

    Re: unetbootin, failure to boot after creation

    Quote Originally Posted by F W Adams View Post
    No arguing with 3999 > 3869 but the dd was only asked to copy the first partition, and about 1000 < 3869. When source is really bigger than destination it gives an error message.
    I see. Yes, that first partition should have been copied correctly. Provided that the settings for heads, sectors/track and cylinders won't create problems.
    Is it possible the KINGSTON drive is storing the partition flags in the area before the partitions start and consequently not looking at them on copy paritions?

    Anyway glad to have it fixed. Thanks.
    I'm not sure, but probably the partition table including flags is located in the MBR (the head of the drive, before the partitions), and I think this is also where the settings for heads, sectors/track and cylinder reside. So if you copy also the first 512 bytes from the good drive to the bad one, you might repair everything.

  4. #14
    Join Date
    Nov 2007
    Beans
    21

    Re: unetbootin, failure to boot after creation

    Quote Originally Posted by Cheesehead View Post
    Double-check that you used a valid 10.04 image.
    Try making the USB Stick again.

    The directory listing you posted seems to have neither a kernel or a compressed-system to use that kernel, both of which come from the 10.04 image.
    what if i am using ubuntu 12.04
    i am tryiing to make HBCD using the iso file and unetbootin but it boot only to main screen where is the only choise is default and when i click it it doesnt do anything and my hbcd doesnt start

Page 2 of 2 FirstFirst 12

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •