Oracle (creator of VirtualBox) have said this is a user error and not vbox failure)Ībout USB pendrive I had copied an file size 6 GB and in other computer the file had to be extracted and thus an good test and the file was extracted without errors. (a number of other situations have also been known to cause squashfs errors but they usually apply to VMs were insufficient RAM is allocated causing virtualbox, VMware etc to fail. The media validation tests (now automatic, they used to be user initiated in prior releases) are supposed to catch most ( if not all) of these, however if media is faulty, it’s also possible for faulty media to falsely pass, thus the ISO validation step being required ( it’ll catch that situation).
Probably the most useful bug report that maybe useful is Bug #1874662 “Corrupted installation medium” : Bugs : Ubuntu In my experience, the write to install media is the most likely failing point. In the manual, did you perform checksum validation? SQUASHFS errors are usually the result of a faulty ISO, or inability to read the source media during installation. Īug7744: [ 155.553103 SQUASHFS error: failed to read block 0X2acb002, data probably corrupt Kernel offset : (from relocation range: XXX ) Kernel panic - not syncing to : Attemped to kill init ! exitcode=0x00000100ĬPU: 4 PID: 1 Comm : run-init not tainted 5.8.0-25-generic #26-ubuntuĮntry_SYSCALL_64_after_hwframe_6+0x44/0xa9
Zlib compression failed data probably corrupt
[ 155.553103 SQUASHFS error: failed to read block 0X2acb002, data probably corrupt XXX means long value numbers memory regions. USB pen drive has not problems and was created in Lubuntu 18.04.5 32 bits using current Lubuntu 20.10 64 ISO.Īfter file checking the install crash and only is possible read the last lines.
Unhappily not has enough time to run tests 10 to 13. Memory test from test 1 to 9 not problems.
0 kommentar(er)
