-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New NanoKVM - /dev/mmcblk0p3 - no filesytem #76
Comments
This must be the data partition that is automatically created when the KVM boots. This happens whenever the firmware is reflashed, so I assume these little guys are mass-produced and were probably never turned on at the factory. See #7 (comment) on reflashing the firmware. |
Well, the partition was there, but no exFAT had been created. I dumped the partition with dd and it was all zeros. After creating the filesystem myself it worked. Version 2.0.9 |
Yeah I got a new one a couple of days ago and had to re-image the included MicroSD card, as it wasn't working correctly. |
What method did you use for that? I tried step #5 from this, but nothing happened.
I copied the decompressed image file to the root of /dev/mmcblk0p2 The wiki makes it sound like upon reboot something is supposed to happen with it, but it just stays there. Or do I need to write the image to the sd-card with dd ? |
Yeah, use dd to write it to the SD and you should be good They have a guide on their wiki for flashing, it says to use balenaEtcher but dd will ofc also do the trick. Step 5 in the User Guide is about updating, that wont do anything if the system image is missing in the first place. |
@madworm Hi, we have implemented partition formatting and data mounting in/etc/init.d/S01fs. Has this been helpful for your question? |
Just letting you know that I've received a "fresh" NanoKVM today
The text was updated successfully, but these errors were encountered: