- Site menu:
- Latest Discussions
- Latest Newswire
- Archives
- Submit Story
- Story HOWTO
- Syndicate
- E-mail Alerts
Fsck errors in the Linux filesystem on my OpenBSD laptop NOT caused by OpenBSD
|
|
|
Comments (3)
It could be that Puppy Linux is powering down too soon after unmounting. It might be that the disks cache has a few I/O's pending when it loses power. Is the disk spinning when the power goes off? Try poking around in the init shutdown scripts and find the part where it unmounts and try putting a /usr/bin/sleep 30 in there (after the unmount to give it another 30 seconds).
How to invoke /usr/bin/sleep if all disks are unmounted?
Good question, I think the root partition gets remounted as read only.
Edit: Slackware is doing this in rc.0 (which is a BSD style init script)
# This never hurts again (especially since root-on-LVM always fails # to deactivate the / logical volume... but at least it was # remounted as read-only first) /bin/sync
# sleep 3 fixes problems with some hard drives that don't # otherwise finish syncing before reboot or poweroff /bin/sleep 3
# This is to ensure all processes have completed on SMP machines: wait
Edit: Slackware is doing this in rc.0 (which is a BSD style init script)
# This never hurts again (especially since root-on-LVM always fails # to deactivate the / logical volume... but at least it was # remounted as read-only first) /bin/sync
# sleep 3 fixes problems with some hard drives that don't # otherwise finish syncing before reboot or poweroff /bin/sleep 3
# This is to ensure all processes have completed on SMP machines: wait
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post