Quote:
Originally Posted by geekmaster
They "documented" command also limits it to writing 1K blocks (4MB). The way I showed you always worked for me, but some people had problems zeroing the entire device. It is NORMAL for an "out of space" error to occur when you do not limit the size, because the /dev/zero source is infinite capacity.
If that does not work, try it again with as documented in the guide.
|
Here's the putty result using the documented command:
Quote:
login as: root
root@192.168.15.244's password:
#################################################
# N O T I C E * N O T I C E * N O T I C E #
#################################################
Rootfs is mounted read-only. Invoke mntroot rw to
switch back to a writable rootfs.
#################################################
[root@[192_168_15_244] root]# dd if=/dev/zero of=/dev/mmcblk0p3 bs=4K count=1K
1024+0 records in
1024+0 records out
4194304 bytes (4.0MB) copied, 0.080287 seconds, 49.8MB/s
[root@[192_168_15_244] root]# rm /mnt/us/ENABLE_DIAGS
rm: can't remove '/mnt/us/ENABLE_DIAGS': No such file or directory
[root@[192_168_15_244] root]# 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] root]# reboot
|
It's currently sitting at the Enable USBnet screen, with an amber light. I cannot navigate.
Should I try a hard boot? Or let it sit for a bit?