Assuming there are no issue in thousands .IMG distro users and the problem is limited to my reality, is there someone so patient to help me to produce a working
6.12.65(64) distro USB Key ??
I just “burned” a 5.211.65-1(64) .img file into a 8M Kingston usb key
It was done both with
dd if=distroname.img of=/dev/sdc
as well under windowsXP with win32diskimager
Both ways the USB key is perfectly bootable and the distro can be installed on many type of PC (netbook, notebook, laptop, towers, mini-pc etc.)
When I connect this key to an Ubuntu working PC it mounts the key as
/dev/sdc (not sdc1) on /media/LIVE_ and it shows graphically the key content
It is strange instead , if I do fdisk /dev/sdc a very strange arrangement is shown (pardon for italian language):
Disco /dev/sdc: 8010 MB, 8010194944 byte
247 testine, 62 settori/tracce, 1021 cilindri, totale 15644912 settori
Unità = settori di 1 * 512 = 512 byte
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Identificativo disco: 0xbb0eb409
Questa non sembra una tabella delle partizioni.
Probabilmente è stato scelto il dispositivo sbagliato.
Dispositivo Boot Start End Blocks Id System
/dev/sdc1 ? 3447419926 5314066216 933323145+ 66 Sconosciuto
/dev/sdc2 ? 2573 2573 0 72 Sconosciuto
Le voci nella tabella delle partizioni non sono nello stesso ordine del disco
The USB key , anyway , as said is bootable and works ok.
I tried to burn many (if not all)more recent .IMG distros the same way, dd or win32diskimager
All the burned keys produce a simple “boot error” message in all PCs I tried to boot from.
Again, if I try fdisk /dev/sdc to all these unworking keys, the disk structure is perfectly the same as the working ones (same identical fdisk result)
More, all the unworking keys , inserted into the same Ubuntu PC are showing correctly the “LIVE” disk content
But they simply do not boot.
Could anyone check their USB key structure once “burned” ???
Or…any hint to avoid I go crazy ???
Thanks !!!