Latest 32bit USB distro not working?

HI

I’m checking the latest 32bit USB image available
(Stable-5.211.65-1) just downloaded

I’m flashing a 8GB usb pen the usual way:
dd if=distro.img of=/dev/sdx

There is no way to make it boot (it says boot error on more PC)

Just flashed the 4.211.64-7 the same way , it works like a charm.

Is there any known issue with the usb image ??

At the moment I’m dowloading 4.211.64-9 and 5.211.65-1(64bit)
to see how those behave…

Thanks

For information 4.211.64-9 (32bit) works fine

I re-downloaded the 5.211.65-1 several times but no luck

By the way , the new images are 2GB rather the old 1GB

Once uncompressed on usb key , they still have the whole .ISO image inside

Why is this ???
Isn’t it a waste of space (and download capability) ??

Thanks

What is the boot error you are seeing?

Simply “boot error” message when system starts to access usb device for boot
It repeats whenever enter key is pressed
tried on more machines hardware , same thing.
5.211.65-1(64bit) works OK too, only the newest 32bit seems to be faulty
Of course, tried different usb keys…

Just tested 32bit and 64bit and it worked fine for me. I also see over 400 people have installed the 5.211.65-1 from USB since it was published. Seems to be a isolated issue on your side.

Far from suppose a bugged distro was published on mainsite, just to know if someone else encountered this problem…
Three PC , so three different downloads and three different USB keys, tried many combinations of all these, same result 5.211.65-1 (32bit) no boot (and a lot of PC to test boot from)…all other distro are OK
There would be something paranormal on the lab here…
I will try with an .ISO CD…

I don’t want to be tedious…

Last time, I wasn’t able to make Stable-5.211.65-1(32bit) USB-IMG to boot once written on USB pen

This time is the same exact thing with the
Stable-5.211.65-3 64bit (FreePBX-5.211.65-3-x86_64-Full-1388073872.img)

Downloaded by a linux machine and written with dd if=(img_name) of=/dev/sdx
Downloaded by a windows machine and written with win32 diskimager

Same result like the previous 65-1 (32bit) , “boot error” displayed when machine boots

Tried more machines and more usb pens

On linux the .img file length is 1572864000 bytes

Am I the only who experience these problems ???
Could my download system corrupt the image ??

Thanks

Did you verified your downloaded images (IMG and/or ISO) with MD5SUM hash just before creating the USB or DVD install media? Never say never…paranormal DSL lines…

It has to be a issue on your side as it works just fine here and once again I show well over 1000 installs of that img already.

What the hell…
Surely is a local issue
All usbpen written in different ways, are bootable here only on classic style hw pc (motherboard , cards etc) also if new
All compact pc tried here (mini-pc netbook all-in-one etc), fails to boot giving back simply a "boot error"
Probably it is something bios-related I can’t get rid of…
Any suggestion ?? (other than go with an USB external cd-rom and run the .ISO image…)

The strange thing is there are some .img that works with these compact pc, ie 4.211.64-7(32) 4.211.64-9(32) 5.211.65-1(64)
Of course the burning process and supports are the same…

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 !!!

I don’t know if this could be of any help…I didn’t tried a USB install yet.

I’m going to speak about the 64 bit IMG version (not about the 32 bit version).

In the mean time could you post the MD5SUM hash of your downloaded FreePBX Distro 6.12.65-3 64 bit IMG file?

I noticed that three different downloads made at three different times in the last 36 hours of the FreePBX Distro 6.12.65-3 64 bit IMG file (file timestamp: 26.01.2014) resulted in three very identical MD5SUM hashes which, in my very specific case, were always:

eef001ff4eb1b1bfdc562d4621e9db33

As result, this one looked like a little bit strange considering that, every time, those three MD5SUM hashes were equals each others but, in contrast, they differ from the one provided here for that specific IMG file (the link I provide here is not yet advertised on the FreePBX Distro download page as happens with the ISO MD5SUM hash).

It’s strange that three different downloads, if eventually corrupted in different ways, gave the same MD5SUM hash: I think downloads were OK (not corrupted).

The “official” MD5SUM hash for the 64 bit FreePBX Distro 6.12.65-3 IMG file reports:

37fa22ef6ec02e84e143f40bfd26a326

So a questions rises: what’s wrong? is it my side? …or the MD5SUM hash “officially” provided above isn’t the one of that IMG file published? …or is the provided MD5SUM hash correct but the IMG file published in some way corrupted?

Now I’ll try a USB install with that IMG file and hope to report back.

Transferred the downloaded IMG file (one with the MD5SUM hash equals to “eef001ff4eb1b1bfdc562d4621e9db33”) using dd to a bulk un-partitioned (hence un-formatted) 2 GB USB 2.0 stick: it then booted flawlessly FreePBX Distro 6.12.65-3 64 bit on the very first desktop workstation available here in my Lab.

Here some info before and after the dd:

fdisk -l

Disk /dev/sdf: 2063 MB, 2063597568 bytes, 4030464 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 label type: dos
Disk identifier: 0xf272400a

Device Boot Start End Blocks Id System

dd if=/home/parnassus/Downloads/FreePBX-6.12.65-3-x86_64-
Full-1390698000.img of=/dev/sdf

3072000+0 records in
3072000+0 records out
1572864000 bytes (1.6 GB) copied, 769.993 s, 2.0 MB/s

fdisk -l

Disk /dev/sdf: 2063 MB, 2063597568 bytes, 4030464 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 label type: dos
Disk identifier: 0xbb0eb409

This doesn’t look like a partition table
Probably you selected the wrong device.

Device Boot Start End Blocks Id System
/dev/sdf1 ? 3447419926 5314066216 933323145+ 66 Unknown
/dev/sdf2 ? 2573 2573 0 72 Unknown

Partition table entries are not in disk order

So the resulting USB file systems structure is equal to the one reported.

The USB stick mounts itself as “LIVE”.

At this point our results are the same :
Different md5sum from one published on website

md5sum FreePBX-6.12.65-3-x86_64-Full-1390698000.img eef001ff4eb1b1bfdc562d4621e9db33 FreePBX-6.12.65-3-x86_64-Full-1390698000.img

Fresh 8Gb microSD on USB reader (but the same on 8Gb USB Stick)

Disco /dev/sdc: 7948 MB, 7948206080 byte 245 testine, 62 settori/tracce, 1021 cilindri, totale 15523840 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: 0x3f5b65ce

Dispositivo Boot Start End Blocks Id System

dd if=FreePBX-6.12.65-3-x86_64-Full-1390698000.img of=/dev/sdc 3072000+0 record dentro 3072000+0 record fuori 1572864000 byte (1,6 GB) copiati, 641,099 s, 2,5 MB/s
fdisk /dev/sdc

Disco /dev/sdc: 7948 MB, 7948206080 byte
245 testine, 62 settori/tracce, 1021 cilindri, totale 15523840 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

As yours, my USB devices mount themselves as LIVE
But I get “boot error” on all machines here, I’ll try some other models
The strange thing is some distro work ok (i.e. as said 5.211.65-1(64)) with the same no md5 match and the same strange fdisk structure.

Is it perhaps a BIOS issue ???
If was so, what should I check ???

Thank you

I can’t comment about BIOS related issues regarding your USB boot failures (of your created USB Sticks) but few things are becoming clearer now:

  1. the MD5SUM Hash of "FreePBX-6.12.65-3-x86_64-Full-1390698000.img" file is, IMHO, wrong (or it's correct but it doesn't refer to the IMG file at all and it doesn't refer to the ISO file contained into the IMG file too).
  2. the published "FreePBX-6.12.65-3-x86_64-Full-1390698000.img" file provides a common calculated MD5SUM Hash which was always equal to what we calculated using independent procedures. This MD5SUM Hash should be used to validate IMG downloads.
  3. fdisk command exectuted on mounted "LIVE" USB Stick reports two Partition Identifiers (Id): 66 and 72 (see above for details).
  4. USB Stick contains "FreePBX-6.12.65-3-x86_64-Full-1390698000.iso" file (see point 1).

Then we could discuss about the FreePBX Distro IMG structure once it was transferred to the USB Stick (IMHO it’s a Live CD on Bootable USB).

I’m having the same issue with checksums not matching USB images.

First, the img.md5sum files have a path that I must remove.

I’ve downloaded each img file multiple times and the checksums (both MD5 and SHA256) are consistent with my downloads suggesting a consistent mangling or no mangling.

provided MD5 checksums:
a805924a5d2a2d968198f35357b2d3fa FreePBX-5.211.65-8-i386-Full-1394596981.img
69bf1cab11d0e66ce67b0746f4727bb5 FreePBX-5.211.65-8-x86_64-Full-1394598197.img
2988311f69b0c4ce2bf1bdd1615f4bd0 FreePBX-5.211.65-9-i386-Full-1395548161.img
95561b19da4a1f921d63ab834618f7af FreePBX-5.211.65-9-x86_64-Full-1395581080.img
12342392a916a62b4427645ae79ab3b4 FreePBX-5.211.65-10-i386-Full-1396481127.img
409753fc33743b0332e880ed726fa64b FreePBX-5.211.65-10-x86_64-Full-1396483193.img

My MD5 checksums:
772d31534ac1b9b200b5b7c08cbc24c8 FreePBX-5.211.65-8-i386-Full-1394596981.img
5d3943e94416fe51e555fce4d331b974 FreePBX-5.211.65-8-x86_64-Full-1394598197.img
1a5f20a01a3422186209416fb8322972 FreePBX-5.211.65-9-i386-Full-1395548161.img
4511166b66e5e51abbed4d2f8790afc0 FreePBX-5.211.65-9-x86_64-Full-1395581080.img
82b622adff57ba845c245746c4fcf342 FreePBX-5.211.65-10-i386-Full-1396481127.img
e200648dae8949ff0ac329530cae36ba FreePBX-5.211.65-10-x86_64-Full-1396483193.img

DVD install not an option for installation at remote sites at this time.

I’m wondering about the comment that thousands of people have installed without issue. Is that a conclusion based on number of downloads or do installed systems report method of install? If based on number of downloads, it might not be a valid conclusion as people might download the img and fail the install then download the iso and succeed.

Surely a question that belongs in the “Distro Discussion & Help” forum, this one is for problems with install problems and questions of FreePBX not “The FreePBX Distribution”

Just trying to keep us all rigorous here, as documented at:-

http://www.freepbx.org/forums

Thanks. I wasn’t entirely sure this thread belonged here, but I was adding additional information.

Is it possible for a moderator to move this thread?

I can create a new thread, but it won’t have the previous posts.

moved.