Thanks, Clark. I do think it's probably best to run fsck by default at
boot, but under conditions where I'm sure everything has been cleanly
shutdown, I'd like to be able to skip it. I read that one can use
"shutdown -hf now" to cause fsck to be skipped at the next boot, but I
see that this causes a fastboot to occur. In my case, this causes the
system to boot into the TS shell and I have to "exit" out of that shell
to continue the normal SD boot. Can someone help me to get a fastboot to
continue on with an SD boot, rather than needing a user to enter "exit"?
Don
On 9/1/2011 6:56 PM, Clark Dunson wrote:
Hey Don;
We run Read-Only debian (http://wiki.debian.org/ReadonlyRoot) out of
jfs, and use /etc/fstab to control this. We mount "/" as read-only,
and "/var" as read/write. I found that forcing an fsck at every boot
causes automatic journal recovery for our "/var" partition and is a
must. Now I have yanked the power a ton of times and she always
comes back up (so far :).
- Clark
On Sep 1, 2011, at 3:33 PM, Don Tucker wrote:
> This does not appear to have been a problem for anyone, but if it
> becomes a problem for someone in the future, this is what I believe
> is happening. I think that jfs mounts the root file system as read
> only in the event that it detects the file system as bad. I'm not
> sure what the normal behavior for a rootfs with jfs is, because
> there is no entry in /etc/fstab for "/" on my board. My proposed
> solution is to attempt to touch a file in /etc/rc.local, and if
> there is a failure (e.g. "touch: cannot touch 'testfile': Read-only
> file system"), then reboot forcing fsck (i.e. "shutdown -rF now").
>
> Don
>
> On 8/29/2011 5:23 PM, Don Tucker wrote:
>>
>> I've noticed that sometimes my TS-7260, booting to an SD card with
>> a Debian file system, will sometimes return errors during file
>> writes, reporting that the file system is read-only. I think this
>> might happen if the the system hasn't been properly shutdown, but
>> I haven't been able to consistently reproduce the behavior. Can
>> anyone explain a possible reason for why I'm seeing this?
>>
>> Thanks in advance,
>> Don
>>
>
smime.p7s
Description: S/MIME Cryptographic Signature
|