FreeNAS 11.2 installation error: UZIP(zlib) inflate() failed

wolrechris

Cadet
Joined
Sep 25, 2019
Messages
7
Hey FreeNAS users,
I have an issue while installing FreeNAS 11.2-U6. After passing through the installer, the installation starts but ends immediately. Here's the full console output:

Code:
2+0 records in
2+0 records out
2097152 bytes transferred in 0.073843 secs (28400191 bytes/sec)
dd: /dav/da1: end of device
3+0 records in
2+0 records out
2097152 bytes transferred in 0.056840 secs (36895476 bytes/sec)
da1 created
da1p1 added
da1p2 added
gmirror: Invalid class name.
da1 destroyed
da1 created
da1p1 added
da1p2 added
active set on da1
md0.uzip: UZIP(zlib) inflate() failed
g_vfs_done():md0.uzip[READ(offset=14254080, length=65536)]error = 86
vnode_pager_generic_getpages_done: I/O read error 5
vm_fault: pager read error, pid 153 (python3.6)
pid153 (python3.6), uid 0: exited on signal 11
Segmentation fault
The FreeNAS installation on da1 has failed. Please enter to continue..


I'm trying to install FreeNAS on a 32 GB Intenso USB drive. I've already run FreeNAS on the same hardware for several years, however I've used two mirrored 16 GB Intenso Rainbow Line USB drives. Already tried installing on those too, but the problem remains.

System specs:
Intel Core i5-2500
8GB DDR3-1333MHz (2 x 4GB dims)
Since the system was a pre-built HP (HP Compaq 6200 Pro MT), the motherboard seems to be proprietary (Bios version: J01 v02.24)
Integrated Intel 82579LM Gigabit Ethernet

Any clues would be appreciated!
 
D

dlavigne

Guest
Which utility are you using to burn the image? Have you tried both USB2 and USB3 slots? Have you run a memtest lately to see if the RAM is still good (signal 11 is often related to RAM errors). Have you run 11.2 at all on this system before?
 

wolrechris

Cadet
Joined
Sep 25, 2019
Messages
7
I eventually figured this out, seems like from Freenas 11.1 onwards most Intenso USB drives have the same issue. I had tried different USB drives, but all by Intenso. Using two SanDisk 32GB in mirrored mode now and not having any issues!
 
Top