Thomas Exner wrote:
> when running fsck the first error message is "ROOT INODE UNALLOCATED"
> ...
> Is there a chance to get the data back?
Dunno about current versions, but IIRC some earlier versions of
dump(8) could handle even a badly-corrupted FS. No harm in trying,
since it will not try to
Dear all:
I have a very similar problem as Roland Smith almost two years ago. My
hard drive got corrupted (I do not really know why) and when running
fsck the first error message is "ROOT INODE UNALLOCATED" (the full
output of fsck is given below. I can then type "y" and it looks like
that fs
Roland Smith writes:
> > huff@>> fsck /dev/da3a
> > ** /dev/da3a
> > ** Last Mounted on /backup
> > ** Phase 1 - Check Blocks and Sizes
> > ** Phase 2 - Check Pathnames
> > ROOT INODE UNALLOCATED
> > ALLOCATE? [yn]
> >
> >a) what's probably happened?
>
> Error messages are expla
On Fri, 6 Feb 2009 14:48:41 -0500, Robert Huff wrote:
>
> Had a power outage recently; when trying to fsck several
> external hard drives I'm getting unexpected errors.
> For example:
>
> huff@>> fsck /dev/da3a
> ** /dev/da3a
> ** Last Mounted on /backup
> ** Phase 1 - Check Blocks a
On Fri, Feb 06, 2009 at 02:48:41PM -0500, Robert Huff wrote:
>
> Had a power outage recently; when trying to fsck several
> external hard drives I'm getting unexpected errors.
> For example:
>
> huff@>> fsck /dev/da3a
> ** /dev/da3a
> ** Last Mounted on /backup
> ** Phase 1 - Check Bl
Had a power outage recently; when trying to fsck several
external hard drives I'm getting unexpected errors.
For example:
huff@>> fsck /dev/da3a
** /dev/da3a
** Last Mounted on /backup
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
ROOT INODE UNALLOCATED
ALLOCATE
