Re: [SLE] Partition suddenly going into read-only status

On Friday 27 October 2006 18:45, LDB wrote:
I recently had my SuSE 10.0 installation have its
root partition go into read-only mode - It was proposed
that my disk is going bad. I rebooted and everything
is fine after the reboot.

No, nothing changed. It just suddenly went into read-only mode.

Any ideas?

Hi LDB,

Spontaneously dropping into read-only ("dirty") mode is a sign of a failed
hard disk read or write operation. You were forced to reboot which, in turn,
caused the appropriate flavor of 'fsck' to be run automatically on the
unmounted partition. Apparently, the filesystem was successfully "cleaned"
and put back into service, but you'll be a much happier camper if you take
preemptive measures, now, instead of waiting for this 'transient' problem to
reappear.

In my experience, the frequency and severity of 'transient' drive errors only
increases over time... sometimes failures happen very soon and are severe...
other times you can 'stumble along' for several weeks or even months. One
thing you *can* be sure of, though, is *transient* errors and hard disks are
*not* a good mix. :-)

I'd check to see if a bootable floppy or CD-ROM based diagnostic utility is
available at the drive manufacturer's website. If S.M.A.R.T. is supported and
enabled, this may tell you more about the problem. I'd also make timely
backups of any data and configuration files, just in case.

hth & regards,

Carl

--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx

Relevant Pages

  • Re: [SLE] Partition suddenly going into read-only status
    ... root partition go into read-only mode - It was proposed ... It just suddenly went into read-only mode. ... Spontaneously dropping into read-only mode is a sign of a failed hard disk read or write operation. ... You were forced to reboot which, in turn, caused the appropriate flavor of 'fsck' to be run automatically on the unmounted partition. ...
    (SuSE)
  • Re: [SLE] Partition suddenly going into read-only status
    ... root partition go into read-only mode - It was proposed ... It just suddenly went into read-only mode. ... Spontaneously dropping into read-only mode is a sign of a failed hard disk read or write operation. ... You were forced to reboot which, in turn, caused the appropriate flavor of 'fsck' to be run automatically on the unmounted partition. ...
    (SuSE)
  • [SLE] Partition suddenly going into read-only status
    ... root partition go into read-only mode - It was proposed ... that my disk is going bad. ... is fine after the reboot. ... It just suddenly went into read-only mode. ...
    (SuSE)
  • Re: Prevent command prompt from popping up at system startup
    ... -You want to run ewfmgr -commit to commit the data files to disk. ... This won't use up your RAM overlay. ... would be hard to estimate how big the EWF overlay can be. ... you can always force your device to reboot on a scheduled ...
    (microsoft.public.windowsxp.embedded)
  • Re: hard drive scrubbing utility
    ... disk scrubber could be bypassed by a rootkit, or even another level of filter driver. ... So if I put my secret data on the computer, ... each windows XP software system at each reboot. ... I have some ideas as to a method to scrub a hard drive on the fly. ...
    (microsoft.public.vc.mfc)