Quote:
Originally Posted by ppoo
...
[root@[192_168_15_244] us]# dd if=/dev/zero of=/dev/mmcblk0p3 bs=4K
dd: writing '/dev/mmcblk0p3': No space left on device
8193+0 records in
8192+0 records out
33554432 bytes (32.0MB) copied, 0.267083 seconds, 119.8MB/s
[root@[192_168_15_244] us]# idme -d --bootmode main
Devmode enabled
Reading vars from temp storage...
...None found, Copying vars from /proc
Setting bootmode to main
Writing new vars to temp area
You must reboot before new values will take effect
[root@[192_168_15_244] us]# rm /mnt/us/ENABLE_DIAGS
rm: can't remove '/mnt/us/ENABLE_DIAGS': No such file or directory
[root@[192_168_15_244] us]# mount -text3 /dev/mmcblk0p1 /mnt/us/tmp
mount: wrong fs type, bad option, bad superblock on /dev/mmcblk0p1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
...
|
It did exactly as expected.
You are trying to mount a drive that you just zeroed out. It will be reformatted as ext3 by the startup scripts when you reboot, and then it will be mounted and some files and folders will be added to it. Your settings will be set to defaults, so you will need to go into the settings menu to make any changes you need, such as locale and wifi settings.
You will also need to update to whatever firmware version you want. Sometimes an update can take a long time, and can look bricked, when it is really just "busy".
You can reboot with a "reboot" command, after the "idme" command that you did. Do a reboot command INSTEAD OF trying the mount the zeroed drive, in the transcript above.