Here's a way to work around this problem which from discussion effects only a
nand install and must be (I think) a kernel bug. Save this as
clean_shutdown.sh and follow the commented instructions:-
_
#!/bin/bash
#put this
2011-03-09@20:26 Neil Jerram
> Interesting. Is there a way to check for the "filesystem was not
> unmounted cleanly" status without removing the uSD and taking it to
> another computer?
>
>Neil
yes, you can play with the usb file storage gadget module.
==> /opt/qtmoko/bin/usb-mass-storag
On 9 March 2011 20:07, dmatthews.org wrote:
> I think I should add to my own post to mention that I briefly tried the
> January SHR testing a few weeks ago. That had the same problem ie (even) a
> clean shutdown -> fsck reporting improper unmounting of the uSD.
Interesting. Is there a way to c
I think I should add to my own post to mention that I briefly tried the January
SHR testing a few weeks ago. That had the same problem ie (even) a clean
shutdown -> fsck reporting improper unmounting of the uSD.
To summarize my experience:-
qtmoko v26 - this problem does not happen
SHR testing -
> mmh.. I can't say anything on this topic... I've never tried nand since
> om2008 :P
> maybe it's a bug specific for nand users with a uSD partition?
>
yes maybe - I always use the nand though and this did not happen with v26
> please try this:
> log-in via usb-ssh on your moko
> /etc/init.d/
> > no, not here.
> > I've v33 and works for me! (full installation on uSD with 3
> > partitions: storage/rootfs/swap)
>
> My roofs is on nand; the rootfs unmounts cleanly, but not the uSD based
> partition that I automount on /media/card
mmh.. I can't say anything on this topic... I've never tr
> no, not here.
> I've v33 and works for me! (full installation on uSD with 3
> partitions: storage/rootfs/swap)
My roofs is on nand; the rootfs unmounts cleanly, but not the uSD based
partition that I automount on /media/card
> rather, are you 100% sure about your hardware clock? otherwise sy
no, not here.
I've v33 and works for me! (full installation on uSD with 3
partitions: storage/rootfs/swap)
rather, are you 100% sure about your hardware clock? otherwise system
vs rtc clock skews may trigger a check of the filesystem!
regards.
On Wed, Mar 9, 2011 at 6:36 PM, dmatthews.org wrot
I do think this is a bug new in v33
as described below any shutdown/reboot, whether from commandline or gui, means
that a fsck of the card reports it was not cleanly unmounted.
I ran
lsof | grep /media/card
to show no open files - but this is too regular (100% reproducible) and never
happen
9 matches
Mail list logo
