Hi
for me openwrt also doesnt umount the disk ... okay i mount them by hand (in an
init script) and i dont add them to fstab but i found a
simple but effective solution...
maybe im wrong but for me it seems a poweroff/reboot doesnt bring any service
down
,as it is done on my desktop box, it just reboots without killing the runnung
apps...
therefor openssh and dropbear doesnt unconnect on a reboot and the connection
is dropped when the router is up again ... the shell where the
poweroff/reboot command is typed in just "hangs"
to avoid this and get a clean umount of my disk i do this....
i dont use dropbear thefor i stop the sshd script in init.d i dont know if the
dropbears init script has the same name ...
to /etc/profile add this lines and source the file or logout and login again so
that
the the changes are used in the current shell ... ash --login should also work
...
the portmap and nfsd script are stop and syslog is killed because
if they are not killed the fs wont correctly umount
romount() { /etc/init.d/portmap stop
/etc/init.d/nfsd stop
killall syslogd
for i in `cat /proc/mounts|grep "^/dev/"|sed -e "s/ .*//g"|sort
-r|uniq`
do umount -rf $i
done
echo 0 > /proc/diag/led/power
ifdown wan
}
reboot() { romount > /dev/null 2>&1
/sbin/reboot
/etc/init.d/sshd stop
exit
}
poweroff() { romount > /dev/null 2>&1
/sbin/poweroff
/etc/init.d/sshd stop
exit
}
greets
Am Samstag 30 Januar 2010 14:13:57 schrieb [email protected]:
> Is there a sync command before the unmount?
>
> Maybe the system does not reach the umount call, and therefor it is
> never cleanly unmounted? You could debug that.
>
> Maybe the controller is caching and needs specific commands to write the
> cache to disc? Did you search the web?
>
> good luck, ede
>
> On 30.01.2010 00:11, Gerlando Falauto wrote:
> > Hi all,
> >
> > I am (slowly) experimenting with my LaCie Ethernet Disk Mini v2 NAS.
> > In order to maintain compatibility with Lacie's software, I did not
> > change the disk layout (yet).
> > I can run my own OpenWRT without disrupting the original firmware
> > by putting the kernel's uImage on [sda9]/snaps/00/boot and the root
> > filesystem on [sda2] which is an xfs partition (it's the 300GB user
> > partition) mounted as read/write.
> >
> > Now every time I shutdown the box, my xfs filesystem gets corrupted
> > and at the next reboot
> > kernel ends up panicking because it can't mount the root filesystem to
> > find an init file.
> >
> > I figured the shutdown sequence did not correctly unmount my filesystem;
> > I found the executed command was "umount -a -r", so I tried doing it
> > manually:
> >
> > r...@openwrt:~# umount -a -r
> > umount: devpts busy - remounted read-only
> > umount: tmpfs busy - remounted read-only
> > umount: tmpfs busy - remounted read-only
> > umount: can't remount /dev/root read-only
> > umount: can't remount rootfs read-only
> >
> > r...@openwrt:~# mount -t proc proc /proc
> > r...@openwrt:~# umount -r /
> > umount: can't remount /dev/root read-only
> >
> > I know that mounting the initial root filesystem as read-write is not
> > a very nice thing to do,
> > but could someone please point out why it's, like, forbidden by law,
> > so that I even get punished for doing it?
> >
> > Thanks a lot!
> > Gerlando
> > _______________________________________________
> > openwrt-devel mailing list
> > [email protected]
> > https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
> _______________________________________________
> openwrt-devel mailing list
> [email protected]
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
