![]() ![]() I also ran the memtest utility that comes with the Arch live image and it says my memory is OK, so I don't think it's that, either. So it seems to be the specific combination of Arch and the NUC that is the problem, though I've no idea why. ![]() And I can boot another distro's live image (I tried Puppy Linux) on the NUC. The image on the USB stick is OK because it boots fine on another machine. (This step you might need to manually select one from boot manager, if your primary HDD is at first priority). Restart the system and live boot into your USB. But I didn't manage to install it correctly those times (I think I forgot to install a bootloader!), and I haven't got it to boot successfully again, in spite of trying many times. Next using any live USB installer (my preference are YUMI or LiLi USB creator), make your USB drive bootable. They seem to occur at different points in the boot process each time, and how badly the boot is affected seems to vary: sometimes it leads to a completely crashed blank screen, sometimes I get a half-working environment but with certain files and executables inaccessible, and once or twice it even seems to have booted completely successfully. What's weird about this is that the errors are a bit random. Where the XXXXs are numbers and hex codes that are different each time. SQUASHFS error: Unable to read data cache entry ![]() SQUASHFS error: squashfs_read_data failed to read block XXXX ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |