- Check Pathnames
UNALLOCATED I=5 OWNER=root MODE=0
SIZE=0 MTIME=Apr 22 17:28 2007
NAME=/lost+found
UNEXPECTED SOFT UPDATE INCONSISTENCY
REMOVE? [yn
On Mon, 23 Apr 2007, L Goodwin wrote:
[...]
I assume I'll have to run fsck on /usr, but have 2 questions:
1) Is this problem caused by yesterday's accidental power-off?
Yes, most likely.
2) What prompts should I expect from fsck, and how should I reply to each in
order to resolve this
Thanks, Garrett.
Ran fsck -y /usr
* FILE SYSTEM MARKED CLEAN *
* FILE SYSTEM WAS MODIFIED *
Upon reboot, all is well EXCEPT for the following 2 warnings:
---
Mounting
On Mon, 23 Apr 2007 13:23:16 -0700 (PDT)
L Goodwin [EMAIL PROTECTED] wrote:
Last night, I was starting to install Samba3, but wrong FreeBSD disc
(2) in the CD-ROM drive (first package to install on disc 1). After
placing the right disc in the drive, I accidentally pushed the POWER
button
Yes, it's a hardware switch and a very bad design. It's flush with the surface
of the faceplate and is right next to the CD-ROM button. Also sensitive to the
lightest touch. Replacement would require buying a new case (not in budget).
Think I'll make a clear plexi failsafe cover. Reminds me of
L Goodwin writes:
I accidentally pushed the POWER button instead of the CD-ROM door
open/close button and turned the computer off. In my defense, the
power button is right next to it AND has a hair trigger. :-(
I turned the computer back on, and FreeBSD booted with no
complaints, so
Thanks, Robert.
Robert Huff [EMAIL PROTECTED] wrote:
L Goodwin writes:
I accidentally pushed the POWER button instead of the CD-ROM door
open/close button and turned the computer off. In my defense, the
power button is right next to it AND has a hair trigger. :-(
I turned the
On Thu, Aug 11, 2005 at 03:05:06PM +1000, Jerahmy Pocott wrote:
Hello everyone,
After a server lost power unexpectedly (read: someone pulled the plug
out), on reboot
the automatic fsck failed with UNEXPECTED SOFT UPDATE INCONSISTENCY as
the message. Running fsck interactively doesn't seem
THE FOLLOWING DISK SECTORS COULD NOT BE READ: 66322510,
Sounds like a HW issue to me.
Anyway to confirm this? It is not a very old drive and the filesystem
is still readable,
I suppose it could have developed some bad sectors..
Is there a way to flag them as bad without formating
At 03:49 PM 8/11/2005, Jerahmy Pocott wrote:
THE FOLLOWING DISK SECTORS COULD NOT BE READ: 66322510,
Sounds like a HW issue to me.
Anyway to confirm this? It is not a very old drive and the filesystem
is still readable,
I suppose it could have developed some bad sectors..
If you have
Hello everyone,
After a server lost power unexpectedly (read: someone pulled the plug
out), on reboot
the automatic fsck failed with UNEXPECTED SOFT UPDATE INCONSISTENCY as
the message. Running fsck interactively doesn't seem to be able to
fix it..
Every time in phase one it says:
CANNOT
On Aug 10, 2005, at 11:05 PM, Jerahmy Pocott wrote:
THE FOLLOWING DISK SECTORS COULD NOT BE READ: 66322510,
Sounds like a HW issue to me.
---
Chad Leigh -- Shire.Net LLC
Your Web App and Email hosting provider
[EMAIL PROTECTED]
___
Hi Everyone,
A user is having a problem accessing their maildir. The problem arose
when we tried to access it as well. When doing an ls in their directory
the one file returns the following:
ls -l
1104761413.M777698P25745V0400FF01I0239B49E_0.rmail4.enter.net\,S\=6806
ls:
. However:
I *very* quickly ran into a case where I got an unexpected soft update
inconsistency after crashing the machine by doing something naughty with
Vinum while there was disk activity (note: the filesystem which exhibited the
problem was not on a vinum volume).
So my question is:
Do
On Tue, Jan 20, 2004 at 12:31:30AM +0100, Peter Schuller wrote:
Do soft updates, or do they not, algorithmically guarantee filesystem
meta-data consistency in the event of a crash?
If you have a power failure or similar unclean shutdown, then SU
guarantees consistency. If there is a kernel
* quickly ran into a case where I got an unexpected soft update
inconsistency after crashing the machine by doing something naughty with
Vinum while there was disk activity (note: the filesystem which exhibited the
problem was not on a vinum volume).
So my question is:
Do soft updates, or do
something wrong with the
filesystem, went to singleuser with `shutdown now`, ran fsck(8), and got
some unexpected soft update inconsistency messages in my ~/Mail.
The filesystem is always ok during the normal boot-time fsck run, so I'm
wondering whether this is normal, or if the fs is screwed
://www.eyrie.org./~eagle/faqs/questions.html
2141 files, 24867 used, 233164 free UNALLOCATED
FILE=/var/spool/postfix/incoming/0/2/0236D2FDAB2
UNEXPECTED SOFT UPDATE INCONSISTENCY
SUMMARY INFORMATION BADBLK(S) MISSING IN BIT MAPSFREE BLK COUNT(S) WRONG IN
SUPERBLKALLOCATED FRAG 12580728 MARKED FREE
On Sat, Jun 14, 2003 at 12:58:34PM +0200, Roman Neuhauser wrote:
The filesystem is always ok during the normal boot-time fsck run, so I'm
wondering whether this is normal, or if the fs is screwed. Attached is
the output of fsck(8) run in multiuser (postfix was running).
[EMAIL PROTECTED] ~
** Phase 1 - Check Blocks and Sizes
CANNOT READ: BLK 152744928
UNEXPECTED SOFT UPDATE INCONSISTENCY
CONTINUE? [yn] y
THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152744946,
CANNOT READ: BLK 152745312
UNEXPECTED SOFT UPDATE INCONSISTENCY
CONTINUE? [yn] y
On Mon, Dec 09, 2002 at 10:21:39AM +1100, Andrew Cutler wrote:
Unfortunately the answer presented itself very soon after posting the
message.
I pulled the hard drive out of the box, and tried to format it in a
Windows machine. It occurred to me that the drive had not been formated
and
SOFT UPDATE INCONSISTENCY
CONTINUE? [yn] y
THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152744946,
CANNOT READ: BLK 152745312
UNEXPECTED SOFT UPDATE INCONSISTENCY
CONTINUE? [yn] y
THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152745393,
CANNOT READ: BLK 152746208
UNEXPECTED SOFT UPDATE
On Fri, 29 Nov 2002, Vinco Maldini wrote:
1) What does the result below mean? (Is my drive failing? Why can't I
clean the FS?)
[ ... snip ... ]
CANNOT READ: BLK 152744928
UNEXPECTED SOFT UPDATE INCONSISTENCY
[ ... snip ... ]
THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152744946
On Fri, 29 Nov 2002, Vinco Maldini wrote:
1) What does the result below mean? (Is my drive failing? Why can't I
clean the FS?)
[ ... snip ... ]
CANNOT READ: BLK 152744928
UNEXPECTED SOFT UPDATE INCONSISTENCY
[ ... snip ... ]
THE FOLLOWING DISK SECTORS COULD NOT BE READ: 152744946
2) Are there any BSD tools for reading the SMART data off the Hard Disk
so that I can see whether it is about to fail or currently experiencing
HW failure. Any other ways to check for bad sectors?
JH I thought that someone asked this same questions a few days ago, but I
JH can't find it in
it is about to fail or currently experiencing
HW failure.
TIA
Andrew Cutler
- START SCREEN SNIPPET
mojo# fsck /dev/ad2s1e
** /dev/ad2s1e
** Last Mounted on /data
** Phase 1 - Check Blocks and Sizes
CANNOT READ: BLK 152744928
UNEXPECTED SOFT UPDATE INCONSISTENCY
26 matches
Mail list logo
