<LL control="dev/sys/sdtest" value="SD performance read=540kB/s write=422kB/s no error (0 0), ManufactorerID 27 Date 2014/2 CardType 2 Blocksize 512 Erase 0 MaxtransferRate 25000000 RWfactor 2 ReadSpeed 22222222Hz WriteSpeed 22222222Hz MaxReadCurrentVDDmin 3 MaxReadCurrentVDDmax 5 MaxWriteCurrentVDDmin 3 MaxWriteCurrentVDDmax 1" Code="200"/>
I found that without this new updates don't stay put after a reboot.
It's pretty useless on their part, but I would assume there are multiple configurations saved in the Miniserver which are timestamped and if it doesn't know the correct time that doesn't work and the wrong (old) config is loaded at boot. Just a guess though. If this is the issue you'd have to ask why they didn't just use a sequence number stored on the SD card?
Robin
Try pining the miniserver. I had a faulty cable that was causing errors too.
--- 192.168.0.183 ping statistics ---
57 packets transmitted, 57 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.305/0.393/0.540/0.039 ms