I’m kinda having a problem with one of my “new” devices (NUC - like device) that I wanted to test. It is able to install and flash the image to the local device (at least I think). But when it reboots, it’s not able to boot again. It gets stuck in this state where it doesn’t react anymore.
Well … I can see errors like :
CP437: Invalid Argument
fsck.ext4: No such fie or directory while trying to open /dev/disk/by-label/resin-rootA
But the thing is, when I use a tool like gparted-live. I can see those disks with that label …
Is there something I can do to test it further ? Or to get boot - logs, or … has someone a good idea I can try ?
It’s resin os v2.12.5+rev1 (dev). And it’s an Intel Bay Trail-D J1900. (quad core celeron J1900 @1.99, 3I380D) with 4GB of ram. If you need more details, just let me know…
But it seems to start the initial flashing correctly, cause it appears on my dashboard. And it also changes state (I see it gets to the flashing state, and then offline). So the flashing “appears” to be working…
But … Is there a way to see into logs of the initial flashing ? So I can check if everything is going fine ?
So first time, it boots, starts initial installation and it appears on the dashboard. Then it shutdowns. I remove the USB key, and reboot it. And then it “hangs” with those error messages …
One “strange” thing I noticed, is that, when the device booted and is in this “blocked” status.
If I insert an USB stick at that moment, I’ll see the following at that moment :