| 1 |
> On Sep 2, 2014, at 8:55, Joseph <syscon780@×××××.com> wrote: |
| 2 |
> |
| 3 |
>> On 09/02/14 06:36, Mick wrote: |
| 4 |
>>> On Tuesday 02 Sep 2014 01:26:05 Joseph wrote: |
| 5 |
>>> On 09/02/14 01:08, Neil Bothwick wrote: |
| 6 |
>>> >On Mon, 1 Sep 2014 17:42:47 -0600, Joseph wrote: |
| 7 |
>>> >> I just tried "usb_instal.sh" script from systemrescuecd-x86-4.3.0.iso |
| 8 |
>>> >> and my box boots just fine. So why do I have problem using "unetbootin" |
| 9 |
>>> >> and generating bootable USB manually. |
| 10 |
>>> > |
| 11 |
>>> >unetbootin uses some $MAGIC that doesn't work with all ISOs. isohybrid |
| 12 |
>>> >seems to work with everything and is much simpler to use too. |
| 13 |
>>> |
| 14 |
>>> I just tried it as root: |
| 15 |
>>> isohybrid install-amd64-minimal-20140828.iso |
| 16 |
>>> dd if=/home/joseph/Downloads/install-amd64-minimal-20140828.iso of=/dev/sda |
| 17 |
>>> bs=4096 sync |
| 18 |
>>> |
| 19 |
>>> And the USB still can not boot it :-/ |
| 20 |
>> |
| 21 |
>> This is rather strange. |
| 22 |
>> |
| 23 |
>> What do you see when you run |
| 24 |
>> |
| 25 |
>> fdisk -l /dev/sda |
| 26 |
>> |
| 27 |
>> *after* you have completed dd and sync as you show above? |
| 28 |
>> |
| 29 |
>> -- |
| 30 |
>> Regards, |
| 31 |
>> Mick |
| 32 |
> |
| 33 |
> Yes, indeed I find it very strange as well. |
| 34 |
> I just re-run the dd on my faster box. |
| 35 |
> |
| 36 |
> dd if=/home/joseph/Downloads/install-amd64-minimal-20140828.iso of=/dev/sdb bs=4096 |
| 37 |
> 48640+0 records in |
| 38 |
> 48640+0 records out |
| 39 |
> 199229440 bytes (199 MB) copied, 318.573 s, 625 kB/s |
| 40 |
> sync |
| 41 |
> |
| 42 |
> fdisk -l /dev/sdb |
| 43 |
> |
| 44 |
> Disk /dev/sdb: 960 MiB, 1006632960 bytes, 1966080 sectors |
| 45 |
> Units: sectors of 1 * 512 = 512 bytes |
| 46 |
> Sector size (logical/physical): 512 bytes / 512 bytes |
| 47 |
> I/O size (minimum/optimal): 512 bytes / 512 bytes |
| 48 |
> Disklabel type: dos |
| 49 |
> Disk identifier: 0x1047d058 |
| 50 |
> |
| 51 |
> Device Boot Start End Blocks Id System |
| 52 |
> /dev/sdb1 * 0 389119 194560 17 Hidden HPFS/NTFS |
| 53 |
> |
| 54 |
> -- |
| 55 |
> Joseph |
| 56 |
|
| 57 |
Hi, |
| 58 |
|
| 59 |
Just wanna say few words to clarify few things about bootstraping. If you know what you are doing, this all is very simple. |
| 60 |
|
| 61 |
What you need for a working system is a working root filesystem that contains all the scripts, modules and executables. A minimal cd contains this. You could also use stage3 tar ball. |
| 62 |
|
| 63 |
Then you need a working kernel image and possibly a initrd. There is a working kernel on minimal cd. |
| 64 |
|
| 65 |
All begins with boot loader. That loader is loaded by BIOS first. Then boot loader starts executing and loads kernel with right parameters. Kernel takes over and loads rootfs and so on. |
| 66 |
|
| 67 |
On normal disk (USB, sata, ATA, SCSI (and DVD i think)) you have a normal MBR (first 512 bytes of disk) which BIOS loads to 0x07C0 address in memory and starts executing. So just install boot loader (like grub) to the beginning of the disk and it will boot. With right commands/config you can load the kernel correctly and boot. |
| 68 |
|
| 69 |
CD is different. BIOS can't read ISO file system. For CD boot you will need to create image of a floppy-disk and install your boot loader into that image. The boot loader has to have drivers to read the real ISO file system so that it can load the kernel into memory and boot. Because of this a plain cd isoimage is unbootable although all necessary stuff is there. It is easily arranged so that it becomes a bootable USB disk. |
| 70 |
|
| 71 |
-- |
| 72 |
-Matti |
Archives