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
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 an
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 the
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]
___
freebsd-questi
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:
CANNO
