From: "Tyler Littlefield" <tyler@tysdomain.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: root fs has suddenly became read only
Date: Sun, 17 Aug 2008 07:26:47 -0600 [thread overview]
Message-ID: <002601c9006c$e6e4c4b0$4200a8c0@tdsportable> (raw)
In-Reply-To: <48A7EFB3.7060407@baechler.net>
hello,
I ran an fsck and the problem is solved. :)
Thanks,
~~TheCreator~~
Visit TDS for quality software and website production
http://tysdomain.com
visit the piratecafe for programming related resources:
http://piratecafe.net
msn: tyler@tysdomain.com
skype: st8amnd127
----- Original Message -----
From: "Tony Baechler" <tony@baechler.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, August 17, 2008 3:30 AM
Subject: Re: root fs has suddenly became read only
> Tyler Littlefield wrote:
>> I was wondering if anyone had any ideas. everything under / is now
>> read-only.
>>
>
>
>
> Hi,
>
> Can you give more details? What distro are you using? What did you do
> right before that happened? Were there any messages in any logs like
> syslog or dmesg? Are you booting from a live CD which mounts your drives
> as ro? Have you ran fsck or had file system errors lately? Did your
> computer lock up and not shut down properly? This is doubtful, but are
> you using the ext2 filesystem without journaling? Is there an error in
> your boot scripts that prevents it from switching to mounting RW?
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> __________ NOD32 3361 (20080816) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Tyler Littlefield
` Tony Baechler
` Tyler Littlefield [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002601c9006c$e6e4c4b0$4200a8c0@tdsportable' \
--to=tyler@tysdomain.com \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).