can't mount fs back to ro

[knc1]

It is a lab126 screw-up.

Notice all of the /dev/root being used for /chroot/* ?

All of that "chroot" stuff is relatively (by firmware version) "new".

[geekmaster]

I just tried 'mntroot rw' then 'mount', which showed both '/' mounts as 'rw'. Then I did 'mntroot ro' (while in /var/tmp/root/ folder), and 'mount' showed '/dev/root' as 'ro' again (no error message). And I have CRP and pals on it too.

No idea what is holding yours open so it cannot remount, nor why it mounts that way on a reboot. How are you rebooting? Did you do a 'reboot' shell command, or something else?

And the command you extracted from 'mntroot' looks fishy, considering that '/' is a generic shared mountpoint now. That looks like trouble in the paradise to me (experience shows that only ONE of those mounts gets remounted, and without specifying which one, it is a fools gambit to do it the way they did). However, with that said, 'mntroot ro' worked for me (this time).

[encol]

Originally Posted by geekmaster

How are you rebooting? Did you do a 'reboot' shell command, or something else?

AAARGH! i did it by shell command before, now i tried restarting from UI settings and now it is stuck in the "Man under tree"!

[geekmaster]

Originally Posted by encol

AAARGH! i did it by shell command before, now i tried restarting from UI settings and now it is stuck in the "Man under tree"!

Can you boot to diags with CRP (hard reboot while charging)? If not, you've got some learning to do, for sure... even with diags, perhaps... lessons learned hard but deep.

We need more info from you to figure that one out. Perhaps if you CAN get to diags, reflashing main does not seem so bad now. But try hard-rebooting first (but not enough reboots to trigger "your kindle needs repair"). I hope you have CRP (coward's rescue pack) installed. And hopefully you do not need to use the serial port to flash a clean rootfs.

Also, did it boot far enough to see the USB drive (full capacity, not 0MB fake drive)?

[encol]

I connected usb cable to PC, i long-pressed power button, "tree screen" disappears and then re-appears, but it does not enter in diags mode, and i can't see it as usb storage (usbnet was up before reboot)

[geekmaster]

Originally Posted by encol

I connected usb cable to PC, i long-pressed power button, "tree screen" disappears and then re-appears, but it does not enter in diags mode, and i can't see it as usb storage (usbnet was up before reboot)

USBnet? Can you SSH in?

[encol]

Originally Posted by geekmaster

But try hard-rebooting first (but not enough reboots to trigger "your kindle needs repair"). I hope you have CRP (coward's rescue pack) installed. And hopefully you do not need to use the serial port to flash a clean rootfs.

Also, did it boot far enough to see the USB drive (full capacity, not 0MB fake drive)?

CRP is installed, but it does not enter in the diags mode: i see only the "man under tree"
I'm not sure how to do "hard-rebooting": i just connected usb cable to my pc and then i made a long-press on the power button

I don't see any USB drive

i can't ssh to it

[geekmaster]

Try using a USB charger instead of connecting to your PC. You might have USB power saver timing interference (unless you turned it off in your PC BIOS and/or in your OS).

[encol]

Same behavior

How long i have to do the "long press"?
When the led starts blinking i have to release it?

[geekmaster]

Originally Posted by encol

Same behavior

How long i have to do the "long press"?
When the led starts blinking i have to release it?

Longer than when it starts blinking, I think, but 40 seconds is probably more than enough -- try holding it longer. Or maybe whatever is causing /dev/root be rw is also causing your current problem.

If you cannot get to diags, you may need to use the serial port to fix this problem.

[encol]

Originally Posted by geekmaster

try holding it longer

i just tried, nothing changed.
But WHY a reboot from ssh does not cause this problem?

[knc1]

Reboot or "shutdown -r now" ?

[encol]

reboot

[geekmaster]

Originally Posted by encol

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.

[encol]

i had only 3 books in it