View Single Post
Old 06-21-2016, 02:44 PM   #29
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by encol View Post
i just tried, nothing changed.
But WHY a reboot from ssh does not cause this problem?
The reboot method may just be a coincidence. It may have been sequential degradation regardless of reboot method. Your rw-mounted rootfs may be eating itself.


Perhaps it froze at the kindletree screen because it is full? I have rarely seen anything in lab126 scripts that check to see if sufficient space is available -- even "too many books" has been a problem in the past. It might be stuck trying to update something in /etc, for example. The serial port may display status messages that could give you a clue.

Last edited by geekmaster; 06-21-2016 at 02:57 PM.
geekmaster is offline   Reply With Quote